LCLS Event System - Software

Transcription

1 LLS vent System - Software Software Requirements vent Generation (VG) vent Receiver (VR) Beam Synch Acquisition (BSA) PIS Displays VG IO Diagnostics, vent ode Setup, BSA vent Definitions (DF) VR IO Diagnostics, VR Hardware, vent ode Diagnostics, Device Trigger Setup Oct 21, 2008 M Operations Meeting Stephanie Allison saa@slac.stanford.edu

2 Modulator Triggers Hardware Block Diagram 2007 ommissioning xisting ontrol System RF Timing Future MPS Beam Path rate 360Hz Fiducial 119MHz lock Beam Rate, Beam Path Timing V G F A N 1 F A N 2 P N T I O Acq and BPM F alibration Triggers BPM rates V R I O Acc and Standby Triggers LLRF rate V R 1 Fiber Distribution: Timing Pattern, Timestamp, vent odes PADs and PAs V R 2 V R 3 I O Trigger TORO F Triggers Triggers Laser Steering rate F A N 3 V R 1 A M 1 I O 1... V R 8 A M 8 I O 8 Toro Farc rate F A N 4 V R I O Profile Monitor rate V R 1 A M 1 A M 2 I O 1 V R 4 A M 7 A M 8 I O 4 Oct 21, 2008 M Operations Meeting Stephanie Allison saa@slac.stanford.edu

3 vent System Requirements vent Generator IO: Send out proper event codes at 360Hz based on: PNT pattern input (beam code and bits that define beam path and other conditions) Add LLS conditions such as BPM calibration on off-beam pulses, diagnostic pulse etc. Near future event codes also based on new MPS and user input for kicker control and single-shot Send out system timestamp with encoded pulse ID from PNT Send out PNT pattern to be used by SL-aware IOs Beam-synchronous acquisition management (more later) Oct 21, 2008 M Operations Meeting Stephanie Allison saa@slac.stanford.edu

4 vent System Requirements, cont vent Receiver IO: 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 VG in the event pattern (more later) Perform beam-synchronous acquisition for the SLaware IO based on the PNT part of the event pattern Process pre-defined records when specific event codes are received Oct 21, 2008 M Operations Meeting Stephanie Allison saa@slac.stanford.edu

5 vent Time Line 120 Hz Beam 360Hz Fiducial Time (msec) Beam F0 F1 F2 F3 F4 F5 F6 F B0 B1 B2 Kly Standby S0 S1 S2 X2 BPM alib X0 Y0 X1 Y1 Oct 21, 2008 M Operations Meeting Stephanie Allison saa@slac.stanford.edu

6 VR IO Time Line 1 Beam Pulse (B0) Record processing (event, interrupt) vent Timestamp, pattern records, and BSA ready Fiducial vent Received Triggering vent odes Start nd Hardware Triggers Receive pattern for 3 pulses ahead Kly Accel Acq Trigger Beam Kly Standby Fiducial Fiducial F0 0 ~ ~500 Time (usec) 1023 B0 F Oct 21, 2008 M Operations Meeting Stephanie Allison saa@slac.stanford.edu

7 vent System Requirements, cont Beam Synchronous Acquisition (BSA): Acquire all beam-dependent scalars across multiple IOs on the same pulse over multiple pulses of a certain kind (not just x-pulses-in-a-row) up to 120Hz. Acquire up to 2800 values per scalar in one acquisition request. ach value of the 2800 values can be an average of up to 1000 values. ach acquisition request can specify: Beam code (defines project, 1 = LLS) Machine conditions of interest rate, TS, permits, etc Provide constant 1HZ beam-synchronous data for channel archiver and displays Oct 21, 2008 M Operations Meeting Stephanie Allison saa@slac.stanford.edu

8 BSA IO Data Gathering A lient DF Setup Timing rate I O P N T V G BPM F Triggers Data DF Flags, Pattern, etc Data gathering part consists of the following actions: BSA event definition (DF) setup and start request done on the VG IO. 360hz checking on the VG IO with user notification when finished. 360hz requests (acquisition control) sent by the VG IO to all VR IOs via fast fiber optic link. Data checking, averaging, and array update per scalar record per request on the VR IOs. Data on VR IO must be available within 7.3 msec after beam or it will be lost, even when beam is less than 120hz. DF will finish with arrays that are not complete if this time budget cannot be met. For an acquisition at full beam rate (ie, 30hz), if data is acquired at a lower rate (ie, 10hz), the array will not be complete. Use rate-limit bits as-needed when setting up the DF. Implementation is all PIS record-based. V R I O BPM rate BSA Data A lient Oct 21, 2008 M Operations Meeting Stephanie Allison saa@slac.stanford.edu

9 VG IO Global vent Display More to come for kicker control, MPS interface, and pulse stealing

10 VG IO Pattern Diagnostics ommon rrors: MPG_IPLING, TIMOUT, PULSID_NOSYN PVs update at 0.5hz (on mod720 bit) For BSA

11 VG IO vent odes

12 VG IO ondition Masks for vent ode 140 For now, masks are displayed as bit masks need name for each bit!

13 VG IO All DF Diag Display Put new app name in reserve record edefreserve sequence will assign next available DF number 15 user-defined requests at one time, is this enough? Issue apps that crash before freeing. alan app is using DF 12 until freed by the app alan can do multiple acqs System DFs are reserved and setup at VG IO boot and never freed.

14 VG IO DF Diag Display Turn ON when ready. VG IO 360Hz event task will turn OFF when finished. Turn back ON to flush and restart the acq. Set machine conditions values acquired only on pulses where ALL inclusion conditions are true AND NO exclusion condition is true Beam code describes project, 1 = LLS (0=any beam code good for testing) Define # in each average, # measurements, severity at or above which data is not included in average. Forever option used by system DFs. Push FR to free this DF number. Name and user will be blanked out.

15 VG IO DF Mask Diag Display ondition (bit) names come from the SL Database (PNBN) and ordered alphabetically in new records by the edefmask sequence. hoose conditions that define the pulses of interest. Only pulses with these conditions will provide values to the acquisition.

16 VR IO Sector vent Display

17 ommon rrors: MPG_IPLING and TIMOUT PVs update at 0.5hz (on mod720 bit) Pattern Pipeline (but no TS 4!) For BSA Missing Pattern Interrupt xtra Interrupts Missing Pattern Interrupt Fiducial Processing Too Long

18 VR IO General Time Diagnostics Display epicstimegeturrent evrtimeget OK epicstimegetvent (Record Timestamps) evrtimegetsystem vent System problem (pulse ID set to invalid) General Time will transition between different time providers without going backward in time

19 VR IO VR Hardware Transition module uses 14 regular triggers Front panel uses extended delay triggers (only 3 for PM VR) Fiber connection status (from VR fanout module), polled at 0.5hz

20 All BPM VRs first 7 channels for data, last 7 channels for calibration: Data acquired at 360hz (event code 20 on TS 2,5; event code 30 on TS 3,6; event code 40 on TS 1,4) where only TS 4 will produce X/Y/TMIT record updates if the pulse has beam. alibration on TS 2,3,5,6 only. See event display for event code description nabled so that beam rate is calculated Note: nabling IRQ causes interrupts/task switches at the rate of the event code receipt ( watch PU performance after enabling)

21 VR IO vent ode Diagnostic Display Delay from fiducial vent code description Standby (base rate) beamindependent events Rate calculated only if IRQ is enabled (fiducial IRQ automatically enabled on all IOs) MJB requests all standby event codes be replaced by 36 event codes using the same delay (like SL)

22 VR IO Device Trigger Setup Display

23 VR IO Device Trigger Diagnostic Display

24 VR IO Device BSA Diagnostic Display opied from DF diag display Last averaged values RMS zero when # avg is 1 Various inputs/outputs to averaging ssub record Last 100 values of value