EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: put to disabled records and monitors
From: "Pal Trivan" <[email protected]>
To: "Andrew Johnson" <[email protected]>, <[email protected]>, "Zimoch Dirk" <[email protected]>
Date: Fri, 31 Aug 2012 21:54:53 +0200
Dear Andrew, Tim and Dirk,
 
Indeed, this is 'excatly' what I am doing, and it works 'fine', in the prototype setup, before being put into production.
The reason why it took me time to get to the SMSL/STPL construct for the setpoint (VAL) is because we had, unfortunately, an 'old' version of SynApps installed, which had a type mismatch error, and could not change VAL via the record pointed to by the STPL field.
Last week, I communicated with Mark, and then Dirk kindly patched this correctly at our installation, in record time.
 
I am not an expert as Dirk is on the 'inners' of EPICS, thus he has been kindly communicating with yourselves, also on my behalf !
 
Many thanks, and we'll keep you posted in case of other issues.
 
Sincerely,
 
Trivan Pal
GFA Controls
PSI
 

________________________________

From: [email protected] on behalf of Andrew Johnson
Sent: Fri 8/31/2012 6:21 PM
To: [email protected]
Subject: Re: put to disabled records and monitors



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




References:
Re: put to disabled records and monitors Tim Mooney
Re: put to disabled records and monitors Dirk Zimoch
Re: put to disabled records and monitors Andrew Johnson

Navigate by Date:
Prev: asyn R4-20 available Mark Rivers
Next: Re: Mass PV assign and event flag sync [was: Creating INLINK/OUTLINK in record support] Andrew Johnson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: put to disabled records and monitors Andrew Johnson
Next: nsls2 debian repository news Michael Davidsaver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·