Meinberg TCR LANTIME User Manual
Technical Information
Operating Instructions
LANTIME / TCR
ETX 1HE
Contact Information
Meinberg Funkuhren GmbH & Co. KG
Auf der Landwehr 22
D-31812 Bad Pyrmont
Telephone: +49 (0) 52 81 / 9309-0
Telefax: +49 (0) 52 81 / 9309-30
Internet: http://www.meinberg.de
E-Mail: info@meinberg.de
Bad Pyrmont, 14. November 2006
Table of Contents
Quick Start..................................................................................................................... 8
Network Timeserver with TCR synchronized time base...............................................9
The Modular System LANTIME.................................................................................10
Supported Network Services.............................................................................. 11
Additional Features and Options........................................................................ 12
User Interface..................................................................................................... 12
Options............................................................................................................... 12
Why to use a Network Timeserver.....................................................................13
Network Time Protocol (NTP).................................................................................... 13
NTP Target......................................................................................................... 14
NTP-Client Installation...................................................................................... 14
IRIG receiver TCR510.................................................................................................16
Description of IRIG-Codes...................................................................................... 16
IRIG-Standard format.............................................................................................. 17
AFNOR-Standard format.........................................................................................18
Overview..................................................................................................................18
Function principle.................................................................................................... 19
Input Signals............................................................................................................ 20
Input for unmodulated codes................................................................................... 20
Input for modulated codes....................................................................................... 21
Input impedance.......................................................................................................21
Booting the Single Board Computer............................................................................22
Configuration User Interface....................................................................................... 23
The Front Panel Layout........................................................................................... 24
TCR Status LEDs............................................................................................... 24
LC Display......................................................................................................... 24
MENU Key.........................................................................................................24
CLR/ACK Key................................................................................................... 24
NEXT Key..........................................................................................................24
INC Key..............................................................................................................24
Configuration via LC Display..................................................................................25
The menus in Detail................................................................................................. 26
Root Menu..........................................................................................................26
Menu IRIG state................................................................................................. 26
IRIG system state: Bit 7 ... 0.............................................................................. 27
IRIG system configuration Bit 2 ... 0................................................................. 27
Menu Reference Clock State....................................................................................28
Menu SETUP..................................................................................................... 28
SETUP LAN PARAMETERS........................................................................... 29
SETUP TCR PARAMETERS............................................................................29
The LANTIME configuration interfaces..................................................................... 31
The web interface.........................................................................................................32
Configuration:Main Menu....................................................................................... 33
Configuration: Ethernet........................................................................................... 34
Network interface specific configuration.................................................................36
IPv4 addresses and DHCP..................................................................................36
IPv6 addresses and autoconf.............................................................................. 36
High Availability Bonding................................................................................. 37
Additional Network Configuration.....................................................................38
Configuration: Notification......................................................................................39
Alarm events.......................................................................................................40
E-mail messages................................................................................................. 40
Windows Popup Messages.................................................................................41
SNMP-TRAP messages..................................................................................... 41
VP100/NET wall mount display........................................................................ 41
User defined Alarm scripts.................................................................................42
Alarm messages..................................................................................................42
Configuration: Security............................................................................................43
Password.............................................................................................................44
HTTP Access Control.........................................................................................44
SSH Secure Shell Login..................................................................................... 45
Generate SSL Certificate for HTTPS ................................................................ 46
NTP keys and certificates...................................................................................47
SNMP Parameter................................................................................................47
Configuration: NTP................................................................................................. 48
NTP Authentication............................................................................................51
NTP AUTOKEY................................................................................................ 53
Configuration: Local................................................................................................56
Administrative functions.................................................................................... 57
User Management...............................................................................................58
Administrative Information................................................................................ 59
Software Update................................................................................................. 60
Automatic configuration check.......................................................................... 61
Get Diagnostics Information.............................................................................. 62
Web interface language...................................................................................... 62
Configuration: Statistics.......................................................................................... 63
Statistical Information........................................................................................ 64
Configuration: Manual.............................................................................................65
The Command Line Interface...................................................................................... 67
CLI Ethernet.............................................................................................................68
CLI Notification.......................................................................................................71
Alarm events.......................................................................................................71
E-mail messages................................................................................................. 72
Windows Popup Messages.................................................................................73
SNMP-TRAP messages..................................................................................... 73
VP100/NET wall mount display........................................................................ 73
CLI Security.............................................................................................................74
Password.............................................................................................................74
SSH Secure Shell Login..................................................................................... 74
Generate SSL Certificate for HTTPS ................................................................ 75
NTP keys and certificates...................................................................................75
CLI NTP Parameter................................................................................................. 76
CLI NTP Authentication.................................................................................... 77
CLI NTP Autokey.............................................................................................. 77
CLI Local................................................................................................................. 78
Administrative functions.................................................................................... 78
User Management...............................................................................................79
Administrative information................................................................................ 79
Software Update................................................................................................. 80
SNMP Support.............................................................................................................81
Configuration over SNMP ...................................................................................... 83
Examples for the usage of the SNMP configuration features............................ 84
Further configuration possibilities......................................................................85
Send special timeserver commands with SNMP................................................85
Configuration of the timeserver with SNMP: Reference................................... 87
SNMP Traps.............................................................................................................90
SNMP Trap Reference....................................................................................... 91
Attachment: Technical Information.............................................................................92
Skilled/Service-Personnel only: Replacing the Lithium Battery............................. 92
Technical Specifications LANTIME Multipac........................................................92
Safety instructions for building-in equipment......................................................... 93
CE-Label.................................................................................................................. 93
Rear Panel Connectors.............................................................................................94
Rear View LANTIME............................................................................................. 95
Technical Specifications TCR510........................................................................... 96
Signal description TCR510................................................................................ 98
Rear Connector Pin Assignments TCR510........................................................ 99
Technical Specifications LAN CPU...................................................................... 100
Rear Connector Pin Assignments LAN CPU...................................................101
VGA, Keyboard Connector Pin Assignments.................................................. 101
Technical Specifications Power Supply.................................................................102
Time Strings...........................................................................................................103
Format of the Meinberg Standard Time String................................................ 103
Format of the GPS167 Capture String............................................................. 104
Format of the SAT-Time String....................................................................... 105
Format of the Uni Erlangen String (NTP) .......................................................106
Format of the NMEA 0183 String (RMC)....................................................... 108
Format of the ABB SPA Time String.............................................................. 109
Format of the COMPUTIME Time String....................................................... 110
Menu Quick Reference.......................................................................................... 111
Declaration of Conformity.....................................................................................112
Manual VP100/NET Display configuration.......................................................... 113
Global Configuration File...................................................................................... 115
Global Option File................................................................................................. 116
Third party software...............................................................................................117
Operating System GNU/Linux.........................................................................117
Samba............................................................................................................... 117
Network Time Protocol Version 4 (NTP)........................................................ 118
mini_httpd........................................................................................................ 118
GNU General Public License (GPL)................................................................119
Timecode (option)..................................................................................................123
Abstract.............................................................................................................123
Principle of Operation...................................................................................... 123
Block Diagram Timecode.................................................................................123
IRIG Standard Format...................................................................................... 124
AFNOR Standard Format.................................................................................125
Assignment of CF Segment in IEEE1344 Code.............................................. 126
Generated Time Codes..................................................................................... 127
Selection of Generated Time Code...................................................................127
Outputs............................................................................................................. 128
AM - Sine Wave Output...................................................................................128
PWM DC Output..............................................................................................128
Technical Data..................................................................................................128
USB Stick.............................................................................................................. 129
Menu Structure................................................................................................. 129
Menu Configuration Files................................................................................ 130
Menu Script Files............................................................................................. 131
Keypad locking.................................................................................................131
Reference............................................................................................................... 132
Quick Start
TCR: no data available Wed, 18.11.2003
NTP: Not Sync UTC 10:03:30
TCR: NORMAL OPERATION Wed, 18.11.2003
NTP: Not Sync UTC 10:04:10
SETUP: T CR PARAMETERS
IRIG CODE: B122/B123
Are you sure ? Press ...
INC -> YES MENU -> NO
- Approximately one minute after power up no display will be shown. After that the
current state of the TCR receiver and the NTP will be displayed.
==>
- If the TCR receiver remains asynchronous (FAIL LED is still on after 1 minute)
the selected IRIG code and the cable (Input Impedance) are to check. Press
MENU 3 times to enter SETUP menu and then NEXT to enter TCR PARAMETERS. Then press CLR/ACK and then NEXT to display the current selected
IRIG-CODE:
- Enter TCP/IP address, netmask and default gateway:
- Press Menu three times to enter the LAN PARAMETERS setup menu
- Press CLR/ACK to see the TCP/IP address first
- Press CLR/ACK once again to be able to enter the IPv4 TCP/IP address
- With NEXT the respective digit is to select while INC is used to set the value
- To take over the changes it is necessary to press CLR/ACK again
- A wildcard '*' is displayed to confirm the changes
- Pressing NEXT, the netmask and the default gateway can be entered in the
same way.
- Pressing MENU following by INC causes the changes to become active
NOTE: All settings are related to the first Ethernet connection (ETH0).
After this all further settings can be done via network interface, either by using a
WEB browser or a Telnet Session.
Default user: root
Default password: timeserver
8
Network Timeserver with TCR synchronized time base
LANTIME (Local Area Network Timeserver) provides a high precision time base
to a TCP/IP network (Stratum-1-Server). The NTP (Network Time Protocol) is used
to synchronize all NTP clients with the reference. The several LANTIME variants
differ from each other by the time reference. A GPS receiver, a DCF77 receiver or an
IRIG time code receiver can be integrated as an internal reference as well as a
combination of these references (hybrid system). External references are also
possible. LANTIME/TCR is a set of equipment composed of a IRIG Time Code
Receiver TCR510, a single-board computer with integrated network board and a
power supply, all installed in a metal 19" modular chassis and ready to operate. A
simplified LINUX operating system is installed on the single-board computers flash
disk. Four push buttons and a 2 x 40 character LC display can be used to configure
and monitor the time server. After the network connection has been established the
time server can also be configured and monitored remotely from a workstation via
TELNET or FTP. An integrated HTTP server enables access to the LANTIME by
using an ordinary WEB browser.
9
The Modular System LANTIME
LANTIME is a set of equipment composed of a IRIG Time Code Receiver
TCR510, a single-board computer SBC GEODE 266 MHz with integrated network
card, and a power supply unit T60B, all installed in a metal desktop case and ready to
operate. The interfaces provided by LANTIME are accessible via connectors in the
front panel of the case. Details of the components are described below.
Front View LANTIME/TCR
The implemented NTPD distributes the reference time from the IRIG Time Code
Receiver cyclic in the network. Information on the NTPD is monitored on the LC
display or can be inquired via the network.
The installation of LANTIME is very easy for the system/network administrator. The
network address, the netmask and the default gateway have to be configured from a
terminal program connected to the serial terminal on the front panel. The network
address or the equivalent name of LANTIME has to be shown to all NTP clients in
the TCP/IP network.
As well as NTP the Linux system also supports a number of further network
protocols: HTTP(S), FTP, SSH and Telnet. Because of this remote configuration or
status requests can come from any WEB browser. This access via the network can be
deactivated. Changes in the receiver status, errors or other important events are
logged either on the local Linux system or on an external SYSLOG-Server. In
addition messages can be sent to a data center via SNMP traps or automatically
generated e-mails where they can be recorded. Furthermore all alarm messages can be
displayed by the large display VP100/20/NET that is accessed via network
connection. In order to avoid a service interruption several LANTIME NTP servers
can be installed in the same network to obtain redundancy.
10
Supported Network Services
The following network services are provided via RJ45 10/100Base-T Ethernet (Auto
sensing):
- NTP v2, v3, v4
- NTP broadcast mode
- NTP multicast
- NTP symmetric keys
- NTP Autokey
- Simple Network Time Protocol (SNTP)
- TIME
- SNMP v1,2,3 with extended SNMP-Agent and SNMP-Traps for NTP and reference clock status
- DHCP Client
- NFS
- TELNET
- FTP
- HTTP
- HTTPS with Openssl2
- SSH2 Secure Shell Login
- Alarm messages via e-mail
- IPv6
- 3 global IPv6 addresses configurable
- Autoconf Feature to be disabled
- supported network services: NTP, HTTP, HTTPS, SNMP, SSH
- Windows „net time“ via NETBIOS
- Winpopup (Window Mail)
11
Additional Features and Options
- external NTP timeserver
- free configuration of NTP: thereby MD5 authentication and access control via address & mask restriction
- extended menu guidance for configuration and monitoring via Telnet, SSH or
serial terminal interface
- optional up to 3 RJ45/10/100 Mbit Ethernet interfaces
- extended HTTP statistic support with long-term graphic and access statistic to
NTP
- alarm messages can be displayed on external large display VP100/20/NET
- USB memory stick slot for extended functionality: software update, transfer of
secure certificates, log files and configurations, keypad locking
User Interface
- terminal connection via serial interface, status LED
- Web browser interface with graphical statistic of the one-day cycle offsets
- Telnet or Secure Shell Login for password protected operation of the Linux operating system
- FTP access for updating the operating system and downloading log files
- Simple Network Management Protocol for automatically SNMP-Traps in case of
alarm
- SYSLOG messages can be passed to different computers
- configurable e-mail notification
- Simulation of a synchronous radio clock in order to operate without antenna
Options
- up to two further Ethernet RJ45 connectors
- Frequency and pulse outputs via BNC connectors (e.g. 10 MHz, 2.048 MHz, PPS)
- higher free running accuracy with optional oscillators (OCXO)
- IRIG-B outputs
- ANZ14/NET or VP100/20/NET as display connected via network
12
Why to use a Network Timeserver
A network timeserver should be used if accurate time is essential for undisturbed
operation. It is possible to synchronize computers in a network using Public Domain
Time servers over the Internet, but there are good reasons not to use them:
- The possibility to send notification via e-mail or SNMP-Trap to an administrator
in the event of any synchronisation failure.
- The computers in the network do not have a reliable internet connection.
- The computers in the network cannot rely on the availability of external timeservers. Most operators of these timeservers do not guarantee continuous availability nor the accuracy of their service.
- NTP is able to compensate for the propagation delay of the network packets only
in case of “usual” internet traffic. However, if unforeseen occurrences cause
badly fluctuating propagation times, it is possible that the time synchronisation
is disturbed. Reasons for this may be: hacker attacks, numerous upcoming new
viruses etc.
- An own timeserver cannot be easily compromised by external sources.
Network Time Protocol (NTP)
NTP is a common method for synchronization of hardware clocks in local und
global networks. The basic concept, version 1 [Mills88], was published in 1988 as
RFC (Request For Comments). Experiences made from the practical use in Internet
was followed by version 2 [Mills89]. The software package NTP is an
implementation of the actual version 3 [Mills90], based on the specification RFC1305 from1990 (directory doc/NOTES). Permission to use, copy, modify and
distribute this software for any purpose and without fee is hereby granted (read File
COPYRIGHT).
NTP's way of operation is basically different from that of most other protocols. NTP
does not synchronize all connected clocks, it forms a hierarchy of timeservers and
clients. A level in this hierarchy is called a stratum, and Stratum-1 is the highest level.
Timeservers of this level synchronize themselves by a reference time source, such as
a radio controlled clock, GPS-receiver or modem time distribution. Stratum-1-Servers
distribute their time to several clients in the network which are called Stratum-2.
A high precision synchronization is feasible because of the several time references.
Every computer synchronizes itself by up to three valued time sources. NTP enables
the comparison of the hardware times and the adjustment of the own clock. A time
precision of 128 ms, often better than 50 ms, is possible.
13
NTP Target
The software package NTP was tested on different UNIX systems. Many UNIX
systems have pre-installed a NTP client. Only some configurations have to be made
(/etc/ntp.conf - see NTP Client Installation). NTP clients as freeware or shareware are
also available for the most other operating systems like Windows
XP/2000/NT/95/98/3x, OS2 or MAC. The following WEB site is recommended to
get the latest version of NTP: "http://www.eecis.udel.edu/~ntp/". More information
you can find on our web page at "http://www.meinberg.de/english/sw/ntp.htm".
NTP-Client Installation
The following example shows the installation of a NTP client under UNIX. First
make sure that there is no NTP installed on your computer because many UNIX
operating systems include NTP already.
The shipped source code of the NTP daemon has to be compiled on the target system.
Using the enclosed script file configures the compilation of the NTP daemon and all
tools.
configure
All necessary information from the system will be collected and the corresponding
make files will be generated in the subdirectories.
After that the NTP daemon and all needed utilities will be generated. Therefore type:
make
While compiling the NTP daemon several warnings may appear. These warnings are
mostly unimportant. In case of problems during the compilation read the system
dependent notes in the subdirectory ‘html’.
Afterwards the generated programs and tools have to be moved in the corresponding
directories. Therefore type:
make install
The time adjustment can occur in different ways. Either the system time can be set
once by using the tool "ntpdate lantime" or the NTPD daemon is started. In the first
case it is recommended to set the time automatically with "cron" or once when
booting the system. The second case is described below.
First a file named /etc/ntp.conf has to be generated with an editor. Adapting the file to
Meinberg LANTIME it should contain the following:
# Example for /etc/ntp.conf for Meinberg LANTIME
server 127.127.1.0 # local clock
server 172.16.3.35 # TCPIP address of LANTIME
# optional: Driftfile
# driftfile /etc/ntp.drift
# optional: activate all messages in syslogfile
# logconfig =all
14
The NTP daemon is started with "ntpd" or, using "rc.local", while booting the system.
Status messages during operation are saved in /var/adm/messages and /
var/adm/syslog (corresponding to the syslog configuration).
e.g.: tail /var/log/messages
shows the last lines from the file "messages"
The status messages can also be redirected in a log file by using the following option:
ntpd -llogfile
The command "ntpq" in the directory "ntpq" requests the actual status of the NTP
daemon (see also doc/ntpq.8).
e.g.: ntpq/ntpq
An interpreter appears; Type "?" for a list of all available commands. The command
"peer" is used to list all active reference clocks:
remote refid st t when poll reach delay offset jitter
================================================================================
LOCAL(0) LOCAL(0) 3 l 36 64 3 0.00 0.000 7885
lantime .GPS. 0 l 36 64 1 0.00 60.1 15875
with the following meaning:
- remote: list of all valid time servers (ntp.conf)
- refid: reference number
- st: actual stratum value (hierarchy level)
- when: last request (seconds)
- poll: period of requesting the time server (seconds)
- reach: octal notation of the successful requests, shifted left
- delay: delay of the network transmission (milliseconds)
- offset: difference between system time and reference time
(milliseconds)
- jitter: variance of the offsets (milliseconds)
Repeatedly "peer" commands lets the user observe the accuracy of the NTP daemon.
Every 64 seconds (value of -poll) a new time string is red in from the radio clock. The
NTP daemon needs approx. 3...5 minutes for initialisation. This is indicated by a
wildcard (*) on the left side of the remote name.
The NTP daemon terminates itself if the system time differs from the UTC time by
more than 1024 seconds. This often happens when the time zone is not correctly set
(see also system manual "zic" or "man zic").
15
IRIG receiver TCR510
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 definition of time code formats was completely arbitrary and left to the
individual ideas of each design engineer. Hundreds of different time codes were
formed, some of which were standardized by the „Inter Range Instrumantation
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 TCR510 however only decodes IRIG-A, IRIG-B or AFNOR NFS
87-500 formats. The AFNOR code is a variant of the IRIG-B format. Within this code
the complete date is transmitted instead of the ‘Control Functions’ of the IRIGtelegram.
Description of IRIG-Codes
The specification of individual IRIG time code formats is defined in IRIG Standard
200-98. They are described by an alphabetical character followed by a three-digit
number sequence. The following identification is taken from the IRIG Standard 20098 (only the codes relevant to TCR510 are listed):
character bit rate designation A 1000 pps
B 100 pps
1st digit form designation 0 DC Level Shift
width coded
1 sine wave carrier
amplitude modulated
2nd digit carrier resolution 0 no carrier (DC Level
Shift)
1 100 Hz, 10 msec
resolution
2 1 kHz, 1 msec resolution
3 10 kHz, 100 msec
resolution
3rd digit coded expressions 0 BCD, CF, SBS
1 BCD, CF
2 BCD
3 BCD, SBS
BCD: time of year, BCD-coded
CF: Control-Functions (user defined)
SBS: seconds of day since midnight (binary)
16
IRIG-Standard format
17
AFNOR-Standard format
Overview
The Board TCR510 was designed for the decoding of unmodulated and modulated
IRIG- and AFNOR-Timecodes. Modulated codes transport the time information by
modulating a sinusoidal carrier signals amplitude whereas unmodulated signals
employ a pulse width modulated DC signal.
The receivers automatic gain control allows the reception of signals within a range
from abt. 600mVpp up to 8Vpp. The potential free input can be jumper selectable
terminated in either 50 Ω, 600 Ω or 5 kΩ. Modulated codes are applied to the board
via an on board SMB connector.
18
The unmodulated or 'DC Level Shift' timeocdes are applied via SUB-D connector on
rear panel. Galvanic insulation of this input is obtained by an opto coupler device.
TCR510 provides two configurable serial ports ( RS232 or 1xRS485 option ), a pulse
per minute and per second ( PPS / PPM ) as well as a DCF Simulation port at TTL
Level. Further three fixed frequency outputs at 100 kHz, 1 MHz and 10 MHz at TTL
Level are available.
Function principle
After the received IRIG-Code has passed a consistency check, the software clock and
the battery backed realtime clock of TCR510 are synchronized to the external time
reference. If an error in the IRIG-telegram is detected, the boards system clock
switches into holdover mode.
Apart from the codes AFNOR NFS 87-500 and IEEE1344, IRIG-Codes do not carry
a complete date but the number of the day within the current year ( 1...366 ). Hence
the date that is output in the serial telegram must be completed by the date stored in
the buffered real time clock. The day within the current year calculated from the
RTCs date is compared with the day number from the IRIG-Code every minute.
When a mismatch between these two day numbers is detected the board signalizes
freewheeling mode, however the systems time base will continue to synchronize with
the IRIG-signal. The DCF-Simulation is surpressed in this case.
Time and date of the real time clock can be set by a Meinberg Standard Telegram via
serial port COM0. Received IRIG-time can be re-calculated into UTC provided that
no time zone changeovers such as daylight saving appear in the received IRIGtelegrams. For more information please see chapter 'UTC-Offset' in the online
documentation of the enclosed software TCRMON.
IRIG-telegrams do not include announcers for the change of time
zone (daylight saving on/off) or for the insertion of a leap second.
Start or end of daylight saving time is executed with a delay of one
second by TCR510PCI therefore. If a leap second is inserted, the
system clock will be set to second ‘0’ for two consecutive seconds.
The board TCR510 decodes the following formats:
A133: 1000 pps, amplitude modulated sine wave signal, 10 kHz
carrier frequency
BCD time of year, SBS time of day
A132: 1000 pps, amplitude modulated sine wave signal, 10 kHz
carrier frequency
BCD time of year
A003: 1000 pps, DC Level Shift pulse width coded, no carrier
19
BCD time of year, SBS time of day
A002: 1000 pps, DC Level Shift pulse width coded, no carrier
BCD time of year
B123: 100pps, amplitude modulated sine wave signal, 1 kHz carrier
frequency
BCD time of year, SBS time of day
B122: 100 pps, amplitude modulated sine wave signal, 1 kHz carrier
frequency
BCD time of year
B003: 100 pps,DC Level Shift pulse width coded, no carrier
BCD time of year, SBS time of day
B002: 100 pps, DC Level Shift pulse width coded, no carrier
BCD time of year
AFNOR NFS 87-500: 100 pps, amplitude modulated sine wave signal, 1 kHz carrier
frequency
BCD time of year, complete date, SBS time of day
Input Signals
Modulated IRIG or AFNOR-Codes are applied via the on board SMB connector.
The lead should be shielded. Unmodulated codes are applied at SUB-D connector on
rear panel. Voltages applied to this input shall not exceed 12 V. The IRIG-Code to be
used must be set at the DIP Switch.
Input for unmodulated codes
Unmodulated IRIG-Codes, often referred to as pulse with coded or DC-Level Shift
Codes ( DCLS ), are fed into the board via SUB-D connector on rear panel. Insulation
of this input is done by a opto coupler device. The input circuitry is shown below.
20
Input for modulated codes
JP1 in Position 1 - 50
JP1 in Position 2 - 600
JP1 offen - ca. 5 k
Ω
Ω
Ω
Modulated codes must be applied to the on board SMB Connector. An automatic
gain control allows decoding of codes within an amplitude range from abt. 600 mVpp
up to 8 Vpp. To allow adaption of different time code generators, the boards input
impedance can be selected by an on board jumper.
Input impedance
The IRIG-specification does not define values for the output impedance of
generators or the input impedance of receivers. This fact led to incompatibility of
some modules, because the manufacturers could choose the impedances freely. For
example: if the output impedance of the generator is high and the input impedance of
the receiver low, the signal level at the receiver input might be too low for correct
decoding. Therefore the board TCR510 provides a jumper to select the impedance
(50Ω, 600 Ω or 5 kΩ) of the input for modulated codes ( SMB ) to comply with the
requirements of several systems.
Meinberg IRIG-generators have an output impedance of 50 Ω, to build a matched
transmission system when using a coaxial cable. If such a generator is used to
synchronize TCR510, the input impedance has to be set to 50 Ω accordingly (default
on delivery).
In addition to the telegram, the AFNOR-code defines the input/output impedances
also. If TCR510 is synchronized by this code, an input impedance 600 Ω of must be
set.
The setting „5 kΩ“ may be necessary if the generator has a high output impedance
(see specifications of manufacturer). The driver software shows a bar chart for
evaluation of the signal level at the receiver input.
The following detail of the placeplan of TCR510 shows the possible jumper setting
with the related input impedance:
21
Booting the Single Board Computer
waiting for refclock on COM1
with 9600 Baud 7E2
TCR: NORMAL OPERATION Wed, 18.11.2002
NTP: Not Sync MEZ 10:04:10
TCR: NORMAL OPERATION Wed, 18.11.2002
NTP: Offset TCR: 1ms MEZ 10:04:10
The LINUX operating system is loaded from a packed file on the flash disk of the
single board computer to a RAM disk. All files of the flash disk are stored in the
RAM disk after booting. Because of that it is guaranteed that the file system is in a
defined condition after restart. This boot process takes approx. one minute. After the
LINUX system has started up already the network function is initiated and the driver
software LANTIME is started. This driver tries to get a valid time from the TCR
reference clock in order to set the LANTIMEs clock. If TCR clock is not connected
the LANTIME is waiting for a valid time.
After starting up the LINUX system the network function is initiated and the program
for communication with the TCR510 and the NTPD (NTP daemon) is started. After
that NTPD starts synchronisation with the reference clocks (usual the hardware clock
of the single board computer and the TCR). Until synchronisation is finished the
following message is displayed:
For the synchronisation of the NTPD with the TCR it is necessary that the IRIGreceiver is locked with the input signal (FAIL LED is turned off and the LOCK LED
is turned on). In this case the following message is monitored on the display:
The second line shows the user that the NTPD is synchronized with the TCR with an
offset of -1 ms. Because of the internal time of the NTP which is adjusted by a
software PLL (phase locked loop) it takes a certain time to optimise this offset. The
NTPD tries to keep the offset below ±128 ms; if the offset becomes too large the
system time is set with the IRIG-time. Typically values for the offset are +-5 ms after
the NTPD has already synchronized.
22
Configuration User Interface
There are several ways to configure the LANTIME parameters:
Command Line Interface (CLI) via TELNET
Command Line Interface via SSH
Command Line Interface via serial interface terminal (BGT versions only)
HTTP Interface
Secure HTTP Interface (HTTPS)
Front panel LCD Interface
SNMP Management
To put LANTIME into operation for the first time an IP address is entered via the
front panel keys and LC display (refer to: DHCP IPv4 or AUTOCONF IPv6).
LANTIME variants without LC display have to be given the IP address via the serial
interface in the front panel, running a terminal software e.g. on a laptop. If once the
IPv4 address, netmask and IPv4 GATEWAY are configured, or the network interface
is initialised by IPv6 SCOPE-LINK, the LANTIME is accessible from any computer
in the network (remote).
To set up a TELNET connection the following commands are entered:
telnet 198.168.10.10 // LANTIME IP address
user: root
password: timeserver
With “setup” the configuration program is started.
To set up a SSH connection the following commands are entered:
ssh root@198.168.10.10 // LANTIME IP address
password: timeserver
With “setup” the configuration program is started.
To set up a HTTP connection the following address is to enter in a web browser:
http://198.168.10.10 // LANTIME IP address
password: timeserver
To set up a Secure HTTP (HTTPS) connection the following address is entered in a
web browser:
https://198.168.10.10 // LANTIME IP address
password: timeserver
23
The Front Panel Layout
TCR Status LEDs
The boards state is signalised by two front panel leds. The red FAIL led indicates
the freewheeling mode. It is activated when the board has switched into freewheeling
mode, and turned off when the clock is synchronized. The green LOCK led shows the
state of the internal time base and the oscillator regulation. LOCK flashes when the
internal time base is adjusted, and is constantly turned on when the oscillator
regulation has settled. Depending on the oscillators offset the settling phase ( flashing
LOCK led ) can take a few hours.
LC Display
The 2 x 40 character LC display is used to show the receiver’s status and let the
user edit parameters. The keys described below let the user select the desired menu.
The next chapter lists all available menus in detail. A quick reference of the available
menus and submenus can be found at the end of this document.
MENU Key
This key lets the user step through several display menus showing specific data.
CLR/ACK Key
This key has to be used when parameters are to be modified. When this key is
pressed the parameters that have been edited are saved in the battery buffered
memory. If the menu is left without pressing CLR/ACK all changes are discarded.
NEXT Key
When editing parameters (LCD cursor is visible) this key moves the cursor to the
next digit with respect to the next parameter to be edited. If the current menu just
displays data (cursor not visible) pressing this key switches to a submenu (if
available).
INC Key
When editing parameters this key increments the digit or letter at the cursor
position.
24
Configuration via LC Display
On first installation of LANTIME the network parameters can only be configured
by the front panels push buttons and the LC display. Press MENU until the SETUP
menus appear on the display. The first setup menu are the LAN PARAMETERS.
Pressing NEXT further setup menus appear. Pressing CLR/ACK the LAN
PARAMETERS menu is entered. The submenu TCP/IP ADDRESS appears. Pressing
NEXT the following submenus can be chosen: NET MASK, DEFAULT
GATEWAY, IPv6 address, HOSTNAME, DOMAINNAME, NAMESERVER and
REMOTE CONNECT. CLR/ACK lets the user enter the corresponding submenu to
make changes with NEXT and INC. Pressing CLR/ACK after changing parameters
acknowledges the changes. Leaving the menu with MENU all changes are discarded
and the setup menu is displayed again. All changed settings of the LAN
PARAMETER’s sub menu come into affect not before MENU is pressed once again
and the changes are confirmed.
The unique 32 bit TCP/IP address must be set by the network administrator. The net
mask will be defined by the network. It is probable that you will need to set up the
default gateway also.
The correct connection to the LANTIME can be reviewed from any other workstation
in the network with the program PING.
REMOTE CONNECT lets the user enable or disable all connections via network (e.g.
TELNET, FTP or HTTP). If changes occur via HTTP interface or setup program the
message “REMOTE CONNECT: partial enabled” may appear. The NTP protocol will
restart after any change.
NOTE: Any HTTP, HTTPS, SSH or TELNET connection to the LANTIME is
possible only if REMOTE CONNECT is enabled!
25
The menus in Detail
TCR: NORMAL OPERATION Wed, 18.11.2002
NTP: Offset TCR: -1ms UTC 10:04:10
LANTIME:4.05 SN:000000000000
TCR510 :1.01 SN:9008890
NTP:4.2.0 OS:2.4.20
HWaddr: 00:00:00:00:00:00
1024 b2:a7:95:c1:fa:eb:de:9a:92:05:33:e4
:47:68:eb:91 LanV4
IRIG Receiver State: --**--*- AGC:0xFF
Drift:-00001us TFOM:0xFF SysConf:0x00
Root Menu
The root menu is shown when the receiver has completed initialisation after powerup. The left side of the first line of the display shows the receiver’s mode of operation
as described above. If the antenna is disconnected or not working properly, the text
"ANTENNA FAULTY" is displayed instead. The second line shows the offset of this
reference clock to the local time (in this example the offset is 1 ms).
On the right side of the display the current date, the name of the time zone (the time
zone is always UTC) and time are monitored. If the "SYNC Simulation" option is
enabled an "*" will be shown behind the time.
If the NEXT key is pressed from the root menu a submenu is displayed showing the
receiver’s software revision of the LANTIME software and the TCR510 flash
software:
If the NEXT key is pressed twice from the root menu a submenu is displayed showing
the NTP software version, the operating system version and the MAC address of the
integrated net card.
Pressing NEXT the third time the fingerprint of the SSH key is displayed:
Menu IRIG state
Pressing MENU in the root menu is shown when the single board computer has
completed initialisation after power-up. The first line of the display shows the system
state with 8 options described above. On the right side the AGC (Automatic Gain
Control of the input signal) value in hexadecimal will be shown. The second line will
display the drift in [us] of the internal oscillator, the TFOM value (Time Figure Of
Merit: the quality of the IRIG-signal, only used with IEEE 1344) and the current
system configuration:
26
IRIG system state: Bit 7 ... 0
Bit 7: Invalid UTC parameter
Bit 6: TCAP exceeded, jitter out of range
Bit 5: Lock on
Bit 4: Telegramm error
Bit 3: Data available
Bit 2: Invalid sysconf
Bit 1: Pulses enabled
Bit 0: Warmed up
Invalid UTC parameter: This bit is set to one if the checksum of the ‘Offset from
UTC’ parameter, which must be used if no IEEE1344 extensions are available, is
invalid. User must enter new ‘Offset from UTC’ data to clear this bit. Please note that
the IRIG-receiver never leaves freewheeling mode if IEEE1344 is disabled and the
UTC-Parameter are invalid!
TCAP exceeded, jitter out of range: If the jitter between two consecutive IRIGtelegrams exceeds +/- 100us the receiver switches into freewheeling mode and the
‘TCAP exceeded’ Bit is set. ‘TCAP exceeded’ is cleared if the measured jitter is
below +/- 100us.
Lock on: ‘Lock On’ is set whenever the receiver is in synchronous mode and the
internal oscillator correction value has settled.
Telegram error: This bit is set if the cosistency check of two consecutive IRIGtelegrams fails. The IRIG-receiver switches into freewheling mode if ‘telegram error’
is set.
Data available: ‘data available’ is set if the receiver can read the timecode.
Invalid sysconf: If ‘invalid sysconf’ is set the checksum of the system configuration
data is invalid. In this case the default mode ‘IEEE1344 disabled’ is selected. User
must cycle the system or enter a new system configuration in the IRIG-parameter
menu.
Pulses enabled: The pulse per second (PPS) signal which increases the NTP’s
acurracy is turned when ‘lock on’ is set the first time. The ‘pulses enabled’ bit is set if
the PPS signal is enabled.
IRIG system configuration Bit 2 ... 0
Bit 7 ... 4: reserved
Bit 3: ignore Day Of Year enabled
Bit 2: ignore TFOM
Bit 1: ignore SYNC
Bit 0: IEEE 1344 enabled
27
Menu Reference Clock State
TCR: 0000 clk_okay
filtoffset= -8.42 -4.23 -10.25
SETUP: LAN PARAMETERS
Pressing MENU in the main menu lets the user enter to the status menu of the
reference clocks. The name of the reference clock, the actual state and the last four
offsets to the NTP time are displayed (the left one is the newest).
The state of the refclock will be displayed like "0000". The first two numbers reflects
the actually state and the second two numbers the last state of the refclock. The
following states are possible:
00: clock okay
01: clock no reply
02: clock bad format
03: clock fault
04: clock bad signal
05: clock bad date
06: clock bad time
Menu SETUP
From this menu, several topics can be selected which let the user edit parameters or
force special modes of operation. A specific topic can be selected using the NEXT
key. Depending on the current topic, pressing the CLR/ACK key either enters edit
mode with the selected set of parameters or switches to the selected mode of
operation (after the user has acknowledged his decision). Once edit mode has been
entered, the NEXT key lets the cursor move to the digit or letter to be edited whereas
the INC key increments the digit or letter under the cursor. If changes have been
made, the CLR/ACK key must be pressed. If all changes have been made in one setup
submenu you have to press the MENU key. After that you will be asked to save the
settings. Press INC to change and save the last changes. Otherwise all changes are
discarded when the user presses the MENU key in order to return to the SETUP
display.
28
SETUP LAN PARAMETERS
TCP/IP ADDRESS
000.000.000.000
SETUP: TCR PARAMETERS
Offset from UTC: +02:00
SETUP: TCR PARAMETERS
IRIG Code: B122/123
In this submenu the network parameters are configured. These parameters have to
be adapted to the existing network when the LANTIME is installed the first time. The
following parameters can be set: TCP/IP ADDRESS, NETMASK, DEFAULT
GATEWAY, IPv6 ADDRESS HOSTNAME, DOMAINNAME, NAMESERVER,
SYSLOG SERVER, SNMP MANAGER, REMOTE CONNECT, RESET
FACTORY SETTINGS und NET LINK MODE. All settings are applied to the
first Ethernet interface only. All further Ethernet interfaces have to be configured via
HTTP or CLI interface. With the submenu REMOTE CONNECT you can enable or
disable all network connections via TELNET, FTP or HTTP. When the network
parameters have been changed the configuration file is updated and the NTPD is
restarted.
With the submenu RESET FACTORY SETTINGS the following parameters will
be set to the default values:
All configuration parameters of the timeserver are saved on the Flash Disk in the file /
mnt/flash/global_configuration. It is recommended not to modify this file manually
but to use the configuration interface (HTTP, CLI or SNMP). If this file does not
exist, an empty file is generated. The default configuration file is part of the
attachment.
The parameters for speed and mode of the net card can be changed with the menu
item NET LINK MODE. There are 5 modes available: Autosensing, 10 MBit/HalfDuplex, 100 MBit/Half-Duplex, 10 MBit/Full-Duplex, 100 MBit/Full-Duplex.
Default setting is Autosensing.
SETUP TCR PARAMETERS
In this menu the parameters of the IRIG-receiver can be set. The submenu „Offset
from UTC“ lets the user set the offset from local time to UTC time. The IRIG-signal
provided no information of the offset from UTC and the receiver has to generate this
information for the NTP daemon.
With the NEXT button the menu for the used IRIG-Code will be displayed.
29
The submenu „IGNORE SYNC“ lets the user enable or disable the IRIG SYNC
SETUP: TCR PARAMETERS
IGNORE SYNC disabled
SETUP: TCR PARAMETERS
DATE
SETUP: TCR PARAMETERS
OSCILL. ADJUST: CAL:2341 FINE:3704
SETUP: TCR PARAMETERS
Reset IRIG parameters
simulation mode. If you want to use the IRIG-receiver without connecting an IRIGsignal this mode will simulate a valid output for the NTP daemon. This is only for test
purposes. IGNORE SYNC should be disabled under normal operating conditions.
Press CLR/ACK to change the mode
The submenu „DATE“ lets the user set the date of the IRIG-receiver. If no IEEE1344
extensions are present in the connected IRIG-signal, no date information is available
from it. The item „IEEE 1344“ must be set to ‘disable’ and the user must manually
enter the current date. Press CLR/ACK to edit and to confirm the date of the IRIGreceiver. After setting the time manually the NTP daemon will be restarted
automatically.
The basic model of the TCR510 includes a voltage controlled temperature
compensated oscillator (VCTCXO). Its nominal frequency of 10 MHz is adjusted by
using two digital-to-analog converters (DACs). One of them is responsible for the
coarse tuning and the other one for the fine adjustment of the oscillator.
The value for the coarse-DAC is settable in the menu "OSCILL. AJUST" in the range
of -32768 to 32768. If the edited value exceeds the maximum value is stored. This
menu only lets the user modify the coarse-DAC (CAL). The fine-DAC (FINE) is
displayed but not to edit. It will be cleared automatically.
This value should only be changed by specialized personnel of company
Meinberg and not by the user!
The submenu „Reset IRIG parameters“ lets the user reset the IRIG-parameters to the
default values. The UTC parameters will be set to +00:00 and the system
configuration will be set to 0x00.
30
Loading...