[ntp:questions] Single GPS/PPS time source gets marked as a falseticker

E-Mail Sent to this address will be added to the BlackLists Null at BlackList.Anitech-Systems.invalid
Thu Jul 14 18:34:45 UTC 2011

On 7/14/2011 9:46 AM, Uwe Klein wrote:
> Rob wrote:
>> The native binary protocol usually has a SPECIFICATION
>>  about the time field in the messages (like: it is the
>>  current time at the moment the beginning of the message
>>  is leaving the receiver).  The NMEA protocol has a
>>  "time of fix", and that tells you nothing about what
>>  time it is now.
> $GPZDA ?
> imho binary protocols oftentimes add more problems than
> they solve.  more delay != more uncertainty

Some GPS chips, e.g. SiRF III (Garmin has used that in the past),
 only allow you to set the (dozen?) messages' update rates
 to a range (one every second to one every thirty seconds,
 not turn them off, so, you get a bunch of message you don't
 want / need every so often, and there appears to be nothing
 else you can do about it.

 However, on the same chip, in NMEA mode, you can turn the
  message off with a update rate of zero;

E-Mail Sent to this address <BlackList at Anitech-Systems.com>
  will be added to the BlackLists.

More information about the questions mailing list