Torsten Bögershausen
90643807f3
When the motorRecord is initialized, init_record() is called. For asynMotors init_record() calls init_controller() in devMotorAsyn.c From here, the encoder ratio is send to the driver. After doing that, the code "locks" the execution waiting for a callback to call epicsEventSignal(pPvt->initEvent) which "unlocks" the code. As Mark Clift points out, this code can be simplified and the initEvent can be removed. Mark Rivers suggested to use the asynFloat64SyncIO interface, which locks the asyn port when calling the driver.
motor
This module contains motor support for the Experimental Physics and Industrial Control System (EPICS).
The core motor functionality resides in this respository. Starting with R7-0 the drivers have been moved from motor to standalone github repositories, which have been added to motor as submodules. The driver repositories can be found here: https://github.com/epics-motor
Getting started
Updating clones created before 2019-04-02
Use the following procedure to update clones that were created before the beginning of the motor split:
$ cd motor
$ make distclean
$ git fetch origin
$ git status
<behind by many commits and can be fast-forwarded>
$ git stash
$ git rebase origin/master
$ git stash apply
$ git submodule init
$ git submodule update
Failure to 'make distclean' before rebasing will result in many driver source directories in motorApp with "O.*" directories that need to be removed manually.
Cloning motor with support for all motor controllers
The following command results in a motor directory that contains all of the driver submodules:
$ git clone --recursive https://github.com/epics-modules/motor.git
Cloning motor with support for a single motor controller
The following procedure allows only required drivers to be built, which can significantly reduce build times:
$ git clone https://github.com/epics-modules/motor.git
$ cd motor
$ git submodule init
$ git submodule update modules/motorMotorSim
Additional Info
For more information, see: