Upload
anis-glenn
View
217
Download
0
Embed Size (px)
Citation preview
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 1
ITER CODACITER CODAC
COCOntrol, ntrol, DData ata AAccess and ccess and CCommunication System for ITERommunication System for ITER
Anders Wallander
ITER Organization (IO) 13067 St. Paul lez Durance, France
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 2
Basics
Plasma is an ionized hot gasThe fourth state of matter
Lawson criterion (“triple product”)Temperature * Density * Time > Big Number
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 3
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)
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 4
This is ITER
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 5
This is the ITER Agreement
140 slices
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 6
A bit of interface problems
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 7
Island mentality
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 8
Missing Items
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 9
The control system can help to fix this
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 10
The control system is horizontal
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 11
it connects to everything
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 12
it identifies and may eliminate missing items
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 13
it integrates
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 14
and is the primary tool for operation
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 15
But this will only work if…
…all these links work
StandardsArchitecture
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 16
EPICS
In February 2009 ITER Organization decided to use EPICS for the control system
This decision was based on three independent studies
In February 2010 ITER Organization released the first version of CODAC Core System, which basically is a package of selected EPICS products
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 17
Finite set of “Lego blocks”, which can be selected and connected as required
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 18
Plant System I&C
Is a deliverable by ITER member state.Set of standard components selected from catalogue.One and only one plant system host.
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 19
ITER Subsystem
is a set of related plant system I&C
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 20
CODAC Servers and Terminals
are servers running Red Hat Enterprise Linux (RHEL) and EPICS/CSS/???. These servers implements supervision, monitoring, coordination, configuration, automation, data handling, archiving, visualization, HMI…
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 21
Plant Operation Network
is the work horse general purpose flat network utilizing industrial managed switches and mainstream IT technology
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 22
Plant System Host
is an IO furnished hardware and software component installed in a Plant System I&C cubicle. There is one and only one PSH in a Plant System I&C. PSH runs RHEL (Red Hat Enterprise Linux) and EPICS (Experimental Physics and Industrial Control System) soft IOC (Input Output Controller). It provides standard functions like maintaining (monitoring and controlling) the Common Operation State (COS) of the Plant System. PSH is fully data driven, i.e. it is customized for a particular Plant System I&C by configuration. There is no plant specific code in a PSH. PSH has no I/O.
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 23
Slow Controller
is a Siemens Simatic S7 industrial automation Programmable Logic Controller (PLC). There may be zero, one or many Slow Controllers in a Plant System I&C. A Slow Controller runs software and plant specific logic programmed on STEP 7 and interfaces to either PSH or a Fast Controller using IO furnished interface (EPICS driver and self description). A Slow Controller has normally I/O and IO supports a set of standard I/O modules. A Slow Controller has no interface to HPN. A Slow Controller synchronizes its time using NTP over PON. A Slow Controller can act as supervisor for other Slow Controllers.
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 24
Fast Controller
is a dedicated industrial controller implemented in PCI family form factor and PCIe and Ethernet communication fabric. There may be zero, one or many Fast Controllers in a Plant System I&C. A Fast Controller runs RHEL and EPICS IOC. It acts as a channel access server and exposes process variables (PV) to PON. A Fast Controller has normally I/O and IO supports a set of standard I/O modules with associated EPICS drivers. A Fast Controller may have interface to High Performance Networks (HPN), i.e. SDN for plasma control and TCN for absolute time and programmed triggers and clocks. Fast Controllers involved in critical real-time runs a RT enabled (TBD) version of Linux on a separate core or CPU. A Fast Controller can have plant specific logic. A Fast Controller can act as supervisor for other Fast Controllers and/or Slow Controllers. The supervisor maintains Plant System Operating State.
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 25
High Performance Computer
are dedicated computers (multi core, GPU) running plasma control algorithms.
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 26
High Performance Networks
are physically dedicated networks to implement functions not achievable by the conventional Plant Operation Network. These functions are distributed real-time feedback control, high accuracy time synchronization and bulk video distribution.
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 27
ITER subsystem # of PS I&C # of PSH+controllers # of servers+terminals
Tokamak 6 55 6
Cryo and cooling water 5 40 3
Magnets and coil power supply 8 30 3
Building and power 37 66 3
Fuelling and vacuum 6 45 3
Heating 8 55 4
Remote handling 2 15 2
Hot cell and environment 3 20 2
Test blanket 6 24 7
Diagnostics 89 400 20
Central 0 0 170
TOTAL 167 750 220
Estimate of system size
~1000 computers connected to PON
EPICS Collaboration Meeting Spring 2010, Aix France, Jun 2, 2010Page 28
Conclusions
• The non-technical peculiarities of the ITER project has been addressed• Components making up ITER control system have been defined and a baseline architecture outlined• Flexibility in combining these standard components have been emphasized• Having a set of standard components and a sound architecture will ease integration
We would like to thank the EPICS community allowing us to get started very quickly on the ITER control system
We promise to pay back to the community in the future with the development of ITER control system and an enlargement of the community
https://www.iter.org/org/team/chd/cid/codac/Pages/