Baro may return wrong value

[ledvinap]

This bug is present (but probably much harder to trigger) in baseflight: cleanflight/cleanflight#720

[trollcop]

unless you're actually contributing something (like working code), may I
politely request you to go fuck yourself, good sir?
On Apr 3, 2015 9:42 PM, "Petr Ledvina" notifications@github.com wrote:

This bug is present (but probably much harder to trigger) in baseflight:
cleanflight/cleanflight#720
cleanflight/cleanflight#720

—
Reply to this email directly or view it on GitHub
#269.

[digitalentity]

@trollcop, actually @ledvinap got a point. This bug is likely present in baseflight. Took a while to figure it out here cleanflight/cleanflight#569.
In baseflight this line

baseflight/src/sensors.c

Line 361 in 5fffabb

baroDeadline = currentTime;

probably should be changed to
baroDeadline = micros();
to fix this.

[trollcop]

great, go ahead and change it.
I'm not clicking any links with joblessflight in them.
On Apr 3, 2015 9:56 PM, "Konstantin Sharlaimov" notifications@github.com
wrote:

@trollcop https://github.com/trollcop, actually @ledvinap
https://github.com/ledvinap got a point. This bug is likely present in
baseflight. Took a while to figure it out here cleanflight/cleanflight#569
cleanflight/cleanflight#569.
In baseflight this line

baseflight/src/sensors.c

Line 361 in 5fffabb

baroDeadline = currentTime;

probably should be changed to
baroDeadline = micros();
to fix this.

—
Reply to this email directly or view it on GitHub
#269 (comment).