Hi again,
I quickly made a setup running motor 6-4-2 release. The problem is still
there.
But I seem to get a little clue.
I have 3 three such controllers and two works just fine. With the well
functioned
controller, when one axis is reported as "motor in moton", I try to move
any
other axis and this axis will end up with MIP=0x420 and DMOV is never
reset.
On the problemic controller, the first axis' MSTA field is 0xa0a when
idling.
According to the motor doc, it means "PROBLEM: driver stopped polling".
(Which is
not true, because it can be moved and position is reported correctly and
even DMOV field.)
Would this false status report affect the other axis?
How do I know why the first axis is reported as "PROBLEM", while the
polling is correct.
Where should I put diagnostic messages?
Thanks.
Xiaoqiang
- Replies:
- Re: MM4000 asynMotor problem J. Lewis Muir
- References:
- MM4000 asynMotor problem Wang Xiaoqiang
- RE: MM4000 asynMotor problem Pearson, MR (Matthew)
- RE: MM4000 asynMotor problem Wang Xiaoqiang
- Navigate by Date:
- Prev:
RE: MM4000 asynMotor problem Wang Xiaoqiang
- Next:
Re: MM4000 asynMotor problem J. Lewis Muir
- 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 Wang Xiaoqiang
- Next:
Re: MM4000 asynMotor problem J. Lewis Muir
- 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
|