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

Prevent incorrect rescheduling for BMP280 baro dummy ut_delay #612

Merged

Conversation

martinbudden
Copy link
Contributor

No description provided.

@stronnag
Copy link
Collaborator

I wonder if this will also solve #586, both the affected vehicles have BMP280, whilst my BMP180 craft is unaffected.Will test later today.

@stronnag
Copy link
Collaborator

Flew 4 lipos / 7 distinct flights / one hour air time with this on 1.2.0 master and saw no instance of the random #586 behaviour. I'm more likely to believe that fixes #586 than anything to do with 0f63bc6, as this fix would explain the mid-flight behaviour of #586 observed once. More testing tomorrow on the other BMP280 platform.

@martinbudden
Copy link
Contributor Author

This is good news. I was puzzled as to how 0f63bc6 could cause the problem.

@digitalentity digitalentity merged commit 79fdc6d into iNavFlight:development Sep 18, 2016
@martinbudden martinbudden deleted the inav_baro_bmp280_fix branch September 18, 2016 16:39
@stronnag
Copy link
Collaborator

Please also consider back porting this into master (and a point release, it's bad news for BMP280 users).

@digitalentity
Copy link
Member

I'm going to merge #614 and start towards an intermediate 1.2.1 release.

@digitalentity digitalentity mentioned this pull request Sep 18, 2016
digitalentity pushed a commit that referenced this pull request Sep 18, 2016
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

Successfully merging this pull request may close these issues.

3 participants