EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Re: copying of monitored data
From: "Jeff Hill" <[email protected]>
To: "Marty Kraimer" <[email protected]>, <[email protected]>
Date: Tue, 10 Jun 1997 16:11:43 -0600
> HOWEVER,
> 
> The biRecord.c support code is not incorrect because there get_enum_str,
> put_enum_str, get_enum_strs will ONLY get called if the field type
> in question is DBF_ENUM. The only such field in the biRecord is VAL.
> Many record support modules in base make this assumption.
> 

Yes, but PV values in the CA server monitor queue will be ignored in favor
of the current value in the record if we leave the code as it is today.
Therefore, clients that monitor the .VAl field of a bo record as a
string will see the sequence of events "on off on" converted
to "on on on" if the events are spaced closely together in time.

Explanation:
This is because, when dbGetField() is called, the dbAddr structure 
is pointing at the value on the CA monitor queue and not at the 
.VAL field. The bo record's get_enum_str() routine ignores the 
dbAddr structure passed in and always converts  the VAL field
to a string (returning the current and not the historic value of
the .VAL field).

Jeff

Replies:
Re: copying of monitored data Marty Kraimer

Navigate by Date:
Prev: Re: IOC hangs (scanOnce crashes) Chip Watson
Next: Re: IOC hangs (scanOnce crashes) Ralph Lange
Index: 1994  1995  1996  <19971998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: copying of monitored data Marty Kraimer
Next: Re: copying of monitored data Marty Kraimer
Index: 1994  1995  1996  <19971998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·