[Dsg-ft] [New Logentry] FTT condensation interlock tripped

[Raffaella De Vita]

Hi Amanda,
I think keeping the sensor disabled will be enough for now.
Thanks for the explanation about the rest button. 
Best regards,
	Raffaella

> On 21 Sep 2018, at 15:18, Amanda Hoebel <amandah at jlab.org> wrote:
> 
> Hi Raffaella,
> 
> The sensor measures condensation by conductivity. If the sensor comes in contact with anything conductive, such as a metal surface, it will trip. We can disconnect the sensor until it is needed or keep the interlock disabled.
> 
> Regarding the reset, please press and hold the button down until the tripped interlock clears. The reset response is slow sometimes, possibly due to high network traffic / GUI / EPICS response time. We don't see the reset delay with the LabVIEW interface. We will look into making the EPICS reset more robust.
> 
> Regards,
> Amanda
> 
> 
> From: "Eugene Pasyuk" <pasyuk at jlab.org>
> To: "raffaella devita" <Raffaella.Devita at ge.infn.it>
> Cc: "dsg-ft" <dsg-ft at jlab.org>, amandah at jlab.org
> Sent: Friday, September 21, 2018 7:23:43 AM
> Subject: Re: [New Logentry] FTT condensation interlock tripped
> 
> I somehow managed to reset this latched interlock. I turned chiller back on.  
> 
> -Eugene
> 
> From: "Raffaella De Vita" <Raffaella.Devita at ge.infn.it>
> To: dsg-ft at jlab.org, amandah at jlab.org
> Cc: pasyuk at jlab.org
> Sent: Friday, September 21, 2018 1:53:19 AM
> Subject: Fwd: [New Logentry] FTT condensation interlock tripped
> 
> Hi Amanda,
> As you can see from the attached logbook entry there was a trip of the ft interlocks caused by the condensation sensor that was added last year. The GUI shows under/over limit from what is hard to understand what’s wrong with it. The sensor is actually not installed at the moment but is located in the cRio rack under the crate. Since it is not used, we can disable it but when I did, the “reset latched errors” button still didn’t clear the errors. 
> Can you check?
> For now we would like to keep the sensor disabled and re-enable the Hv, Lv and Chiller to be able to operate the detector.
> Thanks,
> Raffaella 
> 
> Inizio messaggio inoltrato:
> 
> Da: pasyuk at jlab.org <mailto:pasyuk at jlab.org>
> Data: 21 settembre 2018 03:50:03 CEST
> A: raffaella.devita at ge.infn.it <mailto:raffaella.devita at ge.infn.it>, battaglieri at ge.infn.it <mailto:battaglieri at ge.infn.it>
> Oggetto: [New Logentry] FTT condensation interlock tripped
> 
> FTT condensation interlock tripped <https://logbooks.jlab.org/entry/3595999>
> Edit <https://logbooks.jlab.org/entry/3595999/edit?destination=email/send>
> Delete <https://logbooks.jlab.org/entry/3595999/delete?destination=email/send>
> Lognumber 3595999 <https://logbooks.jlab.org/entry/3595999>. Submitted by pasyuk <https://logbooks.jlab.org/user/pasyuk> on Thu, 09/20/2018 - 21:45 <https://logbooks.jlab.org/entries?start_date=1537490743&end_date=1537497943&book=FT&book=HBLOG>. 
> Logbooks:	FT <https://logbooks.jlab.org/book/ft> HBLOG <https://logbooks.jlab.org/book/hblog>
> We got this error and it seems a bit strange. The humidity is about 5%. The first tab on hardware interlocks window shows "condensation status" Overlimit. On the second tub left most status shows condensation status Under limit. Latched interlocks show " Ok. It might be real, or it might be some issue with sensor or may be with PLC.
> Anyhow, for the time being I turned off the chiller.May be it clears if calorimeter warms up.
> 
> _______________________________________________
> Dsg-ft mailing list
> Dsg-ft at jlab.org <mailto:Dsg-ft at jlab.org>
> https://mailman.jlab.org/mailman/listinfo/dsg-ft <https://mailman.jlab.org/mailman/listinfo/dsg-ft>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_ft/attachments/20180922/1d4b59dc/attachment-0002.html>