Hello,
We are using two ranger_mini_v3 robots and have encountered an issue with the odometry data when using the ROS 2 driver.
Symptoms:
The /odom topic continues to publish at the expected rate. However, the odometry data—especially the rotation—is often incorrect.
It appears as though roughly half of the rotational information is being dropped or missed. This issue seems to occur randomly but frequently.
We have attempted to investigate the issue but have not yet identified the root cause.
It is unclear whether the problem originates from the CAN interface, the ROS 2 drivers or the encoders themselves
The problem occurs on both of our robots, which makes a hardware-specific failure less likely.
Has anyone else experienced this issue or is aware of a potential cause or fix?
Please let us know if you need any additional information, logs, or diagnostics from our side.
Thanks in advance!
Anselme
Hello,
We are using two ranger_mini_v3 robots and have encountered an issue with the odometry data when using the ROS 2 driver.
Symptoms:
The /odom topic continues to publish at the expected rate. However, the odometry data—especially the rotation—is often incorrect.
It appears as though roughly half of the rotational information is being dropped or missed. This issue seems to occur randomly but frequently.
We have attempted to investigate the issue but have not yet identified the root cause.
It is unclear whether the problem originates from the CAN interface, the ROS 2 drivers or the encoders themselves
Has anyone else experienced this issue or is aware of a potential cause or fix?
Please let us know if you need any additional information, logs, or diagnostics from our side.
Thanks in advance!
Anselme