Requirements for ITER CODAC

EPICS Collaboration Meeting

July 29, 2009, Daejeon, Korea Page 1

Requirements for ITER CODAC

Franck Di MaioCODAC & IT

CHD Department



Outline

Introduction: PSH & Mini-CODAC R&D Tasks The EPICS Decision Plans Self-Description Architecture & tools Conclusion



ITER I&C ArchitectureIntroduction



CODAC ArchitectureIntroduction

Fast Controller

Plant System Host

PLC

Middleware

Syn

chro

no

us D

ata

Central CODAC Systems

Plasma Control

OperatorSoftware



CODAC Architecture

Plant System Host (PSH)

Is integrated in the Plant System Instrumentation & Control (I&C).

Provides a single point of entry for communication between the CODAC Systems and the plant system’s local controllers.

Is in charge of:– configuration management, – command dispatching, – state monitoring, – alarms and logs interfacing,– data flow and events

dispatching. Is supplied by ITER IO

Fast Controller

Plant System Host

PLC

Syn

chro

no

us D

ata

Central CODAC Systems

Plasma Control

OperatorSoftware

Introduction

Middleware



CODAC Architecture

Fast Controller

Plant System Host

PLC

Syn

chro

no

us D

ata

Introduction

Middleware

Before Integration

Mini-CODAC

Mini-CODAC

Implements a sub-set of the CODAC systems functions.

Provides a SCADA environment for the development

– Configuration Management– Local supervision– Human Machine Interface

(HMI)– Alarms, logs, data

handling… Is a tool for acceptance

tests at factory and on site



Outline

Introduction R&D Tasks The EPICS Decision Plans Self-Description Architecture & tools Conclusion



SCADA Survey

Market Survey + evaluation of selected products against ITER Requirements.

The open source products, EPICS & TANGO, are the ones that match the ITER requirements at best.– TANGO relies on recent technology.– EPICS benefits from a large community and a strong

support.

iFIX

Contract with ATOS Origin

R&D Tasks



Communication Technologies Survey

Evaluation of selected communication technologies against some specific user-cases.

Channel Access and CORBA have limits but replacement or complement isn’t justified now.

It is recommended to use an API that abstract the implementation.

Channel Access Limits

No built-in commands invocation OK for a model with simple commands.

Performances OK, except for large data New version or dedicated data-stream services

Scalability is limited Multi-layers architecture

10

Channel Access

CORBA DDS ICE

TAO, OmniORB RTI ZeroC

100

1.000

10.000

100.000

10 100 1.000 10.000 100.000 1.000.000

Late

ncy

[ms]

Payload size [bytes]

EPICS (sync)OmniNotifyIceStorm

Contract with Cosylab

R&D Tasks



PSH Prototype

Objectives: On site evaluation of EPICS and Tango Pre-engineering of CODAC conceptsUse cases:1. Direct control of the I/O channels of a PLC.2. Integration of another type of PLC simulating

the control of a plant system.Implemented on both EPICS and TANGO.

Contract with Alceli Hunt Beratung

R&D Tasks



Prototype Architecture

PSH 1

EPICS TANGO

Mini-CODAC 1MEDM, StriptoolPython/Java/C/C++

Siemens S7/300

PSH 2S7 DS,CPS DS, Modbus DS,Simple case DS

Mini-CODAC 2 Jdraw, atkmoniPython/Java/C/C++

Modbus / TCP

S7 IOC,CPS IOC,

Modbus IOC,

S7 / TCP

YokogawaStardom FCJ

Power Supply Simulation(complex case)

I/O interface(simple case)

Ethernet NW (PON)

Ethernet NW (PS LAN)

R&D Tasks



Prototyping Results

The 2 use cases have been implemented. Both EPICS and Tango are acceptable base for

implementing the functions and the CODAC concepts.

PSH

SlowController

R&D Tasks



The EPICS Decision

It is a necessity for ITER to standardize the Plant System’s controller software at the very beginning. Currently: 161 plant systems with FAT starting in 2012.

Feb-09: EPICS will be used as the baseline for the software environment for the ITER control system

Plant Control Design Handbook, vs. 4.1, 06-May-2009:The software infrastructure for PSH and Mini-CODAC is EPICS

version R3.14.10. [R111] EPICS version R3.14.10 shall be used for PS fast

controllers. [R112] Communication between PS fast controllers and

PSH shall use EPICS Channel Access. [R113] The Operating System of the PS fast controllers

shall be Linux (version [TBD]). Deviations may be considered by IO for difficult real-time cases.

… and PLC are Siemens Simatic S7 (same document)



Outline




Core Systems

Core functions:– Communications– “SCADA” functions:

• HMI• Alarm Handling• Error & trace logging• Parameters monitoring• Plant system supervision• Data Archiving• Testing

– Configuration management (self-description) To be implemented by packaged CODAC core systems

Built and distributed in an incremental manner. – One major release / year (1st quarter)– Starting from 2010

According to the Mini-CODAC architecture for now.

Plans



Roadmap

Vs 1 2010/Q1 Preliminary Release

Vs 2 2011/Q1 Stable release for developers

Vs 3 2012/Q1 Stable release for FAT

Priorities:1. Integrate PLCs (Siemens S7)2. Develop configuration management (self-description)3. Freeze the Application Programming Interfaces (APIs)4. Integrate fast controllers (EPICS IOC)

Plans



Resources

IO staff estimation: 4-6 ppy (2009-2012) Task Agreement with ITER-IN (3 years, from

2009/Q3) on PSH and Prototype Mini-CODAC Support contract (3 years, from 2009/Q4) for

EPICS, QA & user support. New contracts in 2010

Surveys and collaborations– EPICS Tools survey (June 2009)– Task Agreement with ITER-KO on EPICS for Tokamak

(August 2009)

Plans



Outline

Introduction R&D Tasks The EPICS Decision Plans Self-Description (Denis Stepanov) Architecture & tools Conclusion



… is a concept of providing all the necessary information about Plant Systems along with the Plant Systems themselves. The ultimate goal is to make both Plant Systems I&C and CODAC software system-neutral, decreasing the hard-coded programming part of the system specificity and increasing the data configuration part.

… has to be introduced and actively supported by the software from the very beginning to avoid being a huge set of inconsistent, unreliable, poorly maintained data.

… represents static configuration data not changing during the Plant System operation. It can be modified through dedicated maintenance procedures.

… is expressed in XML constrained by a well-defined W3C XML Schema (XSD).

… shall capture all “hidden knowledge” of Plant System configuration, at least in the form of documentation.

… forms a part of software interface between the Plant Systems I&C and Central I&C Systems.

Plant System Self-Description



The Self-Description Data consist of:Plant System I&C unique identification;Command list;Alarms list;Set-points list;Plant System I&C Operating Limits and Conditions;Physical (raw) signals list (I/O);Processed / converted signals list;Data streams list;Logging messages list;Definition of the Plant System I&C state machine in accordance with the defined Plant System operating states;Definitions of Plant System I&C HMI;Initial values for run-time configuration used for Plant System I&C start-up;Identification of source codes and binary packages of the Plant System I&C specific software;Documentation.

(as stated in the Plant Control Design Handbook v 4.1, May 2009)

Self-Description Scope



Device descriptions for EPICS and TANGO in XML

tango device_server

1 ¥..

name

instance

1 ¥..

name

class

1 ¥..

name

device

1 ¥..

name

property

0 ¥..

name

value

1 ¥..

attribute

0 ¥..

name

attribute_property

1 ¥..

name

value

class_property

0 ¥..

name

value

substitutions file

1 ¥..

name

pattern var

1 ¥..

set

1 ¥..

sub

1 ¥..

template record

1 ¥..

type

name

field

1 ¥..

name

value

TANGO

EPICS

(mapping of TANGO’s MySQL database)

(mapping of EPICS text templates and substitution lists)



PSH

PSH software

PlantSystem

SCADA frontend Feedback Loops Computers Slow Controllers (PLC)Fast Acquisition Computers

CODAC

CODAC Systems Self-description ToolkitCentral Database

· Channels· Streams· Alarms· State machine· Mimics description· Live DB· OLC· ...

Self-description dataflow: operation

PSH static configuration

1

PS parameters

2

PS dynamic parameters

3

PS devices dynamic parameters

4PS data 5

PS data 6

PS response

7



CODAC

CODAC Systems Self-description ToolkitCentral Database

PSH

PSH software

IO

DA

PlantSystem

SCADA frontend Feedback Loops Computers Slow Controllers (PLC)Fast Acquisition Computers

Mini-CODAC

</>

CODAC Systems Self-description ToolkitSelf-desc Storage

Plant System Development Environment

SCADA Programming

Embedded Devices Programming

PLC Programming

Self-description dataflow: development

PS description

1

Devel tools’ project files

2PSH static configuration

2

PS devices programs + static configuration

3

PS parameters

4

PS dynamic parameters

5

PS data

7

PS data

8

PS response

9

PS requirements and needs

12

PS development progress 12

CODAC test data

12

PS devices dynamic parameters

6

Problem report

10

PS programmer

Program development

3

PCDH deliverables11



Outline




Core Systems, Mini-CODAC Architecture

CODAC Systems: Alarm Handling (AH) Error & Trace Logging (EL) Live Database/Monitoring (LD) Data Archiving (DA) Data Retrieval (DR) Testing Tools (TT) Communication Middleware (CM) Generic Plant System Software (PS) Visualization / HMI Builder (VB) Plant System self description (SD)

AH EL

PS Control, Slow

LDDRDA

TT

Generic PS

Operator

CM

Mini-CODAC

PSH

Plant System Controller

PS Control, Fast

Se

lf D

escr

iptio

n



Pure EPICS Architecture

Select the best EPICS mature tools to cover the core functions

Benefit: – Stable– Widely used (support)

Limits: – Not fully consistent– Migration to new ITER

adapted tools. The 2010 version:

– EPICS tools– A 1st version of the

self-description system– S7 PLC integration

EDM

CA

HMI

ALH

CA

HMI HMI

Channel Access (CA)

CA GW

CA

CA

S7 IOC

S7

CA

Mini-CODAC

PSH

Con

fig F

iles

ChanArch

CA

VDCT

HMI

Log Handler

Plant SystemControllers

S7 PLC

S7

EPICS IOC

CA

Sel

f D

escr

ipti

on

DB

Configuration

Synoptics

Alarms

Data Archiver

Errors/trace Logging



The Eclipse Mini-CODAC Alternative

Use the Eclipse technology for Mini-CODAC – a consistent

environment integrating the different functions.

Join the CSS club for adopting/improving and developing new tools.

Considered for future releases (> 1).

Use Eclipse RCP for Mini-CODAC

LD DR

Channel Access (CA)

CA GW

CA

CA

S7 IOC

S7

CA

Mini-CODAC

PSH

Con

fig F

iles

ChanArch

CA

AH

Log Handler

Plant SystemControllers

S7 PLC

S7

EPICS IOC

CA

Sel

f D

escr

ipti

on

DB

HMI

RCPCA



Vs 1 Architecture (pure EPICS)

EPICS components:• VDCT • SNL and Sequencer • EDM • autoSave • ALH • Channel Archive/Retrieval • Channel Access Gateway • IocLogServer• Wireshark-CACasnooper • CAJ • CoThread • S7PLC driver

HMI

VDCT

HMI

ALH

CAC

HMI

Channel Archive Engine

HMI

Java Application

CAJCAC

HMI

CA Diagno-

stics Tools

HMI

EDM

CAC

iocLogServer

Sequencer &

SNL

CAC

TCP/IP

CAC

Config F

iles

Self D

escription

File S

torage

CAS

GATEWAY Sequencer

CAC

CAS

S7 IOC

S7 PLCCAC

AutoSave

iocLogClient

CAS

Fast Controller

AutoSave

iocLogClient

S7

S7 PLC EPICS IOC

PSH

Plant System

Mini-CODAC

PONPS LAN

Config F

iles

Channel Retrieval

CAC



Conclusion - Main Requirements

Specific constraints The ITER schedule The ITER procurement model The ITER size (~200 systems)

Main requirements: A very good EPICS Base for many years (procurement: 10+)

– Prescribed as a standard for all plant systems controllers, from R3.14.10. Plant System Host with high reliability and high performance

– The critical interface between IOCs and central systems– Key components: CA gateway, S7 driver, RIOC (Linux, ATCA?)

Implementation of the self-description concept– A “prescriptive” management system for the plan systems– With special requirements (XML, deliverable)

New tools for central services and HMI– CSS tools? To be evaluated for Vs 2 or 3

A stable API for the high-level applications– Required for the design of ITER-specific applications (ex: scheduling system).

2012: start of FAT2015: start of integration2018: first plasma2026: DT operation

DA

IO

DA

IndLab





Date post:	05-Jan-2016
Category:	Documents
Upload:	zaza
View:	45 times
Download:	2 times

Requirements for ITER CODAC

Documents