Re: A general question about convert e.g. in longout record drvh, drvl handling

["Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov>]

An option that doesn’t depend on DRVL/DRVH at all is this:

record(longout, zero) {

  field(LOLO, -1)

  field(LLSV, INVALID)

  field(HIHI, 1)
  field(HHSV, INVALID)
  field(IVOA, "Set output to IVOV")
  field(IVOV, 0)

}

If VAL gets set to any value other than 0 by any means, the record will go into Invalid alarm and the IVOA action will reset VAL back to 0 when the record processes. You also get a nice HIHI or LOLO Invalid alarm severity if someone tries to change it, in case that interests you.

You might want to set DISP to 1 to prevent anyone modifying the fields in the first place though.

- Andrew

On Jan 27, 2021, at 5:53 AM, Heinz Junkes via Core-talk <core-talk at aps.anl.gov> wrote:

Yes, the Idea with DOL/OMSL is a good one ;-)

And thanks for the clear answer about drvl = drvh = 0.
Unfortunately I had not thought of that at that moment. Makes total sense.

But maybe it would be worth to exclude the "0" (default) in the convert
or to give a warning when loading the db file with DRVH = DRVL (!0)?

Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.

On 27. Jan 2021, at 12:08, Ralph Lange via Core-talk <core-talk at aps.anl.gov> wrote:

On Wed, 27 Jan 2021 at 11:56, Heinz Junkes via Core-talk <core-talk at aps.anl.gov> wrote:
I have defined a longout record and wanted to achieve that you can set exactly only one value.

Wouldn't a constant DOL and OMSL set to supervisory achieve that?

Cheers,
~Ralph

-- 

Complexity comes for free, simplicity you have to work for.