1. F. Di Maio ITER IO / CHD / CIT / CODAC
CODAC Core System
F. Di Maio
ITER
IO / CHD / CIT / CODAC

2. Introduction
ITER is a large experimental facility built and procured by many partners, distributed in all the member states, over a long construction period.
ITER Organization (IO) must specify and support standards
EPICS is the standard software environment for the ITER controls (2009).
Technical specifications for the plant systems controls are issued by IO in the “Plant Control Design Handbook” (PCDH).
IO provides CODAC Core system, the uniform software package for the development of the plant systems instrumentation & control (I&C) supporting the PCDH standards.
PCDH 5.2:
The software infrastructure for PSH and Mini-CODAC is EPICS version R
[R111] EPICS version R shall be used for PS fast controllers.
[R112] Communication between PS fast controllers and PSH shall use EPICS Channel Access.

3. Plant System Instrumentation & Control (I&C) Architecture
Supplied by IO
Mini-CODAC: stand-alone system before integration
Linux, EPICS
Linux, EPICS
SIMATIC S7 PLC
Complete software
Development tools and standard components
Standard components for integration

4. Core System Releases Roadmap
2010/Q1
Version 1
Preliminary
Integration of PLCs
EPICS distribution
Self-description tools (preliminary)
Examples
2011/Q1
Version 2
(1st) Stable for developments
Extensions for fast controllers
Introduction of new Mini-CODAC tools APIs frozen
2012/Q1
Version 3
(1st) Stable for tests
New Mini-CODAC tools (CSS)
Robustness
There will be one version per year. These are the main objectives for the 1st ones.
Version 1 is a preliminary one and we shall stabilize the product 1st for development and then for the tests.
Because of the procurement schedule, the priority is on industrial controls but we shall also cover fast controllers, starting from version 2.
ITER-Specific methods and tools (self-description) are a priority, from version 1.

5. Area of work Software management and software distribution
With possible sharing of results and efforts
Software management and software distribution
Configuration data (“SDD”)
Slow controllers (PLC) integration
Mini-CODAC tools (plant system development and tests)
Fast controllers support

6. 1 - Software Management / Software Distribution
RHEL (64 bits) is the selected Linux distribution, ITER users are provided with the RHEL distribution by IO
RHEL 5.3 in vs 1.
RHEL 5.5 in vs 2
EPICS components ( ) and ITER ones are managed in an IO SVN repository, built as RPMs and distributed using IO Satellite Server(s) as official releases to be shared by all ITER users.
Support is set-up for ITER community registered users.
Online support by Cosylab and IO.
Issue reporting and tracking system (Bugzilla).
Special arrangement to support ITER tasks.
Sharing with other EPICS users could be discussed.

7. Distribution Management
Software
Distribution Management
CODAC Core System
EPICS
Red Hat Linux
IO’s RedHat Network Satellite
Server
Version Control Repository
Development Work
Published Version
Internet
The developers can work locally or globally, with or without using the codac-dev.iter.org access
The development work is managed using the svn.iter.org version control repository
When a version of CODAC Core System is read to be published, it is packaged in Red Hat Package Manager (RPM) format
The packaged RPM format files are stored on a Red Hat Network Satellite server
The Red Hat Network Satellite server is maintaining the RPM files in a database
The RPM database is structured in elements called “Channels”
The are Channels for “development”, “run-time”, and so on
Users can subscribe to these channels through their yum client
The Red Hat Network Satellite server is maintaining ITER managed copies of EPICS framework and Red Hat Linux operating system
Internal and external systems for development, as well as the target systems are installed from same source, the Red Hat Network Satellite Server
Subscribed systems can get updates of the CODAC Core System
Will be detailed by Matjaz Kobal (Cosylab) on Thursday. 7

8. 2 - Configuration Data - SDD
Self-Description Data (SDD) - An ITER concept
For each Plant System, the detailed configuration shall be supplied (XML representation compliant with a common schema).
The software shall be driven from this configuration data
In Vs 1:
A baseline version of the data model
A preliminary version of SDD editor and of translators to generate EPICS and STEP 7 data.
From Vs 2:
New implementation (Eclipse)
Use of RDB (PostgreSQL) + Web applications.
Link with EPICS application development (CSS DCT, VDCT, SNL…)

9. SDD
SDD v1 screenshots
Plant system I&C
Component type
Property 9

10. 3 - PLC Integration Siemens SIMATIC S7 communications:
Vs1: SLS S7 driver
Exchanges of data-blocks over TCP (send/receive S7 functions)
Good quality
Good performances
Considered for Vs2: Native S7 protocol.
Would require a new driver based on either open source library or on Siemens library.
More flexibility (direct access without specific code in the PLC)
Performances.
Integration via SDD:
SDD editor to describe the CODAC / Slow controller interface
SDD translator to generate the EPICS records, PLC data blocks and driver initialization

11. EPICS Records generated
PLC
EPICS Records generated
Process Variable
record (ao,"4511RT-TST-1:AOU8-JZ-CRC") {
field (DTYP,"S7plc")
field T=UINT8")
field (PINI,"YES") }
record (ao,"4511RT-TST-1:AOU16-JZ-CRC")
field =UINT16")
Device type – S7plc
record (ai,"4511RT-TST-1:AIU8-JT-CRC") {
field (DTYP,"S7plc")
field T=UINT8")
field (SCAN,"I/O Intr")
field (PINI,"YES") }
record (ai,"4511RT-TST-1:AIU16-JT-CRC")
field T=UINT16")
Configuration Properties
State Properties 12

12. PLC variables generated
DATA_BLOCK DB2
TITLE= Configuration Properties of channel 1
STRUCT
TST_1_AOU8_JZ_CRC :BYTE ;
TST_1_AOU16_JZ_CRC :WORD ;
TST_1_AOU32_JZ_CRC :DWORD ;
TST_1_AO8_JZ_CRC :CHAR ;
TST_1_AO16_JZ_CRC :INT ;
TST_1_AO32_JZ_CRC :DINT ;
TST_1_AOF_JZ_CRC :REAL ;
END_STRUCT
BEGIN
END_DATA_BLOCK
DATA_BLOCK DB3
TITLE= State Properties of channel 1
TST_1_AIU8_JT_CRC :BYTE ;
TST_1_AIU16_JT_CRC :WORD ;
TST_1_AIU32_JT_CRC :DWORD ;
TST_1_AI8_JT_CRC :CHAR ;
TST_1_AI16_JT_CRC :INT ;
TST_1_AI32_JT_CRC :DINT ;
TST_1_AIF_JT_CRC :REAL ;
Signal name
Component type
+ sequence number
Import the configuration files on S7
Develop/adopt PLC software using these interface variables 13

13. PLC sample Archive Viewer HMI Alarms PLC Connection Status
Configuration
State 14

14. 4 – Mini-CODAC Tools
Standard “core” services : HMI builder (synoptics), alarms handler, data archiver, error/trace logger…
From V1: Standard EPICS tools
EDM, ALH, SNL, Channel Archiver…
From V2: Control System Studio tools
SNS “suite” for alarms, synoptics, archive
SNL editor
DCT (?)
The ITER distribution includes a reference example, ICH Sample, that simulates the control of a RF source for Heating & Current Drive.
A clear area for
future collaborations

15. ICH Sample HMI
And we’ll demonstrate the samples in the afternoon. 16

16. 5 – Fast Controllers support
From now, ITER Organization prescribes/supports PCI Express (PCIe) for I/O.
Separated I/O chassis and CPU/Network chassis is the preferred solution.
Recommended configuration: a PXI Express chassis as a PCIe extension of an industrial computer, such as PICMG 1.3 based system.
IEEE is the candidate for the Time Communication Network
With Core System V2, EPICS drivers (RH) will be supplied for:
N.I. PXI-6682 : Synchronization and timing (IEEE )
N.I. PXIe-6368: General purpose I/O
16b, 32MS/s analog input
16b, 3.33 MS/s analog output
Digital I/O and 32b counters

17. Topics ITER contacts Thank you !
Software management and software distribution
Configuration data (“SDD”)
Slow controllers (PLC) integration
Mini-CODAC tools / CSS
Fast controllers support
Denis Stepanov, Petri Makijarvi, Changseung Kim
Lana Abadie, Denis Stepanov
Kirti Mahajan, Franck Di Maio
Nadine Utzel, Lana Abadie
Petri Makijarvi, Changseung Kim, Kirti Mahajan
Thank you !