In article <[EMAIL PROTECTED]>,
David Schwartz <[EMAIL PROTECTED]> wrote:
> An interesting question is how good a guaranteed relationship for the
>NMEA data is good enough. I would argue "90% of the time, the NMEA data will
>follow within 600mS of the corresponding PPS pulse" is good enough. However,
>you really do want something to be guaranteed by the manufacturer.
>Otherwise, it's "well, I hope it works, it seems to" with the NMEA data.
We've actually gone to great lengths in our code to "qualify" the NMEA
data when it comes in. We maintain a history of data until we feel
confident that the data is matching the PPS's and that all are in sync.
This way we can tell when the Garmin has a glitch and we can reject data
that is bad or comes too late.
Plus, as others have said, it's necessary to limit which NMEA strings are
sent from the GPS so you don't have data from one second constantly crossing
the next second's boundary.
================= GPS based time synchronization solutions =================
Patrick Klos Email: [EMAIL PROTECTED]
Klos Technologies, Inc. Web: http://www.timegeeks.com/
==================== http://www.loving-long-island.com/ ====================
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
