CODAC Core System F Di Maio ITER IO

CODAC Core System F. Di Maio ITER IO / CHD / CIT / CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 1

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 3. 14. 11. [R 111] EPICS version R 3. 14. 11 shall be used for PS fast controllers. [R 112] Communication between PS fast controllers and PSH shall use EPICS Channel Access. CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 2

Plant System Instrumentation & Control (I&C) Architecture Supplied by IO Mini-CODAC: stand-alone system before integration Linux, EPICS Complete software Linux, EPICS Development tools and standard components SIMATIC S 7 PLC Standard components for integration CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 3

Core System Releases Roadmap Integration of PLCs EPICS distribution Self-description tools (preliminary) Examples 2010/Q 1 Version 1 Preliminary 2011/Q 1 Version 2 (1 st) Stable for developments Extensions for fast controllers Introduction of new Mini-CODAC tools APIs frozen 2012/Q 1 Version 3 (1 st) Stable for tests New Mini-CODAC tools (CSS) Robustness CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 4

Area of work With possible sharing of results and efforts 1. 2. 3. 4. Software management and software distribution Configuration data (“SDD”) Slow controllers (PLC) integration Mini-CODAC tools (plant system development and tests) 5. Fast controllers support CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 5

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 (3. 14. 11) 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. CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 6

Software Version Control Repository Distribution Management Development Work ion s r e d. V e lish b u P CODAC Core System EPICS Red Hat Linux IO’s Red. Hat Network Satellite Server Internet Will be detailed by Matjaz Kobal (Cosylab) on Thursday. CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 7

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 (Postgre. SQL) + Web applications. – Link with EPICS application development (CSS DCT, VDCT, SNL…) CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 8

SDD v 1 screenshots Plant system I&C Component type Property CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 9

3 - PLC Integration Siemens SIMATIC S 7 communications: § Vs 1: SLS S 7 driver – Exchanges of data-blocks over TCP (send/receive S 7 functions) – Good quality – Good performances § Considered for Vs 2: Native S 7 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 CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 11

PLC EPICS Records generated Process Variable Device type – S 7 plc record (ao, "4511 RT-TST-1: AOU 8 -JZ-CRC") { field (DTYP, "S 7 plc") record (ai, "4511 RT-TST-1: AIU 8 -JT-CRC") field (OUT, "@4511 RT-PCS-1 -1/0 T=UINT 8") { field (PINI, "YES") field (DTYP, "S 7 plc") } field (INP, "@4511 RT-PCS-1 -1/0 T=UINT 8") record (ao, "4511 RT-TST-1: AOU 16 -JZ-CRC")field (SCAN, "I/O Intr") { field (PINI, "YES") field (DTYP, "S 7 plc") } field (OUT, "@4511 RT-PCS-1 -1/2 =UINT 16") record (ai, "4511 RT-TST-1: AIU 16 -JT-CRC") field (PINI, "YES") { } Configuration Properties State Properties field (DTYP, "S 7 plc") field (INP, "@4511 RT-PCS-1 -1/2 T=UINT 16") field (SCAN, "I/O Intr") field (PINI, "YES") } CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 12

PLC variables generated DATA_BLOCK DB 2 Signal name TITLE= Configuration Properties of channel 1 STRUCT Component type TST_1_AOU 8_JZ_CRC : BYTE ; + sequence number TST_1_AOU 16_JZ_CRC : WORD ; TST_1_AOU 32_JZ_CRC : DWORD ; DATA_BLOCK DB 3 TST_1_AO 8_JZ_CRC : CHAR ; TITLE= TST_1_AO 16_JZ_CRC : INT ; State Properties of channel 1 STRUCT TST_1_AO 32_JZ_CRC : DINT ; : BYTE ; TST_1_AOF_JZ_CRC : REAL ; TST_1_AIU 8_JT_CRC TST_1_AIU 16_JT_CRC : WORD ; END_STRUCT TST_1_AIU 32_JT_CRC : DWORD ; BEGIN TST_1_AI 8_JT_CRC : CH END_DATA_BLOCK TST_1_AI 16_JT_CRC : INT ; • Import the configuration files on S 7 • Develop/adopt PLC software using these interface variables TST_1_AI 32_JT_CRC TST_1_AIF_JT_CRC END_STRUCT BEGIN END_DATA_BLOCK CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence : DINT ; : REA Page 13

PLC sample HMI Connection Status Archive Viewer Alarms Configuration State CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 14

4 – Mini-CODAC Tools Ø Standard “core” services : HMI builder (synoptics), alarms handler, data archiver, error/trace logger… • From V 1: Standard EPICS tools - EDM, ALH, SNL, Channel Archiver… • From V 2: Control System Studio tools - SNS “suite” for alarms, synoptics, archive - SNL editor - DCT (? ) A clear area for future collaborations Ø The ITER distribution includes a reference example, ICH Sample, that simulates the control of a RF source for Heating & Current Drive. CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 15

ICH Sample HMI CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 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 1588 -2008 is the candidate for the Time Communication Network With Core System V 2, EPICS drivers (RH) will be supplied for: – N. I. PXI-6682 : Synchronization and timing (IEEE 1588 -2008) – N. I. PXIe-6368: General purpose I/O • 16 b, 32 MS/s analog input • 16 b, 3. 33 MS/s analog output • Digital I/O and 32 b counters CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 17

Topics ITER contacts 1. Software management and software distribution 2. Configuration data (“SDD”) 3. Slow controllers (PLC) integration 4. Mini-CODAC tools / CSS 5. 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 ! CODAC Core System, 2 -June-2010, EPICS Collaboration Meeting Aix-en-Provence Page 18