Author: Taliercio, C.
Paper Title Page
WEPKS011 Use of ITER CODAC Core System in SPIDER Ion Source 801
 
  • C. Taliercio, A. Barbalace, M. Breda, R. Capobianco, A. Luchetta, G. Manduchi, F. Molon, M. Moressa, P. Simionato
    Consorzio RFX, Associazione Euratom-ENEA sulla Fusione, Padova, Italy
  
  In Febru­ary 2011 ITER re­leased a new ver­sion (v2) of the CODAC Core Sys­tem. In ad­di­tion to the se­lect­ed EPICS core, the new pack­age in­cludes also sev­er­al tools from Con­trol Sys­tem Stu­dio [1]. These tools are all in­te­grat­ed in Eclipse and offer an in­te­grat­ed en­vi­ron­ment for de­vel­op­ment and op­er­a­tion. The SPI­DER Ion Source ex­per­i­ment is the first ex­per­i­ment planned in the ITER Neu­tral Beam Test Fa­cil­i­ty under con­struc­tion at Con­sorzio RFX, Pado­va, Italy. As the final prod­uct of the Test Fa­cil­i­ty is the ITER Neu­tral Beam In­jec­tor, we de­cid­ed to ad­here since the be­gin­ning to the ITER CODAC guide­lines. There­fore the EPICS sys­tem pro­vid­ed in the CODAC Core Sys­tem will be used in SPI­DER for plant con­trol and su­per­vi­sion and, to some ex­tent, for data ac­qui­si­tion. In this paper we re­port our ex­pe­ri­ence in the usage of CODAC Core Sys­tem v2 in the im­ple­men­ta­tion of the con­trol sys­tem of SPI­DER and, in par­tic­u­lar, we an­a­lyze the ben­e­fits and draw­backs of the Self De­scrip­tion Data (SDD) tools which, based on a XML de­scrip­tion of the sig­nals in­volved in the sys­tem, pro­vide the au­to­mat­ic gen­er­a­tion of the con­fig­u­ra­tion files for the EPICS tools and PLC data ex­change.
[1] Control System Studio home page: http://css.desy.de/content/index_eng.html
 		 
 
WEPMN036 Comparative Analysis of EPICS IOC and MARTe for the Development of a Hard Real-Time Control Application 961
 
  • A. Barbalace, A. Luchetta, G. Manduchi, C. Taliercio
    Consorzio RFX, Associazione Euratom-ENEA sulla Fusione, Padova, Italy
  • B. Carvalho, D.F. Valcárcel
    IPFN, Lisbon, Portugal
  
  EPICS is used world­wide to build dis­tribut­ed con­trol sys­tems for sci­en­tif­ic ex­per­i­ments. The EPICS soft­ware suite is based around the Chan­nel Ac­cess (CA) net­work pro­to­col that al­lows the com­mu­ni­ca­tion of dif­fer­ent EPICS clients and servers in a dis­tribut­ed ar­chi­tec­ture. Servers are called Input/Out­put Con­trollers (IOCs) and per­form re­al-world I/O or local con­trol tasks. EPICS IOCs were orig­i­nal­ly de­signed for Vx­Works to meet the de­mand­ing re­al-time re­quire­ments of con­trol al­go­rithms and have late­ly been port­ed to dif­fer­ent op­er­at­ing sys­tems. The MARTe frame­work has re­cent­ly been adopt­ed to de­vel­op an in­creas­ing num­ber of hard re­al-time sys­tems in dif­fer­ent fu­sion ex­per­i­ments. MARTe is a soft­ware li­brary that al­lows the rapid and mod­u­lar de­vel­op­ment of stand-alone hard re­al-time con­trol ap­pli­ca­tions on dif­fer­ent op­er­at­ing sys­tems. MARTe has been cre­at­ed to be portable and dur­ing the last years it has evolved to fol­low the mul­ti­core evo­lu­tion. In this paper we re­view sev­er­al im­ple­men­ta­tion dif­fer­ences be­tween EPICS IOC and MARTe. We dis­sect their in­ter­nal data struc­tures and syn­chro­niza­tion mech­a­nisms to un­der­stand what hap­pens be­hind the scenes. Dif­fer­ences in the com­po­nent based ap­proach and in the con­cur­rent model of com­pu­ta­tion in EPICS IOC and MARTe are ex­plained. Such dif­fer­ences lead to dis­tinct time mod­els in the com­pu­ta­tion­al blocks and dis­tinct re­al-time ca­pa­bil­i­ties of the two frame­works that a de­vel­op­er must be aware of.  
poster icon Poster WEPMN036 [2.406 MB]