Hey,
Did you make sure that you don't have the fake jointstatepublisher running? Usually it get's launched in the headless mode automatically via the demo.launch. If you have two authorities (the fake one and the real one) running at the same time, you'll see the robot "flicker" or "jump around" in Rviz, since the messages are coming in at the same time.
If that's not the case, I'd start checking each intermediate step:
rostopic echo /jointstates
# Are the jointstates changing when you move the robot?
rosrun tf tf_echo YOUR_ROBOT_BASE YOUR_ROBOT_TIP
# Are the tf's changing?
If that's still the case, make sure that you are listening to the correct planning scene in rviz (usually move_group/monitored_planning_scene
). Also, you can display the current transforms in Rviz and see if they are changing/moving.
If everything of this works out, then, uhm, maybe somethings wrong with your urdf? Just report the different results, and I'll have a look.
Cheers,
Rabe
Originally posted by Rabe with karma: 683 on 2014-11-25
This answer was ACCEPTED on the original site
Post score: 4
Original comments
Comment by Marcel Usai on 2014-11-27:
Thanks for your quick answer! I could test it just a few minutes ago though...
It seemed that I was listening to the wrong planning scene topic in rviz. After changing it, it works perfectly fine!
Comment by RicoJ on 2020-12-10:
Hi guys, awesome discussion. In addition to what Rabe said, another thing might help is checking out your TF frames one by one with rosrun rqt_tf_tree rqt_tf_tree
while doing rosrun tf tf_echo YOUR_ROBOT_BASE YOUR_ROBOT_TIP
. I found my bug this way.