Experimental Physics and
Industrial Control System

Hello Marissa,

It might be something as simple as torque to the motor is not enabled; check the EPICS motor record "Enable control" (CNEN) field. It needs to be 1:"Enable" to move the motor.

As I understand it, Mark Clift's Galil EPICS device/driver sends the "move begin failure axis" message if 2.5 seconds after a motion command is issued, motion has not been detected by the driver. That could be caused by a variety of circumstances. Check the displays Mark provides and if that does not yield the answer, you may have to use Galil Suite to query the controller.

Ron

On 03/22/2017 09:00 AM, Pearson, Matthew R. wrote:

Hi,

I’ve not worked with DC motors with that driver (only steppers). However you could check the motor type setting. The PV name might be DMC01:A:A_MTRTYPE_CMD.

Also check the drive enable signal (DMC01:A:A_ON_CMD) which should be “On”

If there’s an issue with limits then either .HLS or .LLS will be set to 1.

Cheers,
Matt


Data Acquisition and Control Engineer
Spallation Neutron Source
Oak Ridge National Lab

On Mar 21, 2017, at 6:55 PM, Marissa Elizabeth Kranz <[email protected]> wrote:

Hello,

I am working on a project involving the control of 40 brushed DC motors by the Galil DMC 4080 controller. We have an IOC shell set up with encoder feedback that the motor is tracking (if we move the motor shaft a bit then it corrects itself to the encoder position), but whenever we try to send the motor to a specified position through the motor record's VAL field we receive the following error:

epics> dbpf DMC01:A.VAL 40
DBR_DOUBLE:         40
epics> move begin failure axis A
2017/03/21 15:46:03.777 asynMotorController:writeFloat64 error, status=3 axis=0, function=1, value=888.888889

Has anyone encountered this same error and knows what causes this output?

Thanks so much,
Marissa Kranz