[Fwd: Re: MM4000 asynMotor problem]

[Ron Sluiter <sluiter@aps.anl.gov>]

-------- Original Message --------
Subject: 	Re: MM4000 asynMotor problem
Date: 	Fri, 13 Mar 2009 08:35:41 -0500
From: 	Ron Sluiter <sluiter@aps.anl.gov>
To: 	Wang Xiaoqiang <Xiaoqiang.Wang@psi.ch>
References: 	<67F374811ED3544C8543E6C0EE5EAA4B021DDCD2@MAILBOX0B.psi.ch>



Hello Xiaoqiang,

There were some major problems with the asynMotor device driver
architecture that have been fixed and only recently released.
The following is from the most recent Release Notice; 
<http://www.aps.anl.gov/bcda/synApps/motor/R6-4/motor_release.html>

> _*asyn motor archtecture updates*_
>
> # Motor record GET_INFO commands were not supported by the asyn motor 
> archtecture in previous releases.
> # A motor record bug was fixed that caused unscheduled retries to occur 
> with asyn motor.
I suspect that the 1st item above may be causing the problem described.

Although the most recent motor record release (R6-4-2) is not without
problems, I suggest that you update to that release and see if it fixes the
problem you are seeing.
_*
*_Thank you for contacting me.  You are the 1st person I know of that is
using the MM4000 asynMotor support.  Please let me know if the R6-4-2
motor record version resolves this problem and if you experience any
other motor record related problems, specifically, any problem with the
MM4000 asynMotor support.

Best regards,
Ron

Wang Xiaoqiang wrote:
> Hi,
>
> I use MM4000 asynMotor driver to control Newport MM4006 controllers. 
> The movements are done correctly. 
>
> But for certain axis/axes, the DMOV field does not reset to 1 after
> position is reached. 
> I poll the controller status using "MS" command, which reports the axis
> is not moving. 
> Also the MOVN field is going through 0->1->0 sequence correctly.
>
> Other fields when this happens:
> MSTA - 0x80a
> MIP  - 0x420
> >From the MIP field, it is waiting for a Delay callback, which never
> comes?
>
> To reset DMOV field, I can write 1 to PROC field or any field any can
> process
> the record but without moving the motor, e.g. SPMG field.
>
> I am using motor 6-2-2 release for asynMotor device support, 
> but the MM4000 driver is updated to 6-4-2.
>
> Many thanks.
> --
> Dr. Xiaoqiang Wang
> Paul Scherrer Institut, WBGB/010
> 5232 Villigen PSI, Switzerland
>
>