ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

"Verify that data is being published on the /turtlebot01/scan topic" even though data exists in /turtlebot01/scan on physical turtlebot3

asked 2022-10-26 17:53:32 -0500

wyatt gravatar image

updated 2022-10-27 12:03:43 -0500

Hello! I've been trying to get move_base functioning on two physical turtlebot3 waffle_pi for a few days now, but I have been stuck on this issue for quite awhile now. I am able to subscribe to each of the turtlebots and get lidar data using their namespace/scan, and I am so far able to send teleop commands. But I am still not able to get move_base working, as I believe the localization/amcl is not working correctly.

I am running with 2 Turtlebot3 waffle_pi The server is running in a docker image as Ubuntu 20.04, ROS1 Noetic

Here are the warnings I am getting:

[ WARN] [1666818216.636210456]: No laser scan received (and thus no pose updates have been published) for 1666818216.636097 seconds. Verify that data is being published on the /turtlebot01/scan topic. [ WARN] [1666818216.651007763]: No laser scan received (and thus no pose updates have been published) for 1666818216.650903 seconds. Verify that data is being published on the /turtlebot02/scan topic. [ WARN] [1666818220.743254097]: Timed out waiting for transform from turtlebot01/base_footprint to map to become available before running costmap, tf error: canTransform: target_frame map does not exist.. canTransform returned after 0.100328 timeout was 0.1. [ WARN] [1666818220.776271416]: Timed out waiting for transform from turtlebot02/base_footprint to map to become available before running costmap, tf error: canTransform: target_frame map does not exist.. canTransform returned after 0.101146 timeout was 0.1

Unfortunately I am not able to upload any files yet, but here are the relevant ones:

All of my launch files are here: https://gist.github.com/wyattmotion2a...

Here is my TF tree: https://imgur.com/53QqTZB

Here is a link with related images. https://imgur.com/a/yruhL7F

I believe the problem is somehow related to the TF tree and AMCL not publishing the correct transforms. But I am not sure what the real problem is or how to track it down. Thank you for any help!

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2022-10-27 13:04:02 -0500

wyatt gravatar image

updated 2022-10-27 16:58:08 -0500

Update: It seems I am able to fix the

Timed out waiting for transform from turtlebot01/base_footprint to map to become available before running costmap, tf error: canTransform: target_frame map does not exist.. canTransform returned after 0.100328 timeout was 0.1. [ WARN]

errors by publishing a transform as follows:

rosrun tf static_transform_publisher 0 0 0 0 0 0 map /turtlebot02/base_footprint 100

rosrun tf static_transform_publisher 0 0 0 0 0 0 map /turtlebot01/base_footprint 100

I'm not sure if this is the correct transform, but it removes that error. For now, I still have the following error:

[ WARN] [1666893666.696421084]: No laser scan received (and thus no pose updates have been published) for 1666893666.696324 seconds. Verify that data is being published on the /turtlebot02/scan topic.

[ WARN] [1666893681.694004683]: No laser scan received (and thus no pose updates have been published) for 1666893681.693916 seconds. Verify that data is being published on the /turtlebot01/scan topic.

Another update:

I've been able to solve all warnings and RVIZ errors by adding more transformations:

node pkg="tf" type="static_transform_publisher" name="map_to_base_footprint" args="0 0 0 0 0 0 map /$(arg name)/base_footprint 100"/>

node pkg="tf" type="static_transform_publisher" name="odom_to_map" args="0 0 0 0 0 0 map /$(arg name)/odom 100"/>

node pkg="tf" type="static_transform_publisher" name="scan_to_map" args="0 0 0 0 0 0 map /$(arg name)/scan 100"/>

node pkg="tf" type="static_transform_publisher" name="base_scan_to_base_scan" args="0 0 0 0 0 0 /$(arg name)/base_scan base_scan 100"/>

node pkg="tf" type="static_transform_publisher" name="base_scan_to_map" args="0 0 0 0 0 0 map /$(arg name)/base_scan 100"/>

However this has still not resolved the ultimate issue of localization not happening. Now the lidar data is displayed in rviz, but it is not localized correctly as you can see here:

https://imgur.com/a/lcqsh2v

edit flag offensive delete link more

Comments

After changing many things, I believe the root cause of the issue is related to this pr:

https://github.com/ROBOTIS-GIT/ld08_d...

the frame_id of the scan does not allow you to set different namespaces, it is hard coded. So it would not work with multiple robots

wyatt gravatar image wyatt  ( 2022-11-02 19:23:34 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2022-10-26 17:42:28 -0500

Seen: 67 times

Last updated: Oct 27 '22