breadoven
breadoven
> Looks great. Has this already been tested with and without baro, or does that testing need to be done? Well I tested fixed wing and a quad recently which...
Ah well done, you're completely right. `inav_use_gps_no_baro `doesn't only use the GPS if the Baro isn't available, it in fact doesn't use the Baro at all even if available. This...
Actually looking at the history of `navigation_pos_estimator.c`, `inav_use_gps_no_baro `was originally only relevant for a quad and only if no Baro was available so the setting description made more sense: https://github.com/iNavFlight/inav/blob/c411b500b2cec7964a9e465a73f3ac76c84edab9/src/main/navigation/navigation_pos_estimator.c#L619...
With the code as it is now it will use Baro and GPS as available so I think the setting is redundant and should be removed. If you want to...
When disarmed the Altitude should remain around 0 regardless of height changes of the drone itself. However, when Armed altitude should follow and hold the height changes of the drone...
I assume you're using version 7.1.1. If so there's a bug that disables the Baro if `inav_use_gps_no_baro `is set to ON (default setting). Setting to OFF will enable the Baro.
> same like before... > >  > >  Is this armed or disarmed though ?
Nav altitude is calculated from a weighted average of Baro and GPS altitudes + an acceleration factor. More weighting is applied to the Baro than the GPS which is why...
Looks like you had overlapping fields which were blocking out the Lat/Lon fields in the first post. There's the throttle symbol (S shaped) to the left of the 3 for...
I tried this with an F411 and an old Omnibus F4 Pro (F405 I believe) and the Tuning tab works OK for both. That's with the latest Configurator master and...