I have flown with the default settings, which give steady results. Although I haven't yet done an automatic landing. So I intend to do some tests as the altitude is a bit more crucial on landing.
Has anyone fiddled with this parameter or know a reason why GPS is better?
For reference here's the relevant extract:
| // ALTITUDE_MIX OPTIONAL |
| // |
| // Configures the blend between GPS and pressure altitude. |
| // 0 = GPS altitude, 1 = Press alt, 0.5 = half and half, etc. |
| // |
| // The default is to use only GPS altitude. |
| // |
| //#define ALTITUDE_MIX 0 |
Replies
Often it is a default because we think it will be "safer" for a broader range of people/systems. Sometimes it is a default because it was just the way we are used to doing it. Sometimes it is the default because one of us forgets to change it from our personal setting to what we intend to be the default when we commit changes to the repository and it just gets perpetuated.
Some day when we have time (meaning likely never) we will go through and "fix" all the defaults ;)
But on this particular issue, I am in agreement. I think 100% baro is the way to go. It looks much better particularly around the transitions when you start or stop climbing or descending.
GPS is a known quantity and we had earlier issues with the BPM library. That's all sorted now for the release and the pressure is beating the GPS in accuracy.
Jason