<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
For the webopi version</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<ol>
<li>go to RICH Overview from the main menu</li><li>then click on the Hard Interlocks button in the upper right and select Interlock Controls</li><li>click on the Details button near the middle of the screen in the N2 Volume and Gas section</li><li>finally click on the N2 Volume Sensor Locations</li></ol>
<div>Here's a direct link to that screen once you've already logged in to the webopi page if you don't want to go through those steps.</div>
<div><br>
</div>
<div><a href="https://hallbopi.jlab.org/webopi3.3/w?opi=https://hallbopi.jlab.org/opis/apps/cRioIntlkApp/RICH_S1_N2.opi" id="LPlnk181268">https://hallbopi.jlab.org/webopi3.3/w?opi=https://hallbopi.jlab.org/opis/apps/cRioIntlkApp/RICH_S1_N2.opi</a><br>
</div>
<div><br>
</div>
<div>When I go to that page I get non-zero values for the humidity sensors, like in the attached image.</div>
<div><br>
</div>
</div>
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Marco Mirazita <Marco.Mirazita@lnf.infn.it><br>
<b>Sent:</b> Tuesday, April 6, 2021 3:41 AM<br>
<b>To:</b> Valery Kubarovsky <vpk@jlab.org><br>
<b>Cc:</b> Tyler Lemon <tlemon@jlab.org>; Brian Eng <beng@jlab.org>; dsg-hallb_rich@jlab.org <dsg-hallb_rich@jlab.org>; Bob Miller <rmiller@jlab.org>; Denny Insley <dinsley@jlab.org>; Morgan Cook IV <mcookiv@jlab.org><br>
<b>Subject:</b> Re: [dsg-hallb_rich] [EXTERNAL] Re: Fw: unable to connect to RICH N2 cRIO in hall</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">Hello,<br>
thank you everyone for this work.<br>
But I have one question now, how can I check the status of the N2 <br>
system? From the web OPI interface it looks that all the humidity values <br>
are at 0.<br>
Marco<br>
<br>
<br>
<br>
Il 2021-04-03 18:35 Valery Kubarovsky ha scritto:<br>
> Thank you, folks!<br>
> I inspected the interlock limits, and they are as expected.<br>
> Valery<br>
> <br>
> -------------------------<br>
> <br>
> From: dsg-hallb_rich <dsg-hallb_rich-bounces@jlab.org> on behalf of<br>
> Tyler Lemon <tlemon@jlab.org><br>
> Sent: Saturday, April 3, 2021 08:02<br>
> To: Brian Eng <beng@jlab.org>; Marco Mirazita<br>
> <Marco.Mirazita@lnf.infn.it><br>
> Cc: Morgan Cook IV <mcookiv@jlab.org>; Bob Miller <rmiller@jlab.org>;<br>
> Denny Insley <dinsley@jlab.org>; dsg-hallb_rich@jlab.org<br>
> <dsg-hallb_rich@jlab.org><br>
> Subject: Re: [dsg-hallb_rich] [EXTERNAL] Re: Fw: unable to connect to<br>
> RICH N2 cRIO in hall<br>
> <br>
> Hi Brian,<br>
> <br>
> Thanks for swapping out the cRIOs.<br>
> <br>
> It looks good to me, too; all the values are as expected.<br>
> <br>
> The only thing I think that would need double checking by Valery or<br>
> Marco is the interlock limits since the limits might not have been<br>
> restored properly given that this is a different cRIO and there were<br>
> issues with the previous cRIO.<br>
> <br>
> -Tyler<br>
> <br>
> -------------------------<br>
> <br>
> From: Brian Eng <beng@jlab.org><br>
> Sent: Saturday, April 3, 2021 12:51 AM<br>
> To: Tyler Lemon <tlemon@jlab.org>; Marco Mirazita<br>
> <Marco.Mirazita@lnf.infn.it><br>
> Cc: dsg-hallb_rich@jlab.org <dsg-hallb_rich@jlab.org>; Bob Miller<br>
> <rmiller@jlab.org>; Denny Insley <dinsley@jlab.org>; Morgan Cook IV<br>
> <mcookiv@jlab.org><br>
> Subject: Re: [dsg-hallb_rich] [EXTERNAL] Re: Fw: unable to connect to<br>
> RICH N2 cRIO in hall<br>
> <br>
> The cRIO has been swapped out with a spare.<br>
> <br>
> It was a totally Benny Hill show swapping it out with everything that<br>
> could take longer or go wrong doing so, but at least it's complete.<br>
> <br>
> All indicators are green in EPICS so I'm assuming everything is okay,<br>
> but someone else can give it a more thorough check later.<br>
> <br>
> -------------------------<br>
> <br>
> From: Tyler Lemon <tlemon@jlab.org><br>
> Sent: Friday, April 2, 2021 1:22 PM<br>
> To: Brian Eng <beng@jlab.org>; Marco Mirazita<br>
> <Marco.Mirazita@lnf.infn.it><br>
> Cc: dsg-hallb_rich@jlab.org <dsg-hallb_rich@jlab.org>; Bob Miller<br>
> <rmiller@jlab.org>; Denny Insley <dinsley@jlab.org>; Morgan Cook IV<br>
> <mcookiv@jlab.org><br>
> Subject: Re: [dsg-hallb_rich] [EXTERNAL] Re: Fw: unable to connect to<br>
> RICH N2 cRIO in hall<br>
> <br>
> Hi Marco,<br>
> <br>
> Like Brian said, we're in the process of configuring a spare cRIO to<br>
> swap it for the the failed one in Hall B.<br>
> <br>
> We've asked Mark Taylor to verify the hostname of the cRIO at Peter's<br>
> desk so we can get its network settings configured ahead of time.<br>
> Brian will then go in to the lab to swap the cRIOs.<br>
> <br>
> Despite the N2 cRIO being down, we can still see from the EP cRIO<br>
> that the humidity is still low in RICH, low enough to where it is<br>
> below the sensors' capability to measure.<br>
> <br>
> In the meantime, the N2 flow can be verified in person by a Hall B<br>
> Tech if they go up to the top level of the Forward Carriage.<br>
> <br>
> -Tyler<br>
> <br>
> -------------------------<br>
> <br>
> From: Brian Eng <beng@jlab.org><br>
> Sent: Friday, April 2, 2021 10:07 AM<br>
> To: Marco Mirazita <Marco.Mirazita@lnf.infn.it>; Tyler Lemon<br>
> <tlemon@jlab.org><br>
> Cc: dsg-hallb_rich@jlab.org <dsg-hallb_rich@jlab.org>; Bob Miller<br>
> <rmiller@jlab.org>; Denny Insley <dinsley@jlab.org>; Morgan Cook IV<br>
> <mcookiv@jlab.org><br>
> Subject: Re: [dsg-hallb_rich] [EXTERNAL] Re: Fw: unable to connect to<br>
> RICH N2 cRIO in hall<br>
> <br>
> Hi Marco,<br>
> <br>
> I filed a support ticket with NI to see if there was any way to get<br>
> it working without swapping controllers, but they're quite slow with<br>
> replies.<br>
> <br>
> I'll work with Sergey on getting IPs swapped in the mean time.<br>
> <br>
> -------------------------<br>
> <br>
> From: dsg-hallb_rich <dsg-hallb_rich-bounces@jlab.org> on behalf of<br>
> Marco Mirazita <Marco.Mirazita@lnf.infn.it><br>
> Sent: Friday, April 2, 2021 7:59 AM<br>
> To: Tyler Lemon <tlemon@jlab.org><br>
> Cc: dsg-hallb_rich@jlab.org <dsg-hallb_rich@jlab.org>; Bob Miller<br>
> <rmiller@jlab.org>; Denny Insley <dinsley@jlab.org>; Morgan Cook IV<br>
> <mcookiv@jlab.org><br>
> Subject: Re: [dsg-hallb_rich] [EXTERNAL] Re: Fw: unable to connect to<br>
> RICH N2 cRIO in hall<br>
> <br>
> Hi all,<br>
> any update on this? Do you know how much time will be needed to<br>
> replace<br>
> or fix the broken cRIO? If it takes long time, would it be possible to<br>
> <br>
> switch the nitrogen system readout on the one that is now connected to<br>
> <br>
> the EP and is basically not in use?<br>
> Thank you,<br>
> Marco<br>
> <br>
> Il 2021-03-30 18:12 Marco Mirazita ha scritto:<br>
>> Hi Tyler,<br>
>> isn't the alarm system based on the cRIO readings? If so, it cannot<br>
>> work even if it is still enabled.<br>
>> Thank you,<br>
>> Marco<br>
>> <br>
>> <br>
>> <br>
>> Il 2021-03-30 16:39 Tyler Lemon ha scritto:<br>
>>> Hi Marco,<br>
>>> <br>
>>> - do we still have remote access to the information on the<br>
> nitrogen<br>
>>> flow?<br>
>>> <br>
>>> No, the flow can only be remotely read out through that cRIO.<br>
>>> There is a local display on the nitrogen panel on top of the<br>
> forward<br>
>>> carriage someone can read in person.<br>
>>> <br>
>>> - do we still have remote access to the information on the<br>
> humidity<br>
>>> level inside the RICH?<br>
>>> The humidity in the electronic panel can still be read by the EP<br>
>>> cRIO. Those humidity readings are still very low, making me<br>
> confident<br>
>>> that there is still N2 flow to RICH.<br>
>>> <br>
>>> We cannot read the humidity in the nitrogen volume because the<br>
> cRIO<br>
>>> appears to have failed.<br>
>>> <br>
>>> - do we still have the alarm system working?<br>
>>> To my knowledge, all the alarms are still enabled.<br>
>>> <br>
>>> - do we still have the backup system working?<br>
>>> Yes, the backup N2 system is still connected and will provide N2<br>
> if<br>
>>> the main supply pressure stops. This system has no electrically<br>
>>> controlled or remote controlled elements so the backup flow<br>
>>> automatically starts if N2 supply pressure is lost through the use<br>
> of<br>
>>> a normally-open pneumatic valve.<br>
>>> <br>
>>> -------------------------<br>
>>> <br>
>>> From: Marco Mirazita <Marco.Mirazita@lnf.infn.it><br>
>>> Sent: Tuesday, March 30, 2021 10:26 AM<br>
>>> To: Tyler Lemon <tlemon@jlab.org><br>
>>> Cc: Denny Insley <dinsley@jlab.org>; Morgan Cook IV<br>
>>> <mcookiv@jlab.org>; Bob Miller <rmiller@jlab.org>;<br>
>>> dsg-hallb_rich@jlab.org <dsg-hallb_rich@jlab.org>; Valery<br>
> Kubarovsky<br>
>>> <vpk@jlab.org><br>
>>> Subject: [EXTERNAL] Re: [dsg-hallb_rich] Fw: unable to connect to<br>
> RICH<br>
>>> N2 cRIO in hall<br>
>>> <br>
>>> Hi Tyler,<br>
>>> could you please clarify the situation? In particular:<br>
>>> - do we still have remote access to the information on the nitrogen<br>
>>> flow?<br>
>>> - do we still have remote access to the information on the humidity<br>
>>> level inside the RICH?<br>
>>> - do we still have the alarm system working?<br>
>>> - do we still have the backup system working?<br>
>>> Thank you,<br>
>>> Marco<br>
>>> <br>
>>> Il 2021-03-29 14:52 Tyler Lemon ha scritto:<br>
>>>> Hi Denny and Morgan,<br>
>>>> <br>
>>>> Please see the email chain below.<br>
>>>> <br>
>>>> Brian went in to Hall B last week to check the the RICH N2 volume<br>
>>>> cRIO that failed and it looks like the cRIO will have to be<br>
>>> replaced.<br>
>>>> <br>
>>>> Until the cRIO issue is resolved, can Hall B Engineering<br>
>>> periodically<br>
>>>> check the local N2 flow readout for RICH on the top of the forward<br>
>>>> carriage to make sure the detector is still getting appropriate N2<br>
>>>> flow? We're still all working from home and have to make special<br>
>>>> arrangements to go in to the lab.<br>
>>>> <br>
>>>> We can remotely see that the humidity in the RICH electronic<br>
> panel<br>
>>> is<br>
>>>> still very low (below the point we're able to read with the<br>
> humidity<br>
>>>> sensors), but it'd still be good to check the flow meters in case<br>
>>>> something happens to that cRIO.<br>
>>>> <br>
>>>> Thanks.<br>
>>>> <br>
>>>> -Tyler<br>
>>>> <br>
>>>> -------------------------<br>
>>>> <br>
>>>> From: Dsg-internal <dsg-internal-bounces@jlab.org> on behalf of<br>
>>> Tyler<br>
>>>> Lemon <tlemon@jlab.org><br>
>>>> Sent: Monday, March 29, 2021 8:32 AM<br>
>>>> To: Amrit Yegneswaran <yeg@jlab.org>; 'dsg-internal'<br>
>>>> <dsg-internal@jlab.org><br>
>>>> Subject: Re: [Dsg-internal] unable to connect to RICH N2 cRIO in<br>
>>> hall<br>
>>>> <br>
>>>> Remotely, no there is not a way.<br>
>>>> <br>
>>>> If you go up to the top of the forward carriage, there are local<br>
>>>> displays on the flow meters.<br>
>>>> <br>
>>>> -------------------------<br>
>>>> <br>
>>>> From: Dsg-internal <dsg-internal-bounces@jlab.org> on behalf of<br>
>>> Amrit<br>
>>>> Yegneswaran <yeg@jlab.org><br>
>>>> Sent: Monday, March 29, 2021 8:29:04 AM<br>
>>>> To: 'dsg-internal' <dsg-internal@jlab.org><br>
>>>> Subject: Re: [Dsg-internal] unable to connect to RICH N2 cRIO in<br>
>>> hall<br>
>>>> <br>
>>>> thanks brian<br>
>>>> we'll talk about this issue in today's meeting<br>
>>>> is there anyway to see wheteher there is nitrogen flow?<br>
>>>> <br>
>>>> -------------------------<br>
>>>> <br>
>>>> From: Brian Eng <beng@jlab.org><br>
>>>> Sent: Saturday, March 27, 2021 12:15 AM<br>
>>>> To: Amrit Yegneswaran <yeg@jlab.org>; Tyler Lemon<br>
> <tlemon@jlab.org>;<br>
>>>> 'dsg-internal' <dsg-internal@jlab.org><br>
>>>> Subject: Re: unable to connect to RICH N2 cRIO in hall<br>
>>>> <br>
>>>> It wouldn't force boot into safe mode (still the same blinking<br>
>>> status<br>
>>>> LED) nor be detected by MAX when connected via USB or directly<br>
> with<br>
>>> a<br>
>>>> network cable.<br>
>>>> <br>
>>>> Looks like might have to swap the cRIO out, but I'm going to file<br>
> a<br>
>>>> ticket with NI first to make sure there isn't something else I can<br>
>>> do<br>
>>>> locally before doing that since that seems like kind of a pain to<br>
>>> do.<br>
>>>> <br>
>>>> -------------------------<br>
>>>> <br>
>>>> From: Brian Eng <beng@jlab.org><br>
>>>> Sent: Friday, March 26, 2021 12:15 AM<br>
>>>> To: Amrit Yegneswaran <yeg@jlab.org>; Tyler Lemon<br>
> <tlemon@jlab.org>;<br>
>>>> 'dsg-internal' <dsg-internal@jlab.org><br>
>>>> Subject: Re: unable to connect to RICH N2 cRIO in hall<br>
>>>> <br>
>>>> First look isn't good, the status LED on the cRIO is constantly<br>
>>>> blinking which according to the manual means:<br>
>>>> <br>
>>>> The cRIO-9035 has not booted into NI Linux Real-Time. The<br>
> cRIO-9035<br>
>>>> either booted into an unsupported operating system, was<br>
> interrupted<br>
>>>> during the boot process, or detected an unrecoverable software<br>
>>> error.<br>
>>>> <br>
>>>> I did notice that the network went down/up several times along<br>
> with<br>
>>>> it trying to access the SD card, so it seems like it's in some<br>
> sort<br>
>>> of<br>
>>>> boot loop.<br>
>>>> <br>
>>>> I didn't bring the Windows laptop down with me today and it's<br>
> later<br>
>>>> than I planned on being here so I'll try formatting it locally<br>
>>>> tomorrow to see if I can't just get it on the network so that<br>
>>>> Tyler/Pete can reinstall the needed software.<br>
>>>> <br>
>>>> -------------------------<br>
>>>> <br>
>>>> From: Amrit Yegneswaran <yeg@jlab.org><br>
>>>> Sent: Friday, March 19, 2021 4:45 PM<br>
>>>> To: Brian Eng <beng@jlab.org>; Tyler Lemon <tlemon@jlab.org>;<br>
>>>> 'dsg-internal' <dsg-internal@jlab.org><br>
>>>> Subject: Re: unable to connect to RICH N2 cRIO in hall<br>
>>>> <br>
>>>> brian,<br>
>>>> from tyler's e-mail it appears that since there is still N2 so<br>
>>> there<br>
>>>> should be no urgent problem.<br>
>>>> which means you can decide when you wish to go.<br>
>>>> like always late in the evening.<br>
>>>> <br>
>>>> pity the hallb techs aren't able to help.<br>
>>>> <br>
>>>> on the good news aide patrizia, is willing to consider the<br>
> robotic<br>
>>>> version, but we need to come up with a plan on what other project<br>
>>>> (which are on the books we can use the system)<br>
>>>> so all, put on your thinking caps<br>
>>>> <br>
>>>> -------------------------<br>
>>>> <br>
>>>> From: Dsg-internal <dsg-internal-bounces@jlab.org> on behalf of<br>
>>> Brian<br>
>>>> Eng <beng@jlab.org><br>
>>>> Sent: Friday, March 19, 2021 2:48 PM<br>
>>>> To: Tyler Lemon <tlemon@jlab.org>; 'dsg-internal'<br>
>>>> <dsg-internal@jlab.org><br>
>>>> Subject: Re: [Dsg-internal] unable to connect to RICH N2 cRIO in<br>
>>> hall<br>
>>>> <br>
>>>> I can go in and check it tonight if need be.<br>
>>>> <br>
>>>> -------------------------<br>
>>>> <br>
>>>> From: Dsg-internal <dsg-internal-bounces@jlab.org> on behalf of<br>
>>> Tyler<br>
>>>> Lemon <tlemon@jlab.org><br>
>>>> Sent: Friday, March 19, 2021 1:45 PM<br>
>>>> To: 'dsg-internal' <dsg-internal@jlab.org><br>
>>>> Subject: [Dsg-internal] unable to connect to RICH N2 cRIO in hall<br>
>>>> <br>
>>>> Hello,<br>
>>>> <br>
>>>> I'm going to preface this by saying that from the EP cRIO, we can<br>
>>> see<br>
>>>> that the humidity in RICH is still low and at a good level so RICH<br>
>>> is<br>
>>>> still getting N2 without issues.<br>
>>>> <br>
>>>> That being said, I cannot connect to the N2 volume cRIO (hostname<br>
>>>> richcrio) over the network.<br>
>>>> <br>
>>>> Peter noticed this a few days ago and I asked Hall B engineering<br>
> to<br>
>>>> check on the cRIO. Their response was not helpful since they just<br>
>>>> looked at the cRIO chassis from the outside. I have since asked<br>
> them<br>
>>>> to recheck the chassis, looking inside to see if there are any<br>
>>> lights<br>
>>>> flashing inside, but this probably won't be done today.<br>
>>>> <br>
>>>> It seems more likely than not that someone will have to go in to<br>
>>> Hall<br>
>>>> B to check the cRIO.<br>
>>>> <br>
>>>> Since we can still monitor the internal humidity from the EP<br>
> cRIO,<br>
>>> I<br>
>>>> don't think this is something that has to be absolutely taken care<br>
>>> of<br>
>>>> right this movement.<br>
>>>> <br>
>>>> Should I start the process of getting approval to go in myself?<br>
> Or<br>
>>>> would Brian be able to check the cRIO?<br>
>>>> <br>
>>>> -Tyler<br>
>>>> _______________________________________________<br>
>>>> dsg-hallb_rich mailing list<br>
>>>> dsg-hallb_rich@jlab.org<br>
>>>> <a href="https://mailman.jlab.org/mailman/listinfo/dsg-hallb_rich">https://mailman.jlab.org/mailman/listinfo/dsg-hallb_rich</a><br>
>>> _______________________________________________<br>
>>> dsg-hallb_rich mailing list<br>
>>> dsg-hallb_rich@jlab.org<br>
>>> <a href="https://mailman.jlab.org/mailman/listinfo/dsg-hallb_rich">https://mailman.jlab.org/mailman/listinfo/dsg-hallb_rich</a><br>
>> _______________________________________________<br>
>> dsg-hallb_rich mailing list<br>
>> dsg-hallb_rich@jlab.org<br>
>> <a href="https://mailman.jlab.org/mailman/listinfo/dsg-hallb_rich">https://mailman.jlab.org/mailman/listinfo/dsg-hallb_rich</a><br>
> _______________________________________________<br>
> dsg-hallb_rich mailing list<br>
> dsg-hallb_rich@jlab.org<br>
> <a href="https://mailman.jlab.org/mailman/listinfo/dsg-hallb_rich">https://mailman.jlab.org/mailman/listinfo/dsg-hallb_rich</a><br>
> _______________________________________________<br>
> dsg-hallb_rich mailing list<br>
> dsg-hallb_rich@jlab.org<br>
> <a href="https://mailman.jlab.org/mailman/listinfo/dsg-hallb_rich">https://mailman.jlab.org/mailman/listinfo/dsg-hallb_rich</a><br>
</div>
</span></font></div>
</div>
</body>
</html>