[Dsg-hallb_magnets] Torus controlled ramp down, Fast DAQ cRIO terminal server

[Tyler Lemon]

They mentioned last night that there have been network issues over the weekend. If the networking for the FastDAQ cRIO drops out, would that cause the cRIO to hang up and stop? Would this type of error be recorded in the error logs?


Even though it wasn't the same error we've seen before, it is suspicious that the only 906X series cRIO stopped.


Since the magnets are ramped down and FastDAQ recording is stopped, I'm going to try to get to the cRIO through the terminal server and see if what I was doing last night is the correct procedure. I'll write up a list of steps we can add to the area with the talks from the training in October.


- Tyler



________________________________
From: Brian Eng
Sent: Sunday, December 9, 2018 11:28:33 PM
To: Tyler Lemon; dsg-hallb magnets
Subject: Re: [Dsg-hallb_magnets] Torus controlled ramp down, Fast DAQ cRIO terminal server


BTW, nothing in the console output log /usr/clas12/DATA/logs/hallbmoxa6_15.log (on clon machine). The cRIO error report from MAX doesn't have anything either.


Both of them only have output from when the cRIO was restarted.


Certainly seems to indicate that it is something specific with the 906x series of cRIO as we have only seen issues with that family, but only when they're in the end station.


Maybe there was beam issues prior? Other than radiation issues I'm not sure what's special about being in Hall B vs the EEL.

________________________________
From: Dsg-hallb_magnets <dsg-hallb_magnets-bounces at jlab.org> on behalf of Tyler Lemon <tlemon at jlab.org>
Sent: Sunday, December 9, 2018 10:44:09 PM
To: dsg-hallb magnets
Subject: Re: [Dsg-hallb_magnets] Torus controlled ramp down, Fast DAQ cRIO terminal server


Hello,


We did not need to swap cRIOs this evening. Rather than putting the spare magnet cRIO back at Brian's desk, I'm putting it in the spares cabinet in the Hall B Counting house.


It is on one shelf up from the bottom in an anti-static bag.


Tyler

________________________________
From: Dsg-hallb_magnets <dsg-hallb_magnets-bounces at jlab.org> on behalf of Tyler Lemon <tlemon at jlab.org>
Sent: Sunday, December 9, 2018 9:29:33 PM
To: dsg-hallb magnets
Subject: [Dsg-hallb_magnets] Torus controlled ramp down, Fast DAQ cRIO terminal server


Hi,


Amanda asked me to help with the Torus controlled ramp. I tried rebooting the cRIO through NI MAX, the LabVIEW project, and the MOXA terminal server.


I'm not sure if I got the sequence of commands correct to reboot with the MOXA terminal server.


I stopped the logging  and telnet-ed into the terminal server port 15  for the Torus FastDAQ cRIO.


The telnet command I used was "telnet hallb-moxa6 4015"


It said it connected successfully, but nothing happened when I typed "reboot".


If these are the correct steps, it seems to me the cRIO is dead and needs to be replaced like what has happened a few times in the past.


Best regards,

Tyler


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_magnets/attachments/20181210/b539aa0e/attachment-0001.html>