[Dsg-ft] interlocks on calorimeter temperature
Raffaella De Vita
Raffaella.Devita at ge.infn.it
Thu Aug 2 13:47:35 EDT 2018
Hi Peter,
thanks so much for looking into this. I saw that the temp1 value had
exceed the range but, after it went back down, when I tried resetting
the latched errors nothing happened. Maybe I did something wrong.
Anyway, it's all working now. Thanks again,
Raffaella
Peter Bonneau wrote:
> Hi Raffaella,
>
> The Interlock status for sensor #1 is now reporting a temperature
> within the set interlock range.
> There was a latched interlock error for sensor #1 which indicates this
> signal was not within range earlier and needed a reset.
> As shown on the attached Mya plot, temp #1 was 25.048 C at 11:37:50
> which exceeded the 25 C trip level.
>
> I've reset the interlock and LV & HV is now enabled.
>
> Peter
>
>
>
>
> ------------------------------------------------------------------------
> *From: *"Raffaella De Vita" <Raffaella.Devita at ge.infn.it>
> *To: *"Amanda Hoebel" <amandah at jlab.org>
> *Cc: *"dsg-ft" <dsg-ft at jlab.org>
> *Sent: *Thursday, August 2, 2018 12:44:17 PM
> *Subject: *[Dsg-ft] interlocks on calorimeter temperature
>
> Hi Amanda,
> the FT cRio is detecting a high temperature condition on sensor 1 for
> the calorimeter even if the reported temperature is actually in range. I
> tried changing the range or resetting multiple times with no success.
> Could you take a look and advise?
> Thanks,
> Raffaella
> _______________________________________________
> Dsg-ft mailing list
> Dsg-ft at jlab.org
> 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/20180802/410492c1/attachment-0002.html>
More information about the Dsg-ft
mailing list