[Dsg-hallb_magnets] TR817F2 at 325K, LV cRIO restarted

[Tyler Lemon]

Hello, 

This morning, Cerenox TR817F2 was at 325 K. Torus LV cRIO has been restarted to correct error since the automatic recovery is not working. 

Looking at MyaViewer (plot is attached), there are a few times where the Cerenox reading dropped to ~15 K before jumping to 325 K (seen as vertical lines on plot). These vertical lines have not been seen when other Cerenoxes have jumped to 325 K. The vertical lines could mean that the LV cRIO is trying to reinitialize the Cerenox, but there is something preventing the Cerenox from fully recovering after just running the start-up algorithm for it. 

I will continue to look at what changes can be made to the LabVIEW to prevent a sensor from maintaining 325 K. 

All Cerenoxes that have had the 325 K error have been in either LV Chassis 1, LV Chassis 2 or LV Chassis 4. These three LV Chassis all read into the LV cRIO through the same NI-9870 module. In the mean time, swapping Torus LV cRIO module 1 for a spare would eliminate the possibility that the cRIO module in-use is bad. Where would the spare be kept? 

Best regards, 
Tyler 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_magnets/attachments/20170220/cbb111c2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: TR817F2 at 325 K 2017-02-20.PNG
Type: image/png
Size: 54074 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_magnets/attachments/20170220/cbb111c2/attachment-0001.png>