1 / 7

Requirements of the SwissFEL Timing

Requirements of the SwissFEL Timing. Frame rate requirements. Increase the event clock to about 150 MHz (currently 125 MHz not sufficient). Precisely 142.8 MHz required. [Rocket IO speed of greater than 2.5 GHz] Preliminary discussions with MRF has started

oreynolds
Download Presentation

Requirements of the SwissFEL Timing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements of the SwissFEL Timing

  2. Frame rate requirements • Increase the event clock to about 150 MHz (currently 125 MHz not sufficient). • Precisely 142.8 MHz required. [Rocket IO speed of greater than 2.5 GHz] • Preliminary discussions with MRF has started • Technological challenges on low jitter transmission according to Jukka

  3. EVG: a better Sequencer • SwissFEL will be operated at 100 Hz rep (seq. trigger rate) • From our experience in injector test facility we know that: • we have to maintain several event sets at different rates, consequence: • : every sequence pattern is different • Do less frequent sequencer programming of the EVG by IOC (CPU), delegate more to EVG

  4. EVG: proposal for a new sequencing

  5. EVG: other requirements … • It must be possible to delay the internal, external or AC synced sequencer trigger with much higher resolution at least at microsecond level. This will replace the currently existing phase shifter which delays the sequence trigger generated by the AC input trigger with resolution of 0.1 ms.

  6. Other requirements … • We most probably will use backward links: • some applications already are in sight • some simple low level protocol is required if the to identify data sender (EVR). Notion of protocols already exists in mrfDataBuffer driver has to be looked at more carefully. • Diagnostics on distribution network: • Some features like readout of power levels of the in/out ports especially at fanouts • temperature, etc • or any kind of information which releases us from going to the distribution locations for manual/visual checking. Such information could be read via network interface or bus interface e.g. VME, etc.

  7. Other requirements … • EVR: • Not much new major features needed but a minor.. • trigger the same pulser from 2 (or more) events with independent local delays

More Related