Author: Mahajan, K.
Paper Title Page
MOPPC079
CODAC Core System, the ITER Software Distribution for I&C 281
 
  • F. Di Maio, L. Abadie, C.S. Kim, K. Mahajan, D. Stepanov, N. Utzel
    ITER Organization, St. Paul lez Durance, France
 
  In order to support the adoption of the ITER standards for the Instrumentation & Control (I&C) and to prepare for the integration of the plant systems I&C developed by many distributed suppliers, the ITER Organization is providing the I&C developers with a software distribution named CODAC Core System. This software has been released as incremental versions since 2010, starting from preliminary releases and with stable versions since 2012. It includes the operating system, the EPICS control framework and the tools required to develop and test the software for the controllers, central servers and operator terminals. Some components have been adopted from the EPICS community and adapted to the ITER needs, in collaboration with the other users. This is the case for the CODAC services for operation, such as operator HMI, alarms or archives. Other components have been developed specifically for the ITER project. This applies to the Self-Description Data configuration tools. This paper describes the current version (4.0) of the software as released in February 2013 with details on the components and on the process for its development, distribution and support.  
poster icon Poster MOPPC079 [1.744 MB]  
 
TUCOAAB03
Approaching the Final Design of ITER Control System 490
 
  • A. Wallander, L. Abadie, F. Di Maio, B. Evrard, C. Fernandez Robles, J.L. Fernández-Hernando, J-M. Fourneron, J.Y. Journeaux, C.S. Kim, K. Mahajan, P. Makijarvi, S. Pande, M.K. Park, V. Patel, P. Petitbas, N. Pons, A. Simelio, S. Simrock, D. Stepanov, N. Utzel, A. Vergara-Fernandez, A. Winter, I. Yonekawa
    ITER Organization, St. Paul lez Durance, France
 
  The control system of ITER (CODAC) is subject to a final design review early 2014, with a second final design review covering high-level applications scheduled for 2015. The system architecture has been established and all plant systems required for first plasma have been identified. Interfaces are being detailed, which is a key activity to prepare for integration. A built to print design of the network infrastructure covering the full site is in place and installation is expected to start next year. The common software deployed in the local plant systems as well as the central system, called CODAC Core System and based on EPICS, has reached maturity providing most of the required functions. It is currently used by 55 organizations throughout the world involved in the development of plant systems and ITER controls. The first plant systems are expected to arrive on site in 2015 starting a five-year integration phase to prepare for first plasma operation. In this paper, we report on the progress made on ITER control system over the last two years and outline the plans and strategies allowing us to integrate hundreds of plant systems procured in-kind by the seven ITER members.  
slides icon Slides TUCOAAB03 [5.294 MB]  
 
THPPC004
CODAC Standardisation of PLC Communication 1097
 
  • S. Pande, F. Di Maio, B. Evrard, K. Mahajan, P. Sawantdesai, A. Simelio, A. Wallander, I. Yonekawa
    ITER Organization, St. Paul lez Durance, France
 
  As defined by the CODAC Architecture of ITER, a Plant System Host (PSH) and one or more Slow Controllers (SIEMENS PLCs) are connected over a switched Industrial Ethernet (IE) network. An important part of Software Engineering of Slow Controllers is the standardization of communication between PSH and PLCs. Based on prototyping and performance evaluation, Open IE Communication over TCP was selected. It is implemented on PLCs to support the CODAC data model of ‘State’, ‘Configuration’ and ‘Simple Commands’. The implementation is packaged in Standard PLC Software Structure(SPSS) as a part of CODAC Core System release. SPSS can be easily configured by the SDD Tools of CODAC. However Open IE Communication is restricted to the PLC CPUs. This presents a challenge to implement redundant PLC architecture and use remote IO modules. Another version of SPSS is developed to support communication over Communication Processors(CP). The EPICS driver is also extended to support redundancy transparent to the CODAC applications. Issues of PLC communication standardization in the context of CODAC environment and future development of SPSS and EPICS driver are presented here.