Hi,
Thanks to all your replies. I'd reply once here.
> Was the final position reached? Or did the motor stop just outside the
deadband RDBD?
Yes. The actual position is reached.
> Are you able to do another move after you 'prod' the record?
Yes. It can still drive the motor to the correct position.
> Does this happen every time on the same axes, or intermittently?
Every time with the same axes.
>To help diagnose this it might be worth turning on Asyn tracing for
that
>axis, like:
>asynSetTraceIOMask("PORTNAME",{card_no},255)
>asynSetTraceMask("PORTNAME",{card_no},255)
I have redirect the output to file. From there I can say the
communication is correct.
MS and TP command return correct information.
>Might be worth updating to asynMotor from 6-4-2 as well.
This is also what Ron has suggested.
I will try first use the new release. But because the way how drivers
are used in SLS,
it requires some time to setup. I will get back to you then.
Thanks all.
Xiaoqiang
- Replies:
- RE: MM4000 asynMotor problem Wang Xiaoqiang
- References:
- MM4000 asynMotor problem Wang Xiaoqiang
- RE: MM4000 asynMotor problem Pearson, MR (Matthew)
- Navigate by Date:
- Prev:
RE: MM4000 asynMotor problem Pearson, MR (Matthew)
- Next:
RE: MM4000 asynMotor problem Wang Xiaoqiang
- 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: MM4000 asynMotor problem Pearson, MR (Matthew)
- Next:
RE: MM4000 asynMotor problem Wang Xiaoqiang
- 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
|