Why DISABLED axis are skipped?
Disabled axis are skipped from some stuffs like metadata positioners and standard command like wa
.
- https://gitlab.esrf.fr/bliss/bliss/-/blob/master/bliss/common/alias.py#L371
- https://gitlab.esrf.fr/bliss/bliss/-/blob/master/bliss/scanning/scan_meta.py#L306
- Also i think when a motor controller fail at initialization, axis are set
DISABLED
Why do we do that?
In my mind
-
DISABLED
means that we can't move a motor, but we can read it's position -
OFF
means that the axis is not reachable
That's the way we use it in Daiquiri.
Could we clarify the situation? By maybe improving the documentation for each axis states?
Here is what we can get from the source code:
MOVING : 'Axis is moving'
READY : 'Axis is ready to be moved (not moving ?)'
FAULT : 'Error from controller'
LIMPOS : 'Hardware high limit active'
LIMNEG : 'Hardware low limit active'
HOME : 'Home signal active'
OFF : 'Axis power is off'
DISABLED: 'Axis cannot move (must be enabled - not ready ?)'
Here we already can fix that READY
means that we can request a motion, but it still can be MOVING
at the same time (READY
is not not MOVING
).
I am about to display back DISABLED
axis position from wa
so i would like to be sure about it.
Maybe related to #2946 (closed) #3964 #3970
Edited by Valentin Valls