Meinberg LANTIME M600and GPS PTP NTP Time Server User’s Manual M600

User Manual: Meinberg LANTIME M600andGPS PTP NTP Time Server User’s Manual Troubleshoot Meinberg LANTIME M600andGPS PTP NTP Time Server |

Open the PDF directly: View PDF .
Page Count: 146

Download
Open PDF In Browser	View PDF

MANUAL
LANTIME M600 GPS PTP
Network Time Server and
PTP Grandmaster Clock

27th October 2011
Meinberg Radio Clocks GmbH & Co. KG

Table of Contents
1 Impressum

1

2 Quick Start

2

3 Network Timeserver with GPS synchronized time base

4

4 The
4.1
4.2
4.3
4.4
4.5

Modular System LANTIME
Supported Network Services . . . . .
Additional Features . . . . . . . . .
User Interface . . . . . . . . . . . .
Options . . . . . . . . . . . . . . .
Why to use a Network Time Server?

.
.
.
.
.

5
6
6
6
7
7

5 Network Time Protocol (NTP)
5.1 NTP Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 NTP-Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8
8
8

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

6 Precision Time Protocol (PTP) / IEEE1588
6.1 General Information . . . . . . . . . . . . . . . .
6.2 Functionality in Master Systems . . . . . . . . .
6.3 Functionality in Slave Systems . . . . . . . . . .
6.4 PTPv2 IEEE 1588-2008 Conguration Guide . . .
6.4.1 General Options . . . . . . . . . . . . . .
6.4.2 Network Layer 2 or Layer 3 . . . . . . . .
6.4.3 Multicast or Unicast . . . . . . . . . . . .
6.4.4 Two-Step or One-Step . . . . . . . . . .
6.4.5 End-To-End (E2E) or Peer-To-Peer (P2P)
6.4.6 Mode Recommendations . . . . . . . . .
6.4.7 Message Rate Settings . . . . . . . . . .
6.4.8 ANNOUNCE Messages . . . . . . . . . .
6.4.9 SYNC/FOLLOWUP Messages . . . . . .
6.4.10 (P)DELAY_REQUEST Messages . . . .
6.4.11 HQ Filter . . . . . . . . . . . . . . . . .

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
Delay Measurements
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

10
10
11
11
12
12
12
12
13
13
13
13
14
14
14
15

7 GPS satellite controlled clock
16
7.1 GPS170 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.2 Time Zone and Daylight Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8 Mounting the GPS Antenna
17
8.1 Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.2 Antenna Short-Circuit Assembly with surge voltage protection . . . . . . . . . . . . . . . . . . . 18
8.3 Antenna Short-Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9 Booting the GPS receiver

20

10 Booting the Single Board Computer

21

11 Configuration User Interface
11.1 The menus in Detail . . . . . . . . . . .
11.2 Menu: Reference Time . . . . . . . . .
11.2.1 Description of the Gracal Menu
11.2.2 Menu Setup MRS . . . . . . . .
11.2.3 Menu IRIG Input Management .
11.2.4 Info GPS Receiver . . . . . . . .

0

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

22
22
24
24
24
26
27

11.3

11.4
11.5

11.6

11.7

11.2.5 GPS Receiver Position . . . . . . . . . . .
11.2.6 GPS Satellite Constellation . . . . . . . . .
11.2.7 GPS Status and Version . . . . . . . . . . .
11.2.8 Setup GPS Receiver Parameters . . . . . .
11.2.9 Init GPS Receiver . . . . . . . . . . . . . .
11.2.10 Init Receiver Position . . . . . . . . . . . .
11.2.11 Init Receiver Time . . . . . . . . . . . . . .
11.2.12 Initiate Cold Boot of GPS Receiver . . . . .
11.2.13 Initiate Warm Boot of GPS Receiver . . . .
11.2.14 Set Antenna Cable Length . . . . . . . . .
11.2.15 Set GPS Receiver Simulation Mode . . . .
11.2.16 Setup GPS Outputs . . . . . . . . . . . . .
11.2.17 Enable Outputs . . . . . . . . . . . . . . .
11.2.18 Setup Serial Outputs . . . . . . . . . . . .
11.2.19 Setup Time Zone . . . . . . . . . . . . . .
11.2.20 TIME CODE (IRIG) . . . . . . . . . . . . .
11.2.21 Synthesizer Frequency Output . . . . . . .
Menu Time Service . . . . . . . . . . . . . . . . .
11.3.1 Menu NTP Current State . . . . . . . . . .
11.3.2 Menu: NTP Conguration . . . . . . . . .
11.3.3 Menu: Stratum of local clock . . . . . . . .
11.3.4 Menu: PTP State / Setup PTPv1 (Option)
Menu: NTP Conguration . . . . . . . . . . . . .
11.4.1 Menu: External NTP Servers . . . . . . . .
11.4.2 Menu: Stratum of local clock . . . . . . . .
Programmable pulse (Option) . . . . . . . . . . . .
11.5.1 SETUP POUT X . . . . . . . . . . . . . .
11.5.2 Mode . . . . . . . . . . . . . . . . . . . .
11.5.3 Timer Mode . . . . . . . . . . . . . . . . .
11.5.4 Single Pulse . . . . . . . . . . . . . . . . .
11.5.5 Cyclic mode . . . . . . . . . . . . . . . . .
11.5.6 PPS, PPM, PPH Modes . . . . . . . . . .
Menu: Network . . . . . . . . . . . . . . . . . . .
11.6.1 Menu: Global Conguration . . . . . . . .
11.6.2 Menu: Setup Network Interfaces . . . . . .
11.6.3 Menu: Setup IPv4 LAN Parameter . . . . .
11.6.4 Menu: Setup IPv6 Parameter . . . . . . . .
11.6.5 Menu: Link Mode . . . . . . . . . . . . . .
11.6.6 Menu: Network Services . . . . . . . . . .
Menu: System . . . . . . . . . . . . . . . . . . . .
11.7.1 Menu: Set time zone . . . . . . . . . . . .
11.7.2 Menu: Restart NTP . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

12 The graphical user interfaces
13 The WEB Interface
13.1 Conguration: Main Menu . . . . . . . .
13.2 Conguration: Ethernet . . . . . . . . . .
13.2.1 SYSLOG Server . . . . . . . . . .
13.3 Network interface specic conguration .
13.3.1 IPv4 addresses and DHCP . . . .
13.3.2 IPv6 addresses and autoconf . . .
13.3.3 High Availability Bonding . . . . .
13.3.4 Additional Network Conguration
13.4 Conguration: Notication . . . . . . . .
13.4.1 Alarm events . . . . . . . . . . . .
13.4.2 E-mail messages . . . . . . . . . .
13.4.3 Windows Popup Messages . . . .
13.4.4 SNMP-TRAP messages . . . . . .
13.4.5 VP100/NET wall mount display .
13.4.6 User dened Alarm scripts . . . .

27
28
28
28
28
29
29
29
29
30
30
30
30
31
31
32
32
33
33
33
33
34
35
35
36
36
36
37
37
37
37
38
39
39
40
40
41
41
41
42
42
43

44
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

45
45
47
48
48
48
49
49
50
51
51
52
53
53
53
53

13.4.7 NTP Client Monitoring . . . . . . .
13.4.8 Alarm messages . . . . . . . . . . .
13.5 Conguration: Security . . . . . . . . . . .
13.5.1 Password . . . . . . . . . . . . . . .
13.5.2 HTTP Access Control . . . . . . . .
13.5.3 SSH Secure Shell Login . . . . . . .
13.5.4 Generate SSL Certicate for HTTPS
13.5.5 NTP keys and certicates . . . . . .
13.5.6 SNMP Parameter . . . . . . . . . .
13.6 Conguration: NTP . . . . . . . . . . . . .
13.6.1 NTP Authentication . . . . . . . . .
13.6.2 NTP AUTOKEY . . . . . . . . . .
13.7 Conguration: Local . . . . . . . . . . . . .
13.7.1 Administrative functions . . . . . .
13.7.2 User Management . . . . . . . . . .
13.7.3 Administrative Information . . . . .
13.7.4 Software Update . . . . . . . . . . .
13.7.5 Automatic conguration check . . .
13.7.6 Get Diagnostics Information . . . .
13.7.7 Receiver Information . . . . . . . .
13.7.8 Web interface language . . . . . . .
13.8 Conguration: Statistics . . . . . . . . . . .
13.8.1 Statistical Information . . . . . . . .
13.9 Conguration: Manual . . . . . . . . . . .
13.10Conguration: PTP . . . . . . . . . . . . .
13.10.1 PTPv2 - Global Conguration . . .
13.10.2 PTP Network Conguration . . . .
13.10.3 PTP State Files . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

53
54
55
56
56
56
57
58
58
59
61
62
65
65
66
67
68
69
69
70
70
71
71
73
74
76
77
78

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

79
80
82
84
86
87
87

15 SNMP Support
15.1 Conguration over SNMP . . . . . . . . . . . . . . . . . . . . . . .
15.1.1 Examples for the usage of the SNMP conguration features
15.1.2 Further conguration possibilities . . . . . . . . . . . . . . .
15.1.3 Send special timeserver commands with SNMP . . . . . . .
15.1.4 Conguration of the timeserver with SNMP: Reference . . .
15.2 SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2.1 SNMP Trap Reference . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

90
91
91
92
92
94
98
99

16 Attachment: Technical Information
16.1 Skilled/Service-Personnel only: Replacing the Lithium
16.2 Technical Specications M600/300 Multipac . . . . .
16.3 Safety instructions for building-in equipment . . . . .
16.3.1 CE-Label . . . . . . . . . . . . . . . . . . . .
16.4 Rear Panel Connectors . . . . . . . . . . . . . . . .
16.5 Connector Assignments . . . . . . . . . . . . . . . .
16.6 TERMINAL (Console) . . . . . . . . . . . . . . . . .
16.7 Error Relay . . . . . . . . . . . . . . . . . . . . . . .
16.7.1 Technical Specication . . . . . . . . . . . .
16.8 Technical Specications GPS receiver . . . . . . . . .
16.8.1 Oscillator specications . . . . . . . . . . . .
16.8.2 Technical Specications GPS Antenna . . . .
16.8.3 Signal Description GPS170 . . . . . . . . . .
16.8.4 Rear Connector Pin Assignments GPS170 . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

100
100
100
101
101
102
103
103
104
104
105
106
107
108
109

14 The
14.1
14.2
14.3
14.4

Command Line Interface
CLI Ethernet . . . . . . . . . . .
CLI Notication . . . . . . . . .
CLI Security . . . . . . . . . . .
CLI NTP Parameter . . . . . . .
14.4.1 CLI NTP Authentication
14.5 CLI Local . . . . . . . . . . . .

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

Battery
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

Page 0
16.9 Technical Specications LAN CPU . . . . . . . . . . .
16.9.1 Rear Connector Pin Assignments LAN CPU . .
16.9.2 VGA, Keyboard Connector Pin Assignments . .
16.10Technical Specications Power Supply . . . . . . . . .
16.11Time Code . . . . . . . . . . . . . . . . . . . . . . . .
16.11.1 Abstract of Time Code . . . . . . . . . . . . .
16.11.2 Principle of Operation . . . . . . . . . . . . . .
16.11.3 Block Diagram Time Code . . . . . . . . . . .
16.11.4 IRIG Standard Format . . . . . . . . . . . . . .
16.11.5 AFNOR Standard Format . . . . . . . . . . . .
16.11.6 Assignment of CF Segment in IEEE1344 Code .
16.11.7 Generated Time Codes . . . . . . . . . . . . .
16.11.8 Selection of Generated Time Code . . . . . . .
16.11.9 Outputs . . . . . . . . . . . . . . . . . . . . .
16.11.10Technical Data . . . . . . . . . . . . . . . . .
16.12Time Strings . . . . . . . . . . . . . . . . . . . . . . .
16.12.1 Format of the Meinberg Standard Time String .
16.12.2 Format of the Meinberg Capture String . . . .
16.12.3 Format of the SAT Time String . . . . . . . .
16.12.4 Format of the Uni Erlangen String (NTP) . . .
16.12.5 Format of the NMEA 0183 String (RMC) . . .
16.12.6 Format of the NMEA 0183 String (GGA) . . .
16.12.7 Format of the ABB SPA Time String . . . . .
16.12.8 Format of the Computime Time String . . . . .
16.12.9 Format of the RACAL standard Time String . .
16.12.10Format of the SYSPLEX-1 Time String . . . .
16.13Manual VP100/NET Display conguration . . . . . . .
16.14Global Conguration File . . . . . . . . . . . . . . . .
16.15Global Option File . . . . . . . . . . . . . . . . . . . .
16.16Third party software . . . . . . . . . . . . . . . . . . .
16.16.1 Operating System GNU/Linux . . . . . . . . .
16.16.2 Samba . . . . . . . . . . . . . . . . . . . . . .
16.16.3 Network Time Protocol Version 4 (NTP) . . .
16.16.4 mini_httpd . . . . . . . . . . . . . . . . . . .
16.16.5 GNU General Public License (GPL) . . . . . . .
16.17Reference . . . . . . . . . . . . . . . . . . . . . . . .

0

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

Date: 27th October 2011

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

110
111
111
112
112
112
112
113
114
115
116
117
117
118
118
119
119
120
121
122
124
125
126
127
128
129
130
131
133
133
133
133
133
134
134
139

LANTIME M600 GPS PTP

Page 1

1 Impressum
Meinberg Radio Clocks GmbH & Co. KG

Lange Wand 9, 31812 Bad Pyrmont - Germany
Phone: + 49 (0) 52 81 / 93 09 - 0
Fax:
+ 49 (0) 52 81 / 93 09 - 30
Internet: http://www.meinberg.de
Mail:
info@meinberg.de
Date:

2010-09-16

LANTIME M600 GPS PTP

Date: 27th October 2011

1

Page 2

2 Quick Start

2 Quick Start
When booting the system the following message will be displayed while dots will be counted up in the lower line.
Approximately one minute after power up display will change to the following screen to wait for OCXO HQ
oscillator warmed up:

MEINBERG LANTIME
is booting... please wait...
.......

Main Menu will be displayed with some important status informations after booting has nished:

12:00:00

UTC
Tue, 01.01.2008

F1

NTP: Offs. 1ms
Stratum: 1
MRS: sync to GPS
XTL:SYNC SVs:9/10
PTP: ok PTP_SLAVE
GM:00:00:00:00:00:00
Press F1 for help or F2 for setup overview

The internal reference clock (HQ OCXO) is either controlled by an installed GPS receiver or by external time
sources (depending on Options like IRIG in or PPS in). The priorities for this regulation can be dened in the
settings. Press the following buttons to set up the MRS mode: i,g,g,g

MRS Status
-> Setup Input Priorities  Satellite Constellation Network Interfaces  DHCP:disable 

->

->

->

Reference Time
Time Service
Network
System
Reference Time
Time Service
Network
System
Reference Time
Time Service
Network
System
Reference Time
Time Service
Network
System

<-

-> Info GPS Receiver
Setup GPS Receiver
Setup Outputs

-> NTP Current State
external NTP servers
Stratum of local clock
PTP IEEE1588

<-

<-

-> Global Configuration
Network Interfaces
Network Services

<-

<-

<-

-> Set time zone


Reference Time
Time Service
Network
System

<-

-> Info GPS Receiver
Setup GPS Receiver
Setup Outputs

<-

To enter the following sub menus press the OK or right arrow button.

11.2.1 Description of the Grafical Menu
11.2.2 Menu Setup MRS
-> Reference Time
Time Service
Network
System

OK

<-

-> MRS Management
Info GPS Receiver
Setup GPS Receiver
Setup Outputs
->
OK

<-

MRS Status and Setup  MRS Status

OK

F1

Numerical Status
Graphical Status

<-

MRS Status
1.GPS
2.PPS
3.FRQ
4.NTP
5.PTP

OK

is
is
no
is
is

F1

available
available
signal
available
available

:
:
:
:
:

-50.0us
-50.0ns
n/a
- 5.0ns
-50.0ns

With the OK and arrow buttons you can select an overview of the current status of the MRS. All possible reference
clocks will be shown with the number of priority, the name of the reference clock and the current oset to the internal time reference (OCXO). The current master will be marked with a "*" behind the name of the reference clock.
In the next menu ("Setup Input Priorities") the user can dene in which order the references will be used to
control the internal oscillator. The reference clock with the highest priority will always be used if it is available.

MRS Status
-> Setup Input Priorities  Setup Fixed Offsets
 Setup Precisions
<-

LANTIME M600 GPS PTP

F1

OK

Set Precision of Refclocks [ns]
GPS:
PPS:
TCR:
NTP:
PTP:
FRQ:

Date: 27th October 2011

25

Page 26

11 Conguration User Interface

Example:

The external PPS with an precision of 100ns is the current master. If this master is no longer available it will
switch to the next reference source of the priority order  in this case the IRIG input with an precision of 10us.
With the formula ((10000ns/100ns)*11.4) we get hold over time of 19min. The online display of the MRS status
will show the remaining time and the calculated time. The hold over time will be recalculated if the status of the
reference clocks will change.

-> Numerical Status
Graphical Status

MRS Status

 IRIG Input Management <-

-> IRIG Receiver State
setup IRIG Receiver

<-

OK

Bit
Bit
Bit
Bit
Bit
Bit
Bit
Bit

7:
6:
5:
4:
3:
2:
1:
0:

Invalid UTC parameter
TCAP exceeded, jitter out of range
Lock on
Telegram error
Data available
Invalid sysconf
Pulses enabled
Warmed up

-> IRIG Receiver State
setup IRIG Receiver

 Setup IRIG Receiver

 GPS Receiver Position  Satellite Constellation  GPS Status & Version
<-

Reference Clock Information
MRS State: SYNC
GPS170 v.1.20
OCXO HQ
S/N: 0290100000680

11.2.5 GPS Receiver Position
This menu shows the current receiver position. The OK key lets the user select one of three formats. The
default format is geographic latitude, longitude and altitude with latitude and longitude displayed in degrees,
minutes and seconds. The next format is geographic too, with latitude and longitude displayed in degrees with
fractions of degrees. The third format displays the receiver position in earth centred, earth xed coordinates
(ECEF coordinates).

LANTIME M600 GPS PTP

Date: 27th October 2011

27

Page 28

11 Conguration User Interface
GPS Receiver Position
LAT: 51.9828
51°58’58” N
LON: 9.2258
09°13’32” E
ALT: 176 m

-> GPS Receiver Position  Satellite Constellation  GPS Status & Version
<-

The next line will reect the version number of the GPS170 and the oscillator type. In the bottom line the serial
number of the GPS170 will be shown.

11.2.8 Setup GPS Receiver Parameters
->

-> Init
Init
Init
Init

Init GPS Receiver
 Setup Antenna Length
Setup Simulation Mode

Init GPS Receiver
Setup Antenna Length
-> Setup Simulation Mode

Receiver Position 

28

Init GPS Receiver
 Init
Init
Init
Init

Date: 27th October 2011

Receiver Position  Init
Init
Init
Init

Receiver Position  Init
Init
Init

Receiver Position
Receiver Time
 Init
Init

Initiate COLD Boot
of GPS Receiver

Receiver Position
Receiver Time
COLD Boot
 Init

Initiate WARM Boot
of GPS Receiver

Receiver Position
Receiver Time
COLD Boot
WARM Boot
<-

LANTIME M600 GPS PTP

Press F2 to confirm

Date: 27th October 2011

29

Page 30

11 Conguration User Interface

11.2.14 Set Antenna Cable Length
This menu asks the user to enter the length of the antenna cable. The received time frame is delayed by approx.
5 ns per meter antenna cable. The receiver is able to compensate this delay if the exact cable length is given.
The default value is 20 m. The maximum value that can be entered is 500 m (only with low loss cable).

Edit and Set
Antenna Cable Length
of GPS receiver
Length: 020 m

Init GPS Receiver
-> Setup Antenna Length  Setup Simulation Mode <-

Simulation Mode: disabled

11.2.16 Setup GPS Outputs
->

Enable Outputs


Enable Outputs
Synthesizer: always
Pulses: always
Serial Outputs: always

<-

Enable Outputs
-> Setup Serial Outputs 

Enable Outputs
Setup Serial Outputs
-> Setup IRIG Output
 Code: AFNOR NFS-87500  Setup Pulse Outputs <-

-> Setup prg. pulse outputs  Enable Outputs


Date: 27th October 2011

<-

LANTIME M600 GPS PTP

11.2 Menu: Reference Time

Page 31

11.2.18 Setup Serial Outputs
->

Enable Outputs
-> Setup Serial Outputs 

Time Zone Parameters
of display
-> Daylight Saving OFF
Daylight Saving ON

Setup COM 0
Setup COM 1
Setup Time Zone <-

<-

Daylight Saving OFF
>TZ Name:MEZ <
Offs.:+01:00h
Day of Week: Sun
Date:25.10.**** Time:03:00:00

Beginning and ending of daylight saving may either be dened by exact dates for a single year or using an algorithm which allows the receiver to re-compute the eective dates year by year. The gures below show how to
enter parameters in both cases. If the number of the year is displayed as wildcards (
*
), a day-of-week must be
specied. Then, starting from the congured date, daylight saving changes the rst day which matches the congured day-of-week. In the gure below October 25th, 2008 is a Saturday, so the next Sunday is October 26th, 2008.
All changeover rules for the daylight saving like "the rst/the second/the second to last/the last Sunday/Monday
etc. in the x-th month," can be described by the used format "rst specied day-of-week after a dened date".
If the number of the year is not displayed as wildcards the complete date exactly determines the day daylight
saving has to change (October 26th, 2008 in the gures below), so the day-of-week does not need to be specied
and therefore is displayed as wildcards.

Time Zone Daylight Saving OFF
TZ Name: MEZ
Offs.UTC:+01:00h
Day of Week: Sun
Date:25.10.**** Time:03:00:00

Time Zone Daylight Saving OFF
TZ Name: MEZ
Offs.UTC:+01:00h
Day of Week: ***
Date:26.10.2008 Time:03:00:00

If no changeover in daylight saving is wanted, identical dates and times must be entered in both of the submenus
(DAYLIGHT SAV ON/OFF). After this a restart should be done.

11.2.20 TIME CODE (IRIG)
This menu lets the user select the Timecodes to be generated by GPS-TC. Most IRIG-Codes do not carry any
time zone information, hence UTC is selected for output by default. If desired, the clocks local time can be output
by selecting "TIME: LOCAL".

Enable Outputs
Setup Serial Outputs
-> Setup IRIG Output
Setup Pulse Outputs

<-

Time Code (IRIG,AFNOR,IEEE)
Output Settings
> Code: B002+B122
<
TIME: UTC

Refer to chapter Timecode for details.

11.2.21 Synthesizer Frequency Output
Synthesizer
Frequency Output
Frequence: 0 Hz
Phase: 0 el

This setup menu lets the user edit the frequency and phase to be generated by the on-board synthesizer. Frequencies from 1/8 Hz up to 10 MHz can be entered using four digits and a range. The range can be selected if
the UP or DOWN key is pressed while the cursor is positioned on the frequency
s units string. If the least
signicant range has been selected valid fractions of the frequency are .0, .1 (displayed as 1/8), .3 (displayed

32

Date: 27th October 2011

LANTIME M600 GPS PTP

11.3 Menu Time Service

Page 33

as 1/3), .5 and .6 (displayed as 2/3). Selection of 1/3 or 2/3 means real 1/3 or 2/3 Hz, not 0.33 or 0.66. If
frequency is set to 0 the synthesizer is disabled.
The last line of the display lets the user enter the phase of the generated frequency from -360◦ to +360◦
with a resolution of 0.1◦ . Increasing the phase lets the signal come out later. Phase aects frequencies less than
10.00 kHz only, if a higher frequency is selected a message "(phase ignored)" informs the user that the phase
value is ignored.

11.3 Menu Time Service
11.3.1 Menu NTP Current State
A table with current information of the reference clocks will be shown in this menu.
NTP Query Output
Id
0
*1
o2
3

St
12
00
00
01

wh
02
08
11
15

reach
377
377
377
377

delay
0.000
0.000
0.000
0.436

offset
0.000
0.011
0.011
0.043

jitter
0.000
0.007
0.007
0.038

11.3.2 Menu: NTP Configuration
The default conguration of the timeserver consists of a local clock, which represents the hardware clock of your
LANTIME system and the GPS reference clock. The local clock is only chosen as the NTP time reference after
the GPS clock lost its synchronisation. The stratum level of this local clock is set to 12, this ensures that clients
recognise the switchover to the local clock and are able to eventually take further actions. The local clock can
be disabled if the timeserver should not answer anymore when the reference clock is out of order. Four additional
external NTP servers can be set up in this menu to provide a high grade of redundancy for the internal reference
clock.

-> external
external
external
external

NTP
NTP
NTP
NTP

server
server
server
server

1 <2
3
4

Edit NTP Configuration
external NTP servers
IPv4 address of external NTP
Server1:
192.168.10.12

OK

11.3.3 Menu: Stratum of local clock
The local clock is only chosen as the NTP time reference after the GPS clock lost its synchronization. The
stratum level of this local clock is set to 12, this ensures that clients recognize the switchover to the local clock
and are able to eventually take further actions. The local clock can be disabled if the timeserver should not
answer anymore when the reference clock is out of order. The eld Stratum of local clock is used to change
the stratum level of the local clock (see above), default is 12.

NTP Configuration
Stratum of local clock
new stratum value from 0 to 15
stratum: 12

LANTIME M600 GPS PTP

Date: 27th October 2011

33

Page 34

11 Conguration User Interface

11.3.4 Menu: PTP State / Setup PTPv1 (Option)
The Precision Time Protocol (PTP) IEEE1588 is an optional network card with a special hardware time stamping
unit to realize the high precision timing in the range of nano seconds via ethernet network. This menu reect the
main parameters:

IEEE 1588 PTP State
Get PKTs: ok Stratum: 1 OCX:*
State: PTP_MASTER
PFM:
GM UUID: 00:00:00:00:00:00

The Get PKTs: signals if any hardware timestamping with PTP packets is active or not. If the state no will be
displayed please check the following conditions:

• Is an ethernet cable connected to the PTP port and the LINK is up?
• Is the PTP port congured with a valid IP address and netmask?
• Is the Default Gateway congured?
• Check if Multicast enabled your network environment (Switch or Router).
• Are there any other PTP Master in your network?
The stratum value reects the PTP stratum in a range from 1 to 255. The State: will show the current PTP
state PTP_MASTER, PTP_SLAVE, PTP_LISTENING and PTP_PASSIVE. The GM UUID is the MAC address
of the current PTP Grandmaster in your network.

Menü Setup PTP

PTP Mode: PTP_MASTER
Prefered Master Flag: disabled
Sync Intervall[2^x]: 1
PTP Sub Domain: _DFLT

The PTP Mode can be switched between PTP_MASTER and PTP_SLAVE. The Preferred Master Flag
decides if this master will be the rst in the Best Master Algorithm which choose the grandmaster in a PTP
network  this ag can be enabled or disabled. The Sync Interval determine how fast the PTP packets will be
send by the Grandmaster and will be congured as a value of power of 2.
The PTP Sub Domain will determine which Multicast address will be used by the PTP Grandmaster. The
PTP IEEE1588 supports 4 Multicast addresses: _DFLT, _ALT1, _ALT2, _ALT3.

34

Date: 27th October 2011

LANTIME M600 GPS PTP

11.4 Menu: NTP Conguration

Page 35

11.4 Menu: NTP Configuration
The NTP conguration page is used to set up the additional NTP parameters needed for a more specic conguration of the NTP subsystem.

->

-> NTP Current State  NTP Current State  external
external
external
external

NTP Current State
-> external NTP servers  Stratum of local clock <-

The rst page will reect the current state of the NTP. The line Oset PPS: 1 ms shows the current oset
between the system time and the reference time (GLN).
To enter the following sub menu press the OK or right arrow button:

NTP Configuration
external NTP servers


11.4.1 Menu: External NTP Servers
The default conguration of the timeserver consists of a local clock, which represents the hardware clock of your
LANTIME system and the GPS reference clock. The local clock is only chosen as the NTP time reference after
the GPS clock lost its synchronisation. The stratum level of this local clock is set to 12, this ensures that clients
recognise the switchover to the local clock and are able to eventually take further actions. The local clock can be
disabled if the timeserver should not answer anymore when the reference clock is out of order. Seven additional
external NTP servers can be set up to provide a high grade of redundancy for the internal reference clock.

NTP Current State
external NTP servers
-> Stratum of local clock <-

LANTIME M600 GPS PTP

Date: 27th October 2011

Edit NTP Configuration
Stratum of local clock
new stratum value from 0 to 15
stratum: 12

35

Page 36

11 Conguration User Interface

11.4.2 Menu: Stratum of local clock
The local clock is only chosen as the NTP time reference after the GPS clock lost its synchronization. The
stratum level of this local clock is set to 12, this ensures that clients recognize the switchover to the local clock
and are able to eventually take further actions. The local clock can be disabled if the timeserver should not
answer anymore when the reference clock is out of order. The eld Stratum of local clock is used to change
the stratum level of the local clock (see above), default is 12.

NTP Configuration
Stratum of local clock
new stratum value from 0 to 15
stratum: 12

11.5 Programmable pulse (Option)
At the male connector type VG64 there are optionally three programmable TTL outputs (Prog Pulse 1-3), which
are arbitrarily programmable.

11.5.1 SETUP POUT X
This menu is used for conguration of the pulse outputs.
There are three pulse outputs available (POUT 1-3).

Programmable
Output 1:
Output 2:
Output 3:

Pulses Output
TIMER
CYCLIC
PASSIV

With the arrow key right or OK Button the parameters of each programmable pulse output can be set:

Programmable Pulses Output
--->
Output 1
<--Output 2
Output 3

Each programmable pulse output has its own Mode to be set. With the arrow keys up and down the mode can
be selected:

---> POUT1
POUT1
POUT1
POUT1
POUT1
POUT1
POUT1

36

Mode
Mode
Mode
Mode
Mode
Mode
Mode

PASSIV <--TIMER
SINGLE
CYCLIC
PPS
PPM
PPH

Date: 27th October 2011

LANTIME M600 GPS PTP

11.5 Programmable pulse (Option)

Page 37

11.5.2 Mode
This eld selects the mode of operation of an output. Possible modes are PASSIV, TIMER, SINGLE, CYCLIC,
PPS, PPM and PPH.

11.5.3 Timer Mode
POUT1 TIMER1
output activ: low
Time ON: 10:50:00
Time OFF: 11:00:00
POUT1 TIMER2
output activ: low
Time ON: 13:00:00
Time OFF: 14:00:00
POUT1 TIMER3
output activ: low
Time ON: 23:45:00
Time OFF: 09:30:00

If Timer mode is selected, a window as shown above is displayed. The switching plan is assigned per day. Three
turn-on and turn-o times are programmable for each output. If a switching time has to be congured, only the
turn-on and turn-o time must be programmed. Thus the example shows switching times from 10:50 to 11:00,
13:00 to 14:00 and 23:45 to 09:30. A turn-o time earlier than the turn-o time would cause the output to be
enabled over midnight. For example a program 'ON Time' 10:45:00, 'OFF Time' 9:30:00 would cause an active
ouput from 10:45 to 9:30 (the next day!). If one or more of the three switching times are unused just enter the
same time into the elds 'ON Time' and 'OFF Time'. In this case the switch time does not aect the output.

11.5.4 Single Pulse
Selecting Single Pulse generates a single pulse of dened length once per day.

POUT1 SINGLE:
output activ: low
Time: 12:00:00
Length: 00.10 sec

You can enter the time when the pulse is generated in the eld 'Time'. The value in eld 'Length' determines
the pulse duration. A pulse duration from 10 msec to 10 sec in steps of 10 msec can be selected.
The example shows a single pulse at 12:00 every day with a duration of 100 ms.

11.5.5 Cyclic mode
Cyclic mode is used for generating periodically repeated pulses.

POUT1 CYCLIC:
output activ: low
Time: 00:00:02
Length: 00.10 sec

The value in eld 'Time' determines the time between two consecutive pulses (2 sec in example above). This cycle
time must be entered as hours, minutes and seconds. The pulse train is synchronized at 0:00 o'clock local time,
so the rst pulse of a day always occurs at midnight. A cycle time of 2 seconds for example, would cause pulses

LANTIME M600 GPS PTP

Date: 27th October 2011

37

Page 38

11 Conguration User Interface

at 0:00:00, 0:00:02, 0:00:04 etc. Basically it is possible to enter any cycle time between 0 and 24 hours, however
only a cycle times that causes a constant distance between all consecutive pulses make sense. For example a cycle
time of 1 hour 45 minutes would generate a pulse every 6300 seconds (starting from 0 o'clock). The duration
between the last pulse of a day and the rst pulse of the next day (0:00:00 o'clock) would only be 4500 sec.

11.5.6 PPS, PPM, PPH Modes
POUT1 Pulse Per Sec (PPS):
output activ: low
Length: 00.10 sec
POUT1 Pulse Per Min (PPM):
output activ: low
Length: 00.10 sec
POUT1 Pulse Per Hour (PPH):
output activ: low
Length: 00.10 sec

These modes generate pulses of dened length once per second, once per minute or one per hour. 'Time' determines the pulse duration (10 msec...10 sec). The respective output remains in active state, when selecting a
pulse duration longer than 990ms in pulse per sec mode.

38

Date: 27th October 2011

LANTIME M600 GPS PTP

11.6 Menu: Network

Page 39

11.6 Menu: Network
Reference Time
Time Service
-> Network
System

OK

<-

-> Global Configuration  Hostname  Network Interfaces
 IPv4 LAN Parameter  Network Services
<-

SSH:on
TELN:on
SNMP:off
FTP:on

OK

IPv6:on
HTTP:on
HTTPS:on
NetB:off

In this submenu the network conguration parameters related to the network interfaces can be changed. The
submenus can be selected with the arrow keys and the OK button:
As soon as an IP address is congured, additional network conguration can be done via network connection
with TELNET, SSH or the WEB interface. Ask your network administrator for network specic parameters.
Every change of the network parameters will restart the NTP. All network specic parameters will be saved on the
ash disk (/mnt/ash/cong/global_conguration) and will be reloaded after reboot. It is highly recommended
not to edit this le manually but to congure the parameters via the several conguration interfaces (HTTP, CLI
or SNMP). If this le is not present, an empty le will be created. See Appendix for the default settings of this
le.

11.6.1 Menu: Global Configuration
-> Global Configuration  Hostname
 IPv4 LAN Parameter
IPv6 LAN Parameter
Link Mode

Global Configuration
-> Network Interfaces
 ETH0  DHCP:
ADDRESS:
NETMASK:
DEF.GATEWAY:

enabled <172.16.3.64
255.255.255.0

There is a separate conguration submenu for every physical network interface. If there is no DHCP client mode
activated a static IP address for each interface can be entered. IPv4 addresses are built of 32 bits which are
grouped in four octets, each containing 8 bits. You can specify an IP address in this mask by entering four
decimal numbers, separated by a point . .
Example: 192.168.10.2

Additionally you can specify the IPv4 netmask and your default gateway address.
Please contact your network administrator, who can provide you with the settings suitable for your specic network.
If there is a DHCP (Dynamic Host Conguration Protocol) server available in your network, the LANTIME
system can obtain its IPv4 settings automatically from this server. If you want to use this feature (again, you
should ask your network administrator whether this is applicable in your network), you can change the DHCP
Client parameter to ENABLED. Using DHCP is the default factory setting.

40

Date: 27th October 2011

LANTIME M600 GPS PTP

11.6 Menu: Network

Page 41

If the DHCP client has been activated, the automatically obtained parameters are shown in the appropriate
elds (IPv4 address, netmask, gateway).

11.6.4 Menu: Setup IPv6 Parameter
->

->

Link Local Address
 Link Global Address 1
Link Global Address 2
Link Local Address
Autoconfiguration Flag
Link Global Address 1
-> Link Global Address 2

Edit and Set
IPv6 Link Global Address 1 ETH0
0201::feff:8032

<-

Edit and Set
IPv6 Link Global Address 2 ETH0
0201::feff:8032

<-

The IPV6 parameter can be congured via the front panel display for the rst ethernet port (ETH0) only. Additionally IPV6 conguration can be done via network connection with TELNET, SSH or the WEB interface.
You can specify up to three IPv6 addresses for your LANTIME timeserver. Additionally you can switch o the IPv6
autoconf feature. IPv6 addresses are 128 bits in length and written as a chain of 16 bit numbers in hexadecimal
notation, separated with colons. A sequence of zeros can be substituted with :: once.
If you enabled the IPv6 protocol, the LANTIME always gets a link local address in the format fe80:: . . . .,
which is based upon the MAC address of the interface. If a IPv6 router advertiser is available in your network and
if you enabled the IPv6 autoconf feature, your LANTIME will be set up with up to three link global addresses
automatically.

11.6.5 Menu: Link Mode
IPv4 LAN Parameter
IPv6 LAN Parameter
-> Link Mode
<-

Global Configuration
-> Network Interfaces
 System

-> Set time zone
 Daylight Saving OFF  Set time zone
Setup Outputs) .
This menu lets the user enter the names of the local time zone with daylight saving disabled and enabled,
together with the zones
 time osets from UTC. These parameters are used to convert UTC to local time, e.g.
MEZ = UTC + 1h and MESZ = UTC + 2h for central Europe. The range of date daylight saving comes in
eect can be entered using the next two pages of the setup menu.
Beginning and ending of daylight saving may either be dened by exact dates for a single year or using an
algorithm which allows the receiver to re-compute the eective dates year by year. The gures below show how to
enter parameters in both cases. If the number of the year is displayed as wildcards (
*
), a day-of-week must be
specied. Then, starting from the congured date, daylight saving changes the rst day which matches the congured day-of-week. In the gure below October 25th, 2008 is a Saturday, so the next Sunday is October 26th, 2008.
All changeover rules for the daylight saving like "the rst/the second/the second to last/the last Sunday/Monday etc. in the x-th month," can be described by the used format "rst specied day-of-week after a dened date".
If the number of the year is not displayed as wildcards the complete date exactly determines the day daylight
saving has to change (October 26th, 2008 in the gures below), so the day-of-week does not need to be specied
and therefore is displayed as wildcards.

Time Zone Daylight Saving OFF
TZ Name: MEZ
Offs.UTC:+01:00h
Day of Week: Sun
Date:25.10.**** Time:03:00:00

42

Time Zone Daylight Saving OFF
TZ Name: MEZ
Offs.UTC:+01:00h
Day of Week: ***
Date:26.10.2008 Time:03:00:00

Date: 27th October 2011

LANTIME M600 GPS PTP

11.7 Menu: System

Page 43

If no changeover in daylight saving is wanted, identical dates and times must be entered in both of the submenus
(DAYLIGHT SAV ON/OFF).

11.7.2 Menu: Restart NTP
If the time of the reference clock has changed (e.g. while testing with dierent times) the system time has to bet
set with the time of the reference clock and the NTP has to be restarted.

Set Time Zone
-> Restart NTP
local)
...mbgLtNtp.mbgLtNtpCurrentStateVal.0 = 1
...mbgLtNtp.mbgLtNtpStratum.0 = 12
...mbgLtNtp.mbgLtNtpActiveRefclockId.0 = 1
...mbgLtNtp.mbgLtNtpActiveRefclockName.0 = LOCAL(0)
...mbgLtNtp.mbgLtNtpActiveRefclockOset.0 = 0.000 ms
...mbgLtNtp.mbgLtNtpActiveRefclockOsetVal.0 = 0
...mbgLtNtp.mbgLtNtpNumberOfRefclocks.0 = 3
...mbgLtNtp.mbgLtNtpAuthKeyId.0 = 0
...mbgLtNtp.mbgLtNtpVersion.0 = 4.2.0@1.1161-r Fri Mar 5 15:58:56 CET 2004 (3)
...mbgLtRefclock.mbgLtRefClockType.0 = Clock Type: GPS167 1HE
...mbgLtRefclock.mbgLtRefClockTypeVal.0 = 1
...mbgLtRefclock.mbgLtRefClockMode.0 = Clock Mode: Normal Operation
...mbgLtRefclock.mbgLtRefClockModeVal.0 = 1

90

Date: 27th October 2011

LANTIME M600 GPS PTP

15.1 Conguration over SNMP

Page 91

...mbgLtRefclock.mbgLtRefGpsState.0 = GPS State: sync
...mbgLtRefclock.mbgLtRefGpsStateVal.0 = 1
...mbgLtRefclock.mbgLtRefGpsPosition.0 = GPS Position: 51.9834◦ 9.2259◦ 181m
...mbgLtRefclock.mbgLtRefGpsSatellites.0 = GPS Satellites: 06/06
...mbgLtRefclock.mbgLtRefGpsSatellitesGood.0 = 6
...mbgLtRefclock.mbgLtRefGpsSatellitesInView.0 = 6
...mbgLtRefclock.mbgLtRefPzfState.0 = PZF State: N/A
...mbgLtRefclock.mbgLtRefPzfStateVal.0 = 0
...mbgLtRefclock.mbgLtRefPzfKorrelation.0 = 0
...mbgLtRefclock.mbgLtRefPzfField.0 = 0
Please note that you only see the object names (like mbgLtRefclock.mbgLtRefPzfField) if you installed the
Meinberg MIB les on your client workstation rst (please see the web interface or CLI setup tool chapters to
nd out how to do this).
By using the standard MIB, no NTP get requests are allowed. Only the standard system and network parameters can be accessed (e.g. using the NET-SNMP command snmpget).
Only by using the Meinberg MIB the change of conguration parameters is possible (the command snmpset is
used to alter a variable, for example).

15.1 Configuration over SNMP
The LANTIME timeserver can be congured via several user interfaces. Besides the possibility to setup its parameters with the web interface (HTTP and/or HTTPS) and the direct shell access via Telnet or SSH, a SNMP
based conguration interface is available.
In order to use the SNMP conguration features of the timeserver, you need to full the following requirements (the system has to be reachable over the network, of course):
a)
b)
c)

SNMP has to be activated in the timeservers setup by setting up a RWCOMMUNITY
In the SNMP conguration the read-write-access needs to be activated
The timeserver-specic MIB les must be present on the clients,
they have to be included in the SNMP setup of the client software

a) and b) can be achieved by using the web interface or the shell access, please see the appropriate chapters in
this manual. The mentioned MIB les can be found directly on the timeserver located at /usr/local/share/snmp/mibs. All les with names starting with MBG-SNMP- have to be copied onto the SNMP clients by using
the timeservers ftp access (for example). You may also use the web interface, on the page Local you will nd a
button Download MIB les. You will get a tar-archive if you are using the download button, which you have to
unpack rst.
Afterwards, copy all MIB les to the MIB directory on your client(s) and congure your SNMP client software to use them.

15.1.1 Examples for the usage of the SNMP configuration features
The following examples are using the software net-snmp, a SNMP open source project. You will nd detailed
information at www.net-snmp.org!
To browse the conguration branch of the timeserver-MIB, you could use the following command on a UNIX
system with net-snmp SNMP tools installed:
root@testhost:/# snmpwalk -v 2c -c public timeserver.meinberg.de mbgLtCfg

LANTIME M600 GPS PTP

Date: 27th October 2011

91

Page 92

15 SNMP Support

MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfghostname.0 = STRING: LantimeSNMPTest
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgDomainname.0 = STRING: py.meinberg.de
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgNameserver1.0 = STRING: 172.16.3.1
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgNameserver2.0 = STRING:
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgSyslogserver1.0 = STRING:
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgSyslogserver2.0 = STRING:
[ ... ]
To alter a parameter, with net-snmp you would use the snmpset command:
root@testhost:/# snmpset -v 2c -r 0 -t 10 -c rwsecret timeserver.meinberg.de
mbgLtCfghostname.0 string helloworld

MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfghostname.0 = STRING: helloworld
root@testhost:/#

Please note that your SNMP request has to be sent with a sucient timeout (in the above snmpset example
this was achieved by using the -t 10 option, choosing a timeout of 10 seconds), because after each parameter
change, the timeserver reloads its conguration, which takes a few seconds. The request is acknowledged by the
SNMP agent afterwards.
To change a group of parameters without reloading the conguration after each parameter, you have to send all
parameter changes in one single request. You can do this with the net-snmp snmpset command by speciying
multiple parameters in one command line:
root@testhost:/# snmpset -v 2c -r 0 -t 10 -c rwsecret timeserver.meinberg.de
mbgLtCfghostname.0 string helloworld mbgLtCfgDomainname.0 string
internal.meinberg.de

MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfghostname.0 = STRING: helloworld
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgDomainname.0 = STRING: internal.meinberg.de
root@testhost:/#

The available SNMP variables are described in detail in the SNMP conguration reference part of this manual.
Additionally, it is recommended to also read the mentioned MIB les.

15.1.2 Further configuration possibilities
Because the timeserver uses a standard version of the net-snmp SNMP daemon (with extended features covering
the timeserver-specic functions), all conguration parameters of the SNMPD can be used. The conguration
le of the SNMP daemon is located at /usr/local/share/snmp after boot time, the lename is snmpd.conf.
During the boot sequence, this le is created dynamically by using a template le and appending the SNMP
parameters stored in the timeserver setup.
If you need to customize the conguration of the timeservers SNMPD (for setting up detailed access control
rights for example), you may edit /mnt/ash/packages/snmp/etc/snmpd_conf.default (which is the mentioned template le). Please note that some lines are appended to this le (as described above), before it is used
as /usr/local/share/snmp/snmpd.conf by the snmpd process.

15.1.3 Send special timeserver commands with SNMP
The timeserver is capable of receiving special commands by SNMP in order to reboot the unit or reload its
conguration after you manually changed it. A special SNMP variable is reserved for this (mbgLtCmdExecute)
and has to be set to a special integer value for each command. The following commands are available:
Reboot(1)

92

Date: 27th October 2011

LANTIME M600 GPS PTP

15.1 Conguration over SNMP

Page 93

Setting the mbgLtCmdExecute variable to value 1 will reboot the timeserver after a short waiting period of approximately 3-5 seconds.
FirmwareUpdate(2)

This command installs a previously uploaded (with FTP for example) rmware version.
ReloadCong(3)

The parameters of the timeserver conguration (stored in
/mnt/ash/global_conguration) are re-read and afterwards a number of subsystems (e.g. NTPD, HTTPD/HTTPSD,
SMBD) will be restarted in order to use those eventually changed settings. Please note that the SNMPD will not
be restarted by this command (you have to use reboot instead or restart it manually by killing the process and
starting it again in the shell).
GenerateSSHKey(4)

A new SSH key will be generated.
GenerateHTTPSKey(5)

A new HTTPS key will be generated.
ResetFactoryDefaults(6)

The conguration of the timeserver is reset to factory defaults, afterwards an automatic ReloadCong is executed
in order to use these default settings.
GenerateNewNTPAutokeyCert(7)

A new key is generated, it can be used with the NTP AUTOKEY feature.
SendTestNotication(8)

A test message is sent by using all notication methods the timeserver has a conguration for (e.g. mail, winpopup, SYSLOG etc.).
A few examples:

(we are again using the snmpset command which comes with the net-snmp tools).

root@testhost:/# snmpset -v2c -r 0 -t 10 -c rwsecret timeserver.meinberg.de
mbgLtCmdExecute.0 int 1

MBG-SNMP-LANTIME-CMD-MIB::mbgLtCmdExecute.0 = INTEGER: Reboot(1)
root@testhost:/#

The command shown above is forcing the timeserver to reboot. Instead of using the integer value, you may also
enter the command name, as it is dened in the MIB le MBG-SNMP-LANTIME-CMD.txt (and in the command
list above).
If you want the timeserver to reload it's conguration le (which you previously uploaded via FTP probably),
you would enter this command:

root@testhost:/# snmpset -v2c -r 0 -t 10 -c rwsecret timeserver.meinberg.de
mbgLtCmdExecute.0 int ReloadCong

MBG-SNMP-LANTIME-CMD-MIB::mbgLtCmdExecute.0 = INTEGER: ReloadCong(3)
root@testhost:/#

Please pay attention to the options -r 0 (meaning no retries) and -t 10 (meaning timeout of 10 secs) in
the above examples. These options avoid multiple executions of the desired command, additionally they give your
snmpset command enough time to wait for an acknowledgement from the timeservers snmp agent.

LANTIME M600 GPS PTP

Date: 27th October 2011

93

Page 94

15 SNMP Support

15.1.4 Configuration of the timeserver with SNMP: Reference
The MIB of the timeserver includes the following parts:
SNMP Object

Name

Description

enterprises.5597

mbgSNMP

Root node of the Meinberg-MIB

mbgSNMP.3

MbgLANTIME

Root node of the LANTIME MIB

mbgLANTIME.1

mbgLtNtp

LANTIME NTP status variables

mbgLANTIME.2

mbgLtRefclock

LANTIME reference time source status variables

mbgLANTIME.3

mbgLtTraps

LANTIME SNMP traps

mbgLANTIME.4

mbgLtCfg

LANTIME conguration variables

mbgLANTIME.5

mbgLtCmd

LANTIME control commands

Further detailed information can be found in the Meinberg MIB les.
Reference of LANTIME SNMP conguration variables:

SNMP branch

Variable

Data type

Description

mbgLtCfgNetwork

mbgLtCfghostname

string

The hostname of the timeserver

mbgLtCfgDomainname

string

The Domainname of the timeserver

mbgLtCfgNameserver1

string

(IPv4

or

IP-address of rst nameserver

or

IP-address of second nameserver

IPv6-address)

mbgLtCfgNameserver2

string

(IPv4

IPv6-address)

mbgLtCfgSyslogserver1

string

(IPv4

IPv6-address

or

IP-address or hostname of rst syslog-

or

server

or

IP-address or hostname of second syslog-

or

server

hostname)

mbgLtCfgSyslogserver2

string

(IPv4

IPv6-address
hostname)

mbgLtCfgTelnetAccess

integer (0 = disabled,

1

=

Telnet access activated?

en-

abled)

mbgLtCfgFTPAccess

integer (0 = disabled,

1

=

FTP-access activated?

en-

abled)

mbgLtCfgHTTPAccess

integer (0 = disabled,

1

=

Webinterface activated?

en-

abled)

mbgLtCfgHTTPSAccess

integer (0 = disabled,

1

=

Encrypted webinterface activated?

en-

abled)

mbgLtCfgSNMPAccess

integer (0 = disabled,

1

=

SNMP-daemon activated?

en-

abled)

94

Date: 27th October 2011

LANTIME M600 GPS PTP

15.1 Conguration over SNMP
SNMP branch

Page 95

Variable

Data type

mbgLtCfgSambaAccess

integer (0 = disabled,

1

Description

=

LANManager-access activated?

en-

abled)

mbgLtCfgIPv6Access

integer (0 = disabled,

1

=

IPv6-protocol enabled?

en-

abled)

mbgLtCfgSSHAccess

integer (0 = disabled,

1

=

SSH-access activated?

en-

abled)

mbgLtCfgNTP

mbgLtCfgNtpServer1IP

string

(IPv4

IPv6-address

or

First external NTP-server

or

hostname)

mbgLtCfgNtpServer1KEY

integer

Link to the key which should be used for
the rst NTP-server

mbgLtCfgNtpServer2IP

string

(IPv4

IPv6-address

or

Second external NTP-server

or

hostname)

mbgLtCfgNtpServer2KEY

integer

Link to the key which should be used for
the second NTP-server

mbgLtCfgNtpServer3IP

string

(IPv4

IPv6-address

or

Third external NTP-server

or

hostname)

mbgLtCfgNtpServer3KEY

integer

Link to the key which should be used for
the third NTP-server

mbgLtCfgStratumLocal

integer(0..15)

Stratum-value

Clock

of

the

internal

system

clock of the timeserver

mbgLtCfgNTPTrustedKey

integer

Link to the key which should be used for
the internal reference time source

mbgLtCfgNTPBroadcastIP

string

(IPv4

or

IPv6-address)

mbgLtCfgNTPBroadcast

IP-address,

which has to be used for

NTP-broadcasts (or multicasts)

integer

Link to the key which should be used for

Key

outgoing NTP-broadcasts

mbgLtCfgNTPBroadcast

integer (0 = dis-

Autokey

abled,

1

=

Use autokey for NTP broadcasts?

en-

abled)

mbgLtCfgAutokeyFeature

integer (0 = disabled,

1

=

Use autokey feature of the NTP server?

en-

abled)

LANTIME M600 GPS PTP

Date: 27th October 2011

95

Page 96
SNMP branch

15 SNMP Support
Variable

Data type

mbgLtCfgAtomPPS

integer (0 = disabled,

1

Description

=

en-

(Liste

von

Atom PPS (pulse per second) activated?

abled)

mbgLtCfgEMail

mbgLtCfgEMailTo

string

EMail-addressn)

One or more (semicolon separated) email
address(es). which should receive warnings and alarm notications from the
timeserver

mbgLtCfgEMailFrom

string

(EMail-

address)

mbgLtCfgEMailSmarthost

string

The EMail-address which is used as the
senders address for email notifcations

(IPv4

IPv6-address

or

The SMTP-host, which is used for send-

or

ing mails

or

First host, which receives notications

or

sent as SMTP-traps

hostname)

mbgLtCfgSNMP

mbgLtCfgSNMPTrapRecei

string

ver1

IPv6-address

(IPv4

hostname)

mbgLtCfgSNMPTrapRecei

string

The SNMP community used when send-

ver1Community

ing SNMP-Traps to the rst host

mbgLtCfgSNMPTrapRecei

string

ver2

IPv6-address

(IPv4

or

Second host, which receives notications

or

sent as SMTP-traps

hostname)

mbgLtCfgSNMPTrapRecei

string

ver2Community

The SNMP community used when sending SNMP-Traps to the second host

mbgLtCfgSNMPRO

string

Community

The SNMP community, which has readonly access and therefore can be used to
only monitor status variables or conguration values (SNMP V2c)

mbgLtCfgSNMPRW

string

Community

The SNMP community, which has readwrite access and there for can be used
to monitor status variables and get/set
conguration values (SNMP V2c)

mbgLtCfgSNMPContact

string

Contact information (e.g. name of a contact person) of the timeserver

mbgLtCfgSNMPLocation

string

Location (e.g. building/room number) of
the timeserver

mbgLtCfgWinpopup

mbgLtCfgWMailAddress1

string

First receiver of notications sent as windows popup messages

mbgLtCfgWMailAddress2

string

Second receiver of notications sent as
windows popup messages

96

Date: 27th October 2011

LANTIME M600 GPS PTP

15.1 Conguration over SNMP

Page 97

SNMP branch

Variable

mbgLtCfgWalldisplay

mbgLtCfgVP100Display1IP string

Data type

(IPv4

IPv6-address

mbgLtCfgVP100Display

Description

or

hostname or IP-address of the rst wall-

or

mount display used for showing notica-

hostname)

tions

string (Hexstring)

The serial number of the rst wall mount

1SN

display

used

for

showing

notications

(can be found in the setup menu of the
display)

mbgLtCfgVP100Display

string

2IP

IPv6-address

mbgLtCfgVP100Display

(IPv4

or

hostname or IP-address of the second

or

wall mount display used for showing no-

hostname)

tications

string (Hexstring)

The serial number of the rst wall mount

2SN

display

used

for

showing

notications

(can be found in the setup menu of the
display)

mbgLtCfgNotify

mbgLtCfgNotifyNTPNot

string(combination)

Sync

Exactly one, none or a combination of
the following notication types:

email = sending an email
wmail = sending a winpopup-message
snmp = sending a SNMP-trap,
disp = showing on wall mount display,
syslog = sending a syslog-entry
for the event NTP not synchronized

mbgLtCfgNotifyNTP

string

Stopped

tion)

mbgLtCfgNotifyServer

string

Boot

tion)

mbgLtCfgNotifyRefclock

string

NotResponding

tion)

mbgLtCfgNotifyRefclock

string

NotSync

tion)

mbgLtCfgNotifyAntenna

string

Faulty

tion)

(combina-

(see

mbgLtCfgNotifyNTPNotSync)

for

the event NTP Daemon stopped

(combina-

(see

mbgLtCfgNotifyNTPNotSync)

for

the event Timeserver reboot

(combina-

(see

mbgLtCfgNotifyNTPNotSync)

for

the event Refclock not ready

(combina-

(see

mbgLtCfgNotifyNTPNotSync)

for

the event Refclock not synchron

(combina-

(see

mbgLtCfgNotifyNTPNotSync)

for

the event GPS antenna not connected
or dammaged

mbgLtCfgNotifyAntenna

string

Reconnect

tion)

mbgLtCfgNotifyCong

string

Changed

tion)

mbgLtCfgNotifyLeapSecond string
Announced

LANTIME M600 GPS PTP

(combina-

(see

mbgLtCfgNotifyNTPNotSync)

for

the event GPS antenna reconnected

(combina-

(see

mbgLtCfgNotifyNTPNotSync)

for

the event Conguration changed

(combina-

tion)

Date: 27th October 2011

(see

mbgLtCfgNotifyNTPNotSync)

for

the event Leap second announced

97

Page 98

15 SNMP Support

SNMP branch

Variable

Data type

mbgLtCfgEthernet

mbgLtCfgEthernetIf0IPv4

string

Description

IP

address)

the timeserver

mbgLtCfgEthernetIf0IPv4

string (IPv4 Netz-

IPv4-netmask of rst network interface of

Netmask

maske)

the timeserver

mbgLtCfgEthernetIf0IPv4

string

Gateway

address)

(IPv4

(IPv4

IP-

IP-

IPv4-address of rst network interface of

IPv4-address of the default gateway of
the timeservers rst network interface

mbgLtCfgEthernetIf0DHCP integer (0 = dis-

Congure the rst network interface of

Client

abled,

=

en-

the timeserver with DHCP?

(IPv6

IP-

First IPv6-IP-address of the timeservers

1

abled)

mbgLtCfgEthernetIf0IPv6

string

IP1

address)

mbgLtCfgEthernetIf0IPv6

string

IP2

address)

mbgLtCfgEthernetIf0IPv6

string

IP3

address)

mbgLtCfgEthernetIf0IPv6

integer (0 = dis-

Activate autoconf for the IPv6 - cong-

Autoconf

abled,

uration of the timeservers rst network

mbgLtCfgEthernetIf0

rst network interface

(IPv6

Second

IPv6-IP-address

of

the

time-

servers rst network interface

(IPv6

1

IP-

IP-

Third IPv6-IP-address of the timeservers
rst network interface

=

en-

abled)

interface?

integer (0..4)

Conguration of the network-speed and

NetlinkMode

duplex settings of the timeservers rst
network interface

0 = autosensing,
1 = 10Mbit/s half duplex,
2= 10Mbit/s full duplex,
3=100Mbit/s half duplex,
4=100Mbit/s full duplex

For all additional Ethernet interfaces of the timeserver, If0 only has to be replaced with Ifx, where x is
substituted by the number of the desired Ethernet interface. Example: The IPv4-address of the timeservers third
Ethernet interface can be set with mbgLtCfgEthernetIf2IPv4IP!

15.2 SNMP Traps
If congured, the LANTIME is sending SNMP traps, which can be received by up to 2 SNMP management systems. These traps can be received by using the NET-SNMP suite tool snmptrapd, you can start it on a UNIX
system with snmptrapd p (-p is for output to stdout, -s would use the syslog for output). The corresponding
MIB les can be found on the LANTIME at /usr/local/share/snmp/mibs/ , all Meinberg specic MIB les are
named MBG-SNMP. . . . . These MIB les can be downloaded by using the web interface (see Local page,
Download MIB les button), after unpacking the archive le you can import the MIB les into your management
system.
The following SNMP-traps are available:

98

Date: 27th October 2011

LANTIME M600 GPS PTP

15.2 SNMP Traps

Page 99

"NTP not sync"

NTP not synchronised to refclock

"NTP stopped"

NTP stopped

"Server boot"

System has rebooted

"Receiver not responding"

no answer from GPS

"Receiver not sync"

GPS receiver not synchronised

"Antenna faulty"

GPS antenna not connected

"Antenna reconnect"

GPS antenna reconnected

"Cong changed"

System parameter changed by user

Leap second announced

Leap second announced

See the Notication page at the web interface and Command Line Interface description to learn how to congure
the SNMP trap receivers.

15.2.1 SNMP Trap Reference
All traps can be found under the mbgLtTraps section in the Meinberg MIB. A special trap exists for every notication event the timeserver knows. Please note that the traps are only sent if you congured the notication type
SNMP trap for the event, otherwise no trap is generated. All traps have a string parameter included, which
contains the plain text event message for the appropriate event (you are able to change the default text messages,
see web interface and/or CLI setup section to nd out how to do this).
Here is a list of all traps the timeserver knows:

Whenever the NTP daemon (ntpd) looses sync, it will generate this trap and send it to the congured SNMP trap receivers.

•

mbgLtTrapNTPNotSync (mbgLtTraps.1):

•

mbgLtTrapNTPStopped (mbgLtTraps.2):

or because of an error condition.

This trap is sent when the NTP daemon stopped, manually

After nishing the boot process, this trap is generated.

•

mbgLtTrapServerBoot (mbgLtTraps.3):

•

mbgLtTrapReceiverNotResponding (mbgLtTraps.4):

timeserver is not responding.

•

mbgLtTrapReceiverNotSync (mbgLtTraps.5):

ceivers will receive this trap.

If the internal receiver looses sync, the SNMP trap re-

This trap will be sent whenever the timeserver recognises a
broken connection to the antenna of the receiver.

•

mbgLtTrapAntennaFaulty (mbgLtTraps.6):

•

mbgLtTrapAntennaReconnect (mbgLtTraps.7):

established, this trap is sent.

•

mbgLtTrapCongChanged (mbgLtTraps 8):

this trap.

•

After the connection to the antenna has been re-

After reloading its conguration, the timeserver generates

mbgLtTrapLeapSecondAnnounced (mbgLtTraps 9):

GPS receiver, this trap will be sent.

•

Trap to be sent when the internal receiver of the

If a leap second has been announced by the internal

This trap is sent whenever you are requesting a test
notication; it is only used for testing the connection between the timeserver and your SNMP trap receivers.

mbgLtTrapTestNotication (mbgLtTraps 99):

LANTIME M600 GPS PTP

Date: 27th October 2011

99

Page 100

16 Attachment: Technical Information

16 Attachment: Technical Information
16.1 Skilled/Service-Personnel only: Replacing the Lithium Battery
The life time of the lithium battery on the board is at least 10 years. If the need arises to replace the battery, the
following should be noted:

ATTENTION!
There is a Danger of explosion if the lithium battery is
replaced incorrectly. Only identical batteries or batteries recommended by the manufacturer must be used for
replacement.
The waste battery has to be disposed as proposed
by the manufacturer of the battery.

CE marking

This device follows the provisions
of the directives 93/68/EEC

16.2 Technical Specifications M600/300 Multipac
HOUSING:

Metal desktop case, Schro 282T
Front panel: 1U/84HP (43 mm high / 442 mm wide)

POWER
SUPPLY:

100-240 VAC/VDC

INPUT FUSE:

Electronic

PROTECTION
RATING:

IP20

POWER
CONSUMPTION: 28W
PHYSICAL
DIMENSIONS:

100

442 mm wide x 43 mm high x 288 mm deep
(498 mm wide with mounting bracket, 85mm high as XL/2U model)

Date: 27th October 2011

LANTIME M600 GPS PTP

16.3 Safety instructions for building-in equipment

Page 101

16.3 Safety instructions for building-in equipment
This building-in equipment has been designed and tested in accordance with the requirements of Standard
IEC60950-1 "Safety of Information Technology Equipment, including Electrical Business Equipment".
During installation of the building-in equipment in an end application (i.e. rack) additional requirements in
accordance with Standard IEC60950-1 have to be taken into account.

• The building-in equipment is a class 1 - equipment and must be connected to an earthed outlet
(TN Power System).
• The building-in equipment has been evaluated for use in oce environment (pollution degree 2) and may be
only used in this environment. For use in rooms with a higher pollution degree more stringent requirements
are applicable.
• The building-in equipment may not be opened.
• Protection against re must be assured in the end application.
• The ventilation opening may not be covered.
• The equipment/building-in equipment was evaluated for use in a maximum ambient temperature of 40◦ C.
• For safe operation the building-in equipment must be protected by max 16 A fuse in the power installation
system.
• Disconnection of the equipment from mains is done by pulling the mains plug.

16.3.1 CE-Label
Low voltage directive:

2006/95/EC EN 60950-1

EMV-directive:

89/336EEC EN50081-1

Safety of Information Technology Equipment,
including Electrical Business Equipment
Electromagnetic compatibility.
Electromagnetic compatibility (EMC).
Generic emission standard.
Part 1: Residential, commercial and light industry
EN50082-2

Electromagnetic compatibility (EMC).
Generic immunity standard.
Part 2: Industrial environment

LANTIME M600 GPS PTP

Date: 27th October 2011

101

Page 102

16 Attachment: Technical Information

16.4 Rear Panel Connectors

Name

Type

Signal

Cabel


Network
RJ-45
Ethernet
shielded data line
IEEE1588 PTP
RJ-45
Ethernet
shielded data line
Error
DFK
relay
screw terminal
Time Code (IRIG-B)

modulated (AM)
DCLS

BNC
BNC

3Vpp into 50 Ohm
2.5Vpp into 50 Ohm

shielded coaxial line
shielded coaxial line

PPS,PPM
10 MHz
Syntheziser
COM 0 , COM 1

BNC
BNC
BNC
9pol. D-SUB

TTL
TTL
TTL
RS232

shielded
shielded
shielded
shielded

data
data
data
data

line
line
line
line

Antenne
Netz

BNC
1575.42 MHz
shielded data line
power cord receptable
power supply cord
(option DFK)

option

add. Network or
add. Network (FO)

102

RJ-45
SC- or STconnectors

Ethernet
100BaseFX

Date: 27th October 2011

shielded data line
GI 50/125µm or
GI 62,5/125µm
multimode gradient ber

LANTIME M600 GPS PTP

16.5 Connector Assignments

Page 103

16.5 Connector Assignments

1

TxD0_OUT
RxD0_IN
GND -

5

1

6

TxD1_OUT
RxD1_IN

9

GND -

COM0

5

6

9

COM1

16.6 TERMINAL (Console)
To connect a serial terminal use 9 pin SUBD RS232 connector in the front panel. Via the serial terminal connection it is possible to congure parameters with the command line interface. You have to use a NULL-MODEM
cable connecting to your PC or Laptop computer. You can use e.g. the standard Hyperterminal program shipped
with your Windows operating system. Congure your terminal program with 38400 Baud, 8 Databits, no parity
and 1 Stopbit. The terminal emulation have to set to VT100. After connecting to the timeserver there will be
displayed the login message (press RETURN for rst connection; default user: root password: timeserver).

DSR_IN RTS_OUTCTS_INRI_IN-

6

9

1

5

-DCD_IN
-RXD_IN
-TXD_OUT
-DTR_OUT
-GND

TERM

LANTIME M600 GPS PTP

Date: 27th October 2011

103

Page 104

16 Attachment: Technical Information

16.7 Error Relay
On the back panel of the device you can nd a DFK connector labeled Error. This relay output is connected
to the TTL TIME_SYNC output of the reference clock (GPS, PZF, TCR, ...). If the internal reference clock
has been synchronized by its source (GPS, DCF77 or IRIG) the relay will switch to mode NO . In case of bad
antenna signal or the device has been switched o the relay falls back to mode NC.
Additionally the relay can be switched by one of the notication conditions. In the notication condition table via WEB or CLI interface you can select the relay out. The priority is on the TIME SYNC ERROR signal of
the receiver (refclock not sync). Relay state which will be set via notication conditions will be reseted by any
access via the WEB or CLI interface (if no TIME SYNC ERROR is active).

16.7.1 Technical Specification
SWITCHING VOLTAGE max.:

125 VDC
150 VAC
1A

SWITCHING CURRENT max.:
SWITCHING LOAD max.:
SWITCHING-CURRENT
UL/CSA:

RESPONSE TIME:

DC
AC

30 W
60 VA

0.46A
0.46A
1A

150V AC
65V DC
30V DC

ca.2ms

Error

Normal Operation: CO - NO connected
Error:

CO - NC connected

CO NO NC
Error

VCC

104

Date: 27th October 2011

LANTIME M600 GPS PTP

16.8 Technical Specications GPS receiver

Page 105

16.8 Technical Specifications GPS receiver

RECEIVER:

6 channel C/A code receiver with external antenna/converter unit

ANTENNA:

Antenna/converter unit with remote power supply refer to chapter
"Technical Specications GPS Antenna"

ANTENNA
INPUT:
LC DISPLAY:

Antenna circuit dc-insulated; dielectric strength: 1000 V
Length of cable: refer to chapter "Mounting the Antenna"
1HE: 2 x 40 character, menu selectable by push buttons and light
BGT: 4 x 16 Zeichen, menu selectable by push buttons

TIME TO
SYNCHRONIZATION: One minute with known receiver position and valid almanac
12 minutes if invalid battery buered memory
PULSE OUTPUTS:
ACCURACY
OF PULSES:

Change of second (P_SEC, TTL level)
Change of minute (P_MIN, TTL level)
Better than +-250 nsec after synchronization and 20 minutes of operation
Better than +-2 µsec during the rst 20 minutes of operation

FREQUENCY
OUTPUTS:

10 MHz (TTL level)

SERIAL PORTS:

3 asynchronous serial ports (RS-232)
COM0:
COM1:
COM2+3:

xed, internal used
xed, internal used
congurable, sending Standard Meinberg
Time String (once per second or per minute)

POWER
REQUIREMENTS:

5 V +- 5 %, @ 700 mA

PHYSICAL
DIMENSION:

Eurocard, 100 mm x 160 mm

REAR EDGE
CONNECTOR:

According to DIN 41612, type C 64, rows a+c (male)

RF CONNECTOR:

Coaxial SMB connector (male)

AMBIENT
TEMPERATURE:

0 ... 50 ◦ C

HUMIDITY:

85 % max.

LANTIME M600 GPS PTP

Date: 27th October 2011

105

106

Date: 27th October 2011

1·10-9
< ±250 ns
1Hz -60dBc/Hz
10Hz -90dBc/Hz
100Hz -120dBc/Hz
1kHz -130dBc/Hz
±2·10-8
±0.2Hz (Note1)
±4·10-7
±4Hz (Note1)
±1·10-11

± 865 µs
± 6.3 s
±2·10-7
(0...60°C)

2·10-9

< ±250 ns

1Hz -60dBc/Hz
10Hz -90dBc/Hz
100Hz -120dBc/Hz
1kHz -130dBc/Hz
±1·10-7
±1Hz (Note1)
±1·10-6
±10Hz (Note1)
±1·10-11

± 4.3 ms

± 16 s

±1·10-6
(-20...70°C)

OCXO LQ

±5·10-8
(-20...70°C)

± 1.6 s

± 65 µs

1Hz -75dBc/Hz
10Hz -110dBc/Hz
100Hz -130dBc/Hz
1kHz -140dBc/Hz
±1.5·10-9
±15mHz (Note1)
±1·10-7
±1Hz (Note1)
±5·10-12

< ±100 ns

2·10-10

OCXO MQ

±1·10-8
(5...70°C)

± 788 ms

± 22 µs

1Hz < -85dBc/Hz
10Hz < -115dBc/Hz
100Hz < -130dBc/Hz
1kHz < -140dBc/Hz
±5·10-10
±5mHz (Note1)
±5·10-8
±0.5Hz (Note1)
±1·10-12

< ±100 ns

5·10-12

OCXO HQ

±2·10-10
(5...70°C)

± 158 ms

± 4.5 µs

1Hz < -80dBc/Hz
10Hz < -110dBc/Hz
100Hz < -125dBc/Hz
1kHz < -135dBc/Hz
±1·10-10
±1mHz (Note1)
±1·10-8
±0.1Hz (Note1)
±1·10-12

< ±100 ns

2·10-12

OCXO DHQ

±6·10-10
(-25...70°C)

± 8 ms

± 1.1 µs

1Hz -75dBc/Hz
10Hz -89dBc/Hz
100Hz -128dBc/Hz
1kHz -140dBc/Hz
±2·10-11
±0.2mHz (Note1)
±5·10-10
±5mHz (Note1)
±1·10-12

< ±100 ns

Rubidium
(only available
for 3U models)
2·10-11

The given values for the accuracy of frequency and �me (not short term accuracy) are only valid for a constant ambient
temperature! A minimum �me of 24 hours of GPS-syncronicity is required before free run starts.

Note 1: The accuracy in Hertz is based on the standard frequency of 10 MHz.
For example: Accuracy of TCXO (free run one day) is ±1·10-7·10MHz = ± 1 HZ

accuracy
free run, one day
accuracy,
free run, 1 year
accuracy
GPS-synchronous,
average 24h
accuracy of time
free run, 1 day
accuracy of time
free run, 1 year
temperature
depandant drift
free run

short term stability
(� = 1 sec)
accuracy of PPS
(pulse per sec)
phase noise

TCXO

Oscillators available for Meinberg GPS Receivers/Time Servers:
OCXO, TCXO, Rubidium

Page 106
16 Attachment: Technical Information

16.8.1 Oscillator specifications

LANTIME M600 GPS PTP

16.8 Technical Specications GPS receiver

Page 107

16.8.2 Technical Specifications GPS Antenna
ANTENNA:

dielectrical patch antenna,
receive frequency:

BANDWITH:

9 MHz

CONVERTER:

local oscillator to
converter frequency:
rst IF frequency:

POWER
REQUIREMENTS:

10 MHz
35.4 MHz

12V ... 18V, @ 100mA
(provided via antenna cable)

CONNECTOR:

N-Type, female

AMBIENT
TEMPERATURE:

-40 ... +65◦ C

HOUSING:

25 x 25 mm
1575.42 MHz

ABS plastic case for
outdoor installation (IP66)

Physical Dimension:

140

6

180

68
84

450
70

44

M6

240

LANTIME M600 GPS PTP

Date: 27th October 2011

107

Page 108

16 Attachment: Technical Information

16.8.3 Signal Description GPS170
Name
Pin
Function

GND
32a+c
Ground
VCC in (+5V)
1a+c
+5V supply
VCC in (+12V)
2a+c
+12V supply (only for older oscillators)
VDD in (+5V)
3a+c
+5 V supply (TCXO / OCXO)
P_SEC out

6c

Pulse when second changes, TTL level,
active high, length 200 msec

P_MIN out

8c

Pulse when minute changes, TTL level,
active high, length 200 msec

/RESET in/out
Prog. Pulse out
100 kHz out
1 MHz out
10 MHz out
TIME CODE DC
TIME CODE AM

9c
10c-12c
10a
11a
12a
13a
14a

RESET signal, Open Drain pulled up to +5V
programmable pulse, TTLlevel
100 kHz frequency output, TTL level
1 MHz frequency output, TTL level
10 MHz frequency output, TTL level
Time code unmod. out
Time code mod. out 3Vpp

DCF_MARK out

17c

DCF77 compatible second marks, TTL level,
active high, length 100/200 msec

TIME_SYN

19c

TTL output, HIGH level
if synchronization has been achieved,
LOW level after reset or in case
of serious errors (e.g. antenna faulty)

F_SYNTH

21c

Synthesizer output, TTL-Pegel

F_SYNTH_OD

22c

Synthesizer output, Open Drain,
max sink current to GND: 150mA

F_SYNTH_SIN

23c

Synthesizer output, sine-wave 1.5 V e.

CAPx

27c, 28c

Time capture inputs (TTL),
capture on falling slope

COMx TxD out
COMx RxD in

COMx RS-232 transmit data output
COMx RS-232 receive data input

SDA, SCL, SCL_EN
(reserved)

internal serial control bus,
for extension boards, reserved, do not connect

108

Date: 27th October 2011

LANTIME M600 GPS PTP

16.8 Technical Specications GPS receiver

Page 109

16.8.4 Rear Connector Pin Assignments GPS170
PIN

a

c

1

VCC in (+5V)

VCC in (+5V)

2

VCC in (+12V)

VCC in (+12V)

3

VDD in (TCXO/OCXO)

VDD in (TCXO/

4

(reserved, FreqAdjust out)

5
6

P_SEC out

7
8

(reserved, 10 MHz in) P_MIN out

9

/RESET in/out

10

100 kHz out

ProgPulse0 out

11

1 MHz out

ProgPulse1 out

12

10 MHz out

ProgPulse2 out

13

SCL

14

SCL_EN

15

COM2 RxD in

SDA

16

COM2 TxD out

(reserved, P3.2)

17

COM3 RxD in

DCF_MARK out

18

COM3 TxD out

(reserved, Vref/TxD2

19

GND

TIME_SYN out

20

GND

(reserved, P2.3)

21

GND

F_SYNTH out

22

GND

F_SYNTH_OD out

23

GND

F_SYNTH_SIN out

24

GND

COM1 TxD out

25

GND

26

GND

COM0 TxD out

27

GND

CAP1 in

28

GND

CAP0 in

29

GND

COM1 RxD in

30

GND

COM0 RxD in

31

GND

GND

32

GND

GND

DIN 41612 connector, Typ C 64, row a + c

LANTIME M600 GPS PTP

Date: 27th October 2011

109

Page 110

16 Attachment: Technical Information

16.9 Technical Specifications LAN CPU

PROCESSOR:

GeodeTM LX800 with 500 MHz

MAIN MEMORY:

128 MB

CACHE-MEMORY:

16 KB 2nd Level Cache

FLASHDISK:

512 MB

NETWORK
CONNECTOR:

10/100 MBIT with RJ45-Jack

SERIAl INTERFACE:

Four serial RS232-Ports 16550 compatible to FIFO
- RS232 9-pol. DSUB-male connector
- three RS232 male connector according to DIN 41612,
type C 96 ( only TxD, RxD, DCD)

PARALLEL
INTERFACE :

One LPT-Port male connector type C 96

VGA-CONNECTION:

10-pol pin contact strip

KEYBOARD
CONNECTION:

10-pol pin contact strip

STATE LEDs:
POWER
REQUIREMENTS:

- power supply
- 'Connect', 'Activity' and 'Speed' of the network connection
5 V +- 5 %, @ 1 A

FRONTPANEL:

3 HE / 4 TE (128 mm high x 20,3 mm wide)

CONNECTOR:

According to DIN 41612, type C 96, rows a+b+c (male)
DSUB-plug (9-pol) RJ45-jack, USB Port

AMBIENT
TEMPERATURE:

0 ... 50 ◦ C

HUMIDITY:

85 % max.

110

Date: 27th October 2011

LANTIME M600 GPS PTP

16.9 Technical Specications LAN CPU

Page 111

16.9.1 Rear Connector Pin Assignments LAN CPU
c

b

a

1

VCC in (+5V)

VCC in (+5V)

VCC in (+5V)

2

VCC in (+5V)

VCC in (+5V)

VCC in (+5V)

3

GND

GND

GND

4

PPS in

/AFD out

5

/ERR in

/SLIN out

/INIT out

6
7
8

/ACK in

9

/SLCT in

10

GND

GND

GND

11

GND

GND

GND

16

- USB1 in/out

+ USB1 in/out

17

+ USB3 in/out

18

- USB3 in/out

12
13
14
15

19
20

- USB2 in/out

+ USB2 in/out

21

10MHz in

22

GND

GND

GND

23

Rx+ in

Tx- out

Tx+ out

24

Rx- in

- USB4 in/out

25

+ USB4 in/out

LED SPEED 100M out

LED 10M out

26

GND

GND

GND

27

RxD4 in

TxD4 out

DCD4 in

28

RxD3 in

TxD3 out

DCD3 in

29

RxD2 in

TxD2 out

PPS2 in

30

RxD1 in

TxD1 out

DCD1 in

31

GND

GND

GND

32

GND

GND

GND

16.9.2 VGA, Keyboard Connector Pin Assignments

R
G
B
+5V
KBDAT

LANTIME M600 GPS PTP

Date: 27th October 2011

HSYNC
VSYNC
GND
GND
KBCLK

VGA
Tastatur

111

Page 112

16 Attachment: Technical Information

16.10 Technical Specifications Power Supply
INPUT:

85 ... 264 V AC, 47 ... 63 Hz, 1 A/230 V, 2 A/115 V

FUSE:

Electronic

16.11 Time Code
16.11.1 Abstract of Time Code
The transmission of coded timing signals began to take on widespread importance in the early 1950
s. Especially
the US missile and space programs were the forces behind the development of these time codes, which were used
for the correlation of data. The denition of time code formats was completely arbitrary and left to the individual
ideas of each design engineer. Hundreds of dierent time codes were formed, some of which were standardized
by the "Inter Range Instrumentation Group" (IRIG) in the early 60
s.
Except these "IRIG Time Codes", other formats like NASA36, XR3 or 2137 are still in use. The board TCR
however generates the IRIG-B, AFNOR NFS 87-500 code as well as IEEE1344 code which is an IRIG coded
extended by information for time zone, leap second and date. Other formats may be available on request.

16.11.2 Principle of Operation
The Board TCG has been designed for the generation of IRIG, AFNOR and IEEE1344 standard time codes. Apart
from the digitally generated amplitude-modulated code, the TCG also provides the unmodulated DC-Level shift

112

Date: 27th October 2011

LANTIME M600 GPS PTP

16.11 Time Code

Page 113

code. The modulated sine wave carrier and the board
s internal time pattern are derived from the radio clock
s
disciplined oscillator.

16.11.3 Block Diagram Time Code

EPLD

10 Mhz
PPS

digital
sinewave
generator

modulator

D/A converter

timecode

driver
50 Ω
unbalanced

driver
TTL

Time Code AM

Time Code DCLS

microcontroller

LANTIME M600 GPS PTP

Date: 27th October 2011

113

Page 114

16 Attachment: Technical Information

16.11.4 IRIG Standard Format

114

Date: 27th October 2011

LANTIME M600 GPS PTP

16.11 Time Code

Page 115

16.11.5 AFNOR Standard Format

LANTIME M600 GPS PTP

Date: 27th October 2011

115

Page 116

16 Attachment: Technical Information

16.11.6 Assignment of CF Segment in IEEE1344 Code
Bit No.

Designation

Description

49

Position Identier P5

50

Year BCD encoded 1

51

Year BCD encoded 2

52

Year BCD encoded 4

53

Year BCD encoded 8

54

empty, always zero

55

Year BCD encoded 10

56

Year BCD encoded 20

57

Year BCD encoded 40

58

Year BCD encoded 80

59

Position Identier P6

60

LSP - Leap Second Pending

set up to 59s before LS insertion

61

LS - Leap Second

0 = add leap second, 1 = delete leap second 1.)

62

DSP - Daylight Saving Pending

set up to 59s before daylight saving changeover

63

DST - Daylight Saving Time

set during daylight saving time

64

Timezone Oset Sign

sign of TZ oset 0 = '+', 1 = '-'

65

TZ Oset binary encoded 1

66

TZ Oset binary encoded 2

Oset from IRIG time to UTC time.

67

TZ Oset binary encoded 4

Encoded IRIG time plus TZ Oset equals UTC at all times!

low nibble of BCD encoded year

high nibble of BCD encoded year

68

TZ Oset binary encoded 8

69

Position Identier P7

70

TZ Oset 0.5 hour

71

TFOM Time gure of merit

72

TFOM Time gure of merit

time gure of merit represents approximated clock error. 2.)

73

TFOM Time gure of merit

0x00 = clock locked, 0x0F = clock failed

74

TFOM Time gure of merit

75

PARITY

set if additional half hour oset

parity on all preceding bits incl. IRIG-B time

1.) current rmware does not support leap deletion of leap seconds
2.) TFOM is cleared, when clock is synchronized rst after power up. see chapter Selection of generated timecode

116

Date: 27th October 2011

LANTIME M600 GPS PTP

16.11 Time Code

Page 117

16.11.7 Generated Time Codes
Besides the amplitude modulated sine wave signal, the board also provides unmodulated
DC-Level Shift TTL output in parallel. Thus six time codes are available.
a) B002:
100 pps, DCLS signal, no carrier
BCD time-of-year
b)

B122:

100 pps, AM sine wave signal, 1 kHz carrier frequency
BCD time-of-year

c)

B003:

100 pps, DCLS signal, no carrier
BCD time-of-year, SBS time-of-day

d)

B123:

100 pps, AM sine wave signal, 1 kHz carrier frequency
BCD time-of-year, SBS time-of-day

e)

B006:

100 pps, DCLS Signal, no carrier
BCD time-of-year, Year

f)

B126:

100 pps, AM sine wave signal, 1 kHz carrier frequency
BCD time-of-year, Year

g)

B007:

100 pps, DCLS Signal, no carrier
BCD time-of-year, Year, SBS time-of-day

h)

B127:

100 pps, AM sine wave signal, 1 kHz carrier frequency
BCD time-of-year, Year, SBS time-of-day

i)

AFNOR:

Code according to NFS-87500, 100 pps, wave signal,
1kHz carrier frequency, BCD time-of-year, complete date,
SBS time-of-day, Signal level according to NFS-87500

j)

IEEE1344:

Code according to IEEE1344-1995, 100 pps, AM sine wave signal,
1kHz carrier frequency, BCD time-of-year, SBS time-of-day,
IEEE1344 extensions for date, timezone, daylight saving and
leap second in control functions (CF) segment.
(also see table 'Assignment of CF segment in IEEE1344 mode')

16.11.8 Selection of Generated Time Code
The time code to be generated can be selected by Menu Setup IRIG-settings or the GPS Monitorprogram
GPSMON32 (except Lantime models). DC-Level Shift Codes (PWM-signal) B00x and modulated sine wave
carrier B12x are always generated simultaneously. Both signals are provided at the VG64-Connector, i.e. if code
B132 is selected also code B002 is available. This applies for the codes AFNOR NFS 87-500 and IEEE1344 as well.
The TFOM eld in IEEE1344 code is set dependent on the 'already sync'ed' character ('#') which is sent
in the serial time telegram. This character is set, whenever the preconnected clock was not able to synchronize
after power up reset. The 'time gure of merit' (TFOM) eld is set as follows.
Clock synchronized once after power up:
Clock not synchronized after power up:

TFOM = 0000
TFOM = 1111

For testing purposes the output of TFOM in IEEE1344 mode can be disabled. The segment is set to all zeros
then.

LANTIME M600 GPS PTP

Date: 27th October 2011

117

Page 118

16 Attachment: Technical Information

16.11.9 Outputs
The module M600 provides modulated (AM) and unmodulated (DCLS) outputs. The format of the timecodes is
illustrated in the diagramms "IRIG-" and "AFNOR standard-format".

AM - Sine Wave Output

The amplitude-modulated carrier is available at the VG-connector pin 14a. The carrier frequency depends on
the code and has a value of 1 kHz (IRIG-B). The signal amplitude is 3 Vpp (MARK) and 1 Vpp (SPACE) into
50 Ohm. The encoding is made by the number of MARK-amplitudes during ten carrier waves. The following
agreements are valid:

a)
b)
c)

binary "0":
binary "1":
position-identier:

2 MARK-amplitudes, 8 SPACE-amplitudes
5 MARK-amplitudes, 5 SPACE-amplitudes
8 MARK-amplitudes, 2 SPACE-amplitudes

DCLS Output

The pulse width DCLS signals shown in the diagramms "IRIG" and "AFNOR standard format" are coexistent to
the modulated output and is available at the VG connector pin 13a with TTL level.

16.11.10 Technical Data
OUTPUTS:

Unbalanced AM-sine wave-signal:
3 VPP (MARK) / 1 VPP (SPACE) into 50 Ohm
DCLS signal: TTL, high and low active

118

Date: 27th October 2011

LANTIME M600 GPS PTP

16.12 Time Strings

Page 119

16.12 Time Strings
16.12.1 Format of the Meinberg Standard Time String
The Meinberg Standard Time String is a sequence of 32 ASCII characters starting with the STX (start-of-text)
character and ending with the ETX (end-of-text) character. The format is:
D:dd.mm.yy;T:w;U:hh.mm.ss;uvxy 

The letters printed in italics are replaced by ASCII numbers whereas the other
characters are part of the time string. The groups of characters as dened below:

dd.mm.yy

Start-Of-Text, ASCII Code 02h
sending with one bit occuracy at change of second
the current date:
dd
day of month
(01..31)
mm
month
(01..12)
yy
year of
the century (00..99)

w

the day of
the week

hh.mm.ss

the current
hh
mm
ss

uv

(1..7, 1 = Monday)
time:
hours
minutes
seconds

(00..23)
(00..59)
(00..59, or 60 while leap second)

clock status characters (depending on clock type):
u:

`#'
``

v:

`*'
``

GPS: clock is running free (without exact synchr.)
PZF: time frame not synchronized
DCF77: clock has not synchronized after reset
(space, 20h)
GPS: clock is synchronous (base accuracy is reached)
PZF: time frame is synchronized
DCF77: clock has synchronized after reset
GPS: receiver
PZF/DCF77:
(space, 20h)
GPS: receiver
PZF/DCF77:

has not checked its position
clock currently runs on XTAL
has determined its position
clock is syncronized with transmitter

x

time zone indicator:
`U'
``

y

anouncement of discontinuity of time, enabled during last hour before discontinuity comes in eect:
` !'
announcement of start or end of daylight saving time
`A'
announcement of leap second insertion
``
(space, 20h) nothing announced



UTC
MEZ
`S'

Universal Time Coordinated, formerly GMT
European Standard Time, daylight saving disabled
MESZ European Summertime, daylight saving enabled

End-Of-Text, ASCII Code 03h

LANTIME M600 GPS PTP

Date: 27th October 2011

119

Page 120

16 Attachment: Technical Information

16.12.2 Format of the Meinberg Capture String
The Meinberg Capture String is a sequence of 31 ASCII characters terminated by a CR/LF (Carriage Return/Line
Feed) combination. The format is:
CHx_tt.mm.jj_hh:mm:ss.f 

The letters printed in italics are replaced by ASCII numbers whereas the other characters
are part of the time string. The groups of characters as dened below:
x
_

0 or 1 corresponding on the number of the capture input
ASCII space 20h

dd.mm.yy the capture date:
dd
day of month
mm
month
yy
year of the century

(01..31)
(01..12)
(00..99)

hh:mm:ss.f the capture time:
hh
hours
(00..23)
mm
minutes
(00..59)
ss
seconds
(00..59, or 60 while leap second)
f
fractions of second, 7 digits


Carriage Return, ASCII Code 0Dh



Line Feed, ASCII Code 0Ah

120

Date: 27th October 2011

LANTIME M600 GPS PTP

16.12 Time Strings

Page 121

16.12.3 Format of the SAT Time String
The SAT Time String is a sequence of 29 ASCII characters starting with the STX (start-of-text) character and
ending with the ETX (end-of-text) character. The format is:
dd.mm.yy/w/hh:mm:ssxxxxuv 

The letters printed in italics are replaced by ASCII numbers whereas the other characters
are part of the time string. The groups of characters as dened below:


Start-Of-Text, ASCII Code 02h
sending with one bit occuracy at change of second

dd.mm.yy

the current date:
dd
day of month
mm
month
yy
year of the century
w
the day of the week

(01..31)
(01..12)
(00..99)
(1..7, 1 = Monday)

hh:mm:ss

the current time:
hh
hours
mm
minutes
ss
seconds

(00..23)
(00..59)
(00..59, or 60 while leap second)

xxxx

time zone indicator:
`UTC`
Universal Time Coordinated, formerly GMT
`MEZ`
European Standard Time, daylight saving disabled
`MESZ'
European Summertime, daylight saving enabled

u

clock status characters:
`#'
clock has not synchronized after reset
``
(space, 20h) clock has synchronized after reset

v

anouncement of discontinuity of time, enabled during last hour
before discontinuity comes in eect:
` !'
announcement of start or end of daylight saving time
``
(space, 20h) nothing announced



Carriage Return, ASCII Code 0Dh



Line Feed, ASCII Code 0Ah



End-Of-Text, ASCII Code 03h

LANTIME M600 GPS PTP

Date: 27th October 2011

121

Page 122

16 Attachment: Technical Information

16.12.4 Format of the Uni Erlangen String (NTP)
The time string Uni Erlangen (NTP) of a GPS clock is a sequence of 66 ASCII characters starting with the STX
(start-of-text) character and ending with the ETX (end-of-text) character. The format is:
tt.mm.jj; w; hh:mm:ss; voo:oo; acdfg i;bbb.bbbbn lll.lllle hhhhm

The letters printed in italics are replaced by ASCII numbers whereas the other characters are part
of the time string. The groups of characters as dened below:


Start-Of-Text, ASCII Code 02h
sending with one bit occuracy at change of second

dd.mm.yy

the current date:
dd
day of month
mm
month
yy
year of
the century
w
the day of
the week

(01..31)
(01..12)
(00..99)
(1..7, 1 = Monday)

hh.mm.ss

the current time:
hh
hours
mm
minutes
ss
seconds

v

sign of the oset of local timezone related to UTC

oo:oo

oset of local timezone related to UTC in hours and minutes

ac

clock status characters:
a:
`#'
clock has not synchronized after reset
``
(space, 20h) clock has synchronized after reset
c:
``

(00..23)
(00..59)
(00..59, or 60 while leap second)

`*'
GPS receiver has not checked its position
(space, 20h) GPS receiver has determined its position

d

time zone indicator:
`S'
MESZ
``
MEZ

f

anouncement of discontinuity of time, enabled during last hour
before discontinuity comes in eect:
` !'
announcement of start or end of daylight saving time
``
(space, 20h) nothing announced

g

anouncement of discontinuity of time, enabled during last hour
before discontinuity comes in eect:
`A'
announcement of leap second insertion
``
(space, 20h) nothing announced

i

leap second insertion
`L'
leap second is actually inserted
(active only in 60th sec.)
``
(space, 20h) no leap second is inserted

bbb.bbbb

latitude of receiver position in degrees
leading signs are replaced by a space character (20h)

n

latitude, the following characters are possible:
`N'
north of equator

122

European Summertime, daylight saving enabled
European Standard Time, daylight saving disabled

Date: 27th October 2011

LANTIME M600 GPS PTP

16.12 Time Strings
`S'

Page 123
south d. equator

lll.llll

longitude of receiver position in degrees
leading signs are replaced by a space character (20h)

e

longitude, the following characters are possible:
`E'
east of Greenwich
`W'
west of Greenwich

hhhh

altitude above WGS84 ellipsoid in meters
leading signs are replaced by a space character (20h)



End-Of-Text, ASCII Code 03h

LANTIME M600 GPS PTP

Date: 27th October 2011

123

Page 124

16 Attachment: Technical Information

16.12.5 Format of the NMEA 0183 String (RMC)
The NMEA String is a sequence of 65 ASCII characters starting with the `$GPRMC' character and ending with
the characters CR (carriage return) and LF (line-feed). The format is:
$GPRMC,hhmmss.ss,A,bbbb.bb,n,lllll.ll,e,0.0,0.0,ddmmyy,0.0,a*hh

The letters printed in italics are replaced by ASCII numbers or letters where as the
other characters are part of the time string. The groups of characters as dened below:
$

Start character, ASCII Code 24h
sending with one bit occuracy at change of second

hhmmss.ss

the current time:
hh
hours
mm
minutes
ss
seconds
ss
fractions
of seconds

(00..23)
(00..59)
(00..59, or 60 while leap second)
(1/10 ; 1/100)

A

Status

(A = time data valid)
(V = time data not valid)

bbbb.bb

latitude of receiver position in degrees
leading signs are replaced by a space character (20h)

n

latitude, the following characters are possible:
`N'
north of equator
`S'
south d. equator

lllll.ll

longitude of receiver position in degrees
leading signs are replaced by a space character (20h)

e

longitude, the following characters are possible:
`E'
east of Greenwich
`W'
west of Greenwich

ddmmyy

the current date:
dd
day of month
mm
month
yy
year of
the century

(01..31)
(01..12)
(00..99)

a

magnetic variation

hh

checksum (EXOR over all characters except `$' and `*')



Carriage Return, ASCII Code 0Dh



Line Feed, ASCII Code 0Ah

124

Date: 27th October 2011

LANTIME M600 GPS PTP

16.12 Time Strings

Page 125

16.12.6 Format of the NMEA 0183 String (GGA)
The NMEA (GGA) String is a sequence of characters starting with the `$GPRMC' character and ending with the
characters CR (carriage return) and LF (line-feed). The format is:
$GPGGA,hhmmss.ss,bbbb.bbbbb,n,lllll.ll,e,A,vv,hhh.h,aaa.a,M,ggg.g,M0*cs 

The letters printed in italics are replaced by ASCII numbers or letters where as the
other characters are part of the time string. The groups of characters as dened below:
$

Start character, ASCII Code 24h
sending with one bit occuracy at change of second

hhmmss.ss

the current time:
hh
hours
mm
minutes
ss
seconds
ss
fractions
of seconds

A

Status

(00..23)
(00..59)
(00..59, or 60 while leap second)
(1/10 ; 1/100)

(A = time data valid)
(V = time data not valid)

bbbb.bbbbb latitude of receiver position in degrees
leading signs are replaced by a space character (20h)
n

latitude, the following characters are possible:
`N'
north of equator
`S'
south d. equator

lllll.lllll

longitude of receiver position in degrees
leading signs are replaced by a space character (20h)

e

longitude, the following characters are possible:
`E'
east of Greenwich
`W'
west of Greenwich

A

Position x (1 = yes, 0 = no)

vv

Satellites used (0..12)

hhh.h

HDOP (Horizontal Dilution of Precision)

aaa.h

Mean Sea Level altitude (MSL = altitude of WGS84 - Geoid Separation)

M

Units, meters (xed value)

ggg.g

Geoid Separation (altitude of WGS84 - MSL)

M

Units, meters (xed value)

cs

checksum (EXOR over all characters except `$' and `*')



Carriage Return, ASCII Code 0Dh



Line Feed, ASCII Code 0Ah

LANTIME M600 GPS PTP

Date: 27th October 2011

125

Page 126

16 Attachment: Technical Information

16.12.7 Format of the ABB SPA Time String
The ABB SPA Time String is a sequence of 32 ASCII characters starting with the characters
ending with the  (Carriage Return) character. The format is:

">900WD"

and

>900WD:yy-mm-tt_hh.mm;ss.f:cc 

The letters printed in italics are replaced by ASCII numbers whereas the other
characters are part of the time string. The groups of characters as dened below:
yy-mm-tt

the current date:
yy
year of the century
mm
month
dd
day of month
_

(00..99)
(01..12)
(01..31)

Space (ASCII code 20h)

hh.mm;ss.f the current time:
hh
hours
mm
minutes
ss
seconds
f
milliseconds

(00..23)
(00..59)
(00..59, or 60 while leap second)
(000..999)

cc

Check sum. EXCLUSIVE-OR result of the previous characters,
displayed as a HEX byte (2 ASCII characters 0..9 or A..F)



Carriage Return, ASCII Code 0Dh

126

Date: 27th October 2011

LANTIME M600 GPS PTP

16.12 Time Strings

Page 127

16.12.8 Format of the Computime Time String
The Computime time string is a sequence of 24 ASCII characters starting with the T character and ending with
the LF (line feed, ASCII Code 0Ah) character. The format is:
T:yy:mm:dd:ww:hh:mm:ss 

The letters printed in italics are replaced by ASCII numbers whereas the other
characters are part of the time string. The groups of characters as dened below:
T

Start character
sending with one bit occuracy at change of second

yy:mm:dd

the current date:
yy
year of the century
mm
month
dd
day of month
ww
the day of the week

(00..99)
(01..12)
(01..31)
(01..07, 01 = monday)

hh:mm:ss

the current time:
hh
hours
mm
minutes
ss
seconds

(00..23)
(00..59)
(00..59, or 60 while leap second)



Carriage Return, ASCII Code 0Dh



Line Feed, ASCII Code 0Ah

LANTIME M600 GPS PTP

Date: 27th October 2011

127

Page 128

16 Attachment: Technical Information

16.12.9 Format of the RACAL standard Time String
The RACAL standard Time String is a sequence of 16 ASCII characters terminated by a X (58h) character and
ending with the CR (Carriage Return, ASCII Code 0Dh) character. The format is:
yymmddhhmmss 

The letters printed in italics are replaced by ASCII numbers whereas the other
characters are part of the time string. The groups of characters as dened below:


Control character
sending with one bit
accuracy at change of second

code 58h



Control character

code 47h



Control character

code 55h

yymmdd

the current
yy
mm
dd

date:
year of the century
month
day of month

(00..99)
(01..12)
(01..31)

hh:mm:ss

the current
hh
mm
ss

time:
hours
minutes
seconds

(00..23)
(00..59)
(00..59, or 60 while leap second)



Carriage Return, ASCII code 0Dh

Interface
parameters:

7 Databits, 1 Stopbit, odd. Parity, 9600 Bd

128

Date: 27th October 2011

LANTIME M600 GPS PTP

16.12 Time Strings

Page 129

16.12.10 Format of the SYSPLEX-1 Time String
The SYSPLEX1 time string is a sequence of 16 ASCII characters starting with the SOH (Start of Header) ASCII
controll character character and ending with the LF (line feed, ASCII Code 0Ah) character. The format is:
ddd:hh:mm:ssq 

The letters printed in italics are replaced by ASCII numbers whereas the other
characters are part of the time string. The groups of characters as dened below:


Start of Header (ASCII control character)
sending with one bit accuracy at change of second

ddd

day of year

hh:mm:ss

the current time:
hh
hours
mm
minutes
ss
seconds
q
Quality
indicator

(001..366)
(00..23)
(00..59)
(00..59, or 60 while leap second)
(space) Time Sync (GPS lock)
(?) no Time Sync (GPS fail)



Carriage-return (ASCII code 0Dh)



Line-Feed (ASCII code 0Ah)

LANTIME M600 GPS PTP

Date: 27th October 2011

129

Page 130

16 Attachment: Technical Information

16.13 Manual VP100/NET Display configuration
send2display Version 0.1

usage: send2display -h hostname -s serialnumber [options]
Valid options are:
-h,
-s,
-c,
-b,
-a,
-m,
-e,
-q,
-v,
-?,

host H
Uses H as the hostname of the display unit
serialnumber S Uses S as the serialnumber of the display (e.g. 03A00C7F)
clear M
Clear message M (0-31)
beep
Beeper sound while showing the message
clearall
Clear all messages of the display
message M
Create/change message M (0-31, default = 0)
executions E
Sets number of consecutive executions to E (1-9, default = 1)
quiet
Quiet mode (no program output to stdout/stderr)
verbose
Verbose mode (output of debugging info on stdout)
help
Show help message

Dening messages

a)

Static or ashing text:
You can dene a maximum of 9 lines for a message.
Start with -(x) "text", where (x) represents the line number.
-1,
line1 "text"
Set text for line 1
-2,
line2 "text"
Set text for line 2
...
You can set the duration and mode for each line separately. Speciy the following
options directly after the text-denition of a line:
-f,
-d,

b)

noash
duration X

Change line mode to static (default is ashing)
Set the duration of the line to x seconds (default is 3 seconds)

Scrolling text:
You can dene a maximum of 241 characters per scrolling message. If you want the message
to "softly" end, simply add some spaces to the end of your text (attention: text and
spaces must be no more than 241 chars in length).
-t,

scrolltext "text"

Set scrolltext

If you want the message (any type) to appear periodically, you can set the time interval with:
-D,
-H,
-M,

periodday D
periodhour H
periodminute M

Display message every D days
Display message every H hours
Display message every M minutes

(You can combine these options. Default is: message is displayed only once)
Possible error codes: 1=parameter error, 2=no ACK from display, 3=network error

Examples:

send2display -h 172.16.3.251 -s 0a03007f -m1 -e2 -1"Hello World" -d5 -2"what a nice day" -d3
(shows two lines of text (2 times), 1st line is shown for 5 seconds and 2nd line for 3 seconds)
send2display -h 172.16.3.251 -s 0a03007f -m1 -e1 -1"Oops" -H2 -M30
(shows one line of text every 2 hours and 30 minutes, a sound (beep)
can be heared while the message is displayed)
send2display -h 172.16.3.251 -s 0a03007f -c1

130

Date: 27th October 2011

LANTIME M600 GPS PTP

16.14 Global Conguration File

Page 131

(deletes the message 1, so no more beeps every 2:30 hrs ...)
send2display -h 172.16.3.251 -s 0a03007f -t"Hello world..." -e3
(shows a scrolling message with soft end, repeating it 3 times

16.14 Global Configuration File
This le contains all global parameters of the LANTIME. You can nd this le on the write protected ash disk
at /mnt/ash/global_conguration:
##
# Conguration File #
##
# Conguration File Section
Conguration File Version Number:
Conguration File Last Change:

4.17

# Network Parameter Section
Hostname
Domainname
Default IPv4 Gateway
Default IPv6 Gateway
Nameserver 1
Nameserver 2
Syslogserver 1
Syslogserver 2
Telnet Port active
FTP Port active
SSH active
HTTP active
HTTPS active
SNMP active
SAMBA active
IPv6 active

[ASCII,50]
[ASCII,50]
[IP]
[IP]
[IP]
[IP]
[ASCII,50]
[ASCII,50]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

# NTP Section
External NTP Server 1 IP
External NTP Server 1 KEY
External NTP Server 1 AUTOKEY
External NTP Server 2 IP
External NTP Server 2 KEY
External NTP Server 2 AUTOKEY
External NTP Server 3 IP [ASCII,50]
External NTP Server 3 KEY
External NTP Server 3 AUTOKEY
NTP Stratum Local Clock
NTP Trusted Key
NTP AUTOKEY feature active
NTP ATOM PPS active
NTP Broadcast TCPIP
NTP Broadcast KEY
NTP Broadcast AUTOKEY
NTP Trust Time

[ASCII,50]
[NUM]
[BOOL]
[ASCII,50]
[NUM]
[BOOL]
:
[NUM]
[BOOL]
[NUM,0..15]
[NUM]
[BOOL]
[BOOL]
[IP]
[NUM]
[BOOL]
[NUM]

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

# EMail Section
EMail To Address
EMail From Address
EMail Smarthost

[ASCII,50]
[ASCII,50]
[ASCII,50]

:
:
:

LANTIME M600 GPS PTP

LanGpsV4
py.meinberg.de

1
1
1
1
1
1
0
1

12
0
1
0
0
0

Date: 27th October 2011

131

Page 132

132

16 Attachment: Technical Information

# SNMP Section
SNMP Trap Receiver Address 1
SNMP Trap Receiver Community 1
SNMP Trap Receiver Address 2
SNMP Trap Receiver Community 2
SNMP V3 User Name
SNMP Read Community String
SNMP Write Community String
SNMP Contact String
SNMP Location String

[ASCII,50]
[ASCII,50]
[ASCII,50]
[ASCII,50]
[ASCII,50]
[ASCII,50]
[ASCII,50]
[ASCII,50]
[ASCII,50]

:
:
:
:
:
:
:
:
:

# Windows Messages Section
WMail Address 1
WMail Address 2

[ASCII,50]
[ASCII,50]

:
:

# VP100 Display Section
VP100 Display Address 1
VP100 Display Sernum 1
VP100 Display Address 2
VP100 Display Sernum 2

[ASCII,50]
[ASCII,50]
[ASCII,50]
[ASCII,50]

:
:
:
:

# Notication Section
Notication on NTP_not_sync
Notication on NTP_stopped
Notication on Server_boot
Notication on Refclock_not_respon.
Notication on Refclock_not_sync
Notication on Antenna_faulty
Notication on Antenna_reconnect
Notication on Cong_changed
Notication on Leap second announ.

[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]

:
:
:
:
:
:
:
:
:

# Ethernet Parameter Section
ETH0 IPv4 TCPIP address
ETH0 IPv4 NETMASK
ETH0 DHCP CLIENT
ETH0 IPv6 TCPIP address 1
ETH0 IPv6 TCPIP address 2
ETH0 IPv6 TCPIP address 3
ETH0 IPv6 Autoconf
ETH0 Net Link Mode
ETH0 Bonding Group

[IP]
[IP]
[BOOL]
[IP]
[IP]
[IP]
[BOOL]
[NUM,0:4]
[NUM,0:4]

:
:
:
:
:
:
:
:
:

root
public
Meinberg
Germany

0
0
1

1

Date: 27th October 2011

LANTIME M600 GPS PTP

16.15 Global Option File

Page 133

16.15 Global Option File
This le contains all global options for special hardware conguration of the LANTIME. Do not modify this le.
You can nd this le on the write protected ash disk at /mnt/ash/global_options:

#GLOBAL OPTIONS
NUMBER ETHERNET INTERFACES
SYSTEM LAYOUT
SYSTEM ADV LAYOUT
SYSTEM LANGUAGE
SYSTEM PARAMETER
SYSTEM DESIGN

:
:
:
:
:
:

1
0
0
0
server
0

16.16 Third party software
The LANTIME network timeserver is running a number of software products created and/or maintained by open
source projects. A lot of people contributed to this and we explicitly want to thank everyone involved for her/his
great work.
The used open source software comes with its own license which we want to mention below. If one of the
licenses for a third party software product is violated, we will as soon as possible apply any changes needed in
order to conform with the corresponding license after we acknowledged about that violation.
If a license for one of the software products states that we have to provide you with a copy of the source
code or other material, we will gladly send it to you on data media via normal post or by e-mail upon request.
Alternatively we can provide you with a link to a download location in the internet, allowing you to download the
most actual version. Please note that we have to charge you for any incurred expenses if you choose to receive
the source code on data media.

16.16.1 Operating System GNU/Linux
The distribution of the GNU/Linux operating system is covered by the GNU General Public License (GPL), which
we included below.
More information about GNU/Linux can be found on the GNU website
www.gnu.org
and on the website of GNU/Linux
www.linux.org

16.16.2 Samba
The Samba software suite is a collection of programs, which implement the Server Message Block (SMB) protocol
for UNIX systems. By using Samba your Lantime is capable of sending Windows popup messages and serves
request for network time by clients using the NET TIME command.
The distribution of Samba is covered  like GNU/Linux  by the GNU General Public License, see below.
The website of the Samba project (or a mirror) can be reached at
www.samba.org

16.16.3 Network Time Protocol Version 4 (NTP)
The NTP project, lead by David L. Mills, can be reached in the internet at www.ntp.org. There you will nd
a wealthy collection of documentation and information covering all aspects of the application of NTP for time

LANTIME M600 GPS PTP

Date: 27th October 2011

133

Page 134

16 Attachment: Technical Information

synchronization purposes. The distribution and usage of the NTP software is allowed, as long as the following
notice is included in our documentation:
*************************************************************************
*
*
* Copyright (c) David L. Mills 1992-2004
*
*
*
* Permission to use, copy, modify, and distribute this software
*
* and its documentation for any purpose and without fee is hereby
*
* granted, provided that the above copyright notice appears in all
*
* copies and that both the copyright notice and this permission
*
* notice appear in supporting documentation, and that the name
*
* University of Delaware not be used in advertising or publicity
*
* pertaining to distribution of the software without specic,
*
* written prior permission. The University of Delaware makes no
*
* representations about the suitability this software for any
*
* purpose. It is provided "as is" without express or implied
*
* warranty.
*
*
*
*************************************************************************

16.16.4 mini httpd
For our web based conguration tool (HTTP and HTTPS) we use mini_httpd from ACME Labs. The distribution
and usage of this program is free provided as long as the following notice appears in the documentation:

Copyright c 2000 by Jef Poskanzer (jef@acme.com). All rights reserved.
Redistribution and use in source and binary forms, with or without
modication, are permitted provided that the following conditions
are met:
1.

Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

2.

Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS AS IS AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Find out more regarding mini_httpd at the ACME Labs homepage:
www.acme.com

16.16.5 GNU General Public License (GPL)
Version 2, June 1991 - Copyright (C) 1989, 1991
Free Software Foundation, Inc.

134

Date: 27th October 2011

LANTIME M600 GPS PTP

16.16 Third party software

Page 135

675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not
allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast,
the GNU General Public License is intended to guarantee your freedom to share and change free softwareto
make sure the software is free for all its users. This General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to using it. (Some other Free Software
Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your
programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service
if you wish), that you receive source code or can get it if you want it, that you can change the software or use
pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask
you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies
of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And
you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) oer you this license which gives
you legal permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there
is no warranty for this free software. If the software is modied by someone else and passed on, we want its
recipients to know that what they have is not the original, so that any problems introduced by others will not
reect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that
redistributors of a free program will individually obtain patent licenses, in eect making the program proprietary.
To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modication follow.
GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING,
DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder
saying it may be distributed under the terms of this General Public License. The "Program", below, refers to
any such program or work, and a "work based on the Program" means either the Program or any derivative work
under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with
modications and/or translated into another language. (Hereinafter, translation is included without limitation in
the term "modication".) Each licensee is addressed as "you".
Activities other than copying, distribution and modication are not covered by this License; they are outside
its scope. The act of running the Program is not restricted, and the output from the Program is covered only if
its contents constitute a work based on the Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium,
provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and
give any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option oer warranty

LANTIME M600 GPS PTP

Date: 27th October 2011

135

Page 136

16 Attachment: Technical Information

protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on
the Program, and copy and distribute such modications or work under the terms of Section 1 above, provided
that you also meet all of these conditions:
a) You must cause the modied les to carry prominent notices stating that you changed the les and the
date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived
from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms
of this License.
c) If the modied program normally reads commands interactively when run, you must cause it, when started
running for such interactive use in the most ordinary way, to print or display an announcement including an
appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty)
and that users may redistribute the program under these conditions, and telling the user how to view a copy of
this License. (Exception: if the Program itself is interactive but does not normally print such an announcement,
your work based on the Program is not required to print an announcement.)
These requirements apply to the modied work as a whole. If identiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then
this License, and its terms, do not apply to those sections when you distribute them as separate works. But when
you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the
whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and
thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather,
the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work
based on the Program) on a volume of a storage or distribution medium does not bring the other work under the
scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed
under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written oer, valid for at least three years, to give any third party, for a charge no
more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily
used for software interchange; or,
c) Accompany it with the information you received as to the oer to distribute corresponding source code.
(This alternative is allowed only for noncommercial distribution and only if you received the program in object
code or executable form with such an oer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modications to it. For an
executable work, complete source code means all the source code for all modules it contains, plus any associated
interface denition les, plus the scripts used to control compilation and installation of the executable. However,
as a special exception, the source code distributed need not include anything that is normally distributed (in either
source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which
the executable runs, unless that component itself accompanies the executable.
If distribution of executable or object code is made by oering access to copy from a designated place, then
oering equivalent access to copy the source code from the same place counts as distribution of the source code,
even though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this

136

Date: 27th October 2011

LANTIME M600 GPS PTP

16.16 Third party software

Page 137

License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you
under this License will not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants
you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law
if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on
the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying,
distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically
receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and
conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not
limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that
contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations,
then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit
royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance
of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or
to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free
software distribution system, which is implemented by public license practices. Many people have made generous
contributions to the wide range of software distributed through that system in reliance on consistent application
of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any
other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this
License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit
geographical distribution limitation excluding those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this
License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License from
time to time. Such new versions will be similar in spirit to the present version, but may dier in detail to address
new problems or concerns.
Each version is given a distinguishing version number. If the Program species a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either
of that version or of any later version published by the Free Software Foundation. If the Program does not specify
a version number of this License, you may choose any version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions
are dierent, write to the author to ask for permission. For software which is copyrighted by the Free Software
Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be
guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the
sharing and reuse of software generally.
NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED

LANTIME M600 GPS PTP

Date: 27th October 2011

137

Page 138

16 Attachment: Technical Information

IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.
SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM
TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS

138

Date: 27th October 2011

LANTIME M600 GPS PTP

16.17 Reference

Page 139

16.17 Reference
[Mills88]

Mills, D. L., "Network Time Protocol (Version 1) - specication and implementation",
DARPA Networking Group Report RFC-1059, University of Delaware, July 1988

[Mills89]

Mills, D. L., "Network Time Protocol (Version 2) - specication and implementation",
DARPA Networking Group Report RFC-1119, University of Delaware, September 1989

[Mills90]

Mills, D. L., "Network Time Protocol (Version 3) - specication, implementation and analysis",
Electrical Engineering Department Report 90-6-1, University of Delaware, June 1989
Kardel, Frank, "Gesetzliche Zeit in Rechnernetzen", Funkuhren, Zeitsignale und Normalfrequenzen,
Hrsg. W. Hilberg, Verlag Sprache und Technik, Groÿ-Bieberau 1993
Kardel, Frank, "Verteilte Zeiten", ix Multiuser-Multitasking-Magazin, Heft 2/93,
Verlag Heinz Heise, Hannover 1993

LANTIME M600 GPS PTP

Date: 27th October 2011

139

Konformitätserklärung
Declaration of Conformity

Hersteller
Manufacturer

Meinberg Funkuhren GmbH & Co. KG
Lange Wand 9
D-31812 Bad Pyrmont

erklärt in alleiniger Verantwortung, daß das Produkt
declares under its sole responsibility, that the product

Produktbezeichnung

PTP Timeserver

Product Name

Modell / Typ

Lantime M600/GPS/PTP

Model Designation

auf das sich diese Erklärung bezieht, mit den folgenden Normen übereinstimmt
to which this declaration relates is in conformity with the following standards

EN55022:1998, Class B
(+A1:2000 +A2:2003)

Grenzwerte und Meßverfahren für Funkstörungen von
informationstechnischen Einrichtungen
Limits and methods of measurement of radio interference characteristics of
information technology equipment

EN55024:1998
(+A1:2001 +A2:2003)

Grenzwerte und Meßverfahren für Störfestigkeit von
informationstechnischen Einrichtungen
Limits and methods of measurement of Immunity characteristics of
information technology equipment

EN 60950-1:2001

Sicherheit von Einrichtungen der Informationstechnik

(+A11:2004)

Safety of information technology equipment

gemäß den Richtlinien 2004/108/EG (Elektromagnetische Verträglichkeit), 2006/95/EG (Niederspannungsrichtlinie) und 93/68/EWG (CE Kennzeichnung) sowie deren Ergänzungen.
following the provisions of the directives 2004/108/EC (electromagnetic compatibility), 2006/95/EC (low voltage directive) and
93/68/EEC (CE marking) and its amendments.

Bad Pyrmont, den 03.07.2009



File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : No
Page Count                      : 146
Page Mode                       : UseOutlines
Author                          : 
Title                           : 
Subject                         : 
Creator                         : LaTeX with hyperref package
Producer                        : pdfTeX-1.40.10
Create Date                     : 2011:10:27 15:15:14+02:00
Modify Date                     : 2011:10:27 15:15:14+02:00
Trapped                         : False
PTEX Fullbanner                 : This is pdfTeX, Version 3.1415926-1.40.10-2.2 (TeX Live 2009/Debian) kpathsea version 5.0.0