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

[Amrit Yegneswaran]

dear wesley, 
look at the e-mail carefully! 
i am saying computer center informs us as a matter of course when they plan something, so based on that shouldn't every one learn f rom that procedure . 
why did not someone in hall b not broadcast the fact that there was to be a power outage, like the computer center typically does . 
Aren't people supposed to learn from experts. 
Or is it the opinion that computer center is informing staff of power outages just for the fun of it. 

of course computer center didn't have anything to do with it, where did you get that idea from. 
i guess i forgot and wrote in a foreign language. 
yeah it was just the UPS that failed and it was just for the sake of a nail a kingdom was lost. 
just wow 
amrit 


From: "Wesley Moore" <wmoore at jlab.org> 
To: "Amrit Yegneswaran" <yeg at jlab.org>, "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Tuesday, June 27, 2017 8:55:24 PM 
Subject: RE: [Dsg-hallb_magnets] [New Logentry] Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network 

Has nothing to do with the computer center. Was it found to but an actual power outage? Sounded like it was just a UPS that failed. 
Wesley 


-------- Original message -------- 
From: Amrit Yegneswaran <yeg at jlab.org> 
Date: 6/27/17 8:31 PM (GMT-05:00) 
To: dsg-hallb magnets <dsg-hallb_magnets at jlab.org> 
Subject: Re: [Dsg-hallb_magnets] [New Logentry] Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network 


hi tyler and brian, 
great work. 
why weren't the software people informed before the circuit breaker panel was powered down. 
computer center always informs before power outages, so that people can safely turn off their systems. 
being on UPS doesn't mean a damn for huge voltage or current spikes, its like using a fly swatter on an elephant. 
is there some person in hallb who should have known the the power was going to be out, if so, why didn't they inform system owners to safely power off these sensitive systems. 
see you tomorrow 
amrit 




From: tlemon at jlab.org 
To: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Tuesday, June 27, 2017 6:10:02 PM 
Subject: [Dsg-hallb_magnets] [New Logentry] Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network 

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 

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