[Dsg-hallb_magnets] [New Logentry] Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network

[Nicholas Sandoval]

Hi All,
Attached is a word document from what I have found looking at archives, talking with Doug, and responding with Denny Monday night.  

Best Regards,
Nick

----- Original Message -----
From: "Amrit Yegneswaran" <yeg at jlab.org>
To: "Brian Eng" <beng at jlab.org>, "Ruben Fair" <rfair at jlab.org>, "Glenn Young" <gyoung at jlab.org>, "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org>
Sent: Wednesday, June 28, 2017 9:33:01 AM
Subject: Re: [Dsg-hallb_magnets] [New Logentry] Follow-up Re: Solenoid	and Torus	FastDAQ cRIOs cannot connect to network

good grief brian, you job's comforter! 
anyway, as i believe that the measure of person's character is inversely proportional to the sum of how much one prevaricates, equivocates, deceives, and lies, you score an A+ 


From: "Brian Eng" <beng at jlab.org> 
To: "Amrit Yegneswaran" <yeg at jlab.org> 
Cc: "Ruben Fair" <rfair at jlab.org>, "Glenn Young" <gyoung at jlab.org>, "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Wednesday, June 28, 2017 8:11:16 AM 
Subject: Re: [Dsg-hallb_magnets] [New Logentry] Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network 

Seeing as how I have NI service request from Nov 2016 that is still actively being worked on I wouldn't dare to guess a time. 

Hopefully quicker than that though. 

> On Jun 27, 2017, at 10:51 PM, Amrit Yegneswaran <yeg at jlab.org> wrote: 
> 
> champion, 
> how long will it take? 
> are we talking the standard 4 to 6 weeks here? 
> goodnight and godbless 
> From: "Brian Eng" <beng at jlab.org> 
> To: "Ruben Fair" <rfair at jlab.org>, "Glenn Young" <gyoung at jlab.org> 
> Cc: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
> Sent: Tuesday, June 27, 2017 9:04:53 PM 
> Subject: Re: [Dsg-hallb_magnets] [New Logentry] Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network 
> 
> Hi Ruben, 
> 
> I figured we'd just discuss the options in the meeting tomorrow as well since there are a few different things we could try. 
> 
> It is very suspicious that only the fast DAQ cRIOs (both of the different model LV ones are fine) have the exact same problem: they don't fully boot even after reinstalling the NI software (safe mode is okay). 
> 
> While I think it is probably a hardware issue since formatting (we tried a few different methods for doing so) and reinstalling don't work, therefore its less likely to be software since it really isn't running anything other than NI provided stuff, it is much to early to say anything conclusively yet. 
> 
> I suspect at the very least there will be some repair cost since the current cRIOs are out of their warranty period. 
> 
> ----- Original Message ----- 
> > From: "Ruben Fair" <rfair at jlab.org> 
> > To: tlemon at jlab.org 
> > Cc: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
> > Sent: Tuesday, June 27, 2017 6:14:15 PM 
> > Subject: Re: [Dsg-hallb_magnets] [New Logentry] Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network 
> 
> > Ok thanks Tyler 
> > 
> > We can discuss a path forward when I get back tomorrow. Looks when they switched 
> > the power off without turning off the cRios first, something got fried? 
> > Difficult to understand as these things are hanging off the UPS units right? 
> > 
> > I am cc'ing Glenn Young as it looks like we might have to spend some money to 
> > overcome this problem. 
> > 
> > Regards 
> > 
> > Ruben 
> > 
> > On Jun 27, 2017, at 6:10 PM, tlemon at jlab.org wrote: 
> > 
> > 
> > 
> > 
> > Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network 
> > 
> > 
> > Lognumber 3477357 . Submitted by tlemon on Tue, 06/27/2017 - 18:05. Logbooks: 
> > HBSOLENOID HBTORUS 
> > Entry Makers: beng, tlemon 
> > References: 3477321 - Solenoid and Torus FastDAQ cRIOs cannot connect to 
> > network 
> > 
> > 
> > Brian and I replaced the Solenoid FastDAQ cRIO with the spare cRIO-9067 in Joe's 
> > spare locker. 
> > 
> > We were able to get the spare loaded with LabVIEW 2016 and the latest firmware 
> > (4.0.0f0). The Solenoid FastDAQ LabVIEW program has been modified to use the 
> > cRIO-9067 and can be found at: 
> > https://github.com/JeffersonLab/clas12-crio-sol-fast/tree/spare_deploy 
> > 
> > The new Solenoid FastDAQ cRIO is running and sending data to the PLC but it is 
> > not sending data to EPICS. We could see in the NI Distributed Systems Manager 
> > that it was writing to the shared variables and PVs but the data was not able 
> > to be seen on EPICS. 
> > 
> > We submitted the old, broken Solenoid FastDAQ cRIO to RadCon for survey and will 
> > pick it up tomorrow. 
> > 
> > The Torus FastDAQ cRIO is still down with the same error as this morning. It 
> > seems like it is some sort of hardware issue and the best course of action 
> > would be to swap it with a spare or send it away to be fixed. 
> > 
> > 
> > 
> > _______________________________________________ 
> > 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 
> _______________________________________________ 
> 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 --------------
A non-text attachment was scrubbed...
Name: HallB62617outage.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 419975 bytes
Desc: not available
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_magnets/attachments/20170628/081a9091/attachment-0001.docx>