codac core system

CODAC Core System, 2-June-2010, EPICS Collaboration Meeting Aix-en-Provence

CODAC Core System

F. Di Maio

ITER

IO / CHD / CIT / CODAC


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 R3.14.11. [R111] EPICS version R3.14.11 shall be used for PS fast controllers. [R112] Communication between PS fast controllers and PSH shall use EPICS Channel Access.


Plant System

Host

Fast Controller

COTSIntelligent

Device

Actuators and Sensors

CODAC System /Mini-CODAC

Fast Controller

Slow Controller

Slow Controller

Plant System I&C

Signal Interface

Remote I/O

Plant Operation Network (PON)

Plant Operation Network (PON)

Remote I/O

Signal Interface

InterlockController

Signal Interface

Central Interlock System

Central Interlock Network (CIN)

Time Communication Network (TCN)

Audio/video Network (AVN)

Synchronous Data Network (SDN)

CODAC Terminal

Plant System Instrumentation & Control (I&C) Architecture

Supplied by IO

Linux, EPICS SIMATIC S7 PLC

Mini-CODAC: stand-alone system before integration

Linux, EPICS

Complete software Development tools and standard components

Standard components for integration


Core System Releases Roadmap

2010/Q1Version 1

Preliminary

Integration of PLCs

EPICS distribution

Self-description tools (preliminary)

Examples

2011/Q1Version 2

(1st) Stable for developments

Extensions for fast controllers

Introduction of new Mini-CODAC tools APIs frozen

2012/Q1Version 3

(1st) Stable for tests

New Mini-CODAC tools (CSS)

Robustness

Core System


Area of work

1. Software management and software distribution

2. Configuration data (“SDD”)

3. Slow controllers (PLC) integration

4. Mini-CODAC tools (plant system development and tests)

5. Fast controllers support

With possible sharing of results and efforts


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.


Distribution Management

Software

Version ControlRepository Development Work

Published Version

Internet

Will be detailed by Matjaz Kobal (Cosylab) on Thursday.


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…)


SDD v1 screenshots

Plant system I&C

Component type

Property

SDD


Page 11

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


Page 12

EPICS Records generated

record (ao,"4511RT-TST-1:AOU8-JZ-CRC"){ field (DTYP,"S7plc") field (OUT,"@4511RT-PCS-1-1/0 T=UINT8") field (PINI,"YES")}record (ao,"4511RT-TST-1:AOU16-JZ-CRC"){ field (DTYP,"S7plc") field (OUT,"@4511RT-PCS-1-1/2 =UINT16") field (PINI,"YES")}

record (ai,"4511RT-TST-1:AIU8-JT-CRC"){ field (DTYP,"S7plc") field (INP,"@4511RT-PCS-1-1/0 T=UINT8") field (SCAN,"I/O Intr") field (PINI,"YES")}

record (ai,"4511RT-TST-1:AIU16-JT-CRC"){ field (DTYP,"S7plc") field (INP,"@4511RT-PCS-1-1/2 T=UINT16") field (SCAN,"I/O Intr") field (PINI,"YES")}

Process Variable

Device type – S7plc

Configuration Properties

State Properties

PLC


Page 13

DATA_BLOCK DB2TITLE= Configuration Properties of channel 1STRUCT

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_STRUCTBEGINEND_DATA_BLOCK

DATA_BLOCK DB3TITLE= State Properties of channel 1STRUCT

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 ;

END_STRUCTBEGINEND_DATA_BLOCK

Signal name

Component type + sequence number

•Import the configuration files on S7•Develop/adopt PLC software using these interface variables

PLC variables generated

PLC


Page 14

Configuration State

HMI

Alarms

Archive ViewerConnection Status

PLC sample

PLC


Page 15

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 forfuture collaborations


Page 16

ICH Sample HMI


Page 17

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.

• IEEE1588-2008 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 (IEEE1588-2008)– 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


Page 18

Topics

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 !

ITER contacts

codac core system

Documents