Network Time Protocol

The Network Time Protocol, NTP, is how computers and devices on a network agree on the time. A device asks a time server for the current time, corrects its own clock, and repeats the request at intervals. SNTP is a simpler variant used by devices that need less accuracy.

In power systems, NTP is one of several outputs a time server provides, alongside PTP and IRIG-B. The manufacturer's time server datasheet gives NTP/SNTP accuracy of 10 milliseconds, against PTP accuracy of 0.2 microseconds, and states that PTP is preferred over NTP because NTP loses GNSS timing accuracy. That difference decides which protocol to use: NTP suits event logging and general coordination; it does not suit protection or measurement that needs sub-microsecond agreement.

This guide is a protocol explainer, not a product page. It does not recommend a public NTP server: public servers, free servers and hobbyist builds are outside the scope of a hardware time server manufacturer, and no public server is listed here. For a power system, the time source should be a local server fed by satellite signals, not a public internet server.

Before ordering a time server, confirm the satellite systems available at the site, the output protocols the devices need, and the delivery terms. Ask for the current datasheet to be confirmed in writing before ordering.

What to confirm before ordering

Before payment, confirm the model, the specification from the current datasheet, the quantity, the price, the lead time, and the delivery terms, in writing. Ask in your inquiry to confirm the payment terms, the trade terms, and the reply time you should expect, rather than assuming any of them. No price, minimum order or lead time figure is stated on this site.