It sounds to me like you either have a hardware issue with the Mamba MK4 H743 V2 FC, or Betaflight just doesn't yet have the correct driver support for the particular barometer it is making use of. Did you end up raising a GitHub issue for it?

I believe in your original post you mentioned you had a Geprc M10 GPS module, and that comes with a magnetometer and barometer on the module. If you connected the SDA SCL pins then you should be able to use that barometer, however not sure how BF handles multiple baros. If you do want to use that baro then you would need the custom define BARO_DPS310 for 4.4.

(13-Jan-2024, 01:02 PM)SnowLeopardFPV Wrote: Did you end up raising a GitHub issue for it?

Not yet, I was trying first to get a new spare FC to confirm that Baro works on a brand new FC but I couldn't find anywhere in stock anymore so I guess I'll raise an issue

(13-Jan-2024, 05:52 PM)mstc Wrote: I believe in your original post you mentioned you had a Geprc M10 GPS module, and that comes with a magnetometer and barometer on the module. If you connected the SDA SCL pins then you should be able to use that barometer, however not sure how BF handles multiple baros. If you do want to use that baro then you would need the custom define BARO_DPS310 for 4.4.

Is not the Geprc module, is the iFlight Blitz M10 and as far as I can tell this one doesn't have a baro.

A quick update on this. I have raised a GitHub and one of the developers suggested when I connect FC to BetaFlight to also power it up and then restart it. That was the only sequence that made that FC to detect a Baro. However, the values were way off, and clearly, something was wrong with it. I did not quite understand what was different in that sequence why needed to be powered it up and then restarted it.

Anyway, I managed to find the same FC somewhere in stock so I've ordered a new one. The new one shows Baro no problem when connected to USB - C with the same BF version (no need to power it up or restart it). So I'm going to replace the old one and test again if the alt values make sense and if GPS rescue works.

(12-Jan-2024, 09:50 PM)Green_Weedle Wrote: Not sure if its related, but mine tried to rocket to the moon yesterday too when still using BF4.5 RC1.  I had it set to use  "current altitude" and don't have a barometer or magnetometer.  I tried again later with a fixed altitude setting and 1M initial rise, AND dropping my gyro to 4K (I think the release notes say GPS rescue code is resource intensive).   It seemed a little better, no un-commanded blast-off, but a little wonky still?   (I would have noodled with it a bit more in the field, but Speedy Bee is not ready for BF4.5 yet.)

I'm going to try again today with BF4.5 RC2 and will report back.

I don't mean to hijack the thread as it's is not related to the Baro per se, but I wanted to report that mine still shoots for the moon on RC2 when set to either "hold current altitude "or "use max altitude"  for GPS rescue (trying to go much higher than what I see as current altitude in OSD, his is a little unstable, but a point of reference).  If I set for a specific altitude, it seems to do better, but still not well tested enough to say for sure.  I'm only using GPS, no compass, no baro, so not ideal for rescue as is  Still testing...