<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">My preference would be to change the alarms and not touch the code.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Dave - will this work for you?</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Ruben<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Brian Eng<br>
<b>Sent:</b> Monday, January 7, 2019 10:59:23 AM<br>
<b>To:</b> Tyler Lemon<br>
<b>Cc:</b> Ruben Fair; David Kashy; Probir Ghoshal; Nicholas Sandoval; hallb-engineering@jlab.org; dsg-hallb magnets<br>
<b>Subject:</b> Re: [Dsg-hallb_magnets] [New Logentry] Torus Alarm: METAL4K_DT_MAX</font>
<div> </div>
</div>
<div style="word-wrap:break-word; line-break:after-white-space">Looking at the data it was TR817F1 that spiked to 325 K for a single reading. The PLC updates the statistics (min/max/avg/etc) every 5 seconds. Which is why the CCM_DT_MAX was bad for 5 seconds,
see attached myaPlot image.
<div class=""><br class="">
</div>
<div class="">However, the code we deployed on the cRIO worked as expected in that it was only bad for one reading before returning to the correct value. Prior versions would get stuck at 325 K.</div>
<div class=""><br class="">
</div>
<div class="">I had thought there was some delay (setting it to >5 seconds should work) to the alarms such that 1 bad reading (they're updated every 1 sec on cRIO and 5 sec on PLC) wouldn't cause an alarm?</div>
<div class=""><br class="">
</div>
<div class="">We can make code changes on the cRIO or PLC to try and mask these spurious readings if that's something that's desired or needed. However, we'd need to add some logic such that an actual failure would still get read out as 325 K, so it would be
safer to just change the alarms since the current behavior is fairly well understood albeit it makes the plots kind of messy since it throws off the scale so much.</div>
<div class=""><br class="">
</div>
<div class="">Hope that helps explain what happened and let us know if we should work on changing the code.</div>
<div class=""><br class="">
</div>
<div class=""><img id="x_868C94CB-10E4-4B4E-BF54-0779CB16CD6E" class="" data-outlook-trace="F:1|T:1" src="cid:231C5586-024C-4DA6-8CDA-9AD8496E3809@jlab.org"></div>
<div class=""><br class="">
</div>
<div class="">--<br class="">
Brian Eng<br class="">
Detector Support Group<br class="">
757-269-6018<br class="">
</div>
<div class=""><br class="">
<blockquote type="cite" class="">On Jan 7, 2019, at 8:24 AM, Tyler Lemon <<a href="mailto:tlemon@jlab.org" class="">tlemon@jlab.org</a>> wrote:<br class="">
<br class="">
Hello,<br class="">
<br class="">
I'm forwarding this email chain to the dsg-hallb_magnets mailing list so Brian and other DSG members that support the magnet can have the full story on what's been happening.<br class="">
<br class="">
It seems to me that it's a similar problem as the 325 K error with the Cernoxes we had that Brian's fixed excitation voltage code resolved. If I remember right, the fixed-voltage code has already been applied to all Cernoxes. <br class="">
<br class="">
Best regards,<br class="">
Tyler<br class="">
<br class="">
<br class="">
From: Probir Ghoshal<br class="">
Sent: Monday, January 7, 2019 8:10 AM<br class="">
To: Ruben Fair; David Kashy; <a href="mailto:hallb-engineering@jlab.org" class="">hallb-engineering@jlab.org</a>; Nicholas Sandoval; Tyler Lemon<br class="">
Subject: Re: [New Logentry] Torus Alarm: METAL4K_DT_MAX<br class="">
<br class="">
Ruben, Dave<br class="">
<br class="">
This we have already addressed in the past and if I am not mistaking Brian E had his algorithm that sets the excitation current. The hardware (chassis) seemed to be working.<br class="">
Rama, Bring and Nick can comment to get the last updated software and the result.<br class="">
<br class="">
Regards<br class="">
<br class="">
Probir<br class="">
<br class="">
<br class="">
<br class="">
From: Ruben Fair<br class="">
Sent: Monday, January 7, 2019 8:04 AM<br class="">
To: David Kashy; hallb-engineering@jlab.org; Nicholas Sandoval; Tyler Lemon; Probir Ghoshal<br class="">
Subject: Re: [New Logentry] Torus Alarm: METAL4K_DT_MAX<br class="">
<br class="">
Tyler, Nick, Probir,<br class="">
<br class="">
Let me know what you think about this. I have also asked Rama to comment.<br class="">
<br class="">
Ruben<br class="">
<br class="">
<br class="">
From: kashy@jlab.org <kashy@jlab.org><br class="">
Sent: Sunday, January 6, 2019 7:35:02 AM<br class="">
To: hallb-engineering@jlab.org; Nicholas Sandoval; Tyler Lemon; Probir Ghoshal; Ruben Fair<br class="">
Subject: [New Logentry] Torus Alarm: METAL4K_DT_MAX<br class="">
<br class="">
Torus Alarm: METAL4K_DT_MAX<br class="">
<br class="">
<div class=""><span class="x_Apple-tab-span" style="white-space:pre"></span>• Edit<br class="">
</div>
<div class=""><span class="x_Apple-tab-span" style="white-space:pre"></span>• Delete<br class="">
</div>
Lognumber 3641551. Submitted by kashy on Sun, 01/06/2019 - 07:31.<br class="">
Logbooks:<span class="x_Apple-tab-span" style="white-space:pre"> </span>HBLOG HBTORUS<br class="">
Entry Makers:<span class="x_Apple-tab-span" style="white-space:pre"> </span>kashy<br class="">
Last night at 1/5/2019 at 22:39 there was a 5 second period where the signal went from 4.5K to 255K.<br class="">
All signals that go into this this signal jumped at this time.<br class="">
CCM_DT_MAX<br class="">
CCM_USHR_DT<br class="">
CCM_DSHR_DT<br class="">
But only the first one above went to 255K.<br class="">
A similar alarm went off this morning at1/6/2019 at 6:16<br class="">
This time it was triggered by a quick step change from 4.5 to 43K on the USHR signal.<br class="">
(Neither of these can be real temperature changes so it must be something in the instrumentation)<br class="">
These were false alarms. Can we find a reason and stop it from happening?<br class="">
Thanks<br class="">
Dave<br class="">
_______________________________________________<br class="">
Dsg-hallb_magnets mailing list<br class="">
Dsg-hallb_magnets@jlab.org<br class="">
https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets</blockquote>
</div>
</div>
</body>
</html>