Hi all,
So I've just about finished a new device support and record set
involved in my current project, and I am sitting looking at the how to
handle when to raise monitors.
The IOC dev guide says that record support should *NOT* call
db_post_event() for values that do not change. So I've started coding in
the check for each value held by the record, and I stooped, probably
because its Friday, and looked at why.....
The record and its connected device have over 100 monitorable
fields, and if any one changes, there will be changes in almost 80 other
fields, so to the point...
Will I break anything by posting a monitor for the 20 or so
remaining field that have not changed ?
I will of course incur the network load for 20 extra fields, but
what other costs are there. Or is posting on a no change just bad enough
practice that it should not be done for any reason ?
--Bill
--
Bill Nolan
Washington University Medical School
Department of Biochemistry
4566 Scott Ave.
Mail Stop 8231
St. Louis, Mo 63110
1.314.362.4445 Fax 1.314.362.7183
- Replies:
- Re: "Best Pratice" on Monitors Tim Mooney
- Navigate by Date:
- Prev:
Re: EPICS source Documentation Andrew Johnson
- Next:
RE: EPICS source Documentation - Bloviation inside - don't open unless you want to waste the time Gurd, Pamela A.
- 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
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: EPICS source Documentation Andrew Johnson
- Next:
Re: "Best Pratice" on Monitors Tim Mooney
- 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
2018
2019
2020
2021
2022
2023
2024
|