Can MCRBCC and the driver for G:BCYCLE monitor for sequencer problems?
Occasionally, the device G:BCYCLE gets into a state where it starts continuously returning 57 -75 (sequencer problem) errors. This happened over the weekend with the big power glitch. Every time I have seen it, it is easily rectified with a reset to G:BCYCLE. Can the front-end monitor for this condition and do a self reset after some appropriate delay?
G:BCYCLE is crucial to the Beamtrail collection process. When bcycle is in error, beamtrail cannot succeed.