Skip to content

don't wait for !is_busy in closed loop control#37

Merged
samuelsadok merged 1 commit into
mainfrom
fix-enter-closed-loop-control
May 21, 2025
Merged

don't wait for !is_busy in closed loop control#37
samuelsadok merged 1 commit into
mainfrom
fix-enter-closed-loop-control

Conversation

@samuelsadok
Copy link
Copy Markdown
Member

This addresses a firmware change in fw v0.6.11, in which requested_state during CLOSED_LOOP_CONTROL is newly reported as BUSY.

Previously, when issuing a request_axis_state service call with CLOSED_LOOP_CONTROL, the node would wait for the axis to leave the BUSY state before returning. Since fw v0.6.11, this meant that the call would never return when entering CLOSED_LOOP_CONTROL.

This addresses a firmware change in fw v0.6.11, in which requested_state
during CLOSED_LOOP_CONTROL is newly reported as BUSY.

Previously, when issuing a `request_axis_state` service call with
`CLOSED_LOOP_CONTROL`, the node would wait for the axis to leave the
BUSY state before returning. Since fw v0.6.11, this meant that the
call would never return when entering CLOSED_LOOP_CONTROL.
@samuelsadok samuelsadok merged commit 0a5322f into main May 21, 2025
4 checks passed
@samuelsadok samuelsadok deleted the fix-enter-closed-loop-control branch May 21, 2025 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant