Another thought related to this topic.
The EPICS "motor" record currently uses the "Reject" model if a request is
made to move past a soft limit. However, it does set a field, .LVIO (Limit
Violation) if a move request is made that would violate the soft limits
(.LLM, .HLM), so there is an "alarm" visible on operator interfaces (but I
think it does not really raise alarms, those are set by checking against the
standard .LOW, .HIGH, etc. fields). Generally I think that "Reject" is the
desired behavior, because the invalid request is likely due to operator
error.
However, just last week I had to modify the SNL program for our
monochromator in order to implement the "Clamp" behavior, moving to the soft
limit if the calculated position for a motor was beyond the soft limit. It
would also be nice if the motor record could be switched between the two
modes (Reject or Clamp) that are being discussed for the ao record. My
point is that this is a more general problem than "ao" and it would be nice
to agree to a solution that can be slowly propogated to other records.
Mark Rivers
- Navigate by Date:
- Prev:
Re: AO: Drive Limit Mode Bob Dalesio
- Next:
Re: NAN and [email protected] Marty Kraimer
- 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: Drive Limit Mode Andreas Luedeke
- Next:
Problem with iocsh prompt Rarback, Harvey
- 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
|