6 ms·
Why was it discontinued? Here's my guess. Any GPS receiver module (cheap) + any embedded board (cheap) = same thing. If you use a high powered commodity embedd
by contingencies 10y ago
Why was it discontinued? Here's my guess.
Any GPS receiver module (cheap) + any embedded board (cheap) = same thing. If you use a high powered commodity embedded board (eg. Raspberry Pi 3) then you can get other stuff done with it, too. Therefore, why have a standalone product? Low power consumption is about the only reason I can think of, but people running networks of servers that require a highly accurate local timing source are not generally people who care about minute variations in power consumption.
- cnvogel 10y agoA standalone product can have its advantages if it's designed with care to the specific task of timekeeping (which most other PCs or embedded boards aren't). This product (from looking at the schematics) has a true voltage controlled oscillator which allows you to get your local clock to agree consistently within few nanoseconds with the GPS timebase. (UPDATE: It has in Rev. 1.2, not in the latest :-( ). With a realtime OS (for reception of packets), or, much preferable, an Ethernet PHY that allows for hardware timestamping of incoming packets (something like http://www.ti.com/product/DP83640 http://www.ti.com/product/DP83640), you then could transfer this nanosecond precision to other machines on your network. Compared with the ~few microseconds you typically get with traditional NTP on a commodity PC or embedded board. The product linked to on Tindie, as far as I can see, does not have the latter, though.
- contingencies 10y agoIf you care that much about accuracy you should take a look at https://en.wikipedia.org/wiki/Precision_Time_Protocol https://en.wikipedia.org/wiki/Precision_Time_Protocol ... "IEEE 1588 is designed for local systems requiring accuracies beyond those attainable using NTP".