Status of I&C System Development for ITER Diagnostic Systems in Japan T. Yamamotoa, T. Hatae, E. Yatsuka, S. Kitazawa, R. Imazawa, Y. Hashimotoa, M. Ishikawa, H. Ogawa, T. Oikawa and K. Itami National Institutes for Quantum and Radiological Science and Technology aJapan Expert Clone The Spring 2017 EPICS Collaboration meeting KURRI, Kumatori, Japan, 17th May 2017 The views and opinions expressed herein do not necessarily reflect those of the ITER Organization.

Outline of talk Schedule and Current status I&C systems for ITER diagnostic systems Prototyping using EPICS Plans Conclusion

Schedule and Current status Five diagnostic systems and two port integration systems will be delivered from Japan to ITER. [www.fusion.qst.go.jp/english/iter-e/diagnostics.html]

Schedule and Current status (cont.) 2016 2017 2018 2019 MFC (ex VV) PoPola ETS DIM IRTh UP10 & LP2 Final Design & Prototyping PDR PDR (Nov. 2015) FDR Final Design & Prototyping PDR FDR Final Design & Prototyping Final Design & Prototyping PDR Final Design & Prototyping PDR PA conclusion ITER Organization was established on 2007. PDR: Preliminary Design Review FDR: Final Design Review PA: Procurement Arrangement

Schedule and Current status (cont.) Preliminary and final designs for the ITER diagnostic systems procured by Japan are being performed. PDRs for the five diagnostic systems are planned from 2015 to 2018. PDR for PoPola was held on November 2015. PDR for ETS was held on June 2016. PDRs for DIM, IRTh and MFC will be held in several months. Dates are under discussion.

2. I&C Systems for ITER Diagnostic systems CODAC System (central control) CODAC: COntrol, Data Access and Communication Plant system (local control)

2. I&C Systems for ITER Diagnostic systems (cont.) “Slow controller” is applied for control and data acquisition slower than 100 Hz. Consists of PLCs. “Fast controller” is applied for control and data acquisition faster than 100 Hz. Consists of industrial computers with Linux.

2. I&C Systems for ITER Diagnostic systems (cont.) Operator or Researcher Central Control System CODAC System CODAC: COntrol, Data Access and Communication We designed a supervisory system for the ITER diagnostic systems [1]. EPICS CA Diagnostic system (plant system) Plant System Host Interface point with CODAC System Configuration Parameters Validation Sequence Control Plant Automation Supervisory system for the diagnostic system [1] T. Yamamoto, et al., “Development of the supervisory systems for the ITER diagnosticsystems in JADA”, Fusion Engineering and Design 89 (2014) 532-535.

2. I&C Systems for ITER Diagnostic systems (cont.) Outline of ETS I&C architecture. State machine is operating. Port plug, Interspace Port cell, Gallery Vacuum vessel Diagnostic building YAG and Ruby laser system Occupational Safety/Local Interlock CSN Injection optics Alignment optics CIN Thermocouples/limit switch Controllers for laser and alignment optics Beam dump Driver units for actuators Plasma PON To the central I&C system Scattered light Collection optics Plant System Host/Supervisory TCN Fiber bundle Red boxes are I&C cubicles. Fast controllers are used for real-time control to align optics. Slow controllers are used for the laser sub-system (chiller or vacuum system). Polychromators cubicle #1 Polychromators cubicle #2 Data acquisition and processing DAN Fiber head units Polychromators cubicle #3 SDN Energy monitor Beam Position monitor Beam Dump monitor Beam monitor and polychromator control Polychromators cubicle #4 Asyn driver is used for fast data acquisition. CCD cameras Energy/Position/Beam dump

3. Prototyping using EPICS We developed a simple prototype for our EPICS training in 2014. We evaluated both fast and slow controller systems. Data acquisition is performed periodically using soft trigger. IOCs for both fast and slow controllers are running in the PSH. Slow controller system consists of Siemens S7 PLC. I/O module for the fast controller is National Instruments PXI system. The prototype measures temperature using thermocouples.

3. Prototyping using EPICS (cont.) This screen simulates a simplified ITER plasma operation. An example of acquired data. Thermocouples were attached to SUS plate. The plate was heated by a oven and cooled by ice. Wire-break caused by bad-contact at the terminal block was detected.

3. Prototyping using EPICS (cont.) Results of the evaluation. Fast controller 5-millisecond 10-millisecond 50-millisecond RMS (jitter) 1.134355e-05 (s) 1.239381e-05 (s) 1.176067e-05 (s) Slow controller 200-millisecond 500-millisecond 1000-millisecond RMS (jitter) 0.4837 (s) 0.7710 (s) 0.2712 (s) The jitter of the slow controller system was very large. We found the time stamping was drifted. We discussed the issue with ITER staff.

3. Prototyping using EPICS (cont.) Results of the evaluation (cont.) DAQ operation expected 200 ms 200 ms 200 ms 200 ms Actual DAQ operation 200 ms 200 ms 200 ms 200 ms : data acquisition, transfer and time stamping The data acquisition operation was different from our expectation as described in the above figure.

3. Prototyping using EPICS (cont.) Results of the evaluation (cont.) PSH IOC Time stamping here. DAQ every 200 ms SPSS Communication (Ethernet) PLC CPU DAQ every 200 ms Please note that this prototyping and evaluation were performed 3 years ago. The issue may be resolved in the latest CODAC Core System. TC module Thermocouples

4. Plans We are starting final designs and prototyping to validate our designs. We need a good practice of the I&C system design using EPICS. We would like to collaborate with the EPICS community.

5. Conclusion We are performing preliminary and final design for the ITER diagnostic systems procured by Japan. We designed I&C systems for the diagnostic systems according to the ITER standards. We developed a prototype to learn EPICS. We evaluated the prototype and found the issues. We need good practice of EPICS development and would like to collaborate with EPICS community.

Thank you very much for your attention.