<html><body><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div data-marker="__QUOTED_TEXT__"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000"><div>Hi Rama,<br></div><div>raw hex values when TR817B8 first read 325 K are:<br></div><div>V1 = 25F493<br></div><div>V2 = 12F564<br></div><br><div>Nick,<br></div><div>I will have to look into the reset of the module. There is at least a function that clears the input/output buffers of the LV Chassis, but I am not sure if that is the type of reset you mean.<br></div><br><div>Regards,<br></div><div>Tyler<br></div><hr id="zwchr"><div><b>From: </b>"Nicholas Sandoval" <sandoval@jlab.org><br><b>To: </b>"Tyler Lemon" <tlemon@jlab.org><br><b>Cc: </b>"Ramakrishna Bachimanchi" <bachiman@jlab.org><br><b>Sent: </b>Friday, February 24, 2017 7:46:41 AM<br><b>Subject: </b>Re: [Dsg-hallb_magnets] CCM temp @ 325K<br></div><br><div>Is there a a bit level reset for each RS232 module on the cRIO chassis? Or something similar? <br><br>-Nick<br><br>----- Original Message -----<br>From: "Ramakrishna Bachimanchi" <bachiman@jlab.org><br>To: "Tyler Lemon" <tlemon@jlab.org>, "dsg-hallb magnets" <dsg-hallb_magnets@jlab.org><br>Sent: Thursday, February 23, 2017 5:48:35 PM<br>Subject: Re: [Dsg-hallb_magnets] CCM temp @ 325K<br><br>Hi Tyler, <br><br>cam you please send me the raw hex values for V1 and V2 and also the values for I1 and I2, when it happens again. I will look into the algorithm one more time and see, if we can adjust few things to correct this issue <br><br>Thanks, <br><br>Rama <br><br>On 2/23/2017 5:31 PM, Tyler Lemon wrote: <br><br><br><br>Hi Nick, <br><br>The LV cRIO has been reset. TR817B8 now reads normal temperature. <br><br>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><br>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. <br><br>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><br>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><br>Regards, <br>Tyler <br><br><br><br><br>From: "Nicholas Sandoval" <sandoval@jlab.org> <br>To: "Tyler Lemon" <tlemon@jlab.org> <br>Sent: Thursday, February 23, 2017 2:04:19 PM <br>Subject: CCM temp @ 325K <br><br>Hi Tyler, <br><br>Just noticed a temp at 325K, still on CCM B <br><br>Best Regards, <br>Nick <br><br><br>_______________________________________________<br>Dsg-hallb_magnets mailing list<br>Dsg-hallb_magnets@jlab.org<br>https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets</div></div></div></div><br></div></div></body></html>