David J Taylor wrote:
Very expensive. Oh and it does /not/ provide NTP, just SNTP.
Probably their main market is the Windows systems world, where clients implement 'only' SNTP and usually no NTP. What they mention as advantages in their FAQ sounds as not-so-sound design when compared to the usual NTP implementation. It is best to have, besides your local radio receiver, some external peers to doublecheck the time. With GPS this may be more of a theoretical issue (although it could happen that your antenna is covered, damaged or needs to be temporarily removed for example for roof work). With other timestandard receivers (DCF for example) this is really needed, as the reception can sometimes fail (thunderstorms) and the error-checking in the protocol is suboptimal (sometimes it returns the wrong time due to multiple bit errors). A good NTP server smooths all those problems out. Probably a rewrite of the firmware could turn it into a much more useful unit. A full NTP implementation including the possibility to configure a couple of external sources should help a lot. Rob _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
