I have two identical lilygo t-echo devices, updated to FW 2.2.15. One shows a GPS lock and updates its location, the other shows “no gps module”. Yet CLI command meshtastic —info shows the device has coordinates.
A factory reset appeared to briefly restore this module’s ability to fully recognize the GPS but after a configuration change, again no gps module found.
Any idea what might be foing on and how i could fix this?
There are some GPS bugs in the firmware 2.2.15 release. They were addressed in 2.2.16.
Releases · meshtastic/firmware (github.com)
Fix typo in GNSS_MODEL definition and usages for the UC6580 by @GPSFan in #2988
Add fallthrough option to avoid a GPS stuck off. by @jp-bennett in #3017
Upgraded to 2.2.16, same problem persists. bummer
Yeah. I am seeing the same issue on my T-Beam with M8N & SX1262 running .13, .15 and .16.
My T-Beams with NEO-6M and Heltec devices seems to work fine.
Upon boot the M8N devices find and lock a location. The M8N devices seem to stop updating their location after boot unless I reboot them.
This might be fixed by Remove gps_attempt_time and use broadcast interval instead by thebentern · Pull Request #3064 · meshtastic/firmware · GitHub which was just merged.
In a last ditch attempt I swapped to a known good GPS antenna and same issue persisted. It is definitely not a hardware issue with the T-Beams with NEO-8.
I appreciate all the cooperation and work people put into the firmware updates, which is way above my knowledge.
There is another GPS bug fix in 2.2.18. It didn’t appear to solve my issue though.
The GPS LED blinks like normal until I flash the firmware. At which point it shuts down.
Here is a log with GPS Warnings. I did replace the Lat/Long coordinates with “XXXXXXXXXX” for the purposes of this post but they are real values.
T-Beam-AXP2101-V1.2
Firmware is 2.2.18.e9bde80
DEBUG | ??:??:?? 1 [Power] Battery: usbPower=1, isCharging=0, batMv=4170, batPct=100
DEBUG | ??:??:?? 1 [GPS] NMEA GPS time 2024-01-15 01:01:52
DEBUG | ??:??:?? 1 [GPS] Upgrading time to quality 4
DEBUG | 01:01:52 1 [GPS] Read RTC time as 1705280512
WARN | 01:01:52 1 [GPS] Warning, 2 new GPS checksum failures, for a total of 2.
DEBUG | 01:01:52 1 [GPS] publishing pos@0:2, hasVal=0, Sats=0, GPSlock=0
DEBUG | 01:01:52 1 [GPS] No GPS lock
DEBUG | 01:01:52 1 [GPS] onGPSChanged() pos@0, time=1705280512, lat=0, lon=0, alt=0
INFO | 01:01:52 1 [GPS] updatePosition LOCAL pos@0, time=1705280512, latI=0, lonI=0, alt=0
DEBUG | 01:01:52 1 [GPS] Setting local position: latitude=0, longitude=0, time=1705280512
DEBUG | 01:01:52 1 [GPS] Node status update: 1 online, 1 total
INFO | 01:01:52 1 [RangeTestModule] Range Test Module - Disabled
INFO | 01:01:54 4 [PowerFSM] Initialise the NimBLE bluetooth module
DEBUG | 01:01:56 6 [GPS] hasValidLocation RISING EDGE
DEBUG | 01:01:56 6 [GPS] WANT GPS=0
DEBUG | 01:01:56 6 [GPS] GPS Lock took 5, average 0
INFO | 01:01:56 6 [GPS] Setting GPS power=0
DEBUG | 01:01:56 6 [GPS] publishing pos@65a48405:2, hasVal=1, Sats=7, GPSlock=1
DEBUG | 01:01:56 6 [GPS] New GPS pos@65a48405:3 lat=XXXXXXXXXX, lon=-XXXXXXXXXX, alt=192, pdop=1.48, track=0.76, speed=0.00, sats=7
DEBUG | 01:01:56 6 [GPS] onGPSChanged() pos@65a48405, time=1705280516, lat=XXXXXXXXXX, lon=-XXXXXXXXXX, alt=192
INFO | 01:01:56 6 [GPS] updatePosition LOCAL pos@65a48405, time=1705280516, latI=XXXXXXXXXX, lonI=-XXXXXXXXXXX, alt=192
DEBUG | 01:01:56 6 [GPS] Setting local position: latitude=XXXXXXXXXX, longitude=-XXXXXXXXXX, time=1705280516
DEBUG | 01:01:56 6 [GPS] Node status update: 1 online, 1 total
INFO | 01:01:56 6 [GPS] Sending smart pos@65a48405:6 to mesh (distanceTraveled=12715400.000000m, minDistanceThreshold=100m, timeElapsed=6610ms)
INFO | 01:01:56 6 [GPS] Providing time to mesh 1705280516
INFO | 01:01:56 6 [GPS] Position reply: time=1705280516, latI=XXXXXXXXXXX, lonI=–XXXXXXXXXXX
DEBUG | 01:01:56 6 [GPS] Initial packet id 79396976, numPacketId 4294967295
DEBUG | 01:01:56 6 [GPS] Update DB node 0x1c50623c, rx_time=1705280516, channel=0
DEBUG | 01:01:56 6 [GPS] handleReceived(LOCAL) (id=0x04bb8072 fr=0x3c to=0xff, WantAck=0, HopLim=3 Ch=0x0 Portnum=3 WANTRESP rxtime=1705280516 priority=10)
DEBUG | 01:01:56 6 [GPS] No modules interested in portnum=3, src=LOCAL
DEBUG | 01:01:56 6 [GPS] localSend to channel 0
DEBUG | 01:01:56 6 [GPS] Add packet record (id=0x04bb8072 fr=0x3c to=0xff, WantAck=0, HopLim=3 Ch=0x0 Portnum=3 WANTRESP rxtime=1705280516 priority=10)
DEBUG | 01:01:56 6 [GPS] Expanding short PSK #1
DEBUG | 01:01:56 6 [GPS] Using AES128 key!
DEBUG | 01:01:56 6 [GPS] ESP32 crypt fr=1c50623c, num=4bb8072, numBytes=35!
DEBUG | 01:01:56 6 [GPS] enqueuing for send (id=0x04bb8072 fr=0x3c to=0xff, WantAck=0, HopLim=3 Ch=0x8 encrypted rxtime=1705280516 priority=10)
DEBUG | 01:01:56 6 [GPS] txGood=0,rxGood=0,rxBad=0
DEBUG | 01:01:56 6 [GPS] Using channel 0 (hash 0x8)
DEBUG | 01:01:56 6 [GPS] Expanding short PSK #1
DEBUG | 01:01:56 6 [GPS] Using AES128 key!
DEBUG | 01:01:56 6 [GPS] ESP32 crypt fr=1c50623c, num=4bb8072, numBytes=35!
DEBUG | 01:01:56 6 [GPS] decoded message (id=0x04bb8072 fr=0x3c to=0xff, WantAck=0, HopLim=3 Ch=0x0 Portnum=3 WANTRESP rxtime=1705280516 priority=10)
No GPS with T-Echo running 2.2.17
I had this same issue with one of my T-Echo units, both running 2.2.17. The fix was to go into Position Config and change the GPS update interval from 0 to the default 120, and change the Fix attempt duration from 0 to the default 900. How it only happened on one unit, I have no idea. Hope this helps all with a similar issue.
Yeah, those config params would not work for me. I need a short GPS update interval (shorter than 10 seconds if it allowed me) but you are correct in that changing the update interval seemed to cause the GPS updates to stop entirely.
I have since upgraded to 2.2.22 (from code locally compiled and loaded) which appears to work with a GPS update interval of 10s. So hopefully this stays working and makes its way to a future release.
Still having this issue on 2.3.10