Skip to content
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

Problem with date #52

Open
iw9grl opened this issue Jan 15, 2022 · 4 comments
Open

Problem with date #52

iw9grl opened this issue Jan 15, 2022 · 4 comments

Comments

@iw9grl
Copy link

iw9grl commented Jan 15, 2022

Hi

after GPS fix, the time is set correctly ( UTC ) but the date remain to 31/12/1999 also after several hour .

could you please help me ?
thank you
73

@peterus
Copy link
Member

peterus commented Jan 21, 2022

you are not the only one who is having issues like this.
currently there is no fix for this as the data is coming directly from the gps library. Maybe it is the gps chip or the library.

@efiten
Copy link

efiten commented Apr 19, 2022

Is there already a solution, or workaround for this ?
With other programs, GPS can read out and show the date correctly.

73
Erwin

@stroobandt
Copy link

The TTGO T-Beam v1.1 appears to be using the NEO-M8N GPS chip instead of the NEO-6M.
This may be the reason for the faulty date indication.

versions

@xe2ad
Copy link

xe2ad commented Aug 4, 2022

Hi @iw9grl ,
I can't get any GPS info in my Tbeam, what GPS fix did you run and how did you do that?
Best regards,
-David, XE2AD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants