Main event codes for HXR/SXR running (with permission from Carolina Bianchini Mattison):


Detailed picture of event codes and modifier bits


Relative timing of the event codes


LCLS timing operates at 360 Hz; each 360 Hz interval is called a "time slot".  The time slots iterate from 1 to 6 and then cycle back to 1 again.  So, time slot 1 (or any particular time slot) occurs every 6 360Hz intervals or 60 Hz.  In addition to that, a set of markers are generated to distinguish the consecutive sets of time slots.  A 60 Hz marker is attached to every set of 6 time slots; a 30 Hz marker is attached to every other set of 6 time slots; a 10 Hz marker is attached to every 6th set of time slots, and so on down to 0.5 Hz.  Thus, the sequence of time slots and markers looks like

60Hzxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
30Hzxxxxxx





xxxxxx





xxxxxx





xxxxxx






10Hzxxxxxx





























xxxxxx






5Hzxxxxxx










































1Hzxxxxxx










































0.5Hzxxxxxx










































Time Slot123456123456123456123456123456123456123456123456

I hope you get the idea...


A set of event codes maps to the occurrence of these time slots in the following manner.


60Hz30Hz10Hz5Hz1Hz0.5Hz
TS1111213141516
TS2212223242526
TS3313233343536
TS4414243444546
TS5515253545556
TS6616263646566


There are also event codes 10, 20, 30, 40, 50, 60.  These are generated such that 10 = 11+41, 20=21+51, 30=31+61, 40=11+41, 50=21+51, 60=31+61; i.e. they are all 120 Hz and occur for two different timeslots each.


Shared Beam Timing

When the copper LINAC is setup to deliver beam to both soft and hard x-ray lines it does so by preferentially sending hard x-ray beam on time slot 4 and soft x-ray beam on time slot 1.  LCLS only uses time slots 1 and 4 to deliver beam.  To get more than 60 Hz beam to either line requires the other time slot (1 or 4) to be used.  So, the shared delivery modes should look like so

60Hzxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
30Hzxx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

xx

10Hzxx









xx









xx









xx









5Hzxx





















xx





















1Hzxx













































0.5Hzxx













































Time Slot141414141414141414141414141414141414141414141414
60H/60SSHSHSHSHSHSHSHSHSHSHSHSHSHSHSHSHSHSHSHSHSHSHSHSH
90H/30SSHHHSHHHSHHHSHHHSHHHSHHHSHHHSHHHSHHHSHHHSHHHSHHH
110H/10SSHHHHHHHHHHHSHHHHHHHHHHHSHHHHHHHHHHHSHHHHHHHHHHH
115H/5SSHHHHHHHHHHHHHHHHHHHHHHHSHHHHHHHHHHHHHHHHHHHHHHH


and so on.  I hope you get the idea.  The general rule is that the lower rate beam line will always be delivered on its time slot (1=SXR, 4=HXR) and its beam rate marker (0.5 .. 60Hz), and the other beam line will consume the remainder of the time slots 1 and 4.

Special Event codes

Event codemeaning
162BYKIK - see above
163

kicker to A-line (parasitic running with Endstation A - has not been done recently)

It has been observed that the presence of code 163 means that you can have beam even on event code 162!

There is no reason for you to see this event code (it was on for some test w/o realizing the consequences for a beamtime in run 20)

event code 137 correctly shows if beam is present.

164HXR test burst - request burst via event sequencer being NOT the beam owner
150HXR burst- request burst via event sequencer being the beam owner w/ correct setup in ACR