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

[tlemon at jlab.org]

Logentry Text:
--
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. 

---

This is a plain text email for clients that cannot display HTML.  The full logentry can be found online at https://logbooks.jlab.org/entry/3477357
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_magnets/attachments/20170627/7dc62724/attachment.html>