The motor record issues absolute move command if UEIP and URIP are both
0. It issues relative move commands if UEIP or URIP is 1.
Kevin
On 9/29/20 8:04 AM, Guilherme Jovanini Montagner via Tech-talk wrote:
> It seems that EPICS is issuing "absolute" movements, instead of
> "relative". Commanded position of 3mm shouldn't result in a target of
> 307200 counts for motor 1, but should issue an incremental movement of
> 0,7mm (in this situation), or +71680 counts, and after that, the DIFF
> field should be considered in order to issue further movements
>
> What can justify this behaviour? Did we implement this technique correctly?
> Thank you for your attention.
>
> *Guilherme Jovanini Montagner*
> +55 19 99806.9117
> +55 19 2517.8911
> guilherme at setup.com.br
>
> Labview Certified Developer
>
> ------------------------------------------------------------------------
- Replies:
- Re: Implementing closed loop on EPICS level Guilherme Jovanini Montagner via Tech-talk
- References:
- Implementing closed loop on EPICS level Guilherme Jovanini Montagner via Tech-talk
- Navigate by Date:
- Prev:
Re: Implementing closed loop on EPICS level Bruno Martins via Tech-talk
- Next:
Re: Implementing closed loop on EPICS level Guilherme Jovanini Montagner via Tech-talk
- 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: Implementing closed loop on EPICS level Bruno Martins via Tech-talk
- Next:
Re: Implementing closed loop on EPICS level Guilherme Jovanini Montagner via Tech-talk
- 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
|