Realisation of the interlocking between SPS, LHC and CNGS and open issues

1. Realisation of the interlocking between SPS, LHC and CNGS and open issues Beam Interlock Systems (BIS) B.Puccio and R.Schmidt for the Beam Interlock Team

2. Why a Beam Interlock System? As one of the systems involved in the machine protection, the Interlock system has to: Transmitsthe result as: - Dump Request - Injection Permit - Extraction Enable Collects status or default signals Performs a summation of all signals Kicker System BIS

3. Specification for LHC Beam Interlock system • Fast • Safe • High Test Coverage • Maintainable • Monitorable • Cost Effective • Deterministic ~70μs over 28km Requesting Beam Dump = SIL 3 On startup – ‘As Good As New’ Low repair time Self-Diagnosing Provides first Post Mortem info Protects $$$ but need not be $$$ Know what it’s going to do & when 8. A CERN-wide generic Beam Interlock System LHC ring, LHC- Injection, SPS ring, Transfer-Lines

4. The LHC solution as a generic answer Application SW Beam Permit Beam Permit Control Network Beam Permit #2 up to 1200 meters VME CRATE …up to 14 User Interfaces + User Interfaces (installed in User’s rack) #1 Safe Beam Parameter Receiver Safe Beam Par. (via Timing) Test & Monitoring Module coppercable Patching #3 Core module Beam Permit Loops F.O. interface Beam Interlock Controller

5. Some Hardware pictures User Interface Front view PCB Front view CIBT card (Test & Monitoring board) BIC crate with beam-1 cards only Rear view Patching at the back of the BIC crate

6. The main features • BIC as proposed for LHC can be “easily” used for interlocking the SPS ring, SPS-LHC-CNGS Transfer lines and LHC Injection. • Designed to be Safe, Fast, and Deterministic. • Redundancy throughout: User Systems BIS  Kicker system • Simplicity for crucial process  Effort on monitoring and maintainability • Cost effective: • Set of BIC cards  6k CHF (VME system not included) • User Interface  1k CHF each (connection cable not included) • Using a Generic solution with unique Hardware: • Simplify the Hardware production, installation and maintenance • Reduce the workload in using a common Monitoring Software • Offer the same environment to the Operators

7. Beam Interlock Systems as service and client of AB-CO • The Beam Interlock Systems are at the same time service to the accelerator operation and client of AB/CO • Service: • Provide safe and fast linkbetween Equipment systems & Kicker system • Play key role in Post-Mortem process and Beam Abort analysis • Supply remote monitoring and failure diagnostics • Client: • VME system and Timing connection support from CO-HT • JAVA based supervision  support from CO-AP • FESA framework  supported as [] by CO-HC • (future) Database support for asset management, controls layout, naming and configuration support from CO-DM • Logging, Post Mortem and ALARMS client for CO-DM & CO-AP • Tools for automated commissioning during regular cold-checkout are expected (similar to the Sequencerused for Hw Commissioning)

8. Schedule • BIC project is quite mature now: • Basic technical choices validated during last TT40/TI8 Extraction tests. • Since then, the Hw has been upgraded and tested in the lab. • Hw board pre-series production foreseen for the end of the year. 2006 2007 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q4 Extensive testing additional Analysis of Dependability Series Production Install &Commission SPS start-up CNGS test Beam commissioning Injection test • BICs will be used for the next SPS start-up (in // with existing Interlock system) as a “real” test bench before LHC • Concerning the 2 next major milestones (CNGS tests and LHC sector test): the required BICs will be installed and commissioned on time.

9. System partition and manpower Manpower: the BIC hardware design, fabrication, installation and commissioning is performed by… In our team: 1.0 electronic engineer (very talented PhD student) 1.0 FSU for one year Help from other teams (inside and outside CO): 0.3 technical engineer (electronics) 0.5 technical engineer (electronics) * : if Injection Permit Loop involves distributed BICs

10. System X System X System X System X System X System X Injection Interlock Injection Interlock How to implement the Injection Inhibit requested by the Experiments and BT? • Using same architecture as for LHC Beam Permit in using same BIC: • Do NOT consume resources in new Hw & Sw developments • Easy to implement, to extend, to maintain, and to monitor • Expensive solution (25 to 30 KCHF per BIC), since only one connection per BIC • Other solutions are possible: • Using PLC and Optical Links for example • Collaboration with BT is being considered

11. Realisation of the interlocking between SPS, LHC and CNGS and open issues Safe Beam Parameters Transmission system

12. Summary of requirements BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BLM BIC BIC LHC modes BLM BLM BLM EXP. INJ InjK BETS BETS SafeEnergy Energy ? Beam_PresenceFlags INJ ExtI Ibeam1 BCT1 Safe_BeamFlags Ibeam2 BCT2 BETS: Beam Energy Tracker System InjK: Injection Kicker System ExtI: SPS Extraction Interlock BIC: Beam Interlock Controller BCT: Beam Current Transformer • 3 of the Parameters are built from 2 types of information: • The Parameter transmission is less time critical (except for the BeamPresenceFlags) • To be delivered with reliability to various systems • To be distributed over Long Distance • Expected level of reliability: SIL2

13. Proposal for distributing SLP via the timing system distribution CTG SLP GEN BLM BLM BLM BLM BLM BLM BLM BLM CTRS CTRS CTRS CTRS CTRS BLM BLM BLM BLM BLM BLM BLM BIC INJ BCT BCT BETS BIC BIC BIC ExtK INJ ExtI BLM BLM BLM EXP. Energy Timing Distributed Network Ibeam1 Ibeam2 Beam Presence Flags CTRS: Temporary name for a VME Timing Receiver card with dedicated SLP connections Safe Beam Flags MKQA • Energy and Beam Intensity values are transmitted to the Timing Generator (CTG) and to the SLP Generator • The SLP-G computes the Safe Beam Flags and the Beam Presence Flags • The SLP-G could be only used for critical cases: Beam Presence Flag should be guaranteed 1mS before Injection • The CTG sends regularly (every ~1sec) Parameters over the Timing network as “standard” frames • Safe Beam Parameters are received by the Users via dedicated VME board (“CTRS”) – ensuring safety • The SLP-G performs cross check in receiving Parameters via a “CTRS”

14. Conclusions • BIC is a tangible example of the fruitful collaboration within CO. An “equipment project” done from the front end to supervision layer withing the CO group. Concerning to the 2 next major milestones (CNGS tests and LHC sector test):  We expect the required BICs will be installed, commissioned on time and be ready to participate. Concerning Injection Inhibit requested by the Experiments: under study - Use similar architecture as LHC Beam Permit Loops with distributed BIC? - Or use another (and cheaper) solution? Concerning Transmission of Safe Beam Parameters via Timing System Network - Valuable idea for completing a essential request in using existing resources - Opportunity to confirm once more how a closed collaboration within CO can be profitable for the involved teams. Software support within CO has been good, and is required to continue for some time. The electronic engineer (PhD student) is vital for the BIC projects.

15. That’s all

16. Guinea pig Ginea pig back