-
Notifications
You must be signed in to change notification settings - Fork 964
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
Bug report: "SOME data is TOO OLD" is spamming the debug log before the GPS has locked on satellites #1160
Comments
Do you have a log where this comes up? Thanks! |
done |
This looks like a TEcho? |
I've seen this in the logs of my rak4631_19003 with the RAK-12500 GNSS module as well. |
This is because the T-ECHO GPS does not send Date too often. The timeout of all data is 300ms for position, date and time T-ECHO sends Date every X seconds, which means position and time are sent, but date is "too old" triggering this. I wrote some rant about this on discord some week ago when I had done some testing. A possible work around would be to increase the allowed age of the date-data to 5000ms or even more, depending on what testing will show. |
ernax78 — 01/22/2022 |
Seems like 5000 ms is used in the T-Echo sample code https://github.com/Xinyuan-LilyGO/LilyGO-T-Echo/blob/main/examples/GPS/GPS.ino |
I increased the time to 5000msec and added a bit more verbose logging in case that still happens. I have a feature branch on my TinyGPS Fork that updates date and time regardless of lock status (it's always populated if valid, SoftRF does the same thing in their lib) and merge that back in as soon as the underlying problems with jumping coordinates are identified and fixed. |
It would be nicer to just have this message once, or at least only once per second.
Meshtastic-device/src/gps/NMEAGPS.cpp
Row 119: DEBUG_MSG("SOME data is TOO OLD\n");
Not sure about how to solve this though... :)
The text was updated successfully, but these errors were encountered: