<html><body><div>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. <div><br></div><div>Wesley</div><br><br>-------- Original message --------<br>From: Amrit Yegneswaran <yeg@jlab.org> <br>Date: 6/27/17 8:31 PM (GMT-05:00) <br>To: dsg-hallb magnets <dsg-hallb_magnets@jlab.org> <br>Subject: Re: [Dsg-hallb_magnets] [New Logentry] Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network <br><br></div><br><div><div style="font-family: tahoma,new york,times,serif; font-size: 14pt; color: #009900"><div>hi tyler and brian,<br></div><div>great work.<br data-mce-bogus="1"></div><div>why weren't the software people informed before the circuit breaker panel was powered down.<br data-mce-bogus="1"></div><div>computer center always informs before power outages, so that people can safely turn off their systems.<br data-mce-bogus="1"></div><div>being on UPS doesn't mean a damn for huge voltage or current spikes, its like using a fly swatter on an elephant.<br data-mce-bogus="1"></div><div>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.<br data-mce-bogus="1"></div><div>see you tomorrow<br data-mce-bogus="1"></div><div><span id="transmark" style="display: none; width: 0px; height: 0px;"></span>amrit<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>tlemon@jlab.org<br><b>To: </b>"dsg-hallb magnets" <dsg-hallb_magnets@jlab.org><br><b>Sent: </b>Tuesday, June 27, 2017 6:10:02 PM<br><b>Subject: </b>[Dsg-hallb_magnets] [New Logentry] Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network<br></div><div><br></div><div data-marker="__QUOTED_TEXT__"><div id="center"><div id="main"><h1 class="node-title"><a href="https://logbooks.jlab.org/entry/3477357" rel="bookmark" target="_blank" data-mce-href="https://logbooks.jlab.org/entry/3477357">Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network</a><br data-mce-bogus="1"></h1><div class="date-vitals"><p class="author-datetime">Lognumber <a href="https://logbooks.jlab.org/entry/3477357" class="lognumber" target="_blank" data-mce-href="https://logbooks.jlab.org/entry/3477357">3477357</a>. Submitted by <a href="https://logbooks.jlab.org/user/tlemon" target="_blank" data-mce-href="https://logbooks.jlab.org/user/tlemon">tlemon</a> on Tue, 06/27/2017 - 18:05.</p><table class="field-vitals"><tbody><tr><th>Logbooks:</th><td><a href="https://logbooks.jlab.org/book/hbsolenoid" target="_blank" data-mce-href="https://logbooks.jlab.org/book/hbsolenoid">HBSOLENOID</a> <a href="https://logbooks.jlab.org/book/hbtorus" target="_blank" data-mce-href="https://logbooks.jlab.org/book/hbtorus">HBTORUS</a><br data-mce-bogus="1"></td></tr><tr><th>Entry Makers:</th><td>beng, tlemon</td></tr><tr><th>References:</th><td><a href="https://logbooks.jlab.org/entry/3477321" target="_blank" data-mce-href="https://logbooks.jlab.org/entry/3477321">3477321 - Solenoid and Torus FastDAQ cRIOs cannot connect to network</a><br data-mce-bogus="1"></td></tr></tbody></table></div><div class="logentry node-content"><p>Brian and I replaced the Solenoid FastDAQ cRIO with the spare cRIO-9067 in Joe's spare locker.</p><p>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: <a href="https://github.com/JeffersonLab/clas12-crio-sol-fast/tree/spare_deploy" target="_blank" data-mce-href="https://github.com/JeffersonLab/clas12-crio-sol-fast/tree/spare_deploy">https://github.com/JeffersonLab/clas12-crio-sol-fast/tree/spare_deploy</a><br data-mce-bogus="1"></p><p>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.</p><p>We submitted the old, broken Solenoid FastDAQ cRIO to RadCon for survey and will pick it up tomorrow.</p><p>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.</p></div><div class="attachment-box"><br></div></div></div><br>_______________________________________________<br>Dsg-hallb_magnets mailing list<br>Dsg-hallb_magnets@jlab.org<br>https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets<br></div></div></div></body></html>