Closed vatanaksoytezer closed 3 years ago
I realized we need the joint states plugin to achieve that. I can open a new PR to document it if it's appropriate.
I can open a new PR to document it if it's appropriate.
Thanks for offering! My suggestion would be to add a simple demo to ros_ign_gazebo_demos
using the joint states plugin.
Thanks for checking out! Sure I can do that. Will open one soon.
Environment
In ROS + gazebo invoking
<node name="urdf_spawner" pkg="gazebo_ros" type="spawn_model" args=" -urdf -model robot -param robot_description" respawn="false" output="screen" />
statement opens up gazebo, spawns the model and starts to publish/joint_states
.I am currently trying to replicate a similar behaviours with ROS2 Foxy. My setup is a docker image with ROS2 Foxy, Ubuntu 20.04, source build of ros2 branch of
ros_ign
and Binary install of Ignition Edifice.This how my launch file looks like:
Description
robot_description
. I tried a similar behaviour with sdf files too. I manage to givecmd_vel
commands and readodom
from ign. Though I didn't get anyjoint_states
. I can confirm that this is not a bridge issue by issuingign topic -l
command and there is nojoint_states
. My initial goal is to spawn the robot on ign, and show the robot movements on rviz. Withros_ign_bridge
oftf
I can show the frames in rviz but since I don't have thejoint_states
I can't show the model of the robot. Also intf
messages I can only see the base_link but no other links. I think this is mostly becausediff_drive_plugin
publishes it, not the ign gazebo. I would be happy to share any information you would like and would be happy to contribute with some PRs if there are any bugs / missing features related to these issues if you can brief me.Steps to reproduce
You should be able to reproduce by sourcing the workspace and launching the file provided. I think it can be reproduced with any xacro file. If you want to take a deeper look I can send the full description file as well.
Output