The ITER Neutral Beam (NBI) Test Facility, under construction in Padova, Italy consists in the ITER full scale ion source for the heating neutral beam injector, referred to as SPIDER, and the full size prototype injector, referred to as MITICA. The Control and Data Acquisition System (CODAS) for SPIDER has been developed and is going to be in operation in 2016. The system is composed of four main components: Supervision, Slow Control, Fast Control and Data Acquisition. These components interact with each other to carry out the system operation and, since they represent a common pattern in fusion experiments, software frameworks have been used for each (set of) component. In order to reuse as far as possible the architecture developed for SPIDER, it is important to clearly define the boundaries and the interfaces among the system components so that the implementation of any component can be replaced without affecting the overall architecture. This work reports the experience gained in the development of SPIDER components, highlighting the importance in the definition of generic interfaces among component, showing how the specific solutions have been adapted to such interfaces and suggesting possible approaches for the development of other ITER subsystems.

Integrating supervision, control and data acquisition -The ITER Neutral Beam Test Facility experience

Luchetta A;Manduchi G;Taliercio C;Capobianco R;Moressa M;Simionato P;Zampiva E
2016

Abstract

The ITER Neutral Beam (NBI) Test Facility, under construction in Padova, Italy consists in the ITER full scale ion source for the heating neutral beam injector, referred to as SPIDER, and the full size prototype injector, referred to as MITICA. The Control and Data Acquisition System (CODAS) for SPIDER has been developed and is going to be in operation in 2016. The system is composed of four main components: Supervision, Slow Control, Fast Control and Data Acquisition. These components interact with each other to carry out the system operation and, since they represent a common pattern in fusion experiments, software frameworks have been used for each (set of) component. In order to reuse as far as possible the architecture developed for SPIDER, it is important to clearly define the boundaries and the interfaces among the system components so that the implementation of any component can be replaced without affecting the overall architecture. This work reports the experience gained in the development of SPIDER components, highlighting the importance in the definition of generic interfaces among component, showing how the specific solutions have been adapted to such interfaces and suggesting possible approaches for the development of other ITER subsystems.
2016
Istituto gas ionizzati - IGI - Sede Padova
Control systems
Data acquisition
Neutral beam injector
Software frameworks
System integration
File in questo prodotto:
Non ci sono file associati a questo prodotto.

I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.

Utilizza questo identificativo per citare o creare un link a questo documento: https://hdl.handle.net/20.500.14243/323980
Citazioni
  • ???jsp.display-item.citation.pmc??? ND
  • Scopus 7
  • ???jsp.display-item.citation.isi??? ND
social impact