The Net.Time clock has been designed to meet specific requirements of the electrical utility industry, regardless if the deployment is for substation timing, telecom timing or as a gateway between the two domains. Many different input reference types can be used and converted to many different output types. It is even possible to convert IRIG-B to PTP.
Not implementing new timing protocols yet? Net.Time protects your capital investment becuase it can be configured to provide traditional timing outputs such as IRIG-B and NTP using GNSS as the input reference. When the time comes to deploy new timing interfaces the options can be easily implemented by adding licenses to the unit. If your network evolves into using PTP as a backup timing source delivered through the telecom network, Net.Time is ready and easy to provision for this.
Timing redundancy has been designed into Net.Time when using backup timing references. If a higher tier reference becomes unavailable then Net.Time will switch to the next best reference source. For example, GNSS can be the primary reference and if a GNSS outage or anomaly occurs then Net.Time can switch to a secondary reference such as 1588v2.
An enhanced holdover mode can be implemented to improve time of day holdover performance when the primary reference is lost. A frequency reference is configured as a backup (such as SyncE, T1/E1, 1.544/2.048 MHz, 5/10 MHz) that is used to compensate for holdover drift. The base oscillator is an OCXO with a Rubidium oscillator option available.
Inputs: GNSS, 1588v2, IRIG-B, SyncE, T1/E1, 1.544/2.048 MHz, 5/10 MHz, 1 PPS, ToD
Outputs: 1588v2, NTP, IRIG-B, SyncE, T1/E1, 1.544/2.048 MHz, 5/10 MHz, 1 PPS, ToD
Parrallel Redundancy Protocol (PRP) is natively supported for PTP and NTP
PTP Power Profile and Telecom Profiles are supported along with other PTP profiles. It is possible to also convert between different PTP profiles, for example telecom profile in and power profile out.