MOBATIME DTS 4138.timeserver Owner's Manual

MOUNTING AND
INSTRUCTION MANUAL
DTS 4138.timeserver
Network – Time Server and Master Clock
© MOBATIME
BE-800870.13
Certification of the Producer
STANDARDS
The DTS 4138.timeserver was developed and produced in accordance with the EU Guidelines:
2014 / 30 / EU
EMC
2014 / 35 / EU
LVD
2008 / 57 / EU
Railway
2011 / 65 / EU
RoHS
1907 / 2006
REACH
2012 / 19 / EU
WEEE
References to the Instruction Manual
1.
2.
3.
4.
5.
6.
7.
The information in this Instruction Manual can be changed at any time without notice.
The current version is available for download on www.mobatime.com.
The device software is continuously being optimized and supplemented with new options. For this
reason, the newest software version can be obtained from the Mobatime website.
This Instruction Manual has been composed with the utmost care, in order to explain all details in
respect of the operation of the product. Should you, nevertheless, have questions or discover errors in
this Manual, please contact us.
We do not answer for direct or indirect damages, which could occur, when using this Manual.
Please read the instructions carefully and only start setting-up the product, after you have correctly
understood all the information for the installation and operation.
The installation must only be carried out by skilled staff.
It is prohibited to reproduce, to store in a computer system or to transfer this publication in a way or
another, even part of it. The copyright remains with all the rights with BÜRK MOBATIME GmbH,
D-78026 VS-Schwenningen and MOSER-BAER AG – CH 3454 Sumiswald / SWITZERLAND.
© MOBATIME
2 / 104
800870.13
Overview
1
Safety ....................................................................................................................... 6
2
Maintenance ............................................................................................................. 9
3
General Information: Introduction............................................................................ 10
4
Displays .................................................................................................................. 13
5
Installation .............................................................................................................. 15
6
Operation ................................................................................................................ 16
7
Updates .................................................................................................................. 55
8
Time administration ................................................................................................ 62
9
SNMP ..................................................................................................................... 69
10 Power supply alternatives ....................................................................................... 73
APPENDIX
A
Connection diagrams .............................................................................................. 74
B
Time zone table ...................................................................................................... 78
C
Alarm list ................................................................................................................. 80
D
Troubleshooting ...................................................................................................... 82
E
Serial Telegrams..................................................................................................... 84
F
Copyright Notice ..................................................................................................... 89
G
Parameters ............................................................................................................. 90
H
Technical data ........................................................................................................ 95
I
Index....................................................................................................................... 98
J
Connection table (to fill in) .................................................................................... 100
© MOBATIME
3 / 104
800870.13
Table of contents
6.5.13
6.5.14
6.5.15
6.5.16
6.5.17
6.5.18
6.5.19
6.5.20
6.5.21
6.5.22
6.5.23
6.5.24
6.5.25
1 Safety ......................................................... 6
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
Safety instructions ....................................... 6
Symbols and Signal Words used in this
Instruction Manual ....................................... 6
Intended Use ............................................... 6
Observe operating safety! ........................... 7
Consider the installation site! ...................... 7
Please observe the electromagnetic
compatibility!................................................ 7
Network security .......................................... 7
Pay attention to the instructions for the
connection of the power supply ................... 8
2 Maintenance ............................................... 9
2.1
2.2
2.3
Troubleshooting: Repairs ............................ 9
Cleaning ...................................................... 9
Disposing ..................................................... 9
3 General Information: Introduction .............. 10
3.1
3.2
3.3
3.4
3.5
3.6
Scope of Delivery ...................................... 10
Technical Data .......................................... 10
Introduction ................................................ 10
Device types .............................................. 11
DTS Distributed Time System ................... 11
MOBA-NMS - Network Management System
................................................................... 11
3.6.1
3.6.2
Overview of the main functions ............................ 12
Device management............................................ 12
4 Displays .................................................... 13
4.1
4.2
4.3
LED displays front side ............................. 13
LED indication back side ........................... 13
Display ....................................................... 14
5 Installation................................................. 15
5.1
5.2
5.3
5.4
5.5
Connections .............................................. 15
Boot procedure of the DTS 4138.timeserver
................................................................... 15
Firmware ................................................... 15
Initial configuration .................................... 15
Basic settings (factory settings) ................ 15
6 Operation .................................................. 16
6.1
General ...................................................... 16
6.1.1
6.1.2
6.1.3
6.2
6.3
6.4
MOBA-NMS operation .............................. 18
Main menu ................................................. 19
Status menu .............................................. 20
6.4.1
6.4.2
6.5
Telnet .................................................................. 16
SSH..................................................................... 17
Menu structure .................................................... 17
Time information and status ................................ 22
Time source information ...................................... 23
Configuration menu ................................... 24
6.5.1
6.5.2
6.5.3
6.5.4
6.5.5
6.5.6
6.5.7
6.5.8
6.5.9
6.5.10
6.5.11
6.5.12
Lines ................................................................... 25
DCF – output ....................................................... 25
DCF / Pulse / Frequency output........................... 26
Serial interface .................................................... 27
IRIG / AFNOR / DCF-FSK Output ........................ 29
NTP slave clocks / time zone server .................... 30
Time handling ...................................................... 31
Time source ........................................................ 32
Time adjustment / Time-keeping.......................... 33
Redundant operation ........................................... 34
NTP server .......................................................... 35
Manual time set / Leap second ............................ 39
© MOBATIME
4 / 104
6.6
Alarms ................................................................. 39
Alarm relay .......................................................... 40
Alarm mask ......................................................... 40
E-mail .................................................................. 41
SNMP traps ......................................................... 43
Alarm input .......................................................... 44
General settings .................................................. 45
Network ............................................................... 46
Services (network services FTP, telnet, SSH...) ... 48
SNMP .................................................................. 49
SNMP V1 / V2c.................................................... 50
SNMP V3 ............................................................ 51
Time zone selection ............................................. 53
Maintenance menu .................................... 54
7 Updates..................................................... 55
7.1
Important information about the update
procedure ................................................... 55
7.2 Updating images with MOBA-NMS ........... 56
7.3 Updating images with FTP ......................... 56
7.4 Updating applications or configurations with
FTP ............................................................ 57
7.5 Updating images via USB .......................... 57
7.6 Updating applications or configurations via
USB ............................................................ 58
7.7 FTP connection .......................................... 59
7.8 SFTP connection ....................................... 59
7.9 SCP connection ......................................... 60
7.10 Save Configuration externally .................... 60
7.11 Copying Telegram files to the DTS
4138.timeserver ......................................... 61
8 Time administration ................................... 62
8.1
8.2
8.3
Concept of time administration .................. 62
Time acceptance ....................................... 63
Time acceptance from an external source
(DCF or GPS) ............................................ 63
8.4 Time acceptance from external AFNOR-A/C,
IRIG-B12x source ...................................... 64
8.5 Time acceptance from NTP ....................... 64
8.6 NTP as backup .......................................... 64
8.7 Time server ................................................ 64
8.8 Time accuracy, time-keeping ..................... 65
8.9 Leap second .............................................. 65
8.10 NTP Authentication .................................... 65
8.10.1 NTP symmetric keys ............................................ 65
8.10.2 NTP Autokey ....................................................... 66
8.11 Redundant operation of 2 DTS
4138.timeservers ....................................... 67
9 SNMP........................................................ 69
9.1
9.2
9.3
General ...................................................... 69
Device configuration with SNMP ............... 70
DTS subagent SNMP notification .............. 70
9.3.1
9.3.2
9.3.3
9.3.4
9.3.5
9.3.6
Startup [dts4138StartUp] ..................................... 70
Shutdown [dts4138Shutdown] ............................. 70
Status changed [dts4138StatusChanged] ............ 71
Configuration changed [dts4138ConfigChanged] . 71
Alive Notification [dts4138Alive] ........................... 72
Alarm Notification [dts4138Alarm] ........................ 72
10 Power supply alternatives.......................... 73
800870.13
APPENDIX
A Connection diagrams ................................ 74
A.1
A.2
A.3
A.4
A.5
Front connections ...................................... 74
Connections (rear view) ............................ 75
Plug-in spring terminals ............................. 77
Connection GPS / GNSS 4500, DCF 4500
or GNSS 3000 ........................................... 77
IRIG-B00x Digital Output TTL connection . 77
B Time zone table ........................................ 78
C Alarm list ................................................... 80
D Troubleshooting ........................................ 82
E Serial Telegrams ....................................... 84
E.1
E.2
General ...................................................... 84
Syntax of the telegram configuration file ... 85
F Copyright Notice ....................................... 89
G Parameters ............................................... 90
H Technical data........................................... 95
I Index ......................................................... 98
J Connection table (to fill in) ....................... 100
© MOBATIME
5 / 104
800870.13
1
Safety
1.1
Safety instructions
Read this chapter and the entire instruction manual carefully and follow all instructions
listed. This is your assurance for dependable operations and a long life of the device.
Keep this instruction manual in a safe place to have it handy every time you need it.
1.2
Symbols and Signal Words used in this Instruction Manual
Danger!
Please observe this safety message to avoid electrical shock!
There is danger to life!
!
Warning!
!
Caution!
Please observe this safety message to avoid bodily harm and injuries!
Please observe this safety message to avoid damages to property and
devices!
Notice!
Additional information for the use of the device.
Important information in the Manual!
This information must be followed!
1.3
Intended Use
The DTS 4138.timeserver is a time server for the use in network environments. It can
be synchronized from NTP and be used as NTP server. In addition, it can read the time
from DCF or GPS (e.g. from GPS 4500).
It can operate as master clock for a self-setting IRIG clock line. The DTS 4138 has 1
such line.
For additional functions, see the device descriptions in chapter 3.
The device is designed for 19" racks and intended to be installed in a 19" cabinet.
Operate the device only in installed condition and with all connectors plugged in.
Use this product only as stated in this instruction manual. Any other use is considered
improper use.
© MOBATIME
BE-800870.13
1.4
Observe operating safety!
!
• Never open the housing of the device! This could cause an electric short or even a
fire, which would damage your device. Do not modify your device!
Caution!
• The device is not intended for use by persons (including children) with limited
physical, sensory, or mental capacities or a lack of experience and/or knowledge.
• Keep packaging such as plastic films away from children. There is the risk of
suffocation if misused.
!
1.5
Consider the installation site!
• To avoid any operating problems, keep the device away from moisture and avoid
dust, heat, and direct sunlight. Do not use the device outdoors.
Caution!
• The device is designed for 19" racks and should only be operated installed in a 19"
cabinet.
Danger! Make sure
that you wait before using the device after any transport until the device has
reached the ambient air temperature. Great fluctuations in temperature or
humidity may lead to moisture within the device caused by condensation, which
can cause a short.
!
1.6
Please observe the electromagnetic compatibility!
• This device complies with the requirements of the EMC and the Low-voltage Directive.
Caution!
!
1.7
Caution!
Network security
• The default password shall be changed after the commissioning of the device.
• A reset of the password to default through hardware is not possible.
Using MOBA-NMS the password can be modified.
In case an access via MOBA-NMS is not possible, support effort will be needed or
the device has to be sent back to the factory.
• Use encrypted services (SSH, SCP, SFTP)
• All unused services shall be deactivated: FTP, Telnet,…
• Refer to our Security Guidelines TE-801312
(see www.mobatime.com – Login area:
> Customer_area > Product_Resources - 10_Timerserver_TimeCenter).
© MOBATIME
7 / 104
800870.13
1.8
Pay attention to the instructions for the connection of the power supply
The connections are described in appendix "A Connection diagrams".
Danger! Absolutely pay attention:
Mounting, installation, commissioning and repairs of electrical devices must
only be carried out by a licensed electrician. While the national installation
regulations must be adhered.
For the power supply connection ( DC In1 ) / ( DC In2 ), two fuses in
according to the performance data has to be provided (in both lines).
The used fuses for the DC-supply have to be approved for DC.
Each power supply connection ( DC In1 ) / ( DC In2 ), needs to be realized
with an all-pole disconnection device, which is installed near to the device
mentioned in this manual, which is clearly labeled and good accessible.
Before working on a device or on the electrical installations the
corresponding circuits have to be switched off and secured against
uncontrolled power on.
In case more than one supply voltage is used ( DC In1 ) / ( DC In2 ), all of
them have to be disconnected before starting any maintenance work.
© MOBATIME
8 / 104
800870.13
2
Maintenance
2.1
Troubleshooting: Repairs
Please read carefully Appendix D Troubleshooting if your device does not work
properly.
If you cannot rectify the problems, contact your supplier from whom you have
purchased the device.
Any repairs must be carried out at the manufacturer’s plant.
Disconnect the power supply immediately and contact your supplier if …
• liquid has entered your device.
• the device does not properly work and you cannot rectify this problem yourself.
2.2
Cleaning
• Please make sure that the device remains clean especially in the area of the
connections, the control elements, and the display elements.
• Clean your device with a damp cloth only.
• Do not use solvents, caustic, or gaseous cleaning substances.
2.3
Disposing
Device
At the end of its lifecycle, do not dispose of your device in the regular household
rubbish. Return your device to your supplier who will dispose of it correctly.
Packaging
Your device is packaged to protect it from damages during transport.
Packaging is made of materials that can be disposed of in an environmentally friendly
manner and properly recycled.
© MOBATIME
9 / 104
800870.13
3
General Information: Introduction
3.1
Scope of Delivery
Please check your delivery for completeness and notify your supplier within 14 days upon
receipt of the shipment if it is incomplete.
The package you received contains:
• DTS 4138.timeserver
• Mounting set for rack mounting consisting of:
- 4 pcs nuts for 19" housing
- 4 screws M6 for the nuts
- 4 plastic discs for screws M6
• Connector set
- 1 * spring terminal 6-pole orange
- 3 * spring terminal 4-pole orange
- 2 * spring terminal 2-pole orange
- 1 * spring terminal 5-pole orange
• 2 pcs mounting tools with spring terminals
3.2
Technical Data
See Appendix "H Technical data“.
3.3
Introduction
The DTS 4138.timeserver is a NTP Time Server for use in network environments. It can
be synchronized by DCF or GPS (e.g. from GPS 4500), AFNOR-A/C, IRIG-B1 and NTP,
and act as a NTP server in a network.
It can be used as a master clock for NTP slave clocks, synchronized via unicast or
multicast with NTP and time zone table.
It is equipped with 2 LAN interfaces for the operation in two independent networks.
In addition, the DTS 4138 provides an IRIG/AFNOR line (available as analog and digital
(current loop and RS422) output), a serial interface for the output of time tele-grams as
well as an output line for technical pulses (pulse/frequency/DCF).
As the "main“ master clock, the DTS 4138 can synchronize other master clocks or other
equipment with DCF and monitor with 1 alarm input.
The DTS 4138 can send both e-mails and SNMP traps for alerting purposes.
Using MOBA-NMS and SNMP, the DTS 4138 can be fully operated and its configuration
and system status can be requested.
To maintain a redundant time source, two DTS 4138 can be linked by an optical link.
1
With IRIG-B synchronization the date must be set manually once or by another time source (GPS).
© MOBATIME
10 / 104
800870.13
3.4
3.5
Device types
Model:
Features:
Product no.:
DTS 4138.timeserver
According to above description with TCXO
(temperature compensated quartz)
117982
DTS 4138S.timeserver
Like DTS 4138; Siemens version
117981
DTS Distributed Time System
DTS (Distributed Time System) is a system developed by Moser-Baer AG to connect
decentralized master clocks, slave clock lines and time servers. For communication,
standard LAN (Ethernet) is used. The DTS can be centrally operated and monitored.
3.6
MOBA-NMS - Network Management System
MOBA-NMS is software used for central management and inquiry of state and alarm
information. It supports DTS devices as well as all MOBATime analog and digital network
clocks and can handle a network with more than 1000 devices. This software provides
extensive functions for the configuration, installation, back-up / recovery etc. especially
for DTS devices.
© MOBATIME
11 / 104
800870.13
Due to the DTS concept, MOBA-NMS can be installed multiple times in one network.
With different user rights on the device and software level, the configuration abilities of
different users can be set as required.
For DTS devices, all communication is conducted over SNMP V3. The SFTP protocol is
used for broadcasting files.
3.6.1
Overview of the main functions
The main MOBA-NMS functions for DTS devices and network clocks are listed below:
• automatic device scan over multicast or IP range
• device management using user-defined device groups ➔ see chapter „3.6.2 Device
management“
• intuitive user interface with input check for the device configuration
• status / alarm request and display on the device group level
• device firmware update for one or several devices (parallel)
• support for device commands, e. g. reset, restart etc.
• back-up / recovery of DTS devices
• transfer of the whole DTS configuration to another device
• user management with different access rights
• monitor for NTP and time zone packages
• editor for time zone files
• online help
• etc.
3.6.2
Device management
All MOBATime network devices are displayed in the so-called device view. Here, the
devices can be grouped according to user-defined criteria. For this, the individual devices
can simply be moved to the according groups and sorted using drag and drop. There is
no limit to the number of groups and sub-groups.
Besides the organizational advantages (easier locating, better
overview), a device group has the following advantages:
• commands and device updates can be applied to the whole
group (including sub-groups).
• Alarms and errors of included devices are displayed on the
group level.
• Complete groups can be moved / sorted among themselves.
The content of the device view can be saved and opened at a
later time. The created structure and breakdown into groups is
preserved.
© MOBATIME
12 / 104
800870.13
4
Displays
4.1
LED displays front side
Description
Color
Status
Description
Power
Green
On
Off
Mains or DC power supply is in order
No power supply
Alarm
Red
On
Off
The alarm relay signalizes an alarm
No active alarms
Sync
Green
On
Off
DTS 4138 can read the time from a synchronization
source
Synchronization source is not available
LAN 1 control lamps:
Left
Green
Orange
Blinking
Blinking
Network activity
No connection to network
Right
Yellow
Off
On
10 Mbit
100 Mbit
LAN 2 control lamps:
Left
Green
Orange
Blinking
Blinking
Network activity
No connection to network
Right
Yellow
Off
On
10 Mbit
100 Mbit
4.2
LED indication back side
Description
Color
Status
Description
DCF in
red
Blinking
DCF (GPS reception), blinking every second ➔ time
information from receiver
© MOBATIME
13 / 104
800870.13
4.3
Display
Display showing the current status of the DTS 4138.
Display of:
-Time, date
-Current time source
-Stratum of the DTS 4138, status: Master / Slave
-Software version
-IPv4 address LAN 1
-IPv4 address LAN 2
-IPv6 address LAN 1
-IPv6 address LAN 2
-Alarm summary
-Current alarms
The display can be operated by means of the corresponding “Display“ button:
First press the button briefly:
Other buttons to press briefly:
Press button longer (>3 sec):
Switch on the background light
Scroll through all displays
Change to default display (time and date)
The display changes after approx. 3 min without pressing the button for the default
display and the background light goes off.
If a USB stick has been plugged in, it will be displayed. If only telegram files should be
copied or the network settings should be changed, this can be activated directly with
the button. (Press the button until the copy process starts).
© MOBATIME
14 / 104
800870.13
5
Installation
5.1
Connections
The connections are specified in Appendix “A Connection diagrams“.
Only connect the designated devices to the various inputs and outputs.
5.2
Boot procedure of the DTS 4138.timeserver
The normal booting time of the DTS 4138 is approx. 60 sec. with pre-set IP or with
DHCP. After booting procedure, the text "starting" appears on the display (during the
booting procedure the display is dark and empty). Without connection to a DHCP
server, the first start up can take up to 75 seconds. After that, the DHCP option must
be set to "off" in the network configuration.
The display “starting“ remains until the time of output to the lines.
The duration, depending on the configuration, is 5-30 sec.
5.3
Firmware
It is recommended to install the current firmware on your device prior to the definite
commissioning. The current firmware can be found under www.mobatime.com – Login
area: > Customer_area > Product_Resources > Timeserver.
5.4
Initial configuration
Per default, the LAN 1 interface is configured with DHCP on. After booting in a network
with DHCP server, the received IP address can be displayed.
The LAN 2 interface is configured with the following static settings per default:
IP 192.168.1.5, Subnet 255.255.255.0, Gateway 192.168.1.1
If these possibilities do not work out for the initial configuration, the network
configuration can be modified using a USB stick. For this purpose, a text file named
DTS4138NW.conf is created and filled with the corresponding parameters (not all
parameters are required):
IP1:192.168.1.3
SUB1:255.255.255.0
GW1:192.168.1.1
IP2:10.0.0.7
SUB2:255.255.240.0
GW2:10.0.0.1
The insertion of the USB stick is displayed. For taking over the network settings, press
the button until the normal time display reappears.
5.5
Basic settings (factory settings)
The basic settings can be found in the table in Appendix “G Parameters”.
© MOBATIME
15 / 104
800870.13
6
Operation
6.1
General
Operation occurs via a terminal menu or SNMP. SNMP operation is explained in chapter
“9 SNMP“. Operation with the terminal menu takes place either via Telnet or SSH. After
a connection has been set up, the login screen is displayed:
To start the menu, dts must be logged in as user. The standard password is dts.
(Changing the password ➔ see chapter “6.5.19 General settings“).
Only one menu can be open at any time. The first menu started has priority. The menu
is automatically closed after 15 min. without operation, and any possible connection via
Telnet or SSH is interrupted.
Backspace:
Backspace must be set to "delete“ with the serial terminal.
Local echo:
Some terminals (serial or Telnet) do not display the characters entered. It is, therefore,
necessary to switch on the "local echo" in the terminal.
6.1.1
© MOBATIME
Telnet
Windows 8, 10, 11:
e.g. with Putty
User: dts
Standard password: dts
Linux:
Start console and enter “telnet [IP-address]
16 / 104
800870.13
6.1.2
SSH
Windows 8, 10, 11:
e.g. with Putty
User: dts
Standard password: dts
Linux:
Start console and enter “ssh dts@[IP-address]“
Password: dts
6.1.3
Menu structure
menu title
parameters
menu options
response line
input line (prompt)
status line
The current menu is always displayed in the menu title. The menu options show all
the selectable menu functions. Provided the menu item is not a further menu, the set
parameters are displayed. Error messages (e.g. invalid entries) or additional
information to the selected menu items are displayed in the response line. The input
line shows the current input values or options possible. The status line only appears,
when an information has to be displayed, e.g. "An alarm is active".
All entries must be completed with ENTER (Return) (e.g. also ESC).
The menu window can always be exited with Ctrl-C (incl. termination of the Telnet and
SSH connection).
The desired menu can be selected with the relevant number.
The numbers 98 and 99 are always used identically:
• With 98, the settings entered are saved and the menu exited. Depending on the
change, the DTS 4138, or only partial functions, are rebooted.
• With 99, all changes to the menu are reversed and the menu exited.
In the menus where data cannot be saved (command 98), the menu is only exited
with 99, but any changes are not saved.
The current menu is updated, without any further entry, with ENTER.
© MOBATIME
17 / 104
800870.13
6.2
MOBA-NMS operation
For the configuration of DTS devices via GUI, MOBA-NMS (see chapter „3.6 MOBANMS - Network Management System“) can be used. All configuration possibilities are
subordinated in different configuration pages (called „tabs“). These tabs are connected
to the terminal menu and designated accordingly. Example: The terminal menu
„Configuration ➔ Alarms“ can be found in MOBA-NMS under the tab „Alarms“.
Configuration example:
configuration pages
(tabs)
For further details on the general MOBA-NMS operation, check the integrated online help
(menu „Help ➔ Show help“).
Important: To enable the communication between MOBA-NMS and the DTS devices,
SNMP must be activated! Set terminal menu „Configuration ➔ SNMP ➔
SNMP Mode“ to „on“. SNMP is activated by default.
© MOBATIME
18 / 104
800870.13
6.3
Main menu
Menus:
Status:
Display of various information regarding operation and environment
See chapter “6.4 Status menu“
Configuration: Configuration of the DTS 4138
See chapter “6.5 Configuration menu “
Maintenance:
© MOBATIME
Software update, backup and restore
See chapter “6.6 Maintenance menu“
19 / 104
800870.13
6.4
Status menu
The status menu consists of 2 pages.
Status menu page 1:
The menu shows various information on the current operating status.
© MOBATIME
1.
Requesting alarm status, display of all the DTS 4138 active errors.
Display of the DTS 4138 alarms (64) on 4 pages. The ALARM DETAIL menu
pages can be scrolled through with ENTER. Active alarms are displayed with a *.
The ALARM DETAIL menu page can be exited with 99. All DTS 4138 active
alarms are displayed, masking (e-mail, traps, relay) only occurs later.
2.
Alarm history display.
Display of the DTS 4138 alarm record, newest alarm first. The ALARM RECORD
menu pages can be scrolled through with ENTER. The ALARM RECORD menu
page can be exited with ESC.
Max. length of error report: 240 messages.
3.
Current time and status display. See chapter "6.4.1 Time information and status"
4.
Time source information display. See chapter "6.4.2 Time source information"
5.
Power supply information (current, voltage) display.
6.
Current network configuration display. With ENTER, a second page can be
displayed with network information.
7.
DTS 4138 system information display (internal status, regulation voltage of the
quartz..). This information is for support purposes only.
8.
Product information like serial number, firmware version etc.
9.
All respective software versions of the DTS 4138 components.
20 / 104
800870.13
Status menu page 2:
Display of information with regard to the internal state of the NTP server.
© MOBATIME
21 / 104
800870.13
6.4.1
© MOBATIME
Time information and status
- Internal time of the DTS:
local time
- Stratum and status of the DTS:
current stratum,
status: MASTER, SLAVE, not defined
- Last measured drift:
drift before the last quartz correction
- Last quartz correction:
time of the last quartz correction
- Time source:
current time source
- Offset to source:
offset to source (source – system time)
- Last time info. from source:
time of the last information from source
- Jitter of the source:
current jitter
- Quality of the source:
quality of the source
22 / 104
800870.13
6.4.2
© MOBATIME
Time source information
- Currently measured offset:
last measured offset with source info and type of
measurement (only needed for Moser-Baer
support).
- Last time received DCF:
last time received from DCF source
In (): Information about number of available
satellites (only for GPS 4500 and GNSS 3000).
For DCF, this value is random.
- Sec. counter DCF:
the counter is incremented by 1 with each DCF
pulse. For the minute marker, the counter is set
to 0.
- Last time received link:
last time received from DTS Link
- Sec. counter link:
analogue sec. counter DCF
- NTP – Source:
current time source (system-peer) of the NTP
Server
Antenna = DCF or GPS
- NTP source offset:
current offset of the NTP Server
- NTP source jitter:
jitter of the current source
- NTP source stratum:
stratum of the current source
23 / 104
800870.13
6.5
Configuration menu
Configuring the DTS 4138 through various submenus:
© MOBATIME
1.
Configuring the lines / outputs (DCF/pulse/frequency, serial interfaces,
IRIG/AFNOR/DCF-FSK and NTP slave clock line) See chapter "6.5.1 Lines"
2.
Configuring the time source, time-keeping etc.
See chapter "Fehler! Verweisquelle konnte nicht gefunden werden.6.5.7 Time
handling"
3.
Alarm settings (alarm relay, e-mail, SNMP)
See chapter "6.5.13 Alarm"
4.
General settings of the DTS 4138 (language, time zone for alarms and display,
password for menu, power supply monitoring...)
See chapter "6.5.19 General settings"
5.
Network Settings
See chapter "6.5.20 Network"
6.
Services (switching network services such as FTP, Telnet, SSH on or off)
See chapter "6.5.21 Services (network services FTP, telnet, SSH...)"
7.
SNMP Configuration for GET/ SET.
See chapter "6.5.22 SNMP" (Traps are described in menu ’2. Configuration’ ➔’3.
Alarms’ ➔ ’3. Traps’. See also chapter “6.5.17 SNMP traps“)
24 / 104
800870.13
6.5.1
Lines
Under lines, settings can be undertaken for the following functions:
1
2
3
4
5
DCF - Output
DCF / Pulse / Frequency output
Serial Interface
IRIG / AFNOR / DCF-FSK output
NTP slave clocks / time zone server
6.5.2
➔ see chapter 6.5.2
➔ see chapter 6.5.3
➔ see chapter 6.5.4
➔ see chapter 6.5.5
➔ see chapter 6.5.6
DCF – output
The DTS 4138 is equipped with one DCF output line.
This line is available on the electrical current loop DCF output.
1. Select line function: off or DCF on
2.
© MOBATIME
Select time zone ➔ see chapter 6.5.25 Time zone selection.
25 / 104
800870.13
6.5.3
DCF / Pulse / Frequency output
1.
Select line function: Line switched off, line DCF output, line pulse output, line
frequency output
2.
Select time zone ➔ see chapter 6.5.25 Time zone selection.
3.
Select pulse mode: every second, minute, hour or user-defined.
(Only active with the pulse output function)
4.
Select pulse length in ms (1-500ms)
(Only active with the pulse output function)
5.
User-defined pulse interval (1-3600 sec) only active with pulse type 3 (=user) (the
value is also only then displayed). The pulse always occurs after a multiple of the
pulse interval from the 0 second in the 0 minute, e.g.:
– Pulse interval 960 sec. (16 min.)
➔ Pulse occurs: 00:00:00, 00:16:00, 00:32:00, 00:48:00, 01:00:00, 01:16:00 ...
– Pulse interval 25sec
➔ Pulse occurs: 00:00:00, 00:00:25, 00:00:50, 00:01:15, 00:01:40, 00:02:05 ...
... 00:59:35, 01:00:00, 01:00:25 ...
6.
Output correction (-500ms...+500ms)
7.
Frequency (1Hz to 5MHz)
Important: Only frequencies which fulfill the following requirements are to be used,
otherwise, phase shifts occur:
20'000'000 / frequency = whole number value
Important: Frequencies above 2 MHz are not sent out as a square-wave signal
anymore.
© MOBATIME
26 / 104
800870.13
6.5.4
Serial interface
Serial telegram output via RS232, RS422 or RS485.
1. Select mode:
Line switched off / on
2. Select time zone ➔ see chapter 6.5.25 Time zone selection.
3. Com mode:
1 = send RS 232 (receive is not enabled)
2 = send and receive RS232
3 = send and receive RS485
4 = send RS 422 (receive is not enabled)
4. Baudrate: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400
5. Data bit: 7 or 8
6. Stop bit: 1 or 2
7. Parity: none, even, odd
8. Selecting telegram file changes to the menu “SELECTION OF FILE“
Notice:
To set the parameters, the line type has to be selected first.
Notice:
No flow control available.
The description of the telegram function and the telegram file can be found in Appendix
E Serial Telegrams.
© MOBATIME
27 / 104
800870.13
Selection of the telegram file:
The copy procedure of telegram files is explained in chapter "7.11 Copying Telegram
files to the DTS 4138.timeserver“.
© MOBATIME
28 / 104
800870.13
6.5.5
IRIG / AFNOR / DCF-FSK Output
1. Select mode: see picture below
2. Select time zone ➔ see chapter 6.5.25 Time zone selection.
3. Configuration of the output voltage level (100 – 5500 mV):
The defined voltage corresponds to the expected output amplitude when power
matching (impedance matching) with a load of 50 Ohms is fulfilled. The output
voltage is not controlled, resp. it is not adjusted in case of a load change.
4. Configuration of the output voltage level supervision (0 – 2000 mV):
When the output voltage falls below the defined voltage level, an alarm is released.
Selection line function:
Notice:
© MOBATIME
With the activation of one of this outputs, the modulated and the digital
output are activated at the same time.
Example:
To activate IRIG-B002 output, the Code 01: IRIG-B (B122) has to be set
for the corresponding output.
29 / 104
800870.13
6.5.6
NTP slave clocks / time zone server
NTP slave clock line for operating slave clocks on the LAN (Ethernet). With this clock
line, a world time function can be realized.
1. Mode of clock line: 0 = off, 1 = Send NTP multicast, 2 = Send NTP multicast and
time zone table, 3 = Send time zone table, 4 = Time zones on request, 5 (only for
maintenance) = Send an empty time zone table and return to previous mode.
2. Multicast adress for NTP and time zone server: 239.192.54.x
Group address: x = 1-15 for MOBATIME devices, e.g. NCI, SEN 40.
3. Multicast port for Time zone server (enter an arbitrary value, empty is not allowed!
Value e.g.: 65534). The port is also needed for requesting time zone entries
(mode 4).
4. Poll-interval for NTP Multicast in 2^poll-values in seconds (range: 1 – 16).
E.g. poll-value = 2 ➔ interval: 22 = 4 sec., poll-value = 5 ➔ interval: 25 = 32 sec.
For redundant Multicast time servers see remark next page.
5. Packet time to Live (TTL) for NTP- and time-zone-Multicast-packets in hops.
(Number of Routers in a network to transfer the packets through; for simple network
without routing, enter value "1", for 1 Router enter "2").
6. Repeat time to send time zone table: 10 – 86400 sec.
7. Delay time between the sending of the individual time zone entries (one entry per
Multicast packet) of the table: 1 – 60 sec.
8. Configuration of individual time zone entries. Displays menu “TIME ZONE TABLE“.
© MOBATIME
Notice:
Changes of multicast address, poll interval and TLL lead to a restart of
the NTP server.
Notice:
For the operation of a multicast communication (NTP and Time Zone
Server) the configuration of a gateway is required (see chapter “6.5.20
Network”). The gateway can be set manually or by using DHCP.
If there’s no gateway available, it’s possiible to set the own IP as gateway.
30 / 104
800870.13
Notice:
Redundant Multicast time server:
If two NTP servers in the same network should send NTP with the same
Multicast IP address (redundancy), then the first time server has to be
configured with a small pollinterval (e.g. 2 ➔ 4 sec.) and second time
server with a large pollinterval (min. 100 x larger, e.g. 9 ➔ 512 seconds).
As long as the first time server is sending NTP Multicast packets, the
packets from second time server are ignored. This configuration is
needed, to reach a defined situation for the end devices (the DTS with the
more frequently NTP send rate gets higher priority for time reception).
Time zone table for the NTP slave clock line:
Display of all time zone entries (15) of time zone servers for NTP slave clock lines.
Choose a zone number to change selected zone.
Time zone selection ➔ see chapter “6.5.25 Time zone selection“.
The page can be exited with 99. Changes are first stored or reset on the overlying menu
page.
6.5.7
Time handling
Under time handling, settings can be made for the following functions:
•
Time source configuration ➔ see chapter “6.5.8 Time source “
•
Time adjustment configuration ➔ see chapter “6.5.9 Time adjustment / Timekeeping“
• Redundant operation ➔ see chapter “6.5.10 Redundant operation“
• NTP Server ➔ see chapter "6.5.11 NTP server"
• For setting the time manually ➔ see chapter “6.5.12 Manual time set / Leap second“
© MOBATIME
31 / 104
800870.13
6.5.8
Time source
Time source configuration.
1.
Type of time source:
0=none, 1=DCF low quality, 2=GPS-DCF high quality,
3=NTP, 4=AFNOR-A/C or IRIG-B 12X
2.
Time zone of the source: see chapter 6.5.25 Time zone selection.
3.
Alarm delay at failure of time source (minutes):
0 = off, 1-2'160min, default = 0
Error: “loss of time source TO” resp. “loss of local source”
in redundant mode as slave
4.
DTS stratum:
5.
Stratum limits for alarm: Limits for alarm “Time source stratum lost“ (1-16)
6.
Stratum TO (Timeout):
Duration of stratum change 1 to 16 in the case of time loss (1-999h),
e.g. 24 hrs ➔ stratum counts up from 1 to 16 within 24 hrs.
Default value: 12h
7.
Offset per Stratum in ms (0 – 40’000 ms). Stratum is calculated with this value
when time is received again:
Offset/Stratum = 30 ms, offset of the time source 150 ms ➔ Stratum = 5
8.
Max. offset for time source to set valid time in s at start up.
(0-1’000’000s)
9.
Time source correction (only for DCF), +/-60'000ms
0=Stratum is automatically calculated according to
the time source (see chapter 8.3).
1-15= Stratum is set on a fix value
For description of time source see chapter “8 Time administration“
© MOBATIME
32 / 104
800870.13
6.5.9
Time adjustment / Time-keeping
1. Adjust mode:
0=time is slowly adjusted (without time steps)
1=time is set immediately
2. Maximum catch up speed in ns/s (0-10'000’000).
3. Quartz type:
Standard=0 (0-255)
4. Synch. only offset:
0=off
100-5000ms=Limits as from which time is no longer
accepted ➔ Alarm “Syn only diff too great“
5. RTC mode
0=RTC deactivated
1=ON, with initial time set, independent of the mode (1)
2=ON
Notice:
Explanation to the RTC mode:
RTC mode 0:
After startup of the device the system time starts at 00:00. First of all, the
device has to receive the time from its time source. The time adjust
happens according to the
"1 Adjust mode".
RTC mode 1:
The internal real time clock (RTC) is activated. After startup of the device
the system time is set with the RTC time.
The first takeover of the time from the time source happens in one step,
independent from the Adjust mode (1) setting.
RTC mode 2:
The internal real time clock (RTC) is activated. After startup of the device
the system time is set with the RTC time.
The time takeover from the time source happens according to the Adjust
mode (1).
➔ Adjust mode = 0: time is slowly adjusted
Adjust mode = 1: time is set immediately
Important! For the redundant operation, the RTC mode should be switched off!
For a description of time-keeping and adjustment see chapter “8 Time administration“
© MOBATIME
33 / 104
800870.13
6.5.10 Redundant operation
1.
Mode: 0=single operation
1= redundant operation of 2 DTS 4138 (Master-Slave operation)
2= redundant operation of 2 DTS 4138 (Master-Slave operation) without
LAN communication between the 2 devices.
2.
Stratum limit to switch from slave to master. Standard 16 (1-16)
3.
Max. offset of slaves to the slave time source for triggering the alarm “Offset
Source (Slave)“ (0-5'000'000us)
4.
Port for LAN-Link. default 14338
5.
IP address of the 2nd DTS 4138. Only required if the optical link is not working.
Format 10.241.23.99
ENTER without entering an address will delete the entry.
6.
Manual change from slave to master. The command is effected immediately.
Saving with ’98’ is not required when exiting the menu.
For a description of redundant operation, see chapter “8.11 Redundant operation of 2
DTS 4138.timeservers“
Important! In redundant operation, no NTP servers may be configured as backup
sources.
The redundant operation only works with GPS synchronization!
Important! For the redundant operation, the RTC mode should be switched off!
Important! LAN link in redundant mode:
For the redundant operation with additional LAN link, only the LAN 1 can
be used. If this is not possible, select redundant Mode 2.
The LAN link is only used for internal communication between the two
servers. It is not a redundancy for the optical link.
© MOBATIME
34 / 104
800870.13
6.5.11 NTP server
NTP can run as server or combined as server/client. To run NTP as source (NTP as
client), in the menu ’2. Configuration’ ➔ ’2. Time handling’ ➔ ’1. Time source setting'
➔ ’1. Source type' choose NTP and set at least one server. If NTP server is
configured, but NTP is not indicated as time source, NTP only runs as backup time
source (redundancy) to the actual time source.
The exact behavior of NTP time sources is described in chapter “8.5 Time acceptance
from NTP“.
Further two multicast or broadcast addresses can be configured.
1.-4.
Summary about configured NTP – time sources. Select to configure.
5.-6.
Summary about configured NTP – broadcast addresses. Select to configure.
7.
NTP Authentication: Changes to the menu “NTP AUTHENTICATION"
Information about a multicast – address, configured for NTP slave clocks.
© MOBATIME
35 / 104
800870.13
Configuration of the individual server/peer address is as follows:
1.
Insert time sources (IP address or name, e.g. “ntp.metas.ch”)
ENTER without entry of an address will delete value.
2.-3. Configurations of Minpoll and Maxpoll: Inquiry interval 2^poll value in seconds.
0 = automatically
e.g. poll value=2 ➔ intervall 2: 22 = 4sec., poll value=5 ➔ intervall 5: 25 = 32sec.
Range of poll values (exponent): 1 – 16
To get an exact synchronization it’s better to limit Maxpoll to 6 (64 sec.).
4.
Set type of NTP inquiry: server or peer
5. Preferred source: on or off
6. Authentication key: off, key number, autokey
© MOBATIME
Notice:
If a key number is entered, the entered key must also be added to the
trusted keys.
Notice:
All changes lead to a restart of the NTP server!
Notice:
If NTP only runs as a backup (source DCF or GPS), no NTP source
should be indicated as prefer!
Notice:
Maxpoll should not be selected under 4 (16 sec), as otherwise, internal
trimmung may be inaccurate.
Maxpoll and Minpoll on automatic can lead to insufficient synchronization
accuracy. The specified accuracies were measured with Minpoll = 3 and
Maxpoll = 6.
The configuration server should be used whenever possible.
36 / 104
800870.13
Configuration of the Multi- / Broadcast address is as follows:
1. IP address of the destination network (multicast or broadcast).
ENTER without entering an address will delete the entry.
2. Interval for sending out the NTP information in seconds.
The interval is rounded after the entry to NTP standard, which only permits values
of format 2x: 1,2,4,8,16,32,64... Maximum 65536 seconds.
3. TTL (time to live) in hops. Only required for multicast.
Number of routers over which the multicast packet should be transmitted: for
simple networks without a router - enter 1, for 1 router - enter value 2.
4. Authentication key: off, key number, autokey
Notice:
© MOBATIME
All changes lead to a restart of the NTP server.
37 / 104
800870.13
Configuration of the NTP authentication:
The NTP authentication is described in chapter "8.10 NTP Authentication“.
1.
Import keys (from /ram directory)
The file ntp.keys must first be copied into the directory /ram.
Notice:
The file must be named exactly in this way and written entirely in small
letters.
2.
Export keys (to /ram directory)
The current ntp.keys file is written in the directory /ram.
3.
Select the trusted keys separated by commas or space
4.
Select the request key
5.
Select the control key
6.
Set the auto key password
7.
Execute for auto key commands:
gen_iff
generate the IFF certificate
gen_gq
generate the GQ certificate
gen_mv*
generate the MV certificate
gen_all*
generate all (IFF,GQ,MV) certificates
gen_client
generate the client certificate
update_server update the server certificate
update_client update the client certificate
export_iff
export the IFF server certificate to /ram. Parameter password
of the client
export_gq
export the GQ server certificate to /ram.
export_mv*
export the MV server certificate to /ram.
import_iff
import the IFF server certificate from /ram.
import_gq
import the GQ server certificate from /ram.
import_mv*
import the MV server certificate from /ram.
clear_ram
delete the certificates in /ram
clear_keys
delete the certificates in the NTP key directory
Example: export_iff myPassword exports the IFF client certificate to /ram.
*MV schema is currently not available
© MOBATIME
38 / 104
800870.13
6.5.12 Manual time set / Leap second
1. Set UTC time in the format “hh:mm:ss DD.MM.YY“.
Time is set with ENTER!
2. Correct time in ms (- = backwards). Range: +/-10'000ms
Time is set with ENTER!
3. Leap second mode:
0
off
1
Additional second will be inserted at entered time
Is set to 0=off after inserting the leap second.
-1
Second will be left out at entered time
Is set to 0=off after inserting the leap second.
2
Recognize leap second automatically. Only possible with a source with leap
second announcement!
4. Set UTC time of leap second in format: “hh:mm:ss DD.MM.YY“
For a description of the leap second, see chapter “8.9 Leap second“
6.5.13 Alarms
Under alarms, settings can be undertaken for the following functions:
© MOBATIME
•
Alarm relay ➔ see chapter 6.5.14
•
E-mail ➔ see chapter 6.5.16
•
SNMP traps ➔ see chapter 6.5.17
•
Alarm input ➔ see chapter 6.5.18
39 / 104
800870.13
6.5.14 Alarm relay
1. Alarm mask for relay (see chapter "Fehler! Verweisquelle konnte nicht gefunden
werden. Alarm mask")
6.5.15 Alarm mask
Display of all the DTS 4138 alarms (64) on 4 pages. Pages can be scrolled through with
ENTER.
An alarm on the current page can be switched on or off by entering an error number. The
page can be exited with 99. The modifications will be saved or restored one menu level
higher in “ALARM CONFIGURATION“. All Alarms with “error bitxx“ are not yet used.
A description of individual errors can be found in appendix "C Alarm list".
The alarm masks for the various applications (E-mail, SNMP, SNMP Traps, alarm relay)
can differ.
© MOBATIME
40 / 104
800870.13
6.5.16 E-mail
1.
E-mail function on or off.
2.
Alarm mask for e-mail notifications (see chapter "Fehler! Verweisquelle konnte
nicht gefunden werden. Alarm mask")
Changes are stored or reset on the overlying menu page “MAIL
CONFIGURATION“.
3.
IP address of the mail server e.g. 10.249.34.5
ENTER without entering an address will delete the entry.
4.
Mail server port (often 25)
5.-6. Destination e-mail address.
ENTER without entering an address will delete the entry.
7.
Reply address (e.g. support, administrator...)
ENTER without entering an address will delete the entry.
8.
Sender address (important for authentication through the mail server)
ENTER without entering an address will delete the entry.
Press ENTER to change to page 2.
Notice:
© MOBATIME
Configuration of a gateway is required for sending e-mails (see chapter
"6.5.20 Network"). This can be set via DHCP or manually.
41 / 104
800870.13
E-mail configuration page 2:
11. Authentication mode:
0=off (sender e-mail address used for authentication)
1=auto (tries CRAM-MD5, LOGIN- PLAIN in this sequence)
2=PLAIN
3=LOGIN
4=CRAM-MD5
12. User name (only for authentication mode 1-4)
13. Password (only for authentication mode 1-4)
Press ENTER to change to page 1.
Format of an error message via E-mail:
Event <Alarm 03 set: Power failure 1>
Time <11:26:45 10.01.07>
Hostname <DTS4138 (10.241.0.30)>
© MOBATIME
42 / 104
800870.13
6.5.17 SNMP traps
For a description of SNMP functionality, see also chapter “9 SNMP“. Traps are also
designated as notifications (from SNMP V2)
1. Trap mode on or off (applies to alarm and alive traps)
2. Alarm mask for SNMP trap messages (see chapter "Fehler! Verweisquelle
konnte nicht gefunden werden. Alarm mask")
Changes are first stored or reset on the overlying menu page “SNMP TRAP
CONFIGURATION“.
3. Trap community string (group membership for traps).
Standard: trapmobatime.
4. Configuration of the receiving system (trap sink) 1
5. Configuration of the receiving system (trap sink) 2
6. Time period for alive messages in seconds. 0 = no alive traps are sent
Range: 1-7'200sec
© MOBATIME
Notice:
General settings for SNMP can be found in menu ’2. Configuration’ ➔
’7. SNMP’. See also chapter "6.5.22 SNMP").
Notice:
Configuration of a gateway is required for sending SNMP traps (see
chapter 6.5.20 Network). This can be set via DHCP or manually.
Notice:
Each configuration change leads to a restart of the DTS SNMP Agent.
43 / 104
800870.13
Configuration of the receiving systems
1. Address of the evaluation system e.g. 10.240.0.9.
ENTER without entering an address will delete the entry.
2. Port of the evaluation system (usually 162).
3. SNMP Version: 1=SNMP V1, 2=SNMP V2c
Notice:
Each configuration change leads to a restart of the DTS SNMP Agent.
6.5.18 Alarm input
Description of the functionality of the alarm input.
1. Mode off, on or inverted.
© MOBATIME
44 / 104
800870.13
6.5.19 General settings
© MOBATIME
1.
Setting the display language
2.
Setting the time zone for the display, and also all alarm logs, e-mail and SNMP.
(See chapter 6.5.25 Time zone selection).
3.
Power:
0=simple power, 1=redundant power
(See chapter “10 Power supply alternatives“)
4.
Enter password for the menu (user dts) (max. 15 characters).
A password must be configured.
45 / 104
800870.13
6.5.20 Network
1.
Configuration of IPv4 parameters LAN 1
2.
Configuration of IPv6 parameters LAN 1
3.
Set network interface LAN 1: Auto, 100/10Mbit, half, full duplex.
4.
Configuration of IPv4 parameters LAN 2
5.
Configuration of IPv6 parameters LAN 2
6.
Set network interface LAN 2: Auto, 100/10Mbit, half, full duplex.
7.
Set host name.
Notice:
8.
A host name must always be configured.
Host names and their format are described in the Internet standards RFC
952 and RFC 1123:
Domains and host names may only contain letters (capitals or small
letters) and numerals ("0-9"). In addition, the minus sign ("-") may also be
used, as long as it is not at the end.
Everything else is not permitted!
Set domain e.g. test.org
View of the current network state in Menu: ‘1 Status’ ➔ ‘6 Info network config.'
© MOBATIME
Notice:
The menu is closed upon modifying the IP or the DHCP mode.
Notice:
DHCP on/off, each change of this setting will result in a restart of the NTP
server!
Notice:
For the operation of a Multicast communication (NTP and Time Zone
Server) the configuration of a gateway is mandatory. The gateway can
be set manually or by using DHCP. If no gateway is available, the own IP
address can be used.
Notice:
Only one DNS server should be configured (IPv4 or IPv6).
46 / 104
800870.13
Notice:
Modifications to the network must be coordinated with the network
administrator!
Notice:
The LAN 1 gateway has priority compared to the LAN 2 gateway!
Notice:
If only one LAN interface is used, it always has to be LAN 1!
Notice:
The two LAN interfaces may not be configured in the same network
(subnet)!
Network configuration IPv4:
1.
DHCP on or off, the following fields are not available in case of DHCP = on.
A DHCP renew can also be triggered via this point.
Notice:
DHCP on, if no DHCP server is available, leads to longer start-up time
(<75 sec.) of the DTS.
2.-5. Set IP address, subnet mask, gateway and DNS server. Format = 10.240.98.7
© MOBATIME
47 / 104
800870.13
Network configuration IPv6:
1.
Autoconf on or off
2.
DHCPv6 on or off
3.
IP address with prefix in IPv6 format
e.g. 2001:2345:6789::12:1:34/64
4.
Gateway in IPv6 format
5.
IPv6 DNS server
6.5.21 Services (network services FTP, telnet, SSH...)
Network services configuration:
1.-3. Switch the individual services off or on.
© MOBATIME
48 / 104
800870.13
6.5.22 SNMP
For a description of SNMP functionality, see also chapter “9 SNMP“.
1.
Mode. 0=off, 1= V1 + V2c + V3, 2=V2c + V3, 3=V3 only
The MIB 2 SNMP information is also available with "Mode = off"
Notice:
To send out MIB-2 traps, the trap community and the destination address
must at least be configured in menu ’2. Configuration’ ➔ ’3. Alarms’➔ ’3.
Traps’. See also chapter “6.5.17 SNMP traps".
2. Alarm mask for SNMP status (see chapter "6.5.15 Alarm mask"). The modifications
will be saved or restored one menu level higher in “SNMP CONFIGURATION“.
3. DTS Location information, which is displayed in SNMP management tool.
4. Contact information, which is displayed in SNMP management tool.
5. Configuration of SNMP V1 / V2 c (specific settings). See chapter “6.5.23 SNMP V1
/ V2c“
6. Configuration of SNMP V3 (specific settings). See chapter “6.5.24 SNMP V3“
Notice:
© MOBATIME
Each configuration change leads to a restart of the DTS SNMP Agent.
49 / 104
800870.13
6.5.23 SNMP V1 / V2c
1. Community string for read only (Group membership for GET).
Standard: romobatime.
2. Community string for read/write (Group membership for GET/PUT).
Standard: rwmobatime.
Notice:
© MOBATIME
Each configuration change leads to a restart of the DTS SNMP Agent.
50 / 104
800870.13
6.5.24 SNMP V3
1. – 2.
3. – 4.
Configuration of user-defined SNMP accounts dtsUser1 and dtsUser2
Configuration of user-defined SNMP access rights viewDTS1 and viewDTS2
Notice:
Each configuration change leads to a restart of the DTS SNMP Agent.
User configuration SNMP V3:
1. Password for authentication (MD5) and privacy (DES). 8 – 40 characters.
© MOBATIME
2. Minimal security level:
1=noauth (no authentication)
2=auth (only authentication)
3=priv (authentication and privacy)
3. SNMP read access:
0=none (no access)
1=all (full access)
2=DTS info (only DTS specific information)
3=user defined 1 (viewDTS1)
4=user defined 2 (viewDTS2)
51 / 104
800870.13
4. SNMP write access
Notice:
0=none (no access)
1=all (full access)
2=DTS info (only DTS specific information)
3=user defined 1 (viewDTS1)
4=user defined 2 (viewDTS2)
Each configuration change leads to a restart of the DTS SNMP Agent.
Access configuration SNMP V3:
1. - 3. Include View path, form: .1.3..6.1.4.1.13842.4 (e.g. DTS) or .iso
(complete SNMP ISO path).
4. - 6. Exclude View path: analogue include.
Notice:
© MOBATIME
Each configuration change leads to a restart of the DTS SNMP Agent.
52 / 104
800870.13
6.5.25 Time zone selection
Display of all the DTS 4138 time zones (100) over several pages. The pages can be
scrolled through with ENTER.
A time zone can be selected on the current page by entering a time zone number.
Only one time zone can be selected.
A * indicates the selected time zone.
Press ESC to leave the page. The modifications will be saved or restored one menu level
higher.
© MOBATIME
53 / 104
800870.13
6.6
Maintenance menu
1. Initiating a software update (files must have been copied by FTP into the directory
/ram of the DTS 4138 before). ➔ See chapter "7 Updates".
The command always leads to a restart of the DTS 4138 (even if no files were
copied for update).
Notice:
Possibly save configuration first.
2. Initiate a software update (files must first be put on to a USB stick in the DTS 4138).
➔ See chapter "7 Updates". The command always leads to a restart of the DTS 4138
(even if no files were copied for update)
Notice:
Possibly save configuration first.
3. Save the entire configuration (incl. telegram files) and the log files on a USB stick .
Also generates a diagnosis file (dts4138system_xxxxxxxxxxxx.log) in the directory
/ram which is also copied on to the USB stick or which can be downloaded per FTP
(only for support).
4. Backup the entire configuration locally (➔ file dts4138.conf.bkp is created).
5. Restore the entire configuration from a backup stored locally.
6. Restore the entire configuration to factory settings.
7. Restart DTS 4138.
8. Copy telegram files onto the DTS 4138.
➔ See chapter "7.11 Copying Telegram files to the DTS 4138.timeserver".
See also chapter "7 Updates".
© MOBATIME
54 / 104
800870.13
7
Updates
7.1
Important information about the update procedure
The current firmware version can be downloaded from the following web page:
https://www.mobatime.com/support/resources/
Enter the product name (e.g. "4138") in the search field, then select the "Firmware" tab.
Caution:
!
Before updating, be sure to open the CHANGELOG and follow the
instructions. See also below.
To ensure that nothing is lost during the update, always make a backup of
the configuration first.
Caution!
We recommend to always update all images.
Update procedure from older versions:
It is mandatory to follow the procedure below, otherwise the device may stop working
and have to be sent to the factory for repair!
<= V 07
V 08
V 09
V 10
Older Vers.
26082020
26102021
29032022
Step 1:
dtscheck.md5
rootfsDTS 4138.img
uImageDTS 4138
dts4138app.img
Step 2:
dtscheck.md5
dts4138cfg.img
© MOBATIME
55 / 104
800870.13
7.2
Updating images with MOBA-NMS
Steps for updating images using MOBA-NMS:
1. Select DTS device(s) in the device view.
2. Menu ‘Edit‘ ➔ ‘Commands‘ ➔ Select ‘Firmware Update…‘.
3. Enter the path to the file ‘dtscheck.md5‘ or select it using the ‘Browse…‘ button.
4. Enter further paths to images or select them using the ‘Browse…‘ button.
5. Optionally: Check the box ‘Backup device(s) configuration before update‘ and enter
the destination directory for the backup file(s). If a destination folder is selected, the
whole device configuration will be saved before the backup. Additionally, if the
image ‘dts4138cfg.img‘ or ‘dts4138v2cfg.img’ is written too, the saved configuration
can be automatically restored after the update. For this, check the box ‘restore
configuration after update‘.
6. By clicking the ‘OK‘ button, the update is initiated.
Important: The update procedure (item 6) can take some time (<5 min.) and may not
be interrupted under any circumstances. In case of an interruption, the
software on the DTS 4138 is destroyed and can only be repaired in the
factory.
7.3
Updating images with FTP
Possible images are: u-bootDTS4138, rootfsDTS4138.img, uImageDTS4138,
dts4138app.img, dts4138cfg.img or dts4138v2cfg.img. Additionally the files
dtscheck.md5 (old firmware) or firmwareDTS4138.sign and firmwareDTS4138.sha256
must exist. ➔ all file names are case-sensitive.
Steps for updating images:
1. Connect a FTP client software to the DTS 4138 e.g. with Windows file Explorer
enter: ftp://dts@[IP address]) (as user dts).
See also chapter
2. If an update of the image dts4138cfg.img or dts4138v2cfg.img is made, the
configuration of the DTS 4138 and the telegram files may be overwritten. In order to
store the configuration, the file dts4138.conf from the directory /etc and any
possible telegram files must be saved from the directory /var/local/dts. After the
update, the file can again be written on the DTS 4138 in accordance with chapter
“7.4 Updating applications or configurations with FTP“.
3. Change to the directory /ram.
4. Copy the image into the directory /ram.
5. Close FTP connection.
6. The update procedure can be started on DTS 4138 by selecting the menu '3.
Maintenance' ➔ ’1. Update software (FTP)’ and press ENTER. The message
"Update in progress" appears and at the same time, “Please wait!>“ is shown in
the command line. All images are copied. The DTS 4138 is automatically restarted
on completion of the update.
The Telnet or SSH session has to be restarted.
© MOBATIME
56 / 104
800870.13
Notice:
The update procedure (point 6) may take some time depending on the
type and number of images (<5 min) and must not be interrupted under
any circumstances. If interrupted, the software on the DTS 4138 will be
destroyed and the DTS 4138 has to be returned to the manufacturer for
repairing.
Starting up after an update can also take some minutes (<10 min), or it can result in an
additional restart, as the file systems have to be checked first.
To eliminate any mistakes during update procedure, the versions should be verified
after the update.
7.4
Updating applications or configurations with FTP
To update individual files such as, e.g. dts4138app, dts4138menu, ntpd, dts4138mod.ko,
dts4138.conf, etc. on the DTS 4138, the following steps are carried out
➔ all file names are case-sensitive:
1. Connect a FTP client software to the DTS 4138 e.g. with Windows file Explorer enter:
ftp://dts@[IP address]) (as user dts). See also chapter 7.7 FTP connection
2. Change to the directory /ram.
3. Copy all the files to be updated into the directory /ram.
4. Close FTP connection.
5. The update procedure can be started on DTS 4138 by selecting the menu '3.
Maintenance' ➔ ’1. Update software (FTP)’ and press ENTER.
The message "Update in progress" appears and at the same time, “Please wait!>“
is shown in the command line. All images are copied. The DTS 4138 is
automatically restarted on completion of the update.
The Telnet or SSH session has to be restarted.
Notice:
The update procedure (point 5) may take longer time depending on the
type and number of images (<5 min) and must not be interrupted under
any circumstances. If interrupted, the software on the DTS 4138 will be
destroyed and the DTS 4138 has to be returned to the manufacturer for
repairing.
To eliminate any mistakes during update procedure, the versions should be verified
after the update.
7.5
Updating images via USB
Possible images are: u-bootDTS4138, rootfsDTS4138.img, uImageDTS4138,
dts4138app.img, dts4138cfg.img or dts4138v2cfg.img. Additionally the file
dtscheck.md5 (old firmware) or firmwareDTS4138.sign and firmwareDTS4138.sha256
must exist. ➔ all file names are case-sensitive.
Steps for updating images:
1. Copy images to the USB stick
2. Plug the stick in the DTS 4138
Important: USB stick plugged in:
Do NOT press the red button, after insering the USB stick.
Start update, before main display appears again (timeout).
3. If an update of the dts4138cfg.img or dts4138v2cfg.img image is made, the
configuration of the DTS 4138 and the telegram files may be overwritten. In order to
store the configuration, the file dts4138.conf from the directory /etc and any
possible telegram files must be saved from the directory /var/local/dts. After the
© MOBATIME
57 / 104
800870.13
update, the file can again be written on the DTS 4138 in accordance with chapter
“7.4 Updating applications or configurations with FTP“.
4. The update procedure can be started on DTS 4138 by selecting the menu '3.
Maintenance' ➔ ’2. Update software (USB)’ and press ENTER.
The message "Update in progress" appears and at the same time, “Please wait!>“
is shown in the command line. All images are copied. The DTS 4138 is
automatically restarted on completion of the update.
The Telnet or SSH session has to be restarted.
5. As soon as the DTS 4138 is restarted, remove the USB stick.
Notice:
The update procedure (point 4) may take longer time depending on the
type and number of images (<5 min) and must not be interrupted under
any circumstances. If interrupted, the software on the DTS 4138 will be
destroyed and has to be returned to the manufacturer for repairing.
Starting up after an update can also take some minutes (<10 min), or it can result in an
additional restart, as the file systems have to be checked first .
To eliminate any mistakes during update procedure, the versions should be verified
after the update.
7.6
Updating applications or configurations via USB
To update individual files, e.g. dts4138app, dts4138menu, ntpd, dts4138mod.ko,
dts4138.conf, etc. on the DTS 4138, the following steps are carried out
➔ all file names are case-sensitive, all names with 4138:
1.
Copy applications (or configuration) to the USB stick
2.
Plug the stick in the DTS 4138
Important: USB stick plugged in:
Do NOT press the red button, after insering the USB stick.
Start update, before main display appears again (timeout).
3.
The update procedure can be started on DTS 4138 by selecting the menu '3.
Maintenance' ➔ ’2. Update software (USB)’ and press ENTER.
The message "Update in progress" appears and at the same time, “Please wait!>“
is shown in the command line. All applications are copied. The DTS 4138 is
automatically restarted on completion of the update.
The Telnet or SSH session has to be restarted.
4.
As soon as the DTS 4138 is restarted, remove the USB stick.
Notice:
The update procedure (point 3) may take longer time depending on the
type and number of images (<5 min) and must not be interrupted under
any circumstances. If interrupted, the software on the DTS 4138 will be
destroyed and the DTS 4138 has to be returned to the manufacturer for
repair.
To eliminate any mistakes during the update procedure, the versions should be verified
after the update.
Important: USB stick recognition:
After removing the USB stick, wait approx. 1 min. before re-inserting the it
again. Otherwise it can be, that the USB stick is not recognized.
© MOBATIME
58 / 104
800870.13
7.7
FTP connection
Establish anonymous connection:
ftp://“IP address of DTS 4138“
to directly reach the sub-directory /ram, e.g. Windows file Explorer ftp://10.241.0.5
Establish connection as/with a user:
ftp://dts@“IP address of DTS 4138“.
e.g. with Windows file Explorer enter: ftp://[email protected]
Password: dts resp. the defined password for the menu.
To directly reach the sub-directory /ram, you can also enter
ftp://[email protected]/ram.
Establish connection with IPv6:
The address must be written in brackets [ ]:
e.g. with Windows file Explorer enter: ftp://dts@[fd03:4432:4646:3454::2000]
Notice:
The file has to be copied in binary mode (not ASCII).
FTP tools
Windows 8, 10, 11
Linux (Suse, Redhat)
Integrated in the system
(file manager):
Windows file Explorer
Start ➔ Execute: Explorer
Konqueror / Dolphin
Programs (examples)
CuteFTP
Kbear
7.8
SFTP connection
SFTP = SSH File Transfer Protocol
SFTP tools
Windows 8, 10, 11
Linux (Suse, Redhat)
Integrated in the system
(file manager):
-
Konqueror / Dolphin
Programs (examples)
WinSCP
-
© MOBATIME
59 / 104
800870.13
7.9
SCP connection
SCP = Secure Copy Protocol
Notice:
SCP connection can only be established when no menu (operation) is
open.
The following error message can be ignored. There is no influence in the functionality of
the operation:
Command 'groups'
failed with termination code 127 and error message
-sh: groups: not found.
SCP tools
Windows 8, 10, 11
Linux (Suse, Redhat)
Integrated in the system
(file manager):
-
With command line
Programs (examples)
WinSCP
-
7.10
Save Configuration externally
(for backup or copy to another DTS 4138)
Save the current configuration via MOBA-NMS:
1.
Select DTS device in the device view.
2.
Menu ‘Edit‘ ➔ Select ‘Backup configuration…‘.
3.
Select the elements that are to be saved. (In case of doubt, select everything)
4.
Click button ‘Next >‘.
5.
Indicate destination file by clicking the ‘Browse…‘ button.
6.
Optionally: enter a free backup comment. E.g. reason for the backup, use, etc. This
comment will then be shown during the restoration of the backup.
7.
By clicking the ‘Finish‘ button, the backup is created.
8.
At the end of the backup, an overview of the process is shown. It shows which
elements were saved and which ones are not available or could not be saved.
Save the current configuration via FTP:
© MOBATIME
1.
Connect a FTP client software to the DTS 4138 (with Windows file Explorer enter:
ftp://dts@“IP address“) (as user dts).
2.
Change to the DTS 4138 directory /etc.
3.
Save the file dts4138.conf (configuration) to the user PC (e.g. copy the file to the
Desktop or to the directory My Documents).
4.
Additionally also save possible telegram files from the directory /var/local/dts.
60 / 104
800870.13
Save the current configuration via USB-Stick:
The whole procedure can be analogously done with an USB stick.
The copy procedure to the USB stick can be started on DTS 4138 by selecting the
menu '3. Maintenance' ➔ ’3. Backup configuration and log to USB’ and press ENTER.
All files (including telegram files) will be copied into the root directory of the USB stick.
Copy configuration to another DTS 4138:
In order to copy the entire configuration or elements of it from a DTS device to another,
the according assistant in MOBA-NMS can be used. For this, select the source device
(from which the configuration shall be transferred) and start the assistant in the menu
‘Edit‘ ➔ ‘Transfer configuration…‘. It will lead you through the individual steps.
Without MOBA-NMS, perform the procedure explained in chapter 7.4 resp. 7.6.
Notice:
7.11
When copying the configuration from one DTS 4138 to an other, the IP
address may have to be changed after the download.
Copying Telegram files to the DTS 4138.timeserver
Analogously to the previously described procedures telegram files can be copied via FTP
or USB stick to the DTS 4138.
The copy procedure can be started on DTS 4138 by selecting the menu
'3. Maintenance' ➔ ’8. Copy telegram-files' and press ENTER. Afterwards, select again
in the menu “6.5.4 Serial interface“ and reload.
The files are stored in the directory /var/local/dts and can be deleted or copied via
FTP.
Special case USB stick:
If the DTS recognizes the insertion of an USB stick, it is shown on the display. By
pressing the red button the copy procedure can be released (analogously to the above
described procedure). The button has to be pressed until the copy procedure is started.
Management with MOBA-NMS:
With MOBA-NMS, the files do not need to be copied manually via FTP or USB stick,
since this is already integrated in the MOBA-NMS operation. At every file selection, the
‘Change…‘ link can be clicked. This opens a file dialog which shows all files and allows
new files to be loaded onto the device or existing ones to be deleted.
Example of a program file choice:
© MOBATIME
Link for opening the file
dialog for editing the file list.
Notice:
After the file copy procedure, the output of the telegram files are re-started
(take over of the files).
Notice:
The file name is limited to 8 characters before the dot, e.g. IF482Std.tel
61 / 104
800870.13
8
Time administration
8.1
Concept of time administration
The internal master clock as well as the real-time clock runs with UTC (Universal Time
Coordinated). The synchronisation inputs, the time shown on the display, as well as all
outputs are linked via a time zone entry with the master clock time, i.e. all inputs and
outputs can be individually allocated to a specific time zone.
External DCF
Time source
External AFNOR A/C
IRIG-B12x source
*
(A)
NTP
Time zone entry
- Display
- Operation
- Error report
(G)
Time zone entry
UTC
Hauptuhr
(F)
LAN Multicast
Devices
(B)
Time zone entry
Time zone entry
DCF Main
(C)
(E)
Time zone entry
Time zone entry
Serial Telegrams
Line
(D)
Time zone entry
DCF
Line
IRIG / AFNOR
Line
Configurable time zones:
© MOBATIME
(A)
chapter 6.5.8 Time source
(B)
chapter 6.5.2 DCF – output
(C)
chapter 6.5.3 DCF / Pulse / Frequency output
(D)
chapter 6.5.5 IRIG / AFNOR / DCF-FSK Output
(E)
chapter 6.5.4 Serial interface
(F)
chapter 6.5.6 NTP slave clocks / time zone server
(G)
chapter 6.5.19 General settings
*
NTP is always UTC
62 / 104
800870.13
8.2
Time acceptance
Variants of time synchronization
• Adjusting:
After starting the DTS 4138, the time is set for a first time (from source or manually).
Afterwards, the time will only be aligned with maximum adjusting speed if deviating
from the source ➔ no time steps possible.
Configuration: see chapter “6.5.9 Time adjustment / Time-keeping“
• Setting:
Time deviations are always corrected in full immediately: Seconds are set
immediately; partial seconds are corrected with 50ms/s.
Manual time set:
• The time is always set immediately. The stratum is set to 1 or pre-set to a fix
stratum. If new source time information is available, the time will be adjusted again
and the stratum set accordingly.
8.3
Time acceptance from an external source (DCF or GPS)
Acceptance from an external source (DCF input):
• At least 2 minutes reception (DCF-GPS) is required, before the NTP server is
available.
Time source stratum = 0 ➔ stratum of the DTS 4138 = 1
Stratum normal, synchronized operation:
• The stratum value behaves as follows for synchronization from the time source:
If St_fix > 0: then stratum = St_fix (particularly for manually set time) applies
If St_fix = 0: then stratum = 1
Stratum in case of error:
• The stratum value behaves as follows in the case of external time source loss:
If St_fix > 0: then stratum = St_fix applies
If St_fix = 0:
then stratum = MIN((t_current - t_lastsynch)/(To * 255), St_max) applies
• Adjusting the clock after identifying a leap in time:
If St_fix > 0:
then stratum = St_fix applies
If Tst > 0 AND St_fix = 0:
then stratum = MIN(Tdiff/Tst, St_max) applies
If Tst = 0 AND St_fix = 0:
then stratum = 1 (auto) applies
Legend:
To:
St_fix:
St_max:
t_current [s]:
t_lastsynch [s]:
Tst:
Tdiff:
© MOBATIME
Stratum TO <0-16>, Stratum error timeout time 1-999 [h], for loss
of the external source
0..15, configurable stratum, 0 = auto
1..16, configurable stratum, 0 = auto
current time
time of the last synchronization
Offset per stratum, 0..40'000 [ms], parameter time deviation for
stratum alteration by 1
current time difference in ms
63 / 104
800870.13
8.4
Time acceptance from external AFNOR-A/C, IRIG-B12x source
The stratum value is calculated same as with DCF/GPS synchronization (chapter 8.3).
As IRIG-B120 to 123 time codes do not provide information about the current year, the
DTS 4138 has to be synchronized first from another time source or the date has to be
set manually. The DCF input and the IRIG input cannot be used at the same time for
the synchronization (redundant time source with DCF and IRIG synchronization is not
possible).
AFNOR and IRIG-B126 contains the time and date information.
Attention:
8.5
After more than 5 days without power, the DTS 4138 loses the date
information. When synchronized with IRIG-B120 to 123 it has to be set
again manually.
Time acceptance from NTP
Acceptance:
• As NTP RFC 1305, RFC 5905 (www.ntp.org)
(see http://ntp.isc.org/bin/view/Servers/WebHome for internet-server)
Stratum in normal, synchronized operation:
• Stratum value of DTS is always one step higher than that of the current NTP time
server
Stratum in case of an error
• As NTP RFC 1305, RFC 5905 (www.ntp.org)
8.6
NTP as backup
If DTS 4138 is synchronized with a DCF or GPS source, the NTP can be used as
redundancy source. This function is active, as soon as at least one timeserver is
configured in menu ‘2. Configuration’ ➔ ‘2. Time handling ➔ ‘4. NTP server’).
Stratum in normal, synchronized operation:
• Equal Stratum value “Time Acceptance from an external source (DCF or GPS)”
Behavior in case of an error:
• Failure of primary Source:
"St. exp": Means: Expected NTP Stratum of the NTP sources
"St. exp" = MAX(Stratum NTP candidates)
➔ Means: "St. exp" contains the stratum value of the poorest NTP source.
If internal Stratum > "St. exp" + 1, then change to NTP as source takes place
(internal stratum is one step higher than that of the poorest available NTP source).
• As soon as the primary source is available again, the changes are set back.
8.7
Time server
• NTP v4 (compatible with v3) as per RFC 1305, RFC 5905 (Port 123)
• SNTP (UDP), RFC 2030 (Port 123)
• TIME (TCP/UDP), RFC 868 (Port 37)
• DAYTIME (TCP/UDP), RFC 867 (Port 13)
© MOBATIME
64 / 104
800870.13
8.8
Time accuracy, time-keeping
See appendix H Technical data.
8.9
Leap second
The announcement of the switching second is put out by DCF and NTP* each time 1
hour before the defined time.
*The announcement is only sent via NTP if a DCF or IRIG source is active. If only one
NTP source is configured, the state of this source is passed on.
Automatic mode
In the automatic mode, the source (DCF or NTP) is checked for a possible
announcement during 1 hour prior to the moment of a possible leap second. If the
announcement is recognized, it is passed through the NTP and DCF outputs and the
leap second is inserted.
The leap second can be inserted at 2 moments per year: 00:00:00 1.1. or 00:00:00 1.7.
each in UTC. Whether a leap second is inserted is decided by the organization IERS
(http://www.iers.org) each time up to half a year in advance.
8.10
NTP Authentication
NTP provides two variants for authentication in version 4:
•
•
NTP symmetric keys (i.e. symmetric keys)
NTP autokeys
NTP authentication assures a correct time source and prevents manipulation of NTP
information. NTP data itself is, however, not encoded.
8.10.1 NTP symmetric keys
A 32-bit key ID and a cryptographic 64/128-bit check sum of the packet is attached to
each NTP IP packet.
The following algorithms are used for this purpose:
• Data Encryption Standard (DES)
(partly restricted in North America and no longer integrated into new NTP variants
(>V4.2))
• Message Digest (MD5)
The DTS 4138 only supports the MD5 procedure.
The receiving NTP service calculates the check sum with an algorithm and compares it
with the one contained in the packet. Both NTP services must have the same
encryption key and the same corresponding key ID for this purpose.
Packets with a wrong key or wrong check sum will not be used for synchronization .
The DTS 4138 must be correspondingly configured to be able to use NTP
authentication (chapter 6.5.11 NTP server). The NTP service of the other equipment
(e.g. server, PC...) must also be configured. In the case of standard NTP, this occurs
via the ntp.conf file:
# path for key file
keys /etc/ntp/ntp.keys
trustedkey 1 2 3 4 5 6# define trusted keys
requestkey 4 # key (7) for accessing server variables
controlkey 5 # key (6) for accessing server variables
© MOBATIME
65 / 104
800870.13
server ntp1.test.org key 2
server ntp2.test.org key 6
server 192.168.23.5 key 3
The description of the ntp.conf file can be accessed via the corresponding man-page,
or consulted at http://www.eecis.udel.edu/~mills/ntp/html/authopt.html
The authentication mode is automatically activated when a key is used and the paths
for the keys have been correspondingly configured.
trustedkey defines all keys currently permitted
requestkey defines the key for the ntpq help tool.
controlkey defines the key for the ntpdc help tool.
The keys are located in the ntp.keys file defined with keys. This has the following
format:
1
M
2
M
15 M
498 M
TestTest
df2ab658
I_see!
NTPv4.98
The key ID is in the first column of the file, the format of the keys in the second defined
column, and the key itself in the third. There are four key formats, however, nowadays
only the MD5 is still used ➔ M. The letter M is no longer written for new NTP variants
(>V4.2) and is only necessary for backwards compatibility.
The signs ' ', '#', '\t', '\n' and '\0' are not used in the MD5 ASCII key! Key 0 is reserved
for special purposes and should therefore not be used here.
ntp.keys:
man page for ntp.keys to be noted (check the internet)
8.10.2 NTP Autokey
The validity of the time received to the NTP clients is assured by symmetric keys. For a
higher degree of certainty, exchanging the keys used regularly is, however, necessary
to obtain protection, e.g. from replay attacks (i.e. attacks in which recorded network
traffic is simply played back).
The autokey procedure was introduced as the exchange is very involved in a large
network. A combination of group keys and public keys enables all NTP clients to check
the validity of the time information which they receive from servers in their own autokey
group.
NTP Autokey is relatively complex in its use and studying the functionality is definitely
necessary beforehand.
Autokey is descrbied at http://www.cis.udel.edu/~mills/proto.html or on the NTP
homepage http://www.ntp.org.
Autokey is currently defined in an IETF draft.
http://www.ietf.org/internet-drafts/draft-ietf-ntp-autokey-04.txt
The configuration of Autokey is explained in
http://support.ntp.org/bin/view/Support/ConfiguringAutokey or in
http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm#S-CONFIG-ADV-AUTH.
© MOBATIME
66 / 104
800870.13
8.11
Redundant operation of 2 DTS 4138.timeservers
For redundant operation two DTS 4138 devices are synchronized via optical fibers. For
this purpose, a mini GBIC module is plugged into both devices and connected via optical
fibers (see Appendix H Technical data):
mini GBIC module
Both devices must have a GPS receiver in redundant operation. Both devices are
configured for the redundant mode, but are basically equal and work out the master/slave
role among themselves. The slave is always synchronized to the master in operation.
The slave supervises the system time on the basis of its own GPS time and generates
an error message, should the time difference amount exceed the configurable value of
n milliseconds.
GPS
receiver
NTP
DTS Master
status, time
GPS
receiver
LWL connection (DTS Link)
(option for redundant
operation)
Ethernet
status, time
NTP
DTS Slave
• Starting the devices with fiber optic connection
The devices work out among themselves which is the master (normally the one
synchronized first)
• Starting the devices without fiber optic connection
The devices do not send out any time information until there is an LWL connection,
or the devices are reconfigured.
• The slave synchronizes to the master.
Whereby stratum/slave = stratum/master +1
The time of the slave is always set immediately to the master time (no fine
adjustment).
© MOBATIME
67 / 104
800870.13
• In case of loss of the master GPS, the master stratum increases on the basis of the
configurable parameters up to the maximum stratum. The slave follows, i.e. the
slave stratum is always 1 higher. The slave takes over the master role from a
configurable stratum value (if the status of the slave is better than that of the master)
and synchronizes to its own GPS. The previous master becomes the slave. This
distribution of roles remains until the new master loses GPS synchronization.
• In the case of a loss of the master, the slave takes over the master function.
• If the former master is working again, it takes over the actual time of the current
master and remains in slave mode.
• In the case of a fiber optic connection loss, the slave checks the status of the master
over the network and remains in slave mode as long as the master is accessible and
is working normally. If the master is no longer accessible or has a worse status, the
slave takes over the master function.
NTP
The NTP clients select the server with the lower stratum.
DCF77 coded (fiber optic output)
No redundancy
2 LAN Mode
The two redundant DTS 4138 are not located in the same network. The role decision
(master, slave) takes place exclusively via opt. link.
RTC:
RTC is to be deactivated for the redundant mode.
© MOBATIME
68 / 104
800870.13
9
SNMP
9.1
General
The SNMP version V2c or V3 for Get, Set and version V1 or V2c for Notification (Trap)
is used.
A full SNMP agent is implemented on the DTS (MIB II, DTS4138).
For SNMP V2c, following standard Communities are used:
Read only :
romobatime
Read/Write:
rwmobatime
Trap:
trapmobatime
For SNMP V3, following standard User I Passwords are used:
dtsUser1
mobatime
dtsUser2
mobatime
dtsInfo
mobatime
(not changeable, read only)
DtsUser1 and dtsUser2 have full read/write access on all objects. With SNMP V3 rules,
access can be reduced. Changes of the rules can only be modified over the DTS menu
but not via SNMP.
SNMP V3 agent supports user validation (authentication MD5) and encoding
(encryption DES).
MIB II values like sysDescr, sysContact, sysName, or sysLocation can only be modified
over the DTS menu but not via SNMP.
The following MIB definitions are used:
SNMPv2-SMI, SNMPv2-MIB, SNMPv2-CONF, SNMPv2-TC, SNMPv2-TM,
SNMP-FRAMEWORK-MIB, SNMP-MPD-MIB, SNMP-NOTIFICATION-MIB,
SNMP-TARGET-MIB, SNMP-USER-BASED-SM-MIB, SNMP-VIEW-BASED-ACM-MIB,
RFC1213-MIB, IF-MIB, IP-MIB, IP-FORWARD-MIB, TCP-MIB, UDP-MIB,
HOST-RESOURCES-MIB, HOST-RESOURCES-TYPES, DISMAN-EVENT-MIB,
NOTIFICATION-LOG-MIB, UCD-SNMP-MIB, NET-SNMP-MIB, NET-SNMP-TC
SNMP V2c, V3:
DTS-COMMON
(File: DTS-COMMON-MIB.TXT)
General DTS definition, always required
DTS4138
(DTS4138-MIB.TXT)
Device-specific DTS definitions
The MIB files can be copied from the DTS 4138 with FTP (For FTP use, see chapter
“7.7 FTP connection“):
DTS-MIB:
Standard MIBS:
© MOBATIME
/etc/snmp/mibs/
/usr/share/snmp/mibs/
69 / 104
800870.13
9.2
Device configuration with SNMP
If one or several variables are set with Put in a configuration group, the variable
dts4138????ConfigCmd must be set at the end to 1 in the corresponding group. The
values of the entire configuration group are assumed from the DTS with this command
(1=Save).
As long as the accept command has not been set, the changed variables can be restored
to the old values by setting the dts4138????ConfigCmd variable to 2 (2=undo, restore).
After sending the accept command, a dts4138ConfigChanged Notification is sent.
The definitions of the available variables can be taken from the MIB files.
Example:
Management-System
DTS
Put dts4138FTPMode=1
→
Variable is set to 1 internally
Put dts4138NetServicesConfigCmd=1
→
Configuration group is assumed

Sends dts4138ConfigChanged Notification
with the new time dts4138NetConfigChangedTime
9.3
DTS subagent SNMP notification
Protocol: SNMPv2c Notification
For Notifications to be sent out, SNMP must be switched on. In addition, at least one
receiver system must be configured.
9.3.1
Startup
[dts4138StartUp]
Sent out when the subagent for the DTS is started.
This Notification is always sent out, as soon as SNMP is activated and a destination
address is configured.
9.3.2
Shutdown
[dts4138Shutdown]
Sent out when the subagent for the DTS is stopped.
This Notification is always sent out, as soon as SNMP is activated and a destination
address is configured.
© MOBATIME
70 / 104
800870.13
9.3.3
Status changed
[dts4138StatusChanged]
Sent out when the subagent detects a status change in the DTS application process.
The following variables are monitored for changes:
dts4138SysStatus, dts4138NTPTInfoCurrentSource, dts4138SysStratum
This Notification is always sent out, as soon as SNMP is activated, and a destination
address is configured.
The Notification sent out contains the following data:
Field
Type
Size
Description
Example
dts4138SysStatus
Unsigned Int
4 Bytes
Contains the internal
system status
66309
dts4138SysOffset
Integer
4 Bytes
Actual time offset of
the system [us]
-1523 → -1.523ms
dts4138NTPTInfoCurrentSource
Byte String
63
Actual time source
192.168.1.55
dts4138SysStratum
Byte
1 Byte
Actual system
stratum level
1
9.3.4
Configuration changed
[dts4138ConfigChanged]
Sent out when the subagent detects a configuration change in the DTS application
processes.
This Notification is always sent out, as soon as SNMP is activated and a destination
address is configured.
The Notification sent out contains the following data:
Field
Type
Size
Group
dts4138SysConfigChangedTime
TimeTicks 4 Bytes
dts4138System
dts4138NetworkIf0ConfigChangedTime
TimeTicks 4 Bytes
dts4138NetworkIf0
dts4138NetworkIf1ConfigChangedTime
TimeTicks 4 Bytes
dts4138NetworkIf1
dts4138NetConfigChangedTime
TimeTicks 4 Bytes
dts4138Network
dts4138NetServicesConfigChangedTime
TimeTicks 4 Bytes
dts4138NetServices
dts4138TSConfigChangedTime
TimeTicks 4 Bytes
dts4138TimeSource
dts4138RedOpConfigChangedTime
TimeTicks 4 Bytes
dts4138NTPConfigChangedTime
TimeTicks 4 Bytes
dts4138TimeRedundantOp
dts4138TimeNTPServer
dts4138OutMainDCFConfigChangedTime
TimeTicks 4 Bytes
dts4138OutMainDCF
dts4138OutLineDCFPulseFREQConfigChangedTime TimeTicks 4 Bytes
dts4138OutLineDCFPulseFREQ
dts4138OutLineSerialConfigChangedTime
TimeTicks 4 Bytes
dts4138OutLineSerial
dts4138OutLineIRIGConfigChangedTime
TimeTicks 4 Bytes
dts4138OutLineIRIG
dts4138OutLineTZServerConfigChangedTime
TimeTicks 4 Bytes
dts4138OutLineTZServer
dts4138RelayConfigChangedTime
TimeTicks 4 Bytes
dts4138AlarmRelayConfig
dts4138MailConfigChangedTime
TimeTicks 4 Bytes
dts4138AlarmMailConfig
dts4138SnmpConfigChangedTime
TimeTicks 4 Bytes
dts4138SnmpConfig
dts4138SnmpV3ConfigChangedTime
TimeTicks 4 Bytes
dts4138SnmpV3
The ConfigChangedTime variables show the time of the last change of the relevant
configuration group as TimeTicks value in 1/100th seconds. The management system
can decide on the basis of these time values, which configurations need to be
reloaded.
The groups and their parameters are listed in appendix “G Parameters“.
© MOBATIME
71 / 104
800870.13
9.3.5
Alive Notification
[dts4138Alive]
Sent out in a configurable interval.
This Notification is always sent out, as soon as SNMP and the alarm traps are activated
and a destination address is configured.
The Notification sent out contains the following data:
Field
Type
Size
Description
Example
dts4138SysStatus
Unsigned Int
4 Bytes
Contains the internal
system status
66309
dts4138SysAlarms
Byte Array
8 Bytes
64 Bit Alarm flags
1.Byte Bit 0..7
2.Byte Bit 8..15
::
8.Byte Bit 56..63
FFF870FF.FFFFFFFF
¦ ¦
¦
¦ ¦
5.Byte
¦ 2.Byte
1.Byte
9.3.6
Alarm Notification
[dts4138Alarm]
Sent out if alarm status changes, i.e. Notification is sent out when an alarm flag is set or
deleted.
This Notification is always sent out, as soon as SNMP and the alarm traps are activated
and a destination address is configured.
The Notification sent out contains the following data:
© MOBATIME
Field
Type
Size
Description
Example
dts4138TrapAlMsgErrorNr
Byte
1 Byte
No. of the alarm bit (0..63)
dts4138TrapAlMsgErrorState Byte
1 Byte
0 = alarm bit was deleted
1 = alarm bit was set
3
1
dts4138TrapAlMsgErrorTime Unsigned
Int
4 Bytes
PC-time in seconds since
01.01.1970 00:00:00
dts4138TrapAlMsgErrorText
59 Bytes Error text
Text
72 / 104
946684805
Failure supply 1
800870.13
10
Power supply alternatives
The DTS 4138 permits 2 different power supply alternatives:
1. DC power supply with 24VDC +20% / -10% to “DC in 1” or “DC in 2”
Notice:
In the menu: ‘2 Configuration’ ➔ ‘4 General’ ➔ ‘3 Power’ must be set
to '0=single'.
2. Redundant power supply:
Supply1:
Supply2:
DC in 1
DC in 2
Supply is checked once per minute for correct functioning. The alarm ’loss of power
1’ or ’loss of power 2’ is set in case of error.
Notice:
In the menu: ‘2 Configuration’ ➔ ‘4 General’ ➔ ‘3 Power’ must be set to
'1=redundant'.
Block diagram of power supply:
processor
board
U, I,
control
U, I,
control
© MOBATIME
DC in 1
24VDC
+20%-10%
Supervision
DC in 2
24VDC
+20%-10%
Supervision
power
fail
logic supply
DC/DC
24VDC out
(e.g. GPS 4500)
power
73 / 104
800870.13
A
Connection diagrams
A.1
Front connections
HW Reset
LAN 1 connection:
Plug:
RJ45
Interface:
Ethernet, 10/100Mbit half- or full duplex
Use only shielded cables!
LAN 2 connection:
Plug:
RJ45
Interface:
Ethernet, 10/100Mbit half- or full duplex
Use only shielded cables!
Notice:
If only one LAN interface is used, it always has to be LAN 1!
USB connection:
Plug:
Notice:
© MOBATIME
USB host
Only permitted for operations with a USB stick!
74 / 104
800870.13
A.2
Connections (rear view)
DTS 4138 connections
For technical data, see appendix “H Technical data“.
Clamp
Connection
Description
Earth connection
1
2
DC in 1 power supply +
Input for external DC supply
DC in 1 power supply GND Ground
3
4
DC in 2 power supply +
Input for external DC supply
DC in 2 power supply GND Ground
5
6
Alarm relay
Alarm relay
7
8
Common +
Alarm input +
Alarm contact, open when alarm is active
Switching load: 30 W (125 VDC or 1 A), e.g. 1 A @ 30 VDC
or 60 VA (150 VAC or 1 A), e.g. 0.5 A @ 120 VAC
Alarm input (see drawing below):
18-36VDC, max. consumption 6mA DC, closing contact.
Voltage level “high” (ext. 24V available, GND from PIN 11)
or external contact ➔ configurable: alarm or no alarm.
Length of connection max. 3m.
BNC
AFNOR-A/C, IRIG-B12x synchronization input
IRIG-In
IRIG 12x BNC: IRIG-B12x output
Channel 1
AFNOR-A/C, IRIG-B1xx and DCF-FSK output for IRIG line 1
DTS
DTS extension
extension
DTS extension bus
Alarm Input:
5
6
Common + 7
Alarm In + 8
9
10
GND 11
12
13
© MOBATIME
+
18 - 36 VDC
GND
75 / 104
800870.13
Clamp
Connection
Description
9
10
11
12
13
RS232 Tx
RS232 Rx
GND
RS485 A
RS485 B
RS232 interface of line 1 (Exclusive to the RS485
interface line 1; internally the same interface)
14
15
RS422 + Pulse 1
RS422 – Pulse 1
16
17
CL + Pulse 1
CL – Pulse 1
RS422 output line 1 for DCF, pulse and frequency output
(internally the same source of signal like for the current
loop output)
Current loop line 1 for DCF, pulse and frequency output
("Current loop” passive,
optocoupler: Umax= 50VDC, Imax = 10mA)
18
19
20
21
RS422 +
RS422 –
Current Loop +
Current Loop –
Digital IRIG-B signal (00x) of the IRIG line 1
22
23
24
25
26
27
DCF input +
DCF input DCF output +
DCF output DC output +
DC output GND
DCF input e.g. for the connection of a GPS 4500 or DCF
receiver with "current loop“ output.
DTS-Link
Optical connection to a 2nd DTS 4138
Mini GBIC plug-in
Option, for special applications only
EFR
© MOBATIME
RS485 interface of line 1 (Exclusive to the RS232
interface line 1; internally the same interface)
Digital IRIG-B signal (00x) of the IRIG line 1 as current loop
(“current loop” passive,
optocoupler: Umax= 50VDC, Imax = 10mA)
DCF output, “current loop” passive,
Umax= 30VDC, Ion = 10..15mA, Ioff < 1mA @20VDC
DC output for GPS 4500
28 VDC, max. 200 mA
76 / 104
800870.13
A.3
Plug-in spring terminals
Multiple contact strip 100% protected against wrong plug;
WAGO CAGE CLAMP®-connection
Cross section of 0,08 mm² to 1,5 mm² (from AWG 28 to AWG 14)
Voltage CSA 300 V / current CSA 10 A
Rated voltage: EN 250 V
Rated surge voltage: 2,5 kV
Nominal current: 10 A
Strip length: 7 mm (0,28 in)
Pulled off spring terminal with operation tool:
2 operation tools are delivered with the accessory bag.
A.4
Connection GPS / GNSS 4500, DCF 4500 or GNSS 3000
DCF receiver
GPS / GNSS 4500
white
brown
yellow
green
GNSS 3000 according to manual Bx-800813 chap. 9.2 Connection schematics DCF
current loop
A.5
IRIG-B00x Digital Output TTL connection
IRIG digital output
TTL (00x)
IRIG digital output
TTL inverse (00x)
© MOBATIME
77 / 104
800870.13
B
Time zone table
Time zone entries in the standard season table (version 10.3).
No.
City / State
00
01
02
UTC (GMT), Monrovia
London, Dublin, Lisbon
Brussels, Amsterdam, Berlin, Bern,
Copenhagen, Madrid, Oslo, Paris,
Rome, Stockholm, Vienna, Belgrade,
Bratislava, Budapest, Ljubljana, Prague,
Sarajevo, Warsaw, Zagreb
Athens, Helsinki, Riga, Tallinn, Sofia,
Vilnius
Bucharest
Pretoria, Harare,
Kaliningrad
Amman
UTC (GMT)
Istanbul, Kuwait City, Minsk, Moscow,
Saint Petersburg, Volgograd
Praia, Cape Verde
UTC (GMT)
Abu Dhabi, Muscat, Tbilisi, Samara
Kabul
Adamstown (Pitcairn Is.)
Tashkent, Islamabad, Karachi,
Yekaterinburg
Mumbai, Kolkata, Chennai,
New Delhi, Colombo
Astana, Thimphu, Dhaka, Novosibirsk
Bangkok, Hanoi, Jakarta, Krasnoyarsk
Beijing, Hong Kong, Singapore, Taipei,
Irkutsk
Tokyo, Seoul, Yakutsk
Gambier Island
South Australia: Adelaide
Northern Territory: Darwin
Brisbane, Guam,
Port Moresby, Vladivostok
Sydney, Canberra, Melbourne,
Tasmania: Hobart
UTC (GMT)
UTC (GMT)
Honiara (Solomon Is.), Magadan,
Noumea (New Caledonia)
Auckland, Wellington
Majuro (Marshall Is.), Anadyr
Azores
Middle Atlantic
Not used
Brasilia, Buenos Aires
Newfoundland
Atlantic Time (Canada)
La Paz
Bogota, Lima, Quito
New York, Eastern Time (US & Canada)
Chicago, Central Time (US & Canada)
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
© MOBATIME
UTC DST Standard → DST DST → Standard
Offset
0
0
+1
No
Yes
Yes
Last Sun. Mar. (01:00)
Last Sun. Mar. (02:00)
Last Sun. Oct. (02:00)
Last Sun. Oct. (03:00)
+2
Yes
Last Sun. Mar. (03:00)
Last Sun. Oct. (04:00)
+2
+2
Yes
No
Last Sun. Mar. (03:00)
Last Sun. Oct. (04:00)
+2
0
+3
Yes
No
No
Last Thu. Mar. (23:59)
Last Fri. Oct. (01:00)
-1
0
+4
+4.5
-8
+5
No
No
No
No
No
No
+5.5
No
+6
+7
+8
No
No
No
+9
-9
+9.5
+9.5
+10
No
No
Yes
No
No
1st Sun. Oct (02:00)
1st Sun. Apr. (03:00)
+10
Yes
1st Sun. Oct. (02.00)
1st Sun. Apr. (03:00)
0
0
+11
No
No
No
+12
+12
-1
-2
Yes
No
Yes
No
Last Sun. Sep. (02:00)
1st Sun. Apr. (03:00)
Last Sun. Mar. (00:00)
Last Sun. Oct. (01:00)
-3
-3.5
-4
-4
-5
-5
-6
No
Yes
Yes
No
No
Yes
Yes
2nd Sun. Mar. (02:00)
2nd Sun. Mar. (02:00)
1st Sun. Nov. (02:00)
1st Sun. Nov. (02:00)
2nd Sun. Mar. (02:00)
2nd Sun. Mar. (02:00)
1st Sun. Nov. (02:00)
1st Sun. Nov. (02:00)
78 / 104
800870.13
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
Tegucigalpa, Honduras
Phoenix, Arizona
Denver, Mountain Time
Los Angeles, Pacific Time
Anchorage, Alaska (US)
Honolulu, Hawaii (US)
Midway Islands (US)
Mexico City, Mexico
Adak (Aleutian Is.)
UTC (GMT)
UTC (GMT)
UTC (GMT)
UTC (GMT)
UTC (GMT)
Ittoqqortoormiit, Greenland
Nuuk, Qaanaaq,Greenland
Not used
Western Australia: Perth
Caracas
CET standard time
Not used
Not used
Baku
UTC (GMT)
UTC (GMT)
-6
-7
-7
-8
-9
-10
-11
-6
-10
0
0
0
0
0
-1
-3
No
No
Yes
Yes
Yes
No
No
Yes
Yes
No
No
No
No
No
Yes
Yes
+8
-4.5
+1
No
No
No
+4
0
0
Yes
No
No
2nd Sun. Mar. (02:00)
2nd Sun. Mar. (02:00)
2nd Sun. Mar. (02:00)
1st Sun. Nov. (02:00)
1st Sun. Nov. (02:00)
1st Sun. Nov. (02:00)
1st Sun. Apr. (02:00)
2nd Sun. Mar. (02:00)
Last Sun. Oct. (02:00)
1st Sun. Nov. (02:00)
Last Sun. Mar. (00:00)
Last Sat. Mar. (22:00)
Last Sun. Oct. (01:00)
Last Sat. Oct. (23:00)
Last Sun. Mar. (04:00)
Last Sun. Oct. (05:00)
In countries where the DST switch date changes annually (e.g. Iran, Israel), the time zone has to be
defined manually in the user time zone table (entries 80 – 99).
Legend:
UTC:
DST:
DST Change:
Standard → DST:
DST → Standard:
Example:
2nd last Sun. Mar. (02:00)
Important:
Universal Time Coordinate, equivalent to GMT
Daylight Saving Time
Daylight Saving Time changeover
Time change from Standard time (Winter time) to Summer time
Time change from Summer time to Standard time (Winter time)
Switch over on the penultimate Sunday in March at 02.00 hours local time.
The Time Zone Table is usually updated as needed. The current table is available for download under
the following address: www.mobatime.com ➔ Customer Area ➔ Customer Support ➔ Support
Resources ➔ Time Zone Table. In case your device is equipped with a newer version than shown in
this manual, the current time zone settings should be checked.
Modifications / updating the time zone table:
In the DTS device the time zone tables are stored in the files /etc/mbsn.tbl (standard table) and
/etc/usersn.tbl (user table).
The user table can be changed with Moser-Baer AG software such as ETCW or MOBA-NMS.
Using MOBA-NMS, it can be downloaded from there, otherwise, it must be copied on to the DTS 4138
in accordance with the update instructions (chapter “7.4 Updating applications or configurations with
FTP“).
Notice:
© MOBATIME
The file names mbsn.tbl and usersn.tbl must be written in small letters.
79 / 104
800870.13
C
Alarm list
Number Error message
Description / Action
0
Reboot DTS
DTS 4138 restarted, no intervention required
1
Error bit1
Not used
2
Supply voltage too low
Power failure (internally measured) ➔ support
3
Power failure 1
Power failure 1 (only if redundant supply is on)
4
Power failure 2
Power failure 2 (only if redundant supply is on)
5
Error voltage 5V
Power failure (internally measured) ➔ support
6
Error voltage 2.5V
Power failure (internally measured) ➔ support
7
Error voltage 1.25V
Power failure (internally measured) ➔ support
8
Wrong time zone DCF
Check DCF configuration
6.5.2
9
Wrong time zone TC
Check TC configuration (IRIG/DCF/Impulse)
6.5.3 / 5
10
Error bit10
Not used
11
Alarm input
Error from external device
6.5.18
12
Low voltage IRIG
Low voltage on analogue AFNOR/IRIG-B output
6.5.5
13
Error bit13
Not used
14
Error bit14
Not used
15
Error bit15
Not used
16
Time source lost
Stratum too high: check time source
6.5.8
Failure time source TO
No time information from the selected time source within
the configured timeout: Check time source.
In slave mode: check link.
6.5.8
17
18
No valid time
20 min after starting no valid time ➔ Check time source
19
NTP synch. lost
Check NTP source
20
Software trimming
Quartz error or poor source quality
21
NTP not working
Check NTP configuration
22
NTP backup active
Check primary source
23
Syn only diff too large
Check synchronization and source
6.5.9
24
No mail server
Check e-mail configuration, check connection
6.5.16
25
SNMP not running
Check SNMP and trap configuration
6.5.17
26
Error bit26
Not used
27
Error bit27
Not used
28
Error bit28
Not used
29
Error bit29
Not used
30
No link (optical)
No connection via DTS link (optical link) in redundant
operation. Check connection.
31
No link (LAN)
No connection via LAN link in redundant operation. Check
LAN connection.
32
Change Slave->Master
Switch over slave -> master has occurred. Optionally,
check the time source of current slave.
33
Offset source (slave)
In slave mode only: check time sources
Difference between slave and local time source too large
6.5.10
34
Fail local source
In slave mode only: check time sources
6.5.8
35
Error bit35
Not used
© MOBATIME
80 / 104
Chap.
800870.13
36
Error bit36
Not used
37
Error bit37
Not used
38
Tele.-file invalid
Check telegram file: the file name is longer than 8 digits or 6.5.4
the file type is not TEL, Tel or tel; alternatively, syntax error
in telegram file
39
Wrong time zone serial
Check serial time zone configuration
40
Error bit40
Not used
41
Error bit41
Not used
42
Error bit42
Not used
43
Error bit43
Not used
44
Error bit44
Not used
45
Error bit45
Not used
46
Error bit46
Not used
47
Error bit47
Not used
48
Error bit48
Not used
49
Error bit49
Not used
50
Error bit50
Not used
51
Error bit51
Not used
52
Error bit52
Not used
53
Error bit53
Not used
54
Error bit54
Not used
55
Error bit55
Not used
56
Error bit56
Not used
57
Error bit57
Not used
58
Error bit58
Not used
59
Error bit59
Not used
60
Error bit60
Not used
61
Error bit61
Not used
62
Error bit62
Not used
63
Error bit63
Not used
© MOBATIME
81 / 104
6.5.4
800870.13
D
Troubleshooting
Error
1
DTS does not accept
time
→
→
Does the reading change
(approx. every 3 sec) Sec counter
DCF in Status → Source →TIME
SOURCE INFORMATION?
2
Solution / possible cause
No, but 20 min.
have not yet
passed since the
last reboot.
After new installation or powers supply failure, it
may take up to 20 min. until the GPS receiver
(e.g. GPS 4500) sends out valid telegrams. Wait
for this time to pass.
No, for more than
20 minutes.
• Check DCF reception LED
• Check polarity cabling to GPS.
• Check positioning of the GPS receiver
3
Error-Bit 23 (Syn only diff too big)
in Status → Alarm status set
The deviation to the received time is beyond the
maximal allowed time correction.
In the menu Configuration→Time administration
→ Time-keeping configuration → TIME
ADJUSTMENT CONFIGURATION, set the
parameter synch. only offset (4) to 0
(=deactivated). The time is now adjusted
independently of the deviation’s extend. It is
however recommended to set a limit in normal
operation (default 800ms).
4
Offset to source in Status
→Time→
TIME INFORMATION AND
STATUS always shows the same
offset
• If Error-Bit 23 set, see point 3
• The deviation is that big, that offset changes
cannot be seen due to the displayed
resolution.
5
Configuration has just been
changed
In the case of configuration changes, particularly
if the time configuration is concerned, it can take
several minutes for the change to appear
correctly.
6
Error-Bit 16 set (time
source fail stratum)
See 1
7
Error-Bit 17 set (time
source fail TO)
See 1
8
Error-Bit 23 set (Syn
only diff too big)
See 1
9
DTS 4138 is
restarting
continuously.
Check if the network settings are correct,
especially the hostname and the gateway has to
be configured (when no gateway is available, the
own IP address can be used).
10
LAN LED (left one) is
flashing orange.
11
Opening the menu via
Telnet is not possible
or DTS 4138.
timeserver is not or no
longer reachable via
network.
12
Drift (ppm) of quartz
too high
13
System software
update
© MOBATIME
No connection to the network.
Check network cabling.
Check network settings in menu 2 Configuration
–> 5 Network (only possible with serial
connection):
- IP-Address, Subnet mask and Gateway must
be set correctly
- Interface should be set to Auto
- Check connection with "Ping"
- When earlier the menu was not correctly exited
(e.g. LAN cable removed), the menu can be
blocked up to 15 minutes.
The drift displayed in the menu
Status →Time →TIME
INFORMATION AND STATUS is
bigger than stated in the data
sheet.
• The quartz drift is measured and corrected
continuously. After initial operation, it may take
up to 24 hours until optimal accuracy is
reached (with GPS reception).
• Very large temperature change (outside the
specification)
• Time correction was carried out manually.
The system software can be updated using FTP
client software or a USB stick (s. chapter 7
Updates).
Your MOBATIME service informs you of use and
necessity of a software update. If necessary,
they can provide the needed firmware file.
82 / 104
800870.13
14
Needed information to
contact your
MOBATIME service
Device type, part number, production number
and serial number:
These details are given on the adhesive type
label.
The following files must be provided for the
analysis:
All files (in .zip folders, separate for each
device) from the directories /var/log/ and /etc/
and the file: /ram/trim.log.
To copy this files use FTP, e.g. Windows
Explorer with ftp://[IP address], see chapter 7.7.
If the log files cannot be copied, please read
out the current software version:
The software version can be queried in the menu
1 STATUS/9 Versions of the software
Place and date of purchase and of
commissioning of the device.
Most comprehensive possible details of the
malfunction:
Describe the problem, possible causes,
measures taken, the system environment /
operating mode and configuration, etc.
© MOBATIME
83 / 104
800870.13
E
Serial Telegrams
E.1
General
A serial interface can be used in two different modes:
- Send out time of telegrams automatically (periodically)
- Receive command, send time telegram (on request)
Output modes
Auto
Periodic transmission of a time telegram or a command at the end of a
second, minute, hour, or at a max. of 6 programmable times of the day, or
definable output – periodicity.
on request Telegram is transmitted on request. The 'request' strings can be defined.
The following requests are possible:
- stop output
- output telegram at once (singly)
- output telegram at the next second (singly)
- output every second / minute / hourly / daily or switch to auto-mode.
Telegram format
Any character sequence. Fill characters ASCII or binary.
Variable display: ASCII decimal, ASCII hexadecimal or binary. Different
variables are assigned to strings in text tables (e.g. month: Jan, Feb...). Syntax for the
telegram string analogous to the print command in the programming language "C". See
chapter E.2 Syntax of the telegram configuration file.
Telegram time
The telegram always contains the time information for the "next" second for periodical
telegram output. The telegram content is valid at the send time of the first character.
The send time of the telegram can be shifted with the parameter TC (e.g. the standard
IF 482 telegram valid at the end of the telegram).
The transmission time of a time telegram can be calculated with the following table.
According to the transmission format set, the transmission time in ms for one character
is read from the table and multiplied by the number of telegram characters:
7 data bits
8 data bits
parity none
odd/even
none
odd/even
stopp byte
1
2
1
2
1
2
1
2
ms per transmited byte
300 bit/s
30.00 33.33 33.33 36.67 33.33 36.67 36.67 40.00
600 bit/s
15.00 16.67 16.67 18.33 16.67 18.33 18.33 20.00
1200 bit/s
7.50
8.33
8.33
9.17
8.33
9.17
9.17 10.00
2400 bit/s
3.75
4.17
4.17
4.58
4.17
4.58
4.58
5.00
4800 bit/s
1.88
2.08
2.08
2.29
2.08
2.29
2.29
2.50
9600 bit/s
0.94
1.04
1.04
1.15
1.04
1.15
1.15
1.25
19200 bit/s
0.47
0.52
0.52
0.57
0.52
0.57
0.57
0.63
38400 bit/s
0.23
0.26
0.26
0.29
0.26
0.29
0.29
0.31
© MOBATIME
84 / 104
800870.13
Example:
9600 Bit/s, 8 data bits, none, 1 stop bit, the telegram has 20 characters.
Transmission time for the entire telegram:
20 x 1.04 ms = 20.8 ms
Name of the telegram file
The telegram file name is limited to 8 characters and its extension has to be TEL, Tel or
tel, e.g. IF482Std.tel.
E.2
Syntax of the telegram configuration file
!TEL
;telegram type also !CTC or !MTS possible
;-- Start of the file (always on the first line) -----------------------;DEFINITIONS CONFIGURATION FILE FOR PRECISION MASTER CLOCK
;**********************************************************
;Customer:
;Date:
;Author:
;File:
;Interface:
;-- Output string --------------------------------------------------;
the output string has a similar format to the print command in the
;
programming language 'C'.
;
!TS! - String with format information
;
!TV! – Variables list in output sequence
;
The formats and variables available can be seen below:
:
!TS!"........%d....%d..."
;String with Format information
!TV!var1,var2,..
;Variables list
;-- Control and special characters
;
"
->
String beginning/end
;
\"
->
"
;
\xFE
->
h'FE
(Byte binary)
;
\\
->
\
;
\n
->
new line <CR> <LF> (h'0D h'0A)
;
%%
->
%
;
%...
->
Format information (see below)
;-- Possible formats:
;%dn ascii-dez where n=1/2/3/4 (number of decimal points, max. 3 places received)
;
e.g. variable value d'40
=> 40 @ n=2
;
=> 040 @ n=3
;%X ascii-hex
;
e.g. variable value d'40
=> 28
;%c char (binary)
;
e.g. variable value d'40
=> h'28
;%s string (always up to,(comma) see text tables
;
e.g. string
Jan,
=> Jan
;%b hex-output of an asciihex-string (always up to(comma)see
;
text tables
;
e.g. string
120A,
=> h'12 h'0A
;-- Possible variables:
;
;Name: Description:
Range:
Format:
;-------|-----------------------|-----------|-----;
;MSE
(Millisecond)
(0..999)
1W
;HSE
(Hundredth of a second) (0..99)
1B
;ZSE
(Tenth of a second)
(0..9)
1B
;SEK
(Second)
(0..59)
1B
;MIN
(Minute)
(0..59)
1B
;STD
(12h or 24h format)
(0..12)
;
or(0..24) 1B (see !PM!)
;JAR
(Year)
(0..99)
1W
;
or (1990..2089)
© MOBATIME
85 / 104
800870.13
;MTG
;JTG
;WTG
;
;DOW
;KAW
;MON
;MNT
;
;AMF
;TMQ
;
;SAI
;
;AKS
;
;AMF
;SST
;
;
;SYA
;
;CHS
;XCH
;X1C
;X2C
;
;
;
(Day of the month)
(Day of the year)
(Day of the week)
(Day of the week)
(Calendar week)
(Month)
(Month)
(1..31)
(1..366)
(0..6)
(Su..Sa)
(0..7)
(1..53)
(1..12)
(1..12)
1B
1W
1W Text table !WT!
1B !DW!
1B (according to Din ISO 8601)
1W Text table !MO!
1B
(am/pm flag)
(0/1)
1W Text table !AM!
(synchronization qual.) (0..255
or A..Z) 1B (see !TQ!)
(Season)
(0..2)
1W Text table !SA!
(Win/Sum/UTC)
(Season change
(0/1)
1W Text table !AK!
announcement)
(am/pm-Flag)
(0/1)
1W Text table !AM!
(Season status)
(0..3)
1W Text table !ST!
(Bit 0 = Early warning bit)
(Bit 1 = Summer bit)
(Synch. alarm)
(0/1)
1W Texttabelle !SY!
(0:synch ok, 1: synch alarm -> Alarm Nr.16, 17 or 19)
(Check sum)
(0..255)
1B
(XOR Check sum)
(0..255)
1B
(XOR Check sum low nibble in ASCII) (0..9, A..F)
1B
(XOR Check sum high nibble in ASCII)(0..9, A..F)
1B
Definitions:
CHS = (Sum of all bytes up to CHS) AND h’FF
XCH = XOR link of all bytes up to CHS
;e.g.
time telegram with following format (36 ASCII characters)
;
;
"Date: tt:mm:yy Time: hh:mm:ss,mmm<CR><LF>"
;
;!TS!"Date: %d2:%s:%d2 time: %d2:%d2:%d2,%d3\n"
;!TV!MTG,MON,JAR,STD,MIN,SEK,MSE
;-------------------------------------------------------------------;-- Send offset automatic telegram output ----------------------!SO!hh:mm:ss!
;
;Send offset from midnight 00:00:00 at periodic time
;output (!CS!a!...).
;
;hh =
hour
('00..23')
;mm =
minute ('00..59')
;ss =
second ('00..59')
;
;e.g.
the periodic time output should start at 06:00:00
;
in each case:
;
;
!SO!06:00:00!
;
;-------------------------------------------------------------------;-- Interval automatic telegram output ------------------------!TI!p!hh:mm:ss!
;
;Interval from send offset of the periodic time output.
;
;s =
every second
;m =
every minute
;h =
hourly
;d!hh:mm:ss! daily (max. 6 entries)
;p!hh:mm:ss! constant
;hh =
hour
('00..23')
;mm =
minute ('00..59')
;ss =
second ('00..59')
;
;e.g.1 telegram output every second
;
!TI!s!
;
;e.g.2 telegram output daily at 13:00:00 hours
;
!TI!d!13:00:00!
;
;e.g.3: the interval of the periodic time output should be 5 seconds:
;
!TI!p!00:00:05!
;--------------------------------------------------------------------
© MOBATIME
86 / 104
800870.13
;-- Hours format --------------------------------------------------!PM!
;Hours format 12h with am/pm flag
;without this entry:
24h format
;-------------------------------------------------------------------;-- Synchronization mode ------------------------------------------!TC!mmm!
;Pretiming of the telegram in ms (-90..249). To synchronize the telegram
;end with the second start the TC has to be set according to the telegram
;length and the transmission format. If TC is set, it will be performed.
;
;e.g.
Telegram start 120ms before the start of the second:
;
!TC!120!
;-------------------------------------------------------------------;-- Format time quality --------------------------------------------!TQ!MAX VALUE!STEP!
;If this entry is absent, the byte value of TMQ is
;outputted
;MAX VALUE corresponds to the byte value for A
;MAX VALUE-STAGE corresponds to the byte value for B
;MAX VALUE-2*STAGE corresponds to the byte value for C ...
;Example: A for values >=120..101
;
B for values =100..81
;
C for values = 80..61 ...
;
;
!TQ!120!20!
;-------------------------------------------------------------------;-- Command Strings -----------------------------------------------!CS!n!l!"ss..."!
or
!CS!n!ll!"ss..."!
;
;n =
Number of the command ('2...9')
;
n=2 Quit (no telegram output)
;
n=3 Telegram output immediately(singly)
;
n=4 Telegram output at the next second(singly)
;
n=5 Telegram every second
;
n=6 Telegram every minute
;
n=7 Telegram hourly
;
n=8 Telegram daily (-> entry: !TI!d!xx..)
;
n=9 Output command (Request for external time source)
;
n=a Telegram output periodic according to !TI!p! and !SO!
;
;l or
ll = Command length in bytes ('01...20')
;
l=0 Command not active
;
;ss... Command string
;
(max. 20 characters – must conform with 'l' or 'll')
;
Wildcards can be set with the '?' sign.
;
This serves as wildcard for any character.
;
Characters can also be outputted in AsciiHex format:
;
e.g.
\xFE
d.h <FE>=(h'FE) is inserted
;
\\
d.h '\' is inserted
;e.g. Definition of a commando for immediate telegram
;
output after a request (command n=3) :
;
'time<CR>' (characters ll=05)
;
!CS!3!05!"time?"!
;
!CS!3!5!"time\x0D"!
;-------------------------------------------------------------------;-- Area for check sum calculation-------------------------------!CK!aa,bb!
;aa = first character considered (telegram start position: 0)
;bb = last character considered + 1
;Missing !CK! in this case the check sum is formed via the whole telegram up to the
;check sum position.
;--------------------------------------------------------------------
© MOBATIME
87 / 104
800870.13
;=====================================================================
;General info about the text tables:
;
Name of the table:
!xx!
;
Separating character of the entries: , (comma)
;
Maximal 16 characters pro Entry
;
Warning:
, do not forget(comma) after the last entry!
;====================================================================
;-- Text table day of the week (WTG Su..Sa) 7 entries ------------------!WT!Sunday,Monday,Tuesday,Wednesday,Thursday,Friday,Saturday,
;-------------------------------------------------------------------;-- Weekday modus 1 entry --------------------------------------!DW!0..3
; 0 : 0 = Sunday, 1 = Monday,... 6 = Saturday
; 1 : 1 = Sunday, 2 = Monday,... 7 = Saturday
; 2 : 6 = Sunday, 0 = Monday,... 5 = Saturday
; 3 : 7 = Sunday, 1 = Monday,... 6 = Saturday
;-------------------------------------------------------------------;-- Text table months (Jan..Dec) 12 entries ----------------------!MO!Jan,Feb,Mar,Apr,May,Jun,Jul,Aug,Sep,Oct,Nov,Dec,
;-------------------------------------------------------------------;-- Text table season (Win,Sum,UTC) 3 entries --------------------!SA!Win,Som,UTC,
;-------------------------------------------------------------------;-- Text table season change announcement -------------------;-- (no announcement, announcement) 2 entries
!AK!0,1,
;-------------------------------------------------------------------;-- Text table season status --------------------------------------;-- (0 = no announcement, winter
;-- 1 = announcement, winter
;-- 2 = no announcement, summer
;-- 3 = announcement, summer) 4 entries
!ST!A,B,C,D,
;-------------------------------------------------------------------;-- Text table AM/PM flag 2 entries ------------------------------!AM!am,pm,
;1.Entry AM/PM flag=0 d.h. 00:00..11:59
;2.Entry AM/PM flag=1 d.h. 12:00..23:59
;-------------------------------------------------------------------;-- Text table synchronization alarm 2 entries -------------------!SY!ok,alarm,
;1.Entry synchronization ok
;2.Entry synchronization s-failure
;--------------------------------------------------------------------
;-- File End --!EE!
;-- Name of the file (optional) ---@nnn...
;nnn... File name, maximum 12 characters and a final
;
<CR>. The name can also be omitted, in this
;
case CTC 'NONAMEx.TEL'appears in the directory.
;
;IMPORTANT:
;
1) The name must stand AFTER the file end!EE!.
;
;
2) If a file with the same name is loaded on to the
;
CTC, such as one stored on the CTC, the stored one
;
will be OVERWRITTEN.
;
;
;e.g.
!EE!
;
@TELEDEF.TEL
;
;last line
;-------------------------------------------------------------------;last line (guarantees a <CR> after the file name)
© MOBATIME
88 / 104
800870.13
F
Copyright Notice
All rights of the software remain the property of Moser-Baer AG.
Existing software (OpenSource) with their own licences were partly used:
Designation
Description
Version
License
License Description (file)
U-Boot
Boot loader
2009.08
GPL version 2
COPYING
Linux
Operating system 3.2.0-rc3
GPL version 2
COPYING
Busybox
System
environment
1.31.1
GPL version 2
LICENSE
NTP
NTP
4.2.8p14
Free
COPYRIGHT
pure-ftp
FTP server
1.0.49
Free, partly BSD
COPYING
NetSNMP
SNMP agent
5.8
BSD
COPYING
OpenSSL
SSL Lib.
1.1.1a
BSD style
LICENSE
OpenSSH
SFTP server
7.9p1
BSD
LICENCE
dropbear
SSH server
2018.76
MIT style:
LICENSE
Free, party BSD
wide-dhcpv6
DHCPv6 client
20080615
Free
COPYRIGHT
flex
Flex Lib.
2.5.35
BSD adapted
COPYING
zlib
Compress lib.
1.2.5
Free
README
mailsend
E-mail client
1.15b5
GPL
-
The complete license descriptions can be referred to in the file indicated in the respective original
source code on the corresponding project page.
Licence text GPL, BSD and MIT:
GPL version 2: http://www.gnu.org/licenses/gpl-2.0.html
BSD:
http://www.opensource.org/licenses/bsd-license.php
MIT
http://www.opensource.org/licenses/with-license.php
The source code of the open source projects running under GPL can be requested from Moser-Baer
AG ([email protected]). Handling costs will be charged!
© MOBATIME
89 / 104
800870.13
G
Parameters
Group
Parameter
Network
2 * Network
Acc Default
DHCP on/off
RW
IP address
RW
Network mask
RW
Gateway IP
RW
Name server IP
RW
Autoconf V6
DHCPv6
IP address V6 1
IP prefix 1
Gateway IPV6 1
IP address V6 2
IP prefix 2
Gateway IPV6 2
Name server IPV6
Link 10/100Mbit
Device name / Host name
Domain
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
Unit
SNMP
dts4138Network (generally)
dts4138Network1 (LAN 1)
dts4138Network2 (LAN 2)
dts4138DHCPMode
LAN 1: on
LAN 2: off
LAN 1: dhcp
LAN 2: 192.168.1.5
LAN 1: dhcp
LAN 2: 255.255.255.0
LAN 1: dhcp
LAN 2: 192.168.1.1
LAN 1: dhcp
LAN 2:
off
off
0::0
64
0::0
0::0
64
0::0
0::0
auto
DTS4138
dts4138IPAddr
dts4138IPMask
dts4138IPGateway
dts4138IPNameserver
dts4138IPv6AutoConf
dts4138IPv6DHCPMode
dts4138IPv6Addr1
dts4138IPv6Prefix1
dts4138IPv6Gateway1
dts4138IPv6Addr2
dts4138IPv6Prefix2
dts4138IPv6Gateway2
dts4138IPv6Nameserver
dts4138EthernetLinkMode
dts4138Hostname, dts4138NetInfoHostname
dts4138Domain
Network
Services
dts4138NetServices
Telnet
SSH
FTP
RW
RW
RW
off
on
off
dts4138TelnetMode
dts4138SSHMode
dts4138FTPMode
Display language
Password user dts
Time zone operation and
alarm messages
Redundant power supply
RW
RW
RW
engl.
dts
MEZ
dts4138System
dts4138Language
dts4138Password
dts4138Timezone
RW
off
dts4138PowerSupply
on
UTC
dts4138OutputLines
dts4138OutMainDCF
dts4138OutMainDCFMode
dts4138OutMainDCFTimezone
General
Lines
DCF out
Mode
Time zone
RW
RW
dts4138OutLineTZServer
NTP slave
clocks
Mode
Multicast IP
Multicast Port
Poll interval NTP
Multicast TTL
Table interval
Entry interval
Table time zone entries
RW
RW
RW
RW
RW
RW
RW
RW
off
65534
0 ➔ 1sec
1
60
1
-1
2^x sec
sec
sec
dts4138OutLineTZServerMode
dts4138OutLineTZServerMCastAddr
dts4138OutLineTZServerMCastPort
dts4138OutLineTZServerNTPInterval
dts4138OutLineTZServerTTL
dts4138OutLineTZServerTableInterval
dts4138OutLineTZServerEntryInterval
dts4138OutLineTZServerTable
(TZ entry number)
dts4138OutLineDCFPulseFREQ
DCF /
Pulse out
Mode (off, DCF, pulse)
Time zone
Pulse interval (every
second, minute...)
Pulse time
Pulse period
Output correction
Frequency
RW
RW
RW
0
UTC
sek
RW
RW
RW
RW
100
1
0
1000
dts4138OutLineDCFMode
dts4138OutLineDCFTimezone
dts4138OutLineDCFPulseType
ms
sec
ms
Hz
dts4138OutLineDCFPulseTime
dts4138OutLineDCFPulsePeriod
dts4138OutLineDCFPulseCorrection
dts4138OutLineDCFFrequency
dts4138OutLineIRIG
IRIG / DCFFSK-Out
Mode (off, IRIG)
Time zone
© MOBATIME
RW
RW
0
UTC
dts4138OutLineIRIGIRIGMode
dts4138OutLineIRIGTimezone
90 / 104
800870.13
Level
Level bar
RW
RW
2000
200
mV
mV
Mode (off, on)
Time zone
Telegram file
Interface:
Baud rate
Databit
Stopbit
Parity
Com mode
RW
RW
RW
RW
RW
RW
RW
RW
RW
off
UTC
MC482STD.TEL
h’45
9600
7
1
even
out RS232
Mode
IP addr. mail server
Port mail server
Receiver address 1
Receiver address 2
Sender address (“login to
mail server“)
Reply address
Error mask
RW
RW
RW
RW
RW
RW
Off
Auth. Mode
User name
Password
RW
RW
RW
dts4138OutLineSerial
dts4138OutLineSerialMode
dts4138OutLineSerialTimezone
dts4138OutLineSerialTeleFile
dts4138OutLineSerialComParam
Serial out
dts4138OutLineSerialComMode
dts4138AlarmMailConfig
dts4138MailMode
dts4138MailServerIPAddress
dts4138MailServerPort
dts4138MailAddrDestination1
dts4138MailAddrDestination2
dts4138MailAddrFrom
E-mail
RW
RW
dts4138OutLineIRIGOutputLevel
dts4138OutLineIRIGAlarmLevel
25
dts4138MailAddrReply
dts4138MailAlarmMask
All set: FF FF FF FF FF
FF FF FF
off
dts4138MailAuthMode
dts4138MailUser
dts4138MailPassword
dts4138SnmpConfig
SNMP / Traps
Trap mode
Trap community
IP addr. target computer 1
Port target computer 1
Trap Version 1
IP addr. target computer 2
Port target computer 2
Trap version 2
TRAP error mask
RW
RW
RW
RW
RW
RW
RW
RW
RW
off
trapmobatime
dts4138SnmpTrapMode
dts4138SnmpTrapCommunity
dts4138SnmpTrapListenerIPAddress1
dts4138SnmpTrapListenerPort1
dts4138SnmpTrapVersion1
dts4138SnmpTrapListenerIPAddress2
dts4138SnmpTrapListenerPort2
dts4138SnmpTrapVersion2
dts4138SnmpTrapAlarmMask
TO alive message
RW
SNMP mode
SNMP error mask
RW
RW
Location
Contact
rocommunity
rwcommunity
2*Access config:
Password
UserSecLevel
UserRead
UserWrite
View1
View2
View3
View4
View5
View6
RW
RW
RW
RW
romobatime
rwmobatime
dts4138SnmpLocation
dts4138SnmpContact
dts4138SnmpROCommunity
dts4138SnmpRWCommunity
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
1+2: auth
1+2: all
1=dts1 2=dts2
1+2: .1.3.6.1.4.1.8072
1+2: .1.3.6.1.4.1.2021
1+2: .1.3.6.1.4.1.13842.4
1+2: .2
1+2: .2
1+2: .2
dts4138SnmpV3UserPasswordx
dts4138SnmpV3UserLevelx
dts4138SnmpV3UserReadx
dts4138SnmpV3UserWritex
dts4138SnmpV3Viewx1
dts4138SnmpV3Viewx2
dts4138SnmpV3Viewx3
dts4138SnmpV3Viewx4
dts4138SnmpV3Viewx5
dts4138SnmpV3Viewx6
162
V2c
162
V2c
All set: FF FF FF FF FF
FF FF FF
off
sec
on V3
All set: FF FF FF FF FF
FF FF FF
dts4138SnmpTrapAliveMsgInterval
dts4138SnmpMode
dts4138SnmpAlarmMask
Alarm input/
output:
dts4138RelayAlarmConfig
Error mask relay
RW
Mode alarm input
RW
NTP / time
handling
Time source:
All set: FF FF FF FF FF
FF FF FF
dts4138RelayAlarmMask
dts4138AlarmInput
dts4138TimeHandling
Time source
Time zone
Config. stratum
© MOBATIME
RW
RW
RW
2 (GPS, DCF)
0 (UTC)
0
50ms
91 / 104
dts4138TimeSource
dts4138TSType
Stratum
dts4138TSStratumMode
800870.13
Max. Time offset to set
system time OK
TO time source for error
failure synch (TO)
Max. stratum for error
failure synch (Stratum)
TO time source stratum
Offset change to
decrement stratum by 1
Source correction (DCF
only)
RW
60
us
dts4138TSMaxOffsetForTimeValid
RW
12
min
dts4138TSTimeout
RW
24
Stratum
dts4138TSStratumErrorLimit
RW
RW
50
0
h
ms / stratum
dts4138TSStratumTimeout
dts4138TSOffsetPerStratum
ms
dts4138TSDCFAdjustment
Catch-up mode
Max. catch-up speed
Core/Quartz type
Synch only offset
RTC Mode
Leap second mode
Leap second date next
correction
RW
RW
RW
RW
RW
RW
RW
RW
Catch-up:
1 (set)
100ppm
0 (off)
0 (off)
0 (off)
off
ns / sec
ms
Redundant
operation:
dts4138TSAdjustmentMode
dts4138TSMaxAdjustmentSpeed
dts4138TSQuartzType
dts4138TSOffsetSynchOnly
dts4138TSRTCMode
dts4138TSLeapSecMode
dts4138TSLeapSecDate
dts4138RedundantOp
Mode redundant operation
Set manual master
Max. stratum master in red.
operation
Max. time offset master to
time source slave
IP addr. 2. time server
Port DTS LAN link
communication
RW
RW
RW
off
dts4138RedOpMode
16
Stratum
dts4138RedOpSwitchOverStratum
RW
100ms
us
dts4138RedOpMaxOffsetSlaveTimeSource
RW
RW
14338
dts4138RedOp2ndDTSIPAddress
dts4138RedOp2ndDTSIPPort
server
normal
off
dts4138TimeNTPServer
dts4138NTPSourceTable (1..4)
dts4138NTPSourceAddr
dts4138NTPSourceMinPoll
dts4138NTPSourceMaxPoll
dts4138NTPSourceMode
dts4138NTPSourcePrefer
dts4138NTPSourceKey
NTP:
4 * NTP source
Addresses
Minpoll
Maxpoll
Mode
Prefer (-red time source)
Key
2 * Broadcast:
Broadcast address
Interval
Multicast TTL
Key
Trusted Keys
Control Key
Request Key
Autokey Password
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
RW
2^x sec
2^x sec
2 ➔ 4s
1
off
2^x sec
0
0
dts4138NTPBrodacstAddrx
dts4138NTPBrodcastIntervalx
dts4138NTPBroadcastTTLx
dts4138NTPBroadcastKeyx
dts4138NTPKeyTrusted
dts4138NTPKeyControl
dts4138NTPKeyRequest
dts4138NTPAutokeyPassword
dts4138NTPKeyGeneratorCmd
dts4138NTPKeyFileCmd
dts4138TimeManualSet
Manual
Time set
Time
Diff
W
W
Prod. number
Article number
HW revision
HW code
HW name
Firmware version
R
R
R
R
R
R
DTS state
DTS alarms
Alarm relay state
SNMP alarms (masked)
R
R
R
R
Trap state
Trap alarm number
R
R
ms
dts4138ManualTimeSetUTC
dts4138ManualTimeSetDiff
dts4138ProdInfo
dts4138ProdInfoProdNo
dts4138ProdInfoArticleNo
dts4138ProdInfoHWRevision
dts4138ProdInfoHWCode
dts4138ProdInfoHWName
dts4138ProdInfoFirmwareVer
Product Info
System Info
dts4138SysStatus
dts4138SysAlarms
Trap Info
© MOBATIME
92 / 104
800870.13
Trap error state
Trap time
Trap message
R
R
R
DTS stratum
Last drift
Last quartz corr
Act. corr. voltage
Current offset sec
Current offset us
Time of last time info
Jitter
Source quality
Offset of local source
Sample type
Source Type
Last DCF time
Last Link time
DCF pulse counter
Link pulse counter
Red. State
NTP source
NTP offset
NTP Jitter
NTP Stratum
NTP Frequency
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
Version DTS application
Version DTS module
Version FPGA module
Version FPGA
Version NTP
Version kernel
Version busybox (CLI)
Version rootfs
Version language
Version TZ table
Version snmp master
Version snmp common
R
R
R
R
R
R
R
R
R
R
R
R
Voltage 1
Voltage 1
Voltage 2
Voltage 2
Current 1
Current 1
Current 2
Current 2
R
R
R
R
R
R
R
R
IP v4
GW v4
Subnet v4
DNS v4
Hostname
Domain
DHCP
Link
IP v6 link local
IP1 v6
IP2 v6
GW v6
R
R
R
R
R
R
R
R
R
R
R
R
Update cmd.
Backup cmd.
Restore cmd
Restore default cmd
Restart cmd
Copy files cmd
Set all config changed
W
W
W
W
W
W
W
Time Info
sec
us
dts4138SystemTimeInfo
dts4138TinfoStratum, dts4138SysStratum
dts4138TinfoLastDrift, dts4138SysLastDrift
dts4138TInfoLastQCorr
dts4138VoltageQuartzAdjust
dts4138DCFTInfoOffsetSec
dts4138DCFTInfoOffsetUSec, dts4138SysOffset
dts4138TInfoLastTime
dts4138TInfoSourceJitter
dts4138SysTimeReceptionQuality
dts4138SysTimeSource
dts4138DCFTInfoLastTime
dts4138DCFTInfoLastLinkTime
dts4138DCFTInfoSecCount
dts4138DCFTInfoLinkSecCount
dts4138SysMasterMode
dts4138NTPTInfoCurrentSource
dts4138NTPTInfoSystemOffset
dts4138NTPTInfoSourceJitter
dts4138NTPTInfoStratum
dts4138NTPTInfoFrequency
dts4138SystemVersions
dts4138verApplication
dts4138verTimeDriver
dts4138verFPGADriver
dts4138verFPGA
dts4138verNTP
dts4138verLinux
dts4138verCLIShell
dts4138verRootFS
dts4138verLangResource
dts4138verTimezoneTable
dts4138verSNMPMasterAgent
dts4138verSNMPSubAgent
Versions
dts4138SystemPower
Power Info
V
mv
V
mv
A
mA
A
mA
2*Network
Info
dts4138SupplyVoltage2
dts4138SupplyCurrent1
dts4138SupplyCurrent2
dts4138NetworkInfox
dts4138NetInfoxIPAddr
dts4138NetInfoxIPGateway
dts4138NetInfoxIPMask
dts4138NetInfoxIPNameserver
dts4138NetInfoxDomain
dts4138NetInfoxDHCPMode
dts4138NetInfoxEthernetLinkMode
dts4138NetInfoxIPv6AddrLocal
dts4138NetInfoxIPv6Addr1
dts4138NetInfoxIPv6Addr2
dts4138NetInfoxIPv6Gateway
dts4138SystemMaintenance
dts4138SysUpdateCmd
dts4138SysBackupCmd
dts4138SysRestoreCmd
dts4138SysDefaultCmd
dts4138SysRestartCmd
dts4138SysCopyFiles
dts4138SysAllChanged
Commands
© MOBATIME
dts4138SupplyVoltage1
93 / 104
800870.13
© MOBATIME
94 / 104
800870.13
H
Technical data
Dimensions
19“ Rack, 1HU x 28PU (H x W x D [mm]) = 483 x 44 x 125
Weight
approx. 1.8 kg
Ambient temperature
0 to 60ºC, 10-90% relative humidity, without condensation
Operation
Telnet / SSH / MOBA-NMS (via LAN).
In addition, operation is also possible with SNMP.
Accuracy
GPS (DCF input) to NTP server:
GPS (DCF input) to DCF output:
IRIG input to DCF output:
NTP to internal time:
Notice:
Time keeping (internal)
typical < +/- 100 µs
typical < +/- 10 µs
typical < +/- 50 µs
typical < +/- 100 µs
NTP reception (DTS 4138 as client or as server to external clients) can be
influenced by the network traffic load and network devices (Hub, Switch,
Router, Firewall...).
If many clients request simultaneously, the typical accuracy may not be
reached.
- Synchronized with GPS:
+/-10 µs to UTC
Holdover (free run):
After at least 12 hours synchronization from the time source:
DTS 4138 -> TCXO: at 20°C +/- 5°C:
< +/- 10 ms / day (< 0.1ppm) *
at constant temperature*:
< +/- 1 ms / day (< 0.01ppm) *
Generally:
During power break (based on internal RTC):
at 20°C +/- 5°C:
< 5 ppm, but with jitter of +/- 15 ms *
After a power failure the RTC time is available during at least 5 days
(RTC buffered through a SuperCAP).
*measured over 24 h
Redundant operation
- Master to slave (optical DTS link):
Time server
NTP V4
SNTP
TIME
DAYTIME
typical < +/- 1 µs
(fully V3 compatible), RFC 1305, RFC 5905 (Port 123)
(UDP), RFC 2030 (Port 123)
(TCP/UDP), RFC 868 (Port 37)
(TCP/UDP), RFC 867 (Port 13)
Max. number of NTP and SNTP client requests: > 1500 requests / sec.
(e.g. client request every 60 sec. ➔ 90000 clients)
NTP mode
Server, Peer, Broadcast, Multicast
NTP slave clock lines:
1 line with up to 15 different time zone entries.
Communication through multicast:
-RFC 3376: Internet Group Management Protocol, Version 3
-RFC 1112: Host extensions for IP multicasting
-RFC 4601: Protocol Independent Multicast - Sparse Mode (PIM-SM)
-RFC 3973: Protocol Independent Multicast - Dense Mode (PIM-DM)
Time zones (see App. B) Up to 80 predefined, 20 programmable entries (MOBA-NMS)
2 Network interfaces
10BaseT / 100BaseTX (IEEE 802.3)
Data transmission rate: Auto-negotiation / manual
Connection:
RJ-45
Only shielded cables permitted.
IP Configuration
DHCP, Static IP, IPv4, IPv6
Network services
NTP
SNTP
TIME
© MOBATIME
UDP, Port 123
UDP, Port 123
TCP/UDP, Port 37
95 / 104
see timeserver
see timeserver
see timeserver
800870.13
DAYTIME
Telnet
SSH
SCP
SFTP
FTP
SNMP
SMTP
DHCP
DNS
DHCPv6
ECHO
TCP/UDP, Port 13
see timeserver
TCP, Port 23
operation
TCP, Port 22
operation
über SSH
update
über SSH
update
TCP, Port 21
update
UDP, Port 161
operation
UDP, Port selectable (162) alarm notification, see SNMP
TCP, Port selectable (25) alarm mail see E-Mail
UDP, Port 68
dyn. address allocation (client)
TCP/UDP, Port 53
address resolution (client)
only IPV6
ICMP
“Ping“
SNMP
V1, V2c, V3 with MD5 for authentication and DES for encryption (privacy).
E-mail
Alarm reporting via SMTP.
Authentication at the mail server:
- with sender address
- with username/password SMTP-Auth with LOGIN,
PLAIN (RFC 4954) or CRAM-MD5 (RFC 2195)
no “POP before SMTP“ possible
DCF input
DCF receiver or DCF from GPS, active current loop
Time zone:
selectable
Nominal 28 VDC, max. 32mA, response threshold 8mA
AFNOR-A/C, IRIG-B12x input:
Upp: 100mV – 5500mV
Time signal outputs
NTP V4 for slave clocks (unicast and multicast)
1 x IRIG-B output (analog and digital)
1 x DCF, programmable impulse / frequency output over RS 422 and
opto coupler (current loop passive)
1 x DCF current loop interface passive
1 x Script files configurable time telegrams on RS 232, RS 422 (only send)
and RS 485
DCF output (1x)
DCF 77 time code, time zone selectable
Max. time deviation with GPS source:
+/- 10 µs, jitter < 10 µs
DCF time code passive current interface:
Vmax = 30 VDC, Ion = 10..15 am, Ioff < 0.1 mA @20VDC
DCF / impulse /
frequency output (1x)
1 line for technical impulses:
time zone selectable, output signal correction possible (DCF and impulse)
Max. time deviation with GPS source:
+/- 10 µs, Jitter < 1 µs
Rise time typical: 100 ns
Mode:
- DCF time code
- impulses: sec., min., h., or user-defined
- frequency: 1Hz.. 5MHz (no square signal possible above 2MHz)
2 different electrical outputs with the same signal:
- passive current loop output, opto coupler: Imax.=10 mA / Umax.=50 VDC
- RS422 output: signal levels 0V / 3.3V
© MOBATIME
96 / 104
800870.13
IRIG-B output (1x)
1 high precision IRIG line, available as analog and digital signals.
Max. time deviation to GPS (with GPS source):
DC level:
< +/- 10 µs
Modulated:
< +/- 200 µs
Accuracy of the signal according to standard:
DC level pulse rise time between the
10 and 90% amplitude points:
Jitter modulated at carrier frequency:
DC level jitter pulse-to-pulse:
≤ 1 µs
≤ 1%
≤ 200 ns
Line mode: IRIG-B122, IRIG-B Std 12h (B122),
IRIG-B123, IRIG-B DIEM, AFNOR A, AFNOR C, DCF-FSK
IRIG-B126 (127),
IRIG-B002, IRIG-B003, IRIG-B006 (007)
Output voltage level
(RL=50 Ohm):
0.1 – 5.5 Vpp (configurable)
SNR|dB:
typical >= 40dB
Impedance:
Ri < 50 
Opto coupler outputs:
Imax.=10 mA / Umax.=50 VDC
RS422 outputs:
U = typical 3.3 VDC
Serial interface (1x)
1 line for telegram output RS232, RS422 or RS485
Max. time deviation to internal time: +/- 10 ms, Jitter < 10 ms
300-38400 Bauds, 7 or 8 Data bits, Parity: no, even, odd,
Stop bit: 1 or 2, no flow control)
The description of the telegram function is provided in Appendix E.
Signal levels: RS 422/485 = 0 / 3.3V ; RS232 = -6V / +6V
USB plug
USB host for USB stick
Alarm contact
Opening relay contact (Alarm active ➔ contact open).
Switching load:
30 W (125 VDC or 1 A), e.g. 1 A @ 30 VDC
or 60 VA (150 VAC or 1 A), e.g. 0.5 A @ 120 VAC
Alarm reporting /
Error reporting
Alarm contact
E-mail
SNMP notification
Display
Alarm-LED
Alarm input
18-36 VDC, max. 6mA
Function configurable
DTS Link
Plug-in position for mini GBIC module (GigaBit Interface Converter)
1000Mbps, 3,3V (with LC connector)
e.g. D-Link DEM-311GT, SX 850 nm, 1.25 Gbps/MM/3.3 V
Maximal cable length depends on type of cable:
- Multimode fiber with a diameter of 50 µm:
max. 550 m
- Multimode fiber with a diameter of 62.5 µm:
max. 275 m
With LX standard, longer cables can be achieved.
Display
2 lines with up to 16 characters for the display of status information.
DC power supply
24 VDC +20% / -10% ; 0.7 A ; 10 W
Power supply output
Nominal 24 VDC, max. 200 mA (respectively according to power supply)
© MOBATIME
see Alarm contact
see E-mail
see SNMP trap
see Display
-
97 / 104
800870.13
I
Index
2
2 LAN Mode
E
34, 67
A
Accuracy
Alarm
Alarm configuration
Alarm input
Alarm list
Alarm mask
Alarm relay
Alarm status
Authentication
Autoconf – Ipv6
Autokey
93
44
39
44, 95
79
40
40, 95
14
42, 64
48
65
27
15
37
68
24
54
54
59
98
74
76
73
74
74
74
76
38
88
42
D
Data bit
27
Daylight Saving Time
78
DAYTIME
94
DC power supply
72, 74, 95
DCF – connection
76
DCF input
75
DCF output
25, 75, 94
Default values
15, 89
DES – Data Encryption Standard
64
DHCP
47
DHCPv6
48
Display
14
DST
78
DTS (Distributed Time System)
11
DTS Link
34, 66, 74, 75, 95
© MOBATIME
Factory settings
Firmware
Front connections
FTP
15, 54, 89
14
73
48, 58, 94
G
GBIC
GBIC Module
GNSS 3000
GPS 4500
74, 75, 95
66
76
76
I
C
Community (SNMP)
Configuration
Configuration – Backup
Configuration – Restore
Configuration – save
Connection table (to fill in)
Connections – alarm relay
Connections – DCF & GPS
Connections – front view
Connections – IRIG-B12x input
Connections – IRIG-B12x outputs
Connections – rear view
Connectors
Control Key
Copyright
CRAM-MD5
41, 94
F
B
Baudrate
Boot time
Broadcast NTP
E-mail
98 / 104
Initial configuration
Interface
IPv4 configuration
IPv6 – FTP connection
IPv6 configuration
15
83
47
58
48
K
Key
64
L
Language setting
Leap second
Leap second mode
LED description front side
LED-Beschreibung Rückseite
Lines
Linux
Login (menu)
45
64
39
13
13
25
16
16
M
Maintenance
Manual time set
MD5
Menu login
Menu structure
MIB files
mini GBIC
MOBA-NMS
Multicast
Multicast address
Multicast NTP
54
39, 62
64
16
17
68
66, 74, 75, 95
11, 16, 18, 55, 93
30, 93
35
37
N
Network configuration
Network services
Notification
NTP
NTP as backup time source
NTP authentication
NTP Autokey
46
48, 93
69
94
35, 63
38, 64
65
800870.13
NTP broadcast
NTP mode
NTP multicast
NTP server
NTP slave clocks
NTP symmetric keys
NTP time source
NTP version
ntp.keys
ntpq
37
93
37
35
30, 93
64
23, 36
63
38
21
O
Operation (menu)
Operation (MOBA-NMS)
Operation (SNMP)
16
18
69
P
Parameters
Parity
Password
Password configuration
Power setting
Power supply
Problem solving
Program file
89
27
7, 16
45
45
72
81
60
R
Redundant NTP Multicast time server
Redundant operation
Request Key
Restart
RTC
RTC (Real Time Clock)
RTC mode
31
34, 66
38
15, 54
93
61
33
S
SCP
Script file definition
Season table
Security - network
Serial telegrams
SFTP
SMTP
SNMP
SNMP – alarm notification
SNMP – alive notification
SNMP – notification
SNMP – operation
SNMP access configuration
© MOBATIME
59, 94
84
77
7
27, 83
58, 94
94
12, 68, 94
71
71
69
69
52
99 / 104
SNMP configuration
SNMP traps
SNMP user configuration
SNTP
Software update
Software version
Spring terminals
SSH
Standard settings
Start-up
Status menu
Stop bit
Stratum
43, 49
43, 69
51
94
55, 56
14
76
17, 48, 94
15, 89
15
20
27
62
T
Telegram – definition
Telegram file
Telnet
Terminal
TIME
Time acceptance
Time administration
Time server
Time source – configuration
Time source – time accepance
Time zone
Time zone for displayed time
Time zone selection
Time zone server
Time zone table
Time-keeping
Transmission time
Trap
Troubleshooting
Trusted Key
ttl (time to live)
84
27, 54, 60, 83
16, 48, 94
16
94
62
31, 61, 62
63, 93
32
62
77
45
53
30
77
33, 62
83
43, 69
81
38
37
U
Update – software
Update time zone table
USB
USB stick
UTC
55, 56
78
54, 56, 57, 60
14, 15
61, 78
V
Version
14
W
World time
30
800870.13
J
Connection table (to fill in)
Line
Type
Description
Example:
Line
Type
DCF
DCF out DCF for master clock ETC1
© MOBATIME
Description
100 / 104
800870.13
© MOBATIME
101 / 104
800870.13
© MOBATIME
102 / 104
800870.13
© MOBATIME
103 / 104
800870.13
© MOBATIME
BE-800870.13