forked from epics_driver_modules/motorBase
b969f5a0abe036bf6922d7ebc60ef982b8a22b2a
Previously drive resolution was determined using the SU? command, which returns the encoder resolution. The SU? value is not meaningful when open-loop steppers are used, and cannot even be set in the controller. Use the ZB? command to see if stepper positioning is enabled and encoder feedback is disabled. If so the full-step (FR?) and microstep (QS?) values are used to determine drive_resolution. If not then SU? is used to determine drive resolution, as previously.
motor
APS BCDA synApps module: motor
For more information, see:
Report an issue with Motor
Request a feature
converted from APS SVN repository: Fri Oct 16 12:31:41 CDT 2015
Description
This is motor record version 7. The older (incompatible) motor record version 6 is here: https://git.psi.ch/epics_driver_modules/motor.
The "upstream" branch is a fork of https://github.com/epics-modules/motor. Do not modify that one.
All used submodules have their own repo. Don't modify them here.
Languages
C++
62.3%
C
34.6%
Makefile
1.7%
Python
1.3%
Shell
0.1%
