Open dave992 opened 1 year ago
It's likely this is caused by the servos going into energy conservation / eco mode.
That's indeed not a situation that was included in testing during development.
I'm not immediately sure why a second invocation is required.
Is there any indication of whether servos are still on in the state topic(s)?
The /rws/system_states
topics report motors_on: False
just before reproducing this error. (I always start the state machine in a motors off state).
The service call to
/rws/set_motors_on
sometimes fails with the following result:This only seems to happen if I do not use the
abb_robot_driver
for a longer period of time (like 5min plus?) when the motors are off and I want to activate them again via the/rws/set_motors_on
service call.Immediately calling the same service again works and activates the motors as expected.