Experimental Physics and
Industrial Control System

"Wang Xiaoqiang" <[email protected]> · Fri, 13 Mar 2009 23:50:53 +0100

Thanks Lewis.
The version strings are the same "MM4006X Controller Version 6.03b date
02-18-2002"
Also the MSTA field is false only for the first axis of that controller.

Xiaoqiang

-----Original Message-----
From: J. Lewis Muir [mailto:[email protected]] 
Sent: Friday, March 13, 2009 6:25 PM
To: Wang Xiaoqiang
Cc: Pearson, MR (Matthew); epics; Mark Rivers; Ronald L. Sluiter
Subject: Re: MM4000 asynMotor problem

On 3/13/09 11:53 AM, Wang Xiaoqiang wrote:
>  
> 
> 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.

Hi, Xiaoqiang.

Are the firmware versions of the three controllers the same?

I had a problem a while back with the Mclennan PM304 motor module driver
where it wasn't working right.  The problem turned out to be that the
status bits from the controller had different meanings for different
firmware versions (motorApp/MclennanSrc/drvPM304.cc).

Lewis

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System