[dsg-svt] Latching on ambient humidity

[Peter Bonneau]

For troubleshooting humidity sensors: 

1) After a system trip and before resetting, we need screen captures of the "Interlock Status and signal monitoring" and the "Raw data monitoring" tabs of the Hardware Interlock Monitoring System user interface. We need to know which signal is causing the tripping. 

2) Negative readings from a humidity sensor are most often caused by faulty cabling or the sensor. 
To keep running the detector, disable the sensor in the user interface which tripped the interlock until this can be checked in the hall. 






To check the Mpod crate controller and the interlock inhibit signal, we posted this troubleshooting procedure on 10/17/2017: 





1) To check the hardware interlock Mpod logic, you can try disabling the inlet and outlet coolant flow interlock enables. After disabling and at the next trip event, take screen captures of the "Interlock Status and signal monitoring" and the "Raw data monitoring" tabs of the Hardware Interlock Monitoring System user interface. 




2) To check the Mpod crate controller input inhibit signal, you can try turning on the Mpod interlock system override key switch on the cRio crate. This effectively shorts all the Mpod crate enables to the +5V supply. 



From: "Yuri Gotra" <gotra at jlab.org> 
To: "dsg-svt" <dsg-svt at jlab.org> 
Sent: Monday, November 6, 2017 9:37:36 AM 
Subject: [dsg-svt] Latching on ambient humidity 

There is an issue with error readings from region humidity sensors 
(negative readings) which have to be handled. These errors cause 
latching and causing HV channel output inhibits. The issue with inhibits 
has been seen over the past weeks. For now I lowered the low limit. 
Labview GUI needs to be modified to handle bad readings. Thank you 


_______________________________________________ 
dsg-svt mailing list 
dsg-svt at jlab.org 
https://mailman.jlab.org/mailman/listinfo/dsg-svt 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_svt/attachments/20171106/23a866f9/attachment-0002.html>