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

timestamp latency #30

Open
alexsaso opened this issue Jan 21, 2021 · 3 comments
Open

timestamp latency #30

alexsaso opened this issue Jan 21, 2021 · 3 comments

Comments

@alexsaso
Copy link

I am using a Lord Microstrain 3DM-GX5-25 IMU together with this driver. I have the IMU rate configured at 500 Hz, meaning I expect an imu message each 2 ms (0.002 s). This is the case for the most sequential messages, but some messages are further apart (up to 20 ms).

Does anybody know, why is this happening? I was thinking it could be following:

  • some messages are dropped
  • system is overloaded and the processor gets to it with some latency

Thanks,
Aleks

@versatran01
Copy link
Collaborator

versatran01 commented Jan 21, 2021

I think point 2 might be the reason.

Have you tried this one https://github.com/ros-drivers/microstrain_mips
This supports gx5 while ours has not been tested with one.

@alexsaso
Copy link
Author

Thank you for your answer, I will check out the other driver as well.

There is another thing that I have noticed. I store the imu messages into a bag file. When I check the sequence numbers of the messages, I noticed that out of the 4193 messages are missing (meaning sometimes the sequence is not incremented for +1 but a larger number). Does this mean that there are messages dropped and why could this happen?

@versatran01
Copy link
Collaborator

There could be many reasons that cause messages to drop. (maybe system is under heavy load).
If only a few dropped from 4000 msgs then I wouln't worry too much.

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

2 participants