Re: put to disabled records and monitors

[Andrew Johnson <anj@aps.anl.gov>]

Hi Dirk,

On 2012-08-31 Dirk Zimoch wrote:
> Tim Mooney wrote:
> > By the way, you can do a more thorough job of disabling a record by
> > writing 1 to DISP ("Disable putField"), in addition to disabling
> > processing via SDIS or DISA.  (But note that DISP==1 means you can't
> > write to the DISA field, so you have to write to DISA, DISP, DISA in that
> > order.)
> 
> That's the opposite of what we need :-)
> 
> The record has to be configured before it starts its work. That means
> putting values to several fields (VAL and others).

Tim has explained that the behavior that's coded into dbPut() (although 
possibly not ideal) is necessary for the design we have at the moment.  Can 
you configure the EPID to fetch its setpoint through STPL from another record 
which is the one the user actually sets?

I think the fundamental problem is that the epid.VAL field is being used as an 
input, whereas the dbPut() design was really for VAL as an output.  The 
easiest fix might be to add another field (say STPT) that can be used to give 
the epid it's set-point, mark as VAL SPC_NOMOD and copy STPT to VAL whenever 
the record is processed with SMSL set to Supervisory (when STPL is not used).

- Andrew
-- 
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte