Re: List of time synchronization hardware and software

David L. Mills wrote:

Rob,

I can confirm that the Spectracom GPS and WWVB receivers, Arbiter GPS receiver, TrueTime NTS-200 GPS/NTP server, WWV/H audio driver and those systems with the NIST leapsecond file, either via ftp or Autokey, handled the lurch correctly. On the other hand, the EndRun CDMA/NTP server took about five minutes to lurch.

Dave

Rob van der Putten wrote:

Hi there


"Richard B. Gilbert" wrote:


It's not quite what you asked for but:

Publishers of Computer Time Synchronization Software
<http://tf.nist.gov/timefreq/general/softwarelist.htm>

and

Manufacturers of Time and Frequency Receivers
<http://tf.nist.gov/timefreq/general/receiverlist.htm>



Comments on which of these actually handled the leap second correctly would
be nice.


Regards,
Rob

Where can I get the leap second file by ftp? I've looked on the NIST web site and failed to find it. They display the leap second information but I don't see a link to where it's available for download. Getting it by autokey is not an option; I'm behind a NAT firewall/router.
.

Relevant Pages

  • Re: List of time synchronization hardware and software
    ... I can confirm that the Spectracom GPS and WWVB receivers, Arbiter GPS receiver, TrueTime NTS-200 GPS/NTP server, WWV/H audio driver and those systems with the NIST leapsecond file, either via ftp or Autokey, handled the lurch correctly. ...
    (comp.protocols.time.ntp)
  • Re: List of time synchronization hardware and software
    ... I can confirm that the Spectracom GPS and WWVB receivers, Arbiter GPS receiver, TrueTime NTS-200 GPS/NTP server, WWV/H audio driver and those systems with the NIST leapsecond file, either via ftp or Autokey, handled the lurch correctly. ... Publishers of Computer Time Synchronization Software ...
    (comp.protocols.time.ntp)
  • Re: ESA: First Galileo satellite on orbit
    ... > Bitstring, from the wonderful ... >>> Receivers have all the information they need to properly handle the ... >>> insertion of leap seconds. ... > But I didn't think the leap second had happened yet - isn't it inserted at ...
    (sci.geo.satellite-nav)