Gerd_S.gmx
lvl.3
Flight distance : 4303379 ft
Germany
Offline
|
Hi,
I reported a bug within the Goggles firmware (all existing versions) by emailing to support@dji.com and have run into a fight with unqualified support personel about what is a bug and what is not, because of they didn't understand the difference between VPS altitude and barometric altitude!
So please DJI, ensure that bug reports are getting handled and analysed by qualified personel who have at least practical experience with using your products and ensure that verified bug reports are really forwarded to your app and/or firmware developer teams for getting fixed with next software versions!
VPS altitude is not always displayed when applicable:
I found out that VPS altitude will be only displayed while barometric altitude is less than 10m instead of always being displayed while valid (valid up to about 13m over solid ground and independent of barometric altitude)
Imagine you are taking off near a building which is e.g. 10m in height and has a flat roof. Now ascend until you are above the roof and try to
land on it. You would expect the barometric altitude showing e.g. 12 meters and the VPS kicking in and showing 2 meters above the roof. But the Goggles will
just display the baro altitude of 12 meters and the VPS field is hidden, although there is a valid value which is shown on your mobile running GO4 app.
So the decision for showing VPS altitude must not depend on barometric altitude but on its validity only, same as it is implemented within the
GO4 app.
Actually there seems to run a false algorithm of that kind:
if (baroAltitude > 10.0) {
hide.VPS()
} else {
show.VPS()
}
Again, please see screenshots, only difference is 1m more altitude in right one, leading to VPS altitude no longer being displayed.
When looking onto my mobile running GO4, VPS altitude is available there for both situations as should be the case with the Goggles, too!
|
|