Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with /odom data - no data received. #515

Open
CycleMark opened this issue Jan 8, 2025 · 0 comments
Open

Problem with /odom data - no data received. #515

CycleMark opened this issue Jan 8, 2025 · 0 comments
Assignees
Labels
troubleshooting System not working as expected, may be user error.

Comments

@CycleMark
Copy link

Robot Model

Turtlebot4 Lite

ROS distro

Humble

Networking Configuration

Discovery Server

OS

Ubuntu 22.04

Built from source or installed?

Installed

Package version

I'm actually using Jazzy on R Pi5.

I can see data and topics from the iCreate and those from the Pi /scan etc no problem. But I'm getting nothing on the /odom topic.

Starting the robot with:

ros2 launch turtlebot4_bringup lite.launch.py

rplidar etc come up but when I start

ros2 launch slam_toolbox online_sync_launch.py params_file:=/home/ubuntu/ros_ws/config/mapper_params_online_async.yaml

It complains:

[slam_toolbox]: Message Filter dropping message: frame 'laser' at time 1736352837.937 for reason 'discarding message because the queue is full'

Which I've figured out is because there is no odom tf or data being sent out.

Possibly related when I run

ros2 run teleop_twist_keyboard teleop_twist_keyboard --ros-args -p stamped:=true

The robot does not move.

Seems like there is a process missing. Can you please advise?

Thanks

Mark

Type of issue

Navigation (SLAM, Nav2 etc.)

Expected behaviour

Able to move the robot cand create a map

Actual behaviour

No movement and no map unless I force a odom frame:

ros2 run tf2_ros static_transform_publisher 0 0 0 0.3 0.0 0.0 odom base_link

Error messages

No response

To Reproduce

See above

Other notes

No response

@CycleMark CycleMark added the troubleshooting System not working as expected, may be user error. label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
troubleshooting System not working as expected, may be user error.
Projects
None yet
Development

No branches or pull requests

3 participants