Lilygo T-Beam V1.1 no GPS fix

Support
1

So I bought Lilygo T-Beam V1.1 with NEO-6M GPS module. I installed V2.2.9.47301a5 on it with web flasher but Meshtastic shows “No sats” & “No GPS Lock”.
No satellites where found even if I left the device outside for an hour.
There is no lights on or flashing near the GPS module.

Does anyone know what is wrong here?

Console output after reset looks like this:

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13192
load:0x40080400,len:3028
entry 0x400805e4
E (861) esp_core_dump_flash: No core dump��ѥѥ���found!
E (861) esp_core_dump_flash: No core dump partition found!
[ 12][D][esp32-hal-cpu.c:244] setCpuFrequencyMhz(): PLL: 480 / 2 = 240 Mhz, APB: 80000000 Hz
[ 464][I][esp32-hal-psram.c:96] psramInit(): PSRAM enabled
��@INFO | ??:??:?? 0

//\ E S H T /\ S T / C

INFO | ??:??:?? 0 Booted, wake cause 0 (boot count 1), reset_reason=reset
DEBUG | ??:??:?? 0 Filesystem files (491520/1048576 Bytes):
DEBUG | ??:??:?? 0 /prefs/channels.proto (53 Bytes)
DEBUG | ??:??:?? 0 /prefs/config.proto (90 Bytes)
DEBUG | ??:??:?? 0 /prefs/db.proto (181 Bytes)
DEBUG | ??:??:?? 0 /static/.gitkeep (0 Bytes)
DEBUG | ??:??:?? 0 /static/Logo_Black.svg.gz (592 Bytes)
DEBUG | ??:??:?? 0 /static/Logo_White.svg.gz (600 Bytes)
DEBUG | ??:??:?? 0 /static/apple-touch-icon.png.gz (3162 Bytes)
DEBUG | ??:??:?? 0 /static/favicon.ico.gz (2221 Bytes)
DEBUG | ??:??:?? 0 /static/icon.svg.gz (842 Bytes)
DEBUG | ??:??:?? 0 /static/index-0e7e3601.js.gz (203665 Bytes)
DEBUG | ??:??:?? 0 /static/index-f369114b.css.gz (17105 Bytes)
DEBUG | ??:??:?? 0 /static/index-fc2e9253.js.gz (347 Bytes)
DEBUG | ??:??:?? 0 /static/index.html.gz (547 Bytes)
DEBUG | ??:??:?? 0 /static/maplibre-gl-354afb20.js.gz (207264 Bytes)
DEBUG | ??:??:?? 0 /static/robots.txt.gz (42 Bytes)
DEBUG | ??:??:?? 0 /static/site.webmanifest.gz (196 Bytes)
[ 940][I][esp32-hal-i2c.c:75] i2cInit(): Initialising I2C Master: sda=21 scl=22 freq=100000
[ 942][I][XPowersCommon.tpp:248] begin(): SDA:21 SCL:22
[ 946][W][Wire.cpp:301] begin(): Bus already started in Master Mode.
INFO | ??:??:?? 0 AXP2101 PMU init succeeded, using AXP2101 PMU
[ 979][D][XPowersAXP2101.tpp:2791] setInterruptImpl(): DISABLE - HEX:0xffffffff BIN:
DEBUG | ??:??:?? 0 =======================================================================
DEBUG | ??:??:?? 0 DC1 : + Voltage:3300 mV
DEBUG | ??:??:?? 0 DC2 : - Voltage:900 mV
DEBUG | ??:??:?? 0 DC3 : - Voltage:900 mV
DEBUG | ??:??:?? 1 DC4 : - Voltage:1100 mV
DEBUG | ??:??:?? 1 ALDO1: - Voltage:1800 mV
DEBUG | ??:??:?? 1 ALDO2: + Voltage:3300 mV
DEBUG | ??:??:?? 1 ALDO3: + Voltage:3300 mV
DEBUG | ??:??:?? 1 ALDO4: - Voltage:2900 mV
DEBUG | ??:??:?? 1 BLDO1: - Voltage:1800 mV
DEBUG | ??:??:?? 1 BLDO2: - Voltage:2800 mV
DEBUG | ??:??:?? 1 =======================================================================
DEBUG | ??:??:?? 1 Battery: usbPower=1, isCharging=1, batMv=4172, batPct=84
INFO | ??:??:?? 1 Scanning for i2c devices…
[ 1050][W][Wire.cpp:301] begin(): Bus already started in Master Mode.
DEBUG | ??:??:?? 1 Scanning for i2c devices on port 1
DEBUG | ??:??:?? 1 I2C device found at address 0x34
INFO | ??:??:?? 1 axp192/axp2101 PMU found
DEBUG | ??:??:?? 1 I2C device found at address 0x3c
INFO | ??:??:?? 1 ssd1306 display found
INFO | ??:??:?? 1 ssd1306 display found
DEBUG | ??:??:?? 1 0x4 subtype probed in 2 tries
INFO | ??:??:?? 1 2 I2C devices found
DEBUG | ??:??:?? 1 acc_info = 0
INFO | ??:??:?? 1 Meshtastic hwvendor=4, swver=2.2.9.47301a5
DEBUG | ??:??:?? 1 Setting random seed 3995409353
DEBUG | ??:??:?? 1 Total heap: 186216
DEBUG | ??:??:?? 1 Free heap: 151964
DEBUG | ??:??:?? 1 Total PSRAM: 4192107
DEBUG | ??:??:?? 1 Free PSRAM: 4191847
DEBUG | ??:??:?? 1 NVS: UsedEntries 90, FreeEntries 540, AllEntries 630, NameSpaces 3
DEBUG | ??:??:?? 1 Setup Preferences in Flash Storage
DEBUG | ??:??:?? 1 Number of Device Reboots: 6
DEBUG | ??:??:?? 1 OTA firmware version 0.2.1.2fbe7fc
INFO | ??:??:?? 1 Initializing NodeDB
INFO | ??:??:?? 1 Loading /prefs/db.proto
INFO | ??:??:?? 1 Loaded saved devicestate version 22
INFO | ??:??:?? 1 Loading /prefs/config.proto
INFO | ??:??:?? 1 Loaded saved config version 22
[ 1237][E][vfs_api.cpp:105] open(): /littlefs/prefs/module.proto does not exist, no permits for creation
INFO | ??:??:?? 1 No /prefs/module.proto preferences found
INFO | ??:??:?? 1 Installing default ModuleConfig
INFO | ??:??:?? 1 Loading /prefs/channels.proto
INFO | ??:??:?? 1 Loaded saved channelFile version 22
[ 1305][E][vfs_api.cpp:105] open(): /littlefs/oem/oem.proto does not exist, no permits for creation
INFO | ??:??:?? 1 No /oem/oem.proto preferences found
DEBUG | ??:??:?? 1 cleanupMeshDB purged 0 entries
DEBUG | ??:??:?? 1 Number of Device Reboots: 6
DEBUG | ??:??:?? 1 Expanding short PSK #1
INFO | ??:??:?? 1 Wanted region 3, using EU_868
DEBUG | ??:??:?? 1 region=3, NODENUM=0x7a6d6780, dbsize=2
INFO | ??:??:?? 1 Saving /prefs/db.proto
WARN | ??:??:?? 1 SPI.begin(SCK=5, MISO=19, MOSI=27, NSS=18)
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
INFO | ??:??:?? 1 External Notification Module Disabled
INFO | ??:??:?? 1 Turning on screen
DEBUG | ??:??:?? 1 Module wants a UI Frame
DEBUG | ??:??:?? 1 Module wants a UI Frame
WARN | ??:??:?? 1 RF95Interface(cs=18, irq=26, rst=23, busy=33)
INFO | ??:??:?? 1 Starting meshradio init…
DEBUG | ??:??:?? 1 (bw=250, sf=11, cr=4/8) packet symLen=8 ms, payloadSize=0, time 231 ms
DEBUG | ??:??:?? 1 (bw=250, sf=11, cr=4/8) packet symLen=8 ms, payloadSize=253, time 3246 ms
INFO | ??:??:?? 1 Radio freq=869.525, config.lora.frequency_offset=0.000
INFO | ??:??:?? 1 Set radio: region=EU_868, name=LongFast, config=0, ch=0, power=27
INFO | ??:??:?? 1 Radio myRegion->freqStart → myRegion->freqEnd: 869.400024 → 869.650024 (0.250000 mhz)
INFO | ??:??:?? 1 Radio myRegion->numChannels: 1 x 250.000kHz
INFO | ??:??:?? 1 Radio channel_num: 1
INFO | ??:??:?? 1 Radio frequency: 869.525024
INFO | ??:??:?? 1 Slot time: 42 msec
INFO | ??:??:?? 1 Set radio: final power level=20
DEBUG | ??:??:?? 1 Current limit set to 100.000000
DEBUG | ??:??:?? 1 Current limit set result 0
INFO | ??:??:?? 1 RF95 init result 0
INFO | ??:??:?? 1 Frequency set to 869.525024
INFO | ??:??:?? 1 Bandwidth set to 250.000000
INFO | ??:??:?? 1 Power output set to 20
INFO | ??:??:?? 1 RF95 Radio init succeeded, using RF95 radio
INFO | ??:??:?? 1 Not using WIFI
DEBUG | ??:??:?? 1 (bw=250, sf=11, cr=4/8) packet symLen=8 ms, payloadSize=237, time 3057 ms
DEBUG | ??:??:?? 1 LoRA bitrate = 77.526985 bytes / sec
INFO | ??:??:?? 1 PowerFSM init, USB power=1
DEBUG | ??:??:���*�ѕɁstate: BOOT
[ 1915][D][esp32-hal-cpu.c:244] setCpuFrequencyMhz(): PLL: 320 / 4 = 80 Mhz, APB: 80000000 Hz
DEBUG | ??:??:?? 1 [Power] Battery: usbPower=1, isCharging=1, batMv=4173, batPct=84
DEBUG | ??:??:?? 1 [Screen] Screen: Started…
DEBUG | ??:??:?? 1 [GPS] Probing for GPS at 9600
INFO | ??:??:?? 2 [GPS] Found a UBlox Module using baudrate 9600
DEBUG | ??:??:?? 2 [GPS] Module Info :
DEBUG | ??:??:?? 2 [GPS] Soft version: 7.03 (45969)
DEBUG | ??:??:?? 2 [GPS] Hard version: 00040007
DEBUG | ??:??:?? 2 [GPS] Extensions:0
WARN | ??:??:?? 3 [GPS] Unable to save GNSS module configuration.
INFO | ??:??:?? 3 [RangeTestModule] Range Test Module - Disabled
DEBUG | ??:??:?? 3 [GPS] publishing pos@0:2, hasVal=0, Sats=0, GPSlock=0
DEBUG | ??:??:?? 3 [GPS] No GPS lock
DEBUG | ??:??:?? 3 [GPS] onGPSChanged() pos@0, time=0, lat=0, lon=0, alt=0
INFO | ??:??:?? 3 [GPS] updatePosition LOCAL pos@0, time=0, latI=0, lonI=0, alt=0
DEBUG | ??:??:?? 3 [GPS] Node status update: 2 online, 2 total
DEBUG | ??:??:?? 4 [GPS] NMEA GPS time 2049-55-222 112:16:81
DEBUG | ??:??:?? 4 [GPS] Upgrading time to quality 4
DEBUG | 16:17:21 4 [GPS] Read RTC time as -1780990466
DEBUG | 22:53:50 4 [GPS] publishing pos@0:2, hasVal=0, Sats=0, GPSlock=0
DEBUG | 22:53:50 4 [GPS] onGPSChanged() pos@0, time=2513976830, lat=0, lon=0, alt=0
INFO | 22:53:50 4 [GPS] updatePosition LOCAL pos@0, time=2513976830, latI=0, lonI=0, alt=0
DEBUG | 22:53:50 4 [GPS] Node status update: 2 online, 2 total
INFO | 22:53:50 4 [PowerFSM] Initialise the NimBLE bluetooth module
INFO | 22:53:53 7 [Screen] Done with boot screen…
DEBUG | 22:53:53 7 [Screen] showing standard frames
DEBUG | 22:53:53 7 [Screen] Showing 0 module frames
DEBUG | 22:53:53 7 [Screen] Total frame count: 103
DEBUG | 22:53:53 7 [Screen] Added modules. numframes: 0
DEBUG | 22:53:53 7 [Screen] Finished building frames. numframes: 3
DEBUG | 22:54:07 21 [Power] Battery: usbPower=1, isCharging=1, batMv=4172, batPct=84

2

I’ve experienced my GPS locking up on my TBeams every so often after updating my firmware.

On this website there is a GPS reset firmware I use. Once you load the firmware, it will reset your GPS. You’ll have to reload the meshtastic firmware again.

Good luck

3

Can you verify that it is indeed 1.1 and not a 1.2? There’s printed silkscreen next to the sma connector that has the version number. There’s a known issue with v1.2 teams having issues with the GPS.

4

Now that I look at the really small print next to the sma connector, it really says TBeam-AXP2101-V1.2 20230508 there…So it may actually be v1.2.
These model markings are quite confusing. At the end of the board there is a decent size sticker that says “MODEL: T-BEAM-V1.1”

Is there any solution to the GPS problem in v1.2?

5

The latest version without gps problems for me, with the Lilygo, is 2.2.4

6

That is indeed the 1.2, the axp2101 is the new chip that required the change.

Not at this time, but there’s someone working on resolving it currently.

7

Thanks for the replies everyone.
As Chrichton said it seems that the problem with my unit is that it is from a new batch that has axp2101 in it, so it would require code changes for the GPS to work.
I read that all the new units are now coming with axp2101 so I hope someone updates the code at some point.

The code that N1obu linked might work if someone has GPS problems with older T-Beam that has axp192 in it. It was not the solution for my case unfortunately.

8

I also have TBeam-AXP2101-V1.2 boards and up to firmware-2.2.4.3bcab0e GPS works fine.
All updates after that, up to firmware-2.2.9.47301a5, have given troubles with the GPS.

9

Wow. I tried again by rolling all the way to Meshtastic V2.1.23 beta… and it actually worked. For the first time it found some satellites, and I saw the little red GPS light blink.
Thanks :smiley:

10

I’ve got two t-beams V1.1 with firmware 2.2.10. At first I had an issue with the GPS (saying no GPS module/no sats), same as Un5, I set it outside for 20 minutes and it found nothing. Then I got to thinking, I recalled some applications have issues connecting to the mobile phone when the mobile data is turned on, or in this case the phones location service is on. I turned off my phones location, rebooted the t-beams and sure enough, the no GPS module message disappeared and the GPS began to work shortly after that. I’m not sure if anyone else has tried this. Once I got it to work, I confirmed it was the issue by recreating the problem again and again and it is replicatable. For some reason or another, the app feeding the phones gps into the system and the t-beams sees that during connection or boot and doesn’t like it, and never turns on the GPS module. In debug it’s also seen not turning on the GPS during that situation.

16967846239361321198130880600263
169678462393613211981308806002631908×4032 762 KB

11

Some what older thread but I noticed there isn’t much on v1.2. I recently purchased the tbeams that are sent with AXP2101-v1.2. I tried many of the suggestions above because I was also having an issue with “no gps lock” or blinking red light near the antenna connection. No luck.

I then bounced around with different firmwares and version 2.2.2 seemed to do the trick. Updated both of my modules and both now work and show their locations.

Phone’s were androids in airplane mode, bluetooth enabled, gps turned off.

Hope this helps.

12

The fix was put in place with version 2.2.1, so anything after that will work.

13

Oh, perfect. Thanks.

14

Same issue here.
I have 2 devices, both AXP2102-v1.2 ,
They both had 2.1.5 installed, and I tried one with the original firmware, and the GPS worked after a few minutes.
The other one however, I did not try to start up, but installed 2.2.17 and it never showed any GPS. I tried installing 2.2.11, but still no luck.

15

Nevermind… I’m getting GPS lock now, after cleaning the tiny connector.

16

Not sure if this is the right place to post, but…

I have T-beam that had been working great for about a month. I have been driving around with it in my car and my buddy could track my location with a few kilometers.
Now when I use the Meshtastic app on android AND even using serial port, the T-Beam absolutely refuses to turn on the GPS. I click on “Position” and then I click on “ENABLE” and hit the floppy disk icon in the upper right (when using client.mesh…on serial port) or when I use the app, I click on “Position” and then “ENABLE” GPS and it always refuses to stick. I can change the number of seconds it broadcast GPS and it sticks. I put everything to 60 seconds and they all stick after reboot.

Now I just noticed that after rebooting the android phone, the GPS ins finally “ENABLED” but I’m not sure if it actually works. The “Smart position enabled” slider button is disabled and the “GPS mode” “ENABLED” AND it has been well over two minutes and I cannot “Request position” via another radio.

I upgraded from 2.2.19 to 2.2.23 via web flasher on Opera on Arch Linux but no help.

17

I also have two T-Echo devices and they both refuse to “ENABLE” “GPS mode” and, yet, they seem to be putting out GPS coordinates that seem to be correct. So I am confused to say the least.

1 Like