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

I2C pull interface and proper averages #21

Closed
LorenzMeier opened this issue Aug 12, 2014 · 2 comments
Closed

I2C pull interface and proper averages #21

LorenzMeier opened this issue Aug 12, 2014 · 2 comments
Assignees

Comments

@LorenzMeier
Copy link
Member

We should be resetting the integrated flow to zero on I2C reads so the reader does not loose samples, independent of his readout speed.

@priseborough
Copy link

The average flow rate in mrad/sec could be sent across using an int16, as could the averaged x,y,z gyro readings. 1 mrad/sec is enough resolution for our purposes.

The averaged flow readings should not be motion compensated.

@LorenzMeier
Copy link
Member Author

@dominiho We discussed a double buffer for flow and gyro values so that each I2C read command gets the exact difference since the last read - is this now fully implemented and this issue can be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants