Sebastien Petitdemange authored Sep 22, 2020 and Benoit Formet committed Sep 22, 2020

For mesh scans, motor's limits check was done before the motors positions
was completely build.

This patch preserves the last value set in redis, which should mimic better
a real motor controller (since positions, for example, stay the same even
if BLISS is restarted -except if there is a power cut on the controller,
but that's another story-)

changes

- add jog_velocity R/W property, both in YML config + setting in redis
- jog_velocity can be changed while motor is in a jog move
- fix: take sign into account
- calling .jog() without velocity would use current .jog_velocity
- if .jog() is called with a velocity => this will set the new jog_velocity

Added "test" in mockup controller code

'prepare_move' is renamed to 'get_motion', to not confuse the 'prepare_move'
on motor controller. Now, 'get_motion' does not involve any communication,
the check for readiness of the axis has been moved to GroupMove.

About hooks: pre_move, post_move are called in GroupMove. This allows to
fix issue #1575, hooks are called with the motion list corresponding to the
group move, not for individual moves

axis: introduce steps_position_precision to motor controllers, and use it to determine delta in _get_motion

* implement %-arguments on log_* bliss functions for lazy eval purpose
* conversion of existent code

Cyril Guilloud authored Feb 11, 2020 and Cyril Guilloud committed Feb 12, 2020

*for axis / counter / encoder
*for PI E753
   - comm
   - get_axis_info()

This simplify the way to register to the map
Now all registration are done in the object constructor.

* Axis generic class.
* mockup controller.

* some bugfixes

Use common utility function

Globals from the past...

Mockup controller raises an error for values above a certain range

all of them are now:
# Copyright (c) 2015-2019 Beamline Control Unit, ESRF

+ blackified ct2 files.