[Dsg-mvt] MVT with premix in hall B

[Brian Eng]

It's close to what I was looking for, but not quite it.

It sounds like that could go bad if the flows don't match (i.e. there is a leak in the detector), but that's not the same thing as them wanting flow or not.

I was hoping there was something that was on/off indicating we should be sending mixed gas or not.

----- Original Message -----
> From: "Nathan Baltzell" <baltzell at jlab.org>
> To: "BERTRAND Quentin" <Quentin.BERTRAND at cea.fr>
> Cc: "Brian Eng" <beng at jlab.org>, "mdefurne" <mdefurne at jlab.org>, "Guillaume Christiaens" <guillaum at jlab.org>,
> dsg-mvt at jlab.org
> Sent: Monday, November 13, 2017 12:42:34 PM
> Subject: Re: [Dsg-mvt] MVT with premix in hall B

> Thanks Quentin,
> 
> I think that might be what Brian wants.  Combined with testing the .STAT field
> for READ error (value = 3).
> 
> -Nathan
> 
> 
>> On Nov 13, 2017, at 12:36, BERTRAND Quentin <Quentin.BERTRAND at cea.fr> wrote:
>> 
>> Hi Nathan,
>> 
>> FLOW_STAT means that IN_FLOW and OUT_FLOW corresponds to the SETPOINT when it is
>> 1.
>> 
>> Quentin
>> ________________________________________
>> De : Nathan Baltzell [baltzell at jlab.org]
>> Envoyé : lundi 13 novembre 2017 18:02
>> À : Brian Eng
>> Cc : mdefurne; Guillaume Christiaens; BERTRAND Quentin; dsg-mvt at jlab.org
>> Objet : Re: [Dsg-mvt] MVT with premix in hall B
>> 
>> Quentin,
>> 
>> What exactly does FLOW_STAT mean?   Looks like it’s at word 32, 11th bit.
>> 
>> -Nathan
>> 
>> {P,              R,             PORT,   OFFSET, MASK,       ZNAM,   ONAM,   ZSV,
>> OSV,        SCAN}
>> {B_DET_BMT_GAS_, FLOWDIFF_FLT,  R505,   32,     1,          Ok,     Fault,
>> NO_ALARM,   MAJOR,      "I/O Intr"}
>> {B_DET_BMT_GAS_, INFLOW_FLT,    R505,   32,     2,          Ok,     Fault,
>> NO_ALARM,   MAJOR,      "I/O Intr"}
>> {B_DET_BMT_GAS_, OVRFLOW_FLT,   R505,   32,     4,          Ok,     Fault,
>> NO_ALARM,   MAJOR,      "I/O Intr"}
>> # FLOW_START    8
>> # FLOW_STOP     16
>> # <empty>       32
>> # <empty>       64
>> # <empty>       128
>> {B_DET_BMT_GAS_, GEN_WRN,       R505,   32,     256,        Ok,     Fault,
>> NO_ALARM,   MAJOR,      "I/O Intr"}
>> {B_DET_BMT_GAS_, GEN_FLT,       R505,   32,     512,        Ok,     Fault,
>> NO_ALARM,   MAJOR,      "I/O Intr"}
>> {B_DET_BMT_GAS_, FLOW_STAT,     R505,   32,     1024,       Fault,  Ok,
>> MAJOR,      NO_ALARM,   "I/O Intr"}
>> {B_DET_BMT_GAS_, PRES_WRN,      R505,   32,     2048,       Ok,     Fault,
>> NO_ALARM,   MAJOR,      "I/O Intr"}
>> {B_DET_BMT_GAS_, INFLOW_WRN,    R505,   32,     4096,       Ok,     Fault,
>> NO_ALARM,   MAJOR,      "I/O Intr"}
>> {B_DET_BMT_GAS_, OVRFLOW_WRN,   R505,   32,     8192,       Ok,     Fault,
>> NO_ALARM,   MAJOR,      "I/O Intr"}
>> {B_DET_BMT_GAS_, FLOWDIFF_WRN,  R505,   32,     16384,      Ok,     Fault,
>> NO_ALARM,   MAJOR,      "I/O Intr"}
>> {B_DET_BMT_GAS_, PRES_FLT,      R505,   32,     32768,      Ok,     Fault,
>> NO_ALARM,   MAJOR,      "I/O Intr”}
>> 
>> 
>> 
>>> On Nov 13, 2017, at 08:58, Brian Eng <beng at jlab.org> wrote:
>>> 
>>> Yes, a normally off/false boolean(s) that indicates if any of the MVT detectors
>>> need gas would be what I'm looking for.
>>> 
>>> The *_INFLOW_SET PVs will work just fine for calculating the mixing flow.
>>> 
>>> Basically I'm trying to see if there is something that will handle the failure
>>> case right now, the PLC is offline, but the PVs still have numbers in them. So
>>> right now if we had gas it would be trying to flow it despite the gas not
>>> actually being required.
>>> 
>>>> On Nov 10, 2017, at 7:36 PM, Nathan Baltzell <baltzell at jlab.org> wrote:
>>>> 
>>>> Hello All,
>>>> 
>>>> These EPICS pvs suffixed by SET are the setpoints used by the PLC when it is
>>>> actually flowing gas.  And the START/STOP ones are control outputs from EPICS
>>>> to the PLC.  I doubt any of those should be used for trying to understand the
>>>> live status of the gas flow.
>>>> 
>>>> The pvs suffixed by INFLOW/OUTFLOW are readbacks on measured flows.  But I
>>>> suspect Brian wants a boolean status for gas flow?  The FLT (fault) column on
>>>> that screen may also be useful (see attached screenshot).  Depends on what
>>>> logic you want here.  Also, it’s on my todo list to add a summary PV (on ‘OR’
>>>> of all faults) and add it to the overview screen for shift workers and alarms.
>>>> If that will be useful here, I’ll do it ASAP.  Or let’s define what exactly
>>>> you want from EPICS for this and we’ll make it happen.
>>>> 
>>>> Quentin is the PLC expert on all this and defined the PLC-EPICS communications
>>>> that Wesley wrote.
>>>> 
>>>> Ok, that is my understanding of things.
>>>> 
>>>> Cheers,
>>>> Nathan
>>>> 
>>>> 
>>>> P.S.  PLC appears to be offline currently, but:
>>>> https://hallbopi.jlab.org/webopi3.3/w?opi=CLAS12_Menu-web.opi
>>>> click CVT->BMTGas for live readings