Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 How To Set Up for the Event System on an IOC with an EVR(s) Assumes you already know what the event system provides and how it works.

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 epics/modules/event/ /README configure/RELEASE and xxxApp/src/Makefile ErConfigure and other st.cmd commands Hardware Setup Correcting IDs on PMC EVRs Database, ChannelWatcher, and Archiver Setup Nothing on Display Setup though Nothing on VME EVR vs PMC EVR

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 Beam Path Existing Control System 119MHz Clock EVREVR Hardware Block Diagram 2007 Commissioning IOCIOC EVGEVG PNETPNET Fiber Distribution: Timing Pattern, Timestamp, Event Codes EVR1EVR1 Acc and Standby Triggers 360Hz Fiducial Beam Rate, Beam Path Future MPS RF Timing Modulator Triggers PADs and PACs FAN1FAN1 FAN2FAN2 FAN3FAN3 EVR1EVR1... IOC1IOC1 CAM1CAM1 EVR8EVR8 IOC8IOC8 CAM8CAM8 Trigger Laser Steering Crate FAN4FAN4 EVR1EVR1 … IOC1IOC1 CAM1CAM1 EVR4EVR4 IOC4IOC4 CAM7CAM7 Profile Monitor Crate CAM2CAM2 CAM8CAM8 … … Triggers IOCIOC BPM FEE Acq and Calibration Triggers BPM Crates Timing Crate LLRF Crate EVR2EVR2 IOCIOC EVR3EVR3 EVREVR IOCIOC TORO FEE Toro Farc Crate

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 EVG Event Time Line – 4 Fiducials F1 (n=1) F2 (n=2) F3 (n=3) Hz Fiducial Time (msec) B0 P0 P1 P2 Receive Fn+3 PNET, determine Fn+3 LCLS pattern, and advance pipeline (n-2->n-1->n) HW starts sending event codes, starting with fiducial event code R1 9.3 R0 R2 E1E2 Set Event Codes in Other RAM based on the last patterns for Fn+1 E3 F0 (n=0) 8.3 R3 P3 E4 B-3 120Hz BEAM 1.0 L0 L1 L3 Send LCLS pattern L2

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 Trigger Event Time Line – 1 Beam Pulse (B0) F3 0 Fiducial Time (usec) B0 Acq Trigger 1023 Beam Kly Standby Record processing (event, interrupt) Fiducial Event Received Event Timestamp, pattern records, and BSA ready Receive pattern for 3 pulses ahead Hardware Triggers Triggering Event Codes Start Kly Accel

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 Event System Requirements Event Generator IOC : Send out proper event codes at 360Hz based on: PNET pattern input (beam code and bits that define beam path and other conditions) Add LCLS conditions such as BPM calibration on off-beam pulses, diagnostic pulse etc. Future – event codes also based on new MPS and user input Send out system timestamp with encoded pulse ID from PNET Send out PNET pattern to be used by SLC-aware IOCs Manage user-defined beam-synchronous acquisition measurement definitions (event definition or EDEF) Check for match between user EDEFs and input PNET pattern at 360Hz and tag matches in outgoing pattern

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 Event System Requirements, cont Event Receiver IOC: Set trigger delays, pulse widths, and enable/disable via user requests (not yet done on a pulse-by-pulse basis) Set event code per trigger (triggering done in HW when event code received) Receive event pattern 8.3 msec before corresponding pulse Perform beam-synchronous acquisition based on tags set by EVG in the event pattern Perform beam-synchronous acquisition for the SLC- aware IOC based on the PNET part of the event pattern Process pre-defined records when specific event codes are received

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 Databases and Displays Each IOC has its own substitutions files using databases/cwConfig files provided by the event module. Each IOC has its own displays for triggered and beam- synchronous devices. Other event-related diagnostics displays provided by the event module and currently accessible from the “Event” tab on lclshome. Databases divided into 4 categories: EVR Databases Pattern Databases Trigger Database BSA Databases

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 EVR Databases One evr record per EVR. Use evr.db (most apps) from event module. Apps that don’t use the trigger database or don’t save/restore delays, polarities, or pulse widths will use evrWithDelays.db or evrWithExtendedDelays.db from the event module instead. Matching display = tools/edm/display/event/evrDiags.edl Record Reference: bal/subsystems/timing/globalEventV3.htm

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 EVR Databases - cont One erevent record per triggering event per EVR: Use evrEventCtrl.db from event module. Always instantiate :EVENT1 to 14 – you want the spares. See timing block diagram in sharepoint to find mapping between triggered device and TTB/front panel ports. See EVG event display to find event code numbers once you know how devices are to be triggered. One device can be triggered by multiple event codes (ie, BPMs) though not event codes on the same time slot. Enable IRQ if you want records processed on event. Matching display = tools/edm/display/event/evrTriggerDiags.edl Record Reference: ystems/timing/globalEventV3.htm

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 Pattern Databases One Pattern Record Group per IOC: Provides beam/BSA/destination/timeslot information on the current time slot + next 3 timeslots. They also provide generalTime records. All apps (including EVG IOC) should load this one. Use evrPatternAll.db from the event module. Matching displays = tools/edm/display/event/evrPatternDiags.edl and tools/edm/display/event/generalTime.edl

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 Pattern Databases - cont One Pattern Event Record Group per IOC: Provides event records that will fire if IRQ is enabled on an event code. Also provides delay from the fiducial for each event code (used by the trigger database). Must be loaded with evrPatternAll.db. Use evrEventAll.db from the event module. Matching display = tools/edm/display/event/evrEventDiags.edl

Stephanie Allison LCLS Controls Software Meeting Dec 6, 2007 Trigger Database One Trigger Record Group per triggered device: Provides more user-friendly interface for setting delays, pulse widths, polarities than comes with evr.db. Comes with matching CW configuration. Use evrDevTrig.db, evrDevTrig.cwConfig, and evrIocTrig.cwConfig from the event module. Must be consistent with event codes selected in the EVR databases. See timing block diagram in sharepoint to find mapping between triggered device and TTB/front panel ports: ment%20Storage/01%20- %20LCLS%20Systems/electronbeamsys/controls/Share d%20Documents/Timing/TIMING%20System%20BD.pdf Matching display = tools/edm/display/event/evr_dev_diags.edl