ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 1 ITER Update F. Di Maio ITER IO / CHD / CIT / CODAC

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 2 Outline ITER CODAC overview Configuration data management ITER S7 communications PXI Drivers

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 3 Basics Plasma is an ionized hot gas The fourth state of matter Lawson criterion (“triple product”) Temperature * Density * Time > Big Number

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 4 ITER Goal: Demonstrate feasibility of fusion as an energy source Metric: Q=10 sustained for seconds (Q=10 means output power equal 10 times input power) Schedule: 10 years construction phase just started First plasma 2019, first D-T plasma 2027 Collaboration: CN, EU, IN, JA, KO, RF, US Method: Magnetic confinement (Tokamak)

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 5 ITER Status The new schedule and budget has been approved –First Plasma: Nov 2019, DT operation: –Start of on-site delivery and integration: end The responsibility for the Plant System’s Instrumentation and Control is still very distributed –The ITER plant systems are mostly procured in-kind by one or many of the DAs. –Including Plant System Instrument and Control (I&C) Introduction

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 6 ITER CODAC (Control, Data Access and Communication) Plant Systems Instrumentation & Control (I&C) support –Design –Development –Integration –Operation & maintenance CODAC Core system –Core services: communications, alarms, archives, … time & synchronization, synchronous data exchange –Software infrastructure for the plant systems I&C. Design Development and test Integration Operation and maintenance CODAC Applications (R&D) –Supervision –Plasma Control –Scheduling System Introduction

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 7 Plant System Instrumentation & Control (I&C) Architecture Supplied by IO Linux, EPICSSIMATIC S7 PLC Mini-CODAC: stand-alone system before integration Linux, EPICS Introduction Linux, EPICS, Eclipse/Java/CSS CODAC: Control, Data Access and Communication

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 8 CODAC Core System The software provided by ITER Organization (IO) for the plant system I&C developers supporting all ITER standards –Linux distribution (RHEL) –EPICS: base and selected tools (with some customization) –ITER components One major release every year from 2010 –Feb 2010: 1.0 –Feb 2011: 2.0 –… Support organization for ITER users Public distribution issued at the same time as the ITER one. Introduction

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 9 Software Management and Distribution RHEL (64 bits) is the selected Linux distribution for ITER 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. Maven is used to build/run/deploy/package. –mvn commands encapsulates make. Introduction

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 10 Distribution Management Version Control Repository Development Work Published Version Internet Introduction

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 11 Configuration data management (SDD) We are developing a suite of tools for –Defining variables, signals, controllers… –Generating EPICS configuration data (IOC, Alarms, Archive, some HMI), as well as PLC data (variables and communication). The data is stored into a RDB (Postgresql). The data model is implemented in Java, using Hibernate with JPA (Java Persistency API) annotations and Spring for transactions The editor is developed under the Eclipse platform. Web applications are also be developed with Spring. We call that SDD (self description data). It uses the ITER semantic and work flows but the concepts are rather simple.  Contact: Lana Abadie (ITER) Data Management

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 12 SDD use cases 1.Declare each signals or import a signal list (optional) 2.Declare all the functions implemented 3.For each function, declare the variables and commands 4.Declare all controllers: “fast controllers” and PLCs. 5.Deploy the variables and commands to controllers (or to the “Plant System Host”). 6.Enter the full definition of each variable, including any required EPICS field. 7.Validate the new data and commit to the DB. Declare the I/O module into the controller on which the variable is deployed. Connect the signal to the I/O module, specifying the channel number, the signal type, etc. Associate the signal with the variable Deploy the variable to a PLC at step 5 Fill the PLC data (IP name…) Edit a plant system I&C Interface a variable with a signal Map a PLC variable to a PV Data Management

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 13 Data Management SDD Editor (in development)

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 14 Open Issues  How can a data-base centric approach (“top down”) co-exist with a db files editor like VDCT ?  Shall VDCT be more Eclipse/CSS compliant? Options A.Forget about VDCT. Make the new editor the only EPICS db editor. B.Eclipsify/CSSify VDCT 1.Plug-in 2.Eclipse view 3.SWT C.Connect VDCT with the configuration data-base. D.Generate/parse db files from/to the data-base. … ideas? Data Management

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 15 CSS components ITER The main ones: BEAST BOY DataBrowser SNL Editor BEAUTY

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 16 CSS handling at ITER We are packaging the CSS components into the CODAC Core System distribution –Built from the latest source in Mercurial –Adding Postgres (driver 8.2) to Oracle and MySQL –Fixing minor problems We’ll push back extensions and fixes –To stay in sync with changes. –To avoid common packages in ITER branches / copies. Contacts: Lana Abadie (ITER), Anze Zagar (Cosylab) CSS

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 17 CSS extensions ITER extensions 1.IOC development integration (creation/add of an EPICS Application/IOC, build and run). 2.Integration of ITER Data management (SDD) query into the PV Field query plug-in. Xmas list If it appears for Christmas, we’ll be very happy, otherwise, we’ll make sure we’ll have it before next Christmas. –Transmit IOC Error Log messages to JMS and store them in Message RDB. –Activation of BOY screens from BEAST. Contact: Nadine Utzel (ITER) CSS

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 18 Our OPI(s) have been all successfully migrated from EDM to BOY! …actually, only one demo HMI was in our distribution.

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 19 PLC Integration - Update 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. Some extensions added for error detection (header, length, version) but depends on ITER data management. Contact: Kirti Mahajan (ITER) Dropped, because of performances issues

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 20 National Instruments PXI Device Drivers 2 boards –NI PXI-6682 : Synchronization and timing (IEEE ) –NI PXI-6259: M-series Multi-function DAQ 16b, 1.25 MS/s analog inputs 16b, 2.8 MS/s analog outputs Digital I/O and 32b counters For each, we are developing: –A Linux Device Driver –A C-interface library + EPICS Device Support Next? –X-series PXIe-6386 (32 MS/s total on 16 channels) under study –We plan to support NI FlexRIO FPGAs: Development chain under LabView Linux interfacing currently only available with NI provided 32-bit library but no device driver Contact: Petri Makijarvi (ITER)

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 21

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 22 Core System 2.0 Releases Sep-10 Oct-10Nov-10Dec-10Jan-11Feb-11Mar-11Apr-11 May b42.0b32.0b22.0b12.0a32.0.1? 2.1? 2.0 Features freeze30-Sep-2010 Beta 105-Oct-2010 Beta 205-Nov-2010 Beta 307-Dec Code freeze22-Dec-2010 Beta 410-Jan Feb (bug fixes)? 2.1 (added features)? + Daily version (night build) to test bug fixes & new features from latest source

ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 23 Core System 2.0 New Features System RHEL b RDBD: PostgreSQL User Management Self-Description New Data modelData-base / Java API (JPA), Signals, FBS, I/O, PLC com, Mini-CODAC data New SDD editor and translatorEclipse platform, PLC data, IOC data, Mini-CODAC data, fast controllers Web Applications Plant system I&C browsing, PLC data generation Mini-CODAC Eclipse / Control System Studio Integrated platform, Java. New Alarm System BEAST: many new features. Hew HMI BOY: new GUI, scripts New Eclipse/CSS tools CSS tools: SNL editor + …, EPICS plug-in Python support CA interface, Eclipse PSH and controllers New PSH-PLC communications New data layout, transmission errors detection, simple commands support IOC and System MonitoringFast Controllers/PSH : system and IOC tasks monitoring I/O BoardsPXI NI Multi-IO board and Timing modules: driver + EPICS support. Standard interface COS support + ? Examples ICH sample New version (CSS +…) PLC sample Test program - New version (new com, SDD Mini-CODAC…) IOC sample New : Test Program with I/O boards