CERN Timing Overview

CERN Timing OverviewCERN Timing OverviewCERN timing overview

and our future plans with White Rabbit

Jean-Claude BAU – CERN – 22 March 2012 1

OverviewOverview

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

Future of the CERN timing• Overall view• First White Rabbit implementation

Sequencing modelsSequencing models Main goal Main goal

Sequencing

SequencingSequencing models models Strong coupling concepts Strong coupling concepts

Cycle

Injection

Extraction

Cycle 1Cycle 1time

Cycle 2Cycle 2

Injections

Extraction


Basic Period

Cycle 2Cycle 2

Injections

Extraction

BP 1 BP 2

Cycle length = N * Basic PeriodCycle length = N * Basic PeriodBasic Period length = currently 1200ms Basic Period length = currently 1200ms

time


Beam

Cycle 3Cycle 3

Injections

Extractions

Cycle 1Cycle 1 Cycle 2Cycle 2

ClientAcc

ClientAcc

Inj.Acc.Inj.Acc.

All cycles are linked together :All cycles are linked together :All cycles of a beam are always All cycles of a beam are always playedplayed

time

time


Spare beams

Beam ABeam A

Beam ABeam A Beam ABeam A

ClientAcc

ClientAcc

Beam BBeam B Beam CBeam C

Beam BBeam B Beam CBeam C

time

timeInj.Acc.Inj.Acc.

Beam DBeam D

Beam DBeam D

Beam EBeam E

Beam FBeam F

A spare must be on the A spare must be on the shadow of its parentshadow of its parent


Beam Coordination Diagram

AAClientAcc

ClientAcc

time

timeInj.Acc.Inj.Acc.

AA AA

BB

BB BB CC

CC

DD

DD

EE

EE FF

FF GG II

HH

• A BCD is executed in a loopA BCD is executed in a loop• Each accelerator has its own phaseEach 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

Duration


Sequence

NormalOperation

NormalOperation

CoastPrepareCoast

Prepare CoastCoast CoastRecoverCoast

RecoverOutput

Executed 1 time Executed 1 time

Loop waiting condition Loop waiting condition

BCD

Sequence 2Sequence 2



Coupling/Decoupling

ManualManual


Sequence 1Sequence 1Acc 1

Acc 2

• Decoupled acc. play different Decoupled acc. play different BCDs & seq.BCDs & seq.

• No beam can be playedNo beam can be played• Can be recoupled at some Can be recoupled at some

key pointskey points

NormalOperation

NormalOperation

CoastPrepareCoast

Prepare CoastCoast CoastRecoverCoast

Recover

AutomaticAutomatic

Acc 1

Acc 2

Coupling point Decoupling point


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


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

Sequencing modelsSequencing models Loose coupling concepts Loose coupling concepts

Loose coupling

FillingFillingtime

Unpredictable time

Inj. Inj.

CollisionsCollisions

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

Sequencing modelsSequencing models Interaction Loose/Strong coupling accelerators Interaction Loose/Strong coupling accelerators

LHC Injection

LHC injectors Data Master(Strong coupling)

LHC Data Master(Loose coupling)

timetime

Beam request (Type, Ring, Nb batches, ….)

Forewarning Injection

Unpredictable time

Injection

Predictabletime

Distributed timingDistributed timing Messages sent on the timing network 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 messagesExternal 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

Distributed timingDistributed timing Messages sent on the timing networkMessages sent on the timing network

Time window

UTC millisecond ticks

t0 t0+1ms

Msg 1Msg 1 Msg 2Msg 2 Msg nMsg n

Msg 1Msg 1 RTTaskRT

Task

Time

Messages sent on the timing network

Msg 2Msg 2

Distributed timingDistributed timing Local timing Local timing

Timing Receiver card

Msg 1Msg 1 Msg 2Msg 2 Msg nMsg n Timing network

External starts

Clocks

Pulses Trigger external devices Chain counters among timing

receivers

Trigger external devices Chain counters among timing

receivers

RTTaskRT

Task

Distributed timingDistributed timing Local timing Local timing

Complex timing layout

Distributed timingDistributed timing Client timing Client timing librarieslibraries

Front-end timing libraries

WRReceiver

WRReceiver

White Rabbit network

GMTReceiver

GMTReceiver

GMT network

Timing low level layerTiming low level layer

GMT specificGMT specific WR specificWR specific

Timing abstract layerTiming abstract layer

Applications(FESA, …)

Applications(FESA, …)

Concept of triggers/payloads/Telegram

Concept of triggers/payloads/Telegram To be definedTo be defined

Concept of triggers/fieldsConcept of triggers/fields

TransformationTransformation

DB

Future of the CERN timingFuture of the CERN timing OverallOverall viewview

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


VLANs


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


WRDM: Solutions

Future of the CERN timingFuture of the CERN timing First White Rabbit implementation First White Rabbit implementation

AD& ELENA decelerators

Strong coupling acceleratorsStrong coupling accelerators

Loose couplingLoose coupling

AD -> RenovationELENA -> New acceleratorMain 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 -> RenovationELENA -> New acceleratorMain 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 ELENAStop

Future of the CERN timingFuture of the CERN timing First White Rabbit implementation First White Rabbit implementation

WR deployment

WRDMAD & ELENA

WRDMAD & ELENA

WR/GMTGatewayWR/GMTGateway

GTMReceivers

GTMReceiversGTM

ReceiversGTM

ReceiversGTMReceivers

GTMReceiversGTM

ReceiversGTM

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

CERN Timing Overview

Documents

Transcript of CERN Timing Overview