Central TIMING

Overview and basic concepts for AP section

GPSOne pulse per Second

GPS

Smart clockPLL

PLLOne pulse

per Second

Phase locked10MHz

Basic Period1200/900/600 ms

Advanced (100us)One pulseper Second

Synchronized 1KHz(slow timing clock)

Phase locked10MHz

Phase looked40 MHz Eventencoding clock

40MHz PLL

CTSYNC

RS485Timing

CTGU

The newgenerationlowjitter <1nsVMEbasedMTGmodule

UTC time (NTP or GPS)

Eventtables

External events

Hardware developments CTG and CTR

CERN UTC Time

Set once on startup & on Leap Seconds

RS485Timing

CTRP

40 MHz

10 MHz

1 KHz

1PPS

Delay

Control SystemCERN UTC Time

25ns steps

Timing receiver

Events on the GMT

7 events and one millisecond event per millisecond Each event is a 32-Bit quantity…

Type of event 4-Bits Timing=CTIM, UTC-Time, Telegram ….

Accelerator 4-Bits LHC, SPS, CPS, PSB, ADE …

Code 8-Bits Event-Code, Telegram-Group …

Payload 16-Bits User, UTC, Telegram-Group-Value …

CCC TIMING RACK 4SYNC

CCC TIMING RACK 5CBCM B

CCC TIMING RACK 3CBCM A

Main MTG A

LHC MTG A

Main MTG B

LHC MTG B

HP GPS Receiver

GPS Antenna

1PPS 10MHz

LHC Switch

Main Switch

Reflective memoryHUB

DSC Comunications

DSC Synchronization

96

HardwareExternal

Conditionsfrom patch pannel

1PPS

10MHz

40MHz

Sync

A1PPS40MHz

Sync

A1PPS

40MHz

Sync

A1PPS40MHz

Sync

A1PPS

40MHz

Sync

A1PPS

GMTs PSB LEI CPS ADE SPS GMTs PSB LEI CPS ADE SPS

LHC GMT

LHC GMT

16 Ext Events

16 Ext Events 16 Ext Events

16 Ext Events

LHC Beam Energy/Intensity

GMT

LHC Beam Energy/Intensity

GMT

Work-Station /Server

Timing EventGMT

to CCC

SPS Intensity SPS Intensity

What is sequencing?

PS is a network of interconnected accelerators with particle beams passing from one machine to another via transfer lines. Off line organization of these accelerator cycles into

sequences that fulfill the operational requirements. Real time coordination of cycles and beams for transfer

rendezvous points in the accelerator network. Real time response to requests and inhibits that change

the running sequence, seamlessly on the fly.

Terminology: The Telegram

The Telegram is a set of parameters (group values !) (PARTY=PROTON, DEST=FTS,….) describing what each accelerator should do in the current and sometimes in the next accelerator cycles.

Each accelerator telegram layout can be different Telegrams drive the PPM/Multiplexing and SPS Multi-

cycling usually via the USER group They are delivered each basic period.

In the LHC Injector Chain [LIC] 1BP = 1.2S

for LHC it will most probably be 1S

Terminology: The basic period

The basic-period duration is used to define sequence durations The basic-period is a duration measured in

milliseconds (1200 LIC, 1000 LHC, 100 CTF …) for a given accelerator network

It determines the telegram repetition rate and the control systems refresh rate

all cycle and super-cycle durations are a multiple of the basic-period time

The basic-period is the heart beat of the LIC central timing

Terminology: The CYCLE

Set of basic period Length = N x Basic Period Static telegram groups

Their values don’t change within a cycle (USER=SFTPRO)

They are mostly calculated offline (User Matrix) Dynamic telegram groups

Their values can change from a basic period to another within a cycle

They are mostly calculated in real time

USER=EASTA, PARTY=PROTON,BPNM=1

EASTA Cycle

USER=EASTA, PARTY=PROTON,BPNM=2

Basic periods

Terminology: The CYCLE(2)

Representation Cycle of 1 BP

Cycle of 2 BP

A cycle is the basic unit of work for a front end processor in LIC, where the PPM/Multiplexing works with cycles

SFTPRO

EASTC

USER group value

drives PPM

Terminology: The BEAM Links cycles together (in the

same or different accelerators)

When a beam is played by MTG, all cycles of the beam will be played.

The basic unit of work for the central timing

Decisions taken by the MTG on what to do next are based on beams

Defined by : Set of cycles Phase between cycles

Terminology: The BEAM (2)

Representation Looks like one BP in the editor, but is actually defined in real

time by the accelerator phase offsets

EASTA

EASTC

PSB

CPS Phase

Strong and Loose coupling

Strong Coupling Same supercycle length Cycles are strongly

connected to create a beam Free supercycle phase PSB,CPS,LEI,SPS

Loose Coupling Free supercycle length RT synchronization with

machine in strong coupling for beam injection

Supercycle can be stopped Occasional injection ADE

LHC is neither of these

Terminology: NORMAL/SPARE

Maximize accelerator up-time.

Terminology: NORMAL/SPARE(2) Representation

ZERO

PSB

CPSSFTPRO

ISOGPS

SFTPRO

Normal

Normal

Spare

Spare

Terminology: Beam Coordination Diagram

Define the organization of the beams Beam positions Normal/Spare relationship

Built using editors Strong coupling BCD editor

Cycle/Beam/ Compound Operation/BCD builder ADE editor

The BCD is the result of the merging of BCDs produces by the two editors.

Sequences

Lead-InPulse-Start to 14Gev

Main Sequence for Fixed Target

Lead-OutPulse Stop

Lead-InPulse Start to 26Gev

Main Sequence for LHC filling Lead-OutPulse Stop

Fixed Target

LHC Fill

Repeat

LevelSwitch

Sequence Change

Main Lead-out

EjectRampPulse Stop

32 Levels

Lead-in Coast

Pulse StartInject, Ramp

LHC Fillrequest

The Sequence Set

Set of BCDs 16 Sequences Played Sequence/BCD

selected by external conditions

Sequence/BCD change immediately at the end of the supercycle

External Conditions

Comprised of Requests, Inhibits, Interlocks. They are logic levels 1=Bad, 0=Good They control the CBCM

Normal Spare Sequence selection BCD termination

Can be either hardware or software Used By FIDO to make decisions on what to do

next

Footprints and response time

PSB SFTPSB SFT

CPS SFT CPS SFT

SPS SFT

CPS ADE

PSB ADE

SPS MD

CPS SPSMD

PSB ISO PSB SPSMD

Present SPSNext SPS

Output Stream delay

CommitedDescision

Next info in telegram

Time

Footprint of the Spare <= Footprint of the Normal

FiDo programs

MTG integrates the compiler and the interpreter. Can be downloaded in real-time

Syntax Example% Init %(s_level := Level ); % Selected level %( if ( Cmds.cmd_sl ) ( % Request system level % s_level:=d_level % Default level -> Zero Sequence% ) ( Cmds.cmd_nl ) ( % Request next level to execute %

( if ((Excon_7.r_seqsys = 0) & (TId_29>0) ) ( s_level:=d_level ) ( TId_1>0 ) ( s_level:=1 ) ( TId_2>0 ) ( s_level:=2 ) ( TId_3>0 ) ( s_level:=3 ) ( TId_4>0 ) ( s_level:=4 ) ( TId_5>0 ) ( s_level:=5 ) ( TId_6>0 ) ( s_level:=6 ) ( TId_7>0 ) ( s_level:=7 ) ( TId_8>0 ) ( s_level:=8 ) ( else ) ( s_level:=d_level ) ) ));% ----------------------------------------------------------------- %% Inhibits %% ----------------------------------------------------------------- %( BExcon_4.i_ps := Excon_4.i_ps );( BExcon_4.i_p_ad := (tt2_fta & Excon_4.i_p_ad) );( BExcon_4.i_p_md := (destps & misc_a.1 & Excon_4.i_p_md) );( BExcon_4.i_p_eat7 := ((b_ea_t7 ! b_ea_nt7) & Excon_4.i_p_eat7) );( BExcon_4.i_p_ean := ((b_ea_n ! b_ea_nt7 ! b_ea_nt8) & Excon_4.i_p_ean) );( BExcon_4.i_p_eat8 := ((b_ea_t8 ! b_ea_nt8) & Excon_4.i_p_eat8) );( BExcon_4.i_p_ntof := (ntof & Excon_4.i_p_ntof) );

% Return boolean Yes or No in program result bit %

( bad := (BExcon_1 ! BExcon_2 ! BExcon_3 ! BExcon_4) );( PResult := 0 );( PResult.pr_bad := bad );

% End of program %

bad )@

Decision tree

CPS SPSPSBPSBCPSSPSSPS

NormalSpare

Time

The MTG

Inputs BCDs External conditions Timing description (CTIM) External timings FiDo programs

Outputs Telegrams events Timing events Time events ...

Beam Coordination Diagram editor

Strong Coupling

Loose coupling ADEInjectionrendezvouspoints

Start point Function points Eject antiprotons

Cooling

Make MTG table

BCD

The BCD is the result of the merging of BCDs produces by the two editors.

BCD Editor: Rule checker

Sequence Editor

Sequence manager

MTG diagnostic

Timings events (CTIM)

Oracle description (Mapping Event Code Name)

Declare as CTIM equipment module Machine event Virtual events (PPM [LIC only]) Key events

Define the phase between accelerator Drive CTR/TG8 timings and interrupts for RT

task Validate Telegrams (RPLS)

CTIM (2)

SPS Cycles boundaries & payloads

Beam-in

Beam-out

Fixed Target

MD-26

1.2 (0.9) S periods [X n]

W-Start Cycle

Beam-In

Beam-Out

Master Inject (Virtual Event)

F( cycle )

Basic PeriodCycle Boundary

BeamCycle Boundary

Field

1 2 3 4 5 6 8 9 10 11 127Time

CPS

CPS

Timing events (CTIM) (3)

Controllable by knobs in real-time

Virtual eventKey events

About the LHC Timing

Basic-Periods don’t mean a lot, but 1S represents UTC

Telegrams don’t mean a lot Cycle means even less, fixed USER=1 Little or no PPM/Multiplexing The LHC timing is machine safety critical, so it must

be very simple/reliable and hardware monitored Response time to operational requests must be very

rapid <<100ms Controlled directly by the LSA sequencer Need to re-use existing controls infrastructure where

possible

About the LHC Timing

Highly interactive, logic is delegated to LSA Runs/Stops/Aborts several independent

asynchronous concurrent event tables on request Sends event(s) on request Payloads can be used in non multiplexing contexts Sends events such as “post-mortem” on external

event input Most data on the LHC timing cable comes from the

outside world Much closer to the LEP than to other cycling

machines in the LHC Injector Chain (LIC) Almost completely decoupled from LIC

LHC Timing, approach

The basic-period is the UTC second. Implemented as a FESA device controlled

directly from LSA New multi-tasking timing generator hardware

card. Telegram parameters are also events Hardware monitoring of safe beam

parameters

LHC Filling

LHC Nominal LHC Nominal

Batch 1 Batch 2 Batch 3 Batch 4 Batch 1 Batch 2 Batch 3 Batch 4CPS

PSB

SPS

LHC Injection plateauxLHC1S 1.2S

EastA

text

Status

Beam

Decide on the nextRing/Bucket

RephaseSPS RF

R1B2 3 Batch NominalR1B1 2 Batch Nominal

Pre-Injection plateaux Ramp Pilots

IsoldParasiticBeamS

EastaParasitic

Beam

MDMD

Will bedriven into

sparedependingon batchnumber

LHC Filling scheme TableFilling scheme: 234 334 334 334

Bucket Order: 123 456 789 10 11 12Beam intensity: Nominal

Order: All Ring 1 then All Ring 2On error: Repeat

Retry R1B1 2Batch

Dead Line

Nothing on thisside of the deadline can dependon the status of

the beam transfer

Go for R1B2 3Batch

LHC MTG

2.2 G-Bit / S optical link64Mb Reflective memories

CMW ServerLHC MTG

GMTLHC

Clocks:40.00 MHz GPS clock1PPS (1Hz) clockBasic period clock

Event

Tables

SafeParams

Energy/RingIntensity/RingSafe Beam FlgBeam present FlgExtraction permit FlgBIC Beam permit Flg

External Events

LSA High levelSequencer

LSA Archives

FESA LHC API

Slave/Master

See TC on Sept 21st

LHC Timing will be explained and the implications on the rest of the control

system