iter update
Post on 08-Jan-2016
82 Views
Preview:
DESCRIPTION
TRANSCRIPT
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• CSS @ ITER• S7 communications• PXI Drivers
ITER Update, 11-Oct-2010, EPICS Collaboration Meeting Brookhaven Page 3
Basics
Plasma is an ionized hot gasThe 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 sourceMetric: Q=10 sustained for 300-500 seconds(Q=10 means output power equal 10 times input power)
Schedule: 10 years construction phase just startedFirst 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: 2027.– Start of on-site delivery and integration: end 2015.
• 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 7
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
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 (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.
• Maven is used to build/run/deploy/package. – mvn commands encapsulates make.
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&CInterface 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 ManagementSDD 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?
OptionsA. Forget about VDCT. Make the new editor the only EPICS db
editor.B. Eclipsify/CSSify VDCT
1. Plug-in2. Eclipse view3. 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 used @ ITER
The main ones: BEAST BOY DataBrowser SNL Editor BEAUTY
Group
ITER
Welcome Intro Generic 'Welcome' Generic CSS Introduction, Channel Access setup info
I TER – specific ‘Welcome
Setting No Specific Settings Channel Access, Archive etc. not configured
Settings for I TER Postgres DB, BOY colors, archived data…
Login / Authorization LDAP Authentication and Authorization Login support for alarm GUI and SDS
Basic Eclipse Tools SVN Support Access to SVN repository from within CSS.
Data / Archive Access LiveDataSupport Access to control system data
Display Tools Best OPI Yet Operator Panel Editor Prototype
Alarm Tools Alarm Table
Alarm Tree
Archive Table
BEAST GUI User Interface of the Best Ever Alarm System Toolkit
Diagnostic Tools Probe Inspect live PVs
EPICS PV Tree Display a PV's input link hierarchy
System Monitor Memory usage info
caSnooper
Configuration DCT DESY Database Creation Tool
Utilities Post Analyzer Basic fitting and correlation of Data Browser data
Therapist How do you feel about that?
PACE Table editor for 'critical' PVs
RDB Table Editor Generic editor for RDB data
Clock Time to go home, yet?
MessageLogViewer Viewer for the CSS Message log (in RDB, from J MS)
SNL Editor EPICS Sequencer IDE
Trends DataBrowser 'Stripchart' live and archived data
ArchiveSupport Access to historic data
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 extensions1. 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 listIf 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-1588-2008)– 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
top related