IFMIF-EVEDA Epics meeting 2009-04 V2 by wulinqing

VIEWS: 8 PAGES: 15

									i r f u

                IFMIF/EVEDA
s a c la y
             Control System Basis


                  J.F. Gournay
               CEA Saclay – Irfu/SIS
                                                           The IFMIF/EVEDA Project
i r f u
                 • 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
s a c la y         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
                                                            EVEDA
i r f u             • Identical to the final IFMIF accelerator except that
                      the HE portion will comprise only the first accelerating module
                    • Injector: ion source + LE Beam transport + diagnostics
                    • RFQ: 100keV -> 5MeV
s a c la y
                    • 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
Accelerator System Group                                                        Project Team                                           Organisation
                                                                                 Rokkasho

                              Management Team ~ 16

i r f u                                               Deputy PL                   ASG PL                             Deputy PL
 ASG-MT                                                A. Ibarra                  A. Mosnier                          A. Facco

    =                         Quality Assurance               Project Control                  Systems Engineer                         Integr-Qualif
                                 subcontractor                   P. Gastinel                       PY Beauvais                            V. Hennion
stransverse
 a c la y
activities
                                Beam Dynamics                Safety-Radiopro                       Infra-Utilities                CAD & Engineering
officers                           P. Nghiem                      P. Joyer                            T. Trublet                     subcontractor
    +
                                         Injector                    RFQ                               SC DTL                        Mat. Section
sub-systems                               R. Gobin                  A. Pisent                          F. Orsini                      Y. Podadera
coordinators                      BDump & Trans.                   RF Power                     Beam Instru.                       Accel. Control
                                     B. Branas                      P. Mendez              J. Marroncle / Y. Podadera                JF Gournay

 ASG-HT                       Home Teams ~ 35

                                  CEA                          INFN-LNL                    CIEMAT                                 SCKCEN
                                   Injector                    RFQ                        RF Power                              RF Power
                                   SC DTL & Cryo                                           SC DTL
                                   Matching Section                                        Matching Section
                                   RF Power                                                BD & Transport
                                   Accel. Controls                                         Safety/Radiopro
                                   Safety - Radiopro                                       Beam Instrum.
                                   Beam Instrum.

             IFMIF-EVEDA - Accelerator System Group – CS                                       Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009
                                                           Control System Sharing
i r f u
                 • Control systems developed in each EU institute (the so-called local
                   control systems or LCSs)
                 • CEA Saclay
s a c la y               –    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
                                                           Milestones
i r f u



s a c la y




             IFMIF-EVEDA - Accelerator System Group – CS           Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009
                 Conceptual Design – Architecture, Hardware
i r f u
                 • The conceptual design document is
                   expected to be the foundation for the
                   development of all LCSs
s a c la y
                 • 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
                                                             Solutions
i r f u
                 • 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)

s a c la y       • 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
                                                           Software platform
i r f u
                 • To make sure of the compatibility between the different subsystems, a
                   Common Software Platform will be used by each institute
s a c la y       • 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
                                                           Application Model
i r f u
                 • A development model for IOC applications is distributed with the
                   Common Software Platform
s a c la y       • 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
             IFMIF-EVEDA - Accelerator System Group – CS              Epics   Collaboration Meeting, Vancouver, April 30 – May 2nd,
                                                                                   |       |      |      `-----O.Common               2009
                                                                                   |       |      |      `-----O.linux-x86
                                                                                   |       |      |      `-----O.vxWorks-mvme5500
                                                             Naming convention
i r f u
                  • Based on similar principles as for SNS, Spiral2 and other labs


s a c la y                            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
                                                           Evaluation of RTEMS
i r f u
                 • Long and positive experience of VxWorks
                 • Due to the VxWorks licensing cost, Saclay began to use RTEMS
s a c la y       • 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
                                                           Injector Control system
i r f u



s a c la y




             IFMIF-EVEDA - Accelerator System Group – CS                 Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009
                                                           Injector Network Architecture
i r f u



s a c la y




             IFMIF-EVEDA - Accelerator System Group – CS                    Epics Collaboration Meeting, Vancouver, April 30 – May 2nd, 2009
                                                           Conclusion
i r f u
                 • EVEDA control system will be based on conservative EPICS solutions,
                   except for some particular points (OPC, software organization)
s a c la y
                 • 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

								
To top