-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Baxter_Gazebo: can't get current joint states #122
Comments
I think you got the error in your first trial. |
Hi, In short, yep, you're correct! Launching the world once, it failed in the usual way. But then, closing that down and relaunching the world resulted in it working. Sorry for the trivial issue, but thanks so much for your help! |
Hello, I meet the same error.
I get the info
But it didn't solve the problem, and the same error still occurred. |
@sxwgit |
@knorth55
and in a new terminal, I run the code:
Unfortunately, the error still occurs. |
I reinstalled the related librarys and found that the problem was solved. |
@sxwgit I want to know how to reinstall? |
I'm also facing same issue. I'm following these steps: https://sdk.rethinkrobotics.com/wiki/Simulator_Installation These commands:
Gives this error:
I'm using Ubuntu 14.04 and ROS indigo. Please help! |
sometime just restart your PC can resolve your problem |
I tried restarting the PC, but its still not working, please help! |
I used to run Baxter very fast and without problems in Kinetic. But since I updated to noetic, I consistently get a slowdown; including using the real robot. I cannot figure out what I time out so much.I have updated my repo's to reflect python3 updates in print, exceptions, range, imports, etc... Any generic clues about the slowdown due to a switch in noetic are appreciated. |
real robot |
Hi, all. I've solved this by recorrecting my baxter.sh file in the line of |
Hi,
I have an issue with running any of the code to move the robot. I get the below error when I run the joint position waypoints example:
$ rosrun baxter_examples joint_position_waypoints.py -l right Initializing node... Traceback (most recent call last): File "/home/pipothy/ros_ws/src/baxter_examples/scripts/joint_position_waypoints.py", line 191, in
main() File "/home/pipothy/ros_ws/src/baxter_examples/scripts/joint_position_waypoints.py", line 181, in main
waypoints = Waypoints(args.limb, args.speed, args.accuracy) File "/home/pipothy/ros_ws/src/baxter_examples/scripts/joint_position_waypoints.py", line 45, in init
self._limb = baxter_interface.Limb(self._arm) File "/home/pipothy/ros_ws/src/baxter_interface/src/baxter_interface/limb.py", line 121, in init
timeout_msg=err_msg) File "/home/pipothy/ros_ws/src/baxter_interface/src/baxter_dataflow/wait_for.py", line 55, in wait_for
raise OSError(errno.ETIMEDOUT, timeout_msg) OSError: [Errno 110] Right limb init failed to get current joint_states from robot/joint_states
EDIT: When I echo the joint_states topic, I can see data on it so the topic isn't empty.
I already had ROS installed, but other than that, I followed the installation instructions at the link below line by line. I used the commands for kinetic and stopped after launching the baxter world: http://sdk.rethinkrobotics.com/wiki/Simulator_Installation
I then enabled the robot and ran the command to start the example: http://sdk.rethinkrobotics.com/wiki/Joint_Position_Waypoints_Example
This produced the above error.
Am I being silly and have forgot to do something, or is this a genuine error? Apologies if it is me being silly, I can't seem to find anything in the rest of the issues.
The text was updated successfully, but these errors were encountered: