APS-4ID-POLAR / APS-4ID-POLAR/ipython-polar
how is motor backlash handled with respect to the limits with a slit device
Open
bug
- Dominant language
- Python
- Stars
- 1
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
When moving the center (for example) via a PV in Bluesky and a motor limit is hit, the EPICS controls for the motor know the limit has been hit but the slit control (in EPICS) does not know the limit is hit. Bluesky ends up waiting indefinitely.
How can we build this slit device to react to the limits being hit (or prevent the move in the first place)?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.