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  2012  2013  2014  2015  2016  <2017 Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
<== Date ==> <== Thread ==>

Subject: Re: issue with either camonitor or pcaspy in 3.15?
From: Jameson Graef Rollins <jrollins@ligo.caltech.edu>
To: Wang Xiaoqiang <xiaoqiang.wang@psi.ch>, EPICS tech-talk <tech-talk@aps.anl.gov>
Date: Mon, 20 Nov 2017 13:49:44 -0800
On Mon, Nov 20 2017, Wang Xiaoqiang <xiaoqiang.wang@psi.ch> wrote:
> The UDF (UnDeFined) alarm and INVALID severity is to indicate the values 
> are default values, have not got updated by the driver. This is the same 
> behavior as the EPICS database gets initialized on start-up.
>
> Calling setParamStatus to clear the alarm status is all correct. It is 
> then necessary to call driver.updatePVs() to inform ca clients with a 
> DBE_ALARM event update. Otherwise this update event will be delayed 
> until the next driver.updatePVs() call. And in PCASpy 0.6+, every caput 
> triggers a call to driver.updatePVs(). That explains seeing all four 
> updates together, in which channel A gives a value update and B,C,D give 
> an alarm update.
>
> To conclude, it is an incompatible change introduced in PCASpy 0.6. I 
> created an issue to track this.
> https://github.com/paulscherrerinstitute/pcaspy/issues/48
>
> In any case, it is best to explicitly call driver.updatePVs() after 
> calling setParam, setParamStatus, setParamEnums, setParamInfo. I will 
> add this the docs.

Thanks, Xiaoqiang.  This is all very useful info, and adding it to the
documentation would be great.  I'll add updatePVs() to my code where
needed.

jamie.

Attachment: signature.asc
Description: PGP signature


References:
issue with either camonitor or pcaspy in 3.15? Jameson Graef Rollins
Re: issue with either camonitor or pcaspy in 3.15? Wang Xiaoqiang
Re: issue with either camonitor or pcaspy in 3.15? Jameson Graef Rollins
Re: issue with either camonitor or pcaspy in 3.15? Wang Xiaoqiang

Navigate by Date:
Prev: RE: Possible bug in areaDetector/ADSupport/supportApp/nexusSrc/Makefile? Mark Rivers
Next: synApps_5_8 compilation error Mrinal Kanti Bera
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
Navigate by Thread:
Prev: Re: issue with either camonitor or pcaspy in 3.15? Wang Xiaoqiang
Next: Anyone else using Bira Ethernet Power Supply Controllers? Dunning, Michael
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
ANJ, 21 Nov 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·