Hi William,
Just to clarify, the APS motor software and the asyn motor software are part of the same package. There are not two different technologies to compare.
Here is a short summary of the structure of the software.
- Motor record. This is the top level
- Device support. There are 2 types of device support:
Older “model 1” drivers use a different device-dependent device support for each controller type
Newer “model 2” and “model 3” drivers use a single device-independent device support file
- Driver support. There are 2 types of driver support:
Older “model 1” drivers use a motor-driver specific interface to model 1 device support
Model 2 drivers use a device independent driver (drvMotorAsyn) plus a device-dependent driver written in C
Model 3 drivers use the asynMotorController and asynMotorAxis base classes, plus device-dependent derived classes for the controller and axis objects.
Model 1 drivers can really only be used by the motor record. Model 2 and model 3 drivers can also be used with standard EPICS records to implement device-specific
features that the motor record cannot control.
The support that Ron referred to for the MAXnet is a model 3 driver located in motor/motorApp/OmsAsynSrc.
Mark
Hello William,
Jens Eden (PTB) added asyn motor support for both the OMS MAXv and the OMS MAXnet controllers. That support is available beginning with the latest release (R6-8) of the
motor module.
Ron
On 5/6/2014 2:18 PM, Weiwei Lu wrote:
Hi,
We plan to use a soft IOC and an OMS MAXnet motion controller to control a stepper motor. The soft IOC will communicate with the MAXnet motion controller's Ethernet interface. What are the existing EPICS device/driver supports that we can use for this soft IOC application? Can APS's Stepper/DC Motor Controller software or Mark Rivers' devMotorAsyn and drvMotorAsyn be used for this? What are the pros and cons comparing these two technologies? Are there other alternatives?
Advice is greatly appreciated. Thank you in advance.
William Lu
