Mobatime DTS 4801.masterclock Instruction manual

MOUNTING AND

INSTRUCTION MANUAL

Net Master Clock

DTS 4801.masterclock


Network Timeserver and Master Clock

© MOBATIME BE-800652.11

Certification of the Producer

STANDARDS

The DTS 4801.masterclock and the DTS 4802.masterclock were developed and produced in accordance with the EU Guidelines:

2006 / 95 / EG

2004 / 108 / EG

96 / 48 / EG

CB Test Certification (IEC 60950-1) :

DTS 4801 / DTS 4802

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 at 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, however, have any questions or discover any errors in this Manual, please contact us.

4. We are not liable for any direct or indirect damages which could occur when using this Manual.

5. Please read the instructions carefully and only use the product, after you have correctly understood all the information for installation and operation.

6. It is prohibited to reproduce, store in a computer system, or transfer this publication, or any part of it in any way. 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 / 120 800652.11

Overview

1 Safety ................................................................................................................................................ 6

2 Maintenance ...................................................................................................................................... 8

3 General Information: Introduction ...................................................................................................... 9

4 Displays ........................................................................................................................................... 13

5 Installation ....................................................................................................................................... 15

6 Operation ......................................................................................................................................... 17

7 Updates ........................................................................................................................................... 71

8 Time administration ......................................................................................................................... 77

9 SNMP .............................................................................................................................................. 83

10 Description of the switch function .................................................................................................... 90

APPENDIX

A Connection diagrams ...................................................................................................................... 92

B Time Zone Table ............................................................................................................................. 96

C Alarm List ........................................................................................................................................ 99

D Troubleshooting ............................................................................................................................. 101

E Serial Telegrams ........................................................................................................................... 102

F Option IRIG-B: IF 488 Configuration ............................................................................................. 108

G Copyright Notice ............................................................................................................................ 109

H Block diagram ................................................................................................................................ 110

I Technical data ............................................................................................................................... 111

J Index .............................................................................................................................................. 114

K Connection Table (to be filled-in) .................................................................................................. 116

© MOBATIME 3 / 120 800652.11

Table of contents

1 Safety ............................................................. 6

1.1

Safety instructions ....................................... 6

1.2

Symbols and Signal Words used in this

1.3

1.4

1.5

1.6

Instruction Manual ....................................... 6

Intended Use ............................................... 6

Observe operating safety! ........................... 7

Consider the installation site! ...................... 7

Please observe the electromagnetic compatibility! ................................................ 7

2 Maintenance ................................................... 8

2.1

Troubleshooting: Repairs ............................ 8

2.2

2.3

Cleaning ...................................................... 8

Disposing ..................................................... 8

3 General Information: Introduction ................... 9

3.1

3.2

3.3

3.4

3.5

3.6

Scope of Delivery ........................................ 9

Technical Data ............................................ 9

Device Description in this Manual ............... 9

Device Description ...................................... 9

Device types .............................................. 10

DTS Distributed Time System ................... 11

3.7

MOBA-NMS - Network Management

System ...................................................... 11

3.7.1

Overview of the main functions ............................. 12

3.7.2

Device management ............................................. 12

4 Displays ........................................................ 13

4.1

4.2

4.3

LED displays front view ............................. 13

LED displays rear view .............................. 13

Display ....................................................... 14

5 Installation .................................................... 15

5.1

Installation Guidelines ............................... 15

5.2

5.3

Connections .............................................. 15

Boot procedure of the DTS

480x.masterclock ...................................... 15

5.4

Firmware ................................................... 15

5.5

Basic settings (factory settings) ................ 16

6 Operation ...................................................... 17

6.1

General ...................................................... 17

6.1.1

Serial connection ................................................... 18

6.2

6.3

6.1.2

Telnet .................................................................... 18

6.1.3

6.1.4

SSH ....................................................................... 18

Menu structure ...................................................... 19

MOBA-NMS operation .............................. 20

Main menu ................................................. 21

6.4

Status menu .............................................. 22

6.4.1

Time information and status .................................. 24

6.4.2

Time source information ........................................ 25

6.5

Configuration menu ................................... 26

6.5.1

Lines ...................................................................... 27

6.5.2

6.5.3

MOBALine ............................................................. 28

IRIG-B, AFNOR (Option) ....................................... 29

6.5.4

Impulse line ........................................................... 30

6.5.5

DCF active code line ............................................. 31

6.5.6

DCF / Pulse output ................................................ 33

6.5.7

6.5.8

Serial telegrams .................................................... 34

RS 485 Clock line .................................................. 36

6.5.9

NTP slave clocks / Time zone server .................... 39

6.5.10

Switch function / Switch program .......................... 41

6.5.11

Time handling ........................................................ 45

6.5.12

6.5.13

General time configuration .................................... 46

Time source ........................................................... 47

6.5.14

6.5.15

6.5.16

6.5.17

6.5.18

6.5.19

6.5.20

NTP server ............................................................ 48

Communication Alarm Network (CAN) to MTC ..... 52

Manual time set ..................................................... 53

Alarms ................................................................... 54

Alarm relays .......................................................... 54

Alarm mask ........................................................... 55

E-mail .................................................................... 56

SNMP-Traps .......................................................... 58

6.5.21

6.5.22

6.5.23

6.5.24

6.5.25

6.5.26

6.5.27

6.6

6.5.28

General settings .................................................... 60

Network ................................................................. 61

Services (network services FTP, telnet, SSH....) .. 64

SNMP .................................................................... 65

SNMP V1 / V2c ..................................................... 66

SNMP V3 ............................................................... 67

Time zone selection .............................................. 69

Maintenance menu .................................... 70

7 Updates ........................................................ 71

7.1

7.2

7.3

7.4

7.5

Updating images with MOBA-NMS ............ 71

Updating images via FTP .......................... 71

Updating applications or configurations via FTP ....................................................... 72

Updating images via USB .......................... 72

7.6

Updating applications or configurations

FTP connection .......................................... 74

7.7

7.8

7.9

7.10

via USB ...................................................... 73

SFTP Connection....................................... 74

SCP Connection ........................................ 75

Save configuration externally ..................... 75

Copying Telegram or Program files to the

DTS 480x.masterclock ............................... 76

8 Time administration ...................................... 77

8.1

8.2

8.3

8.4

8.5

8.6

8.7

Concept of time administration .................. 77

Time take-over, NTP .................................. 78

Fix stratum for local time source ................ 79

Time server ................................................ 80

Time accuracy, time-keeping ..................... 80

Leap second .............................................. 80

NTP Authentication .................................... 80

8.7.1

8.7.2

NTP symmetric keys ............................................. 80

NTP Autokey ......................................................... 82

9 SNMP ........................................................... 83

9.1

9.2

9.3

General ...................................................... 83

Device configuration with SNMP ............... 84

9.3.1

9.3.2

9.3.3

DTS Subagent SNMP Notification ............. 84

Startup [dts480xStartUp] ....................................... 84

Shutdown [dts480xShutdown] ............................... 84

Status changed [dts480xStatusChanged] ............. 85

9.3.4

Configuration changed

[dts480xConfigChanged] ....................................... 85

9.3.5

Alive Notification [dts480xAlive] ............................ 89

9.3.6

Alarm Notification [dts480xAlarm] ......................... 89

10 Description of the switch function ................ 90

10.1

General Description ................................... 90

10.2

10.3

Combination of the signals ........................ 91

Behavior at start-up, exchange of switch program file ................................................ 91

© MOBATIME 4 / 120 800652.11

APPENDIX

A Connection diagrams ................................... 92

A.1

A.2

A.3

A.4

A.5

Front connections ...................................... 92

Connections (rear view) DTS

4801.masterclock ...................................... 93

Connections (rear view) DTS

4802.masterclock ...................................... 94

Plug-in spring terminals ............................. 95

Connection of GPS 4500, DCF 450 /

4500 or GNSS 3000 .................................. 95

B Time Zone Table .......................................... 96

C Alarm List ..................................................... 99

C.1

Alarms ....................................................... 99

D Troubleshooting .......................................... 101

E Serial Telegrams ........................................ 102

E.1

E.2

General .................................................... 102

Syntax of the telegram configuration file . 104

F Option IRIG-B: IF 488 Configuration .......... 108

G Copyright Notice ......................................... 109

H Block diagram ............................................. 110

I Technical data ............................................ 111

J Index ........................................................... 114

K Connection Table (to be filled-in) ............... 116

© MOBATIME 5 / 120 800652.11

1 Safety

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.

The DTS 480x.masterclock is a master clock 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 MOBALine clock line (with switching function e.g. for clock illumination, switching program and for world time function) or it can drive a line of impulse clocks or DCF active code clocks. The DTS 4802 has 2 such lines.

For additional functions, see the device descriptions in Chapter 3.4.

The device is designed for 19" racks and intended to be installed in a 19" cabinet.

Operate the device only in installed condition.


!

Caution!

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!

 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.

!

Caution!

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.

 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.

!

Caution!

1.6 Please observe the electromagnetic compatibility!

 This device complies with the requirements of the EMC and the Low-voltage

Directive.

 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 / 120 800652.11

2 Maintenance

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 / 120 800652.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 masterclock

 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




 2 pcs mounting tools with spring terminals

.

See Appendix "I Technical data".

3.3 Device Description in this Manual

This instruction manual is for the master clocks DTS 4801.masterclock and DTS

4802.masterclock

. Below both models will be referred to as the DTS

480x.masterclock

and only as 4801 or 4802 with regard to the special features of the individual models.

© MOBATIME

The DTS 480x.masterclock is a master clock for use in network environments. It can be synchronized both from NTP and also function as an NTP server. In addition, it can import the time from DCF or from GPS (e.g. from GPS 4500).

As a master clock, it can supply a self-adjusting MOBALine clock line (with switch function for clock illumination, switch program and world time function) or alternatively to the MOBALine clock line, a line can also be operated with impulse clocks or DCF active code clocks. The DTS 4802 is equipped with two such lines.

Alternatively it can generate serial telegrams and output them via RS 485 (only DTS

4801) or RS 232. Optional the DTS 4801 is able to drive a monitored RS485 clock line

(with switch function for clock illumination) with up to 31 devices.

The DTS 480x can supply NTP clocks with NTP and time zone tables using multicast.

As the "Main“ master clock, it can synchronize other master clocks or other equipment with DCF and monitor with 4 alarm inputs. As an option to DCF, synchronization pulses can also be generated.

9 / 120 800652.11

The DTS 480x can send both e-mails and SNMP traps for alerting purposes.

Using SNMP, configuration and system status can be requested and the DTS 480x operated.

The DTS 480x can be connected as a master clock to a MTC CAN module which can monitor and synchronize up to 16 master clocks.

As part of the DTS system, it functions as a master clock or clock line.

Model:


DTS 4801.masterclock IRIG-B


Characteristics:

According to the description above

1 clock line

MOBALine/Impulse/DCF active code

1

RS 485 clock line

Like DTS 4801, additional with IRIG-B /

AFNOR / DCF-FSK – line

(built in IF 488 interface)

According to the description above

2 clock lines

MOBALine/Impulse/DCF active code

no

RS 485 clock line

Product no.:

203397

203495

203782

© MOBATIME 10 / 120 800652.11

3.6 DTS Distributed Time System

The DTS (Distributed Time System) is a system developed by the company Moser-

Baer AG to link decentralized main clocks, slave clock lines, and time servers. The

LAN (Ethernet) is used as connection. 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.

True 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 / 120 800652.11

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.

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 / 120 800652.11

4 Displays

4.1 LED displays front view

Description Color Status

Off

Off

Flashing

Off

LAN control lamps:

Left Green

Orange

Blinking

Blinking

On

Description

Mains or DC power supply is in order

No power supply

The alarm relay signalizes an alarm

No active alarms

DTS 480x masterclock can read the time from a synchronization source

Time source internally (RTC) or manual time setting

(flashing till "NTP synch. Lost" alarm appears or an external time source is available after restart)

Synchronization source is not available.

Off when alarm "Failure time source Str" occurs.

See chapter 6.5.12, menu 1: "Stratum limit for synchalarm".

For DCF time source the delay for this alarm is defined in chapter 6.5.13, menu 7: "Stratum TO (0-16)

DCF/GPS fail".

Network activity

No connection to network

10 Mbit

100 Mbit

4.2 LED displays rear view

Description Color Description

DCF in red Blinking DCF (GPS reception)

© MOBATIME 13 / 120 800652.11

4.3 Display

Display showing the current status of the DTS 480x.

Display of: -Time, date

-Current time source

-Stratum of the DTS 480x.masterclock

-Line time of MOBALine / Impulse lines

-Software-Version

The display can be operated by means of the corresponding “Display“ button:

First press the button briefly:

Other buttons to press briefly:

Press button longer (>3 sec):

Switch on the background light

Scroll through all displays

Change to default display (time and date)

The display changes after approx. 3 min without pressing the button for the default display and the background light goes off.

If a USB stick has been plugged in, it will be displayed. Should only telegram and/or program files be copied, this can be activated directly with the button. (Press the button until the copy process starts).

© MOBATIME 14 / 120 800652.11

5 Installation

Danger! Always consider:

For mains power supply, a plug is located on the rear side of the DTS 4801 / DTS

4802. This power plug separates the device from the power.

The DTS 480x 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 480x.masterclock

The normal booting time of the DTS 480x 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 / 120 800652.11

5.5 Basic settings (factory settings)

General Internal time zone

Menu password

MEZ dts

Language English

Time source Source DCF-GPS (UTC)

Stratum auto

Error stratum

DCF timeout

5 off

DCF correction

Offset per Stratum

Synch only offset

0ms

50ms off

Lines DCF output

Lines 1 and 2

NTP slave clocks /

Time zone server

RS485 / telegram switching function off, UTC on, MOBALine, MEZ off off off

Network DHCP on

DHCPv6 off

Autoconf IPv6 off

Link auto

Hostname DTS4801

Alarm Relay all on, except 4 alarm inputs

Mail off

SNMP traps off

NW Services SSH on

Telnet on

FTP on

SNMP Modus

RO community

RW community

SNMP Traps Mode

Trap community off romobatime rwmobatime off trapmobatime

© MOBATIME 16 / 120 800652.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:

© MOBATIME

To start the menu, dts must be logged in as user. The standard password is dts.

(Changing the password  see Chapter “4.4.20 General Settings“).

Only one menu can be open at any time. The first menu started has priority. The menu is automatically closed after 15 min. without operation, and any possible connection via

Telnet or SSH 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.

Localecho:

Some terminals (serial or Telnet) do not display the characters entered. It is, therefore, necessary to switch on the "local echo" in the terminal.

17 / 120 800652.11

!

38400 Bauds, 8 data bits, no parity, 1 stop bit.

Windows 2000, XP, Vista: HyperTerminal

Windows 7: Putty (Download from Internet)

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.

Attention:

The serial connection should always be disconnected before switching off the operating PC (exit terminal program or pull out the RS232).

6.1.2 Telnet

Windows 98, 2000, XP, Vista, Windows 7: Start  Run  telnet [IP-address]

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 / 120 800652.11

menu options menu title parameters 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 480x 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 / 120 800652.11

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:

© MOBATIME configuration pages

(tabs)

For further details on the general MOBA-NMS operation, check the integrated online help (menu „Help  Show help“).

Important:

In order for the communication between MOBA-NMS and the DTS devices to work, SNMP must be activated! Set terminal menu

„Configuration  SNMP  SNMP Mode“ to „on“. SNMP is active by default.

20 / 120 800652.11

Menus:

Status Display of various information regarding operation and environment

See Chapter “6.4 Status Menu“

Configuration Configuration of the DTS 480x

See Chapter “6.5 Configuration Menu“

Maintenance Software update, backup and restore

See Chapter “6.6 Maintenance Menu“

© MOBATIME 21 / 120 800652.11

The status menu consists of 2 pages.

Status menu page 1:

© MOBATIME

The menu shows various information on the current operating status.

1. Requesting alarm status, display of all the DTS 480x active errors.

Display of the DTS 480x 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 480x active alarms are displayed, masking (e-mail, traps, relay) only occurs later.

2. Alarm history display.

Display of the DTS 480x 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 99.

Max. length of error report: 240 messages.

3. Current time and status display. See Chapter "6.4.1 Time information and status "

4. Time source information display. See Chapter "6.4.2 Time source information "

5. Line information display (line time, status, line current)

6. Current network configuration display. With ENTER, a second page can be displayed with network information.

7. Internal system information display (internal status,..). 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 480x.

22 / 120 800652.11

Status menu page 2:

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

© MOBATIME 23 / 120 800652.11

6.4.1 Time information and status

- Internal time of the DTS:

- Stratum of DTS:

- Last measured drift:

- Time source:

- Offset to source:

- Jitter of the source:

- Quality of the source:

- CAN server local time current stratum drift before the last quartz correction in "()" Frequency of NTP (only for support) current time source offset to source (source – system time) current jitter quality of the source current CAN server in CAN mode

© MOBATIME 24 / 120 800652.11

6.4.2 Time source information

- Currently measured offset:

- Last time received DCF:

- Sec. counter DCF:

-Stratum of the source:

last measured offset last time received from DCF source

In "()" information about number of available satellites (only with GPS 4500).

With a DCF receiver this is a random value.

the counter is incremented by 1 with each DCF pulse. For the minute marker, the counter is set to 0. stratum of the local time source can be defined

© MOBATIME 25 / 120 800652.11

Configuration of the DTS 480x via different sub-menus:

1. Configuration of the lines / outputs (MOBALine, impulse line, DCF active code line,

DCF out, RS485 line, serial telegrams, NTP slave clock lines, switch functionality) see chapter "6.5.1 Lines"

2. Configuration of the time source, time keeping, etc.

See chapter "6.5.11 Time handling"

3. Alarm settings (alarm relais, e-mail, SNMP)

See chapter "6.5.17 Alarms"

4. General settings for the DTS 480x (language, time zone for alarms and display, password for menu...)

See chapter "4.4.21 General settings"

5. Netzwork settings

See chapter "6.5.23 Network"

6. Services (switch network services such as FTP, Telnet, SSH on or off)

See chapter "6.5.24 Services (Network services FTP, Telnet, SSH....)"

7. SNMP configuration for GET/PUT.

See chapter "6.5.25 SNMP" (Traps are dealt with in menu ’2. Configuration’ 

’3. Alarms’  ’3. Traps’. See also chapter 6.5.21 SNMP Traps)

© MOBATIME 26 / 120 800652.11

6.5.1 Lines

Under lines, the settings for the following 5 functions can be made:

 MOBALine / Impulse line 1 /  see chapter “6.5.2 MOBALine“

DCF active code line 1



see chapter “6.5.4 Impulse line“



see chapter “6.5.5 DCF active code line“

 MOBALine / Impulse line 2  see chapter “6.5.2 MOBALine“

DCF active code line 2  see chapter “6.5.4 Impulse line “

 see chapter “6.5.5 DCF active code line“

(2. Line only active with the DTS 4802)

 DCF / Pulse output

 see chapter “0 DCF / Pulse Output“

 Ser. telegrams / RS485 Line  see chapter “6.5.7 Serial Telegrams”

 see chapter “6.5.8 RS485 Clock Line”

(RS 485 clock line only active with the DTS 4801)

 NTP slave clocks / time zone server

 see chapter “6.5.9 NTP Slave clocks / Time Zone

Server“

 Switch functions

 see chapter “4.4.9 Switch Functions“

© MOBATIME 27 / 120 800652.11

6.5.2 MOBALine

MOBALine clock line with switch function for clock illumination, switch program and world time function. Display of line 1 or 2

1. Select line type: 0 = MOBALine, 1 = Impulse line, 2 = DCF active code line

2. Select line function: Line switched off, line switched on, let clocks run to 12:00.

3. Select MOBALine mode: Minute steps, 30 second steps or cont. (10 sec. steps)

4. Select time zone (see chapter “6.5.28 Time zone selection“)

5. Select maximum current (0-700mA) on the line. The line will be switched off for as long as the overcurrent is connected.

DTS 4802: The maximum current is divided between both lines, i.e. it can always only be the remainder at the most that can be set as the maximum amount.

6. Switch function on or off

7. World time function on or off

8. Configure time zone table for world time

Important:

Changes can only be undertaken when the clock line is switched off!

© MOBATIME 28 / 120 800652.11

Time zone table for the world time function:

Display of all time zone entries (20) of the world time function for MOBALine.

By entering a zone number, the particular entry can be changed.

Select time zone (see chapter “6.5.28 Time zone selection“)

Exit the page with 99. The changes are first saved on the overlying menu page or reset.

6.5.3 IRIG-B, AFNOR (Option)

In the case of the "DTS 4801.masterclock IRIG-B“ model, an IF 488 interface is internally installed. The function is only available, if the clock line is configured to

MOBALine!

The IF 488 interface is configured to "IRIG-B standard" by default. If a different code

(e.g. AFNOR) is required, the back of the DTS 4801.masterclock must be removed and the IF 488 configured by means of the DIP switches (see Appendix F Option IRIG-B: IF

488 configuration).

A maximum of 15 clocks can be connected to an IF 488.

MOBALine is always displayed in the menu (also with integrated IF 488).

© MOBATIME 29 / 120 800652.11

Impulse clock line with display of the line number:


2. Select line function: Line switched off, line switched on

3. Select line mode: Minute steps, ½ minute steps, 1/5 minute steps, 1/8 minute steps, second steps


5. Select maximum current (0-1,000mA) on the line. The line will be switched off as long as the overcurrent is connected.

DTS 4802: The maximum current is divided between both lines, i.e. it can always only be the remainder at the most that can be set as maximum current.

6. Line time with the format: “hh:mm:ss YY.MM.DD“

7. Pulse time (200-30000ms, resolution approx. 50ms)

8. Pause time in catch-up (200-30000ms, resolution approx. 50ms)

9. Catch-up mode: 12 hrs, 24 hrs, 1 week

Important:


Normal operation Acceleration

© MOBATIME t

PD t

PP t

Mode

: t

PD t

PD t

PP t

Mode

Impulse interval is determined by the line mode (e.g. min = 1 minute)

30 / 120 800652.11

6.5.5 DCF active code line

DCF active code line with display of the line number:


2. Select line function: Line switched off, line switched on

3. Select line mode: See the diagrams on the next page.


5. Select maximum current (0-1000mA) on the line. The line will be switched off as long as the overcurrent is connected and restarted only on the next minute.

DTS 4802: The maximum current is divided between both lines, i.e. it can always only be the remainder at the most, that can be set as maximum current.


Important:

© MOBATIME 31 / 120 800652.11

The six different DCF active code modes:

Mode 1

+

U

Mode 2

+

U

-

0

1s 2s 3s t

-

0

1s 2s 3s t

-

0

Mode 3

+

U

1s 2s

3s t

-

0

Mode 4

+

U

1s 2s 3s t

Mode 5:

+

U

1s

0

2s 3s

Mode 6

+

U

1s 2s 3s t

0 t

-

Mode 1/6, 2/5, 3/4 are equal. Their polarity only depends on how the line is connected to the DTS 480x.masterclock. The signal forms shows the voltage measured from terminal a to terminal b (refer to annex A).

© MOBATIME 32 / 120 800652.11

6.5.6 DCF / Pulse output

1. Select line function: Line switched off, line DCF output, line pulse output

2. Select time zone -> see chapter “6.5.28 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 (20-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)

© MOBATIME 33 / 120 800652.11

Serial telegram output via RS232 and RS485.

(RS485 and NMEA is only available with the DTS 4801)

1. Select mode: Line switched off, RS485 line, serial telegrams, NMEA

(RS485 line and NMEA only with DTS 4801).


3. Com mode:

0 = off

1 = send

2 = read RS232

3 = read RS485

4 = send and read (read only from RS232)

5 = send and read (read only from RS485)

The modes 2 and 3 (read RS232 and read RS485) are not yet available.

4. Baudrate: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400

5. Data bit: 7 or 8

6. Stop bit: 1 or 2

7. Parity:

8. Selecting telegram file changes to the menu “SELECTION OF FILE“

Important:

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 34 / 120 800652.11

Selection of the telegram file:

The copy procedure of telegram files is explained in chapter "7.10 Copying telegram or program files to DTS 480x.masterclock".

© MOBATIME 35 / 120 800652.11

6.5.8 RS 485 Clock line

Monitored clock line for 31 slave clocks

(only available with the DTS 4801)

1. Select mode: Line switched off, RS485 line, serial telegrams

2. RS-485 mode: Off, monitored, 12 o’clock position


4. Switch function: 0=off, 1-64 = channel number of the switch functionality

5. Select and configure the slave clocks (menu RS 485 clock line)

6. Display error list (history) of the clock line (error list of the RS 485 slave clock line, see the following pages)

To set the parameters, the line type has to be selected first!

Important:

The RS485 line communicates with the following communication parameters via the

RS485 interface:

9600 bauds, 7 data bits, even parity, 1 stop bit, no flow control

The MOBA-RS485 PROTOCOL is used for the monitored clocks.

The broadcast function can be configured with the serial telgramm MC482STD.TEL.

© MOBATIME 36 / 120 800652.11

Menu

RS 485 Clock line

Display of all the slave clocks (31) in the RS485 clock line on 3 pages. The different pages can be scrolled through by clicking ENTER. A monitored clock is displayed with an [*]. [ ] shows an unmonitored clock. In addition, the name, status, type and state of the light monitoring is displayed.

By entering the clock number, the page changes to that of the required slave clock:

© MOBATIME

1. Select clock function: Clock monitored on or off

2. Clock name for identifying the clock / clock location

Status of the clock: “operation“, “no connection“, “wrong time“, “comm. error“,

“equipment error“, “unknown“,

(Comm. error: e.g. if 2 clocks have the same address)

In brackets behind the status: Info for support

Type of clock, e.g. SU 190, DMU 140, DMU 350, DC 57/100/180

Software and software version of the clock

Status of light monitoring

37 / 120 800652.11

Alarm list of the RS485 slave clock line:

Error number display (continuous), equipment number (clock number), name, date and time of the error in UTC, error name and error number.

The error list is deleted when the DTS 480x is restarted.

© MOBATIME 38 / 120 800652.11

6.5.9 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.

© MOBATIME

1. Mode of clock line: 0 = off, 1 = Send NTP multicast, 2 = Send NTP Multicast and time zone table, 3 = Send time zone table, 4 = Time zones on request, 5 (only for maintenance) = Send an empty time zone table and return to previous mode.

2. Multicast adress for NTP and time zone server: 239.192.54.x

Group address: x = 1..15 for MOBATIME devices, e.g. NCI, SEN 40.

3. Multicast port for time zone server (enter an arbitrary value, empty is not allowed !

Value e.g.: 65534). The port is also needed for requesting Time zone entries

(mode 4).

4. Poll-interval for NTP Multicast in 2^poll-values in seconds (range: 1 – 16).

E.g. poll-value = 2  interval: 2

2

= 4 sec., poll-value = 5  interval: 2

5

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

Important:

Changes of multicast-address, pollinterval and TLL lead to a restart of the

NTP server!

Important:

For the operation of a Multicast communication (NTP and Time Zone

Server) the configuration of a gateway is required (see chapter 6.5.23

Network). The gateway can be set manually or by using DHCP.

If no gateway is available, the own IP can be set as gateway.

39 / 120 800652.11

Important: Redundant NTP Multicast time server:

If in the same network two NTP servers should send NTP with the same

Multicast IP address (redundancy), then the first time server has to be configured with a small pollinterval (e.g. 2  4 sec.) and the 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

480x.masterclock 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.28 Time zone selection“)

The page can be exited with 99. Changes are first stored or reset on the overlying menu page.

© MOBATIME 40 / 120 800652.11

6.5.10 Switch function / Switch program

Switch functions for MOBALine (channel relay) and the RS485 clock line to switch the illumination of the slave clocks.

1. Time zone selection (see chapter “6.5.28 Time zone selection“)

2. Selection of the program file changes to the menu “SELECTION OF FILE“

3. Switch function twilight changes to the menu “SWITCH FUNCTION TWILIGHT“

4. Control inputs changes to the menu “CONTROL INPUTS“

5. Actual channel conditions / manual control changes to the menu “CHANNEL

STATE“

In chapter “10 Description of switch function“ the construction and dependence of the switch function is described.

© MOBATIME 41 / 120 800652.11

Selection of the switch program file:

Copying the program files is described in chapter "7.10 Copying telegram or program files to the DTS 480x.masterclock".

Enter 99 to remove the file selection.

Switching function twilight:

The switch function calculates sunrise and sunset on the basis of the position entered.

The accuracy of the calculation is +/-5 min. within the limits 60° north 60° south.

The switch function can be linked with AND, OR, or exclusive to a channel .

© MOBATIME

1. Channel: 0 = off, 1 - 64 = assigned channel.

2. Link Twilight: 0 = Exclusive twilight function (the switch programs are hidden on this channel )

1 = The twilight function is linked to the switch program OR

2 = The twilight function is linked to the switch program AND

3. Position: longitude in degrees. East = negative

42 / 120 800652.11

4. Position: latitude in degrees. South = negative

5. Switch on 0 – 600 min before sunrise (defines how many minutes before the calculated sunrise time it has to be switched on).

6. Switch off 0 – 600 min after sunrise (defines how many minutes after the calculated sunrise time it has to be switched off).

7. Switch on 0 – 600 min before sunset (defines how many minutes before the calculated sunset time it has to be switched on).

8. Switch off 0 – 600 min after sunset (defines how many minutes after the calculated sunset time it has to be switched off).

-1: With this value, the switch off time is delayed till the next sunrise  the illumination is switched on the whole night.

Actual state: shows if the switch function is on or off. The state change of the lines

(MOBALine and RS485) can be delayed up to 1 min.

Control inputs:

Each of the 4 alarm inputs can be linked as control input or switch input to a channel with AND, OR, or exclusive.

© MOBATIME

1. Channel Input 1: 0 = off, 1 – 64 = assigned channel.

2. Link Input 1: 0 = switch output exclusive (the switch programs are

hidden on this channel)

1= The switch input is linked to the switch program OR

2 = The switch input is linked to the switch program AND


4. Link Input 2: see no. 2


6. Link Input 3: see no. 2


8. Link Input 4: see no.

If an alarm input is used as switch input, it must be masked in all alarm masks.

In chapter “10 Description of switch function“ the set up and dependency of the switch functions are described.

43 / 120 800652.11

Channel state:

Display of all 64 channels of the switch functions. A switched on channel is displayed with an [*]. [ ] shows a locked channel in a switched off state whereas [*] shows a switched on channel in a locked state.

An ! shows that the channel is linked to a control output.

An s shows that the channel is linked to the twilight calculation.

By entering a channel, the page can be changed to that of manual switching for that channel:

After a restart or after changing the program file, it can take up to 2 min until the states displayed correspond to the effective states on the channel relay.

© MOBATIME 44 / 120 800652.11

Manual switching:

© MOBATIME

1. Channel on: The channel is switched on immediately. The channel then takes over the state of the switch programs , switch function or switch inputs again. It can take up to 2 minutes to adopt.

2. Channel off: The channel is switched off immediately. The channel then takes over the state of the switch programs, switch function or switch inputs again. It can take up to 2 minutes to adopt.

3. Channel on and lock: The channel is switched on immediately and locked in this state.

4. Channel off and lock: The channel is switched off immediately and locked in this state.

5. Unlock channel: The channel takes over the state of the switch programs, switch function or switch inputs again. It can take up to 2 minutes to adopt.

In the menu '2 Configuration  2 Time handling', settings can be undertaken for the following functions:

 General settings  See Chapter 6.5.12

 Configuration of the local time source  See Chapter 6.5.13

 NTP Server / NTP Sources  See Chapter 6.5.14

 CAN (MTC)  See Chapter 6.5.15

 Manual time set  See Chapter 6.5.16

45 / 120 800652.11

6.5.12 General time configuration

1. Stratum limit for synchalarm:

Stratum limit (1-16) for generating the alarm „Failure time source Str“.

Default value: 5.

Explanation:

If the stratum of the DTS 480x is higher or equal than the value

"Stratum limits for synchalarm", then after a fix delay of 1 min the alarm

"Failure time source Str" occurs  sync LED turns off !

2. Mode leap second:

0 Off

1 Additional second is added to the time period set

-1

2

Is set to 0=off after adding the leap second.

A second is omitted at the time period set.

Is set to 0=off after adding the leap second.

Recognize leap second automatically. Only possible in the case of a source notifying the leap second!

3. Set period of time for the leap second in UTC with the format: “hh:mm:ss

TT.MM.YY“. The next usual time will be displayed as a proposal.

Description of leap second see chapter “8.6 Leap Second“.

© MOBATIME 46 / 120 800652.11

Time source configuration: '2 Configuration  2 Time handling  2 Local time source settings':

© MOBATIME

1. Source type: 0=none, 1=DCF, 2=local, 3=serial

(serial only in connection with NMEA)

2. Time zone of the source: see chapter “6.5.28 Time zone selection“)

3. DCF/GPS source correction: (-60000ms..+60000ms)

4. Alarm delay at failure of time source (minutes):

0 = off, 1 – 2'160min, default = 0

Error: “Failure time source TO“ only 0=off

100 - 5000ms= Limits as from which time is no longer

6. Fix stratum: 0=Stratum is calculated automatically on the basis of the time source

1 - 15=Stratum of the DTS 480x is set by means of the description in the table in chapter “8.3 Fix stratum for local time source”

7. Stratum TO (Timeout) (0-16) DCF/GPS fail:

Duration of stratum change 1 to 16 in the case of time loss (1-999h), e.g. 24 hrs  after DCF/GPS time source failed, stratum counts up from 1 to 16 within 24 hrs

Default value: 12h

For description of time source see chapter “8 Time administration“

47 / 120 800652.11

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'  ’3 NTP Server / NTP Sources’ at least one server has to be set.

The exact behavior of NTP time sources is described in chapter “8.2 Time take-over,

NTP“.

Further 2 multicast or broadcast addresses can be configured:

1.-4. Summary about configured NTP – time sources. Select to configure and display

changes to the menu "ENTRY TIMESOURCE"

5.-6. Summary about configured NTP – broadcast addresses. Select to

configure and display changes to the menu “NTP MULTI- / BROADCAST-

ENTRY“

7. NTP Authentication: Changes to the menu “NTP AUTHENTICATION“

Information about a multicast – address, configured for NTP slave clocks.

© MOBATIME 48 / 120 800652.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: 2

2

= 4sec., poll value=5  intervall 5: 2

Range of poll values (exponent): 1 – 16

5

= 32sec.

To get an 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

If possible, one source should always be preferred (even if only one source is defined), except if DCF is active.

6. Authentication key: off, key number, autokey

Important:

All changes lead to a restart of the NTP server!

Important:

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 as far as possible.

© MOBATIME 49 / 120 800652.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 2 x

: 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

Important:

All changes lead to a restart of the NTP server!

© MOBATIME 50 / 120 800652.11

Configuration of the NTP authentication:

The NTP authentication is described in chapter “8.7 NTP authentication“.

!

© MOBATIME

1. Import keys (from/ram directory)

The file ntp.keys must first be copied into the directory /ram.

Attention:

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 spaces

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 gen_mv generate the GQ certificate generate the MV certificate gen_all gen_client generate all (IFF,GQ,MV) certificates generate the client certificate update_server update the server certificate update_client update the client certificate export_iff export_gq export_mv export the IFF server certificate to /ram. Parameter password of the client export the GQ server certificate to /ram. export the MV server certificate to /ram. import_iff import_gq import_mv clear_ram clear_keys import the IFF server certificate from /ram. import the GQ server certificate from /ram. import the MV server certificate from /ram. delete the certificates in /ram delete the certificates in the NTP key directory

Example: export_iff myPassword exports the IFF client certificate to /ram.

51 / 120 800652.11

Call menu: '2 Configuration  2 Time handling  4 CAN (MTC)':

!

1. CAN –mode on or off

If CAN is switched on, all the time source entries are accepted according to the set values of the MTC CAN module U6.5. The time sources can no longer be changed if

CAN is switched on on the DTS 480x.

If multicast is used, the local time source must be set to "local".

Otherwise, it can be set to "off".

Attention:

© MOBATIME 52 / 120 800652.11

6.5.16 Manual time set

Call menu: '2 Configuration  2 Time handling  5 Manual time adjustment':

1. Set UTC time in the format “YY.MM.DD hh:mm:ss“.

Time is set with ENTER!

2. Correct time in ms (- = backwards). Range: +/-10'000ms

Time is set with ENTER!

© MOBATIME 53 / 120 800652.11

6.5.17 Alarms

Under alarms, settings can be undertaken for the following functions: relays see chapter 6.5.18

 E-Mail

see chapter 6.5.20

 SNMP-Traps

see chapter 6.5.21

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

© MOBATIME 54 / 120 800652.11

Display of all the DTS 480x 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.

The alarm masks only apply to the corresponding function, but not for the internal alarm recording (Menu '1. Status'  ’1. Alarm state’ and Menu '1. Status'  ’2. Alarm history’).

© MOBATIME 55 / 120 800652.11

6.5.20 E-mail

E-mail alarm messages via SMTP.

E-mail configuration page 1:

1. E-mail function on or off.

2. Alarm mask for e-mail notifications (see chapter "6.5.19 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


4. Mail server port (often 25)

5.-6.Destination e-mail address


7. Reply address (e.g. support, administrator...)


8. Sender address (important for authentication through the mail server)


Press ENTER to change to page 2.

Important:

Configuration of a gateway is required for sending e-mails (see chapter

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

© MOBATIME 56 / 120 800652.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 21 set: NTP does not run>

Time <13:34:34 06.02.09>

Hostname <DTS480x (10.241.0.18)>

© MOBATIME 57 / 120 800652.11

6.5.21 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.19 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

Important:

General settings for SNMP can be found in menu ’2. Configuration’ 

’7. SNMP’. See also chapter "6.5.25 SNMP").

Important:

Configuration of a gateway is required for sending SNMP traps (see chapter 6.5.23 Network). This can be set via DHCP or manually.

Important:

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

Important:

SNMP has to be activated for sending traps.

© MOBATIME 58 / 120 800652.11

Configuration of the receiving systems

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


2. Port of the evaluation system (usually 162).

3. SNMP Version: 1=SNMP V1, 2=SNMP V2c

Important:


© MOBATIME 59 / 120 800652.11

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.28 Time zone selection“)

3. Enter password for the menu (user dts) (max. 15 characters). A password must be configured.

© MOBATIME 60 / 120 800652.11

6.5.23 Network

1. Configuration of IPV4 parameters

2. Configuration of IPv6 parameters

!

Attention: 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.'

The menu is closed upon modifying the IP or the DHCP mode.

Important:

Important:

DHCP on/off, each change of this setting will result in a restart of the NTP server!

Important:

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.

!

!

© MOBATIME

Attention:

Attention:

Only one DNS server should be configured (IPv4 or IPv6).

Settings to the network must be agreed with the network administrator!

61 / 120 800652.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.

Important:

DHCP on, if no DHCP server is available, leads to longer start-up time

(<75 sec.) of the DTS 480x.

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

© MOBATIME 62 / 120 800652.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 63 / 120 800652.11

6.5.24 Services (network services FTP, telnet, SSH....)

Network services configuration:

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

© MOBATIME 64 / 120 800652.11

6.5.25 SNMP

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

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

Important:

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’ at least the trap community and the receiver must be configured. See also chapter “6.5.21 SNMP Traps").

2. Alarm mask for SNMP status (see chapter "6.5.19 Alarm mask"). The modifications will be saved or restored one menu level higher in “SNMP CONFIGURATION".

3. Location information which is displayed in SNMP management tool.

4. Contact information which is displayed in SNMP management tool.

5. Configuration of SNMP V1 / V2 c (specific settings). See chapter “6.5.26 SNMP V1

/ V2c“

6. Configuration of SNMP V3 (specific settings). See chapter “6.5.27 SNMP V3“

Important:


© MOBATIME 65 / 120 800652.11

6.5.26 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.

Important:


© MOBATIME 66 / 120 800652.11

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

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

Important:


User configuration SNMP V3:

© MOBATIME

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

2. Minimal security level: 0=noauth (no authentication)

3. SNMP read access:

2=priv (authentication and privacy)

0=none (no access)

2=DTS info (only DTS specific information)

3=user defined 1 (viewDTS1)


67 / 120 800652.11

4. SNMP write access: 0=none (no access)

2=DTS info (only DTS specific information)



Important:


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.

Important:


© MOBATIME 68 / 120 800652.11

6.5.28 Time zone selection

Display of all the DTS 480x 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 is selected at any time.

Press ESC to leave the page. The modifications will be saved or restored one menu level higher.

© MOBATIME 69 / 120 800652.11

1. Initiating a software update (files must have been copied by FTP into the directory

/ram

of the DTS 480x before).  See chapter "7 Updates". The command always leads to a restart of the DTS 480x (even if no files were copied for update)

Important:

Possibly save configuration first.

2. Initiate a software update (files must first be put on to a USB stick in the DTS

480x).  See chapter "7 Updates". The command always leads to a restart of the

DTS 480x.masterclock (even if no files were copied for update)

Possibly save configuration first.

Important:

3. Save the entire configuration (incl. program and telegram files) and the log files on a USB stick . Also generates a diagnosis file (dts480xsystem_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 dts480x.conf.bkp is created).

5. Restore the entire configuration from a backup stored locally.

After the restore the DTS 480x is automatically restarted.

6. Restore the entire configuration to factory settings.

After the restore the DTS 480x is automatically restarted.

7. Restart DTS 480x.masterclock.

8. Copy telegram or program files on to the DTS 480x.masterclock.

 See chapter "7.10 Copying telegram or program files on to the DTS

480x.masterclock".

See also chapter "7 Updates".

© MOBATIME 70 / 120 800652.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.

Attention:

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

7.2 Updating images via 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 (binary) to the DTS 480x.masterclock 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 480x and the program and telegram files are overwritten. In order to store the configuration, the file dts480x.conf from the directory /etc and any possible program and telegram files must be saved from the directory /var/local/dts. After the update, the file can again be written on the DTS 480x in accordance with chapter “7.3

Updating applications or configurations via FTP“. Impulse lines should be stopped before the update with dtscfg.img and separated from the DTS 480x (after the update, the line starts with MOBALine).

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 480x 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 480x is automatically restarted on completion of the update. The Telnet or SSH session has to be restarted.

© MOBATIME 71 / 120 800652.11

!

Attention:

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 480x 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 via FTP

To update individual files such as, e.g. dts4801, dts4801menu, ntpd, dts4801mod.ko, dts4801.conf, etc. on the DTS 480x, the following steps are carried out  all file

names are case-sensitive.

1. Connect a FTP client software (binary) to the DTS 480x 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.


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 480x is automatically restarted on completion of the update.

The Telnet or SSH session has to be restarted.

Attention:

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 480x will be destroyed and it has to be returned to the manufacturer for repairing.


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 480x.masterclock

3. If an update of the dtscfg.img image is made, the configuration of the DTS 480x and the program and telegram files are overwritten. In order to store the configuration, the file dts480x.conf from the directory /etc and any possible program and telegram files must be saved from the directory /var/local/dts. After the update, the file can again be written on the DTS 480x in accordance with chapter “7.3

Updating applications or configurations via FTP“. Impulse lines should be stopped before the update with dtscfg.img and separated from the DTS 480x (after the update, the line starts with MOBALine).

© MOBATIME 72 / 120 800652.11

!


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 480x is automatically restarted on completion of the update. The Telnet or SSH session has to be restarted.

5. As soon as the DTS 480x is restarted, remove the USB stick.

Attention:

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 480x will be destroyed and the DTS 480x 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 .


!

7.5 Updating applications or configurations via USB

To update individual files such as, e.g. dts4801, dts4801menu, ntpd, dts4801mod.ko, dts4801.conf, etc. on the DTS 480x, the following steps are carried out  all file

names are case-sensitive.

1. Copy applications (or configuration) to the USB stick

2. Plug the stick in the DTS 480x


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 480x is automatically restarted on completion of the update.

The Telnet or SSH session has to be restarted.

4. As soon as the DTS 480x is restarted, remove the USB stick.

Attention:

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 480x 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 73 / 120 800652.11

!

Establish anonymous connection:

ftp://“IP address of DTS 480x“ 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 480x“.

e.g. with Internet Explorer enter: ftp://[email protected]

Password: resp. the defined password for the menu.

To directly reach the sub-directory /ram, you can also enter

ftp://[email protected]/ram.

Establish connection with IPv6: address be written in brackets [ ]:

e.g. with Internet Explorer enter: ftp://dts@[fd03:4432:4646:3454::2000]

The file has to be copied in binary mode (not ASCII).

Attention:

FTP-Tools

Integrated in the system

(file manager):

Programs (examples)

Windows 98, ME, 2000, XP, Vista,

Windows 7

Linux (Suse, Redhat)

Windows Explorer

Start

 Execute: Explorer

CuteFTP

Konqueror

Kbear

SFTP = SSH File Transfer Protocol

SFTP-Tools



Windows 7


(file manager):

Programs (examples)

- Konqueror

WinSCP -

© MOBATIME 74 / 120 800652.11

SCP = Secure Copy Protocol

Important:

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 7


(file manager):

Programs (examples)

-

WinSCP

With command line

-

7.9 Save configuration externally

(for backup or copy to another DTS 480x)

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 480x (with Internet Explorer enter:

ftp://dts@[IP address]

) (as user dts).

2. Change to the DTS 480x directory /etc.

3. Save the file dts4801.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 and program files from the DTS 480x directory /var/local/dts.

© MOBATIME 75 / 120 800652.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 480x by selecting the menu '3. Maintenance'

 ’3. Backup configuration and log to USB’ and press ENTER. All files (including program and telegram files) will be copied into the root directory of the USB stick.

Copy configuration to an other DTS 480x:

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 .

Important:

When copying the configuration from one DTS 480x to an other, the IP address may have to be changed after the download by serial connection

7.10 Copying Telegram or Program files to the DTS 480x.masterclock

Analogously to the previously described procedures telegram and program files can be copied via FTP or USB stick to the DTS 480x.

The copy procedure can be started on the DTS 480x by selecting the menu

'3. Maintenance'  ’8. Copy telegram- and program-files' and press ENTER.

Afterwards, select again in the menu “6.5.7 Serial telegrams” and reload.

The files are stored in the directory /var/local/dts and can be deleted or copied via

FTP.

In addition to the program files (*.prg), *.mbs3 – files (SwitchEditor) can also be copied to the DTS 480x and also be read again later from there.

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.

© MOBATIME

Important:

After the file copy procedure, the output of the telegram files and the treatment of the switch programs are re-started (take over of the files).

Important:

The file name is limited to 8 characters before the dot, e.g. IF482Std.tel.

76 / 120 800652.11

8.1 Concept of time administration

The internal master clock as well as the real-time clock runs with UTC (Universal Time

Coordinated). The synchronisation inputs, the time shown on the display, as well as all outputs are linked via a time zone entry with the master clock time, i.e. all inputs and outputs can be individually allocated to a specific time zone.

External DCF

Time Source

(B)

Time Zone Entry

RS485 Slave Clock Line

Serial Telegrams

LAN Multicast

Devices

(F)

Time Zone Entry

(G)

Time Zone Entry

(C)

Time Zone Entry

UTC

Master

Clock

(D)

Time Zone Entry

(A)

Time Zone Entry

(E)

Time Zone Entry

- Operation

- Display

- Error report

MOBALine, (IRIG),

Impulse Line,

DCF active line

DTS 4802: 2 lines

Configurable time zones:

Time Code output

(DCF 77)

Switch Program

(C) Chapter 6.5.2, 6.5.4

(F) Chapter 6.5.7 6.5.8

© MOBATIME 77 / 120 800652.11

8.2 Time take-over, NTP

Generally NTP as per RFC 1305.

Maximum 4 sources.

Reference clock for DCF with selectable time zone.

Time take-over from DCF:

 Reference clock for the reception from DCF.

At least 3 minutes of reception required before the NTP server is available.

Stratum of the time source = 0  Stratum of DTS 480x = 1.

Time take-over from NTP:

 As per NTP RFC 1305 (www.ntp.org)

(see http://support.ntp.org/bin/view/Servers/WebHome for servers on internet)

Time take-over from RTC (internal time of the DTS 480x):

 The NTP server is started with stratum 3, if a DCF source is configured.

As soon as a time source delivers the time, the stratum is set accordingly.

If there is no DCF time source configured, the NTP server will only start when it receives the time from another NTP server.

Manual time setting:

 The NTP server will be started with stratum 3 if DCF is configured as time source.

As soon as a time source delivers the time, the stratum is set accordingly.

If there is no DCF time source configured, the NTP server will only start when it receives the time from another NTP server.

Error cases:

 DCF failure:

Depending on the setting of the “Stratum TO (1-16)”, the stratum will be counted upwards, till it reaches 16.

When the startum reaches the value "Stratum limit for synchalarm", the alarm

"Failure time source Str" occures (fix delay of 1 min) and the sync LED turns off.

When a time source is available again, the stratum will immediately be set according to the time source (stratum time source + 1).

 DCF failure with NTP as backup time source:

Depending on the setting of the “Stratum TO”, the stratum will be counted upwards, till it reaches 16.

In case the stratum limit is reached and a NTP server with a better stratum is available, the DTS 480x synchronizes from NTP.

When the local time source is available again, the stratum will immediately be set according the time source (stratum time source + 1).

 NTP failure:

The failure of the/all NTP source/s without a defined fix stratum and without DCF.

Normally, it takes 8 * the poll intervall of the current source until the peer is recognized as invalid (source can no longer be reached) and NTP loses synchronization. The length of time, with the exception of the poll interval, also depends on the jitter measured, number of sources, length of synchronization and source deviation, and can thus deviate enormously in individual cases.

Exception for time take-over:

After a software update, the first time take over can last distinctly longer (> 8 minutes).

© MOBATIME 78 / 120 800652.11

8.3 Fix stratum for local time source

In operation with NTP time sources and the parameter "Local time source = off", the behavior of the NTP server is that of a standard NTP server. When the time sources are no longer available or invalid, the NTP server becomes unsynchronized after a short time as per NTP algorithm.

To provide multicast NTP for slave clock lines, the NTP server has to remain synchronized. An unsynchronized server does not send out any time. The slave clocks in this case will run to the 12 o'clock position.

Therefore, in this case it makes sense to set the Fix stratum value unequal to 0 and if only NTP time sources are in use for the synchronization of the DTS 480x, to set the local time source to local.

Time source(s)

DCF/GPS without

NTP

Fix stratum = 0

DCF/GPS with NTP

DCF ok: Stratum DTS 480x always

1, Time always from DCF

DCF nok: If NTP is available

Stratum DTS 480x =

Stratum NTP source + 1

Else: Stratum is increased as per set stratum timeout value till NTP server is

unsynchronized

(Stratum DTS 480x = 16)

DCF ok: Stratum DTS 480x always

1, Time always from DCF

DCF nok: Stratum is increased as per set stratum timeout value till NTP server is

unsynchronized

(Stratum DTS 480x = 16)

Local with NTP

NTP ok: Stratum DTS 480x = current NTP source + 1

NTP nok: Stratum of the local time source is increased as per set stratum timeout value after DTS 480x start  normally the NTP server is unsynchronized quite fast when NTP time source is

failed

Attention:

no reasonable

configuration

Local without NTP

Only for testing purposes for a DTS

480x without any time source which should nevertheless have a NTP time server with a valid time.

The stratum of the DTS 480x starts from 0 to unsynchronised as per set stratum timeout value.

Fix stratum > 0

DCF ok: Stratum DTS 480x always 1,

Time always from DCF

DCF nok: If NTP is available

Stratum DTS 480x =

Stratum NTP source + 1

Else: Stratum is increased as per set stratum timeout value till stratum of time source =

Fix

 Stratum DTS 480x now keeps fix stratum + 1

DCF ok: Stratum DTS 480x always 1,

Time always from DCF

DCF nok: Stratum is increased as per set stratum timeout value till stratum of time source =

Fix

 Stratum DTS 480x now keeps fix stratum + 1

NTP ok: Stratum DTS 480x = current NTP source + 1

NTP stratum of NTP time source > Fix stratum

NTP nok: Stratum DTS 480x = fix stratum + 1

Only for testing purposes for a DTS

480x without any time source which should nevertheless have a NTP time server with a valid time.

The stratum of the DTS 480x is Fix

stratum

+ 1.

© MOBATIME 79 / 120 800652.11

8.4 Time server

 NTP v4 (compatible with v3) as per RFC 1305 (Port 123)

NTP Authentication with MD5 Key / Autokey

 SNTP (UDP), RFC2030 (Port 123)

 TIME (TCP/UDP), RFC 868 (Port 37)

 DAYTIME (TCP/UDP), RFC 867 (Port 13)

8.5 Time accuracy, time-keeping

See Appendix I Technical data.

Manual mode

Notification of the leap second is always issued 1 hour before the period of time set via

DCF and NTP*.

*Notification is only transmitted via NTP, if the local source or a DCF source is switched on. If only a NTP source/s is configured, the state of the source will be passed on.

Automatic mode

In automatic mode, the source is checked for 1 hour before the time of the possible leap second (DCF or NTP) for any possible notification. If notification is recognized, it will be passed on via NTP and DCF output and the leap second added.

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 coded.

8.7.1 NTP symmetric keys

A 32-bit key ID and a cryptographic 64/128-bit hash value 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 480x only supports the MD5 procedure.

© MOBATIME 80 / 120 800652.11

The receiving NTP service calculates the hash value 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 hash value will not be used for synchronization .

The DTS 480x must be correspondingly configured to be able to use NTP authentication (chapter 6.5.14 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.

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)

© MOBATIME 81 / 120 800652.11

The validity of the time received to the NTP clients is assured by symmetric keys. For a higher degree of certainty, exchanging the keys used regularly is, however, necessary to obtain protection, e.g. from replay attacks (i.e. attacks in which recorded network traffic is simply played back).

The autokey procedure was introduced as the exchange is very involved in a large network. A combination of group keys and public keys enables all NTP clients to check the validity of the time information which they receive from servers in their own autokey group.

NTP Autokey is relatively complex in its use and studying the functionality is definitely necessary beforehand.

Autokey is descrbied at http://www.cis.udel.edu/~mills/proto.html or on the NTP homepage http://www.ntp.org.

Autokey is currently defined in an IETF draft.

http://www.ietf.org/internet-drafts/draft-ietf-ntp-autokey-04.txt

The configuration of Autokey is explained in

http://support.ntp.org/bin/view/Support/ConfiguringAutokey

or in

http://www.ntp.org/ntpfaq/NTP-s-config-adv.htm#S-CONFIG-ADV-AUTH

.

© MOBATIME 82 / 120 800652.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 480x.masterclock (MIB II, DTS480x).

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:

dtsInfo:

mobatime mobatime (not changeable, read only)

DtsUser1 and dtsUser2 have full read/write access on all objects. With SNMP V3 rules, access can be reduced. But the access can be restricted with corresponding SNMP V3 rules.

SNMP V3 agent supports user validation (authentication MD5) and encoding

(encryption DES).

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

DTS480x (DTS480x-MIB.TXT)

Device specific DTS definitions

SNMP V1:

DTS-COMMON (File: DTS-COMMON-MIBv1.TXT)

General DTS definition, always required

DTS480x (DTS480x-MIBv1.TXT)

Device specific DTS definitions

The MIB files can be copied from the DTS 480x.masterclock with FTP (for FTP use, see chapter “7.6 FTP Connection“):

DTS-MIB: /etc/snmp/mibs/

Standard MIBS: /usr/share/snmp/mibs/

© MOBATIME 83 / 120 800652.11

9.2 Device configuration with SNMP

If one or several variables are set with Put in a configuration group, the variable

dts480x????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

dts480x

????ConfigCmd

variable to 2

(2=undo, restore).

After sending the accept command, a dts480xConfigChanged Notification is sent.

The definitions of the available variables can be taken from the MIB files and from the menu descriptions of this manual.

Example:

Management System

Put

dts480xFTPMode=1 

DTS

Variable is set to 1 internally

Put

dts480xNetServicesConfigCmd=1  Configuration group is assumed

 Sends

Notification

with the new time dts480xNetConfigChangedTime

9.3 DTS Subagent SNMP Notification

Protocol: SNMPv2c Notification

Important:

For Notifications to be sent out, SNMP must be switched on. In addition, at least one receiver system must be configured.

9.3.1 Startup

Sent out when the subagent for the DTS is started.

[dts480xStartUp]

This Notification is always sent out, as soon as SNMP is activated and a destination address is configured.

9.3.2 Shutdown

Sent out when the subagent for the DTS is stopped.

[dts480xShutdown]


© MOBATIME 84 / 120 800652.11

[dts480xStatusChanged]

Sent out when the subagent detects a status change in the DTS application process.

The following variables are monitored for changes: dts480xSysStatus, dts480xSysTimeSource, dts480xSysStratum, dts480xSysMasterMode

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 Description Example

dts480xSysStatus Unsigned Int 4 Bytes Contains the internal system status

66309 dts480xSysTimeSource Byte dts480xSysStratum Byte

Actual time offset of the system

[us]

-1523

 -1.523ms

1 Bytes Actual time source

1 Bytes Actual system stratum level

2

1

Sent out when the subagent detects a configuration change in the DTS application processes.


The Notification sent out contains the following data:

Field Type Size Description

© MOBATIME dts480xOutLineSwitchConfigChangedTime TimeTicks Bytes dts480xOutLineSwitchFct dts480xSnmpConfigChangedTime TimeTicks dts480xSnmpConfig

The ConfigChangedTime variables show the time (TimeTicks value 1/100 seconds) 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.

85 / 120 800652.11

© MOBATIME

Configuration group table

Configuration group Variable

dts480xSystem dts480xLanguage dts480xTimezone dts480xPassword dts480xDisplayTimezone dts480xDisplayTimeFormat dts480xNetwork dts480xIPAddr dts480xIPMask dts480xIPGateway dts480xIPNameserver dts480xHostname dts480xDomain dts480xDHCPMode dts480xEthernetLinkMode dts480xIPv6AutoConf dts480xIPv6DHCPMode dts480xIPv6Addr1 dts480xIPv6Prefix1 dts480xIPv6Gateway1 dts480xIPv6Addr2 dts480xIPv6Prefix2 dts480xIPv6Gateway2 dts480xIPv6Nameserver dts480xNetServices dts480xTelnetMode dts480xFTPMode dts480xSSHMode dts480xTimeSource dts480xTSLocalMode dts480xTimeNTPServer dts480xTSLocalTimezone dts480xTSLocalTimeout dts480xTSLocalFixStratum dts480xTSLocalCorrection dts480xTSLocalStratumTimeou dts480xTSOffsetSynchOnly dts480xTSErrorStratum dts480xTSLeapSecMode dts480xTSLeapSecDate dts480xTSCanMode dts480xNTPBroadcastAddr1 dts480xNTPBroadcastInterval1 dts480xNTPBroadcastTTL1 dts480xNTPBroadcastKey1 dts480xNTPBroadcastAddr2 dts480xNTPBroadcastInterval2 dts480xNTPBroadcastTTL2 dts480xNTPBroadcastKey2 dts480xNTPSourceTable (1..4)

(dts480xNTPSourceAddr

dts480xNTPSourceMinPoll

dts480xNTPSourceMaxPoll

dts480xNTPSourceMode

dts480xNTPSourcePrefer

dts480xNTPSourceKey) dts480xTimeManualSet dts480xManualTimeSetUTC dts480xManualTimeSetDiff dts480xOutLineClock1 dts480xOutLineClock1Type dts480xOutLineClock1Mode dts480xOutLineClock1Timezone dts480xOutLineClock1AlCurrent dts480xOutLineClock1MBLFunction dts480xOutLineClock1MBLSwitch dts480xOutLineClock1MBLWorldtime

86 / 120 800652.11

© MOBATIME dts480xOutLineClockMBLTZTable (1..20)

(dts480xOutLineClockMBLTZTableEntryNumber) dts480xOutLineClock1ImpFunction dts480xOutLineClock1ImpLinetime dts480xOutLineClock1ImpWidth dts480xOutLineClock1ImpPause dts480xOutLineClock1ImpCatchUp dts480xOutLineClock2 dts480xOutLineClock2Type dts480xOutLineClock2Mode dts480xOutLineClock2Timezone dts480xOutLineClock2AlCurrent dts480xOutLineClock2MBLFunction dts480xOutLineDCFMode dts480xOutLineClock2MBLSwitch dts480xOutLineClock2MBLWorldtime dts480xOutLineClock2MBLTZTable (1..20)

(dts480xOutLineClock2MBLTZTableEntryNumber) dts480xOutLineClock2ImpFunction dts480xOutLineClock2ImpLinetime dts480xOutLineClock2ImpWidth dts480xOutLineClock2ImpPause dts480xOutLineClock2ImpCatchUp dts480xOutLineDCFMode dts480xOutLineDCFTimezone dts480xOutLineDCFPulseType dts480xOutLineDCFPulseTime dts480xOutLineDCFPulsePeriod dts480xOutLineDCFPulseCorrection dts480xOutLineDCFConfigCmd dts480xOutLineSerial dts480xOutLineSerialMode dts480xOutLineSerialTimezone dts480xOutLineSerialComMode dts480xOutLineSerialComParam dts480xOutLineSerialTeleFile dts480xOutLineRS485Mode dts480xOutLineRS485Devices dts480xOutLineRS485DevNameTable(1..32)

(dts480xOutLineRS485DevName) dts480xOutLinesRS485Switch dts480xOutLineTZServerConfigChangedTime dts480xOutLineTZServerMode dts480xOutLineTZServerMCastAddr dts480xOutLineTZServerMCastPort dts480xOutLineTZServerNTPInterval dts480xOutLineTZServerTTL dts480xOutLineTZServerTableInterval dts480xOutLineTZServerEntryInterval dts480xOutLineTZServerTable (1..15)

(dts480xOutLineTZTableEntryNumber) dts480xOutLineSwitchFct dts480xOutLineSwitchTimezone dts480xOutLineSwitchProgFile dts480xOutLineSwitchFctChannel dts480xOutLineSwitchFctComb dts480xOutLineSwitchFctLongitude dts480xOutLineSwitchFctLatiitude dts480xOutLineSwitchFctLeadSun1 dts480xOutLineSwitchFctFolSun1 dts480xOutLineSwitchFctLeadSun2 dts480xOutLineSwitchFctFolSun2 dts480xOutLineSwitchFctState dts480xOutLineSwitchInpChan1 dts480xOutLineSwitchInpComb1 dts480xOutLineSwitchInpChan2 dts480xOutLineSwitchInpComb2 dts480xOutLineSwitchInpChan3 dts480xOutLineSwitchInpComb3 dts480xOutLineSwitchInpChan4

87 / 120 800652.11

© MOBATIME dts480xOutLineSwitchInpComb4 dts480xOutLineSwitchState dts480xOutLineSwitchLockState dts480xOutLineSwitchCmdChannel dts480xOutLineSwitchCmdFunction dts480xRelayConfigChangedTime dts480xRelayAlarmMask dts480xMailConfigChangedTime dts480xMailMode dts480xMailAlarmMask dts480xMailServerIPAddress dts480xMailServerPort dts480xMailAddrDestination1 dts480xMailAddrDestination2 dts480xMailAddrReply dts480xMailAddrFrom dts480xMailUser dts480xMailPassword dts480xMailAuthMode dts480xSnmpConfigChangedTime dts480xSnmpMode dts480xSnmpAlarmMask dts480xSnmpROCommunity dts480xSnmpRWCommunity dts480xSnmpTrapMode dts480xSnmpTrapAlarmMask dts480xSnmpTrapCommunity dts480xSnmpTrapListenerIPAddress1 dts480xSnmpTrapListenerPort1 dts480xSnmpTrapVersion1 dts480xSnmpTrapListenerIPAddress2 dts480xSnmpTrapListenerPort2 dts480xSnmpTrapVersion2 dts480xSnmpTrapAliveMsgInterval dts480xSnmpLocation dts480xSnmpContact dts480xSnmpV3UserPassword1 dts480xSnmpV3UserLevel1 dts480xSnmpV3UserRead1 dts480xSnmpV3UserWrite1 dts480xSnmpV3UserPassword2 dts480xSnmpV3UserLevel2 dts480xSnmpV3UserRead2 dts480xSnmpV3UserWrite2 dts480xSnmpV3View11 dts480xSnmpV3View12 dts480xSnmpV3View13 dts480xSnmpV3View14 dts480xSnmpV3View15 dts480xSnmpV3View16 dts480xSnmpV3View21 dts480xSnmpV3View22 dts480xSnmpV3View23 dts480xSnmpV3View24 dts480xSnmpV3View25 dts480xSnmpV3View26

88 / 120 800652.11

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: dts480xSysStatus Unsigned Int 4 Bytes Contains the internal system status dts480xSysAlarms Byte Array 8 Bytes 64 Bit Alarm flags

1.Byte Bit 0..7

2.Byte Bit 8..15

::

8.Byte Bit 56..63

66309

FFF870FF.FFFFFFFF

¦ ¦ ¦

¦ ¦ 5.Byte

¦ 2.Byte

1.Byte

[dts480xAlarm]

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: dts480xTrapAlMsgErrorNr Byte dts480xTrapAlMsgErrorTime Unsigned

Int dts480xTrapAlMsgErrorText Text

1 Bytes No. of the alarm bit (0..63) 8

0 = alarm bit was deleted

1 = alarm bit was set

4 Bytes PC-time in seconds since

01.01.1970 00:00:00

59 Bytes Error text

1

946684805

Line current too high

© MOBATIME 89 / 120 800652.11

10 Description of the switch function

The switch program is composed of 99 week programs and 64 channel programs.

The week programs describe the behaviour during one week, independent of date and channel number. Such a week program can contain numerous lines and each line is composed of time of the day, days of week as well as the switching function to be executed at this moment.

The 3 possible switching functions are: ON, OFF, Signal 01 – 99 Seconds.

Now the channel programs assign the week programs to the channels, which are dependent on the date. Such a channel program can contain several lines. Each line is composed of the starting date and the number of the week program to be used.

Up to 1000 lines can be programmed in this way. This is the total sum of the lines in the week and channel programs.

Line of a week program:

Time of day

Switching function

Weekday

Line of a channel program:

Start date

Week program number

Line 1

Line 2

Line 3

Line 1

Line 2

Line 3

Channel 1

Line 1

Line 2

Line 3

Line 1

Line 2

Line 3

Channel 2

Line 1

Line 2

Line 3

Line 1

Line 2

Line 3

Channel 3

© MOBATIME

Line 1

Line 2

Line 3

Line 1

Line 2

Line 3

Channel 64

Week programs Channel programs

With the PC software "SwitchEditor" the switch programs can be created on a PC and then be downloaded to the DTS 480x via FTP / USB stick.

A maximum of 8 characters are allowed for the file name of the switch program file and its extension is PRG, Prg or prg.

Additionally the SwitchEditor project file (mbs3) can be stored on the DTS 480x.

90 / 120 800652.11

10.2 Combination of the signals

Switch program channel x

Switch function

(sunrise resp. sunset)

Alarm inputs 1-4

AND

OR

EXCLUSIVE

Menu

"Actual channel condition / manual control"

ON

MOBALine

RS 485 clock line

Menu

"Control Inputs" and Menu

"Switch function twilight"

OFF

Each of the 4 alarm inputs can as control input or switch input be linked to a channel with AND, OR, or exclusive.

If the control input is exclusive, the switch status is transmitted as quickly as possible via MOBALine (0-10sec).

If the control input AND or OR is linked to the switch program, the status of the input is transferred to the next but one minute.

The switch inputs have priority as opposed to the twilight function: i.e. if a control input and the twilight function is linked to the same channel, the twilight function is ignored.

If an alarm input is used as switch input, it must be masked in all alarm masks.

10.3 Behavior at start-up, exchange of switch program file

After starting up the DTS 480x, or after changing the program file, it can take up to 2 min until the switch states to the channel relay are correct.

The max. number of signal commands is limited to 15 per minute.

Important:

© MOBATIME 91 / 120 800652.11

PC - Terminal Connection:

Type of connector: Sub-D 9p connector (male)

Interface: RS232

Baud rate:

Data Bits:

38400 Bauds

8

Parity: no

Stop Bit: 1

Flow control: no

Cable DTS 480x – PC: Crossed cable, female – female connectors (null modem)

(DTE-DTE) Max. length of the connection 3m

Verbindungen zwischen Buchse 1 (SUB-D 9 / 1) and Buchse 2 (SUB-D 9 / 2)

SUB-D 9 / 1 SUB-D 9 / 2

Receive Data *

Transmit Data *

2

3

3

2

Transmit Data

Receive Data

Data Terminal Ready

System Ground *

Data Set Ready & Carrier Detect

Request to Send

Clear to Send

* At least needed connections.

4

5

1 & 6

7

8

1 & 6

5

4

8

7

Data Set Ready & Carrier Detect

System Ground

Data Terminal Ready

Clear to Send

Request to Send

LAN Connection:

Use only shielded cables!

USB Connection:

Important:

Only permitted for the operations with a USB stick!

© MOBATIME 92 / 120 800652.11

A.2 Connections (rear view) DTS 4801.masterclock

!

DTS 4801 connections

For technical data see in Appendix “I Technical data“

Clamp Connection Description

1

2

L Mains connection phase Mains power input with rubber connector

Mains connection earth connection

Break point: by disconnecting the rubber connector

DC in power supply +

DC in power supply GND

Input for external DC supply

Ground

Connection to DTS extension:

Connection length max. 0.5m.

Do only connections when power is off.

4 RS232 RXD*

5 GND

6

7

8

9

11

RS485 A

/RS485 B

Common +

Alarm input 1

Alarm input 2

Output for serial telegrams

Connection length max. 30m

Input for serial telegrams

Output for RS 485 slave clock line / serial telegrams

Output for RS 485 slave clock line / serial telegrams

Alarm inputs:

18-36VDC, max. 6mA current consumption, close contact.

Contact closed  no alarm.

Length of connection max. 30m.

13 Alarm input 3

15

16

17

18

19

20

21

22

23

24

25

26

Alarm input 4

DCF input +

DCF input -

DCF output +

DCF output -

Slave clock line a

Slave clock line b

IRIG a

IRIG b

DC output +

DC output GND

Alarm relay

DCF input e.g. for the connection of a GPS 4500 or DCF receiver with current loop output.

I

DCF or pulse output, current loop passive, Umax=30VDC, on

= 10..15mA, I off

< 1mA @20VDC

Output for MOBALine, impulse line or DCF active line

Output for MOBALine, impulse line or DCF active line

Output for IRIG-B (Option)

Output for IRIG-B (Option)

DC output for GPS 4500 or RS 485 slave clocks

28 VDC, max. 400 mA

Alarm Kontakt, öffnet bei Alarm-

Load: 30 W (60 VDC or 1A) or 60 VA (30 VAC or 1A)

* At the moment only partly available.

© MOBATIME 93 / 120 800652.11

A.3 Connections (rear view) DTS 4802.masterclock

DTS 4802 connections

For technical data see in Appendix “I Technical data“

Clamp Connection

L

Description

Mains connection phase Mains power input with rubber connector

Mains connection earth

Break point: by disconnecting the rubber connector

!

1

2

4 RS232 RXD*

5 GND

6 NC

7 NC

8

9

Common +

Alarm input 1

11

DC in power supply +

DC in power supply GND

Input for external DC supply

Ground

Connection to DTS extension:

Connection length max. 0.5m.

Only plug in connections when the power is off.

Output for serial telegrams

Connection length max. 30m

Input for serial telegrams

Alarm input 2

Alarm inputs:

18-36VDC, max. 6mA current consumption, close contact.

Contact closed  no alarm.

Length of connection max. 30m.

13 Alarm input 3

15

16

17

18

19

20

21

22

23

24

25

26

Alarm input 4

DCF input +

DCF input -

DCF output +

DCF output -

Slave clock line a 1

Slave clock line b 1

Slave clock line a 2

Slave clock line b 2

DC output +

DC output GND

Alarm relay

DCF input e.g. for the connection of a GPS 4500 or DCF receiver with current loop output.

DCF or pulse output, current loop passive, Umax=30VDC,

I on

= 10..15mA, I off

< 1mA @20VDC

Output for MOBALine, impulse line 1 or DCF active line 1




DC output for GPS 4500 or RS 485 slave clocks

28 VDC, max. 400 mA

Alarm Kontakt, öffnet bei Alarm-

Load: 30 W (60 VDC or 1A) or 60 VA (30 VAC or 1A)

* At the moment only partly available.

© MOBATIME 94 / 120 800652.11

A.4 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 out spring terminal with operation tool:

2 operation tools are delivered with the accessory bag.

A.5 Connection of GPS 4500, DCF 450 / 4500 or GNSS 3000

white

Connection of DCF and

GPS receiver

DCF receiver

GPS 4500 brown yellow green

GNSS 3000 according to manual Bx-800813 chap. 9.2 Connection schematics DCF current loop

© MOBATIME 95 / 120 800652.11

B Time Zone Table

Time zone entries in the standard season table (version 10.0).

Time zone

00

06

08

City / State

UTC (GMT),

Monrovia, Casablanca

01 London, Dublin,

Edinburgh, Lisbon

02

Brussels, Amsterdam,

Berlin, Bern,

Copenhagen, Madrid,

Oslo, Paris, Rome,

Stockholm, Vienna,

Belgrade, Bratislava,

Budapest, Ljubljana,

Prague, Sarajevo,

Warsaw, Zagreb

03 Athens, Istanbul, Helsinki,

Riga, Tallinn, Sofia,

Vilnius

04

05

Bucharest, Romania

Cairo, Pretoria, Harare

Amman

UTC

Offset

DST

Change

Standard

0 No

→ DST

DST

→ Standard

0

+1

+2

Yes

Yes

Yes

Last Sun. Mar. (01:00)



+2

+2

Yes

No


+2 Yes Last Thu. Mar. (23:59)

+3 No

Last Sun. Oct. (02:00)



09

Kuwait City, Minsk,

Kaliningrad

Praia, Cape Verde -1 No


Last Fri. Oct. (01:00)

11 +4 No Abu Dhabi, Muscat,

Tbilisi, Moscow, St.

Petersburg, Volgograd,

Samara

13

14

-8 No

+5 No

15

16

17

18

19

Adamstown (Pitcairn Is.)

Tashkent, Islamabad,

Karachi

Mumbai, Calcutta,

Madras,

New Delhi, Colombo

Astana, Thimphu, Dhaka,

Yekaterinburg

Bangkok, Hanoi, Jakarta,

Novosibirsk

Beijing, Chongqing, Hong

Kong, Singapore, Taipei,

Urumqi, Krasnoyarsk

Tokyo, Osaka, Sapporo,

Seoul, Irkutsk

+5.5 No

+6 No

+7 No

+8 No

+9 No

21 South Australia: Adelaide +9.5

22 Northern Territory: Darwin +9.5

23

Yes

No

1 st

+10 No

Sun. Oct (02:00)

24

Brisbane, Guam, Port

Moresby, Yakutsk

Sydney, Canberra,

Melbourne, Tasmania:

Hobart

+10 Yes Sun. Oct. (02.00)

1 st

Sun. Apr. (03:00)

1 st

Sun. Apr. (03:00)

© MOBATIME 96 / 120 800652.11

27

28

29

Honiara (Solomon Is.),

Noumea (New

Caledonia), Vladivostok

Auckland, Wellington

Majuro (Marshall Is.),

Magadan, Anadyr

Azores

+11 No

+12 Yes Last Sun. Sep. (02:00)

+12 No

1 st

Sun. Apr. (03:00)

30 -1 Yes Last Sun. Mar. (00:00)

34 Newfoundland, Yes 2 nd

Sun. Mar. (02:00)

35 Atlantic Time (Canada) -4 Yes 2 nd

Sun. Mar. (02:00)

42 Denver, Mountain Time -7 Yes 2 nd

Sun. Mar. (02:00)

43 Los Angeles, Pacific Yes 2 nd

Sun. Mar. (02:00)

44 Anchorage, Alaska (US) -9 Yes 2 nd

Sun. Mar. (02:00)

45 Honolulu, Hawaii (US) -10 No

46

47

48

Midway Islands (US)

Mexico City, Mexico

Adak (Aleutian Is.)

-11

-6

-10

No

Yes

Yes

1 st

Sun. Apr. (02:00)

2 nd

Sun. Mar. (02:00)


3 rd

Sun. Feb. (00:00)

1 st

Sun. Nov. (02:00)

1 st

Sun. Nov. (02:00)

1 st

Sun. Nov. (02:00)

37

38

Bogota, Lima, Quito

New York, Eastern Time

(US & Canada)

-5 No

-5 Yes Sun. Mar. (02:00)

39 Chicago, Central Time

(US & Canada)

-6 Yes Sun. Mar. (02:00)

40 Tegucigalpa, No

54 Scoresbysund, Greenland

55 Nuuk, Greenland

-1

-3

Yes

Yes


Last Sat. Mar. (22:00)

2 nd

Sun. Mar. (02:00)

57 Western Australia: Perth +8 No

59

61

62

CET standard time

Chile, Easter Island

Baku

+1

-6

+4

No

Yes

Yes

2 nd

Sat. Oct. (22:00)


1 st

Sun. Nov. (02:00)

1 st

Sun. Nov. (02:00)

1 st

Sun. Nov. (02:00)

1 st

Sun. Nov. (02:00)


1 st

Sun. Nov. (02:00)


Last Sat. Oct. (23:00)

1 st

Sun. Nov. (02:00)

2 nd

Sun. Mar. (00:00)

2 nd

Sat. Mar. (22:00)


In countries where the DST switch date changes annually (e.g. Iran, Israel), the time zone has to be defined manually in the user time zone table (entries 80 – 99).

Legend:

UTC:

DST:

DST Change:

Standard

 DST:

DST

 Standard:

Example:

2 nd

last Sun. Mar. (02:00)

Universal Time Coordinate, equivalent to GMT

Daylight Saving Time

Daylight Saving Time changeover

Time change from Standard time (Winter time) to Summer time

Time change from Summer time to Standard time (Winter time)

Switch over on the penultimate Sunday in March at 02.00 hours local time.

Important:

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 97 / 120 800652.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 MOBA-NMS or any other Moser-Baer AG software such as, e.g. ETCW. If not changed using MOBA-NMS, it must be updated in accordance with the update instructions (chapter “7.3 Updating applications and configuration via FTP" or 7.5“ Updating applications or configurations via USB)

The file names mbsn.tbl and usersn.tbl must be written in small letters.

Important:

© MOBATIME 98 / 120 800652.11

C.1 Alarms

6

7

4

5

1

2

3

Number Error message

0 Alarm input 1

Alarm input 2

Alarm input 3

Alarm input 4

8

9

10

11

Error bit4

DTS restart

5V failed

Supply voltage too low

Description / Action

Check device on input 1




Not used

DTS 480x has been restarted, no action required

Hardware error  Support

Check DC voltage (DC in).

Line 1 current too high

Line 1 wrong time zone

Check MOBALine / Impulse line / DCF active line.

Alarm disappears only, if error is removed.

Check time zone setting in (MOBALine / Impulse line / DCF active line)

Wrong time zone DCF out Check time zone setting in (DCF- / pulse output)

12

13

14

15

16

17

18

19

20

Wrong time zone RS485 Check time zone setting in (RS485 output / serial telegrams)

Error IRIG output

Telegram file invalid

Check IRIG line.

Check that the line has been configured to MOBALine. (An impulse line is not started with a plugged in IF 488 option)

Also occurs when restarting the DTS 4801.

(Only for the DTS 4801 with IRIG option)

Check telegram file:

The file name has more than 8 characters or the file type is TEL,

Tel or tel; or syntax error in telegram file.

Swtich program file invalid

Check switch program file:

The file name has more than 8 characters or the file type is not

PRG, Prg or prg.

Wrong time zone sw. prog. Check time zone configuration switch function.

Failure time source Str

Failure time source TO

No valid time

Stratum of the current time source (DCF/GPS/NTP or internal time, in case of time source falure) too high  Check time source.

Can also occur shortly after restart (approx. 10min) for a short time.

 synch LED off

No time information from the source (GPS/DCF) for more than the timeout time configured  check time source.

Configuration see chapter 6.5.13, menu 4: "Alarm delay for failure of the source”

Set time manually, or configure, and/or check the time source.

The RTC or the manually set time appears after restart without time information from the source.

NTP Synch lost

Error bit20

Synchronization lost. Check time source (DCF or NTP) and settings

Not used

NTP error  Check NTP configuration.

As long as there is no DCF/GPS source: Set an NTP source

(even if only one is available) to “prefer“ (preferred source).

Can also occur when reconfiguring time sources or time settings.

After restarting the DTS 480x (< 30 min) the alarm can also occur.

© MOBATIME 99 / 120 800652.11

22

23

24

25

26

27

28

29

30

31

32-62

Wrong time zone DCF in Check time zone settings (time source).

Syn only diff too large Check synchronization and source

No mail server

SNMP not working

Check e-mail configuration.

Observe file mailerror.txt in /ram/ for error correction.

Check SNMP and trap configuration.

Error bit26

Error bit27

Linie 2 current too high

Line 2 wrong time zone

Error bit30

Error bit31

Not used

Not used

Check MOBALine / Impulse line / DCF active line.

Alarm disappears only, if alarm is removed.

(Only active with DTS 4802)

Check time zone setting in (MOBALine / Impulse line)


Not used

Not used

Error device 1-31

RS485 line: Device error  for detailed error description see chapter 6.5.8.


© MOBATIME 100 / 120 800652.11

D Troubleshooting

# Error / Indication: Possible case / Solution

1 sync LED is flashing:

2 Reception problem with

DCF/GPS:

DCF / GPS time source does not receive time –> 2

In menu 1 Status –> 4 Source check, if DCF seconds-counter is counting up continuously from 0 – 59 (corresponding to the current second, value is updated about every 3 seconds.

When counter is wrong  check receiver and cabling.

Check "DCF In" LED on backside of the DTS masterclock.

The local time source DCF/GPS or local has to be configured, otherwise NTP cannot set the time.

3 No NTP time, despite of manual time setting  sync LED is off!

4 General time reception problem If the time difference between DTS 480x.masterclock and the time source (NTP or DCF) is large (> 5 min), the NTP time synchronization may last quite long (> 30 min).

To solve the problem, set the time manually. all the time.

Check network configuration, Hostname has to be configured and

Gateway has to be set (if no Gateway is available in the network, the own IP address of the DTS masterclock can be used as Gateway).

No connection to the network. Check cabling. 6 LAN LED (left side) is flashing orange.

7 Opening the menu via Telnet is not possible or

DTS 480x.masterclock is not or no longer reachable via network.

Check network settings in menu 2 Configuration –> 5 Network (only possible with serial connection):

- IP-Address, Subnet mask and Gateway must be set correctly

- Interface should be set to Auto

- Check connection with "Ping"

- When earlier the menu was not correctly exited (e.g. LAN cable removed), the menu can be blocked up to 15 minutes.

8 Update of the system software. The system software can be updated by using FTP client software,

MOBA-NMS or via a USB stick (see chapter 7 Updates).

Your service office will advise you of the benefits and necessity of updates. The firmware file needed can be obtained from that office.

9 Information required to contact your MOBATIME service.

Device type, part number, production number and serial number:

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/.

To copy this files use FTP, e.g. Windows Explorer with ftp://[IP address], see chapter 7.6 or copy file to a USB stick (chapter 6.6).

If the log files cannot be copied, read out the current software version:

The software versions can be queried in the menu

1 STATUS/9 Software Versions

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, etc.

© MOBATIME 101 / 120 800652.11

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.

© MOBATIME 102 / 120 800652.11

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: parity none stopp byte

7 data bits

odd/even

1 2 1 2 none

8 data bits

odd/even

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

4800 bit/s

3.75

1.88

4.17

2.08

4.17

2.08

4.58

2.29

4.17

2.08

4.58

2.29

4.58

2.29

5.00

2.50

9600 bit/s

19200 bit/s

38400 bit/s

0.94

1.04

1.04

1.15

1.04

1.15

1.15

1.25

0.47

0.52

0.52

0.57

0.52

0.57

0.57

0.63

0.23

0.26

0.26

0.29

0.26

0.29

0.29

0.31

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.

© MOBATIME 103 / 120 800652.11

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)

;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)

© MOBATIME 104 / 120 800652.11

;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!

;--------------------------------------------------------------------

;-- 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!

;--------------------------------------------------------------------

© MOBATIME 105 / 120 800652.11

;-- 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 1

;MAX VALUE+STEP corresponds to the byte value for 2

;MAX VALUE+2*STEP corresponds to the byte value for 3 ...

;

;Example: Stratum 1 = A

; Stratum 2 = B

; Stratum 3 = C

; ...

;

; !TQ!1!1!

;--------------------------------------------------------------------

;-- 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.

;--------------------------------------------------------------------

;=====================================================================

;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




;--------------------------------------------------------------------

© MOBATIME 106 / 120 800652.11

;-- 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 107 / 120 800652.11

F Option IRIG-B: IF 488 Configuration

Generates a time synchronous DCF-FSK, or IRIG-B,or IRIG-E code telegram for automatic time transfer to external time systems from the MOBALine-Code of the DTS 4801. With the integrated DIP switch, 7 different time code formats can be selected. The alarm contact is monitored by the DTS 4801.

(DTS 4801 IRIG-B: Art. No: 203495)

Output code format:

With DIP switch 1 to 4 "MODE" is configurable:

Code according to data sheet

DCF-FSK:

IRIG-B 072

12 Std.-Format

Technical specifications:

Input: MOBALine

Output:

DCF-FSK:

IRIG-B:

IRIG-E:

600 Ohms galvanically separated:

Pulse 1kHz / pause 1,25 kHz

Modulation 1 kHz

Modulation 100 Hz

2Vp-p

2Vp-p / 0,66Vp-p

2Vp-p / 0,66Vp-p

© MOBATIME 108 / 120 800652.11

G 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

Busybox System environment

NTP NTP pure-ftp FTP server

OpenSSL SSL Lib.

1.0.21

0.9.8i

Free, partly BSD

BSD style

COPYRIGHT

COPYING

COPYING

LICENSE

LICENCE

LICENSE dropbear SSH server 0.52 MIT style:

Free, party BSD wide-dhcpv6 DHCPv6 20080615 Free flex Flex Lib. 2.5.4e BSD adapted

COPYRIGHT

COPYING

README

-

The complete license descriptions can be referred to in the file indicated in the respective original source code on the corresponding project page.

Licence text GPL, BSD and MIT:

GPL version 2: http://www.gnu.org/licenses/gpl-2.0.html

BSD: http://www.opensource.org/licenses/bsd-license.php

MIT http://www.opensource.org/licenses/with-license.php

The source code of the open source projects running under GPL can be requested from Moser-Baer

AG ([email protected]). Handling costs will be charged!

© MOBATIME 109 / 120 800652.11

© MOBATIME

Low voltage detection

Ulogic power

DCF in

Current

Signal

Alarm

IRIG Alarm

Current

Signal

Alarm

=

=

Ubat

=

~

IF 488

(optional)

230VAC

24 VDC (in)

24 VDC (out)

Ethernet

10/100Mbit

USB Host

DCF in

DCF / pulse out

MOBALine /

Impulse line 1

IRIG

(only DTS 4801)

MOBALine /

Impulse line 2

(only DTS 4802)

Alarm 1 in

Alarm 2 in

Alarm 3 in

Alarm 4 in sync

RTC alarm

110 / 120

RS 232

2 RXD

8 CTS

3 TXD

7 RTS

6 DSR

1 DCD

4

5

DTR

GND

Terminal

RS232 RXD

RS232 TXD

RS232 telegram

RS485 A

/RS485 B

GND

RS485 clock line

(only DTS 4801)

Alarm

800652.11

Dimensions

Weight

19“ Rack, 1HE x 28TE (H x B x T [mm]) = 483 x 44 x 125 approx. 1.35 kg

Ambient temperature -5 to 50ºC, 10-90% relative humidity, without condensation

Operation Serial r Telnet/SSH as well as MOBA-NMS (via LAN)

In addition, operation is also possible with SNMP.

Accuracy GPS (DCF input) to NTP server:

DCF 77 radio receiver to NTP server:

NTP client to NTP server:

GPS (DCF input) or NTP client to clock line: typical < +/- 0.5ms typical < +/- 5ms

1) typical < +/- 0.5ms typical < +/- 0.5ms +

1)

accuracy of the clock line

If necessary the DCF source has to be adjusted with an offset

Important:

NTP reception (DTS 480x as client and / 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. Requirement for NTP accuracy: Poll interval: minimum 3, maximum 6.

Time keeping (internal) After at least 24 hours synchronization from the time source:

< +/- 0.1 sec. / day (< 1ppm), measured over 24 h, at 20°C +/- 5°C.

During power break (based on internal RTC):

< 5 ppm, but with jitter of +/- 15 ms, measured over 24 h, at 20°C +/- 5°C.

After a power failure the RTC time is available during at least 5 days

(RTC buffered through a SuperCAP).

Time server NTP V4

SNTP

TIME

DAYTIME

(fully V3 compatible), (UDP), RFC 1305 (Port 123)

NTP Authentication with MD5 Key / Autokey

(UDP), RFC 2030 (Port 123)

(TCP/UDP), RFC 868 (Port 37)

(TCP/UDP), RFC 867 (Port 13)

Max. number of NTP and SNTP client requests: typical 250 requests / sec.

(e.g. request of clients once every 60 sec  15'000 clients possible)

MTC-CAN-protocol for the communication with MTC Module CAN

NTP Mode Server, Peer, Broadcast, Multicast

NTP-

slave clock lines 1 line with up to 15 different time zone entries.

Communication through multicast or on IP request:

- RFC 3376: Internet Group Management Protocol, Version 3

- RFC 1112: Host extensions for IP multicasting

- RFC 4601: Protocol Independent Multicast - Sparse Mode (PIM-SM)

- RFC 3973: Protocol Independent Multicast - Dense Mode (PIM-DM)

Time zones (see App. B) Up to 80 predefined, 20 programmable entries (PC Software Tool)

Network interface 10BaseT / 100BaseTX (IEEE 802.3)

Data transmission rate: Auto-negotiation / manual

IP Configuration

Only shielded cable is allowed.

DHCP, Static IP, IPv4, IPv6

© MOBATIME 111 / 120 800652.11

Netzwork services NTP

SNTP

TIME

DAYTIME

Telnet

SSH

SCP

SFTP

FTP

SNMP

SMTP

DHCP

DNS

UDP, Port 123

UDP, Port 123

TCP/UDP, Port 37

TCP/UDP, Port 13

TCP, Port 23

TCP, Port 22

über SSH

über SSH

TCP, Port 21

UDP, Port 161 see timeserver see timeserver see timeserver see timeserver operation operation update update update operation

UDP, Port selectable (162) alarm notification, see SNMP

TCP, Port selectable (25) alarm mail see E-Mail

UDP, Port 68

TCP/UDP, Port 53 dyn. address allocation (client) address resolution (client)

SNMP

E-Mail

Serial interface

(front side)

Serial interface

(back side)

USB plug

DCF Input

V1, V2c, V3 with MD5 for authentication and DES for encryption (privacy).

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“

D-Sub 9 (male): (RS232, 38400, 8, n, 1, no flow control)

Cable length max. 3 m.

Alternatively to RS485 clock line

RS232 or RS485 (RS485 only in DTS 4801)

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), cable length max. 3 m

The description of the telegram functions is provided in Appendix E.

NMEA 0183 without additional synch. pulse:

ZDA telegram, 4800 bauds, 8, 1, none

USB Host for USB stick

DCF77 or DCF from GPS receiver (GPS 4500), current loop

Alarm inputs

Nominal 28 VDC, max. 32mA, response threshold 8mA

4 alarm inputs are available for the monitoring of external devices or as switch input for switch channels (daylight sensor)

18 – 36 VDC, max. 6 mA, close contact.

External contact closed  no alarm.

Cable length max. 30 m (not in the 3 m range of a catenary wire (railway)).

MOBALine output Alternatively to the impulse clock line or DCF active line

DTS 4801.masterclock: 1 line

DTS 4802.masterclock: 2 lines: max. current = sum of both lines

Current: up to 700 mA eff. (total)

Voltage:

Line modes: 10 sec.-, ½ min.- or 1 min. steps

Max. time deviation against internal time. +/- 10 ms

MOBALine with switching function, switching function for clock illumination and World time function available.

At least 28 VDC required

© MOBATIME 112 / 120 800652.11

Impulse line output

DCF active line

Alternatively to the MOBALine clock line or DCF active line



Current:

Voltage:

Line modes:

Voltage:

Line modes: up to 1000 mA impulse current (total)

24 VDC (polarized) (depending on power supply)

1 min., ½ -min., 1/5-min., 1/8-min., 1 sec

Impulse length: 200 – 30'000 ms, approx. 50 ms resolution

Pause length: 200 – 30'000 ms, approx. 50 ms resolution

Acceleration modes: 12 h, 24 h, 1 week

Max. time deviation against internal time: +/- 1 ms

At least 23.5 VDC power supply required

Alternatively to the MOBALine clock line or impusle clock line



Current: up to 1000 mA impulse current (total)

24 VDC (polarized) (depending on power supply)

See diagramm in chapter 6.5.5.

Max. time deviation (pulse start) against internal time: +/- 1 ms

At least 23.5 VDC power supply required

IRIG-B output (option) With built in IF 488 interface. The line has to be run in MOBALine mode.

(Only DTS 4801 IRIG-B: Art. Nr.: 203495).


RS 485 line output

(Only DTS 4801).

Alternatively to serial telegrams

Number of monitored clocks: max. 31


Communication RS485, 19200, 8, n, 1, no flow control,

MOBA-RS485-protocol

DCF / pulse output DCF time code or pulse output selectable.

Passive current loop

Umax = 30 VDC, I on

= 10..15 mA, I off

< 1 mA @20VDC

Cable length max. 30 m (not in the 3 m range of a catenary wire (railway)).

DCF output:

Pulse mode:

Pulse length: time zone selectable second, minute, hour, user defined interval: 1-3600sec.

20 – 500 ms, jitter pulse length: +/- 2 ms

Max. time deviation against internal time: +/- 1 ms, jitter first pulse edge < 0.5 ms

Alarm contact

Alarm reporting /

Error messages

Opening relay contact (alarm active  contact open).

Switching load: 30 W (60 VDC or 1 A)

or 60 VA (30 VAC or 1 A)

Alarm contact

E-Mail see Alarm contact

Display

DC power supply

Mains power supply

Power supply output

2 lines with up to 16 characters for the display of status information.

24 - 28 VDC / 1.5 A (28 V required for MOBALine)

90 – 240 VAC / 50 - 60 Hz / max. 30 VA

Typical: < 5 VA @ 230 VAC (without external load)

Nominal 28 VDC, max. 400 mA

© MOBATIME 113 / 120 800652.11

J Index

DTS Extension 93, 94

A

E

AFNOR 29

Alarm Configuration

Alarm input

54

43, 91

E-Mail 56

E-Mail – techn. data

Error messages

112

99

Alarm input – techn. data

Alarm list

Alarm mask

Alarm recording

112

99

43, 54, 55, 56, 58, 65, 91

22, 55

F

Factory settings

G

70

Alarm relay

Alarm relay – techn. data

Alarm status

Authentication

54, 93, 94

113

14, 22, 55

57, 67, 80

Firmware 14,

Fix stratum

Front connections

79

92

FTP 74,

FTP-Tools 74

Autoconf 63

Autokey 50, 51, 82

B

GPS 4500 – connection 95

Baudrate 18

Baudrate – PC connection 92

H

Baudrate: 34

Block diagram

Broadcast NTP

110

50

I

Impulse line

K

L

30

C

Cable – PC connection

CAN monitoring with MTC

Channel program

Channel relay

Channel relay after start-up

Connections – PC

Connections – rear view

Connections – Rear view

Control input

Control Key 51

Copyright 109

Correcting time manually

92

93

94

43, 91

52

IRIG-B 29

IRIG-B – IF 488

Community (SNMP) 83

Configuration 26

Configuration – save

Connection Table (to be filled-in)

Connections – Front

Connections – DCF & GPS

92

52

90

41

91

75

116

92

95

Interface 102

IPv4 62

IPv6 63

IPv6 – FTP connection

Key

Leap second

LED display front view

LED display rear view

Line current

Line time

Local time source

Login (Menu)

74

108

50, 51, 80

46, 80

13

13

22

22

Lines 27

Linux 18

79

17

D

M

Data bit

Daylight Saving Time

DC power supply

DCF active

DCF input

18, 34

97

93, 94, 113

31, 32

93, 94

Mains power supply

Mains supply

DAYTIME 80,

113

93, 94

Manual time set 53 mbs3-file 76

MD5 67,

Menu Login

Menu structure

17

19

DCF Ouput

DCF receiver – connection

33

95 MIB Files

MOBALine 28

MOBA-NMS 11

DHCPv6 63

Multicast address

DST 97

83

111

48

50

© MOBATIME 114 / 120 800652.11

Multicast with NTP time source

N

Network configuration

Network information

Network services

79

61

22

112

SNMP access configuration

SNMP configuration

SNMP operation

SNMP traps

SNMP user configuration

SNTP 80,

Software Update

NTP 80,

NTP as backup time source

NTP Authentication

NTP Autokey

NTP Broadcast

NTP Multicast

NTP server

NTP slave clocks

48, 78

51, 80

82

50

50

48

39, 111

Software version

Spring terminals

Status menu

T

68

58, 65

84

58, 84

67

71, 72

95

SSH 18,

Start-up 91

22

Stop bit

Sunrise time – calculated

Sunset time – calculated

18, 34

Stratum 24,

42

42

NTP symmetric keys

NTP time source

NTP time take-over

NTP Version

80

49

78

80

Switch function

Switch input

Switch program

Switch program – signal ntp.keys 51

NTP-Modus 111 ntpq 23

14, 22

41, 90

43, 91

41

90

O

Telegram file 34, 70, 76, 102

Operation (Menu)

Operation (SNMP)

Option IRIG-B

P

17

84

108

Telegram file – name

Telnet 18,

Terminal 17

Terminals 93, 94, 95

TIME 80,

77

Password 17

Password configuration

Time administration

Time handling

Time server

45

80, 111

Port

Privacy 67

Program file

Pulse output

Pulse Output

60

39, 56, 59

41, 42, 70, 76, 90

93, 94

33

Time servers in the Internet

Time status

Time zone

Time zone for displayed time

Time zone selection

103

78

25

47

24

96

60

69

R

Request Key

RS 485 line

51

36

Time zone server

Time zone table

Transmission time

RTC 78,

RTC (Real Time Clock) 77

39

96

102

Trap 58,

Troubleshooting 101

S

Trusted Key ttl (time to live)

Satellites 25

SCP 75,

SCP-Tools 75

51

50

Twilight 42,

Twilight function – priority 91

Season table

Serial connection

Serial interface – techn. data

Serial telegrams

96

18

112

34, 102

U

V

Update – Software

Update time zone table

USB

Service – Required Information

Set language

101

60

SFTP 11, 74, 112

SFTP-Tools 74

71, 72

98

70, 72, 73, 76

SNMP

SNMP – alarm notification

SNMP – alive notification

SNMP – notification

SNMP – variables

11, 83, 112

89

89

84

86

W

Week program

World time

World Time Function

90

29, 39

29

© MOBATIME 115 / 120 800652.11

K Connection Table (to be filled-in)

Example:

Line Type Designation

Line Type Designation

MBL MBL Slave clock line, main building west, 1

st

floor

© MOBATIME 116 / 120 800652.11

© MOBATIME 117 / 120 800652.11

© MOBATIME 118 / 120 800652.11

© MOBATIME 119 / 120 800652.11


No results