<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'>I somehow managed to reset this latched interlock. I turned chiller back on. <br><br><div><span name="x"></span>-Eugene<span name="x"></span><br></div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Raffaella De Vita" <Raffaella.Devita@ge.infn.it><br><b>To: </b>dsg-ft@jlab.org, amandah@jlab.org<br><b>Cc: </b>pasyuk@jlab.org<br><b>Sent: </b>Friday, September 21, 2018 1:53:19 AM<br><b>Subject: </b>Fwd: [New Logentry] FTT condensation interlock tripped<br><br><div></div><div>Hi Amanda,</div><div>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. </div><div>Can you check?<br>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.</div><div>Thanks,</div><div>Raffaella <br><br>Inizio messaggio inoltrato:<br><br></div><blockquote><div><b>Da:</b> <a href="mailto:pasyuk@jlab.org" target="_blank">pasyuk@jlab.org</a><br><b>Data:</b> 21 settembre 2018 03:50:03 CEST<br><b>A:</b> <a href="mailto:raffaella.devita@ge.infn.it" target="_blank">raffaella.devita@ge.infn.it</a>, <a href="mailto:battaglieri@ge.infn.it" target="_blank">battaglieri@ge.infn.it</a><br><b>Oggetto:</b> <b>[New Logentry] FTT condensation interlock tripped</b><br><br></div></blockquote><blockquote><div>
<div id="center">
<div id="main">
<style>
<!--/*--><![CDATA[/* ><!--*/
div.field-vitals{
margin: 0.5em 0;
}
div.field-vitals .field-type-taxonomy-term-reference {
margin: 0.1em 0;
}
article.comment {
padding-left: 10px;
}
article.comment.odd {
background-color: #EEEEEE;
}
article.comment.even {
background-color: #DDDDDD;
}
div.node-content.logentry table{
width: auto;
border-collapse: collapse;
border-spacing: 0;
border-width: 1px;
}
div.node-content.logentry th{
border: inherit;
}
div.node-content.logentry blockquote{
background-color: #FFFFFF;
}
div.node-content.logentry caption{
font-size: 1em;
font-weight: normal;
}
table.field-vitals{
margin-top: 1em;
margin-bottom: 1em;
font-size: 87.5%;
}
table.field-vitals th{
vertical-align: middle;
text-align: left;
width: 15%;
padding: 0.1em;
}
table.field-vitals td{
vertical-align: middle;
text-align: left;
width: auto;
padding: 0.1em;
}
table.field-vitals td li {
margin-left: 0;
list-style-type: none;
list-style-image: none;
}
table.downtime {
width: 30em;
margin-bottom: 1em;
border: 1px black dotted;
}
table.downtime th {
text-align: center;
}
table.downtime td {
text-align: center;
}
tr.caption th {
border-bottom: none;
}
table.downtime tfoot{
background-color:#EEEEEE;
}
div.field-name-body{
margin: 1em 0;
font-size: 110%;
}
div.date-vitals p{
margin: .1em 0;
}
article div.ctools-collapsible-container{
margin-left: -5px;
clear: both;
}
#comment-form{
margin-left: 5px;
border: graytext outset medium;
-moz-border-radius: 15px;
border-radius: 15px;
padding: 1em;
}
div.comments-form-box {
margin-top: 2em;
margin-bottom: 5em;
}
h3.comment-title {
}
p.author-datetime{
font-weight: bold;
}
/*--><!]]>*/
</style><h1 class="node-title">
<a href="https://logbooks.jlab.org/entry/3595999" rel="bookmark" target="_blank">FTT condensation interlock tripped</a>
</h1>
<div class="contextual-links-wrapper"><ul class="contextual-links"><li><a href="https://logbooks.jlab.org/entry/3595999/edit?destination=email/send" target="_blank">Edit</a></li><li><a href="https://logbooks.jlab.org/entry/3595999/delete?destination=email/send" target="_blank">Delete</a></li></ul></div>
<div class="date-vitals">
<p class="author-datetime">
Lognumber <a href="https://logbooks.jlab.org/entry/3595999" class="lognumber" target="_blank">3595999</a>. Submitted by <a href="https://logbooks.jlab.org/user/pasyuk" target="_blank">pasyuk</a> on <a href="https://logbooks.jlab.org/entries?start_date=1537490743&end_date=1537497943&book=FT&book=HBLOG" target="_blank">Thu, 09/20/2018 - 21:45</a>. </p>
<table class="field-vitals"><tbody><tr><th>Logbooks: </th><td><a href="https://logbooks.jlab.org/book/ft" target="_blank">FT</a> <a href="https://logbooks.jlab.org/book/hblog" target="_blank">HBLOG</a></td></tr></tbody></table></div>
<div class="logentry node-content">
<p>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.<br>
Anyhow, for the time being I turned off the chiller.May be it clears if calorimeter warms up.</p>
</div>
<div class="attachment-box">
</div>
</div>
</div>
</div></blockquote></div><br></div></body></html>