DTT ICS Kickoff Meeting Frascati 6 February 2019

DTT ICS Kickoff Meeting Frascati 6 February 2019 I&C for Additional Heating Filippo Sartori

Objective of session • Understand the I&C support needs of DTT Additional Heating • Schedule and man a support activity • Make sure that the additional heating requirements are taken in account by DTT CODAS 2/6/2019 2

What I expect Additional heating systems area composed of: 1. Turn-key industrial sub-systems with important I&C (power supplies, cryogenics, RF generator plant, …) 2. I&C Integration for some industrial components (RF dummy loads, vacuum pumping, …) 3. Overall I&C integration of the plant. 1 requires I&C engineer support from beginning, 2 and 3 requires a team effort 1 -2 years before commissioning. 2/6/2019 3

ECH Ø Only ECH for now. Ø Use of ITER Gyrotrons but shorter pulse length. Ø Synchronous modulation needed? Potential synergies with ITER: • Falcon today • GCC @ITER 2020

DTT ICS Kickoff Meeting Frascati 6 February 2019 DTT I&C architecture Gabriele Manduchi & Filippo Sartori

DTT CODAS scope Full responsibility: • DTT Central I&C (DICS) • DTT Operation Networks • DTT Operation Databases Responsible of the integration to Central Systems: • DTT Industrial Plant Systems Responsible of the frontend (controllers and standard IO): • Diagnostics and custom components of Additional Heating Systems

2. DTT CODAS scope Remote Participation Data Collection Distribution Visualisation Experiment Databases Central Control & SCADA Central Interlock Central Safety Machine Prot IF Safety IF RT Networks Data Storage Interface Control System(? ) RT IF Standard IO (? ) Custom Electronics (Diagnostics…) 1/29/2019 SCADA IF Plant System DTT-CODAC meeting in Padua 5 Sept. 2018 Industrial SCADA (turnkey systems)

DTT Central I&C • Central Command & Control – SCADA (direct handling of plant) CCCS • Alarm Handling • High level control of industrial systems • Full control of Diagnostics, Additional Heating. . – Experiment Management • Pulse configuration management(help prepare discharge) – Compare, Save, Verify, Calculate…. • Supervisor (Load experiment, sequence systems…) • Non real-time plant system functions. – Central Real Time Control CRTCS • Central Machine Protection CMPS • Central Occupational Safety System COSS – SCADA

CCCS-1 • SCADA (direct handling of plant) – WINCCOA ? – EPICS? But not Control System Studio, V 7? • Experiment Management – Plant configuration management • • • Completes/complements SCADA Manage configuration of plants: compares, integrates Verifies parameters correctness. Simulates effects ITER SUP? – Non real-time plant system functions • Implements some Plant System non-real-time operation functions

CCCS-2 • Experiment Management – Supervisor (Load experiment, sequence systems…) • Use the SCADA to do it • (Central) Real Time Control (C)RTCS – Real Time Control Systems Handled as plant systems from SCADA and configuration point of view – Traffic monitor on RTON • Verify stationarity, periodicity • Independent collection of all data and time – Database of topics and RT users • Provides configuration information

CMPS • Central Machine Protection System – Two levels: • Central protection • Sub-System protection – interfaces to plant Protection Systems – Interfaces to plant sensors ! Minimize involvement of Central Protection – Two technologies/approaches • Conventional protection: WINCCOA + PLCs + Profisafe • Plasma protection: RTCS technology (Fast Controller) +UDP multicast

COSS • Central Occupation Safety System – Two levels: • Central protection – Mainly monitoring • Sub-System protection – interfaces to plant Safety Systems – Interfaces to plant sensors ! Minimize involvement of Central Safety – PLCS, WINCCOA, Profisafe

DTT Operation Networks Central Control Operation Network CCON Real Time O. N. RTON Time And Event O. N TEON Data Acquisition O. N. DAON Machine Protection O. N. (two networks? ) MPON Occupational Safety O. N. OSON – Phys: Ethernet 1 G, 10 G, … – Traffic: Random behaviour, SCADA communication, Parameters, Alarms, … – Phys: Ethernet 1 G, 10 G, … Fixed Routes – Traffic: UDP multicast. Periodic, Stationary – Phys: ? ? Custom or White. Rabbit? – Traffic: Main Clock, Events, – Phys: Ethernet 1 G, 10 G… – Traffic: TCP large frames. Continuous, Stationary – Phys: Ethernet, Profinet – Traffic 1: Random, Configuration of Machine Protection Systems, – Traffic 2: Periodic, Stationary, Protection Events – Phys Ethernet, Profisafe – Traffic: Periodic, Stationary, Protection Events

Hardware Technologies-0 Procurement strategy: • Tender for selection for 2 PLC technologies • Tender for selection of SCADA technology • Plant System tenders favor offers that propose use of chosen technologies. (TBD %)

Hardware Technologies-1 Controllers: • 2 brands of PLCs (virtual PLC) • Industrial PCs or (better) rack mounted servers • Embedded IOT technology? ? (Cheap) !Minimize deployment of controller to plant. !NO embedded configuration in plant !Maximize use of Virtual computing !Maximize use of Remote IO

Hardware Technologies-2 Low frequency IO: • PLC IO is relatively cheap and easy to deploy. • Maximizing use of Remote IO allow centralization of processing nodes • Explore use of PLC remote IO with “Fast Controllers” IOT as alternative cheap IO where it does not matter…

Hardware Technologies-3 Time Distribution: • PTP simple solution for aligning clocks in “fast controllers” Event and Clock distribution: • White Rabbit? (expensive) • Dedicated Clock and Event Distribution would be more adequate to tokamak topology Better to consider together with high performance acquisition as data time stamping is the real challenge

Hardware Technologies-4 High performance IO • ITER solution not good enough. Expensive, proprietary and aimed at a different market. • Alternatives? ATCA, Compact PCI… still expensive and not addressing all needs • What about distributed remote IO developed within community? – CCFE approach of networked black box is promising. Low cost and rapid. – The key is integrated timestamping using PTP, clock production using PLL, and low latency data distribution over Ethernet. – ITER magnetic diagnostic is using this approach. We should organize a work group involving community to take a decision.

Software Technologies-1 SCADA • WINCCOA (applicable to all tears) • Web based solution (a lot of work) • NO: Control System Studio Middleware (communication central to plant) • OPC-UA (fast growing in Industry) • RESTful (de facto standard in web) • For OSS and MPS proprietary: for instance profinet/profisafe

Software Technologies-2 Signal database: Trends + Experiment data • MDS+ Experiment Configuration database: Plant configuration and Experiment configuration • MDS+ Remote participation: • RDA: MDS+ • RCA: No. Machine

Software Technologies-3 Custom Applications (in house development) • UNICOS or ITER ICL • C++ MARTe • Matlab or Python frameworks? Quality (to be established from day 1) • Continuous integration system: Jenkins • GIT • Code coverage • ….

DTT ICS Kickoff Meeting Frascati 6 February 2019 DTT CODAS Prototype proposal Filippo Sartori

Objectives of prototype-1 • Integration of MDS+, MARTe and WINCCOA • Compare with integration EPICS, MDS+, MARTe that has been deployed recently

Objectives of prototype-2 • MDS+ to handle all parameters, current and historical – Ability to load/save to WINCCOA • MDS+ to store all data, pulse and trends – Collect trends from WINCCOA • Data visualization on MDS+ and on WINCCOA – WINCCOA to access fast signals in MDS+ • High speed data collected by MDS+ • WINCCOA to act as SCADA for MARTe – MARTe WINCCOA using OPC-UA for states – MARTe MDS+ for fast acquisition etc. . • WINCCOA to coordinate pulse sequence

Proposal-1 • Implement Gyrotron Plant Control System • Redo FALCON Test Facility using WINCCOA instead of EPICS Work required: • Redo OPIs in WINCCOA • Redo PLC and MARTe interface to SCADA • Implement WINCCOA to MDS+ connection for data storage • Implement MDS+ interface to WINCCOA for read/write of parameters • Automatize MDS+ WINCCOA configuration. Ø Simulate and test individual components Ø OPTION: deploy to real FALCON