Hi,
> Use DRVH & DRVL so that the database rejects out of range values
> rather than relying on the client application to do this.
Just a side note about AO limit checking and monitor updates. If an AO is already at a DRV limit and the user types in a value beyond the DRV limit, the ao record processes and correctly sets the value back to the DRV limit but if MDEL is set to 0, the record will NOT post a monitor. However, depending on how the CA client gui is programmed (say if it only updates on monitor change), it may leave the user's new value showing. I think most EPICS gui clients are OK but to be safe, for AO records that aren't knobbed or periodically processed, I set MDEL to -1 so it updates whenever if processes. You may want to test that your gui's do the right thing and override the user's value with the last value in this case.
Stephanie Allison
- Navigate by Date:
- Prev:
Re: EDM and Text Control Ralph Lange
- Next:
seq 2.0.10 Laznovsky, 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
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: EDM and Text Control Ralph Lange
- Next:
RE: EDM and Text Control Gavin Smith
- 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
|