© MOBATIME
77 / 84
800847.08
F
Technical data
Dimensions
19“ Rack, 1HE x 28TE (H x W x D [mm]) = 483 x 44 x 125
Weight
approx. 1.2 kg
Ambient temperature
0 to 60ºC, 10-90% relative humidity, without condensation
Operation
Serial int
erface (via RS 232) o
r Telnet/SSH (via LAN)
In addition, operation is also possible with SNMP.
Accuracy
GPS (DCF input) to NTP server:
typical < +/- 100 µs
GPS (DCF input) to DCF output:
typical < +/- 10 µs
NTP to internal time
typical < +/- 100 µs
Important:
NTP reception (DTS 4128 as client or as server to external clients) can be
influenced by the network traffic load and network devices (Hub, Switch,
Router, Firewall...). If many clients request simultaneously, the typical
accuracy may not be reached.
Time keeping (internal)
- Synchronized with GPS:
+/-10 µs to UTC
- Holdover (free run):
After at least 12 hours synchronization from the time source
< +/- 0.01 sec. / day (< 0.1ppm)
(measured over 24 h), at 20°C +/- 5°C.
< +/- 1 ms / day (< 0.01ppm)
(measured over 24 h), at constant temperature.
- After reboot without synchronization:
< +/- 0.25 sec. / day (< 2.5ppm)
(measured over 24 h), at 20°C +/- 5°C.
Redundant operation
- Master to slave (optical DTS link):
typical < +/- 1 µs
Time server
NTP V4
(fully V3 compatible), RFC 1305 (Port 123)
SNTP
(UDP), RFC 2030 (Port 123)
TIME
(TCP/UDP), RFC 868 (Port 37)
DAYTIME
(TCP/UDP), RFC 867 (Port 13)
Max. number of NTP and SNTP client requests: > 1500 requests / sec.
NTP Mode
Server, Peer, Broadcast, Multicast
NTP-slave clock lines:
1 line with up to 15 different time zone entries.
Communication through multicast:
-RFC 3376: Internet Group Management Protocol, Version 3
-RFC 1112: Host extensions for IP multicasting
-RFC 4601: Protocol Independent Multicast - Sparse Mode (PIM-SM)
-RFC 3973: Protocol Independent Multicast - Dense Mode (PIM-DM)
Time zones (see App. B) Up to 80 predefined, 20 programmable entries (PC Software Tool)
