<html><body><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div>Hi Nick,<br></div><div><br data-mce-bogus="1"></div><div>The LV cRIO has been reset. TR817B8 now reads normal temperature. <br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>A bad cRIO module as the cause of the error can be eliminated because the error occurred after we swapped out the NI-9870 cRIO module.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>From checking the LabVIEW indicators, I could see that when the error first occurred, the raw hexadecimal V1 and V2 from the LV Chassis were not equal. This is not consistent with what we have previously seen. </div><div><br data-mce-bogus="1"></div><div>I could also see that the start-up algorithm was being run for the Cerenox at 325 K yet the temperature stayed at 325 K. Just running the start-up algorithm for a Cerenox at 325 K does not seem to be working to automatically recover from the error. <br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Is there anything else happening when the LV cRIO is restarted that would correct the error? Is there something that can be checked that would eliminate the possibility that it is something wrong in the LV Chassis?<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Regards,<br data-mce-bogus="1"></div><div>Tyler<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Nicholas Sandoval" <sandoval@jlab.org><br><b>To: </b>"Tyler Lemon" <tlemon@jlab.org><br><b>Sent: </b>Thursday, February 23, 2017 2:04:19 PM<br><b>Subject: </b>CCM temp @ 325K<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">Hi Tyler,<br><br>Just noticed a temp at 325K, still on CCM B<br><br>Best Regards,<br>Nick<br></div></div></body></html>