Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 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
<== Date ==> <== Thread ==>

Subject: Re: How to support a new stepper motor controller?
From: Rod Nussbaumer <bomr@triumf.ca>
To: <tech-talk@aps.anl.gov>
Date: Tue, 7 Feb 2017 10:25:08 -0800
We've gone that route (streamDevice) for the relatively pedestrian requirements for the Galil motor controllers we use. No coordinated motion, or programmed movements; just discrete single axis motion with switches at each limit. The polling generates a lot of traffic, so we put the controllers on dedicated LANs. We did attempt to provide functionality that is similar to the motor record functions that we previously used in older applications with OMS VME motor controllers, by using logic in EPICS base records.

So far, we've only encountered a few hiccups and were able to address them easily.

Rod Nussbaumer
TRIUMF
Vancouver, Canada


On 02/07/2017 09:04 AM, Kevin Peterson wrote:
In general, the recommendation to write a model 3 driver is a good one.
Under some circumstances, however, that is far from the easiest option.

If the controller doesn't have a status command that allows queries of
the moving state, it can be awkward and inefficient to make the model 3
driver work well with the motor record, which expects the driver to
reliably set the done bit of the MSTA field.

If the goal is EPICS support and the motor record is not required, I
have found that StreamDevice support
(http://epics.web.psi.ch/software/streamdevice/) is a much better fit
and significantly easier to write.

Kevin

On 2/7/17 3:53 AM, Ralph Lange wrote:
Dear motion specialists,

I am writing on behalf of Paramveer Jain (in CC) who has contacted me
with this issue, but as I have never done motion control integration
with EPICS, I'd rather throw this ball up than send him into the wrong
direction.

He is being tasked with developing EPICS support for a locally developed
motor controller.

The hardware setup can be summarized as:

   * Moxa embedded TCP-to-serial converter (NE4110S)
   * Serial connection (RS-232)
   * Homemade motor controller (based on an AT89C52)
   * Ark Motion AMS 3630 stepper motor driver.

The controller software talks ASCII in command/response fashion, e.g.:

   * Read position (rotary encoder)
     Command: STX U<CR>
     Response: STX U pppppp<CR>
     pppppp = six digit hex (divide by 640 to get millimeter)
   * Go to position (rotary encoder)
     Command: STX P1 sss pppppp<CR>
     Response: \06 (ACK)
     sss = three digit hex (speed in mm/s multiplied by 240)
     pppppp = six digit hex (millimeter multiplied by 640)
   * ...

What's the best/easiest way to do this? What are the caveats?
Is there a tutorial he could follow?
Is there existing support for another motor that he could start from?

Thanks a lot for your help!
~Ralph





Replies:
Re: How to support a new stepper motor controller? Paramveer Jain
References:
How to support a new stepper motor controller? Ralph Lange
Re: How to support a new stepper motor controller? Kevin Peterson

Navigate by Date:
Prev: RE: How to support a new stepper motor controller? Mark Rivers
Next: FEMTO amplifier DLPCA-200 Ibrahim Saleh
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
Navigate by Thread:
Prev: Re: How to support a new stepper motor controller? Kevin Peterson
Next: Re: How to support a new stepper motor controller? Paramveer Jain
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
ANJ, 14 Feb 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·