Any update? I have same issue. I though I had t-beam 1.1, though inspecting a bit more it has a smaller sticker stating v1.2.
I’ve searched multiple forums and solutions and I’ve tried (with no luck):
- some reset GPS scripts (they did delete my meshtastics, afterwards I always had to load it back)
- different version of firmware, 2.2.14 beta, 2.2.15 beta, 2.2.19.8f6a283 Alpha and older one 2.1.23.04bbdc6 Beta whish some clamed it should work.
- tried switching GPS IO to TX on 34 and RX on 12 (since the board drawing I found in every place states such pins) - it failed on boot with “E (1633) uart: uart_set_pin(683): tx_io_num error”
Not sure what else to try. Is there some easy way to debug it? manually seeing GPS status via terminal?
Few people also noted that blinking red led indicates that GPS has lock - I have not seen any lock so far.
Here is log with latest firmware (2.2.19 alpha):
DEBUG | ??:??:?? 1 Read RTC time as 1
INFO | ??:??:?? 1 Setting GPS power=1
DEBUG | ??:??:?? 1 WANT GPS=1
INFO | ??:??:?? 1 Setting GPS power=1
DEBUG | ??:??:?? 1 Using GPIO34 for GPS RX
DEBUG | ??:??:?? 1 Using GPIO12 for GPS TX
DEBUG | ??:??:?? 1 NeighborInfoModule is disabled
<..>
DEBUG | ??:??:?? 1 [Screen] Screen: Started...
WARN | ??:??:?? 1 [GPS] Warning, 1 new GPS checksum failures, for a total of 1.
DEBUG | ??:??:?? 1 [GPS] publishing pos@0:2, hasVal=0, Sats=0, GPSlock=0
DEBUG | ??:??:?? 1 [GPS] No GPS lock
DEBUG | ??:??:?? 1 [GPS] onGPSChanged() pos@0, time=0, lat=0, lon=0, alt=0
INFO | ??:??:?? 1 [GPS] updatePosition LOCAL pos@0, time=0, latI=0, lonI=0, alt=0
DEBUG | ??:??:?? 1 [GPS] Setting local position: latitude=0, longitude=0, time=0
DEBUG | ??:??:?? 1 [GPS] Node status update: 2 online, 2 total
INFO | ??:??:?? 1 [RangeTestModule] Range Test Module - Disabled
<..>