<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Thank you<br></div><div><br></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Tyler Lemon" <tlemon@jlab.org><br><b>To: </b>"dsg-hallb magnets" <dsg-hallb_magnets@jlab.org><br><b>Sent: </b>Friday, February 17, 2017 2:15:53 PM<br><b>Subject: </b>Re: [Dsg-hallb_magnets] Torus Cerenox T817F2 at 325K, LV cRIO restarted<br></div><div><br></div><div data-marker="__QUOTED_TEXT__"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div>Hello,<br></div><div>Regarding point 1 in previous email (below in blue), the parameters used at the start of the Cerenox start-up algorithm for a sensor at 325 K were incorrect. It was not using the Cerenox start-up excitation value set, but what the excitation value was before the sensor jumped to 325 K. This has been corrected. The updated LabVIEW will be deployed within the next few minutes.<br></div><br><div>Best regard,<br></div><div>Tyler<br></div><br><br><div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div><span style="color: rgb(0, 0, 255);">Hello,</span><br></div><div><span style="color: rgb(0, 0, 255);">This morning, I noted Torus Cerenox TR817F2 was at 325 K. The LV cRIO was restarted and TR817F2 reads ~4.8 K.</span></div><br><div><span style="color: rgb(0, 0, 255);">The indicators added to LabVIEW earlier this week showed that the start-up algorithm had been running for the sensor since it first jumped to 325 K. With this new information, there are two possibilities:</span><br></div><br><div><span style="color: rgb(0, 0, 255);">1.) How LabVIEW is running the start-up algorithm for just the Cerenox at 325K is not working correctly. I will check this today.</span><br></div><br><div><span style="color: rgb(0, 0, 255);">2.) Just running the start-up algorithm does not fix error. When LV cRIO is restarted, there are no excitations for a few seconds. This short dead period could be what is actually fixing the error. </span><br></div><br style="color: rgb(0, 0, 255);"></div><br></div></div><br>_______________________________________________<br>Dsg-hallb_magnets mailing list<br>Dsg-hallb_magnets@jlab.org<br>https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets<br></div></div></body></html>