[Dsg-hallb_magnets] CCM temp @ 325K

[Ramakrishna Bachimanchi]

Hi Tyler,

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

Thanks,

Rama


On 2/23/2017 5:31 PM, Tyler Lemon wrote:
> Hi Nick,
>
> The LV cRIO has been reset. TR817B8 now reads normal temperature.
>
> 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.
>
> 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.
>
> 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.
>
> 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?
>
> Regards,
> Tyler
>
>
>
> ------------------------------------------------------------------------
> *From: *"Nicholas Sandoval" <sandoval at jlab.org>
> *To: *"Tyler Lemon" <tlemon at jlab.org>
> *Sent: *Thursday, February 23, 2017 2:04:19 PM
> *Subject: *CCM temp @ 325K
>
> Hi Tyler,
>
> Just noticed a temp at 325K,  still on CCM B
>
> Best Regards,
> Nick

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_magnets/attachments/20170223/e016f10f/attachment.html>