Veto Logic Review

Recently it has become apparent that veto logic through all the PLC systems needs to be reviewed. I think the initial documentation for the PMPS did not really focus on veto logic and so it wasn't consistently implemented. Additionally, many of the veto devices have only recently been added.

PLC Project List

• xrt-optics
• lfe-optics
• lfe-vacuum
• tmo-optics
• tmo-vac
• tmo-motion
• rix-optics
• rix-vacuum
• rix-motion

Notes

• lfe-optics has no components downstream of a stopper
• tmo optics needed m2k4 and m3k4 vetoed, and an mk1k1 veto for the entire line. the preemptive systems was not in use. Redeployed the code with an online change.
• reviewed tmo vac with Allen D Pai, did a find all on ffo1, 2, 3, 4 and verified everything using ffo2 is supposed to be vetoed by m1k1 and st3k4 and arbiter2 is also vetoed by st3k4 and m1k1 and is only being used by stuff downstream of st3k4.
• Allen D Pai confirmed all devices in tmo-motion are downstream of st3k4 and st3k4 is being used a veto for the reactive a preemptive systems.
• Jyoti, Joshi Margaret Ghaly and I checked optics and motion and confirmed preemptive and reactive systems are being vetoed properly.

DG2 STP 1 and XRT-M2 Out Fault

eV Bitmask Failsafe Did Not

Bill Schlotter reported that during some beamtime on the K line the undulators were set to an unusually high K value. This put them out of our current setting for active range (PMPS Photon Energy) so no seed undulator could be found, resulting in a calculation for eV of 0. The actual effective eV was around 600eV. The photon energy bitmask was then set to 2#0000_0000_0000_0001 which was inaccurate and problematic as it circumvented some faults. To fix this issue I changed the bitmask logic so a value of zero will result in the current photon energy bitmask being set to 2#1111_1111_1111_1111.