In Examples, Ctrl+C Errors on Exit with Simulated Robot #48
Comments
rethink-imcmahon
pushed a commit
that referenced
this issue
Sep 8, 2015
This commit removes reliance on rospy for handling the shutdown behavior when a Ctrl+C signal is asserted on the joint_velocity_wobbler example. Cleanup was not properly being executed in only the simulated robot through rospy's on_shutdown() callback handler. This change has been tested on both the simulated and real Baxter robots.
rethink-imcmahon
pushed a commit
that referenced
this issue
Sep 8, 2015
This commit removes reliance on rospy for handling the shutdown behavior when a Ctrl+C signal is asserted on the joint_velocity_wobbler example. Cleanup was not properly being executed in only the simulated robot through rospy's on_shutdown() callback handler. This change has been tested on both the simulated and real Baxter robots.
rethink-imcmahon
pushed a commit
that referenced
this issue
Sep 8, 2015
This commit removes reliance on rospy for handling the shutdown behavior when a Ctrl+C signal is asserted on the joint_velocity_wobbler example. Cleanup was not properly being executed in only the simulated robot through rospy's on_shutdown() callback handler. This change has been tested on both the simulated and real Baxter robots.
|
Either this should get fixed in all 13 of our examples with on_shutdown behavior or the root cause needs to be sussed out in |
dirk-thomas
pushed a commit
to ros/ros_comm
that referenced
this issue
Nov 9, 2015
Timers go off and start periodically running in the background, and will throw exceptions when ros shutdown occurs because of the sleep function. These are impossible to catch as they're off in a background thread and can be cleanly handled as in the code change. Others with the same problem: * [baxter examples](RethinkRobotics/baxter_examples#48)
|
Appears there was an underlying @stonier thanks for fixing this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A crossover issue from RethinkRobotics/baxter_simulator#58. The gist:
When running
baxter_examples joint_velocity_wobbler.pyon thebaxter_simulatorrobot, and Ctrl+C is asserted by the user, various errors can be produced byrospyon exit:A Timer Error:
A baxter_interface Limb Error:
This is likely a
rospysimulated_timetimer issue, since thejoint_velocity_wobblerscript does not error like this on the real robot, but it is desirable to find a fix that would prevent this issue entirely.The text was updated successfully, but these errors were encountered: