<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>Ok thanks Tyler</div><div><br></div><div>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?</div><div><br></div><div>I am cc'ing Glenn Young as it looks like we might have to spend some money to overcome this problem.</div><div><br></div><div>Regards</div><div><br></div><div>Ruben</div><div><br>On Jun 27, 2017, at 6:10 PM, <a href="mailto:tlemon@jlab.org">tlemon@jlab.org</a> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div id="center">
<div id="main">
<style>
<!--/*--><![CDATA[/* ><!--*/
div.field-vitals{
margin: 0.5em 0;
}
div.field-vitals .field-type-taxonomy-term-reference {
margin: 0.1em 0;
}
article.comment {
padding-left: 10px;
}
article.comment.odd {
background-color: #EEEEEE;
}
article.comment.even {
background-color: #DDDDDD;
}
div.node-content.logentry table{
width: auto;
border-collapse: collapse;
border-spacing: 0;
border-width: 1px;
}
div.node-content.logentry th{
border: inherit;
}
div.node-content.logentry blockquote{
background-color: #FFFFFF;
}
div.node-content.logentry caption{
font-size: 1em;
font-weight: normal;
}
table.field-vitals{
margin-top: 1em;
margin-bottom: 1em;
font-size: 87.5%;
}
table.field-vitals th{
vertical-align: middle;
text-align: left;
width: 15%;
padding: 0.1em;
}
table.field-vitals td{
vertical-align: middle;
text-align: left;
width: auto;
padding: 0.1em;
}
table.field-vitals td li {
margin-left: 0;
list-style-type: none;
list-style-image: none;
}
table.downtime {
width: 30em;
margin-bottom: 1em;
border: 1px black dotted;
}
table.downtime th {
text-align: center;
}
table.downtime td {
text-align: center;
}
tr.caption th {
border-bottom: none;
}
table.downtime tfoot{
background-color:#EEEEEE;
}
div.field-name-body{
margin: 1em 0;
font-size: 110%;
}
div.date-vitals p{
margin: .1em 0;
}
article div.ctools-collapsible-container{
margin-left: -5px;
clear: both;
}
#comment-form{
margin-left: 5px;
border: graytext outset medium;
-moz-border-radius: 15px;
border-radius: 15px;
padding: 1em;
}
div.comments-form-box {
margin-top: 2em;
margin-bottom: 5em;
}
h3.comment-title {
/* display: none; */
}
p.author-datetime{
font-weight: bold;
}
/*--><!]]>*/
</style><article id="node-550207" class="node node-logentry article ia-n clearfix" role="article"><header class="node-header"><h1 class="node-title">
<a href="https://logbooks.jlab.org/entry/3477357" rel="bookmark">Follow-up Re: Solenoid and Torus FastDAQ cRIOs cannot connect to network</a>
</h1>
</header><div class="date-vitals">
<p class="author-datetime">
Lognumber <a href="https://logbooks.jlab.org/entry/3477357" class="lognumber" data-lognumber="3477357">3477357</a>. Submitted by <a href="https://logbooks.jlab.org/user/tlemon">tlemon</a> on <time datetime="2017-06-27T18:05:57-0400" pubdate="pubdate">Tue, 06/27/2017 - 18:05</time>. </p>
<table class="field-vitals"><tbody><tr><th>Logbooks: </th><td><a href="https://logbooks.jlab.org/book/hbsolenoid">HBSOLENOID</a> <a href="https://logbooks.jlab.org/book/hbtorus">HBTORUS</a></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">3477321 - Solenoid and Torus FastDAQ cRIOs cannot connect to network</a></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">https://github.com/JeffersonLab/clas12-crio-sol-fast/tree/spare_deploy</a></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">
</div>
</article> </div>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Dsg-hallb_magnets mailing list</span><br><span><a href="mailto:Dsg-hallb_magnets@jlab.org">Dsg-hallb_magnets@jlab.org</a></span><br><span><a href="https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets">https://mailman.jlab.org/mailman/listinfo/dsg-hallb_magnets</a></span><br></div></blockquote></body></html>