[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[External] Re: Time precision in gps_fix_t

From: Burton, John
Subject: [External] Re: Time precision in gps_fix_t
Date: Wed, 22 Jan 2020 11:57:21 -0500

PPS is almost a requirement if you want high precision time keeping / time stamps.

The concept is to first synchronize the computer's system clock to GPS time. This is done very well by a combination of GPSD (talks to the GPS receiver), KPPS (kernel interrupt responding to the Pulse Per Second signal provided by many (most?) GPS receivers), and also CHRONYD which synchronizes the system clock to network or device (GPS) time. The PPS signal provides the precise instance when the time measurement is taken. This accounts for the latencies and delays you describe. For an in-depth description of why this is important and how it is done, see the GPSD documentation :


On Wed, Jan 22, 2020 at 11:43 AM Greg Troxel <address@hidden> wrote:
I think PPS is a different thing from what Marco might be asking about.

Many receivers now can provide fixes at faster than 1 Hz.  I have an
M8030 which is doing 2 Hz fixes (I have not tried to change this, but
it's configurable for a variety of 1-10 Hz rates depending on enabled
constellations).  Each fix of course has position and time, but after
being processed through gpsd the json output has lost the fractional
time (probably 0.500s), and every other fix has the same time.  I think
the question is about carrying a time-of-fix through the system without
losing precision.

There will be some latency from measurement at the fix time to
calculation in the chipset to reception  of UBX binary at the computer,
etc.  But I don't think that's a good reason to round.

I am guessing this is fairly easy to fix.


John Burton, Ph.D.
MTEQ, Inc.

10440 Furnace Rd., Suite 204            Office:   540-658-2720 x1407
Lorton, VA 22079-2630                      Mobile: 757-508-6208
address@hidden                            Fax:     540-288-2515


This communication, including any attachments, may contain Proprietary, Export Controlled, Legally Privileged or other Confidential Information. Any unauthorized review, printing, copying, transmission, dissemination, or use of the information is strictly prohibited. If you are not the intended recipient, please indicate to the sender that you have received this email in error, and delete the copy you received.
reply via email to

[Prev in Thread] Current Thread [Next in Thread]