Skip to content

Command Lock X series Actuators #57

Discussion options

You must be logged in to vote

The lock-out gets set by APIs and is limited to maximum 5 seconds per message. You likely have some other process or other computer running that is actively sending commands to the actuators.

APIs send commands with a maximum lifetime that sets an expiration time. It exists for two reasons:

  • While a command is "alive", the actuators won't accept commands frm any other source. This prevents accidentally commanding the robot from two sources, which is what you are running into.
  • If a program crashes or stops sending commands for some reason, the lifetime expires and the actuators turn off output commands. This is particularly important for velocity/effort control where actuators would otherw…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by GogiPuttar
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Questions, comments or problems
1 participant