[Dsg-halla_ecal] [Revised Logentry] ECal controls temperature readout frozen for zones 17-32 since Saturday swing. Alarms not working

jonesdc at jlab.org jonesdc at jlab.org
Mon May 19 07:20:03 EDT 2025


Logentry Text:
--
At 6AM (Mon) I found that the heater thermocouples were stalled on zones 17-32. All temperatures appear to be stuck at their last read value before the event that stalled the readout. This was different from last time when they all went to 0. This meant that any zones that were under their set temperatures continued to output and all others simply turned off I set the controls to manual mode until I could get in to deal with it. The ECal_Controls_Heartbeat variable that monitors these things which I had set to start alarming at 35 was above 10000 and yet I had received no notification from shift crews. I checked the alarm HIGH and HIHI setpoints and they were all 0. Here is where I recorded setting them a few weeks ago https://logbooks.jlab.org/entry/4370281. Although this alarmed me, I was further horrified to see that all my safety alarm setpoints were again ALL set to 0. Here is where I set all of them https://logbooks.jlab.org/entry/4369894. I need to find out why this is
  happeni
 ng and how I can set the default values, because it is a real safety concern. I rely on these alarms to alert me if something is wrong. Anyway, a good part of the detector was well below its set temperature over the weekend. We will have to see how it affected the gains.
I rebooted the cRIO power supply outlet and all readouts returned to working again.

---

This is a plain text email for clients that cannot display HTML.  The full logentry can be found online at https://logbooks.jlab.org/entry/4378357
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-halla_ecal/attachments/20250519/7e132590/attachment.htm>


More information about the Dsg-halla_ecal mailing list