IEEE-1588 PTP Gran Maestro - DTS 4160 i

IEEE-1588 PTP Gran Maestro - DTS 4160 i

El DTS 4160 i es un dispositivo combinado de
distribución y sincronización horaria
con hasta 4 puertos de red
(IPv4/IPv6). Con su alta precisión y
concepto inteligente de funcionamiento redundante,
ofrece un alto grado de fiabilidad
y disponibilidad.

Tipo de oscilador:DTS 4160a.grandmaster i / Tipo A con Oscilador OCXO | DTS 4160c.grandmaster i / Tipo C con Oscilador de Rubidio
4 puertos LAN completamente separados (3x RJ45, 1x SFP):proporciona PTP en 3 puertos maestro o esclavo de 1 y 2 pasos, diferentes perfiles y dominios por puerto, multidifusión/unidifusión, IPv4/IPv6/Capa 2, proporciona NTP en 4 puertos (<10'000 peticiones/s en los 4 puertos combinados)
Salidas:4x E1 BNC (no balanceado), 2x salidas de pulso/frecuencia/10MHz, 1x IRIG-B / AFNOR, 2x salida serie, 1x salida de bucle de corriente DCF
Hora de alta precisión:Recepción horaria de GPS, GLONASS o Beidou, oscilador disciplinado GPS (GPSDO)
Redundancia:funcionamiento maestro-esclavo con conmutación automática en caso de error
Mostrar más
Configuración IPDHCP, DHCPv6, IP estática, Autoconfiguración
AlimentaciónSuministro 1 (conector de red estándar para 240 VCA), Suministros 2 y 3: 22..29 VCC
PrecisiónGPS a tiempo interno: típ. < +/- 30ns, Enlace redundante a tiempo interno: típ. < +/- 50ns, PTP a tiempo interno: yp. < +/- 50-100ns, DCF a tiempo interno: típ. < +/- 200ns (tras compensar el desfase del fix)
OperaciónMOBA-NMS, Telnet, SSH, SNMP (V2c/V3 get, put), RS 232 (terminal)
Mostrar más

Both, PTP and NTP provides time synchronization over a packet based network. But not both protocols are dedicated to the same application fields. It depends on the system’s needs, which of the protocol is preferred.

PTP is needed where a higher level of precision is required (e.g. Telecom, Power distribution, Air traffic control etc.) With PTP sub microsecond or even nanosecond accuracies are feasible, whereas NTP only reaches millisecond level. The key of PTP is hardware timestamping. Only if the timestamping happens close to the wire, it is possible to reach this high level of accuracy. The drawback of it is the need for dedicated hardware and an engineered network.

NTP is an old Internet protocol which is still widely used to distribute time (e.g. clock systems or IT Networks). NTP provides a simple way to synchronize all device over a regular network and even over internet. To ensure a reliable time in a local network, the best solution is to place an NTP server, which is connected to a GNSS Antenna, into the network. Whereas time is needed for clocks, access control systems and other such systems the accuracy of NTP is sufficient. The benefit of NTP is it’s robustness and it’s ability to run on a standard IT equipment.

If you need further information on this topic, please do not hesitate to contact us. We would be pleased to support you.

PTP is the «Precision Time Protocol», which is defined in IEEE 1588. In contrast to NTP, this is a network protocol, which is characterized by significantly higher accuracies (down to the nanosecond range) and is usually used in locally limited networks (e.g. measurement / control / regulation technology, automation technology, etc.).

 

In the foreground is not the absolutely correct time information, but rather the high-precision “clocking” of interconnected devices in such industrial or computer networks. In connection with the PTP network organization and clock types, one speaks initially of Grandmaster Clocks (best possible reference device) and Boundary Clocks (devices with master and slave function), whose role distribution is determined using the best Master Clock algorithm. On the other hand, clearly defined roles are assigned to the ordinary clocks (either as master or clients), so-called transparent clocks then only forward the PTP time stamp when corrected. The runtime correction is ensured using complex computing algorithms. So it is not the case that one procedure is to be replaced by the other: NTP and PTP have different functional focuses, which is why both will continue to have authorization in the future and can also be used in parallel in computer networks if necessary.