<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<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);">
Hi Marco,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The sensor locations map has not been updated for RICH-2. <br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I've been working on the sensor mapping for the nitrogen volume, but I do not have the sensor locations for the electronic panel.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The sensors jumping to a high number (130 C) is an indication of communication error. When the interlock system evaluates the data from the sensors, it also performs a checksum check to ensure that the data is correct. If the data is not correct, it ignores
that value. These communication errors will most likely be resolved by reterminating the cables. I can get the cables to Mindy whenever the current air-cooling tests are completed and the electronic panel is opened up again.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The timestamping is something I'm looking into. I already know that there is an offset in relation to the EPICS archiver that sometimes causes an issue. I hope to have a permanent solution to this in the next few days by setting up the interlock system's controller
to be synchronized to JLab's time server.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Also as an extra side note, I noticed that the airflow 2 reading was zero in the hardware interlock system while the local flow meter display was about 350 slm. I expect it's just a loose connection inside the chassis. I'll look at this once the air-cooling
tests are complete since I may need to power off the interlock system chassis.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
-Tyler<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Marco Contalbrigo <mcontalb@fe.infn.it><br>
<b>Sent:</b> Thursday, May 12, 2022 4:20 PM<br>
<b>To:</b> Tyler Lemon <tlemon@jlab.org><br>
<b>Cc:</b> dsg-hallb_rich@jlab.org <dsg-hallb_rich@jlab.org><br>
<b>Subject:</b> [EXTERNAL] Few questions on slow control/interlock</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi Tyler,<br>
I collect below few things would be nice to clarify<br>
on the slow control monitors:<br>
<br>
- is the "Sensor Location" map updated for RICH2 ?<br>
we do find sensors present both in the EPanel and<br>
N2 volume (i.e. H4, H6, H13), and labels and values<br>
different from "Sensor and limit monitoring" list.<br>
We would need to know the location to trace the<br>
possible difference in the trends during the test.<br>
<br>
- in strip charts INTLK temperature shows often<br>
overflow values that appear to be fake (we do<br>
not see in "Sensor and limit monitoring" and no<br>
interlock shutdown occurs). Still they are annoying<br>
while comparing the trends and in some cases (T3)<br>
they hampers any visualization. Do you know the<br>
origin ?<br>
<br>
- in strip charts there is a mismatch in time between<br>
the SSP and INTLK temperature measurement: the INTLK<br>
appears with a 10 minutes delay. Not a big issue,<br>
but still surprising.<br>
<br>
Thanks, Marco.<br>
</div>
</span></font></div>
</body>
</html>