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

accelerometer_timestamp_relative is always '0' #8926

Closed
BazookaJoe1900 opened this issue Feb 20, 2018 · 2 comments
Closed

accelerometer_timestamp_relative is always '0' #8926

BazookaJoe1900 opened this issue Feb 20, 2018 · 2 comments

Comments

@BazookaJoe1900
Copy link
Member

I am not sure if its a bug or not.
Looking at plots of sensors_combined message, I can see that accelerometer_timestamp_relative is always 0.
I am not sure about the logic that related to this var, and if it just log issue.
I can say that magnetometer_timestamp_relative and baro_timestamp_relative are not constant 0.

@bkueng
Copy link
Member

bkueng commented Feb 20, 2018

The accel timestamp is relative to the gyro timestamp. And because they come from the same driver with the same publication rate, it's always 0.

@bkueng bkueng closed this as completed Feb 20, 2018
@BazookaJoe1900
Copy link
Member Author

@bkueng Thanks.

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