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

In rare cases time sent by GPS is not initially correct which leads to wrong filename and hard track rendering #294

Open
amandel opened this issue Mar 28, 2022 · 1 comment
Labels
bug Something isn't working gps

Comments

@amandel
Copy link
Member

amandel commented Mar 28, 2022

DEV: GPS: TIMEGPS set: 2022-03-12T10:54:21 -> 2022-03-26T10:54:21 0ms.
DEV: GPS: TIMEGPS set: 2022-03-20T12:23:52 -> 2022-03-27T12:23:52 0ms. (GPS Week)

Feels like we should xcheck the date received.

@amandel amandel added bug Something isn't working gps labels Mar 28, 2022
@gluap gluap changed the title In raw cases time sent by GPS is not initially correct which leads to wrong filename and hard track rendering In rare cases time sent by GPS is not initially correct which leads to wrong filename and hard track rendering Apr 4, 2022
@amandel
Copy link
Member Author

amandel commented Apr 17, 2022

amandel added a commit that referenced this issue Apr 17, 2022
…#294)

* Allow debugging of GPS vs location drift
- store gps timestamp in gps record
- log gps timestamp and cpu time every minute to make derivations visible
- read week number also from NAV-SOL message.
- report week changes via statistic message
- use GPS time directly for csv if available
- wait for more precise data till time is set (80 vs 20 ms)
- gps logging, log each message only once
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working gps
Projects
None yet
Development

No branches or pull requests

1 participant