meshtastic / firmware

Meshtastic device firmware
https://meshtastic.org
GNU General Public License v3.0
3.31k stars 801 forks source link

[Feature Request]: GPS default altitude 0 in stead of 42.950km #3331

Closed BjornB2 closed 6 months ago

BjornB2 commented 6 months ago

Platform

ESP32

Description

It seems that when my Heltec with external GPS can't determine the altitude it defaults to 42.950km. It would maybe be better to override the altitude to 0m when this occurs.

thebentern commented 6 months ago

Never seen this before. Do you have any serial logs to illustrate this occurring?

BjornB2 commented 6 months ago

Not really I'm afraid. I see there is also a debug log option that I can enable in the device settings. Could I use that to get the required info? If so, where do I find the log after enabling this?

BjornB2 commented 6 months ago

Attached it to my computer and let it run for a minute. See log attached. I changed part of the lat and long for privacy reasons so that is why there are ###'s there.

mesthastic.log

If you look at the GPS data you see alt=429xxxxx a couple of times and then it changes to alt=5

I hope this helps. I did have the exact same issue with my T-beam 1.1 btw. I set that one to fixed because of it.

Danie10 commented 6 months ago

I have my Heltec V3 set as fixed location with altitude 14m. Have noticed more than once if I share phone GPS, that when I return home and disable phone GPS share, the fixed location shows the phone's last shared GPS, but has also changed the altitude to 49m. I'd definitely not gone up by 49m so could be that Meshtastic is incorrectly interpreting altitude from phone GPS. Interestingly, the 14m or 15m equates to about 49 feet. Could it be that it is multiplying the phone's GPS altitude in metres to feet? My phone is set to metric, but maybe the raw GPS is in US feet?

andrekir commented 6 months ago

Duplicate of #3109:

This is a unsigned/signed problem and does not have anything to do with the specific device. problem is either in TinyGPS++ or in our backend code. The device thinks it's 1400m below sea level.