re...,
> Some users here at LANL had a suggestion that's actually useful.
>...
> The problem is about entering "wrong" values from a GUI,
> that is values outside of [DRVL, DRVH].
> Per default, the AO record would "clamp" the value, e.g.
> Value > DRVH ==> value = DRVH.
>
> This can lead to jumps. Example: [DRVL,DRVH]=[0...10], current value 0.5.
> User wants to make it 0.6 but accidentally enters 60
> ==> You jump to 10. That's a big jump from 0.5!
> Just staying at 0.5 and allowing the user to try again
> might be better.
>...
> Solution: New AO field DRLM - "Drive Limit Mode"
> Possible Values:
>
> a) "Clamp" (default)
> As before, any value outside of DRVL ... DRVH
> is clamped/changed to DRVL or DRVH.
>
> b) "Reject"
> Any value outside of DRVL ... DRVH
> is rejected. The record returns to the
> previous value (still available in the OVAL field).
That would be nice. I'd even argue that "reject" should become the
default. It would be confusing, though, if you wrote "10.0" to a
record whose DRVH appeared (PREC=1) to be "10.0" but actually was
"9.996". A user would want some indication of why the value was being
ignored, or they'd just reboot the crate and claim EPICS had "crashed".
Tim Mooney ([email protected]) (630)252-5417
Beamline Controls & Data Acquisition Group
Advanced Photon Source, Argonne National Lab.
- Navigate by Date:
- Prev:
Re: AO Record: New Drive Limit Mode? J. Frederick Bartlett ([email protected])
- Next:
Re: AO Record: New Drive Limit Mode? Andrew Johnson
- 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: AO Record: New Drive Limit Mode? Bob Dalesio
- Next:
RE: AO Record: New Drive Limit Mode? Redman, Russell O.
- 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
|