Download presentation
Presentation is loading. Please wait.
Published bySage Hammell Modified over 9 years ago
1
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 1 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
2
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 2 PNET Existing Control System 119MHz RF Clock Trigger Delays and Pulse Widths, Event Codes per Output Channel BPM IOCs EVREVR ADCADC LLRF IOCs HW Block Diagram IOC Master EVG PNETPNET Timing Pattern, Timestamp, Event Codes EVREVR Channel Access Beam Rate, Beam Path Trigger 360Hz Fiducial IOC Down stream EVG To Downstream EVRs Beam Rate, Beam Path Future MPS Camera IOCs EVREVR Trigger EVG Fan Out Camera EVG Fan Out EVG Fan Out RF Timing Modulator Triggers P/A Acq & Cntrl
3
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 3 Timing Requirements Maximum trigger rate 360 Hz Clock frequency 119 MHz Clock precision 20 ps Coarse step size 8.4 ns ± 20 ps Delay range >1 sec Fine step size 20 ps Max timing jitter w.r.t. clock 2 ps rms Differential error, location to location 8 ns Long term stability 20 ps
4
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 4 Event Time Line – 120 Hz Beam F0F1F2F3F4F5F6F7 02.85.68.3 11.113.916.719.4 360Hz Fiducial Time (msec) B0B1B2Beam S0S1S2Kly Standby CX0CX1 CX2 BPM CalibCY0CY1 T1T1aT1bT2 T2aT2bT3 Timing data for next Beam pulse
5
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 5 Event Time Line – 1 Beam Pulse (B1) F3 0 Fiducial Time (msec) B1 S1 Acq – BPM, Toriod, PMT, Camera T2 1 1-b 1+d Laser Control 1-a Beam Post-Beam Acq Kly Standby 1+c 1+e B2 Timing Data Received Record processing (event, intr) B1 Timing Data in records, waiting to be used
6
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 6 EVG-to-EVR Data Transfer (Dayle Kotturi)
7
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 7 EVG-to-EVR Data Example (Dayle Kotturi)
8
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 8 Trigger from Event Code (Dayle Kotturi)
9
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 9 Beam-Synchronous Control: rules and algorithm for creating EVG trigger sequences on a pulse-to- pulse 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 Event Applications
10
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 10 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 Event Applications (cont)
11
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 11 Immediate Issues/Comments EVG RF input divider – new circuit added to EVG Do we need EVR with RF recovery (EVR with clock)? 119Mhz 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…….
12
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 12 Future Issues Modulator triggers on existing control system – how to rate-limit from new system Handling non-LCLS beams – add more beam- pulse-dependent info (ie, bunch charge) to timing pattern for IOC apps How to upgrade PMC-EVR firmware
13
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 13 Status (Dayle Kotturi) Received the EVG/EVR 200 series VME hardware (which sends up to 2K 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 mvme6100, RTEMS4.7) with help from Till Straumann, Eric Bjorklund, Timo Korhonen, Jukka Pietarinen and Bob Dalesio
14
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 14 Status (cont) Stephanie Allison and Mark Crane coming up to speed Test stands for HW folks not yet ready Rack/cable design for injector/BC1 well underway Procurement underway
15
Stephanie Allison LCLS Event System saa@slac.stanford.edu 14 June 2006 15 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
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.