forked from epics_driver_modules/motorBase
Kevin Peterson
3683d3f0ea
Record recognizes motor stop while jogging. Text from the pull request: 'The following situation came up while debugging soft limits in a motion controller which had different values then the record. The motor is at position 50mm (RBV=50), the low soft limit is 15 (LLM=15), jogging velocity is 10 mm/sec (JVEL=10). The motion controller has an internal soft limit which is 35 mm, which we want to test. Set JOGR to 1, the motor will move backwards. (Side note: it would be stopped by the record once it passed 25mm). Before that, the motion controller stops the motor internally and reports DONE. The state machine in the record is not prepared to handle this and JOGR stays 1. The expected behavior is that JOGR returns to 0. Because this is an unexpected stop, reset even pending home requests. In other words: call clear_buttons(pmr) Whether or not an alarm is raised may be another question. The natural thing would be to set LVIO to 1, but we don't know why the controller stopped the motion. Unless we add a bit in MSTA like "RA_LVIO"... But in any case this can and should go into a separate commit.'
motor
APS BCDA synApps module: motor
Note: Current discussion on future of the motor module repository: https://github.com/epics-modules/motor/issues/55
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