[Dsg-hallb_magnets] Solenoid installation task time line meeting minutes

[Tyler Lemon]

Hello Ruben, 

Attached is a log of all 325 K Errors since January 1, 2017, including the Cerenox noted today. 

The table contains the Cerenox PV name where the error occurred, the dates of the errors, and which LV Chassis, connector, cRIO module, and module channel reads that Cerenox. 

When creating this table, I noted that the PVs for the Coil F Helium Supply and Return are listed incorrectly. In EPICS they are TR817FS and TR817FR. Attached as "Torus Fast LV Signal List_01May2017.xlsx" is also a version of the Torus master instrumentation list with these PV names corrected. 

Best regards, 
Tyler 


From: "Ruben Fair" <rfair at jlab.org> 
To: "Brian Eng" <beng at jlab.org> 
Cc: "Tyler Lemon" <tlemon at jlab.org>, "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Monday, May 1, 2017 10:59:38 AM 
Subject: Re: [Dsg-hallb_magnets] Solenoid installation task time line meeting minutes 

Brian , Tyler 

First can I see Tyler's table with all misbehaving sensors and also the chassis number and also the connector numbers? 

Regards 

Ruben 

> On May 1, 2017, at 10:43 AM, Brian Eng <beng at jlab.org> wrote: 
> 
> I just spoke with Tyler and he explained that the code is supposed to latch all the chassis if any of them has an error, so that solves that part for me. 
> 
> He also confirmed that last time he deployed the restart code it didn't recover the cernox. 
> 
> I still think it is something to do with these particular chassis. Since it's basically only happened with 2 of them, and most of the errors are concentrated on a single chassis; if it was an issue with the code and/or cRIO I'd expect eventually all chassis to have the error. 
> 
> 
> 
> So the question to Ruben/Probir is: should we completely remove the restart functionality to see if the algorithm can recover a fault itself? 
> 
> 
> 
>> On May 1, 2017, at 10:14 AM, Brian Eng <beng at jlab.org> wrote: 
>> 
>> Per Tyler's meeting minutes if there were no cernox errors until mid-May then the test would have been successful. 
>> 
>> When I checked the chassis status this morning all the chassis had been latched with a 325K error, however so far I've only found 1 sensor that went to 325K (and immediately went back to a "good" value, see attached screenshot, interesting to note that the sensor temp went up just before the jump). 
>> 
>> I was under the impression that the cernox restart functionality didn't work, so either it does in fact work or the new algorithm managed to correct the error itself. I'll need to talk with Tyler to get some more details, maybe we try taking the reset functionality fully out and see what happens? 
>> 
>> The error happened on a sensor connected to chassis #2. 
>> 
>> <Screen Shot 2017-05-01 at 10.04.53 AM.png> 
>> 
>>> On Apr 26, 2017, at 10:12 AM, Tyler Lemon <tlemon at jlab.org> wrote: 
>>> 
>>> Hello, 
>>> 
>>> Attached is minutes from the meeting on Monday April 24, 2017 to discuss the time line for Solenoid installation tasks. In the attachment is also the schedule posted with tasks assigned to DSG highlighted in yellow. 
>>> 
>>> Best regards, 
>>> Tyler 
>>> <2017-04-24 Solenoid meeting minutes I&c TASK TIMELINE FOR INSTALLATION.pdf> 
>> _______________________________________________ 
>> 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/20170501/f01768a8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Torus Fast LV Signal List_01May2017.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 62402 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_magnets/attachments/20170501/f01768a8/attachment-0001.xlsx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 325K Error Log_2017-05-01.pdf
Type: application/pdf
Size: 183181 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_magnets/attachments/20170501/f01768a8/attachment-0001.pdf>