Author: Di Maio, F.
Paper Title Page
MOBAUST01 News from ITER Controls - A Status Report 1
 
  • A. Wallander, L. Abadie, F. Di Maio, B. Evrard, J-M. Fourneron, H.K. Gulati, C. Hansalia, J.Y. Journeaux, C.S. Kim, W.-D. Klotz, K. Mahajan, P. Makijarvi, Y. Matsumoto, S. Pande, S. Simrock, D. Stepanov, N. Utzel, A. Vergara-Fernandez, A. Winter, I. Yonekawa
    ITER Organization, St. Paul lez Durance, France
 
  Con­struc­tion of ITER has start­ed at the Cadarache site in south­ern France. The first build­ings are tak­ing shape and more than 60 % of the in-kind pro­cure­ment has been com­mit­ted by the seven ITER mem­ber states (China, Eu­rope, India, Japan, Korea, Rus­sia and Unites States). The de­sign and man­u­fac­tur­ing of the main com­po­nents of the ma­chine is now un­der­way all over the world. Each of these com­po­nents comes with a local con­trol sys­tem, which must be in­te­grat­ed in the cen­tral con­trol sys­tem. The con­trol group at ITER has de­vel­oped two prod­ucts to fa­cil­i­tate this; the plant con­trol de­sign hand­book (PCDH) and the con­trol, data ac­cess and com­mu­ni­ca­tion (CODAC) core sys­tem. PCDH is a doc­u­ment which pre­scribes the tech­nolo­gies and meth­ods to be used in de­vel­op­ing the local con­trol sys­tem and sets the rules ap­pli­ca­ble to the in-kind pro­cure­ments. CODAC core sys­tem is a soft­ware pack­age, dis­tribut­ed to all in-kind pro­cure­ment de­vel­op­ers, which im­ple­ments the PCDH and fa­cil­i­tates the com­pli­ance of the local con­trol sys­tem. In par­al­lel, the ITER con­trol group is pro­ceed­ing with the de­sign of the cen­tral con­trol sys­tem to allow fully in­te­grat­ed and au­to­mat­ed op­er­a­tion of ITER. In this paper we re­port on the progress of de­sign, tech­nol­o­gy choic­es and dis­cuss jus­ti­fi­ca­tions of those choic­es. We also re­port on the re­sults of some pilot pro­jects aim­ing at val­i­dat­ing the de­sign and tech­nolo­gies.  
slides icon Slides MOBAUST01 [4.238 MB]  
 
MOPKS029 The CODAC Software Distribution for the ITER Plant Systems 227
 
  • F. Di Maio, L. Abadie, C.S. Kim, K. Mahajan, P. Makijarvi, D. Stepanov, N. Utzel, A. Wallander
    ITER Organization, St. Paul lez Durance, France
 
  Most of the sys­tems that con­sti­tutes the ITER plant will be built and sup­plied by the seven ITER do­mes­tic agen­cies. These plant sys­tems will re­quire their own In­stru­men­ta­tion and Con­trol (I&C) that will be pro­cured by the var­i­ous sup­pli­ers. For im­prov­ing the ho­mo­gene­ity of these plant sys­tem I&C, the CODAC group, that is in charge of the ITER con­trol sys­tem, is pro­mot­ing stan­dard­ized so­lu­tions at pro­ject level and makes avail­able, as a sup­port for these stan­dards, the soft­ware for the de­vel­op­ment and tests of the plant sys­tem I&C. The CODAC Core Sys­tem is built by the ITER Or­ga­ni­za­tion and dis­tribut­ed to all ITER part­ners. It in­cludes the ITER stan­dard op­er­at­ing sys­tem, RHEL, and the ITER stan­dard con­trol frame­work, EPICS, as well as some ITER spe­cif­ic tools, most­ly for con­fig­u­ra­tion man­age­ment, and ITER spe­cif­ic soft­ware mod­ules, such as drivers for stan­dard I/O boards. A pro­cess for the dis­tri­bu­tion and sup­port is in place since the first re­lease, in Febru­ary 2010, and has been con­tin­u­ous­ly im­proved to sup­port the de­vel­op­ment and dis­tri­bu­tion of the fol­low­ing ver­sions.  
poster icon Poster MOPKS029 [1.209 MB]  
 
WEPMU040 Packaging of Control System Software 1168
 
  • K. Žagar, M. Kobal, N. Saje, A. Žagar
    Cosylab, Ljubljana, Slovenia
  • F. Di Maio, D. Stepanov
    ITER Organization, St. Paul lez Durance, France
  • R. Šabjan
    COBIK, Solkan, Slovenia
 
  Funding: ITER European Union, European Regional Development Fund and Republic of Slovenia, Ministry of Higher Education, Science and Technology
Con­trol sys­tem soft­ware con­sists of sev­er­al parts – the core of the con­trol sys­tem, drivers for in­te­gra­tion of de­vices, con­fig­u­ra­tion for user in­ter­faces, alarm sys­tem, etc. Once the soft­ware is de­vel­oped and con­fig­ured, it must be in­stalled to com­put­ers where it runs. Usu­al­ly, it is in­stalled on an op­er­at­ing sys­tem whose ser­vices it needs, and also in some cases dy­nam­i­cal­ly links with the li­braries it pro­vides. Op­er­at­ing sys­tem can be quite com­plex it­self – for ex­am­ple, a typ­i­cal Linux dis­tri­bu­tion con­sists of sev­er­al thou­sand pack­ages. To man­age this com­plex­i­ty, we have de­cid­ed to rely on Red Hat Pack­age Man­age­ment sys­tem (RPM) to pack­age con­trol sys­tem soft­ware, and also en­sure it is prop­er­ly in­stalled (i.e., that de­pen­den­cies are also in­stalled, and that scripts are run after in­stal­la­tion if any ad­di­tion­al ac­tions need to be per­formed). As dozens of RPM pack­ages need to be pre­pared, we are re­duc­ing the amount of ef­fort and im­prov­ing con­sis­ten­cy be­tween pack­ages through a Maven-based in­fras­truc­ture that as­sists in pack­ag­ing (e.g., au­to­mat­ed gen­er­a­tion of RPM SPEC files, in­clud­ing au­to­mat­ed iden­ti­fi­ca­tion of de­pen­den­cies). So far, we have used it to pack­age EPICS, Con­trol Sys­tem Stu­dio (CSS) and sev­er­al de­vice drivers. We per­form ex­ten­sive test­ing on Red Hat En­ter­prise Linux 5.5, but we have also ver­i­fied that pack­ag­ing works on Cen­tOS and Sci­en­tif­ic Linux. In this ar­ti­cle, we de­scribe in greater de­tail the sys­tem­at­ic sys­tem of pack­ag­ing we are using, and its par­tic­u­lar ap­pli­ca­tion for the ITER CODAC Core Sys­tem.
 
poster icon Poster WEPMU040 [0.740 MB]