1 / 15

IFMIF/EVEDA Control System Basis J.F. Gournay CEA Saclay – Irfu/SIS

IFMIF/EVEDA Control System Basis J.F. Gournay CEA Saclay – Irfu/SIS. The IFMIF/EVEDA Project. This project takes place in a EU-JA bilateral agreement for the “Broader Approach for Fusion”. Its an addition to the ITER project

rianne
Télécharger la présentation

IFMIF/EVEDA Control System Basis J.F. Gournay CEA Saclay – Irfu/SIS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IFMIF/EVEDAControl System BasisJ.F. GournayCEA Saclay – Irfu/SIS

  2. The IFMIF/EVEDA Project • This project takes place in a EU-JA bilateral agreement for the “Broader Approach for Fusion”. Its an addition to the ITER project • IFMIF: International Fusion Materials Irradiation Facility -> intense flux of 14MeV neutrons for material characterization (2 CW linacs, 125mA deuterons, 40MeV, lithium target) • EVEDA: Engineering Validation and Engineering Design Activities -> prototype for IFMIF (1 CW accelerator 125mA, 9MeV) IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  3. EVEDA • Identical to the final IFMIF accelerator except thatthe HE portion will comprise only the first accelerating module • Injector: ion source + LE Beam transport + diagnostics • RFQ: 100keV -> 5MeV • HWR superconducting accelerator (1 module) 5MeV->9MeV • HEBT and Beam Dump: maximum power of 1.125MW Designed and manufactured in Europe, installed in Japan (Rokkasho) IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  4. Accelerator System Group Organisation Project Team Rokkasho Management Team ~ 16 Deputy PL A. Ibarra ASG PL A. Mosnier Deputy PL A. Facco ASG-MT = Quality Assurance subcontractor Project Control P. Gastinel Systems Engineer PY Beauvais Integr-Qualif V. Hennion transverse activities officers Beam Dynamics P. Nghiem Safety-Radiopro P. Joyer Infra-Utilities T. Trublet CAD & Engineering subcontractor + Injector R. Gobin RFQ A. Pisent SC DTL F. Orsini Mat. Section Y. Podadera sub-systems coordinators BDump & Trans. B. Branas RF Power P. Mendez Beam Instru. J. Marroncle / Y. Podadera Accel. Control JF Gournay ASG-HT Home Teams ~ 35 • CEA • Injector • SC DTL & Cryo • Matching Section • RF Power • Accel. Controls • Safety - Radiopro • Beam Instrum. • INFN-LNL • RFQ • CIEMAT • RF Power • SC DTL • Matching Section • BD & Transport • Safety/Radiopro • Beam Instrum. • SCKCEN • RF Power IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  5. Control System Sharing • Control systems developed in each EU institute (the so-called local control systems or LCSs) • CEA Saclay • Responsible of the overall design and technology choices • Development of the control for the injector, DTL, many diagnostics • Responsible of the compatibility between the different LCSs • Partly responsible of the integration at Rokkasho • Ciemat Madrid • Responsible of the control for the LLRF system and the RF power system • Responsible of the control for HEBT and Beam Dump • Responsible of the control for the diagnostic plate • INFN Legnaro • Responsible of the control for the RFQ • JAEA will provide transversal facilities for the control system • Responsible of the overall PC and network infrastructure at Rokkasho • Responsible of the timing system, the machine protection system and the personal protection system (solutions from JParc) IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  6. Milestones IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  7. Conceptual Design – Architecture, Hardware • The conceptual design document is expected to be the foundation for the development of all LCSs • It describes the control system architecture and the chosen solutions for hardware and software • Architecture • 3 levels • Supervision • IOs processing • Fieldbus + interfacing • Clear limits of work sharing between institutes IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  8. Solutions • Many solutions similar to the Spiral2 project we manage almost in parallel with EVEDA(see presentations about Spiral2 from E. Lecorché et al. at Icalepcs, PCApac or Epics meetings) • Supervision: • PC Linux (Epics + PLCs) • PC Win (Anibus for PLCs local supervision and debugging) • the control system will rely on the set of standard commonly used Epics tools • IOs processing: • VME with a set of standard modules (MVME5500, ADAS ADC, DAC, binary boards) • PLCs with remote IOs on Profibus (Siemens S7) • Modbus-TCP for power supplies control (Mark Rivers, Univ. of Chicago) (standard version: 1 slave/TCP link only -> multi-slaves support added) • OPC for Epics-PLCs communication (Roland Fleischhauer, Carsten Winkler, BESSY) • Diagnostics interfacing to be studied • Optical diagnostics for the injector: solution from Cosylab selected IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  9. Software platform • To make sure of the compatibility between the different subsystems, a Common Software Platform will be used by each institute • It includes: • The real-time VxWorks kernel configured for the 5500 CPU and including all the necessary services • The set of compilers/linkers/include files for the VxWorks 6.7 development • Epics Base 3.14.10 configured for Linux and VxWorks target mvme5500 • Selection of EPICS Support modules • Support for the set of standard VME modules • Selection of EPICS Extensions • To be installed on a Linux PC (RedHat RHEL5.2) specifically configured (packages, users). Scripts to automatically configure the PC. • Starting from a configured PC, the installation of the base, support, extensions, requires only 3 package downloads, 3 tar commands and 3 make commands IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  10. Application Model • A development model for IOC applications is distributed with the Common Software Platform • This model aims to simplify and standardize applications development and IOC integration • The model gives a standard EPICS top directory with: • RELEASE file containing the support modules list • make rules to install graphical interfaces in top/gui directory • site specific IOC configuration scripts (CONFIG_SITE_<target>.cmd) for network, NFS, time, log, autosave • many examples to verify the installation of the common platform • The model includes “Eveda makeBaseApp templates” (thanks to Andrew Johnson for his help) to build and boot IOC applications and to instantiate database objects /home/IFMIFmgr/topIFMIF `-----bin `-----configure `-----db `-----dbd `-----src `-----gui `-----include `-----iocBoot | `-----iocExampleLinux | | `-----boot | | `-----db | | | `-----O.Common | | | `-----O.linux-x86 | | | `-----O.vxWorks-mvme5500 | | `-----src | | | `-----O.Common | | | `-----O.linux-x86 | | | `-----O.vxWorks-mvme5500 IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  11. Naming convention • Based on similar principles as for SNS, Spiral2 and other labs SSSSSS:DDDDII_CCCC:NNNNNNNN Subsystem Device Signal name A utility (derived from Spiral2), accessible from a Web browser by all LCS developers, will be used for the creation of new fields (dictionary of all allowed fields) and for syntax checking IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  12. Evaluation of RTEMS • Long and positive experience of VxWorks • Due to the VxWorks licensing cost, Saclay began to use RTEMS • For IFMIF/EVEDA, we did a complete evaluation • We had positive feedback from the Epics community • But we didn’t see yet any extensive experience for a big facility • What about management of all available CPU ressources with RTEMS ? (2nd Ethernet port, DMA …). What about availabilty of standard drivers ? (PMC modules) • JAEA was strongly in favor of VxWorks (JParc experience) • Conclusion: VxWorks will be used for IFMIF/EVEDA IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  13. Injector Control system Work already in progress: the deuterons source will run in 2010 IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  14. Injector Network Architecture Same scheme will be extended To the other LCSs IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

  15. Conclusion • EVEDA control system will be based on conservative EPICS solutions, except for some particular points (OPC, software organization) • The parallel development with Spiral2 control system enables to re-use many experienced solutions • Main challenge: except the injector LCS which will be commissioned at Saclay, all the other LCSs will be developed in Europe by each institute but could not be fully tested and integrated together before their shipping at Rokkasho IFMIF-EVEDA - Accelerator System Group – CS Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009

More Related