Using Aerotech Automation1 motor controller with EPICS - controller initialization

[John Dobbins via Tech-talk <tech-talk at aps.anl.gov>]

All,

I am working on integrating an Aerotech Automation1 Motor Controller into operations at CHESS. 

We are using an EPICS IOC as a layer between the motor controller and SPEC, the software beamline scientists use to control experiment data acquisition.  The IOC appears to work, i.e. we can enable/disable the motor, home the motor,  and command moves through EPICS.

I am wondering about what is required for controller initialization.

The Automation1 controllers are new to us, but my understanding is that when one connects Automation1 Studio to the controller, the controller is configured using an associated .mcd file.

In my tests to date I believe the controller has already been configured by Automation1 Studio before I start the IOC.   I am wondering if this is a requirement, i.e. if the controller is for example power cycled, does it need to be configured via Autmation1 Studio before it is usable by the EPICS IOC.

The EPICS IOC does some initialization of the controller, e.g. setting velocity, but I don't know if and doubt that this initialization is complete.

Also, more generally, if the motor controller is initialized via Automation Studio and the controller is power cycled, what state does the motor controller come up in?  Are the settings non-volatile? Or does the controller come up in a 'blank' state?

Regards and Happy 2025,

John Dobbins

Research Support Specialist

Cornell High Energy Synchrotron Source

Cornell University

www.chess.cornell.edu