EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: [Fwd: Re: MM4000 asynMotor problem]
From: Ron Sluiter <[email protected]>
To: EPICS <[email protected]>
Date: Fri, 13 Mar 2009 12:53:10 -0500
-------- Original Message --------
Subject: 	Re: MM4000 asynMotor problem
Date: 	Fri, 13 Mar 2009 08:35:41 -0500
From: 	Ron Sluiter <[email protected]>
To: 	Wang Xiaoqiang <[email protected]>
References: 	<[email protected]>



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



Navigate by Date:
Prev: Re: MM4000 asynMotor problem J. Lewis Muir
Next: RE: Difficulty with edm installation Kevin Anderson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  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: Utter Newbie: Can't get simple app going! Jason Tiller
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·