Support #19129
Can MCRBCC and the driver for G:BCYCLE monitor for sequencer problems?
Start date:
02/26/2018
Due date:
% Done:
0%
Estimated time:
Description
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.
History
#1 Updated by Richard Neswold almost 3 years ago
- Status changed from New to Assigned
This isn't a CAMAC front-end issue. :D
#2 Updated by Richard Neswold almost 3 years ago
- Tracker changed from Feature to Support
- Project changed from CAMAC to Front-end Group
- Category set to Front-end Issue
Move out of CAMAC project and into a general area (until an MCRBCC
project is created in Redmine.)