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

Bug with multiple IMU sensor with the same name #428

Open
rafal-gorecki opened this issue Oct 22, 2024 · 0 comments
Open

Bug with multiple IMU sensor with the same name #428

rafal-gorecki opened this issue Oct 22, 2024 · 0 comments

Comments

@rafal-gorecki
Copy link

rafal-gorecki commented Oct 22, 2024

Hello,

I encountered a problem with spawning an IMU with the same name in simulation (on two robots with different namespace). When two IMUs have the same name in GZ, imu_manager reads data from the wrong sensor. This caused there are two IMU instances in the world, but imu_broadcaster subscribes the data from the first sensor.

This is well demonstrated in the video, where the topic imu/data_raw is the data cast from the simulation (gz_bridge), and imu/data is the data from the imu_broadcaster.

Screencast.from.10-22-2024.01.03.14.PM.webm

I suggested solving this using namespaces, but the topic died. ros-controls/ros2_controllers#1104
Now I have in mind to approach the problem from the other side, but I have no idea how to do it, because the gz code is much less known to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant