RT2010, Lisboa Portugal, May 28, 2009 Page 1 Baseline architecture of ITER control system Anders...
-
date post
21-Dec-2015 -
Category
Documents
-
view
213 -
download
0
Transcript of RT2010, Lisboa Portugal, May 28, 2009 Page 1 Baseline architecture of ITER control system Anders...
RT2010, Lisboa Portugal, May 28, 2009Page 1
Baseline architecture of Baseline architecture of ITER control systemITER control system
Anders Wallander, Franck Di Maio, Jean-Yves Journeaux, Wolf-Dieter Klotz, Petri Makijarvi, Izuru Yonekawa
ITER Organization (IO) 13067 St. Paul lez Durance, France
RT2010, Lisboa Portugal, May 28, 2009Page 2
Basics
Goal: Demonstrate feasibility of fusion as an energy source (Q=10 means output power equal 10 times input power)
Schedule: 10 years construction phaseFirst plasma 2019, first D-T plasma 2027
Collaboration: CN, EU, IN, JA, KO, RF, US
RT2010, Lisboa Portugal, May 28, 2009Page 3
This is ITER
RT2010, Lisboa Portugal, May 28, 2009Page 4
This is the ITER Agreement
140 slices
RT2010, Lisboa Portugal, May 28, 2009Page 5
A bit of interface problems
RT2010, Lisboa Portugal, May 28, 2009Page 6
Island mentality
RT2010, Lisboa Portugal, May 28, 2009Page 7
Missing Items
RT2010, Lisboa Portugal, May 28, 2009Page 8
The control system can help to fix this
RT2010, Lisboa Portugal, May 28, 2009Page 9
The control system is horizontal
RT2010, Lisboa Portugal, May 28, 2009Page 10
it connects to everything
RT2010, Lisboa Portugal, May 28, 2009Page 11
it identifies and may eliminate missing items
RT2010, Lisboa Portugal, May 28, 2009Page 12
it integrates
RT2010, Lisboa Portugal, May 28, 2009Page 13
and is the primary tool for operation
RT2010, Lisboa Portugal, May 28, 2009Page 14
But this will only work if…
…all these links work
StandardsArchitecture
RT2010, Lisboa Portugal, May 28, 2009Page 15
Finite set of “Lego blocks”, which can be selected and connected as required
RT2010, Lisboa Portugal, May 28, 2009Page 16
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.
RT2010, Lisboa Portugal, May 28, 2009Page 17
ITER Subsystem
is a set of related plant system I&C
RT2010, Lisboa Portugal, May 28, 2009Page 18
Plant Operation Network
is the work horse general purpose flat network utilizing industrial managed switches and mainstream IT technology
RT2010, Lisboa Portugal, May 28, 2009Page 19
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.
RT2010, Lisboa Portugal, May 28, 2009Page 20
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.
RT2010, Lisboa Portugal, May 28, 2009Page 21
High Performance Computer
are dedicated computers (multi core, GPU) running plasma control algorithms.
RT2010, Lisboa Portugal, May 28, 2009Page 22
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.
RT2010, Lisboa Portugal, May 28, 2009Page 23
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
RT2010, Lisboa Portugal, May 28, 2009Page 24
Timing System
• It is common practice by large experimental facilities to invent their own home made timing system and we want to avoid that• We believe that IEEE 1588-2008 (PTP v2) provides a COTS alternative fulfilling ITER requirements• IEEE 1588, 2008, provides 50 ns RMS synchronization accuracy of absolute time over Ethernet with possibility to program triggers and clocks synchronized with this absolute time using COTS• This standard is being endorsed by more and more suppliers and we will see many new COTS products in the future• This also provides an evolution path to White Rabbit being developed by CERN
• Therefore we have baselined IEEE 1588-2008 for TCN and will confirm this decision by further evaluations in 2nd half of 2010
Main requirements: 50 ns RMS absolute time synchronization (off-line correlation of diagnostics)
RT2010, Lisboa Portugal, May 28, 2009Page 25
Distributed real-time plasma control
• ITER distributed plasma control main characteristics• decoupling and separation of concern• data driven• multiple in multiple out (MIMO)• non intrusive probing• flexibility• scalability• simulation support• minimize latency and jitter
• Two schools of thoughts for real-time network• Reflective memory• Ethernet based (e.g. UDP, RTnet)
• Decision on technology delayed while watching the market• Further test beds and evaluations in 2011
Main requirements: control cycles Hz-kHz, peak bandwidth 25 MB/s, number of nodes participating 50-100
RT2010, Lisboa Portugal, May 28, 2009Page 26
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• Issues on timing and feedback control have been touched
We intend to continue working with our partners all over the world to make the ITER control system contribute to ITER success.
https://www.iter.org/org/team/chd/cid/codac/Pages/