Experimental Physics and
Industrial Control System

Hi

 

I am trying to understand how a motor controller driver works and how the asynMotorController and Axis classes map to the EPICS motor record. For example, I am investigating this driver from ACS motion https://github.com/epics-motor/motorAcsMotion to see if it supports some functions from the motor record that are required by our data acquisition system. Here are my questions:

1.       motor jogging: since the class does not implement the “::moveVelocity” function, does this mean that the driver does not support jogging at all? Or it does at the low-level motor record interface?

2.       VELO and ACCL fields: The class uses different variables to hold acceleration and velocity information other than the base class’s variables “motorVelocity_” and “motorAccel_”. Does this mean that VELO and ACCL fields are useless? Same thing goes for the OFF field.

 

In other words, if a motor driver is based on the motor record, does this guarantee that all fields are functional and working with the controller? How to verify if a certain function not implemented in the asyn classes but working and implemented somewhere else?

 

Best Regards,

 

Abdalla Al-Dalleh

Control Engineer

SESAME (Synchrotron-light for Experimental Science and Applications in the Middle East)
P.O. Box 7, Allan 19252, Jordan
Tel: +96253511348 , ext. 265

Fax: +96253511423

abdalla.ahmad at sesame.org.jo

www.sesame.org.jo