1 / 16

BETS Software for LBDS

BETS Software for LBDS. Data Acquisition & Logging LBDS Technical Audit - 28.01.2008 CERN - AB/BT/EC - N.Magnin. BETS - Software requirements. Roles of Beam Energy Tracking System software are: Controlling and Monitoring of BETS hardware. Acquiring of BETS hardware data.

rodriguezrobert
Download Presentation

BETS Software for LBDS

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. BETSSoftware for LBDS Data Acquisition & Logging LBDS Technical Audit - 28.01.2008 CERN - AB/BT/EC - N.Magnin

  2. BETS - Software requirements • Roles of Beam Energy Tracking System software are: • Controlling and Monitoring of BETS hardware. • Acquiring of BETS hardware data. • Logging of BETS hardware data to database. • Recording of BETS hardware data history, and its Publishing for XPOC.

  3. BETS - System Components

  4. BETS - Acquisition Hardware • 2 identical VME crates for 2 beams • BETS VME crate: • 2 redundant PSU • 2 BEM VME cards • 14 BEI VME cards • 1 BEC VME card • 1 CPU VME card • 1 CTRP PMC card • Receives dump trigger.

  5. BETS - Software Overview Development involves: • Drivers andAPI libraries. • FESA server. • BETS Explorer Java control application. • Configuration of AB/CO services.

  6. BETS - Drivers + API libraries • Drivers for LynxOs developed with driverGen AB/CO tool. • Checking whether hardware and firmware versions are compatible with driver. BETS common VME registers set: • C++ API libraries that ease the use of BETS hardware. • Performes hardware access using AB/CO DAL library. • Implements all register-level functions. • Has no impact on BETS, only rearming is possible. • Applications check whether firmwareis compatible with target system. • Upgrading the firmware using VME interface is not possible.

  7. BETS - FESA Server Composition of 4 FESA classes Deployed as shared-server-split. • 1 Shared-Server process • 4 Server libraries • Access to CMW • Low priority • 1 Real-Time process • 1 RT library • Access to Hardware • High priority • 4 Shared-Memory segments • 4 Device data

  8. Beam 1 (FEC: cfv.ua63.mkdbets) 1 BetsCtrlLbds instance MKD.UA63.MKCB.B1 27 BetsBei instances MKD.UA63.MKCBI.[A..O]B1 MKBH.UA63.MKCBI.[A..D]B1 MKBV.UA63.MKCBI.[A..F]B1 MKQ.UA63.MKCBI.B1 MSD.UA63.MKCBI.B1 2 BetsBem instances MKD.UA63.MKCBM.IB1 MKD.UA63.MKCBM.RB1 1 BetsBec instance MKD.UA63.MKCBC.B1 Beam 2 (FEC: cfv.ua67.mkdbets) 1 BetsCtrlLbds instance MKD.UA67.MKCB.B2 27 BetsBei instances MKD.UA67.MKCBI.[A..O]B2 MKBH.UA67.MKCBI.[A..D]B2 MKBV.UA67.MKCBI.[A..F]B2 MKQ.UA67.MKCBI.B2 MSD.UA67.MKCBI.B2 2 BetsBem instances MKD.UA67.MKCBM.IB2 MKD.UA67.MKCBM.RB2 1 BetsBec instance MKD.UA67.MKCBC.B2 BETS - FESA Instances = 60 FESA instances (+2 for control)

  9. BETS - FESA Main Properties BetsCtrlLbds class: • Statusget the system’s status and operating mode. • Settingset the system’s operating mode. • ReArmrearm the system in case of tracking error. • Resetreset the system in case of hardware error. BetsBem, BetsBei, BetsBec classes: • Statusget the device’s status and operating mode. • CardInfoget info about the VME card version. • Tablesget the lookup table data (BEM and BEI only). • Loggingget the data to log. • PmBufferget the recorded XPOC buffer.

  10. BETS - FESA Main Modes • RECORDING: • Recording of data at ~50 Hz. • Logging of data at ~1 Hz. • Beam injection permitted. • TRIGGERED_OK: • No problem detected. • Beam injection not permitted. • TRIGGERED_ERROR: • Tracking problem detected. • Beam injection not permitted.

  11. BETS - Logging Data Data logged at ~1 Hz to Measurement & Logging database: • BEM • Time stamp [ns] • BEM & BEAs statuses • BEA RAW data (16 bits) • BEM current [KA] • BEM energy [GeV] • BEI • Time stamp [ns] • BEI & BEA statuses • BEA RAW data (16 bits) • BEI voltage/current [KA/KV] • BEI energy [GeV] • BEM ref. energy [GeV] • BEC • Time stamp [ns] • BEC statuses

  12. BETS – XPOC Data Data continuously recordedat ~50 Hz in a circular buffer of a size of 1024 (~20s), saved to SDDS files after each dump : • BEM • Dump time stamp [ns] • Card info Arrays: • Time stamps [ns] • BEM & BEAs statuses • BEA RAW data (16 bits) • BEM current [KA] • BEM energy [GeV] • BEI • Dump time stamp [ns] • Card info Arrays: • Time stamps [ns] • BEI & BEA statuses • BEA RAW data (16 bits) • BEI currents/voltages [KA/KV] • BEI energy [GeV] • BEM ref. energy [GeV] • BEC • Dump time stamp [ns] • Card info Arrays: • Time stamps [ns] • BEC statuses

  13. BETS – Statuses & Alarms Tracking error: • Status = OK • Alarm = WARNING “BEx card has generated a dump.” Must use the ReArm property. Hardware error: • Status = ERROR • Alarm = ERROR “BEx card hardware access error.” Must use the Reset property.

  14. BETS Explorer application • This application shows: • The tree of all BETS FECs and devices. • Status and Mode of all IPOC devices. • Controls pop-up menu for the selected device or FEC. • Last logged values for the selected device.

  15. BETS – Logging data example 24 hours logging of BEI for kicker MKD-A beam 1. Energy Ch1 [GeV]

  16. BETS – XPOC data example XPOC buffer of BEI for kicker MKD-A beam 1. Energy Ch1 [GeV]

More Related