1 / 9

BPM software and longest acquisitions

BPM software and longest acquisitions. L. Jensen BE/BI/SW. LHC Optics Measurement review – 17/6/2013. Outline. Simplified control system layouts BPM Electronics and front-end software LS1 objectives Answers to specific questions Conclusions. Control system overview.

aideen
Download Presentation

BPM software and longest acquisitions

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. BPM software and longest acquisitions L. Jensen BE/BI/SW LHC Optics Measurement review – 17/6/2013

  2. Outline • Simplified control system layouts • BPM Electronics and front-end software • LS1 objectives • Answers to specific questions • Conclusions

  3. Control system overview LHC IQC GUI (L. Drosdal OP) LHC Multi-Turn GUI (V. Kain OP) CMW CMDS SDDS PM-data LHC BPM Concentrators C. Roderick, L. Burdzanowski (BE/CO) Turn-by-turn Bunch-by-bunch IQC (B1 pt2, B2 pt8) Fixed configuration • CMW • Settings • Acquisitions (all) FE B1 / 1 (H/V) FE B2 / 1 (H/V) FE B1 / 2 FE B2 / 2 FE B1 / 32 FE B2 / 32

  4. LHC BPM electronics DAB64x firmware Asynchronous BPM WBTN INT ADC FIFO + Orbit Synchronous capture (bunch-by-bunch): • Bunch selection B (N slots selected) • Consecutive turn selection T • Hard limit: N*T <= 128k => (data/BPM –> never used) • Single hardware (buffer) implementation (IQC/: • Distributed trigger selection via BST: • Injection (warning) => pre-pulse from RF for IQC • Other (elsewhere in cycle) => MTG timing event per beam (1msec frame) Orbit Post-mortem Capture Turn clock (slot delay) 40MHz clock (25ns) (phase delay) Sensitivity selection Synchronous

  5. LHC BPM synchronous modes 2) Turn slot delay 1) ADC phase delay • Beam synchronous setting-up “phase-in” • Some problems seen in the past (calibration sequence) now believed to be resolved (delays should not move) • Now work without automatic TDC corrections • Special cases still causing problems (phase/slot)? • Values in LSA settings DB (reload possible) Bunch in slot 101 Bunch slots (3564) TDC e Start of turn (= end of abort-gap) Time (25nsec)

  6. LHC BPM procedure • Bunch and Turn selection • Data size = 10kB + (B*T)*0.4kB (per front-end) • Normal: single bunch (B=1), T = 3000 => 1Mbytes (per front-end) • 32 front-ends => 32 Mbytes total data size / beam (files) • Desired (Rogelio): 10000 turns -> ~100 Mbytes / beam • Maximum (128k bunches) => 1.3 Gbytes / beam • External BST trigger to all acquisition cards (a few turns delay from MTG event to start) • Acquisition finish: • Data read-out • Raw to position normalisation (see Eva’s presentation) • Calculation of turn-by-turn data (from bunch-by-bunch) • Data published to concentrators

  7. LS1 objectives (software) • Upgrade front-end systems to Linux • 4 * gain in available memory • 5 * gain in Ethernet speed (new Gbit switches) • Redesign software layers (FE->GUIs) • Take into account what we’ve learnt since 2008 • Closer look at use-cases (specifications)

  8. Answers to specific questions 1) DOROS electronics 2) Current BBQ and/or ADT BPMs See Marek’s talk later this afternoon 3) Additional data corrections for turn-by-turn data (X/Y) • See Eva’s talk 4) Shift of data in bunch-by-bunch mode • To be looked into with BE/CO – likely difficult to test without beam

  9. Conclusions • Trying to cover injection oscillation and optics with same mode -> complications • Firmware solutions? • Updated CPUs with compatible firmware expected to relieve some limitations • LHC turn-by-turn data mechanism to be studied • Understand usage • Identify limits to safe operation • Larger-scale tests to be planned during LS1 and following beam restart

More Related