Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: Re: EPICS Python client application survey
From: Benjamin Franksen <benjamin.franksen@bessy.de>
To: tech-talk@aps.anl.gov
Date: Thu, 1 Oct 2009 15:03:54 +0200
On Thursday 01 October 2009, Michael Abbott wrote:
> On Wed, 30 Sep 2009, Andrew Johnson wrote:
> >  * DBE_PROPERTY events.  Generated now on the VAL field of the mbb[io]
> > record types when someone changes one of the *ST fields, a DBE_PROPERTY
> > monitor allows a client to always know what the current ENUM strings
> > are.
>
> I guess that's easy enough: presumably if the DBE_PROPERTY bit is set in
> a CA request to a pre .14.11 server it'll have no effect, 

I'd think so.

> so I guess I
> can just add DBE_PROPERTY to my list of event types.

The idea is that you can set up two monitors: one with a simple DBR_ENUM (or 
DBR_ST_ENUM or DBR_TIME_ENUM) for frequent value and/or status changes 
(DBE_VALUE|DBE_STATUS); and another one with the full DBR_CTRL_ENUM for the 
(hopefully) very infrequent changes of the enumeration strings (requesting 
/only/ events of type only DBE_PROPERTY). Which means you save network 
bandwidth and IOC cpu load as compared to only one monitor requesting 
DBR_CTRL_ENUM for all event types.

Cheers
Ben

References:
Re: EPICS Python client application survey Andrew Johnson
Re: EPICS Python client application survey Michael Abbott

Navigate by Date:
Prev: RE: state notation code flags Mark Rivers
Next: Re: EPICS Python client application survey Michael Abbott
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
Navigate by Thread:
Prev: Re: EPICS Python client application survey Michael Abbott
Next: Re: EPICS Python client application survey Michael Abbott
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·