-
Notifications
You must be signed in to change notification settings - Fork 2
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
Document the delta time between IMU readouts #2
Comments
Read the wiki here: We spent quite a bit of time digging/reverse engineering/documenting this data... and you're free to re-use. |
Thanks @mungewell! |
It's 2000/s, or 0.0005. This is inline with talk of the sample rate being 2 per 1/1000th of a second. It seems like a lot, compared to real-time frame rates. |
2000/s, or 0.0005 |
Perfect, cheers @mick-p1982! |
To confirm, is this the delta time between the two sets of accelerometer and gyro readings within a single sensor frame, or is this the minimum delta time between any two successful reads on the sensor interface? |
It's the delta between the two samples packaged in each USB data packet, for example. It's typically like clockwork, although I have observed other values. Although I wouldn't be surprised if the other values were because the UDP buffer overflowed, possibly because of breaking into the program to debug it... In that case you'd be missing many samples that were discarded by the UDP buffer (dropped datagrams) and so naturally the delta would reflect the difference between the two valid/available datagrams. The timing is very precise. I don't know if temperature or other conditions could cause it to change. It may be so regular that it's only value is to recognize when data is lost. |
No description provided.
The text was updated successfully, but these errors were encountered: