Paper | Title | Other Keywords | Page |
---|---|---|---|
MOPPC016 | IFMIF EVEDA RFQ Local Control System to Power Tests | controls, EPICS, network, software | 89 |
|
|||
In the IFMIF EVEDA project, normal conducting Radio Frequency Quadrupole (RFQ) is used to bunch and accelerate a 130 mA steady beam to 5 MeV. RFQ cavity is divided into three structures, named super-modules. Each super-module is divided into 6 modules for a total of 18 modules for the overall structure. The final three modules have to be tested at high power to test and validate the most critical RF components of RFQ cavity and, on the other hand, to test performances of the main ancillaries that will be used for IFMIF EVEDA project (vacuum manifold system, tuning system and control system). The choice of the last three modules is due to the fact that they will operate in the most demanding conditions in terms of power density (100 kW/m) and surface electric field (1.8*Ekp). The Experimental Physics and Industrial Control System (EPICS) environment [1] provides the framework for monitoring any equipment connected to it. This paper report the usage of this framework to the RFQ power tests at Legnaro National Laboratories [2][3].
[1] http://www.aps.anl.gov/epics/ [2] http://www.lnl.infn.it/ [3] http://www.lnl.infn.it/~epics/joomla/ |
|||
TUPPC102 | User Interfaces for the Spiral2 Machine Protection System | beam-losses, controls, PLC, software | 818 |
|
|||
Spiral2 accelerator is designed to accelerate protons, deuterons, ions with a power from hundreds of Watts to 200kW. Therefore, it is important to monitor and anticipate beam losses to maintain equipment integrities by triggering beam cuts when beam losses or equipment malfunctions are detected; the MPS (Machine Protection System) is in charge of this function. The MPS has also to monitor and limit activations but this part is not addressed here. Linked to the MPS, five human machine interfaces will be provided. The first, “MPS” lets operators and accelerator engineers monitor MPS states, alarms and tune some beam losses thresholds. The second “beam power rise” defines successive steps to reach the desired beam power. Then, “interlock” is a synoptic to control beam stops state and defaults; the “beam losses” one displays beam losses, currents and efficiencies along the accelerator. Finally, “beam structure” lets users interact with the timing system by controlling the temporal structure to obtain a specific duty cycle according to the beam power constraints. In this paper, we introduce these human machine interfaces, their interactions and the method used for software development. | |||
![]() |
Poster TUPPC102 [1.142 MB] | ||