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
Corrupt GPS data after upgrading to "Improved GNSS module initialization" commit #186
Comments
Confirmed as well, I reverted the commit and it works as expected. |
Even with the latest commit, the issue is not resolved (at least for me, ONE+ model A, external GNSS) |
This commit seems have affect older batch of devices. Could you guys confirm the date of purchase of your device? |
Avoided M10 GNSS commands from being sent as a workaround. |
09/09/23 |
09/12/23 here |
07/28/23 |
The issue is fixed now. It affects ONE+ devices with u-blox m10. It does not affect older batches with m8. The cause: |
Just tried the latest commit and the issue seems indeed solved. Thanks! |
After using the latest telelogger build (1505b85) GPS data coming from the device seems corrput.
The
date
field is always000000
, which causes parsing to fail and no GPS data to be sent or recorded.Without the changes from this commit, everything works as expected.
Device: Freematics One+ Model B (pretty new), internal GPS, WIFI, built with platform.io on Windows
The text was updated successfully, but these errors were encountered: