3 ms·
This is a real dilemma when doing scientific data acquisition for years rather than short shots. NTP uses the UTC time standard but there are GPS time sources
by willis936 4y ago
This is a real dilemma when doing scientific data acquisition for years rather than short shots.
NTP uses the UTC time standard but there are GPS time sources that can distribute other time standards over NTP and PTP. What breaks when you do this? Is it a worthy tradeoff?
Note that this is a concern of coordinating timestamps generated by devices that support PTP and devices that only support NTP (as many slow datarate devices do).
- himinlomax 4y agoThis is a very poor design decision in retrospect, NTP should have always used TAI. But it's too late to change it. Unfortunately, not enough people know about this problem or even just about the existence of TAI.
- cesarb 4y ago> NTP should have always used TAI. But it's too late to change it. There's a draft for NTPv5 (https://datatracker.ietf.org/doc/draft-mlichvar-ntp-ntpv5/ https://datatracker.ietf.org/doc/draft-mlichvar-ntp-ntpv5/) which allows the use of TAI instead of UTC.
- willis936 4y agoI'm not sure how this would solve the problem in my lifetime. PLC manufacturers are not known for fast adoption. Why would they ever update a working NTP implementation?