-
Notifications
You must be signed in to change notification settings - Fork 958
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.3.37 - Bug No GPS Module on TBeams #1630
Comments
Same for me; after installing 1.3.37 I also see a 'No GPS' message on my Tbeam 1.1 with NEO-6M GPS chipset. I'm using a Cirocomm 25mm GPS antenna but that ain't helping me here. |
This is from 1.3.32 Firmware so it looks like it may go back further than 1.3.37 //\ E S H T /\ S T / C ??:??:?? 0 booted, wake cause 0 (boot count 1), reset_reason=reset |
Also using a 25mm GPS Antenna along with those real nice cases you desgined on Thingiverse. Great work on those cases! |
Once I used the power button to power off and back on instead of the reset button I got GPS back |
Thanks! |
the device will attempt to factory reset the GPS Chip if it doesn't detect valid NMEA sentences after 60 seconds. That can happen on a direct change from 1.2 to 1.3. The Reset will require a device reboot though. The state is saved in a proto file, that process may have been interrupted during the latest littlefs debugging attempts. |
I just tested I did try letting them set 5 minutes or so, then rebooting via both the power button, via the reset button, or the python-cli, but there was no change. I will also note that both shortly had the little tiny red led blinking that usually indicates a GPS fix by the module.... |
I eventually got one of my Tbeams working. I ended up watching this video and downloaded the GPS reset code referenced in the video and uploaded to my Tbeams. https://youtu.be/xVaWinSfsz4 It worked for one, but not the other. My GPS red light would also blink suggesting it has a GPS lock. Additionally I was using one of the Tbeams to map the helium network and Re flashing Helium Mapper code brings the GPS back to life, however, if I reflash Meshtastic it once again goes back to No GPS. I don’t think anything is wrong with the hardware but as others have suggested it’s more of a GPS sentence format that seems to somehow be getting jumbled up. |
Does anyone know what the last version does the GPS work for TBeams? |
You need to power cycle your device twice with the power button, wait 5 minutes between each. |
Me Too, I have two modules that I've regularly reflashed to the latest version and these two are working fine. |
Whatever tricks worked for all of you, nothing worked for my NEO6M Tbeam. |
I did get it to work once after flashing the 'GPS reset' from'https://github.com/Xinyuan-LilyGO/LilyGo-LoRa-Series/tree/master/firmware/GPS_%20reset_test?spm=a2g0s.imconversation.0.0.71673e5fxJiloO and then flashing 'firmware-tbeam1.1-1.2.60.ab959de.bin'. The good news is that I got a third screen that went from 'NO GPS' to 'NO GPS LOCK' even though the RED LED is always blinking after ~15 sec in all versions. |
There will be a fix for this when 1.3.41 is released |
Same think I’ve seen on 1.39. I’ve had it eventually show “No GPS Lock” at points as well, but it never actually indicates a lock, even though it appears to have a lock based on the LED behavior.-NickOn Sep 16, 2022, at 6:03 AM, pcopa ***@***.***> wrote:
I did get it to work once after flashing the 'GPS reset' from'https://github.com/Xinyuan-LilyGO/LilyGo-LoRa-Series/tree/master/firmware/GPS_%20reset_test?spm=a2g0s.imconversation.0.0.71673e5fxJiloO and then flashing 'firmware-tbeam1.1-1.2.60.ab959de.bin'. The good news is that I got a third screen that went from 'NO GPS' to 'NO GPS LOCK' even though the RED LED is always blinking after ~15 sec in all versions.
But today I restated my 1.3.40 version and I'm back to 'NO GPS' and only two screens.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Following up on this: I have 3 T-Beam v1.1, just recently arrived from Shenzhen. All three initially had the "No GPS Module" symptom. I flashed all three with the GPS Reset V3 sketch, and it seemed to do the trick; the NEO-6M units all started printing out NMEA data at this point. I re-flashed them with Meshtastic firmware 1.3.40, Now they all say "No GPS Lock", which (I suppose) indicates that the unit thinks it's getting valid NMEA data, but the data is telling it that it can't see satellites. Strangely, the red GPS LED is blinking at 1Hz on all three units suggesting there is a lock. I went back to the GPS-reset V3 sketch and connected with TerraTerm. I can see that the NEO-6M actually does have a lock, even in my relatively terrible basement window! This suggests to me that the 1.3.40 firmware is not parsing the NMEA stream correctly or something like that. It might be nice if there was a mode to ask the Meshtastic firmware itself what it thinks it's seeing from the Ublox, because it's unclear to me why it isn't able to parse the stream. Here is what I got from the GPS reset sketch firmware:
Hello from Calgary, Alberta. |
I can confirm this appears to have fixed the problem on 5 of my TBeam modules. (1.3.41.80ddb81) |
Is everyone able to change settings e.g. Lora region after this update? The iphone app crashes when I click on the Lora sub-menu for me after this. The app appears to still be 1.3.40. |
I used the python client via USB to program all mine. I noted that this update after flashing, I seem to have to unplug USB, hard power off the module, power back on, plug USB before I can change these settings like region, name, etc. I would assume you could set these via the app as well after a reboot: flash, hard power off module, power on module, connect, configure. But note that I have not tested this myself yet. |
@1n5aN1aC Thanks, I tried that - the Python client is giving me "Timed out waiting for connection completion". I have tried the full reboot cycle. |
Had the same issue.pip install —upgrade Meshtastic —prethen… meshtastic —set lora.region <your region>Still “No GPS” for me on 1.3.41On Sep 18, 2022, at 10:07 PM, Alexander Farley ***@***.***> wrote:
@1n5aN1aC Thanks, I tried that - the Python client is giving me "Timed out waiting for connection completion". I have tried the full reboot cycle.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Updating the cli as suggested by @ndoolin worked for me and now my devices all appear to be functioning well via the CLI. Looking forward to trying the new iPhone app! |
all mine are working with 1.3.41 |
I updated my tbeams from 1.2.x (can't remember exact version) to 1.3.41 and I think I'm experiencing this issue. I have two tbeam v1.0, and both of them report "no GPS module" after the update. The amber GPS led never blinks. I tried using the GPS-reset-v3 sketch, and that was able to get a lock and output my coordinates to the serial monitor. When I then reflashed with 1.3.41, it reported "no GPS lock" instead of "no GPS module", managed to get a lock, and worked perfectly normally until I unpowered the device and turned it back on. Then it went back to "no GPS module." The GPS stays broken until I reflash with the reset sketch and then 1.3.41, and immediately breaks again as soon as the device loses power. I don't have a tbeam v1.1 to see if this is specific to something I'm doing wrong, or to the tbeam v1.0. The only difference in the startup output from working to not working is the addition of the line |
Have you power cycled (not reset)twice waiting 5 minutes in between? It has fixed every device I have tried it on. |
By power cycling, do you mean turning it off by holding the power button, then back on, like was said in a comment further up? If so, yeah I've done that. Turned it on, waited >5 minutes, turned it off then back on, waited >5 minutes, repeated that a few times on each device in hopes it would work. Hasn't made a difference, only way I've found to get GPS working is by using the reset-v3 sketch and then making sure the device doesn't lose power while I want to use it. |
@Kaeteker : what I usually do after I've re-flashed and it doesn't work, I will:
Just my observations:
Good luck |
I tried the power cycle thing on my TBeam on 2.0.0 to no avail. The So it seems, to me at least, that the attempts to reset the GPS from the Meshtastic firmware aren't working. Wondering if this should be re-opened, but my own problem is solved, so I won't push for it. |
Same, still having issues on the latest firmware. Have to use Lilygo reset .ino, then it'll work. But weirdly, after turning on and off, GPS will stop working and show No GPS Module. |
My T-Beam v1.1 boards show the same symptom - "No GPS Lock" with two dots on the display. Was this issue ever fully resolved? |
No GPS Lock is not the same error, your device GPS had been detected and is working and has not managed to get a lock. |
What I did is: Version is T-BEAM-V1.1 |
Looks like we may have turned down the GPS interrogation too much, I am consistently getting No GPS Module on my tbeam with 1.3.37
This is all I see for GPS in the serial logs when doing a reset
??:??:?? 1 WANT GPS=1
??:??:?? 1 GxGSA NOT available
The text was updated successfully, but these errors were encountered: