turtlebot3
turtlebot3 copied to clipboard
Incomplete tf tree
ISSUE TEMPLATE ver. 0.4.0
-
Which TurtleBot3 platform do you use?
- [X] Burger
- [ ] Waffle
- [ ] Waffle Pi
-
Which ROS is working with TurtleBot3?
- [ ] ROS 1 Kinetic Kame
- [ ] ROS 1 Melodic Morenia
- [X] ROS 1 Noetic Ninjemys
- [ ] ROS 2 Dashing Diademata
- [ ] ROS 2 Eloquent Elusor
- [ ] ROS 2 Foxy Fitzroy
- [ ] etc (Please specify your ROS Version here)
-
Which SBC(Single Board Computer) is working on TurtleBot3?
- [ ] Intel Joule 570x
- [X] Raspberry Pi 3B+
- [ ] Raspberry Pi 4
- [ ] etc (Please specify your SBC here)
-
Which OS you installed on SBC?
- [X] Raspbian distributed by ROBOTIS
- [ ] Ubuntu MATE (16.04/18.04/20.04)
- [ ] Ubuntu preinstalled server (18.04/20.04)
- [ ] etc (Please specify your OS here)
-
Which OS you installed on Remote PC?
- [ ] Ubuntu 16.04 LTS (Xenial Xerus)
- [ ] Ubuntu 18.04 LTS (Bionic Beaver)
- [X] Ubuntu 20.04 LTS (Focal Fossa)
- [X] Windows 10
- [ ] MAC OS X (Specify version)
- [ ] etc (Please specify your OS here)
-
Specify the software and firmware version(Can be found from Bringup messages)
- Software version: [x.x.x]
- Firmware version: [x.x.x]
-
Specify the commands or instructions to reproduce the issue.
- Launch the
RviZsimulatorroslaunch turtlebot3_fake turtlebot3_fake.launch
- Visualize the
tftreerosrun rqt_tf_tree rqt_tf_tree
- Exit the
RviZsimulator - Launch the
Gazebosimulatorroslaunch turtlebot3_gazebo turtlebot3_empty_world.launch
- Visualize the
tftreerosrun rqt_tf_tree rqt_tf_tree
- Launch the
-
Copy and Paste the error messages on terminal.
- none
-
Please describe the issue in detail.
-
The
RviZsimulation publishes a completetftree.
-
The
Gazebosimulation only publishesodomandbase_footprintframes.
-
Is this intentional? What can I do to get the
Gazebosimulation to publish the completetftree?
-
I just found out that the tf tree published by the real TurtleBot3 is identical to the Gazebo version, just odom and base_footprint. Why doesn't the TurtleBot3 publish all the other transformations that the fake node does?
Is it because you're using a 3rd party LIDAR?
I met a similar problem in Rviz using ROS2 Foxy. In Rviz it showed several TF warnings that "no information was transfered from [...] to [map]". Then I checked the code of lidar itself and found nothing related to the TF node. So it means robot doesn't know anything other than the 2D point clouds.
Maybe you need to write this part by yourself.