-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
BF 4.5 RC3 CRSF altitude isn't working as expected #13513
Comments
|
|
Check your Baro after reading the Baro wiki note at Betaflight.com. |
I suspect the conformal coating covering the baro. |
tested with BF 4.3 - same thing. Closing as this has nothing to do with the FW changes |
that's what I'm hinting at. A situation when the altitude changes several hundred meters back and forth in the mid flight could be a serious problem in some flight modes. The was a weighting factor which is 100 by default, so to my opinion only baro should be used but this is not the case. Maybe I don't quite understand how that As I soldered a BMP280 additionally I could test with it that |
Describe the bug
Altitude sent by the FC to the transmitter over CRSF is off the scale or doesn't work at all. Before arming the absolute altitude is shown. Then just after arming it's resetted to zero and then climbs up even if the drone is still on the ground. Then the altitude shown is completely wrong and thats why the variometer goes crazy too.
Watch this video for the details https://youtu.be/bI-lvkCp-eA
Check the altitude map in the lower left corner. 442 is the absolute height in that area
To Reproduce
Compile and install BF 4.5 RC3 upon commit 5457032
Use a transmitter with CRSF protocol and check displayed altitude
Expected behavior
Altitude works the same as in BF 4.3
Support ID
Flight controller
SPEEDYBEEF405V4
Other components
No response
How are the different components wired up (including port information)
No response
Add any other context about the problem that you think might be relevant here
No response
The text was updated successfully, but these errors were encountered: