LCLS Event System Outline HW Block Diagram Timing

LCLS Event System Outline HW Block Diagram Timing Requirements Time Lines EVG to EVR Data Transfer Beam-Synchronous Acquisition and Control Issues/Comments Status/To-Do 14 June 2006 LCLS Event System 1 Stephanie Allison saa@slac. stanford. edu

HW Block Diagram Modulator Triggers Existing Control System 360 Hz Fiducial RF Timing Beam Rate, Beam Path PNET Trigger Delays and Pulse Widths, Event Codes per Output Channel Access Trigger P Master N EVG E T IOC EVG Fan Out E A V D R C Future MPS E V R LLRF IOCs Timing Pattern, Timestamp, Event Codes 119 MHz RF Clock Beam Rate, Beam Path EVG Fan Out BPM IOCs Camera IOCs Trigger P/A Acq & Cntrl Down stream EVG IOC EVG Fan Out To Downstream EVRs Camera 14 June 2006 LCLS Event System 2 Stephanie Allison saa@slac. stanford. edu

Timing Requirements Maximum trigger rate Clock frequency Clock precision Coarse step size Delay range Fine step size Max timing jitter w. r. t. clock Differential error, location to location Long term stability 14 June 2006 LCLS Event System 3 360 Hz 119 MHz 20 ps 8. 4 ns ± 20 ps >1 sec 20 ps 2 ps rms 8 ns 20 ps Stephanie Allison saa@slac. stanford. edu

Event Time Line – 120 Hz Beam 360 Hz Fiducial F 0 Time (msec) 0 Beam Kly Standby F 1 2. 8 Timing data for next Beam pulse LCLS Event System F 3 8. 3 B 0 S 0 BPM Calib 14 June 2006 F 2 5. 6 F 5 11. 1 13. 9 B 1 S 1 CX 0 T 1 F 4 CY 0 T 1 a CX 1 T 1 b 4 T 2 CY 1 T 2 a F 6 F 7 16. 7 19. 4 B 2 S 2 CX 2 T 2 b Stephanie Allison saa@slac. stanford. edu T 3

Event Time Line – 1 Beam Pulse (B 1) Record processing (event, intr) Post-Beam Acq – BPM, Beam Toriod, PMT, Camera B 1 Timing Data in records, waiting to be used Laser Control Kly B 2 Timing Standby Data Received Fiducial F 3 Time (msec) 14 June 2006 LCLS Event System 0 1 -a 1 -b 5 B 1 1 1+c S 1 1+d Stephanie Allison saa@slac. stanford. edu T 2 1+e

EVG-to-EVR Data Transfer (Dayle Kotturi) 14 June 2006 LCLS Event System 6 Stephanie Allison saa@slac. stanford. edu

EVG-to-EVR Data Example (Dayle Kotturi) 14 June 2006 LCLS Event System 7 Stephanie Allison saa@slac. stanford. edu

Trigger from Event Code (Dayle Kotturi) 14 June 2006 LCLS Event System 8 Stephanie Allison saa@slac. stanford. edu

Event Applications Beam-Synchronous Control: rules and algorithm for creating EVG trigger sequences on a pulse-topulse basis Algorithm change on-the-fly based on user requests Single-Shot vs continuous beam pulses – enforce minimum delay between single-shot requests Bunch length measurement Rate limit Beam destination MPS rate limit and destination requests Send out calibration, standby, and software triggers during non-beam time slots 14 June 2006 LCLS Event System 9 Stephanie Allison saa@slac. stanford. edu

Event Applications (cont) Beam-Synchronous Acquisition: mechanism for users to request pulse-by-pulse acquisition across multiple IOCs: Single-shot or multiple contiguous pulses Include or exclude a pulse from resultant waveforms based on information in the timing pattern for that pulse Can be implemented by either data mining of large data/timing-pattern arrays …or use the timing system to trigger data copy to special records based on preset conditions, requires reserve/release of special records 14 June 2006 LCLS Event System 10 Stephanie Allison saa@slac. stanford. edu

Immediate Issues/Comments EVG RF input divider – new circuit added to EVG Do we need EVR with RF recovery (EVR with clock)? 119 Mhz availability throughtout? Fiber plant: Match network bulk cable where possible Where is single mode fiber needed? Between fanouts? To EVR w/RF recovery? How much EVR daisy-chaining can we do? Daisy chain vs tap to split No plans for redundancy TTL triggers – long trigger cables need design Not enough testing has been done Schedule……. 14 June 2006 LCLS Event System 11 Stephanie Allison saa@slac. stanford. edu

Future Issues Modulator triggers on existing control system – how to rate-limit from new system Handling non-LCLS beams – add more beampulse-dependent info (ie, bunch charge) to timing pattern for IOC apps How to upgrade PMC-EVR firmware 14 June 2006 LCLS Event System 12 Stephanie Allison saa@slac. stanford. edu

Status (Dayle Kotturi) Received the EVG/EVR 200 series VME hardware (which sends up to 2 K data buffer) Received the EVR 200 series PMC module Adapted driver and device support to: send the PNET data buffer (measured 66 µs transfer) be OSI (running on mvme 6100, RTEMS 4. 7) with help from Till Straumann, Eric Bjorklund, Timo Korhonen, Jukka Pietarinen and Bob Dalesio 14 June 2006 LCLS Event System 13 Stephanie Allison saa@slac. stanford. edu

Status (cont) Stephanie Allison and Mark Crane coming up to speed Test stands for HW folks not yet ready Rack/cable design for injector/BC 1 well underway Procurement underway 14 June 2006 LCLS Event System 14 Stephanie Allison saa@slac. stanford. edu

To-Do Finish PMC-EVR driver and test (share PMC-EVR and VME-EVR driver as much as possible) EVG sequence RAM programming at 360 Hz EVG rules and algorithm definition for Jan commissioning Add support for EVR timing pattern data records (in place well before next beam pulse) Jitter testing Interface with other subsystems needs review Commissioning test plan 14 June 2006 LCLS Event System 15 Stephanie Allison saa@slac. stanford. edu