<html><body><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div>Hello,<br data-mce-bogus="1"></div><div>This morning, I noted Torus Cerenox TR817F2 was at 325 K. The LV cRIO was restarted and TR817F2 reads ~4.8 K. </div><div><br data-mce-bogus="1"></div><div>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:<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>1.) How LabVIEW is running the start-up algorithm for just the Cerenox at 325K is not working correctly. I will check this today.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>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. <br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Best regards,<br data-mce-bogus="1"></div><div>Tyler<br data-mce-bogus="1"></div></div></body></html>