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

NeoGPS::time_t issue #147

Open
tvanderweide opened this issue Jan 14, 2021 · 1 comment
Open

NeoGPS::time_t issue #147

tvanderweide opened this issue Jan 14, 2021 · 1 comment

Comments

@tvanderweide
Copy link

tvanderweide commented Jan 14, 2021

I'm trying to use the time_t struct to hold a dateTime from a fix and print this at a later point in the code. It's working fine except there's no dateTime_cs field in time_t and I had to do a little work around. Could this be added or am I missing an easy way to access the sub-second GPS accuracy?

@R1DEN
Copy link

R1DEN commented May 23, 2021

I'm trying to use the time_t struct to hold a dateTime from a fix and print this at a later point in the code. It's working fine except there's no dateTime_cs field in time_t and I had to do a little work around. Could this be added or am I missing an easy way to access the sub-second GPS accuracy?

@tvanderweide
AFAIK it is only available after the module receives the GPS "master frame" which is only "sent" once every 12.5 minutes. It sets the "leap second" property and that enables it to be accurate. I also tried to find a workaround on how to set it in a force way (my device has internet connection and can get the leap seond data from there)

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

2 participants