[dsg-hallb_rich] Fw: unable to connect to RICH N2 cRIO in hall

[Tyler Lemon]

Hi Denny and Morgan,

Please see the email chain below.

Brian went in to Hall B last week to check the the RICH N2 volume cRIO that failed and it looks like the cRIO will have to be replaced.

Until the cRIO issue is resolved, can Hall B Engineering periodically check the local N2 flow readout for RICH on the top of the forward carriage to make sure the detector is still getting appropriate N2 flow? We're still all working from home and have to make special arrangements to go in to the lab.

We can remotely see that the humidity in the RICH electronic panel is still very low (below the point we're able to read with the humidity sensors), but it'd still be good to check the flow meters in case something happens to that cRIO.

Thanks.

-Tyler

________________________________
From: Dsg-internal <dsg-internal-bounces at jlab.org> on behalf of Tyler Lemon <tlemon at jlab.org>
Sent: Monday, March 29, 2021 8:32 AM
To: Amrit Yegneswaran <yeg at jlab.org>; 'dsg-internal' <dsg-internal at jlab.org>
Subject: Re: [Dsg-internal] unable to connect to RICH N2 cRIO in hall

Remotely, no there is not a way.

If you go up to the top of the forward carriage, there are local displays on the flow meters.


________________________________
From: Dsg-internal <dsg-internal-bounces at jlab.org> on behalf of Amrit Yegneswaran <yeg at jlab.org>
Sent: Monday, March 29, 2021 8:29:04 AM
To: 'dsg-internal' <dsg-internal at jlab.org>
Subject: Re: [Dsg-internal] unable to connect to RICH N2 cRIO in hall

thanks brian
we'll talk about this issue in today's meeting
is there anyway to see wheteher there is nitrogen flow?



________________________________
From: Brian Eng <beng at jlab.org>
Sent: Saturday, March 27, 2021 12:15 AM
To: Amrit Yegneswaran <yeg at jlab.org>; Tyler Lemon <tlemon at jlab.org>; 'dsg-internal' <dsg-internal at jlab.org>
Subject: Re: unable to connect to RICH N2 cRIO in hall

It wouldn't force boot into safe mode (still the same blinking status LED) nor be detected by MAX when connected via USB or directly with a network cable.

Looks like might have to swap the cRIO out, but I'm going to file a ticket with NI first to make sure there isn't something else I can do locally before doing that since that seems like kind of a pain to do.

________________________________
From: Brian Eng <beng at jlab.org>
Sent: Friday, March 26, 2021 12:15 AM
To: Amrit Yegneswaran <yeg at jlab.org>; Tyler Lemon <tlemon at jlab.org>; 'dsg-internal' <dsg-internal at jlab.org>
Subject: Re: unable to connect to RICH N2 cRIO in hall

First look isn't good, the status LED on the cRIO is constantly blinking which according to the manual means:

The cRIO-9035 has not booted into NI Linux Real-Time. The cRIO-9035 either booted into an unsupported operating system, was interrupted during the boot process, or detected an unrecoverable software error.

I did notice that the network went down/up several times along with it trying to access the SD card, so it seems like it's in some sort of boot loop.

I didn't bring the Windows laptop down with me today and it's later than I planned on being here so I'll try formatting it locally tomorrow to see if I can't just get it on the network so that Tyler/Pete can reinstall the needed software.

________________________________
From: Amrit Yegneswaran <yeg at jlab.org>
Sent: Friday, March 19, 2021 4:45 PM
To: Brian Eng <beng at jlab.org>; Tyler Lemon <tlemon at jlab.org>; 'dsg-internal' <dsg-internal at jlab.org>
Subject: Re: unable to connect to RICH N2 cRIO in hall

brian,
from tyler's e-mail it appears that since there is still N2 so there should be no urgent problem.
which means you can decide when you wish to go.
like always late in the evening.

pity the hallb techs aren't able to help.

on the good news aide patrizia, is willing to consider the robotic version, but we need to come up with a plan on what other project (which are on the books we can use the system)
so all, put on your thinking caps

________________________________
From: Dsg-internal <dsg-internal-bounces at jlab.org> on behalf of Brian Eng <beng at jlab.org>
Sent: Friday, March 19, 2021 2:48 PM
To: Tyler Lemon <tlemon at jlab.org>; 'dsg-internal' <dsg-internal at jlab.org>
Subject: Re: [Dsg-internal] unable to connect to RICH N2 cRIO in hall

I can go in and check it tonight if need be.

________________________________
From: Dsg-internal <dsg-internal-bounces at jlab.org> on behalf of Tyler Lemon <tlemon at jlab.org>
Sent: Friday, March 19, 2021 1:45 PM
To: 'dsg-internal' <dsg-internal at jlab.org>
Subject: [Dsg-internal] unable to connect to RICH N2 cRIO in hall

Hello,

I'm going to preface this by saying that from the EP cRIO, we can see that the humidity in RICH is still low and at a good level so RICH is still getting N2 without issues.

That being said, I cannot connect to the N2 volume cRIO (hostname richcrio) over the network.

Peter noticed this a few days ago and I asked Hall B engineering to check on the cRIO. Their response was not helpful since they just looked at the cRIO chassis from the outside. I have since asked them to recheck the chassis, looking inside to see if there are any lights flashing inside, but this probably won't be done today.

It seems more likely than not that someone will have to go in to Hall B to check the cRIO.

Since we can still monitor the internal humidity from the EP cRIO, I don't think this is something that has to be absolutely taken care of right this movement.

Should I start the process of getting approval to go in myself? Or would Brian be able to check the cRIO?



-Tyler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_rich/attachments/20210329/103c5e33/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://mailman.jlab.org/pipermail/dsg-hallb_rich/attachments/20210329/103c5e33/attachment.txt>