Closed Petrox closed 8 years ago
It's going to be difficult to debug this without being able to see your exact machine. Several of the issues you have mentioned were warnings that I cleaned up in RSDK 1.2.
The errors might very well be issues of ROS sources changing their API's out from underneath your baxter_simulator. You might try using the ros_controls and ros_controllers source code for indigo-devel, and rolling them back to the date where you found the simulation last worked: https://github.com/ros-controls/ros_controllers/tree/indigo-devel
We have a project that depends on baxter_sdk1.1, ubuntu 14.04, ros indigo. (the project is in codefreeze state, so no 1.2 upgrade possible this time, not even apt-get upgrade allowed)
While we do have a working baxter robot, but we're trying to simulate baxter under gazebo 2.2.6 (from osrf repo).
I even set the export LD_LIBRARY_PATH="/usr/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH" trick in my .bashrc, as was suggested on the mailing list, and it solved some error messages about missing robot_state before...
when running roslaunch baxter_gazebo baxter_world.launch
Controller spawner says it loaded the controllers, but when I'm trying to use wobbler, or tuck_arms the last two error messages repeat.
I do remember, that this simulation was working before, maybe dependencies changed or some configuration error happened, but the messages have some conflict between them (loaded, but not running controllers?)
Note: Also sometimes (not every time!) I get parts of the robot falling apart in gazebo with messages like:
or
These might be independent issues, but I can't find direction where to look for clues.
The commands I run:
Both roslaunch working in paralell and gazebo having timing and racecondition issues gives the whole system a pretty you-can-never-reproduce-this-error taste. :)
I do have the same problem on a different machine, where the ros and osrf packages were kept up-to date via apt, but the sources weren't touched in 6 months, and gazebo 2.2.6 shows the same simptoms:
Could not stop controller 'left_joint_velocity_controller' since it is not running.
Any advice?