Hello EPICS motor record users,
Has anyone used (or is currently using) the motor record with the
OMSL field set to "closed-loop"?
If not, I plan on removing it from the motor record with the next
"major" release (i.e. R6-5).
Here at the APS, we use save/restore to preserve the motor record's
DVAL through a reboot or power-cycle. Setting the OMSL to
"closed-loop" has the undesirable effect of preserving DVAL,
but leaving the VAL and RVAL fields to their default values; zero.
Since incremental moves (tweaks) are done from user coordinates
(i.e. the VAL field), an incremental move after a reboot would
cause the motor to move, unexpectedly, to near the zero position.
Since I am unaware of any use for the OMSL field to be set to
"closed-loop", I strongly recommend that motor record users leave
this field in its' default "supervisory" state.
Ron
- Replies:
- Re: Motor Record OMSL field Ron Sluiter
- Navigate by Date:
- Prev:
Re: subArray processing Carl Lionberger
- Next:
EDM Properties Windows Aaron Joos
- 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: catools for cross compiled target Hinko Kocevar
- Next:
Re: Motor Record OMSL field Ron Sluiter
- 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
|