Paper |
Title |
Page |
MOCOAAB03 |
The Spiral2 Control System Progress Towards the Commission Phase |
8 |
|
- E. Lécorché, P. Gillette, C.H. Haquin, E. Lemaître, G. Normand, C.H. Patard, L. Philippe, D.T. Touchard
GANIL, Caen, France
- J.F. Denis, F. Gougnaud, J.-F. Gournay, Y. Lussignol
CEA/DSM/IRFU, France
- P.G. Graehling, J.H. Hosselet, C. Maazouzi
IPHC, Strasbourg Cedex 2, France
|
|
|
The commissioning of the Spiral2 Radioactive Ion Beams facility at Ganil will soon start, so requiring the control system components to be delivered in time. Yet, parts of the system were validated during preliminary tests performed with ions and deuterons beams at low energy. The control system development results from the collaboration between Ganil, CEA/IRFU, CNRS/IPHC laboratories, using appropriate tools and approach. Based on Epics, the control system follows a classical architecture. At the lowest level, Modbus/TCP protocol is considered as a field bus. Then, equipment are handled by IOCs (soft or VME/VxWorks) with a software standardized interface between IOCs and clients applications on top. This last upper layer consists of Epics standard tools, CSS/BOY user interfaces within the so-called CSSop Spiral2 context suited for operation and, for machine tunings, high level applications implemented by Java programs developed within a Spiral2 framework derived from the open-Xal one. Databases are used for equipment data and alarms archiving, to configure equipment and to manage the machine lattice and beam settings. A global overview of the system is therefore here proposed.
|
|
|
Slides MOCOAAB03 [3.205 MB]
|
|
|
TUCOBAB01 |
A Small but Efficient Collaboration for the Spiral2 Control System Development |
498 |
|
- E. Lécorché, C. Berthe, F. Bucaille, P. Gillette, C.H. Haquin, E. Lemaître, J.M. Loyant, G. Normand, C.H. Patard, L. Philippe, R.J.F. Roze, D.T. Touchard, A.H. Trudel
GANIL, Caen, France
- J.F. Denis, F. Gougnaud, J.-F. Gournay, Y. Lussignol, A. Roger, R. Touzery
CEA/DSM/IRFU, France
- P.G. Graehling, J.H. Hosselet, C. Maazouzi
IPHC, Strasbourg Cedex 2, France
|
|
|
The Spiral2 radioactive ion beam facility to be commissioned in 2014 at Ganil (Caen) is built within international collaborations. This also concerns the control system development shared by three laboratories: Ganil has to coordinate the control and automated systems work packages, CEA/IRFU is in charge of the “injector” (sources and low energy beam lines) and the LLRF, CNRS/IPHC provides the emittancemeters and a beam diagnostics platform. Besides the technology Epics based, this collaboration, although being handled with a few people, nevertheless requires an appropriate and tight organization to reach the objectives given by the project. This contribution describes how, started in 2006, the collaboration for controls has been managed both from the technological point of view and the organizational one, taking into account not only the previous experience, technical background or skill of each partner, but also their existing working practices and “cultural” approaches. A first feedback comes from successful beam tests carried out at Saclay and Grenoble; a next challenge is the migration to operation, Ganil having to run Spiral2 as the other members are moving to new projects
|
|
|
Slides TUCOBAB01 [2.747 MB]
|
|
|
TUPPC102 |
User Interfaces for the Spiral2 Machine Protection System |
818 |
|
- L. Philippe, P. Gillette, G. Normand
GANIL, Caen, France
|
|
|
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]
|
|
|