[Dsg-hallb_magnets] on-going tests affected by cRIO communication loss?

[Ruben Fair]

Sounds like a good approach Tyler - tahnks 

Ruben 


From: "Tyler Lemon" <tlemon at jlab.org> 
To: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Tuesday, December 6, 2016 4:21:34 PM 
Subject: Re: [Dsg-hallb_magnets] on-going tests affected by cRIO communication loss? 

Renuka, 

If a change is made to the LabVIEW program and the updated VI is deployed to the cRIO, the cRIO will be stopped for a short period of time while the VI is deployed. This would interrupt any EPICS data logging or PLC communication. It would be good to avoid, for example, the situation where I go to deploy a change to the Solenoid Fast-Daq cRIO but on the same day there are on-going voltage injection tests that would be interrupted. 

As Wesley said and Ruben confirmed, it seems the best way would be to assume everything is operational unless otherwise noted. I will continue to notify you or Ruben to plan any downtime event and wait for the all-clear before proceeding. 

Thank you for your replies. 

Best regards, 
Tyler 


From: "Ruben Fair" <rfair at jlab.org> 
To: "wmoore" <wmoore at jlab.org> 
Cc: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Tuesday, December 6, 2016 4:17:53 PM 
Subject: Re: [Dsg-hallb_magnets] on-going tests affected by cRIO communication loss? 

All, 

Wesley's response is correct. 

Ruben 



From: "wmoore" <wmoore at jlab.org> 
To: "Renuka Rajput-Ghoshal" <renuka at jlab.org> 
Cc: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
Sent: Tuesday, December 6, 2016 4:12:40 PM 
Subject: Re: [Dsg-hallb_magnets] on-going tests affected by cRIO communication loss? 

Tyler, 

I think it's generally the opposite of what you describe. It's assumed everything it operational unless noted otherwise. So if you want the system to be offline, you notify Ruben/Renuka. 

They can chime in to correct me. 

Wesley 

----- Original Message ----- 
> From: "Renuka Rajput-Ghoshal" <renuka at jlab.org> 
> To: "Tyler Lemon" <tlemon at jlab.org> 
> Cc: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
> Sent: Tuesday, December 6, 2016 3:52:59 PM 
> Subject: Re: [Dsg-hallb_magnets] on-going tests affected by cRIO communication loss? 

> Hello Tyler, 
> In the Hall-B solenoid logbook one has to enter the data, I do not think that 
> there is any automatic way of doing that. 
> What do you mean by the on-going Solenoid tests are posted that would be 
> affected by Fast-Daq cRIO or LV cRIO communication loss? 
> 
> Thanks 
> Renuka 
> 
> 
> ----- Original Message ----- 
> From: "Tyler Lemon" <tlemon at jlab.org> 
> To: "dsg-hallb magnets" <dsg-hallb_magnets at jlab.org> 
> Sent: Tuesday, December 6, 2016 2:35:40 PM 
> Subject: [Dsg-hallb_magnets] on-going tests affected by cRIO communication loss? 
> 
> Hello Renuka, 
> 
> Is there a place where on-going Solenoid tests are posted that would be affected 
> by Fast-Daq cRIO or LV cRIO communication loss? Would this be posted in the 
> Hall B Solenoid logbook? 
> 
> Best regards, 
> Tyler 
> 
> _______________________________________________ 
> 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 

_______________________________________________ 
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/20161206/91ce1c71/attachment-0001.html>