You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The calculated telemetry sensor "distance" delivers erratic output.
Expected Behavior
Distance calculation outputs actual distance to initial GPS position.
Steps To Reproduce
The error occurs on radio and simulator. To reproduce use the simulator with enabled telemetry simulator:
setup model and discover telemetry
add calculated telemetry sensor using GPS and Alt, name it "GPdi"
initialize Alt to an arbitrary value e.g. 123m and the GPS position to 25.9973,-97.15712.
Go to Reset telemetry/Reset flight to auto-offset ALT and set the initial GPS Position
check Alt and GPS to be the set GPS position, Alt to be 0m and GPdi to be 0m
change GPS position to 25.9973,-97.15711 (i.e. change least significant longitude digit from 2 to 1 resulting in a change of 0.1 seconds). Expect distance now to be slightly less than 1m.
Sharing the calculated earth radius of the pilot's GPS position (home point) with value in a union leads to overwriting the earth radius upon craft's position because value is newly used to store a hash to allow value widget to recognize change in crafts's lat/lon.
changes:
- moved storage of home point earth radius to gps struct to prevent overwriting the home point earth radius. This should not affect RAM usage.
Is there an existing issue for this problem?
What part of EdgeTX is the focus of this bug?
Transmitter firmware
Current Behavior
The calculated telemetry sensor "distance" delivers erratic output.
Expected Behavior
Distance calculation outputs actual distance to initial GPS position.
Steps To Reproduce
The error occurs on radio and simulator. To reproduce use the simulator with enabled telemetry simulator:
Version
2.9.2
Transmitter
RadioMaster TX16S / TX16SMK2
Operating System (OS)
No response
OS Version
No response
Anything else?
If was a gambler I'd put my money on #4250
The text was updated successfully, but these errors were encountered: