Author: Komiyama, M.
Paper Title Page
TUPDP050 Development and Test Operation of the Prototype of the New Beam Interlock System for Machine Protection of the RIKEN RI Beam Factory 645
 
  • M. Komiyama, M. Fujimaki, N. Fukunishi, A. Uchiyama
    RIKEN Nishina Center, Wako, Japan
  • M. Hamanaka, K. Kaneko, R. Koyama, M. Nishimura, H. Yamauchi
    SHI Accelerator Service Ltd., Tokyo, Japan
  • A. Kamoshida
    National Instruments Japan Corporation, MInato-ku, Tokyo, Japan
 
  We have been operating the beam interlock system (BIS) for machine protection of the RIKEN RI Beam Factory (RIBF) since 2006. It stops beams approximately 15 ms after receiving an alert signal from the accelerator and beam line components. We continue to operate BIS successfully; however, we are currently developing a successor system to stop a beam within 1 ms considering that the beam intensity of RIBF will continue to increase in the future. After comparing multiple systems, CompactRIO, a product by National Instruments, was selected for the successor system. Interlock logic for signal input/output is implemented on the field-programmable gate array (FPGA) because fast processing speed is required. On the other hand, signal condition setting and monitoring do not require the same speed as interlock logic. They are implemented on the RT-OS and controlled by using experimental physics and industrial control system (EPICS) by setting up an EPICS server on the RT-OS. As a first step in development, a prototype consisting of two stations that handle only digital alert signals was developed and installed in part of the RIBF in the summer of 2022 (224 input contacts). The signal response time of the prototype, measured with an oscilloscope, averaged 0.52 ms with both stations (the distance between two stations is approximately 75 m). Furthermore, by additionally installing a pull-up circuit at each signal input contact of the system, the system response time was successfully reduced to approximately 0.13 ms.  
poster icon Poster TUPDP050 [0.816 MB]  
DOI • reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-TUPDP050  
About • Received ※ 03 October 2023 — Revised ※ 09 October 2023 — Accepted ※ 14 December 2023 — Issued ※ 18 December 2023
Cite • reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)  
 
THPDP032 Introduction of the Ethernet-Based Field Networks to Inter-Device Communication for RIBF Control System 1384
 
  • A. Uchiyama, N. Fukunishi, M. Komiyama
    RIKEN Nishina Center, Wako, Japan
 
  Internet Protocol (IP) networks are widely used to remotely control measurement instruments and controllers. In addition to proprietary protocols, common commands such as the standard commands for programmable instruments (SCPI) are used by manufacturers of measuring instruments. Many IP-network-based devices have been used in RIBF control systems constructed using the experimental physics and industrial control system (EPICS); these are commercial devices designed and developed independently. EPICS input/output controllers (IOCs) usually establish socket communications to send commands to IP-network-based devices. However, in the RIBF control system, reconnection between the EPICS IOC and the device is often not established after the loss of socket communication due to an unexpected power failure of the device or network switch. In this case, it is often difficult to determine whether the socket connection to the EPICS IOC is broken even after checking the communication by pinging. Using Ethernet as the field network in the physical layer between the device and EPICS IOC can solve these problems. Therefore, we are considering the introduction of field networks such as EtherCAT and Ethernet/IP, which use Ethernet in the physical layer. In the implementation of the prototype system, EPICS IOCs and devices are connected via EtherCAT and Soft PLCs are run on the machine running EPICS IOCs for sequence control.  
DOI • reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-THPDP032  
About • Received ※ 06 October 2023 — Revised ※ 11 October 2023 — Accepted ※ 11 December 2023 — Issued ※ 15 December 2023
Cite • reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)