You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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), andimu/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.
The text was updated successfully, but these errors were encountered: