Every motion FB you call only makes sense through one lens: an axis is always in exactly one state, and commands move it between them. Don't memorise the diagram — drive it.
Start in Disabled. Each command is only legal from certain states — try an illegal one and the axis tells you. This is exactly why a MoveAbsolute "does nothing" on a disabled axis.
🧭 One state, always. There's no "in between". After a move completes the axis returns to Standstill; after a fault it sits in ErrorStop until you MC_Reset. Your code can always ask "where am I?" and get one answer.
🚧 ErrorStop wins. A fault from any state drops the axis straight to ErrorStop — and the only way out is MC_Reset back to Standstill (or Disabled). That's the safety net the whole model is built around.
An axis is in ErrorStop. You send MC_MoveAbsolute. What happens?