1. CERN Timing Overview CERN timing overview and our future plans with White Rabbit Jean-Claude BAU – CERN – 22 March 20121

2. Overview Sequencing models Goal Strong coupling concept Loose coupling concept Interaction Loose/Strong coupling Sequencing models Goal Strong coupling concept Loose coupling concept Interaction Loose/Strong coupling Timing distribution Messages sent on the timing network Local timing Client timing libraries Timing distribution Messages sent on the timing network Local timing Client timing libraries Future of the CERN timing Overall view First White Rabbit implementation Future of the CERN timing Overall view First White Rabbit implementation

3. Sequencing models  Main goal Sequencing

4. Sequencing models  Strong coupling concepts Cycle Injection Extraction Cycle 1 time Cycle 2 Injections Extraction

5. Sequencing models  Strong coupling concepts Basic Period Cycle 2 Injections Extraction BP 1 BP 2 Cycle length = N * Basic Period Basic Period length = currently 1200ms time

6. Sequencing models  Strong coupling concepts Beam Cycle 3 Injections Extractions Cycle 1 Cycle 2 Client Acc Client Acc Inj. Acc. Inj. Acc. All cycles are linked together :  All cycles of a beam are always played time

7. Sequencing models  Strong coupling concepts Spare beams Beam A Client Acc Client Acc Beam B Beam C Beam B Beam C time Inj. Acc. Inj. Acc. Beam D Beam E Beam F A spare must be on the shadow of its parent

8. Sequencing models  Strong coupling concepts Beam Coordination Diagram A A Client Acc Client Acc time Inj. Acc. Inj. Acc. A A A A B B B B B B C C C C D D D D E E E E F F F F G G I I H H A BCD is executed in a loop A BCD is executed in a loop Each accelerator has its own phase Each accelerator has its own phase All accelerators in a BCD have the same duration All accelerators in a BCD have the same duration Phase Duration

9. Sequencing models  Strong coupling concepts Sequence Normal Operation Normal Operation Coast Prepare Coast Prepare Coast Recover Coast Recover Output Executed 1 time Loop waiting condition BCD Sequence 2 Sequence 3

10. Sequencing models  Strong coupling concepts Coupling/Decoupling Manual Sequence 2 Sequence 1 Acc 1 Acc 2 Decoupled acc. play different BCDs & seq. Decoupled acc. play different BCDs & seq. No beam can be played No beam can be played Can be recoupled at some key points Can be recoupled at some key points Normal Operation Normal Operation Coast Prepare Coast Prepare Coast Recover Coast Recover Automatic Acc 1 Acc 2 Coupling point Decoupling point

11. Sequencing models  Strong coupling concepts Advantages ◦Manage by one timing data master ◦Optimize the usage of the accelerators Advantages ◦Manage by one timing data master ◦Optimize the usage of the accelerators Constraints ◦Maintenance ◦Complex ◦Find a common basic period of time Constraints ◦Maintenance ◦Complex ◦Find a common basic period of time

12. Sequencing models  Strong coupling concepts When to apply this model ? ◦Frequent beam transfer among accelerators ◦Short cycle length ◦Optimization of the accelerators ◦Very close accelerator schedule (maintenance) Use at CERN for LEIR, BOOSTER, CPS, SPS

13. Sequencing models  Loose coupling concepts Loose coupling Filling time Unpredictable time Inj. Collisions Used when : ◦The duration of the cycle is unpredictable ◦The cycling time of the accelerator is long compared to its injector Need to be synchronized with injector only at injection points (RDV) Need to wait the injector at the RDV point Used when : ◦The duration of the cycle is unpredictable ◦The cycling time of the accelerator is long compared to its injector Need to be synchronized with injector only at injection points (RDV) Need to wait the injector at the RDV point

14. Sequencing models  Interaction Loose/Strong coupling accelerators LHC Injection LHC injectors Data Master (Strong coupling) LHC Data Master (Loose coupling) time Beam request (Type, Ring, Nb batches, ….) Forewarning Injection Unpredictable time Injection Predictable time

15. Distributed timing  Messages sent on the timing network Timing Data Master Timing network Telegram Cable id Triggers Used to trigger ◦Local counters ◦Real Time tasks High priority messages Used to trigger ◦Local counters ◦Real Time tasks High priority messages External triggers Describe the played Cycle and the next one ◦Particle type, beam destination, … Sent every Basic Periods Low priority messages Describe the played Cycle and the next one ◦Particle type, beam destination, … Sent every Basic Periods Low priority messages UTC time Identification of the timing cable ◦Auto configuration of the computer Low priority messages Identification of the timing cable ◦Auto configuration of the computer Low priority messages UTC time for time stamping Low priority messages UTC time for time stamping Low priority messages Diagnostics To check the quality of the transmissions Low priority messages To check the quality of the transmissions Low priority messages

16. Distributed timing  Messages sent on the timing network Time window UTC millisecond ticks t0 t0+1ms Msg 1 Msg 2 Msg n Msg 1 RT Task RT Task Time Messages sent on the timing network Msg 2

17. Distributed timing  Local timing Timing Receiver card Msg 1 Msg 2 Msg n Timing network External starts Clocks Pulses Trigger external devices Chain counters among timing receivers Trigger external devices Chain counters among timing receivers RT Task RT Task

18. Distributed timing  Local timing Complex timing layout

19. Distributed timing  Client timing libraries Front-end timing libraries WR Receiver WR Receiver White Rabbit network GMT Receiver GMT Receiver GMT network Timing low level layer GMT specific WR specific Timing abstract layer Applications (FESA, …) Applications (FESA, …) Concept of triggers/payloads/Telegram To be defined Concept of triggers/fields Transformation DB

20. Future of the CERN timing  Overall view http://www.ohwr.org/attachments/913/wrCernControlAndTiming.v1.1.pdf Complex to manage redundancy for Timing & Data WRDM with two ports for the redundancy http://www.ohwr.org/attachments/913/wrCernControlAndTiming.v1.1.pdf Complex to manage redundancy for Timing & Data WRDM with two ports for the redundancy Overview

21. Future of the CERN timing  Overall view VLANs

22. Future of the CERN timing  Overall view Consist of two synchronized WRDM running exactly the same thing  Produce the same messages Only one at a time sends its messages on the WR network The switch between the WRDM should be transparent Main goal : ◦Fast upgrades during a technical stop ◦Reduce intervention time in case of hardware failure of the WRDM WRDM: Master/Slave

23. Future of the CERN timing  Overall view WRDM: Solutions

24. Future of the CERN timing  First White Rabbit implementation AD& ELENA decelerators Strong coupling accelerators Loose coupling AD -> Renovation ELENA -> New accelerator Main constraints ◦AD injection : Can’t wait on the flat top.  synchronization at the start of the ramp ◦Cycle length unknown (Stop) ◦AD ejections to ELENA AD -> Renovation ELENA -> New accelerator Main constraints ◦AD injection : Can’t wait on the flat top.  synchronization at the start of the ramp ◦Cycle length unknown (Stop) ◦AD ejections to ELENA Inj. Ej. to ELENA Stop

25. Future of the CERN timing  First White Rabbit implementation WR deployment WRDM AD & ELENA WRDM AD & ELENA WR/GMT Gateway WR/GMT Gateway GTM Receivers GTM Receivers GTM Receivers GTM Receivers GTM Receivers GTM Receivers GTM Receivers GTM Receivers Deployment for end of 2013 ◦Only a WRDM, No WR nodes foreseen ◦WR to GMT gateway (end 2012) ◦Use of GMT receivers Deployment for end of 2014 ◦AD in production, ELENA in commissioning  2 WRDM ? Deployment for end of 2015 ◦Both in production Deployment for end of 2013 ◦Only a WRDM, No WR nodes foreseen ◦WR to GMT gateway (end 2012) ◦Use of GMT receivers Deployment for end of 2014 ◦AD in production, ELENA in commissioning  2 WRDM ? Deployment for end of 2015 ◦Both in production