[Dsg-hallb_magnets] cernox sensors 325K error
    Ruben Fair 
    rfair at jlab.org
       
    Fri Feb 10 07:55:00 EST 2017
    
    
  
Ok - let's see what Tyler learns from the LV chassis output. 
Ruben 
From: "David Kashy" <kashy at jlab.org> 
To: "Ruben Fair" <rfair at jlab.org> 
Cc: "Tyler Lemon" <tlemon at jlab.org>, "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Friday, February 10, 2017 7:49:11 AM 
Subject: Re: [Dsg-hallb_magnets] cernox sensors 325K error 
We have a 325 on coil B now 
----- Original Message ----- 
From: "Ruben Fair" <rfair at jlab.org> 
To: "Tyler Lemon" <tlemon at jlab.org> 
Cc: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org>, "kashy" <kashy at jlab.org> 
Sent: Thursday, February 9, 2017 4:50:28 PM 
Subject: Re: [Dsg-hallb_magnets] cernox sensors 325K error 
Ok Tyler - sounds like a reasonable approach. 
Regards 
Ruben 
From: "Tyler Lemon" <tlemon at jlab.org> 
To: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org>, "David Kashy" <kashy at jlab.org> 
Sent: Thursday, February 9, 2017 4:48:11 PM 
Subject: [Dsg-hallb_magnets] cernox sensors 325K error 
Hello Ruben and Dave Kashy, 
Before implementing the LabVIEW that will automatically reinitialize a Cerenox sensor if it reads 325K, a version will be deployed to look at the raw hexadecimal text output from the LV Chassis. As Peter mentioned below, this would tell us if the 325K error is caused by the LV Chassis or some conversion done in LabVIEW. 
Since we cannot force the 325K error, we will have to wait for the error to occur to compare the raw LV Chassis output. 
Best regards, 
Tyler 
From: "Amrit Yegneswaran" <yeg at jlab.org> 
To: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Thursday, February 9, 2017 2:44:31 PM 
Subject: Re: [Dsg-hallb_magnets] cernox sensors 
thanks peter and tyler. 
From: "Peter Bonneau" <bonneau at jlab.org> 
To: "Amrit Yegneswaran" <yeg at jlab.org> 
Sent: Thursday, February 9, 2017 2:16:49 PM 
Subject: cernox sensors 
Hi Amrit, 
I looked at the LV cRio code with Tyler. 
They don't seem to know if the excitation chassis is the problem or the 
conversions, etc in the code. 
The data is sent to cRio as text via serial communications then 
immediately changed to a number for the calculations & lookup table. 
We've seen a lot of errors in serial communications in other 
instrumentation. 
I suggested to Tyler that we latch the received text numbers V1 and V2 
when this error occurs before the conversion to numbers. 
That will tell us if the excitation chassis is not sending or we're not 
receiving the raw data correctly. 
Thanks, 
Peter 
_______________________________________________ 
Dsg-hallb_magnets mailing list 
Dsg-hallb_magnets at jlab.org 
https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets 
_______________________________________________ 
Dsg-hallb_magnets mailing list 
Dsg-hallb_magnets at jlab.org 
https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_magnets/attachments/20170210/c7afc441/attachment.html>
    
    
More information about the Dsg-hallb_magnets
mailing list