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

bug in timestamp conversion #2

Open
windkh opened this issue Apr 29, 2017 · 2 comments
Open

bug in timestamp conversion #2

windkh opened this issue Apr 29, 2017 · 2 comments

Comments

@windkh
Copy link

windkh commented Apr 29, 2017

timestamp expects the time to have exactly 6 digits e.g. 112233 which makes
11 hours
22 minutes
33 seconds.

But gps receivers like u-blox send the time in the format containing milliseconds: 112233.44 which would be translated to
11 hours
22 minutes
44 seconds instead of 33 seconds
The functions should not take the last two digits as seconds asuming that the string is 6 digits long!

Please include milliseconds in your algorithm and check for both formats: 6 digits and 9 digits!

@fabdrol
Copy link
Member

fabdrol commented Jun 8, 2018

@windkh could you include a example sentence for us to test with?

@windkh
Copy link
Author

windkh commented Jun 10, 2018

@fabdrol
I changed the project and don‘t have the required hardware available. But you can simply modify an nmea sentence manually by adding a delimiter and two digits tonyour existing timestamp: e.g. append .12

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