Experimental Physics and
Industrial Control System

Hi Abdalla,

Ø  In this case do I need to call the controller or axis classes callbacks?

I’m not sure what you are asking.  Do you mean in the writeInt32 and readInt32 methods?  At the end of writeInt32() you should call pAxis->callParamCallbacks() as is done for the Newport XPS controller here:

https://github.com/epics-motor/motorNewport/blob/9ef83c1c19fab255fe26a770ce978338620ee288/newportApp/src/XPSController.cpp#L297

Ø  For the SPMG field, when going from Go to Move the GUI gives me “Controller Error” and the RBV field does not update until it reaches its destination, this is very similar to the original behavior. This also happened when I reverted my updates for read/write Int32 interfaces.

I just tested two motor drivers that inherit from asynMotorController, the Newport XPS and the Galil.  They do not show this behavior: there is no controller error when changing from Go to Move, and the RBV updates fine while a motion is in progress in Move mode.  What do you mean by “this is very similar to the original behavior”?  Do you mean before you added the code to call the base class writeInt32()?   It seems like your driver may have another issue.

Is your code on Github or elsewhere that I can look at it?

Mark

Hello Mark

I called the base class functions and it worked. I have two questions:

1.       In this case do I need to call the controller or axis classes callbacks?

2.       For the SPMG field, when going from Go to Move the GUI gives me “Controller Error” and the RBV field does not update until it reaches its destination, this is very similar to the original behavior. This also happened when I reverted my updates for read/write Int32 interfaces.

Thanks!

Abdalla.