-
Notifications
You must be signed in to change notification settings - Fork 35
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
Inconsistent publishing rate for sensors #166
Comments
@alonsollorente But, this problem is already fixed in |
Hi! Thank you for the fast answer. I checked that the Update() function in the LiDAR publisher case is the same in the Furthermore, I tried the project in the |
Yes, you are right. It is still not fixed in
About this, I need to find the reason why especially for IMU sensors. |
Hi everyone!
I hope you can help me with this problem that I'm having. I'm trying to broadcast sensory data in ROS2 and going through some difficulties.
Thank you in advance for helping me out! I let you with a brief description of my problem.
Description of the bug
There is an inconsistency in the publishing frequency of sensor data between ROS2 and Unity when using ros_tcp_endpoint. Despite setting the publishing rate to 10Hz for one LiDAR sensor and 100Hz for an IMU, the actual publishing rate observed is significantly lower and inconsistent, being in the case of the IMU around 35Hz. The
ros2 topic hz /imu
output can be seen:To Reproduce
Steps to reproduce the behavior:
Environment set up:
The text was updated successfully, but these errors were encountered: