Kevin Peterson

> @kmpeters: I expect the motor record to account for backlash correction as part of a controlled stop. This is worth a discussion on the motor records GH repository. See:...

> For a given motor, what special cases are there that should prevent a controlled stop from applying appropriate backlash correction? The entire point of backlash correction is to leave...

> We're observing a motor `.RBV` update rate of ~5 Hz for both the servo motor and the PZT we tested. And then, the occasional period when it does not...

The motor record keeps `SREV` and `UREV` consistent with `MRES`, but only `MRES` is used to calculate the positions, velocities and accelerations that are sent to the controller. For the...

> The above reply means that I only need to set MRES for motor resolution and I can ignore SREV & UREV? Yes, that is correct. > Another question is...

For most controllers the RBV and DRBV update during a move at the move poll frequency, even for motors with no encoders or motors with encoders that have UEIP and...

@tboegi, I switched the master branch to use the sequencer mirror. If you rebase this pull request on the master branch, the CI builds should succeed.

I'm very confused. Why did the build of the master branch succeed on OS X: https://github.com/epics-modules/motor/actions/runs/7144493328 While the build of this branch failed: https://github.com/epics-modules/motor/actions/runs/7164362343 With the same `motor/.ci/cue.py`?

I might just ignore the CI failure for now. I've seen weird errors on pull requests that weren't problems on the master branch.

Pedro Nariyoshi reports that these changes work well in his test setup: https://epics.anl.gov/tech-talk/2023/msg01901.php