MOUNTING AND

INSTRUCTION MANUAL
DTS 4135.timeserver
Network – Time Server and Master Clock

© MOBATIME BE-800729.11
 Certification of the Producer

STANDARDS
The DTS 4135.timeserver was developed and produced in accordance with the EU Guidelines:
2006 / 95 / EC
2004 / 108 / EC
96 / 48 / EC

This product belongs to Class A in accordance with EN 55022.

This equipment can lead to radio interference. In this case, actions must be taken by the user.

References to the Instruction Manual

1. 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.
2. 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.
3. 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.
4. We do not answer for direct or indirect damages, which could occur, when using this Manual.
5. 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.
6. The installation must only be carried out by skilled staff.
7. 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 800729.11

 Overview

1 Safety ......................................................................................................................................................... 6
2 Maintenance .............................................................................................................................................. 8
3 General Information: Introduction ............................................................................................................ 9
4 Displays ................................................................................................................................................... 13
5 Installation................................................................................................................................................ 15
6 Operation ................................................................................................................................................. 17
7 Updates.................................................................................................................................................... 61
8 Time administration................................................................................................................................. 67
9 SNMP....................................................................................................................................................... 73
10 Power supply variants............................................................................................................................. 79

APPENDIX
A Connection diagrams .............................................................................................................................. 80
B Time zone table....................................................................................................................................... 84
C Alarm list .................................................................................................................................................. 87
D Troubleshooting....................................................................................................................................... 89
E Serial Telegrams ..................................................................................................................................... 91
F Copyright notice ...................................................................................................................................... 96
G Technical data ......................................................................................................................................... 97
H Index....................................................................................................................................................... 100
I Connection table (to fill in) .................................................................................................................... 102

© MOBATIME 3 / 104 800729.11

Table of contents
6.5.15 Alarm mask ...................................................... 43
1 Safety .................................................................6 6.5.16 E-mail............................................................... 44
1.1 Safety instructions...................................... 6 6.5.17 SNMP traps ...................................................... 46
1.2 Symbols and Signal Words used in this 6.5.18 Alarm input ....................................................... 48
6.5.19 General settings................................................ 49
Instruction Manual...................................... 6 6.5.20 Network............................................................ 50
1.3 Intended Use ............................................. 6 6.5.21 Services (network services FTP, telnet, SSH...)... 53
1.4 Observe operating safety! .......................... 7 6.5.22 SNMP .............................................................. 54
1.5 Consider the installation site!...................... 7 6.5.23 SNMP V1 / V2c................................................. 55
6.5.24 SNMP V3 ......................................................... 56
1.6 Please observe the electromagnetic 6.5.25 Time zone selection .......................................... 59
compatibility! .............................................. 7 6.6 Maintenance menu ...................................60
2 Maintenance ......................................................8 7 Updates ........................................................... 61
2.1 Troubleshooting: Repairs ........................... 8 7.1 Updating images with MOBA-NMS ...........61
2.2 Cleaning .................................................... 8 7.2 Updating images with FTP........................61
2.3 Disposing................................................... 8 7.3 Updating applications or configurations
3 General Information: Introduction ....................9 with FTP...................................................62
7.4 Updating images via USB.........................62
3.1 Scope of Delivery....................................... 9
7.5 Updating applications or configurations
3.2 Technical Data........................................... 9
3.3 Device Description in this Manual............... 9 via USB....................................................63
3.4 Introduction.............................................. 10 7.6 FTP connection ........................................64
3.5 Device types ............................................ 10 7.7 SFTP connection......................................64
3.6 DTS distributed time system..................... 11 7.8 SCP connection........................................65
3.7 MOBA-NMS - Network Management 7.9 Save configuration externally....................65
System..................................................... 11 7.10 Copying Telegram files to the DTS
3.7.1 Overview of the main functions...........................12 4135.timeserver........................................66
3.7.2 Device management..........................................12 8 Time administration........................................ 67
4 Displays ...........................................................13 8.1 Concept of time administration..................67
4.1 LED displays front side............................. 13 8.2 Time acceptance......................................68
4.2 LED indication back side .......................... 13 8.3 Time acceptance from an external source
4.3 Display..................................................... 14 (DCF or GPS)...........................................68
5 Installation........................................................15 8.4 Time acceptance from external AFNOR-
A/C, IRIG-B12x source .............................69
5.1 Installation Guidelines .............................. 15 8.5 Time acceptance from NTP ......................69
5.2 Connections............................................. 15 8.6 NTP as backup.........................................69
5.3 Boot procedure of the DTS 8.7 Time server..............................................69
4135.timeserver ....................................... 15 8.8 Time accuracy, time-keeping ....................69
5.4 Firmware.................................................. 15 8.9 Leap second.............................................70
5.5 Basic settings (factory settings)................ 16 8.10 NTP Authentication ..................................70
6 Operation .........................................................17 8.10.1 NTP symmetric keys ......................................... 70
8.10.2 NTP Autokey .................................................... 71
6.1 General.................................................... 17 8.11 Redundant operation of 2 DTS
6.1.1 Serial connection...............................................18
6.1.2 Telnet ...............................................................18
4135.timeservers......................................71
6.1.3 SSH..................................................................18 9 SNMP .............................................................. 73
6.1.4 Menu structure ..................................................19
6.2 MOBA-NMS operation.............................. 20 9.1 General ....................................................73
6.3 Main menu ............................................... 21 9.2 Device configuration with SNMP...............74
6.4 Status menu............................................. 22 9.3 DTS subagent SNMP notification..............74
6.4.1 Time information and status ...............................24 9.3.1 Start up [dts4135StartUp] ................................. 74
6.4.2 Time source information.....................................25 9.3.2 Shutdown [dts4135Shutdown]............................ 74
9.3.3 Status changed [dts4135StatusChanged] ........... 75
6.5 Configuration menu.................................. 26 9.3.4 Configuration changed
6.5.1 Lines ................................................................27 [dts4135ConfigChanged] ................................... 75
6.5.2 DCF – output.....................................................27 9.3.5 Alive notification [dts413xAlive] .......................... 78
6.5.3 DCF / Pulse / Frequency output 1 and 2..............28 9.3.6 Alarm notification [dts413xAlarm] ....................... 78
6.5.4 Serial interface 1 and 2 ......................................29
6.5.5 IRIG / AFNOR / DCF-FSK Output 1 and 2...........31 10 Power supply variants .................................... 79
6.5.6 NTP slave clocks / time zone server ...................32
6.5.7 Time administration ...........................................33
6.5.8 Time source......................................................34
6.5.9 Time adjustment / Time-keeping.........................35
6.5.10 Redundant operation .........................................36
6.5.11 NTP server........................................................37
6.5.12 Manual time set / Leap second ...........................41
6.5.13 Alarms ..............................................................42
6.5.14 Alarm relays......................................................42

© MOBATIME 4 / 104 800729.11

A Connection diagrams ......................................80
A.1 Front connections .................................... 80
A.2 Connections (rear view) ........................... 81
A.3 Plug-in spring terminals ............................ 83
A.4 Connection GPS 4500 or DCF 4500......... 83
A.5 IRIG-B00x Digital Output TTL connection. 83
B Time zone table...............................................84
C Alarm list ..........................................................87
D Troubleshooting...............................................89
E Serial Telegrams .............................................91
E.1 General.................................................... 91
E.2 Syntax of the telegram configuration file ... 92
F Copyright notice ..............................................96
G Technical data .................................................97
H Index...............................................................100
I Connection table (to fill in) ............................102

© MOBATIME 5 / 104 800729.11

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!
! Please observe this safety message to avoid bodily harm and injuries!

Caution!
! Please observe this safety message to avoid damages to property and devices!

Notice!
Additional information for the use of the device.

1.3 Intended Use

The DTS 4135.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 4135 has 2
such lines.
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.

© MOBATIME 6 / 104 800729.11

 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!  This product belongs to Class A in accordance with EN 55022.
This equipment can lead to radio interference. In this case, measures must be taken
by the user.

© MOBATIME 7 / 104 800729.11

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 8 / 104 800729.11

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 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
- plug 3-pole black for power supply
- spring terminal 12-pole orange
- spring terminal 8-pole orange
- spring terminal 5-pole orange
- spring terminal 2-pole orange
 2 pcs mounting tools with spring terminals

3.2 Technical Data

See Appendix "G Technical data".

3.3 Device Description in this Manual

This instruction manual is for the master clocks DTS 4135.timeserver and DTS
4136.timeserver. Below both models (DTS 4135 and DTS 4136) will be referred to as
DTS 4135 or DTS 413x with the exception of time-keeping.

© MOBATIME 9 / 104 800729.11

 3.4 Introduction
The DTS 4135.timeserver is a NTP Time Server for use in network environments. It
can be synchronized by DCF or GPS (e.g. from GPS4500), 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.
In addition, as a master clock the DTS 4135 provides two independent IRIG/AFNOR
lines (each available as analog and digital (current loop and RS422) output), two
independent serial interfaces for the output of time telegrams (programmable by script
files), as well as two output lines for technical pulses (pulse/ frequency/ DCF).
As the "main“ master clock, the DTS 4135 can synchronize other master clocks or
other equipment with DCF and monitor with 1 alarm input.
The DTS 4135 can send both e-mails and SNMP traps for alerting purposes.
Using MOBA-NMS and SNMP, the DTS 4135 can be fully operated and its
configuration and system status can be requested.
To maintain a redundant time source, two DTS 4135 can be linked by an optical link.

3.5 Device types

Model: Features: Product no.:

According above description with TCXO
DTS 4135.timeserver 203661
(temperature compensated quartz)
Like DTS4135 but with OCXO
DTS 4136.timeserver („heated“ quartz) 203967

Device descriptions:
Since the only difference between DTS 4135 and DTS 4136 is the quartz, no difference
is made on the front plate. It always has DTS 4135.timeserver printed on it. The precise
description is made on the identification label on the back.

1
With IRIG-B synchronization the date must be set manually once or by another time source (GPS).

© MOBATIME 10 / 104 800729.11

 3.6 DTS distributed time system
The 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.7 MOBA-NMS - Network Management System

MOBA-NMS is a 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.
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.

© MOBATIME 11 / 104 800729.11

 3.7.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.7.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.7.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 800729.11

4 Displays

4.1 LED displays front side

Description Color Status Description

Power Green On Mains or DC power supply is in order

Off No power supply
Alarm Red On The alarm relay signalizes an alarm
Off No active alarms
Sync Green On DTS 413x can read the time from a synchronization
source
Off Synchronization source is not available
LAN control lamps:
Left Green Blinking Network activity
Orange Blinking No connection to network
Right Yellow Off 10 Mbit
On 100 Mbit

4.2 LED indication back side

Description Color Status Description

DCF reception red Blinking DCF (GPS reception)

© MOBATIME 13 / 104 800729.11

 4.3 Display

Display showing the current status of the DTS 413x.timeserver.

Display of: -Time, date

-Current time source
-Stratum of the DTS 413x.timeserver
-Software version
-IPv4 address
-IPv6 address
-Alarm summary
-Current alarms
The display can be operated by means of the corresponding “Display“ button:
First press the button briefly: Switch on the background light
Other buttons to press briefly: Scroll through all displays
Press button longer (>3 sec): 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. Should only telegram files be
copied, this can be activated directly with the button. (Press the button until the copy
process starts).

© MOBATIME 14 / 104 800729.11

5 Installation

5.1 Installation Guidelines

Danger! Always consider:

For mains power supply, a plug is located on the rear side of the DTS 413x. This
power plug separates the device from the power.
The DTS 413x must be unplugged from the mains power supply for maintenance
or wiring by pulling this plug.
The plug supplied may only be connected by a licensed electrician.
The effective national installation requirements and guidelines must be followed.

5.2 Connections
The connections are specified in Appendix "A Connection diagrams".
Only connect the designated devices to the various inputs and outputs.

5.3 Boot procedure of the DTS 4135.timeserver

The normal booting time of the DTS 4135 is approx. 60 sec. with pre-set IP or with
DHCP. The booting procedure of the operating system is displayed on the serial
console. After that, 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.4 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 
Customer Data  Product Ressources  Time Server.

© MOBATIME 15 / 104 800729.11

 5.5 Basic settings (factory settings)
General Internal time zone MEZ
Menu password dts
Power single
Language English
Time source Source DCF-GPS (UTC)
Alarm delay for failure 60 min
Stratum auto
Error stratum 12
DCF timeout 24hrs
DCF correction 0ms
Offset per stratum 50ms
Max. offset time ok 50'000us
Time-keeping Mode Catch up
Catch up speed 100'000ns/s
Quartz type 0
Synch only offset 800ms
Redundant operation off
Lines DCF77 output on, UTC
DCF77/pulse/freq. output 1 off
DCF77/pulse/freq. output 2 off
Serial interface 1 off
Serial interface 2 off
IRIG/AFNOR line 1 off
IRIG/AFNOR line 2 off
NTP slave clocks /
Time zone server off
Network DHCP on
DHCPv6 off
Autoconf IPv6 off
Link auto
Hostname DTS4135
Alarm Relay all on
Mail off
SNMP traps off
NW Services SSH on
Telnet on
FTP on
SNMP Modus off
RO-Community romobatime
RW-Community rwmobatime
SNMP Traps Mode off
Trap Community trapmobatime

© MOBATIME 16 / 104 800729.11

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,
SSH, or via a serial terminal. The serial terminal is particularly used for the first
configuration. 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 10 min. without operation, and any possible connection via
Telnet or SSH is interrupted.

Backspace:
Backspace must be set to "delete“ with the serial terminal:
For example, for Hyperterminal under "File  Properties  Settings - Backspace
sends DEL" must be selected.

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.

© MOBATIME 17 / 104 800729.11

 6.1.1 Serial connection
38400 Bauds, 8 data bits, no parity, 1 stop bit.
Windows 2000, XP, Vista: HyperTerminal
Linux: Minicom
Switch off Xon/Xoff and hardware handshake.
After establishing the serial connection, the menu can be initialized with ENTER.
When rebooting, the boot process will be displayed on the serial console.
Warning: The serial connection should always be disconnected before switching off

! the operating PC (exit terminal program or pull out the RS232 plug).

6.1.2 Telnet
Windows 98, 2000, XP, Vista, Windows 7: Start  Run  telnet [IP address]
Password: by default, no password
NetTerm (Shareware)
Linux: Start console and enter “telnet [IP-address]

6.1.3 SSH
Windows 98, 2000, XP, Vista, Windows 7: e.g. with Putty
Linux: Start console and enter “ssh dts@[IP address]“

© MOBATIME 18 / 104 800729.11

 6.1.4 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 4135, 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 19 / 104 800729.11

 6.2 MOBA-NMS operation
For the configuration of DTS devices via GUI, MOBA-NMS (see chapter „3.7 MOBA-
NMS - 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 of a DTS 4801.masterclock:

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 20 / 104 800729.11

 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 4135
See chapter “6.5 Configuration Menu“
Maintenance: Software update, backup and restore
See chapter “6.6 Maintenance Menu“

© MOBATIME 21 / 104 800729.11

 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.

1. Requesting alarm status, display of all the DTS 4135 active errors.
Display of the DTS 4135 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 4135 active alarms are
displayed, masking (e-mail, traps, relay) only occurs later.
2. Alarm history display.
Display of the DTS 4135 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.
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 4135 system information display (internal status, regulation voltage of the
quartz..). This information is for support purposes only.
8. Product information's like serial number, firmware version etc.
9. All several software versions of the DTS 4135.

© MOBATIME 22 / 104 800729.11

 Status menu page 2:

Display of information with regard to the internal state of the NTP server.

© MOBATIME 23 / 104 800729.11

 6.4.1 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

© MOBATIME 24 / 104 800729.11

 6.4.2 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
- 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

© MOBATIME 25 / 104 800729.11

 6.5 Configuration menu

Configuring the DTS 4135 through various submenus:

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 "6.5.7 Time Administration"
3. Alarm settings (alarm relay, e-mail, SNMP)
See chapter "6.5.13 Alarms"
4. General settings of the DTS 4135 (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/PUT.
See chapter "6.5.22 SNMP" (Traps are dealt with in menu ’2. Configuration’ ’3.
Alarms’  ’3. Traps’. See also chapter 6.5.17 SNMP Traps)

© MOBATIME 26 / 104 800729.11

 6.5.1 Lines
Under lines, settings can be undertaken for the following functions:
1 DCF - Output  see chapter 6.5.2
2 DCF / Pulse / Frequency output 1  see chapter 6.5.3
3 DCF / Pulse / Frequency output 2  see chapter 6.5.3
4 Serial Interface 1  see chapter 6.5.4
5 Serial Interface 2  see chapter 6.5.4
6 IRIG / AFNOR / DCF-FSK output 1  see chapter 6.5.5
7 IRIG / AFNOR / DCF-FSK output 2  see chapter 6.5.5
8 NTP slave clocks / time zone server  see chapter 6.5.6

6.5.2 DCF – output

The DTS 4135 is equipped with one DCF output line (DCF main out).
This line is available on the electrical current loop DCF output.

1. Select line function: off or DCF on

2. Select time zone -> see chapter “6.5.25 Time Zone Selection“

© MOBATIME 27 / 104 800729.11

 6.5.3 DCF / Pulse / Frequency output 1 and 2

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 (1…5000Hz)

© MOBATIME 28 / 104 800729.11

 6.5.4 Serial interface 1 and 2
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 “SELECT FILE“
Notice: To set the parameters, the line type has to be selected first.

The description of the telegram function and the telegram file can be found in Appendix
E Serial Telegrams.

© MOBATIME 29 / 104 800729.11

 Selection of the telegram file:

The copy procedure of telegram files is explained in chapter "7.10 Copying telegram
files to DTS 4135.timeserver".

© MOBATIME 30 / 104 800729.11

 6.5.5 IRIG / AFNOR / DCF-FSK Output 1 and 2

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:
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:
When the output voltage falls below the defined voltage level, an alarm is released.

Notice: 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.

© MOBATIME 31 / 104 800729.11

 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
maitenance) = 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“.

Notice: x Changes of multicast-address, pollinterval and TLL lead to a restart of

the NTP server.

Notice: x 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.

© MOBATIME 32 / 104 800729.11

 Notice: Redundant Multicast time server:
If in the same network two NTP server should send NTP with 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 administration

Under time administration, settings can be undertaken for the following functions:
 Time source configuration  see chapter “6.5.8 Time Source“
 Time adjustment configuration  see chapter “6.5.9 Time Adjustment / Time
Keeping“
 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 “

© MOBATIME 33 / 104 800729.11

 6.5.8 Time source
Time source configuration.

1. Type of time source: 0=none, 1=DCF low quality (DCF 77 receiver, MET),
2=DCF high quality (GPS receiver, UTC),
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”
4. DTS stratum: 0=Stratum is automatically calculated according to
the time source.
1-15=Stratum is manually set
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’000ms). Stratum is calculated with this value when
time is received again:
Offset/Stratum = 30ms, offset of the time source 150ms  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
For description of time source see chapter “8 Time Administration“

© MOBATIME 34 / 104 800729.11

 6.5.9 Time adjustment / Time-keeping

1. Adjust mode: 0=time is slowly adjusted (accord. to "Max. catch-up speed")

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

© MOBATIME 35 / 104 800729.11

 6.5.10 Redundant operation

1. Mode: 0=single operation, 1=operation in combination with a 2 nd DTS 4135

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 2 nd DTS 4135. 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 4135.timeservers“

© MOBATIME 36 / 104 800729.11

 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 37 / 104 800729.11

 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 a exact synchronization it’s better to limit Maxpoll to 6 (64 sec.).
4. Set type of inquiry: server or peer
5. Preferred source: on or off
6. Authentication key: off, key number, autokey

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.

© MOBATIME 38 / 104 800729.11

 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: All changes lead to a restart of the NTP server.

© MOBATIME 39 / 104 800729.11

 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.
8. Access control for query: 0= full access (off)
1 = access from local network allowed (local)
2 = no access (on)

© MOBATIME 40 / 104 800729.11

 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
-1 Second will be left out at entered time
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”.

© MOBATIME 41 / 104 800729.11

 6.5.13 Alarms
Under alarms, settings can be undertaken for the following functions:
 Alarm relays  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

6.5.14 Alarm relays

1. Alarm mask for relay (see chapter "6.5.15 Alarm mask")

© MOBATIME 42 / 104 800729.11

 6.5.15 Alarm mask

Display of all the DTS 4135 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 43 / 104 800729.11

 6.5.16 E-mail

1. E-mail function on or off.

2. Alarm mask for e-mail notifications (see chapter "6.5.15 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: Configuration of a gateway is required for sending e-mails (see chapter

"6.5.20 Network"). This can be set via DHCP or manually.

© MOBATIME 44 / 104 800729.11

 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 <DTS4135 (10.241.0.30)>

© MOBATIME 45 / 104 800729.11

 6.5.17 SNMP traps
For a description of SNMP functionality, see also chapter “9 SNMP“.

1. Trap mode on or off

2. Alarm mask for SNMP trap messages (see chapter "6.5.15 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

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 SNMP DTS Agent.

© MOBATIME 46 / 104 800729.11

 Configuration of the receiving systems

1. Address of the evaluation system e.g. 10.240.10.50.

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 SNMP DTS Agent.

© MOBATIME 47 / 104 800729.11

 6.5.18 Alarm input
Description of the functionality of the alarm input.

1. Mode off, on oder inverted.

© MOBATIME 48 / 104 800729.11

 6.5.19 General settings

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.

© MOBATIME 49 / 104 800729.11

 6.5.20 Network

1. Configuration of IPV4 parameters

2. Configuration of IPv6 parameters
3. Set host name.
Notice: 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!
4. Set domain e.g. test.org
5. Set network interface: Auto, 100/10Mbit, half-, full duplex.
View of the current network state in Menu: ‘1 Status’  ‘6 Info network config.'
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).

Notice: Modifications to the network must be coordinated with the network

administrator!

© MOBATIME 50 / 104 800729.11

 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 413x.

2.-5. Set IP address, subnet mask, gateway and DNS-Server. Format = 10.240.98.7

© MOBATIME 51 / 104 800729.11

 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

© MOBATIME 52 / 104 800729.11

 6.5.21 Services (network services FTP, telnet, SSH...)
Network services configuration:

1.-3. Switch the individual services off or on.

© MOBATIME 53 / 104 800729.11

 6.5.22 SNMP
For a description of SNMP functionality, see also chapter “9 SNMP“.

1. Mode. 0=off, 1=on. SNMP information of MIB 2 is always available.

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 / V2c (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: Each configuration change leads to a restart of the DTS SNMP Agent.

© MOBATIME 54 / 104 800729.11

 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: Each configuration change leads to a restart of the DTS SNMP Agent.

© MOBATIME 55 / 104 800729.11

 6.5.24 SNMP V3

1. – 2. Configuration of user-defined SNMP accounts dtsUser1 and dtsUser 2

3. – 4. Configuration of user-defined SNMP access rights viewDTS1 and viewDTS2

Notice: Each configuration change leads to a restart of the DTS SNMP Agent.

© MOBATIME 56 / 104 800729.11

 User configuration SNMP V3:

1. Password for authentication (MD5) and privacy (DES). 8 – 40 characters.

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)

4. SNMP write 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)

Notice: Each configuration change leads to a restart of the DTS SNMP Agent.

© MOBATIME 57 / 104 800729.11

 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: Each configuration change leads to a restart of the DTS SNMP Agent.

© MOBATIME 58 / 104 800729.11

 6.5.25 Time zone selection

Display of all the DTS 4135 time zones (100) over several pages. The pages can be
scrolled through with ENTER.
A time zone can be selected on the actual page by entering a time zone number.
Only one time zone can be selected.
Press ESC to leave the page. The modifications will be saved or restored one menu
level higher.

© MOBATIME 59 / 104 800729.11

 6.6 Maintenance menu

1. Initiating a software update (files must have been copied by FTP into the directory
/ram of the DTS 413x.timeserver before).  See chapter "7 Updates".
The command always leads to a restart of the DTS 413x (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
413x.timeserver).  See chapter "7 Updates".
The command always leads to a restart of the DTS 413x (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 (dts4135system_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 dts413x.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 413x.
8. Copy telegram files onto the DTS 413x.
 See chapter "7.10 Copying telegram files onto the DTS 4135.timeserver ".

See also chapter "7 Updates".

© MOBATIME 60 / 104 800729.11

7 Updates

7.1 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 ‘dtscfg.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 413x is destroyed and it can only be repaired in the
factory.

7.2 Updating images with FTP

Possible images are: u-boot.bin, rootfs.img, uImage26, dtsapp.img, dtscfg.img.
Additionally the file dtscheck.md5 must exist.
 all file names are case-sensitive.
Steps for updating images:
1. Connect a FTP client software to the DTS 413x.timeserver e.g. with Internet
Explorer enter: ftp://dts@[IP address]) (as user dts).
See also chapter "7.6 FTP-Connection"
2. If an update of the image dtscfg.img is made, the configuration of the DTS
413x.timeserver and the telegram files are overwritten. In order to store the
configuration, the file dts413x.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 413x.timeserver in accordance with chapter “7.3
Updating applications or configurations via 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 413x.timeserver 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 413x.timeserver is
automatically restarted on completion of the update.
The Telnet or SSH session has to be restarted.

© MOBATIME 61 / 104 800729.11

 Notice: The update procedure (point 6) 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 413x will be
destroyed and it 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.3 Updating applications or configurations with FTP

To update individual files such as, e.g. dts4135, dts4135menu, ntpd, dts4135mod.ko,
dts4135.conf, etc. on the DTS 413x. timeserver, the following steps are carried out
 all file names are case-sensitive:
1. Connect a FTP client software to the DTS 413x.timeserver e.g. with Internet
Explorer enter: ftp://dts@[IP address]) (as user dts). See also chapter 7.6 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 413x.timeserver 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 413x 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 413x will be
destroyed and it 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.4 Updating images via USB

Possible images are: u-boot.bin, rootfs.img, uImage26, dtsapp.img, dtscfg.img.
Additionally the file dtscheck.md5 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 413x.timeserver
3. If an update of the dtscfg.img image is made, the configuration of the DTS
413x.timeserver and the telegram files are overwritten. In order to store the
configuration, the file dts413x.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 413x.timeserver in accordance with chapter
“7.3 Updating applications or configurations via FTP“.

© MOBATIME 62 / 104 800729.11

 4. The update procedure can be started on DTS 413x 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 413x is automatically
restarted on completion of the update.
The Telnet or SSH session has to be restarted.
5. As soon as the DTS 413x 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 413x will be
destroyed and it 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.5 Updating applications or configurations via USB

To update individual files, e.g. dts4135, dts4135menu, ntpd, dts4135mod.ko,
dts4135.conf, etc. on the DTS 413x, the following steps are carried out
 all file names are case-sensitive, all names with 4135:
1. Copy applications (or configuration) to the USB stick
2. Plug the stick in the DTS 413x
3. The update procedure can be started on DTS 413x.timeserver 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 413x is
automatically restarted on completion of the update.
The Telnet or SSH session has to be restarted.
4. As soon as the DTS 413x 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 413x will be
destroyed and it 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.

© MOBATIME 63 / 104 800729.11

 7.6 FTP connection
Establish anonymous connection:
ftp://[IP address of DTS 413x]
to directly reach the sub-directory /ram, e.g. Explorer ftp://10.241.0.5

Establish connection as/with a user:

ftp://dts@[IP address of DTS 413x].
e.g. with Internet Explorer enter: ftp://dts@10.241.0.5
Password: dts resp. the defined password for the menu.
To directly reach the sub-directory /ram, you can also enter
ftp://dts@[IP address]/ram.

Establish connection with IPv6:

The address must be written in brackets [ ]:
e.g. with Internet Explorer enter: ftp://dts@[fd03:4432:4646:3454::2000]
Notice: The file has to be copied in binary mode (not ASCII).

FTP tools

Windows 98, ME, 2000, XP, Vista,

Linux (Suse, Redhat)
Windows 7

Integrated in the system Windows Explorer

Konqueror
(file manager): Start  Execute: Explorer

Programs (examples) CuteFTP Kbear

7.7 SFTP connection

SFTP= SSH File Transfer Protocol

SFTP-Tools

Windows 98, ME, 2000, XP, Vista,

Linux (Suse, Redhat)
Windows 7

Integrated in the system

- Konqueror
(file manager):

Programs (examples) WinSCP -

© MOBATIME 64 / 104 800729.11

 7.8 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 98, ME, 2000, XP, Vista,

Linux (Suse, Redhat)
Windows 7

Integrated in the system

- With command line
(file manager):

Programs (examples) WinSCP -

7.9 Save configuration externally

(for backup or copy to another DTS 4135)

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:
1. Connect a FTP client software to the DTS 413x (with Internet Explorer enter:
ftp://dts@“IP address“) (as user dts).
2. Change to the DTS 4135 directory /etc.
3. Save the file dts4135.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.

© MOBATIME 65 / 104 800729.11

 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 413x 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 413x:
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.3 resp. 7.5.
Notice: When copying the configuration from one DTS 413x to an other, the IP
address may have to be changed after the download by serial connection.

7.10 Copying Telegram files to the DTS 4135.timeserver

Analogously to the previously described procedures telegram files can be copied via
FTP or USB stick to the DTS 413x.timeserver.
The copy procedure can be started on DTS 413x by selecting the menu
'3. Maintenance'  ’8. Copy telegram-files' and press ENTER. Afterwards, select again
in the menu “6.5.4 Serial interface 1 and 2” 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: 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

© MOBATIME 66 / 104 800729.11

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 External AFNOR A/C

Time Source IRIG-B12x Source

(A) (B)
NTP
Time Zone Entry Time Zone Entry

(K) (C)
- Display
Time Zone Entry DCF
- Operation Time Zone Entry Line 2
-Error report UTC
(J) Master (D)
Clock
LAN Multicast Time Zone Entry DCF
Time Zone Entry
Devices Line 1
(E)
(I)
Time Zone Entry
Time Zone Entry
(H) (F)
Time Zone Entry Time Zone Entry
Serial Telegrams
(G) DCF Main
Line 1
Time Zone Entry
Serial Telegrams IRIG / AFNOR
Line 2 Line 2

IRIG / AFNOR
Line 1

Configurable time zones:

(A) chapter 6.5.8
(B) chapter 6.5.8
(C) chapter 6.5.3
(D) chapter 6.5.3
(E) chapter 6.5.2
(F) chapter 6.5.5
(G) chapter 6.5.5
(H) chapter 6.5.4
(I) chapter 6.5.4
(J) chapter 6.5.6
(K) chapter 6.5.19

© MOBATIME 67 / 104 800729.11

 8.2 Time acceptance
Variants of time synchronization
 Adjusting:
After starting the DTS 4135, 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.
Configuration: see chapter “6.5.9 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 4135 = 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: Stratum TO <0-16>, Stratum error timeout time 1-999 [h], for loss
of the external source
St_fix: 0..15, configurable stratum, 0 = auto
St_max: 1..16, configurable stratum, 0 = auto
t_current [s]: current time
t_lastsynch [s]: time of the last synchronization
Tst: Offset per stratum, 0..40'000 [ms], parameter time deviation for
stratum alteration by 1
Tdiff: current time difference in ms

© MOBATIME 68 / 104 800729.11

 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 timecodes do not provide information about the current year, the
DTS 4135 has to be synchronized first from an other 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: After more than 5 days without power, the DTS 4135 loses the date
information. When synchronized with IRIG-B120 to 123 it has to be set
again manually.

8.5 Time acceptance from NTP

Acceptance:
 As NTP RFC 1305 (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 then the actual NTP timeserver
Stratum in case of an error
 As NTP RFC 1305 (www.ntp.org)

8.6 NTP as backup

If the DTS 4135 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. est":Means: Expected NTP Stratum of the NTP sources
"St. est" = MAX(Stratum NTP candidates)
 Means: "St. est" contains the stratum value of the poorest NTP source.
If internal Stratum > "St. est" + 1, then change to NTP as source takes place
(internal stratum is one step higher then 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 (Port 123)
 SNTP (UDP), RFC2030 (Port 123)
 TIME (TCP/UDP), RFC 868 (Port 37)
 DAYTIME (TCP/UDP), RFC 867 (Port 13)

8.8 Time accuracy, time-keeping

See appendix G, Technical Data.

© MOBATIME 69 / 104 800729.11

 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.

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 4135 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 4135 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

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.

© MOBATIME 70 / 104 800729.11

 The keys are located in the ntp.keys file defined with keys. This has the following
format:
1 M TestTest
2 M df2ab658
15 M I_see!
498 M 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.

8.11 Redundant operation of 2 DTS 4135.timeservers

For redundant operation two DTS 4135 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 G, Technical Data):

mini GBIC Module

Both devices 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.

© MOBATIME 71 / 104 800729.11

 GPS
receiver

NTP
DTS Master

status, time
LWL connection (DTS Link)
GPS (option for redundant

receiver
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).
 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 assumes the master function.
 If the former master is working again, it assumes the actual time of the current
master and remains in slave mode.
 In the case of an 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, no longer
sends out any NTP, or has a worse status, the slave assumes the master function.

NTP
The NTP clients select the server with the lower stratum.
DCF77 coded (fiber optic output)
No redundancy

© MOBATIME 72 / 104 800729.11

9 SNMP

9.1 General
The SNMP version V2c or V3 for Get, Put and Notification (Trap) is used.
A full SNMP agent is implemented on the DTS (MIBII, DTS4135).
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).
MIBII 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
DTS4135 (DTS4135-MIB.TXT)
Device specific DTS definitions
SNMP V1:
DTS-COMMON (File: DTS-COMMON-MIBv1.TXT)
General DTS definition, always required
DTS4135 (DTS4135-MIBv1.TXT)
Device specific DTS definitions

The MIB files can be copied from the DTS 4135 with FTP (For FTP use, see chapter
“7.6 FTP Connection“):
DTS-MIB: /etc/snmp/mibs/
Standard MIBS: /usr/share/snmp/mibs/

© MOBATIME 73 / 104 800729.11

 9.2 Device configuration with SNMP
If one or several variables are set with Put in a configuration group, the variable
dts4135????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=accept).
As long as the accept command has not been set, the changed variables can be
restored to the old values by setting the dts4135????ConfigCmd variable to 2 (2=undo,
restore).
After sending the accept command, a dts4135ConfigChanged Notification is sent.
The definitions of the available variables can be taken from the MIB files.

Example:
Management-System DTS
Put dts4135FTPMode=1  Variable is set to 1 internally
Put dts4135NetServicesConfigCmd=1  Configuration group is assumed
 Sends dts4135ConfigChanged Notification
with the new time dts4135NetConfigChangedTime

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 Start up [dts4135StartUp]

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 [dts4135Shutdown]

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 74 / 104 800729.11

 9.3.3 Status changed [dts4135StatusChanged]
Sent out when the subagent detects a status change in the DTS application process.
The following variables are monitored for changes:
dts4135SysStatus, dts4135SysTimeSource, dts4135SysStratum,
dts4135SysMasterMode
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
dts413xSysStatus Unsigned Int 4 Bytes Contains the internal system 66309
status
dts413xSysOffset Integer 4 Bytes Actual time offset of the system -1523  -1.523ms
[us]
dts413xSysTimeSource Byte 1 Byte Actual time source 2
dts413xSysStratum Byte 1 Byte Actual system stratum level 1
dts413xSysMasterMode Byte 1 Byte Master/slave mode 1

9.3.4 Configuration changed [dts4135ConfigChanged]

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 Description
dts4135SysConfigChangedTime TimeTicks 4 Bytes Contains the TimeTicks value
of the last change in 1/100tth
seconds
dts4135NetServicesConfigChangedTime TimeTicks 4 Bytes
dts4135NetConfigChangedTime TimeTicks 4 Bytes
dts4135RedOpConfigChangedTime TimeTicks 4 Bytes
dts4135TSConfigChangedTime TimeTicks 4 Bytes
dts4135NTPConfigChangedTime TimeTicks 4 Bytes
dts4135OutLine1DCFConfigChangedTime TimeTicks 4 Bytes
dts4135OutLine2DCFConfigChangedTime TimeTicks 4 Bytes
dts4135OutLine1SerialChangedTime TimeTicks 4 Bytes
dts4135OutLine2SerialChangedTime TimeTicks 4 Bytes
dts4135OutLine1IRIGChangedTime TimeTicks 4 Bytes
dts4135OutLine1IRIGChangedTime TimeTicks 4 Bytes
dts4135OutLineTZServerConfigChangedTime TimeTicks 4 Bytes
dts4135RelayConfigChangedTime TimeTicks 4 Bytes
dts4135MailConfigChangedTime TimeTicks 4 Bytes
dts4135SnmpConfigChangedTime TimeTicks 4 Bytes

The ConfigChangedTime variables show the time of the last change of the relevant
configuration group. The management system can decide on the basis of these time
values, which configurations need to be reloaded.

© MOBATIME 75 / 104 800729.11

 Configuration group table
Configuration group Variable
dts4135SysConfigChangedTime dts4135Language
dts4135Timezone
dts4135Password
dts4135DisplayTimezone
dts4135DisplayTimeFormat
dts4135PowerSupply

dts4135NetConfigChangedTime dts4135IPAddr
dts4135IPMask
dts4135IPGateway
dts4135IPNameserver
dts4135Hostname
dts4135Domain
dts4135DHCPMode
dts4135EthernetLinkMode
dts4135IPv6AutoConf
dts4135IPv6DHCPMode
dts4135IPv6Addr1
dts4135IPv6Prefix1
dts4135IPv6Gateway1
dts4135IPv6Addr2
dts4135IPv6Prefix2
dts4135IPv6Gateway2
dts4135IPv6Nameserver

dts4135NetServicesChangedTime dts4135TelnetMode
dts4135FTPMode
dts4135SSHMode

dts4135TSConfigChangedTime dts4135TSType
dts4135TSStratumMode
dts4135TSStratumErrorLimit
dts4135TSTimeout
dts4135TSStratumTimeout1
dts4135TSOffsetPerStratum
dts4135TSMaxOffsetForTimeValid
dts4135TSDCFAdjusment
dts4135TSAdjusmentMode
dts4135TSMaxAdjusmentSpeed
dts4135TSQuartzType
dts4135TSOffsetSynchOnly
dts4135TSLeapSecMode
dts4135TSLeapSecDate

dts4135RedOpConfigChangedTime dts4135RedOpMode
dts4135RedOpSwitchOverStratum
dts4135RedOpMaxOffsetSlaveTimeSource
dts4135RedOp2ndDTSIPAddress
dts4135RedOp2ndDTSIPPort

dts4135NTPConfigChangedTime dts4135NTPBroadcastAddr1
dts4135NTPBroadcastInterval1
dts4135NTPBroadcastTTL1
dts4135NTPBroadcastKey1
dts4135NTPBroadcastAddr2
dts4135NTPBroadcastInterval2
dts4135NTPBroadcastTTL2
dts4135NTPBroadcastKey2
dts4135NTPSourceTable
(Address, min/max poll, mode, prefer)

dts4135RelayConfigChangedTime dts4135RelayAlarmMask

dts4135MailConfigChangedTime dts4135MailMode
dts4135MailAlarmMask
dts4135MailServerIPAddress

© MOBATIME 76 / 104 800729.11

 dts4135MailServerPort
dts4135MailAddrDestination1
dts4135MailAddrDestination2
dts4135MailAddrReply
dts4135MailAddrFrom
dts4135MailUser
dts4135MailPassword
dts4135MailAuthMode

dts4135SnmpConfigChangedTime dts4135SnmpMode
dts4135SnmpAlarmMask
dts4135SnmpROCommunity
dts4135SnmpRWCommunity
dts4135SnmpTrapMode
dts4135SnmpTrapAlarmMask
dts4135SnmpTrapCommunity
dts4135SnmpTrapListenerIPAddress1
dts4135SnmpTrapListenerPort1
dts4135SnmpTrapVersion1
dts4135SnmpTrapListenerIPAddress2
dts4135SnmpTrapListenerPort2
dts4135SnmpTrapVersion2
dts4135SnmpTrapAliveMsgInterval
dts4135SnmpLocation
dts4135SnmpContact
dts4135SnmpV3UserPassword1
dts4135SnmpV3UserLevel1
dts4135SnmpV3UserRead1
dts4135SnmpV3UserWrite1
dts4135SnmpV3UserPassword2
dts4135SnmpV3UserLevel2
dts4135SnmpV3UserRead2
dts4135SnmpV3UserWrite2
dts4135SnmpV3View11
dts4135SnmpV3View12
dts4135SnmpV3View13
dts4135SnmpV3View14
dts4135SnmpV3View15
dts4135SnmpV3View16
dts4135SnmpV3View21
dts4135SnmpV3View22
dts4135SnmpV3View23
dts4135SnmpV3View24
dts4135SnmpV3View25
dts4135SnmpV3View26

dts4135OutLineTZServerConfigChangedTime dts4135OutLineTZServerMode
dts4135OutLineTZServerMCastAddr
dts4135OutLineTZServerMCastPort
dts4135OutLineTZServerNTPInterval
dts4135OutLineTZServerTTL
dts4135OutLineTZServerTableInterval
dts4135OutLineTZServerEntryInterval
dts4135OutLineTZServerTable
(TZ entry number)

dts4135OutLine1DCFConfigChangedTime dts4135OutLine1DCFTimezone
dts4135OutLine1DCFPulseType
dts4135OutLine1DCFPulseTime
dts4135OutLine1DCFPulsePeriod
dts4135OutLine1DCFPulseCorrection
dts4135OutLine1DCFFrequency

dts4135OutLine2DCFConfigChangedTime dts4135OutLine2DCFTimezone
dts4135OutLine2DCFPulseType
dts4135OutLine2DCFPulseTime
dts4135OutLine2DCFPulsePeriod
dts4135OutLine2DCFPulseCorrection
dts4135OutLine2DCFFrequency

© MOBATIME 77 / 104 800729.11

 dts4135OutLine1SerialConfigChangedTime dts4135OutLine1SerialMode
dts4135OutLine1SerialTimezone
dts4135OutLine1SerialComMode
dts4135OutLine1SerialComParam
dts4135OutLine1SerialTeleFile

dts4135OutLine2SerialConfigChangedTime dts4135OutLine2SerialMode
dts4135OutLine2SerialTimezone
dts4135OutLine2SerialComMode
dts4135OutLine2SerialComParam
dts4135OutLine2SerialTeleFile

dts4135OutLine1IRIGConfigChangedTime dts4135OutIRIG1IRIGMode
dts4135OutLine1IRIGTimezone
dts4135OutLine1IRIGOutputLevel
dts4135OutLine1IRIGAlarmLevel

dts4135OutLine2IRIGConfigChangedTime dts4135OutIRIG2IRIGMode
dts4135OutLine2IRIGTimezone
dts4135OutLine2IRIGOutputLevel
dts4135OutLine2IRIGAlarmLevel

9.3.5 Alive notification [dts413xAlive]

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
dts413xSysStatus Unsigned Int 4 Bytes Contains the internal 66309
system status
dts413xSysAlarms Byte Array 8 Bytes 64 Bit Alarm flags FFF870FF.FFFFFFFF
1.Byte Bit 0..7 ¦ ¦ ¦
2.Byte Bit 8..15 ¦ ¦ 5.Byte
:: ¦ 2.Byte
8.Byte Bit 56..63 1.Byte

9.3.6 Alarm notification [dts413xAlarm]

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:
Field Type Size Description Example
dts413xTrapAlMsgErrorNr Byte 1 Byte No. of the alarm bit (0..63) 3
dts413xTrapAlMsgErrorState Byte 1 Byte 0 = alarm bit was deleted 1
1 = alarm bit was set
dts413xTrapAlMsgErrorTime Unsigned 4 Bytes PC-time in seconds since 946684805
Int 01.01.1970 00:00:00
dts413xTrapAlMsgErrorText Text 59 Bytes Error text Failure supply 1

© MOBATIME 78 / 104 800729.11

10 Power supply variants
The DTS 413x.timeserver permits 3 different power supply alternatives:
1. Mains supply with 90 – 240 V / 50 - 60 Hz
Notice: In the menu: ‘2 Configuration’  ‘4 General’  ‘3 Power’ must be set to
'0=single'.

2. 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'.

3. Redundant power supply

with the following variants:
Supply1: Supply2:
Variant 1 Mains supply DC in 2
Variant 2 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

Mains
85..265VAC AC/DC U, I, power
50/60Hz control fail

DC in 1
24VDC Supervision logic supply
+20%-10% DC/DC
24VDC out
(e.g. GPS4500)
DC in 2
24VDC Supervision power
+20%-10%

The mains supply and the DC in 1 input are internally linked, but protected against “Back
powering”.

© MOBATIME 79 / 104 800729.11

A Connection diagrams

A.1 Front connections

PC - Terminal Connection:
Type of connector: Sub-D 9p connector (male)
Interface: RS232
Baud rate: 38400 Bauds
Data Bits: 8
Parity: no
Stop Bit: 1
Flow control: no

Cable DTS 413x – PC: Crossed cable, female – female connectors (null modem)
(DTE-DTE) Max. length of the connection 3m

Connections between female connector 1 (SUB-D 9 / 1) and female connector 2 (SUB-D 9 / 2)

SUB-D 9 / 1 SUB-D 9 / 2
Receive Data * 2 3 Transmit Data
Transmit Data * 3 2 Receive Data
Data Terminal Ready 4 1&6 Data Set Ready & Carrier Detect
System Ground * 5 5 System Ground
Data Set Ready & Carrier Detect 1&6 4 Data Terminal Ready
Request to Send 7 8 Clear to Send
Clear to Send 8 7 Request to Send

* At least needed connections.

LAN Connection:
Plug: RJ45
Interface: Ethernet, 10/100Mbit half or full duplex
Use only shielded cables!

USB Connection:
Plug: USB-Host

Notice: Only permitted for the operations with a USB stick!

© MOBATIME 80 / 104 800729.11

 A.2 Connections (rear view)

DTS 4135 connections

For technical data see in Appendix "G Technical data"

Clamp Connection Description

L Mains connection phase Mains power input with rubber connector
Mains connection earth Break point: by disconnecting the rubber connector
See Appendix G
N Mains connection neutral

1 DC in 1 power supply + Input for external DC supply

2 DC in 1 power supply GND Ground

3 DC in 2 power supply + Input for external DC supply

4 DC in 2 power supply GND Ground

5 Alarm relay Alarm contact, open when alarm is active

6 Alarm relay Max. load: 30 W (60 VDC or 1A)
or 60 VA (30 VAC or 1A)

7 Alarm input + Nominal 24 VDC, max. 100 mA

8 Alarm input - Alarm input: e.g. for external closing contact between
Alarm_in + and Alarm_in - .
Or voltage input: 18-36 VDC, max. 6mA
Voltage level “high” (24V available) or external contact
closed  configurable: alarm or no alarm.

IRIG-In BNC AFNOR-A/C, IRIG-B12x synchronization input

IRIG 12x BNC: IRIG-B12x output AFNOR-A/C, IRIG-B12x and DCF-FSK output for IRIG-
Channel 1 Line 1
IRIG 12x BNC: IRIG-B12x output AFNOR-A/C, IRIG-B12x and DCF-FSK output for IRIG-
Channel 2 Line 2

DTS DTS-Extension DTS-Extension-Bus

Extension

© MOBATIME 81 / 104 800729.11

 Clamp Connection Description
9 RS232 Tx RS232 interface of line 1 (Exclusive to the RS485
10 RS232 Rx interface line 1; internally the same interface)
11 GND
12 RS485 A RS485 interface of line 1 (Exclusive to the RS232
13 RS485 B interface line 1; internally the same interface)

14 RS422 + Pulse 1 RS422 output line 1 for DCF, pulse and frequency output
15 RS422 – Pulse 1 (internally the same source of signal like for the current loop
output)
16 CL + Pulse 1 Current loop line 1 for DCF, pulse and frequency output
17 CL – Pulse 1 ("Current loop” passive,
optocoupler: Umax= 50VDC, Imax = 10mA)
18 RS232 Tx RS232 interface of line 2 (Exclusive to the RS485
19 RS232 Rx interface line 2; internally the same interface)
20 GND
21 RS485 A RS485 interface of line 2 (Exclusive to the RS232
22 RS485 B interface line 2; internally the same interface)

23 RS422 + Pulse 2 RS422 output line 2 for DCF, pulse and frequency output
24 RS422 – Pulse 2 (internally the same source of signal like for the current loop
output)
25 CL + Pulse 2 Current loop line 1 for DCF, pulse and frequency output
26 CL – Pulse 2 ("Current loop” passive,
optocoupler: Umax= 50VDC, Imax = 10mA)

27 RS422 + Digital IRIG-B signal (00x) of the IRIG line 1

28 RS422 – See Appendix A.5
29 Current Loop + Digital IRIG-B signal (00x) of the IRIG line 1 as current-loop
30 Current Loop – (“Current loop” passive,
optocoupler: Umax= 50VDC, Imax = 10mA)
31 RS422 + Digital IRIG-B signal (00x) of the IRIG line 2
32 RS422 – See Appendix A.5
33 Current Loop + Digital IRIG-B signal (00x) of the IRIG line 2 as current-loop
34 Current Loop – (“current loop” passive,
optocoupler: Umax= 50VDC, Imax = 10mA)
35 DCF input + DCF input e.g. for the connection of a GPS 4500- or DCF-
36 DCF input - receiver with "current loop“ output.
37 DCF output + DCF output, “current loop” passive,
38 DCF output - Umax= 30VDC, Ion = 10..15mA, Ioff < 1mA @20VDC
39 DC output + (VB+) DC output for GPS 4500
40 DC output GND 28 VDC, max. 400 mA (or according to the DC in voltage)

DTS-Link Optical connection to a 2 nd DTS 4135.timeserver

Mini GBIC plug-in
EFR Option, for special applications only

© MOBATIME 82 / 104 800729.11

 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 4500 or DCF 4500

white
DCF receiver brown
GPS 4500 yellow
green

A.5 IRIG-B00x Digital Output TTL connection

IRIG digital output

TTL (00x)
IRIG digital output
TTL inverse (00x)

© MOBATIME 83 / 104 800729.11

B Time zone table
Time zone entries in the standard season table (version 10.1).
Time City / State UTC DST Standard → DST DST → Standard
zone Offset Change
00 UTC (GMT), 0 No
Monrovia, Casablanca
01 London, Dublin, 0 Yes Last Sun. Mar. (01:00) Last Sun. Oct. (02:00)
Edinburgh, Lisbon
02 Brussels, Amsterdam, +1 Yes Last Sun. Mar. (02:00) Last Sun. Oct. (03:00)
Berlin, Bern, Copenhagen,
Madrid, Oslo, Paris,
Rome, Stockholm,
Vienna, Belgrade,
Bratislava, Budapest,
Ljubljana, Prague,
Sarajevo, Warsaw,
Zagreb
03 Athens, Istanbul, Helsinki, +2 Yes Last Sun. Mar. (03:00) Last Sun. Oct. (04:00)
Riga, Tallinn, Sofia,
Vilnius
04 Bucharest, Romania +2 Yes Last Sun. Mar. (03:00) Last Sun. Oct. (04:00)
05 Pretoria, Harare, +2 No
Kaliningrad
06 Amman +2 Yes Last Thu. Mar. (23:59) Last Fri. Oct. (01:00)
07 UTC (GMT) 0 No
08 Kuwait City, Minsk, +3 No
Moscow, St. Petersburg,
Volgograd
09 Praia, Cape Verde -1 No
10 UTC (GMT) 0 No
11 Abu Dhabi, Muscat, +4 No
Tbilisi, Samara
12 Kabul +4.5 No
13 Adamstown (Pitcairn Is.) -8 No
14 Tashkent, Islamabad, +5 No
Karachi, Yekaterinburg
15 Mumbai, Calcutta, +5.5 No
Madras,
New Delhi, Colombo
16 Astana, Thimphu, Dhaka, +6 No
Novosibirsk
17 Bangkok, Hanoi, Jakarta, +7 No
Krasnoyarsk
18 Beijing, Chongqing, Hong +8 No
kong, Singapore, Taipei,
Urumqi, Irkutsk
19 Tokyo, Osaka, Sapporo, +9 No
Seoul, Yakutsk
20 Gambier Island -9 No
21 South Australia: Adelaide +9.5 Yes 1st Sun. Oct (02:00) 1st Sun. Apr. (03:00)
22 Northern Territory: Darwin +9.5 No
23 Brisbane, Guam, +10 No
Port Moresby, Magadan,
Vladivostok
24 Sydney, Canberra, +10 Yes 1st Sun. Oct. (02.00) 1st Sun. Apr. (03:00)
Melbourne, Tasmania:
Hobart
25 UTC (GMT) 0 No
26 UTC (GMT) 0 No

© MOBATIME 84 / 104 800729.11

 27 Honiara (Solomon Is.), +11 No
Noumea (New Caledonia),
28 Auckland, Wellington +12 Yes Last Sun. Sep. (02:00) 1st Sun. Apr. (03:00)
29 Majuro (Marshall Is.), , +12 No
Anadyr
30 Azores -1 Yes Last Sun. Mar. (00:00) Last Sun. Oct. (01:00)
31 Middle Atlantic -2 No
32 Brasilia -3 Yes 3rd Sun. Oct. (00:00) 3rd Sun. Feb. (00:00)
33 Buenos Aires, Santiago -3 No
34 Newfoundland, Labrador -3.5 Yes 2nd Sun. Mar. (02:00) 1st Sun. Nov. (02:00)
35 Atlantic Time (Canada) -4 Yes 2nd Sun. Mar. (02:00) 1st Sun. Nov. (02:00)
36 La Paz -4 No
37 Bogota, Lima, Quito, -5 No
Easter Island, Chile
38 New York, Eastern Time -5 Yes 2nd Sun. Mar. (02:00) 1st Sun. Nov. (02:00)
(US & Canada)
39 Chicago, Central Time -6 Yes 2nd Sun. Mar. (02:00) 1st Sun. Nov. (02:00)
(US & Canada)
40 Tegucigalpa, Honduras -6 No
41 Phoenix, Arizona -7 No
42 Denver, Mountain Time -7 Yes 2nd Sun. Mar. (02:00) 1st Sun. Nov. (02:00)
43 Los Angeles, Pacific Time -8 Yes 2nd Sun. Mar. (02:00) 1st Sun. Nov. (02:00)
44 Anchorage, Alaska (US) -9 Yes 2nd Sun. Mar. (02:00) 1st Sun. Nov. (02:00)
45 Honolulu, Hawaii (US) -10 No
46 Midway Islands (US) -11 No
47 Mexico City, Mexico -6 Yes 1st Sun. Apr. (02:00) Last Sun. Oct. (02:00)
48 Adak (Aleutian Is.) -10 Yes 2nd Sun. Mar. (02:00) 1st Sun. Nov. (02:00)
49 UTC (GMT) 0 No
50 UTC (GMT) 0 No
51 UTC (GMT) 0 No
52 UTC (GMT) 0 No
53 UTC (GMT) 0 No
54 Scoresbysund, Greenland -1 Yes Last Sun. Mar. (00:00) Last Sun. Oct. (01:00)
55 Nuuk, -3 Yes Last Sat. Mar. (22:00) Last Sat. Oct. (23:00)
Qaanaaq,Greenland
56 Qaanaaq, Greenland (old) -4 Yes 2nd Sun. Mar. (02:00) 1st Sun. Nov. (02:00)
57 Western Australia: Perth +8 No
58 Caracas -4.5 No
59 CET standard time +1 No
60 Santiago, Chile (old) -4 Yes 2nd Sun. Oct. (00:00) 2nd Sun. Mar. (00:00)
61 Chile, Easter Island (old) -6 Yes 2nd Sat. Oct. (22:00) 2nd Sat. Mar. (22:00)
62 Baku +4 Yes Last Sun. Mar. (04:00) Last Sun. Oct. (05:00)
63 UTC (GMT) 0 No
64 UTC (GMT) 0 No
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: Universal Time Coordinate, equivalent to GMT
DST: Daylight Saving Time
DST Change: Daylight Saving Time changeover
Standard  DST: Time change from Standard time (Winter time) to Summer time
DST  Standard: Time change from Summer time to Standard time (Winter time)
Example:
2nd last Sun. Mar. (02:00) Switch over on the penultimate Sunday in March at 02.00 hours local time.
Notice: 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.

© MOBATIME 85 / 104 800729.11

Modifications / updating the time zone table:
The time zone tables are filed in the /etc/mbsn.tbl (standard table) and /etc/usersn.tbl (user table)
files.
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 4135
in accordance with the update instructions (chapter “7.3 Updating Applications and Configurations“).

Notice: The file names mbsn.tbl und usersn.tbl must be written in small letters.

© MOBATIME 86 / 104 800729.11

C Alarm list

Number Error message Description / Action

0 Reboot DTS DTS 413x 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
9 Wrong time zone TC1 Error in time zone calculation TC1
10 Wrong time zone TC2 Error in time zone calculation TC2
11 Alarm input Error from external device
12 Low voltage IRIG1 Low voltage on analogue AFNOR/IRIG-B output 1
13 Low voltage IRIG2 Low voltage on analogue AFNOR/IRIG-B output 2
14 Error bit14 Not used
15 Error bit15 Not used
16 Time source lost Stratum too high: check time source
No time information from the selected time source within the
17 Failure time source TO
configured timeout: Check time source. In slave mode: check link.
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
24 Mail config. wrong Check e-mail configuration
25 SNMP not working Check SNMP and trap configuration
26 Error bit26 Not used
27 Error bit27 Not used
28 Error bit28 Not used
29 Error bit29 Not used
No connection via DTS link (optical link) in redundant operation.
30 No opt. link
Check connection.
No connection via LAN link in redundant operation. Check LAN
31 No link (LAN)
connection.
Switch over slave -> master has occurred. Optionally, check the
32 Switch over slave -> master
time source of current slave.
In slave mode only: check time sources
33 Offset source (slave)
Difference between slave and local time source too large
34 Local time source lost In slave mode only: check time sources
35 Error bit35 Not used

© MOBATIME 87 / 104 800729.11

 36 Error bit36 Not used
37 Error bit37 Not used
Check telegram file: the file name is longer than 8 digits or the file
38 Wrong telegram format
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 88 / 104 800729.11

D Troubleshooting
Error   Solution / possible cause

1 DTS does not accept Does the reading change (approx. No, but 20 min. After new installation or powers supply failure, it
time every 3 sec) Sec counter DCF in have not yet may take up to 20 min. until the GPS receiver
Status Source TIME SOURCE passed since the (e.g. GPS 4500) sends out valid telegrams.
INFORMATION? last reboot. Wait for this time to pass.
2 No, for more than  Check DCF reception LED
20 minutes.  Check polarity cabling to GPS.
 Check positioning of the GPS receiver
3 Error-Bit 23 (Syn only diff too big) in The deviation to the received time is beyond the
Status Alarm status set 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  If Error-Bit 23 set, see point 3
TIME INFORMATION AND STATUS  The deviation is that big, that offset changes
always shows the same cannot be seen due to the displayed
offset 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 See 1
source fail stratum)
7 Error-Bit 17 set (time See 1
source fail TO)
8 Error-Bit 23 set (Syn See 1
only diff too big)
9 DTS 413x.timeserver Check, if the network settings are correct,
is restarting especially the hostname and the gateway has
continuously. to be configured (when no gateway is available,
the own IP address can be used).
10 LAN LED (left one) is No connection to the network. Check network cabling.
flashing orange.
11 Opening the menu via Check network settings in menu 2
Telnet is not possible Configuration –> 5 Network (only possible with
or DTS 413x. serial connection):
timeserver is not or no - IP-Address, Subnet mask and Gateway must
longer reachable via be set correctly
network. - 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.
12 Drift (ppm) of quartz The drift displayed in the menu Status  The quartz drift is measured and corrected
too high Time TIME INFORMATION AND continuously. After initial operation, it may
STATUS is bigger than stated in the take up to 24 hours until optimal accuracy is
data sheet. reached (with GPS reception).
 Very large temperature change (outside the
specification)
 Time correction was carried out manually.

© MOBATIME 89 / 104 800729.11

13 System software The system software can be updated using
update 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.
14 Needed information to Device type, part number, production
contact your number and serial number:
MOBATIME service This 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-Adresse], see chapter 0 .
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 90 / 104 800729.11

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 91 / 104 800729.11

 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 92 / 104 800729.11

 ;MTG (Day of the month) (1..31) 1B
;JTG (Day of the year) (1..366) 1W
;WTG (Day of the week) (0..6) 1W Text table !WT!
; (Su..Sa)
;DOW (Day of the week) (0..7) 1B !DW!
;KAW (Calendar week) (1..53) 1B (according to Din ISO 8601)
;MON (Month) (1..12) 1W Text table !MO!
;MNT (Month) (1..12) 1B
;
;AMF (am/pm flag) (0/1) 1W Text table !AM!
;TMQ (synchronization qual.) (0..255
; or A..Z) 1B (see !TQ!)
;SAI (Season) (0..2) 1W Text table !SA!
; (Win/Sum/UTC)
;AKS (Season change (0/1) 1W Text table !AK!
; announcement)
;AMF (am/pm-Flag) (0/1) 1W Text table !AM!
;SST (Season status) (0..3) 1W Text table !ST!
; (Bit 0 = Early warning bit)
; (Bit 1 = Summer bit)
;SYA (Synch. alarm) (0/1) 1W Texttabelle !SY!
; (0:synch ok, 1: synch alarm -> Alarm Nr.16, 17 or 19)
;CHS (Check sum) (0..255) 1B
;XCH (XOR Check sum) (0..255) 1B
;X1C (XOR Check sum low nibble in ASCII) (0..9, A..F) 1B
;X2C (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 93 / 104 800729.11

 ;-- 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..995). 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 94 / 104 800729.11

 ;=====================================================================
;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 95 / 104 800729.11

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 1.1.4 GPL version 2 COPYING
Linux Operating system 2.6.18 GPL version 2 COPYING
Busybox System 1.13.2 GPL version 2 LICENSE
environment
NTP NTP 4.2.8p2 Free COPYRIGHT
pure-ftp FTP server 1.0.21 Free, partly BSD COPYING
NetSNMP SNMP agent 5.4.2.1 BSD COPYING
OpenSSL SSL Lib. 0.9.8i BSD style LICENSE
OpenSSH SFTP server 5.2.p1 BSD LICENCE
dropbear SSH server 0.52 MIT style: LICENSE
Free, party BSD
wide-dhcpv6 DHCPv6 client 20080615 Free COPYRIGHT
flex Flex Lib. 2.5.4e BSD adapted COPYING
zlib Compress lib. 1.2.3 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 (support@mobatime.com). Handling costs will be charged!

© MOBATIME 96 / 104 800729.11

G 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 Serial interface (via RS 232) or Telnet / SSH / MOBA-NMS (via LAN)
In addition, operation is also possible with SNMP.
Accuracy GPS (DCF input) to NTP server: typical < +/- 100 µs
GPS (DCF input) to DCF output: typical < +/- 10 µs
IRIG input to DCF output: typical < +/- 50 µs
NTP to internal time typical < +/- 100 µs
Notice: NTP reception (DTS 413x as client or as server to external clients) can be
influenced by the network traffic load and network devices (Hub, Switch,
Router, Firewall...). If many clients request simultaneously, the typical
accuracy may not be reached.
Time keeping (internal) Synchronized with GPS: +/-10 µs to UTC
Holdover (free run): After at least 12 hours synchronization from the time source:
DTS 4135 -> TCXO: at 20°C +/- 5°C: < +/- 10 ms / day (< 0.1ppm) *
at constant temperature*: < +/- 1 ms / day (< 0.01ppm) *
DTS 4136 -> OCXO: at 20°C +/- 5°C: < +/- 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): typical < +/- 1 µs
Time server NTP V4 (fully V3 compatible), 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)
Max. number of NTP and SNTP client requests: > 1250 requests / sec.
NTP Mode Server, Peer, Broadcast, Multicast
NTP slave clock lines: 1 line with up to 15 different time zone entries.
Communication through multicast:
-RFC 3376: Internet Group Management Protocol, Version 3
-RFC 1112: Host extensions for IP multicasting
-RFC 4601: Protocol Independent Multicast - Sparse Mode (PIM-SM)
-RFC 3973: Protocol Independent Multicast - Dense Mode (PIM-DM)
Time zones (see App. B) Up to 80 predefined, 20 programmable entries (MOBA-NMS)
Network interface 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 UDP, Port 123 see timeserver
SNTP UDP, Port 123 see timeserver

© MOBATIME 97 / 104 800729.11

 TIME TCP/UDP, Port 37 see timeserver
DAYTIME TCP/UDP, Port 13 see timeserver
Telnet TCP, Port 23 operation
SSH TCP, Port 22 operation
SCP über SSH update
SFTP über SSH update
FTP TCP, Port 21 update
SNMP UDP, Port 161 operation
UDP, Port selectable (162) alarm notification, see SNMP
SMTP TCP, Port selectable (25) alarm mail see E-Mail
DHCP UDP, Port 68 dyn. address allocation (client)
DNS TCP/UDP, Port 53 address resolution (client)
DHCPv6 only IPV6
ECHO 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
Serial interface D-Sub 9 (male): (RS232, 38400, 8, n, 1, no flow control)
(front side) Cable length max. 3 m.
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)
2 x IRIG-B output (analog and digital)
2 x DCF, programmable impulse / frequency output over RS 422 and
opto coupler (current loop passive)
1 x DCF current loop interface passive
2 x Script files configurable time telegrams on RS 232, RS 422 (only send)
and RS 485
DCF output (1x) DCF timecode, time zone selectable
Max. time deviation with GPS source: +/- 10 µs, jitter < 10 µs
DCF time code passive current loop interface:
Vmax = 30 VDC, Ion = 10..15 am, Ioff < 0.1 mA @20VDC
DCF / impulse / 2 line for technical impulses:
frequency outputs (2x) time zone selectable, output signal correction possible (DCF and impulse)
Max. time deviation with GPS source: +/- 10 µs, Jitter < 10 µs
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

IRIG-B outputs (2x) 2 high precision IRIG lines, both available as analog and digital signals
Max. time deviation to GPS (with GPS source):

© MOBATIME 98 / 104 800729.11

 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: ≤ 1 µs
Jitter modulated at carrier frequency: ≤ 1%
DC level jitter pulse-to-pulse: ≤ 200 ns
Line mode: IRIG-B122, IRIG-B Std 12h (B122), IRIG-B002, IRIG-B003,
IRIG-B123, IRIG-B DIEM, AFNOR A, AFNOR C, DCF-FSK
IRIG-B126, IRIG-B IEEE 1344
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 (2x) 2 lines for telegram output
(back side) RS232 or RS485
Max. time deviation against 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 functions is provided in Appendix E.
USB plug USB Host for USB stick
Alarm contact Opening relay contact (Alarm active  contact open).
Breaking capacity: max. 30 W (DC) or 60 VA (AC)
max. 60 VDC or 1 A / 30 VAC or 1 A
Alarm reporting / Alarm contact see Alarm contact
Error reporting E-Mail see E-Mail
SNMP-Notification see SNMP-Trap
Display see display
Alarm LED -
Alarm inputs 18 – 36 VDC, max. 6 mA, for external closing contact
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% / 20 W
Mains power supply 90 – 240 V / 50 - 60 Hz / 0.25 A
Power supply output Nominal 24 VDC, max. 400 mA (respectively according to power supply)

© MOBATIME 99 / 104 800729.11

H Index
Firmware 14
A Front connections 80
Accuracy 97 FTP 64, 98
Alarm 48
G
Alarm configuration 42
Alarm input – techn. data 99 GBIC 81, 82, 99
Alarm list 87 GBIC Module 71
Alarm mask 43
Alarm relay 42, 99 H
Alarm status 14 HyperTerminal 17
Alarmeingang 48
Authentication 45, 70 I
Autoconf – Ipv6 52
Interface 91
Autokey 71
IPv4 configuration 51
B IPv6 – FTP connection 64
IPv6 configuration 52
Baudrate: 29
Broadcast NTP 39 K
C Key 70

Community (SNMP) 73 L
Configuration – save 65
Language setting 49
Connection table (to fill in) 102
Leap second 70
Connections – alarm relay 81
Leap second mode 41
Connections – DCF & GPS 83
LED description back side 13
Connections – front view 80
LED description front side 13
Connections – IRIG-B12x input 81
Lines 27
Connections – IRIG-B12x outputs 81
Linux 18
Connections – PC 80
Login (menu) 17
Connections – power supply 81
Connections – rear view 81 M
Connectors 83
Control Key 40 Mains supply 79, 81, 99
Copyright 96 Manual time set 41, 68
CRAM-MD5 45 MD5 70
Menu login 17
D Menu structure 19
MIB-Files 73
Data bit 29
mini GBIC 71, 81, 82, 99
Daylight Saving Time 85
MOBA-NMS 11
DAYTIME 98
Multicast 32, 97
DC power supply 79, 81, 99
Multicast address 37
DCF – connection 83
Multicast NTP 39
DCF Eingang 81
DCF input 82 N
DCF output 27, 82
DCF output – techn. data 98 Network configuration 50
DES – Data Encryption Standard 70 Network services 97, 98
DHCP 51 NTP 98
DHCPv6 52 NTP as backup time source 37, 69
Display 14 NTP authentication 40, 70
DST 85 NTP Autokey 71
DTS Link 36, 71, 81, 82, 99 NTP broadcast 39
NTP mode 97
E NTP multicast 39
NTP server 37
E-Mail 44
NTP slave clocks 32, 97
E-Mail – techn. data 98
NTP symmetric keys 70
F NTP time source 25, 38
NTP version 69
Factory settings 60

© MOBATIME 100 / 104 800729.11

ntp.keys 40 Software update 61, 62
ntpq 23 Software version 14
Spring terminals 83
O SSH 18, 98
Operation (menu) 17 Status menu 22
Operation (SNMP) 74 Stop bit 29
Stratum 68
P
T
Parity 29
Password 17 Telegram – definition 92
Password configuration 49 Telegram file 29, 60, 66, 91
Power setting 49 Telnet 18, 98
Power supply 79 Terminal 17
Problem solving 89 TIME 98
Program file 60, 66 Time acceptance 68
Time administration 33, 67, 68
R Time server 69, 97
Time source – time accepance 68
Redundant NTP Multicast time server 33
Time source configuration 34
Redundant operation 36, 71
Time zone 84
Request Key 40
Time zone for displayed time 49
RTC (Real Time Clock) 67
Time zone selection 59
RTC mode 35
Time zone server 32
S Time zone table 84
Time-keeping 35, 68
SCP 65, 98 Transmission time 91
Script file definition 92 Trap 46, 74
Season table 84 Troubleshooting 89
Serial connection 18 Trusted Key 40
Serial interface – techn. data 98 ttl (time to live) 39
Serial telegrams 29, 91
SFTP 11, 64, 98 U
SMTP 98
Update – software 61, 62
SNMP 11, 73, 98
Update time zone table 86
SNMP – alarm notification 78
USB 60, 62, 63, 66
SNMP – alive notification 78
UTC 67, 85
SNMP – notification 74
SNMP – operation 74 V
SNMP – variables 76
SNMP access configuration 58 Version 14
SNMP configuration 46, 54
W
SNMP traps 46, 74
SNMP user configuration 57 World time 32
SNTP 98

© MOBATIME 101 / 104 800729.11

I Connection table (to fill in)

Line Type Description

Example:

Line Type Description

DCF DCF out DCF for master clock ETC1

© MOBATIME 102 / 104 800729.11

© MOBATIME 103 / 104 800729.11
© MOBATIME BE-800729.11