AdminManual TimeSynchronization

.
SPPA-T3000
Administrator Manual
Time Synchronization
2019-03-11
Unrestricted
2 c Siemens AG 2019. Unrestricted. All rights reserved.
CONTENTS
Contents
1 Introduction 7
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 Notational Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.5 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.6 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2 Time Server in SPPA-T3000 Networks 11

2.1 Implementation at SPPA-T3000 . . . . . . . . . . . . . . . . . . . . . 11
2.2 Buerk Mobatime Time Servers . . . . . . . . . . . . . . . . . . . . . . 12
2.3 Buerk Mobatime DTS4138S and DTS4148S . . . . . . . . . . . . . . 12
2.3.1 PTP by DTS4148S . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4 Buerk Mobatime DTS4130S . . . . . . . . . . . . . . . . . . . . . . . 15
2.5 Buerk Mobatime DTS4128 . . . . . . . . . . . . . . . . . . . . . . . . 16
2.6 Mounting DTS41xy to a SPPA-T3000 PRP Network provided by GPS 16
3 Initial Configuration of Buerk Mobatime Time Servers 19

3.1 Default Interface Settings after first Start-Up . . . . . . . . . . . . . . 19
3.2 Installation by using a USB Stick . . . . . . . . . . . . . . . . . . . . 19
3.2.1 Part1: Initial Network Configuration . . . . . . . . . . . . . . 20
3.2.2 Part2: Basic Configurations . . . . . . . . . . . . . . . . . . . 23
3.3 Access to the Time Server . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3.1 Telnet/SSH connection . . . . . . . . . . . . . . . . . . . . . . 29
3.3.2 Serial connection – for DTS4128 / DTS4130S only . . . . . . . 30
3.4 Adaptions of Site Specific Parameter . . . . . . . . . . . . . . . . . . 32
3.4.1 Login Authentication . . . . . . . . . . . . . . . . . . . . . . . 32
3.4.2 Network Settings DTS4128 / DTS4130S . . . . . . . . . . . . 33
3.4.3 Network Settings DTS4138S / DTS4148S . . . . . . . . . . . . 34
3.4.4 Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.4.5 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.5 Adaptions of Usage Specific Parameters . . . . . . . . . . . . . . . . . 39
3.5.1 Deactivation of Telnet . . . . . . . . . . . . . . . . . . . . . . 39
3.5.2 Redundant Power Supply . . . . . . . . . . . . . . . . . . . . 40
3.5.3 Time Source Type . . . . . . . . . . . . . . . . . . . . . . . . 41
3.5.4 Time Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.5.5 Redundant Operation of Time Servers . . . . . . . . . . . . . 43
3.5.6 DCF Output Lines . . . . . . . . . . . . . . . . . . . . . . . . 44
c Siemens AG 2019. Unrestricted. All rights reserved. 3

CONTENTS
3.5.7 LAN Port Configurations on the DTS4138S / DTS4148S . . . 45

3.5.8 PTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.5.9 SIMATIC PCS7 compatible mode . . . . . . . . . . . . . . . . 48
3.5.10 SIMATIC S5 compatible mode (SINEC mode) . . . . . . . . . 49
4 Usage of Network Components in the Time-Net 51

4.1 Store-and-Forward-Time . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.2 Network Switch for SIMATIC PCS7 Compatible Mode . . . . . . . . 52
4.3 Network Switch for PTP in the Automation Highway . . . . . . . . . 53
5 Appendix - Illustrations of Different Scenarios for HPT 59
6 Appendix - Basic Configurations provided on the USB Stick 67

6.1 dts4138_1.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.2 dts4148_1.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.3 dts4138_2.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6.4 dts4138_3.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
6.5 dts4148_3.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
6.6 dts4148_4.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
6.7 dts4148_5.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
7 Appendix - Migration SPPA-T2000 to SPPA-T3000 80

7.1 Migration with Buerk-Mobatime DTS4130S Time Server . . . . . . . 80
7.2 Migration with Buerk-Mobatime DTS4138S . . . . . . . . . . . . . . 81
8 Appendix - Basics of GPS Time Synchronization 82

8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
8.2 Position Calculation with GPS . . . . . . . . . . . . . . . . . . . . . . 83
8.3 Time Calculation with GPS . . . . . . . . . . . . . . . . . . . . . . . 85
8.4 Source of Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
9 Appendix - Time Synchronization in Ethernet Networks 87

9.1 Time Master in Ethernet Networks . . . . . . . . . . . . . . . . . . . 87
9.2 NTP Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . 87
9.3 PTP Time Synchronization (IEEE1588) . . . . . . . . . . . . . . . . 89
9.3.1 Correction Mechanisms . . . . . . . . . . . . . . . . . . . . . . 89
9.3.2 Clock Types under the PTP . . . . . . . . . . . . . . . . . . . 90
9.4 SIMATIC Time of Day Synchronization . . . . . . . . . . . . . . . . . 90
10 Appendix - HOPF Time Server - GPS Satellite Clock HOPF6842 91

CONTENTS
10.1 Hardware of HOPF6842 . . . . . . . . . . . . . . . . . . . . . . . . . 91

10.2 Installation and Setup of the GPS Satellite Clock . . . . . . . . . . . 92
10.2.1 Setup of the Fiber Optic Converter Board 7247 . . . . . . . . 92
10.2.2 Setup of the LAN Board 7271 . . . . . . . . . . . . . . . . . . 92
10.2.3 Setup of the LAN Board 7270 . . . . . . . . . . . . . . . . . . 93
10.2.4 Setup of the HOPF6842 . . . . . . . . . . . . . . . . . . . . . 93
10.2.5 Configuration of the LAN board 7271 via WEB Interface . . . 95
10.3 Connecting the HOPF6842 to the SPPA-T3000 System . . . . . . . . 99
10.4 Accuracy of HOPF6842 . . . . . . . . . . . . . . . . . . . . . . . . . . 99
10.5 Operation of the HOPF6842 . . . . . . . . . . . . . . . . . . . . . . . 100
10.6 Using LAN board 7270 during Commissioning Phase without Antenna100
10.6.1 Configuration of the LAN board during Operation without
Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
10.6.2 Connecting the Antenna after Operation without Antenna . . 101
11 Appendix - IEEE1588 (PTP) supported by SCALANCE Switches103

CONTENTS
Within this document cross-reference links are used.

If you are using Adobe Reader to read this document, we recommend that you
activate the Previous/Next View - buttons in the toolbar. That allows you to
jump back to the last reference you have clicked on, (similar to a common Internet
Browser).
To activate the buttons, follow the instructions below. Now your toolbar
should have these two additional arrows: View→Show/Hide→Toolbar Items→Page
Navigation→Previous View/Next View
Figure 1: Previous View / Next View buttons in Adobe reader toolbar

1 INTRODUCTION
1 Introduction
1.1 Scope
The main aspects of this document are:
• Installing advices of the Time Server hardware

• Information about default values at the first startup of the Time Server
• SPPA-T3000 specific configurations provided on a USB stick (not supported by
Time Servers without USB interface)
1.2 Purpose of the document
This document gives advices for initial configuration and basic usage of Time Servers
used for SPPA-T3000 networks.
The main focus is on Buerk Mobatime Time Servers. But also the discontinued
Time Server HOPF6842 is part of this document.
The document addresses both commissioning engineers and network administrators on
site.
Basically a Time Server is used to synchronize all clients connected to the Automation
Highway. The clients will be time synchronized depending on their supported protocol.
Starting with SPPA-T3000 Release 8.0, the following protocols for time synchronization
are available:
• NTP – Network Time Protocol

• PTP – Precision Time Protocol
• SIMATIC Protocol – PCS7 compatible mode
• SINEC Protocol for SIMATIC S5 (used for SPPA-T3000 Migration)
The pictures shown in Appendix 5 illustrate several scenarios. Initial information is

provided by the subsequent chapters.
1.3 Disclaimer
The content of this manual has been checked for agreement with the hardware and
software described. Since deviations cannot be precluded entirely, full agreement cannot

1 INTRODUCTION
be guaranteed. However, the data in this manual is reviewed regularly and any neces-
sary corrections are included in subsequent editions. Suggestions for improvement are
welcomed.
1.4 Notational Conventions
The following notational conventions are used in this manual:

Item Convention
Text in courier System settings or commands
#./script.sh Execute the script script.sh on a Linux system as the root
user or using a user with root privileges.
"Quotation marks" Names of chapters and terms that are being emphasized.
Pay particular attention to texts marked with this symbol.
Additional notes and tips.
Table 1: Notational conventions
—————————————————————————-
1.5 References
1. RFC 1305 - NTP Protocol Specification, Version 3 (http://rfc.net/rfc1503.

html)
2. Buerk Mobatime DTS4148S.grandmaster / Mounting and Instruction Manual -
BK-801053.03
3. Buerk Mobatime DTS4138S.timeserver / Mounting and Instruction Manual - BK-
800870.06
4. Buerk Mobatime DTS4130S.timeserver / Instruction Manual - BK-800505.08
5. Buerk Mobatime DTS4128.timeserver / Instruction Manual - BE-800847.04
6. Buerk Mobatime Satellite Time Signal Receiver GPS4500 - TE-800348.12
Buerk Mobatime Satellite Time Signal Receiver GPS4500v2 - TE-801056.03
7. SCALANCE X-300 / X-400 – Configuration Manual 03/2016 - C79000-G8976-
C187-27
8. HOPF Elektronik GmbH : Technical Description GPS Satellite Clock 6842
9. HOPF Elektronik GmbH : Technical Description LAN Board 7270

1 INTRODUCTION
10. HOPF Elektronik GmbH : Technical Description Fiber Optic Converter Board 7247
11. HOPF Elektronik GmbH : Technical Description Standard Frequency Module 7530
12. HOPF Elektronik GmbH : Technical Description Master Clock Board 7406
13. HOPF Elektronik GmbH : Technical Description LAN Board 7271
Note:
The latest leaflets, manuals and software for Buerk Mobatime Time Server are provided
under the subsequent download area:
http://www.mobatime.com/customer-area/product-resources/timeserver.
html
1.6 Abbreviations
AS: Automation Server

DTS: Distributed Time System
FO: Fiber Optic
FTP: File Transfer Protocol
GPS: Global Positioning System
GUI: Graphical User Interface
HPT: High Precision Time Synchronization
HRP: High Speed Redundancy Protocol
HSR: High-availability Seamless Redundancy
IEEE: Institute of Electrical and Electronics Engineers
IRIG-B: Inter Range Instrumentation Group (Timecode 100p/sec)
IEC: International Electrotechnical Commission
LAN: Local Area Network
NTP: Network Time Protocol
PTP: Precision Time Protocol
PRP: Parallel Redundancy Protocol

1 INTRODUCTION
SFTP: SSH File Transfer Protocol

SNMP: Simple Network Protocol
SOE: Sequence Of Event
SSH: Secure Shell
WBM: Web Based Management

2 TIME SERVER IN SPPA-T3000 NETWORKS
2 Time Server in SPPA-T3000 Networks
2.1 Implementation at SPPA-T3000
A sample configuration for a SPPA-T3000-based solution is given in Figure 2.
Figure 2: Sample SPPA-T3000 Network
In SPPA-T3000 the following components have to be time-synchronized:
• Thin Clients connected to the Application Highway

• Application Server(s) connected to the Application Highway and the Automation
Highway
• Automation Server(s) connected to the Automation Highway
• Field / IO Devices connected via Profibus to an Automation Server

The first Application Server and all Automation Servers will be configured to become
synchronized to the Time Server(s). At the Application Highway the Thin Clients and
all optional additional Application Servers will be configured to become synchronized to
the first Application Server.
If high accuracy in time synchronization is requested on the Automation Highway, the
Precision Time Protocol (PTP) will be used for devices which support this protocol.
The SIMATIC PCS7 protocol will be used for high accuracy to synchronize the AS-S7
components. As shown in Figure 49 for example the Time Servers and the AS-S7 CPUs
are to be connected via a separate network (TIME-NET) that is used exclusively for the
time synchronization.
At the Automation Servers e.g. AS3000 or CS3000 the NTP/PTP client implementa-
tion is responsible for the calculation of the accurate time on base of the time values
received from the Time Servers. Components below the Automation Server level, e.g.
an IEC61850 network, will be synchronized to the Automation Server.
In case of multi-unit configurations the Time Servers are directly connected to the re-
dundant Multi-Unit-Routers, see Figure 51.
2.2 Buerk Mobatime Time Servers
For time synchronization in SPPA-T3000, network Time Servers manufactured by Buerk

Mobatime are used. This document is related on the different types of these Time
Servers.
In comparison to the Time Servers DTS4128, DTS4130S and DTS4138S, the DTS4148S
is a PTP grandmaster clock according to IEEE 1588-2008v2 for the synchronization of
PTP clients (see also Appendix 9.3).
The devices are designed for 19" racks and intended to be installed in a 19" cabinet.
All Time Servers read the time signal from DCF sources (e.g. DCF 4500 antenna) or
GPS sources (e.g. GPS 4500 antenna). The GPS antenna will be focused here.
Connected via LAN port to the SPPA-T3000 Automation Highway the Time Servers
provide different protocols for all SPPA-T3000 clients. To achieve redundant operation,
respectively two Time Servers are interconnected via fiber optical link.
2.3 Buerk Mobatime DTS4138S and DTS4148S
Both Time Servers are Siemens specific: They are able to provide SIMATIC time signal:
The SIMATIC S5 (SINEC mode) and the SIMATIC PCS7 compatible mode. That is

what the “S” stands for. Exemplarily for the here described two Time Servers, the front
of the DTS4138S is shown in Figure 3.
Figure 3: Buerk Mobatime DTS4138S Front View
Both Time Servers are equipped with:
• 2 LAN interfaces RJ45, 10/100Mbit Ethernet for operation in two independent net-
works Remote operation control: telnet, SSH, FTP, SFTP Network services: PTP
(only DTS4148), NTP, SNTP, SINEC, TIME, DATE, DAYTIME, SNMP (TRAPS,
Get, Put)
• IRIG/AFNOR line analog and digital (current loop and RS422) output
• Alarm Relay
• Serial interface for the output of time telegrams
• Output line for technical pulses (pulse/frequency/DCF)
• Optical link to connect a second DTS for redundant operation, mini GBIC plug-in
• USB port for software update, data download, backup and restore functions
• DCF in electrical
• Input for redundant power supply, 2x DC in, 24 VDC
The “Display Button” is used to scroll through the following information, shown on the
display:
• Time, date
• Current time source
• Stratum of the DTS

• Software version
• IPv4 address LAN 1
• Alarm summary
• Current alarms
Further information is provided in [2] and [3].
2.3.1 PTP by DTS4148S
The DTS4148S supports IEEE1588v2 (not IEEE1588v1) and provides the correction
mechanisms "end-to-end" and "peer-to-peer". In SPPA-T3000 the used mechanism is
"end-to-end".
If both LAN interfaces of the DTS4148S are used with PTP, the Time Server becomes
a “Boundary Clock” with two master ports equally according to IEEE 1588.
For further information about PTP in general check Appendix 9.3 of this document.
Detailed information about PTP used by the DTS4148S Time Server is provided by the
manufacturers’ manual [2].
The clients use the BMC (Best Master Clock algorithm) to negotiate their priority to
the Time Servers.
The configuration of the PTP feature on clients, e.g. AS3000, CS3000, if necessary, is
not part of this document.

2.4 Buerk Mobatime DTS4130S
Figure 4: Buerk Mobatime DTS 4130S Front View
The Time Server DTS4130S is equipped with:
• 1x Terminal Sub-D 9pin RS232 for local operation control

• 1 x LAN interface RJ45, 10/100Mbit Ethernet Remote operation control: telnet,
SSH, FTP Network services: NTP, SNTP, SINEC, TIME, DATE, DAYTIME, SNMP
(TRAPS, Get, Put)
• DCF out, 2x optical BFOC connectors, 1x electrical
• DCF in 1x electrical
• Alarm Relay
• Input for redundant power supply, 1x mains power 85-265 VAC, 2x DC in, 24 VDC
Further information is provided in [4].

2.5 Buerk Mobatime DTS4128
Figure 5: Buerk Mobatime DTS 4128 Front View
The Time Server DTS4128 is equipped with:
• 1x Terminal Sub-D 9p RS232 for local operation control
• 1 x LAN interface RJ45, 10/100Mbit Ethernet Remote operation control: tel-

net, SSH, FTP Network services: NTP, SNTP, TIME, DATE, DAYTIME, SNMP
(TRAPS, Get, Put)
• DCF in / out, electrical
• Alarm Relay
• Input for power supply, DC in, 24 VDC
Further information is provided in [5].
2.6 Mounting DTS41xy to a SPPA-T3000 PRP Network provided by GPS
Note:
DTS41xy stands for DTS4128, DTS4130S, DTS4138S and DTS4148S. The same menu
and configuration steps are necessary for these four types of Time Servers.
Two DTS Time Servers with one or 2 independent antennas are used to synchronize all
SPPA-T3000 clients connected to the Automation Highway and to achieve the 1-fault
tolerant, redundant solution. If required, they can be connected to a PRP based network.
Both devices could have their own GPS receiver as shown in Figure 7. But usually both
Time Servers are connected via DCFMulti4 to one antenna as shown in Figure 6.

Between the Time Server and the antenna, an additional lightning protection box is
interconnected.
Redundancy with two Time Servers is realized via fiber optical link between the two
devices. A fiber optic cable and a GBIC module per device are necessary to interconnect
both Time Servers.
They are both configured for the redundant mode, but are basically equal. The mas-
ter/slave role of each Time Server is negotiated internally. The slave is always synchro-
nized to the master in operation. The slave supervises the system time on the basis
of the GPS antenna and generates an error message, if the time difference exceeds the
configurable value of n milliseconds.
For configuration information on redundancy see Chapter 3.5.5 for further information.
Additional equipment:
• GPS 4500 Satellite receiver

• DCFMulti4 (for the usage of only one antenna for both Time Servers)
• SP 4500 Lightning protection box (between Time Server and antenna)
• GBIC modules and optical cable for redundant operation
For detailed information how to mount the Time Servers, how to connect them with the
fiber optic cable and how to install the GPS antennas, please refer to the manufacturer’s
documentation [6].
Figure 6: Buerk Time Server in redundant configuration with one antenna, “Master” / “Slave”

Figure 7: Buerk Time Server in redundant configuration, “Master” / “Slave”

3 INITIAL CONFIGURATION OF BUERK MOBATIME TIME SERVERS
3 Initial Configuration of Buerk Mobatime Time Servers
This chapter describes the initial configuration of Buerk Mobatime Time Servers.
After the first start-up, the devices will come up with factory default parameters. The
complete list of all initial values is provided by the related Buerk manuals: i.e. [2], [3],
[4], [5].
The default configuration of all Time Servers needs to be changed for SPPA-T3000. Also
adaptions, depending on the usage of the Time Server in the network environment need
to be configured. The most comfortable and fastest procedure is to use pre prepared
configurations provided on a USB stick. This stick will be connected to the USB port
of the Time Server. Afterwards it is possible to copy the configuration from the USB
stick to the Time Server. This feature is available only for DTS4138S and DTS4148S
and will be shown in Chapter 3.2
The manual configuration of usage specific parameter of the Time Server by using SSH
is shown in Chapter 3.5.
Site specific changes are shown in Chapter 3.4. Therefore the devices will be accessed
via network (LAN). In case of DTS4128 and DTS4130S the serial interface is necessary
(only for initial configuration).
3.1 Default Interface Settings after first Start-Up
After the first start-up, the network services Telnet, SSH and FTP are activated for all
devices. All LAN1 ports are configured with DHCP by default.
In case of the DTS4138S and DTS4148S the default network configuration is as follows:
Item Configuration
IP address LAN1: dhcp
LAN2: 192.168.1.5
Network mask LAN1: dhcp
LAN2: 255.255.255.0
Gateway IP LAN1: dhcp
LAN2: 192.168.1.10
Table 2: Default network configuration DTS4138S / DTS4148S
3.2 Installation by using a USB Stick
The procedure described here is only available for DTS4138S and DTS4148S. A USB
stick that contains several files with basic configurations for SPPA-T3000 time synchro-

nization will be provided and delivered with each new Time Server. An overview is
provided in Table 3. These configurations contain usage and plant specific parameters.
The plant specific parameters, such as network settings, have to be adapted by the
operator, before the installation process.
The initial configuration of the Time Servers with USB stick is divided into two separate
parts:
With the first part the Time Server receives his plant specific network configuration.
In the second part the Time Server will be configured with one of the provided basic
configurations.
3.2.1 Part1: Initial Network Configuration
Preparation of the Network Configuration File:

For this part of the procedure the configuration file DTS4148NW.conf respectively
DTS4138NW.conf (file names are case sensitive!) in the root folder (\) of the USB
stick has to be used. It contains default network configurations for both LAN ports.
These default configurations feature DHCP switched off. Both LAN interfaces are con-
figured with IP addresses as shown in Figure 9.
Figure 8: DTS4138NW.conf; DTS4148NW.conf
By using a PC the configuration file needs to be edited on the USB stick. The network
settings have to be adapted as required by the plant network. Figure 9 shows an example.

Figure 9: Example: Plant Specific Network Adaptions on DTS4148NW.conf
If the setting of a parameter is not necessary e.g. the gateway for LAN 2 in Figure 9, it
just could be left out.
Note:
The default network settings of both LAN ports shown in Figure 9 also appear in all
configuration setups provided on USB stick.
Network Installation Procedure with the USB Stick:
The procedure is exemplarily shown for the DTS4148S.
Figure 10: DTS4148S Network Ports
• After the network file is edited as necessary by the plant, plug in the USB stick to
the USB interface of the time server. The display shows the following message:
Figure 11: USB plugged in message
• Press the “Display” button (see Figure 10) to accept the message and start the
copy process from the USB stick to the Time Server
• Now the network configuration parameters will be copied from the USB stick to the
Time Server

• When the regular time / date display reappears, the copy process is finished
• Press the “Display” button again to check the network parameters

If the IP configuration does not correspond to the desired, finish the procedure
regularly. Then check Note 1 and Note 2 below.
• The Time Server is now accessible by the installed IP configuration
• Unplug the USB stick
• End of the first part: Installation of plant specific network configuration
Note 1:
The USB procedure has to be done during the display shows the message in Figure 11.
As long as this message is displayed, the stick is subscribed to the Time Server
and must not be re-plugged again! Otherwise the Time Server will deactivate
the USB port!
To re-plug the stick, the display must show date and time first. Not till then the USB
stick was recognized by the Time Server as being ejected. There is a timeout of approx.
1min.
To activate a deactivated USB port again, a restart of the Time Server is necessary.
This can be done by pressing the reset button between the LAN port(s). See Figure 10
Note 2:
If the IP configuration on the Time Server does not correspond to the desired, the
procedure has to be finished regularly anyway. Then the settings made in the config-
uration file DTS4148NW.conf respectively DTS4138NW.conf has to be checked
and corrected. The configuration will be set to “no info” by the DTS41xx, if the device
is not able to work with the settings found in the configuration file. The network
installation procedure could be repeated.
Note 3:
Not all parameters provided are required or fit to the settings of the network. For
example:
• if only one LAN interface is necessary, LAN1 has to be used.

3.2.2 Part2: Basic Configurations
Configurations Provided on the USB Stick:

The subsequent table gives an overview of the configuration files provided on the USB
stick. The columns 3 and 4 give the related file name if the configuration described in
column 2 is applicable for the appropriate Time Server.
No Configuration DTS4138S DTS4148S
1 LAN1: NTP dts4138_1.conf dts4148_1.conf
LAN2: NTP [6.1] [6.2]
2 LAN1: NTP dts4138_2.conf N/A
LAN2: SINEC [6.3]
3 LAN1: NTP dts4138_3.conf dts4148_3.conf
LAN2: SIMATIC PCS7 [6.4] [6.5]
4 LAN1: NTP N/A dts4148_4.conf
LAN2: PTP [6.6]
5 LAN1: NTP and PTP N/A dts4148_5.conf
LAN2: SIMATIC PCS7 [6.7]
Table 3: Basic Configuration Files on the USB Stick
The SPPA-T3000 Time Servers are always configured for
• redundant configuration, i.e. two Time Servers connected via DTSLINK

• redundant power supply
• GPS antenna for each Time Server
The plant specific values for
• IP addresses, subnet mask, gateway of each Time Server

• IP addresses for each redundancy partner
have to be adapted manually in the configuration file (see Chapter 3.2.2) before the
configuration will be copied to the Time Server.
Note:
These values are shown in the tables provided in Appendix 6. The tables contain only
the important values for SPPA-T3000. The network settings in the basic configuration
files must correspond to the settings in the initial network configuration file adapted in
Chapter 3.2.1 The following values have to be configured via SSH in the DTS4138S and
DTS4148S menu (see Chapter 3.4):

• Time Zone
• Login Password
Information about the basic configurations provided on the USB stick can also be found
in the readme.txt on the USB stick.
Note:
The complete list of all factory default values is listed in the corresponding Time Server
manual [2], [3], [4], [5].
Adaptions of Plant Specific Values in the Configuration File:

The basic configuration files are located on the USB stick in the folder:
\BasicConfigurations. Depending on the Time Server type to be configured and the
desired usage specific settings, one of the files has to be chosen and to be copied from
the directory \BasicConfigurations to the root folder (\) of the USB stick.
Note:
It is recommended to keep the original basic configuration file in the BasicConfigurations
folder for possible later usage.
The chosen configuration file needs to be renamed to follow the naming convention:
• dts4138.conf only for DTS4138S Time Server

• dts4148.conf only for DTS4148S Time Server
Figure 12: Copy and Rename the necessary Configuration File
Now the copied and renamed file has to be opened with a text editor e.g. notepad++.
The network settings for LAN1 [network0] and LAN2 [network1] has to be adapted
as required by the plant. Figure 13 shows the red marked parameters which have to

be changed plant specific. The IP address, subnet mask and gateway addess are just
examples.
Figure 13: Adaptions of the Network Settings in the Configuration File
The IP address of the redundancy partner has to be adapted too. Figure 14 shows an
example.

Figure 14: IP Address of the Redundant Time Server
When the adaption is complete, the configuration file must be saved.
Basic Configuration Installation Procedure with the USB Stick:
• After the configuration file is adapted as necessary for the plant: Plug in the USB
stick to the USB interface of the Time Server (see Figure 10). The display shows
the following message:
Figure 15: USB Plugged in Message
• As shown in Chapter 3.3.1 open a SSH session to the Time Server

• From the “MAIN SELECTION” window choose:
3 Maintenance -> 2 Update Software (USB) -> see Figure 16

Figure 16: Maintenance – Update Software
Then press ENTER and afterwards the Time Server copies the configuration file from
the USB stick and performs a restart with a short notice: “Update in progress” as
shown in Figure 17.

Figure 17: Maintenance Window - Update in Progress
This procedure takes up to a few minutes. During the booting procedure the Time
Server display is dark and empty.
After the restart the Time Server has taken over the parameters from the configuration
file. When the regular time / date display reappears the configuration of the Time
Server is finished.
Note:
The USB procedure has to be done during the display shows the message in Figure
11. As long as this message is displayed, the stick is subscribed to the Time
Server and must not be re-plugged again! Otherwise the Time Server will
deactivate the USB port!
To re-plug the stick, the display must show date and time first. Not till then the
USB stick was recognized by the Time Server as being ejected. There is a timeout of
approx. 1min.
To activate a deactivated USB port again, a restart of the Time Server is necessary.
This can be done by pressing the reset button next to the LAN port(s). See Figure 11
3.3 Access to the Time Server
This chapter describes how to access a Time Server per user terminal especially after
the initial start-up.

The DTS4128 and DTS4130S are equipped with a serial interface. The access
procedure is described in Chapter 3.3.2. The serial connection is only necessary for
initial configuration of the DTS4128 and DTS4130S. After an IP address is configured
to the LAN port, the DTS can be accessed by using SSH.
The DTS4138S and DTS4148S are accessible via SSH session via LAN port 2 and
the static IP settings introduced in Chapter 3.1.
All Time Servers can be accessed by a DHCP provided IP setting on their LAN1 port.
Therefore a SSH session as described in the Chapter 3.3.1 can be used.
3.3.1 Telnet/SSH connection
The network protocols Telnet and SSH are provided to access the Time Server via
LAN, but for security reason, it is strongly recommended to use SSH. Telnet needs to be
deactivated for the DTS4128 and the DTS4130S. For the DTS4138S and the DTS4148S
Telnet is as deactivated in the basic configurations provided on the USB stick.
After the physical connection is established, the Time Server can be accessed by any
terminal application e.g. PuTTY. SSH will be used here.
Figure 18: Initial SSH Session DTS4138S
For initial terminal login use:
• User: dts

• Password: dts
After login the “MAIN SELECTION” window appears:
Figure 19: MAIN SELECTION menu DTS4138S
3.3.2 Serial connection – for DTS4128 / DTS4130S only
The cable for the terminal connection needs DSUB-9 female connectors at both ends
and pins 2, 3 and 5 connected straight through.
Open a terminal session with e.g. HyperTerminal or PuTTY. The port settings are:
• baud rate 38400 bit/s

• data bits: 8
• parity: none
• stop bits: 1
• handshake: None

Figure 20: Serial Connection per HyperTerminal DTS4128
For initial terminal login use:
• User: dts
• Password: dts
After login the “MAIN SELECTION” window appears:

Figure 21: MAIN SELECTION menu DTS4128
3.4 Adaptions of Site Specific Parameter
This chapter describes the basic necessary manual adaptions of site specific parameters
after the initial start-up and, in case of the DTS4138S / DTS4148S, after the initial
configuration by using the USB stick.
Note 1:
It is recommended to install the latest software on the target device prior to the def-
inite commissioning. Therefore see the latest supplementary document: “AdminMan-
ual_FW_Update_TimeServer_DTS41[xy]”
Note 2:
After the successful adaptions of configuration parameter of the Time Server and its
verification, a backup of the running configuration should be done. Detailed information
is provided in the latest emergency plan document: “Administrator Manual Backup and
Restore of Time Server”.
3.4.1 Login Authentication
The initial login and password for all Time Servers is set to “dts”. This setting is also
provided on all USB configurations.

It’s not possible to change the login (username). Nevertheless the password should be
changed to an individual one for security reason.
From the “MAIN SELECTION” window choose: 2 Configuration -> 4 General -> 4
Password (menu)
Figure 22: General Settings Window DTS4138
Enter the desired password by using maximum 12 characters. Save the changes by
entering “98”.
3.4.2 Network Settings DTS4128 / DTS4130S
At the “NETWORK GENERAL” menu the following parameter will be adapted to

site specific ones:
• The Host name (Device name)

• IP Address and Subnet Mask of LAN1
• The Gateway Address
Necessary in case of a Multi-Unit configuration, if the power plant uses a router at
the Backbone Automation Highway
The following procedure is the same for both Time Servers. Both will be accessed by
serial connection. Exemplarily it is shown for the DTS4128.

From the “MAIN SELECTION” window choose: 2 Configuration -> 5 Network
Figure 23: NETWORK Menu DTS4128
To change the Host name chose menu number 6. Enter e.g.: “DTS4128”.
DHCP mode, IP address, Subnet Mask and Gateway Address have to be modified
accordingly. Enter the menu number and then the value according to the specific site
configuration.
Save the changes by entering “98”.
3.4.3 Network Settings DTS4138S / DTS4148S
At the “NETWORK GENERAL” menu the following parameter will be adapted to

site specific ones:
• The Host name (Device name)
• The Gateway Address

Necessary in case of a Multi-Unit configuration, if the power plant uses a router at
the Backbone Automation Highway

The following procedure is the same for both Time Servers independend from the way
of accessing them. Exemplarily it is shown for the DTS4138S via Telnet Session.
From the “MAIN SELECTION” window choose: 2 Configuration -> 5 Network
Figure 24: NETWORK GENERAL Menu DTS4138S
To change the Host name chose menu number 7. Enter e.g.: “DTS4138S”. Save
the changes by entering “98”.
LAN 1 (IPv4) and LAN 2 (IPv4) interfaces have to be modified by entering the menu
number 1 and 4 respectively. The NETWORK IPV4 menu will appear to change all
required entries: DHCP mode, IP address, Subnet Mask and Gateway Address.

Figure 25: NETWORK IPV4 Menu DTS4138S
Enter the menu number and then the value according to the specific site configuration.
This modification has to be done for LAN 1 and LAN 2 respectively.
3.4.4 Time Zone
The following procedure is the same for all Time Servers independend from the way of
accessing them. Exemplarily it is shown for the DTS4128 via HyperTerminal.
From the “MAIN SELECTION” window choose: 2 Configuration -> 4 General -> 2
Timezone displayed times
The appearing menu shows the forseen timezones. The actually valid is marked with
“*”.

Figure 26: TIME ZONE Menu
Enter the number of the time zone according to the geographical position of the power
plant. Enter “01” e.g. for “London”. Hit enter and save the changes by entering “98”.
3.4.5 SNMP
With this procedure general settings for SNMP usage are done.
For the DTS4138S / DTS4148S SNMP is activated per default. Only for the DTS4128
/ DTS4130S it has to be activated manually.
Additionally location and contact information could to be configured depending on site
properties.
Exemplarily it is shown for the DTS4130S via SSH.
From the “MAIN SELECTION” window choose: 2 Configuration -> 7 SNMP

Figure 27: SNMP CONFIGURATION menu DTS4130S
At the “SNMP CONFIGURATION” menu select the entry SNMP mode by choosing
menu number "1". Then enter 1=on to activate SNMP.
Enter DTS location / entry 3 and Contact information / entry 4, if available. Save
the changes by entering “98”.
Security Configuration:
The settings in this chapter are necessary only in case of the running Applica-
tion Software version is < 04.35.00, 06.12.00 or 07.06.00.
Then the SNMP community string for V1/2 needs to be adapted to the security strings
of the SNMP Proxy.
From the “SNMP CONFIGURATION” menu Figure 27 select 5 / SNMP V1/V2c
security configuration.

Figure 28: SNMP V1/V2c CONFIGURATION menu DTS4130S
Change Readonly community string to public

Change Read/write community string to public
3.5 Adaptions of Usage Specific Parameters
This chapter describes the basic necessary manual adaptions of usage specific parameters
after the initial start-up and, in case of the DTS4138S / DTS4148S, after the initial
configuration per USB stick.
Note:
It is recommended to install the latest software on the target device prior to the definite
commissioning. See the latest Administrator Manual for firmware update of the Buerk
Mobatime Time Server.
3.5.1 Deactivation of Telnet
For security reason, it is strongly recommended to use SSH instead of Telnet to access
the Time Server. Telnet needs to be deactivated for the DTS4128 and the DTS4130S.

For the DTS4138S / DTS4148S Telnet is already deactivated by default as part of the
default configurations provided on the USB stick.
Therefore, the following procedure has to be done for the DTS4128 and the DTS4130S
only. Exemplarily it is shown for the DTS4130S.
From the “MAIN SELECTION” window choose: 2 Configuration -> 6 Services
Figure 29: NETWORK SERVICES menu DTS4130S
At the “NETWORK SERVICES” menu select the entry telnet by choosing menu
number 1. Then enter 0=off to deactivate Telnet.
3.5.2 Redundant Power Supply
This feature is not available for DTS4128.

For the DTS4138S / DTS4148S it is part of the default configurations provided on the
USB stick. Therefore, the following procedure has to be done for the DTS4130S only.
From the “MAIN SELECTION” window choose: 2 Configuration -> 4 General

Figure 30: GENERAL SETTINGS Menu DTS4130
At the “GENERAL SETTINGS” menu select the entry Power by choosing menu
number 3. Then enter the value 1 for the redundant mode.
3.5.3 Time Source Type
With this procedure the Source Type for the Time Server units will be configured. It
has to be done for the DTS4128 / DTS4130S only. For the DTS4138S / DTS4148S it
is part of the default configurations provided on the USB stick.
Exemplarily it is shown for the DTS4128 via HyperTerminal.
From the “MAIN SELECTION” window choose:
2 Configuration -> 2 Time handling -> 1 Time source setting

Figure 31: TIME SOURCE Menu DTS4128
At the “TIME SOURCE” menu the Source Type has to be set to mainly used
1=DCF(MEZ) if a DCF receiver is connected to the Time Server. If a GPS receiver is
connected enter 2=GPSDCF(UTC).
For the Alarm delay 90min. is recommended.
For further possibilities refer to the manufacturers manuals.
After the configuration is entered, these changes have to be saved by entering “98”.
3.5.4 Time Adjustment
With this procedure the catch up speed for time adjustment could be edited. As default
value the USB configurations contain: 100000 ns/s. In case of an error of the AS-S7
and/or ET200SP HA the value of the catch up speed may need to be decreased. This
procedure is valid for all Time Servers. Exemplarily it is shown for the DTS4148S.
2 Configuration -> 2 Time handling -> 2 Time adjustment setting

Figure 32: TIME ADJUSTMENT CONFIGURATION Menu DTS4148S
At the “TIME ADJUSTMENT CONFIGURATION” menu select the entry Max.

catch up speed by choosing menu number 2. The desired value needs to be entered
now. The allowed range is: 0 – 10,000,000.
3.5.5 Redundant Operation of Time Servers
With this procedure two Time Server units will be configured as redundant master /
slave system. For the DTS4138S / DTS4148S it is part of the default configurations
provided on USB. For them only the IP address of the redundant Timer Server has to
be configured.
For the DTS4128 / DTS4130S it has to be activated additionally.
Exemplarily it is shown for the DTS4138S.
2 Configuration -> 2 Time handling -> 3 Redundant operation

Figure 33: REDUNDANT OPERATION Menu DTS4138S
At the REDUNDANT OPERATION menu the Mode has to be set to 1=red. re-
spectively 2=red. LAN1-LAN2 in case of the two redundant Time Servers are not
located in the same network (PRP). The role decision (master, slave) then takes place
exclusively via optical link (DTSLINK).
For all Time Servers in redundant operation it is necessary to enter the IP address of
the redundancy partner. Use entry 5 to enter the IP address 2. DTS41xy.
Further details about the master/slave handling are provided by [2], [3], [4], [5].
Note:
Only Time Servers of the same type have to be used for redundant operation, e.g. two
DTS4138S.
3.5.6 DCF Output Lines
If the DCF output is used to synchronize AddFEM SOE, several settings have to be done
at the DCF output. For the DTS4138 / DTS4148S it is part of the default configurations
provided on USB.
So it is shown exemplarily for the DTS4128 via HyperTerminal.
2 Configuration -> 1 Line -> 1 DCF out

Figure 34: DCF Output Menu DTS4128
At the DCF OUTPUT page chose the menu number 1 to set the Mode to 1=DCF
and menu number 2 to set the Time zone to the site specific value, e.g.: 1=MEZ.
After the configuration is entered, the changes have to be saved by entering “98”.
3.5.7 LAN Port Configurations on the DTS4138S / DTS4148S
The DTS4138S / DTS4148S Time Servers have two RJ45 network ports:
LAN port 1 is used to synchronize SPPA-T3000 clients by using NTP and/or PTP.
LAN port 2 is used to synchronize the AS-S7 by using the SIMATIC protocol.
Both Time Servers provide the S5 compatible mode (SINEC) and the PCS7 compatible
mode.

Figure 35: DTS4138S / DTS4148S Network Ports
Note:
If only one LAN interface is necessary, LAN1 has to be used.
3.5.8 PTP
With this procedure the standard settings for PTP will be introduced. The PTP feature
is available for the DTS4148S only and is activated per default on LAN2 respectively on
LAN1 as part of the configuration files dts4148_4.conf [6.6] and dts4148_5.conf
[6.7] provided on USB. If the initial configuration is done by USB, the following procedure
is not necessary.
2 Configuration -> 2 Time handling -> 6 PTP function
The “PTP CONFIGURATION” menu consists of two pages as shown and described
in the following two figures:

Figure 36: PTP Configuration Page 1
The following settings have to be done on page 1:

1. Mode 1 = master
2. Interface 0 = LAN1 or 1 = LAN2
3. Profile 1 = default
4. Delay mechanism 0 = E2E (End-to-End)
5. Transport protocol 2 = Layer 2
6. IPv6 scope default 14 (0xE)
7. UTC leap offset (TAI-UTC): 0
Note:
PTP uses TAI as time base which is defined as UTC + offset. If a leap second appears,
the value of the UTC leap offset counter will change. This would lead to a time jump,
because TAI then is UTC + offset + leap second.
To prevent this behavior, the "UTC leap offset" parameter needs to be set to "0". PTP
then uses UTC time instead of TAI. If a leap second happens, the time server will adjust
his clients smoothly.

Press ENTER to change to page 2:

Figure 37: PTP Configuration Page 2
The following settings have to be done on page 2:

11. Priority 1 0-255, default 128
12. Priority 2 0-255, default 128
13. Domain 0-4, default 0
14. Announce interval 0-4, default 1, values in format 2x sec (every 2 sec)
15. Sync interval -1..1, default 0, values in format 2 x sec (every sec)
16. Announce TO 2..10, default 3, values in format 2x sec (after 8 sec)
Adapt the values accordingly and save the changes by entering “98”.
3.5.9 SIMATIC PCS7 compatible mode
The SIMATIC PCS7 compatible mode is available for the DTS4138S and the DTS4148S.
It is activated by default on LAN2 as part of the configuration files dts4138_3.conf
[6.4], dts4148_3.conf [6.5] and dts4148_5.conf [6.7] provided on the USB stick.
The manual configuration of this feature is shown for the DTS 4148S as follows. Further
configuration information is provided by [2].
2 Configuration -> 2 Outputs -> 6 SINEC

Figure 38: SINEC menu DTS4148S
In the “SINEC” menu the subsequent settings have to be done:

1. Line 2 = on wintertime
2. Type 1 = SIMATIC comp. (PCS7 compatible mode)
3. Interval (sec) 1
4. Time zone Time zone selection, here: UTC +1
Depending on the geographical position of the power plant
See Figure 26 for examples
5. Interface Network Interface: 2 = LAN 2
3.5.10 SIMATIC S5 compatible mode (SINEC mode)
The SINEC protocol is supported by the DTS4130S, the DTS4138S and the DTS4148S.
But it is not supported by the DTS4128.
On the DTS4130S it can be activated. See the subsequent procedure in this Chapter
3.5.10.
The SINEC protocol is activated per default on LAN2 as part of the configuration file
dts4138_2.conf provided on the USB stick for the DTS4138S.
However the basic manual settings for both SIMATIC types are shown in Chapter 3.5.9.

To activate the SIMATIC S5 protocol on the DTS4148S, use the USB pre-configuration
for the SIMATIC PCS7 compatible mode and change the “Type” from
1 = SIMATIC comp (PCS7 compatible mode)
to:
0 = SINEC (SIMATIC S5 compatible mode)
Activate SINEC on DTS4130S

2 Configuration -> 2 Outputs -> 6 SINEC
Figure 39: SINEC menu DTS4130
In the “SINEC” menu the subsequent settings have to be done:

1. Line 2 = on wintertime
2. Time zone Time zone selection, here: UTC +1
Depending on the geographical position of the power plant
See Figure 26 for examples

4 USAGE OF NETWORK COMPONENTS IN THE TIME-NET
4 Usage of Network Components in the Time-Net
Media converters or network switches may be used to increase the coverable distance
between stations and to distribute the time signal.
This is especially necessary for the SIMATIC PCS7 compatible mode which is used to
synchronize AS-S7 CPUs with SOE. These AS-S7 CPUs in daisy chain have to be time
synchronized by installing a separate network the so called Time-Net.
If one or more AS-S7 CPUs are not located close to the others, the network connection
has to be increased by using a media converter.
For distances in the Time-Net below about 100m electrical connections are preferred.
For greater distances the electrical signal will be converted into an optical signal for the
transmission. See Figure 51 as example.
All these additionally used network elements have their own store-and-forward-times,
which will increase the store-and-forward-time of the network. This topic is explained
more detailed in the next chapter.
4.1 Store-and-Forward-Time
The sum of the store-and-forward-times of all network elements in a daisy-chain con-

nection is recommended to be below of 100µsec. This is for accuracy reason in time
synchronization.
Therefore in addition to the AS-S7 CPUs, media converters or switches which may be
used will also increase the store-and-forward-time of the daisy-chain, they are part of.
To stay below the recommended 100µsec the number of AS-S7 CPUs in one line needs
to be reduced if additional network components are added.
Estimated store-and-forward-times:
AS-S7 CPU: 7 µsec
Media converter, e. g.: SCALANCE X-101-1: 8 µsec
SCALANCE Switch, e. g. XB205-3, XC-106-2: 10 µsec
a) Example: Local setup (see Figure 44)

Here it is possible to synchronize up to 12 AS-S7 CPUs in a daisy-chain connection
→ 12 * 7 µsec = 84 µsec < 100 µsec
Figure 45, Figure 47, Figure 48, Figure 51 illustrate the connection of remote AS-S7
CPUs by using fiber optic cables.
For each additionally installed network component in one line, the total number of AS-S7

CPUs has to be reduced at least by one.

b) Example: Local and remote setup (see Figure 45)
Two fiber optic media converters between two AS-S7 CPUs reduce the amount of CPUs
to 10
→ 10 * 7 µsec + 2 * 8 µsec = 86 µsec < 100 µsec
Note 1:
The advantage of star topology is shown in Figure 48. It is recommended to use that
topology with more lines and less AS-S7 CPUs per line. If one CPU malfunctions, the
following AS-S7 is no longer time synchronized.
Note 2:
The following quantity framework applies:
• Per CPU maximum 16 ET 200SP HA stations with high-precision time stamping
• Per ET 200SP HA maximum 32 IO modules (DI) with high-precision time stamping
• Per IO module maximum 16 channels (DI) with high-precision time stamping
• Per ET 200SP HA maximum 512 IO signals with high-precision time stamping
4.2 Network Switch for SIMATIC PCS7 Compatible Mode
If a managed switch is used, e.g. SCALANCE XB205-3, unused ports may be disabled.
This switch is part of the separate Time-Net network of AS-S7 and is not connected to
the Automation Highway. Therefore the administration of the switch via Automation
Highway (e.g. SNMP, WBM) is not possible during regular operation. WBM access is
not possible in that way.
To access a switch temporarily a Field PG can be connected to get access by WBM.
Alternatively the switch can be connected to another switch of the Automation Highway
for configuration issues. After the configuration the switch has to be disconnected
again.
It is recommended to not connect the switch to the Automation Highway permanently
and during regular operation of AS-S7. Otherwise this may cause poorer time synchro-
nization of the AS-S7.

Note:
An alternative solution is the signaling contact which is provided by some switches, e.g.
SCALANCE X-101-1, XC-106-2, X-308-2M, XR324. This contact could be used to
receive fault or error information during the operation from the switch.
The signaling by the relay contact is synchronized with the fault LED, in other words,
errors displayed by this LED are also signaled on the signaling contact.
4.3 Network Switch for PTP in the Automation Highway
Note:
The following screenshots are based on a SCALANCE X308-2M. They describe the neces-
sary configuration details for PTP. Further configuration details on network components
are not part of this document. More information is described in [7].
Maintenance information related to SCALANCE switches that support PTP is introduced
in Appendix 11.

Figure 40: IEEE 1588v2
1588 Mode:
To activate the “1588 Mode” Transparent Clock has to be chosen. The device adopts
the function of a transparent clock and forwards PTP messages to other nodes. These
messages contain a correction field filled in by the device.
In the Transparent Clock menu below the following settings has to be done:

Figure 41: Transparent Clock Configuration
Delay Mechanism: The following 2 delay mechanisms are possible:

End to End (delay request response mechanism will be used)
Peer to Peer (Peer-delay mechanism will be used)
Domain Number: Enter the domain number of the device: Default “0”.
The device ignores PTP messages with a different domain number.
For SPPA-T3000 networks, each device must be in the same domain.
Vlan ID: VLAN functionality is not used in SPPA-T3000 standard.

Therefore enter the SCALANCE default VLAN ID “1”.
Vlan Prio: Enter default VLAN prio “4”.

The next menu further below is Ports. As shown in Figure 42, it gives detailed infor-
mation about the status of the individual ports.
Figure 42: Port Parameter

Port: Shows the available port numbers
Enabled: Shows the port status. The following entries are possible:
disabled: The port is not involved in PTP
enabled: The port processes PTP messages
Faulty Flag: The error status related to PTP.

true: An error occurred. Further information is shown in
the event log of the device.
false: No error has occurred on this port.
Transport Mechanism: Either "Ethernet" or "UDP IPv4".
To enable PTP at a certain port, its individual port configuration has to be adapted.
Click on the port number to open the corresponding page, see Figure 43.

Figure 43: Port Configuration
Port: The chosen port number, see example in Figure 42
Transparent Clock Select the check box if the port has to process PTP messages
enabled:
Transport Mechanism: The communication partner must support the selected transport mechanism.
For SPPA-T3000 “Ethernet” (= Layer 2) will be used.

5 Appendix - Illustrations of Different Scenarios for HPT
c Siemens AG 2019. Unrestricted. All rights reserved.
Note:
The following scenarios are configuration examples. The usage of the DTS4148S LAN ports is service independent.
However, if just one LAN port is necessary (not part of this document) LAN1 has to be used.
5
APPENDIX - ILLUSTRATIONS OF DIFFERENT SCENARIOS FOR HPT
Figure 44: Local Time Synchronization of 12 AS-S7 CPUs
59
5 APPENDIX - ILLUSTRATIONS OF DIFFERENT SCENARIOS FOR HPT
Figure 45: Local and Remote Time Synchronization of 10 AS-S7 CPUs
Figure 46: Local and Remote Time Synchronization of 10 AS-S7 CPUs
62
5
Figure 47: Local and Remote Time Synchronization larger than 12 AS-S7 CPUs; Additional Switches; Media Converters
5
Figure 48: Star Topology for best SOE accuracy (1ms-SOE) Local and Remote Time Synchronization larger than 12 AS-S7 CPUs
63
Figure 49: Ring Topology: SIMATIC Protocol for AS-S7 and PTP for AS/CS3000
Figure 50: PRP Network: SIMATIC Protocol for AS-S7 and PTP for AS/CS3000
Figure 51: Multi-Unit Configuration: SIMATIC Protocol for AS-S7 and NTP for all other Clients
6 APPENDIX - BASIC CONFIGURATIONS PROVIDED ON THE USB STICK
6 Appendix - Basic Configurations provided on the USB Stick
The subsequent tables contain the usage and site specific values provided on the USB
stick, whose manual adaptions were described in the Chapters 3.4 and 3.5. The complete
list of all factory default values is provided in the Time Server manuals accordingly: [2],
[3], [4], [5].

6.1 dts4138_1.conf
Group Parameter Default value
Network
DHCP LAN1: off
LAN2: off
IP address LAN1: 10.0.0.7
LAN2: 192.168.1.5
Network mask LAN1: 255.255.240.0
LAN2: 255.255.255.0
Gateway IP LAN1: 10.0.0.1
LAN2: 192.168.1.1
Device Name / Host Name DTS4138
NetworkServices
Telnet 0=off
SSH 1=on
FTP 1=on
General
Time Zone 0=UTC
Power 1=redundant
DCF out
Mode 1=DCF
Time zone 0=UTC
SINEC
Line 0=off
Type 0=SINEC
Interval (sec) 1
Time zone 0=UTC
Interface 0=none
SNMP
SNMP mode on
read only community string romobatime
read/write community string rwmobatime
Time Source
Time source 2=GPS-DCF
Time zone 0=UTC
Alarm delay for failure of the source 90min
Redundant Operation
Mode 1=redundant
IP address 2. DTS4138 <plant specific value>
Table 4: Basic Configuration: dts4138_1.conf

6.2 dts4148_1.conf
Network
DHCP LAN1: off
LAN2: off
LAN2: 192.168.1.5
LAN2: 255.255.255.0
LAN2: 192.168.1.1
NetworkServices
Telnet 0=off
SSH 1=on
FTP 1=on
General
Time Zone 0=UTC
Power 1=redundant
DCF out
Mode 1=DCF
Time zone 0=UTC
SINEC
Line 0=off
Type 0=SINEC
Interval (sec) 1
Time zone 0=UTC
Interface 0=none
PTP
Mode 0=OFF
Interface 0=LAN1
Profile 1=Default
Delay mechanism 0=E2E (End-to-End)
Transport Protocol 2=Layer2
IPv6 scope Default 14 (0xE)
UTC leap offset (TAI-UTC) in sec 0
Priority 1 128
Priority 2 128
Domain 0
Announce interval 1
Sync interval 0
continue on next page


Announce TO 3
SNMP
SNMP mode on
Time Source
Time zone 0=UTC
Redundant Operation
Mode 1=redundant

6.3 dts4138_2.conf
Network
DHCP LAN1: off
LAN2: off
LAN2: 192.168.1.5
LAN2: 255.255.255.0
LAN2: 192.168.1.1
NetworkServices
Telnet 0=off
SSH 1=on
FTP 1=on
General
Time Zone 0=UTC
Power 1=redundant
DCF out
Mode 1=DCF
Time zone 0=UTC
SINEC
Line 2=on wintertime
Type 0=SINEC
Interval (sec) 1
Time zone 0=UTC
Interface 2=LAN2
SNMP
SNMP mode on
Time Source
Time zone 0=UTC
Redundant Operation
Mode 1=redundant

6.4 dts4138_3.conf
Network
DHCP LAN1: off
LAN2: off
LAN2: 192.168.1.5
LAN2: 255.255.255.0
LAN2: 192.168.1.1
NetworkServices
Telnet 0=off
SSH 1=on
FTP 1=on
General
Time Zone 0=UTC
Power 1=redundant
DCF out
Mode 1=DCF
Time zone 0=UTC
SINEC
Type 1=PCS7 compatible mode
Interval (sec) 1
Time zone 0=UTC
Interface 2=LAN2
SNMP
SNMP mode on
Time Source
Time zone 0=UTC
Redundant Operation
Mode 1=redundant



6.5 dts4148_3.conf
Network
DHCP LAN1: off
LAN2: off
LAN2: 192.168.1.5
LAN2: 255.255.255.0
LAN2: 192.168.1.1
NetworkServices
Telnet 0=off
SSH 1=on
FTP 1=on
General
Time Zone 0=UTC
Power 1=redundant
DCF out
Mode 1=DCF
Time zone 0=UTC
SINEC
Interval (sec) 1
Time zone 0=UTC
Interface 2=LAN2
PTP
Mode 0=OFF
Interface 0=LAN1
Profile 1=Default
Priority 1 128
Priority 2 128
Domain 0
Announce interval 1
Sync interval 0
Announce TO 3


SNMP
SNMP mode on
Time Source
Time zone 0=UTC
Redundant Operation
Mode 1=redundant

6.6 dts4148_4.conf
Network
DHCP LAN1: off
LAN2: off
LAN2: 192.168.1.5
LAN2: 255.255.255.0
LAN2: 192.168.1.1
NetworkServices
Telnet 0=off
SSH 1=on
FTP 1=on
General
Time Zone 0=UTC
Power 1=redundant
DCF out
Mode 1=DCF
Time zone 0=UTC
SINEC
Line 0=off
Type 0=SINEC
Interval (sec) 1
Time zone 0=UTC
Interface 0=none
PTP
Mode 1=Master
Interface 1=LAN2
Profile 1=Default
Priority 1 128
Priority 2 128
Domain 0
Announce interval 1
Sync interval 0
Announce TO 3


SNMP
SNMP mode on
Time Source
Time zone 0=UTC
Redundant Operation
Mode 1=redundant

6.7 dts4148_5.conf
Network
DHCP LAN1: off
LAN2: off
LAN2: 192.168.1.5
LAN2: 255.255.255.0
LAN2: 192.168.1.1
NetworkServices
Telnet 0=off
SSH 1=on
FTP 1=on
General
Time Zone 0=UTC
Power 1=redundant
DCF out
Mode 1=DCF
Time zone 0=UTC
SINEC
Interval (sec) 1
Time zone 0=UTC
Interface 2=LAN2
PTP
Mode 1=Master
Interface 0=LAN1
Profile 1=Default
Priority 1 128
Priority 2 128
Domain 0
Announce interval 1
Sync interval 0
Announce TO 3


SNMP
SNMP mode on
Time Source
Time zone 0=UTC
Redundant Operation
Mode 1=redundant

7 APPENDIX - MIGRATION SPPA-T2000 TO SPPA-T3000
7 Appendix - Migration SPPA-T2000 to SPPA-T3000
With SPPA-T3000 Release 5.0 a migration concept for SPPA-T2000 is provided. The
Buerk Mobatime DTS4130S and DTS4138S can be used for SPPA-T2000 to SPPA-
T3000 migration.
7.1 Migration with Buerk-Mobatime DTS4130S Time Server
To synchronize the involved Buerk Mobatime DTS4130S Time Servers, a serial connec-
tion cable between both Time Servers is necessary. The cable is connected to DCF
out at the SPPA-T3000 Time Servers and linked to DCF in at the SPPA-T2000 Time
Servers.
Figure 52: Migration Configuration with two DTS4130S
At least 1 serial connection cable is mandatory for non-redundant configurations. For

redundant configurations, 2 cables are necessary.
Specification for serial connection cable:
• The sum of all connection cable length must not exceed 200m
• Cable has to fulfill AWG 23 specification
• 2 wires

7 APPENDIX - MIGRATION SPPA-T2000 TO SPPA-T3000
7.2 Migration with Buerk-Mobatime DTS4138S
No serial connection cable will be necessary, if using DTS4138S Time Servers for migra-
tion. These Time Servers are equipped with two independent network interfaces (LAN1
and LAN2), which are connected to the two independent network segments as follows:
One interface is connected to the SPPA-T3000 Automation Highway. The other is
connected to the SPPA-T2000 Plant Bus. The following Figure 53 illustrates a redundant
configuration with DTS4138S.
Figure 53: Migration Configuration with two DTS4138S

8 APPENDIX - BASICS OF GPS TIME SYNCHRONIZATION
8 Appendix - Basics of GPS Time Synchronization
8.1 Overview
The Global Positioning System (GPS) distributes high-precision time and position data
worldwide. At a height of about 20,000km, 22 GPS satellites circle around the earth
on different orbits (see Figure 54). The number of satellites and their orbits give the
opportunity to have 6 to 11 satellites in the view range of an antenna with optimum free
sight to the sky at every location on earth at the same time. For position calculation
the signal of at least 4 satellites is necessary, see Chapter 8.2
Figure 54: GPS Satellite Orbits
At least one atomic clock (accuracy at least 1*10-12 sec) is running in every satellite.
Together with it‘s GPS world time (GPS-UTC) every satellite constantly transmitts it’s
position / orbit data on a carrier frequency of 1.57542GHz.
Special antenna equipment is necessary to receive the GPS signal. The GPS antenna
has to be mounted with direct sight to the Horizon. A connected GPS receiver collects
the information from all satellites in the view range of his antenna.
Buildings, trees, mountains etc. will reduce the view range (see Figure 55). Additionally
the amount of satellites in view range will vary during the day. Hence the best installation
position of the GPS antenna is, if no massive or large-scale objects e.g. buildings block
the sight to the horizon.

Figure 55: GPS antenna installation with reduced view range
8.2 Position Calculation with GPS
For precise time calculation it is required to do a determination of the position of the

receiver first. Therefore the algorithm uses the received satellite position data and the
sending time of the signal and calculates the transfer time of the signal.
Assuming a 2D system as shown in Figure 56 for example, the transfer time leads to a
sphere around each satellite where the GPS antenna could be located. The position of
the antenna can now be found on the points of intersection of these spheres.

Figure 56: 2D-Position calculation depending on transfer time
Because of the internal clock of the GPS receiver is not as precise as the atomic clocks
inside the satellites, the calculated transfer time will be erroneous and the calculated
position is not as precise as required. In the example in Figure 57 the calculated transfer
time is 4sec instead of actually 4,5sec.
Figure 57: Unprecise position calculation depending on erroneous transfer time
With a third calculation of the transfer time derived from the data of a third satellite
three points of sphere intersection (see points B in Figure 58) can be found.

Figure 58: 2D-Position calculation depending on data from 3 satellites
To find the receiver position point A the time of the receiver clock will be shifted as long
as the 3 points of intersection B match in just one point (see point A in Figure 58).
Therefore the clock error has been solved and the receiver clock runs in synchronicity
with the atomic satellite clocks.
In reality hence the data of at least 4 satellites is necessary to do a 3D-position calculation
i.e.: latitude, longitude and height. With 3 satellites as shown in Figure 58 only a 2D-
position could be done and latitude and longitude will be calculated.
8.3 Time Calculation with GPS
With the algorithm introduced in the former chapter the GPS-receiver is able to deter-
mine its exact position. On the other hand the receiver also could adjust its internal
clock to the received, high precise time of the satellites. All depending on the calculated
transfer time.
The GPS-receiver requires data of minimum one satellite to keep the internal clock
synchronized. The more satellites are in the view range of the GPS-receiver, the more
precise the result of adjusting the internal clock will be and an accuracy of ±1µsec can
be achieved with standard GPS receivers.
8.4 Source of Interference
The GPS signal is nearly interference proof due to the high transmission frequency of
1.57542GHz. Very narrow-banded antennas and filters can be used to decode the signal,

because the information is transmitted with phase modulation at constant amplitude.

There are no atmospheric disturbances at great heights. The transmission between layers
in the atmosphere can cause time offsets, but only in range of picoseconds.
If the antenna has a clear view to the horizon an average of 7 to 9 satellites are visible.
That means the time information is 100% available. Even if half the horizon is covered
the availability still reaches 90 to 95%. Due to the low transmission power of the satellites
and the high frequency, the cable length between the antenna and the receiver has to
be short, otherwise the signal cannot be filtered from noise.
Military ground control stations may interfere with the accuracy of the position calcula-
tion for a time. In succession some satellites will transmit wrong orbit data, from which
the transfer time of the signal is calculated wrongly. The error in the time calculation
may amount to some µsec.
Regarding to the antenna itself only a lot of ice or snow on the antenna itself may avoid
the system from receiving the GPS signal correctly. This can be overcome by the usage
of antennas with integrated heating.

9 APPENDIX - TIME SYNCHRONIZATION IN ETHERNET NETWORKS
9 Appendix - Time Synchronization in Ethernet Networks
9.1 Time Master in Ethernet Networks
There are three possibilities to synchronize the time master of an Ethernet Network to
a (national) time standard:
a) The synchronization via satellite uses the GPS signal and generates the
best results. Its basics were introduced in Appendix 8.
b) The synchronization via radio in Europe uses the DCF77 signal. The
sender is located near Frankfurt. A special piece of antenna equipment
is necessary; the antenna has to be mounted with direct sight to the
radio station and has to be adjusted after the installation.
c) The synchronization via modem requires an external time master, which

itself should be synchronized to a time standard. Different protocols like
DCF77 can be used for this mechanism.
Note:
Scope of this document is the synchronization method via satellite.
9.2 NTP Time Synchronization
The Network Time Protocol called NTP is the protocol used on Ethernet-based networks
to synchronize time clients against the time standard (UTC).
There are three different approaches for time synchronization available:
a) request – response mechanism: A client sends a request to the
configured Time Server and gets the actual time with quality information
in the response. Based on the response data, the client’s NTP daemon
calculates the best value for the actual time, corrected by the delay, i.e.,
the network transfer time.
b) broadcast mechanism: The Time Server sends a broadcast message

cyclically and all time clients with the appropriate configuration listen
to this broadcast message. Based on the broadcast data, the client’s
NTP daemon calculates the value of the actual time.
c) multicast mechanism: The Time Server sends a multicast message

cyclically and all time clients with the appropriate configuration listen
to this multicast message. Based on the multicast data, the client’s NTP
daemon calculates the value of the actual time.
The accuracy of a time client’s clock against the time master’s clock varies by the
synchronization mechanism used, the time span past since the time client started the

synchronization, and the deviation of the time client’s clock at the beginning of synchro-
nization.
Broadcast messages and multicast messages are not transferred between physical subnets
via routers or bridges. Their advantage is a minimum of network load.
For the request–response mechanism the advantages are: The following quantity
framework applies:
• the possibility to correct the received time with the network transfer time, which is
part of the NTP algorithm specified in [1].
• the possibility to connect the time client to multiple time masters for redundancy.
With the request–response mechanism a logical NTP network can be set up, where a
time client will be time master for other clients (see Figure 59). Stratum1 Time Servers
synchronize to (national) time standards (stratum0) via satellite, radio or modem. Stra-
tum2 Time Servers and time clients synchronize to stratum1 Time Servers via network.
Stratum3 Time Servers and time clients synchronize to stratum2 Time Servers, and so
on.
Figure 59: Logical NTP Network
To achieve an accuracy of 10 milliseconds already after some synchronization events,

the time of the client could be set to the master’s time once, before starting the syn-
chronization. Not till then the NTP algorithm will adjust the client’s time.

The best accuracy will be reached after 50 to 100 synchronization events on a network
without high load or sporadic load changes.
9.3 PTP Time Synchronization (IEEE1588)
The Precision Time Protocol (PTP) is complying with IEEE 1588v2 and offers higher
accuracy compared to NTP.
PTP is applied in local area networks and achieves clock accuracy in the sub-microsecond
range, what makes it suitable especially for measurement and control systems.
The basis of a PTP network is its composition of communicating clocks.
To determine the device in time provisioning with the highest precision, the Grandmaster
Clock, the so called Best Master Clock (BMC)-Algorithm is applied. The Grandmaster
Clock will become the reference clock for all other devices in the network.
Changes in the network topology may lead to the BMC algorithm executed again in
network segments truncated from the Grandmaster Clock. In SPPA-T3000 the Time
Servers are the Grandmaster Clocks.
9.3.1 Correction Mechanisms
To increase the accuracy of the time signal provided by the Time Server the store-and-
forward-time between the communicating devices will be taken into account. There are
two correction mechanisms provided by the DTS4148S: "end-to-end" and "peer-to-peer"
which will be applied to calculate the store-and-forward-time and do the correction on
the provided time signal.
In SPPA-T3000 the used mechanism is "end-to-end".
However, these mechanisms have to be configured consistently on each device inside the
network for either the "end-to-end" or the “peer-to-peer” mechanism. Both correction
mechanisms cannot be used together at the same time at the same network section.
The approach of the slave time to the reference master time will be done continuously.
Especially jump backs of the slaves’ time will be prevented in that way.
Ent-to-End: This mechanism takes into account the store-and-forward-times between

slave and master of time provisioning. The calculation method executed is based on the
“Delay-Request-Response-Mechanism” which includes several messages handled between
master and slave.

To achieve high accuracy in time synchronization, it is indispensable that all network

components (e.g. switches) that reside on the route between master and slave need
to support PTP to put their own store-and-forward-time into a correction field of the
synchronization message. If not, the accuracy is decreasing depending on e.g. with
increasing network load. Switches which do not support PTP cannot guarantee constant
message delay times between the master and slave due to queuing.
For further information about switches and their configuration with PTP see Chapter 4.3.
Peer-to-Peer: The aim of the “peer-to-peer” correction mechanism based on the peer
delay message handling is to calculate the delay time of messages between two neighbored
ports of PTP-compliant devices. In contrast to a delay request response message that
is transported between the slave and master also over several network nodes, peer delay
messages are only exchanged with the relevant neighbor node, hence the name "peer
delay".
9.3.2 Clock Types under the PTP
• ’Ordinary Clock’ or OC: Could be slave or master, not both at the same time.
These type of clocks synchronize directly.
• ’Boundary Clock’ or BC: Devices with role slave and master at the same time are
able to carry time information from one network segment to another. It receives
time information as a slave and forwards it as a master.
• ’Transparent Clock’ or TC: Receives PTP messages and improves the time infor-
mation in the network by forwarding the modified or corrected message.
9.4 SIMATIC Time of Day Synchronization
The SIMATIC protocol, here the PCS7 compatible mode, is used to synchronize AS-S7
for unit wide accuracy of 1ms SOE. The SIMATIC protocol is used to reach a higher
accuracy of time synchronization compared to NTP synchronized AS-S7.
To synchronize an AS-S7 with the SIMATIC protocol, two network ports are used for
each AS-S7 CPU (not for the last in the chain).

10 APPENDIX - HOPF TIME SERVER - GPS SATELLITE CLOCK HOPF6842
10 Appendix - HOPF Time Server - GPS Satellite Clock HOPF6842
Note:
The Time Server hardware introduced in this chapter is a discontinued production model.
The information given here is outdated and further support or the availability of spare
parts is doubtful and not guaranteed.
10.1 Hardware of HOPF6842
There are two GPS Satellite Clock 6842 with independent antennas required, to get the
1-fault tolerant, redundant solution.
The system is mounted on a half-sized 19" pedestal (3U/42HP) that can be expanded
to a full 19" pedestal and is equipped with:
• an LCD display (2x16 digits) and a keypad for set-up of the configuration
• 2 serial interfaces RS232 (V.24) and RS422 (V.11)
• a power supply (115/230 VAC)
The system can be expanded with two adapter cards of the following type:
• LAN board 7270 to connect the system as time master to the Ethernet network.
The board is available with network transfer rate of either 10 Mbit/s or 10/100
Mbit/s.
• Fiber Optic Converter Board 7247 with up to 4 fiber optic lines to send DCF77
pulses
• Master Clock Board 7406 with 2 lines to synchronize slave clocks
The output can be configured to operate as:
• 2 independent minute slave lines

• a combination of one minute and one second slave line
• 2 independent DCF77 time code lines
• Standard Frequency Module 7530 to generate a frequency output between 1 Hz and
10 MHz

For SPPA-T3000 the LAN board 7270 with 100 Mbit/s is specified as adapter to the
Ethernet network and a Fiber Optic Converter Board 7247 will additionally be installed to
connect the AddFEM SOE directly to the time master for higher accuracy. To generate
required synchronization pulses for connection of third party products, it is possible to
use the build-in interfaces, or one of the different interface cards (Master Clock Board
7406, Standard Frequency Module 7530) can be installed. One HOPF6842 can have only
two additional cards installed. If more than two cards are required, either an additional
HOPF6842 or a HOPF 7000 system has to be installed. The HOPF 7000 is compatible
to the HOPF6842, but can have up to 8 cards installed due to a greater backplane.
10.2 Installation and Setup of the GPS Satellite Clock
To install the GPS satellite clock follow the instructions delivered by the manufacturer.
After the installation is complete, the antenna connected and the power supply switched
on, the GPS satellite clock has to be configured. Before connecting the LAN board 7270
with the network, the information about the system behavior should be taken in account
(see Chapter 10.3). In SPPA-T3000 the configuration of the LAN board 7270 should be
done according to the network configuration of the system. In the examples below the
IP-address 172.16.130.1, net mask 255.255.192.0, and the address of the automation
server 172.16.132.1 is assumed as gateway address. For details on how to configure and
set up the GPS satellite clock 6842, the LAN board 7270 and the Fiber Optic Converter
Board 7247 please see the manufacturer’s documentation [8], [9] and [10].
10.2.1 Setup of the Fiber Optic Converter Board 7247
The HOPF Fiber Optic Converter Board 7247 can have up to 4 transmitters or receivers
installed and has to be ordered according to the requirements. For the time synchro-
nization of the AddFEM SOE, a minimum of one transmitter must be installed and
configured to transfer the DCF77 pulse. For example, if FL1 is installed at JB1 on the
board (see [10]), the jumper a, c and d must be open and jumper b must be closed. If
more than one transmitter is installed, the settings have to be done accordingly for FL2
at JB2, FL3 at JB3 and FL4 at JB4. No additional configuration of the HOPF6842 is
required.
10.2.2 Setup of the LAN Board 7271
The on-board DIP switches have to be set to identify the bus system of the HOPF6842
and the board number. The DIP switches are located on the lower-left side of the LAN

board and should be set only by the manufacturer or qualified assembling personnel.
The switch DS1 requires the following setting for the LAN board:
Swtich number 1 2 3 4 5 6 7 8
Value ON OFF OFF OFF OFF OFF OFF OFF
All other configurations has to be done via the WEB interface, which requires a config-
ured IP address as described in Chapter 10.2.4. Details can be found at the manufac-
turers’ documentation. Within Chapter 10.2.5 the configuration via the WEB interface
is shown by screenshots from a test installation.
10.2.3 Setup of the LAN Board 7270
The on-board DIP switches for the LAN board have to be set to identify the bus system
of the HOPF6842 and the board number. The DIP switches are located on the lower-left
side of the LAN board and should be set only by the manufacturer or qualified assembling
personnel.
The switch DS1 requires the following setting for the LAN board:
Value ON OFF ON ON ON ON ON ON
To simulate the “GPS sync” during installation phase of the antenna (see Chapter 5.6)
the switch DS2 requires the following setting for the LAN board: The switch DS1 requires
the following setting for the LAN board:
Value DO NOT MODIFY; LEAVE AS MANUFACTURED ON
This mode is only available in new manufactured cards with firmware version 6.00 or
higher. In this mode a lost antenna signal can only be detected by controlling the display
of the HOPF6842. After the antenna is installed, the DIP switch has to be reset to OFF,
otherwise there is no possibility to recognize failure of the antenna by the management
proxy.
10.2.4 Setup of the HOPF6842
To enter the configuration mode of the HOPF6842, press the ENT button at the key-
board of the HOPF6842. Now the display changes from showing the time information
(example)

LT: 14:10:43 D-R

WE 16/JUN/2004
to display the main menu
SET=1 SHOW=2
S.CLOCK=3 INI=4
Now press the 1 button to start the configuration mode of the HOPF6842. The display
will change to show the entry display for the first configuration block. Now press the N
button to answer the questions until the question for setting the IP address of the first
LAN board is displayed
SET LAN 1
ADDR. Y/N
The question has to be answered by pressing the Y button and the display changes to
show
LAN 1 >
Now enter the IP address of the LAN board, for example 172.016.130.001. Enter only
the numerical values, every block with 3 digits including the leading zeros. The dots are
inserted automatically. For the example the display then will change to
LAN 1 >172.016.130.001
Now enter the ENT button to finish the entry and the question for setting the IP address
is shown again. Enter the N button to get the next configuration question for entering
the gateway address.
SET LAN 1
GATEWAY ADR. Y/N
show
G.W 1 >
Now enter the IP address of the first Application Server as gateway, for example
172.016.132.001. Enter only the numerical values, every block with 3 digits includ-
ing the leading zeros; the dots are inserted automatically. For the example the display
then will change to
G.W 1 >172.016.
132.001
Now enter the ENT button to finish the entry and the question for setting the IP address
the net mask
SET LAN 1
NET MASK. Y/N

show
NET MASK LAN 1
>
Now enter the bits of the host part for the net mask, e.g., 14 for a net mask
255.255.192.0, and the display will change to
NET MASK LAN 1
>14<
Now enter the ENT button to finish the entry and the question for setting the net mask
the control byte
SET LAN 1
CNTRL.-BYTE Y/N
When a LAN board 7271 is installed and the configuration at the HOPF6842 is done,
press the BR button to finish the configuration. Now continue with the configuration of
the LAN board 7271 via the WEB interface (see Chapter10.2.5). When a LAN board
7270 is installed, the question has to be answered by pressing the Y button and the
display changes to show
BIT 7654 3210
_
Now the configuration of the second LAN board has to be set by pressing the appropri-
ate 0 button or 1 button for every bit to set the bit mask to 0000 0010, which is the
configuration for the NTP procedure with UTC time zone coding.
BIT 7654 3210
0000 0010
After the values for all bits are entered, press the ENT button to finish the entry and
then the BR button to finish the configuration.
10.2.5 Configuration of the LAN board 7271 via WEB Interface
After an IP address is assigned to the LAN board 7271, the final configuration can be
done via the WEB interface. The following screenshots from a test environment show
the different screens. To login to the LAN board a username and password has to be
entered. The username for configuration modus is “master” and at the manufactory
default no password is assigned.

Figure 60: HOPF6842 - Login Screen
Details about the WEB interface can be found at the manufacturer’s documentation [13].
The two important screens for activating NTP and definition of stratum value for crystal
mode are shown on the next page. To activate the NTP protocol at the configuration
option “Network” the link “Time” at the tab “Protocols” has to be selected. Within
this configuration window the NTP has to be enabled and all other protocols have to be
disabled. To define the stratum value for crystal mode or while operating without antenna
during commissioning phase it is possible to configure the NTP server at the configuration
option “NTP” the link “Server Configuration” at the tab “Server Configuration” has to
be selected. Within this configuration at the tab “Crystal Operation” the mode “Switch
to specific stratum” has to be enabled and the stratum “10” has to be set. This
configuration replaces the DIP switch setting of DS2 Switch 1 at the LAN board 7270
described at Chapter 10.2.3

Figure 61: HOPF6842 - Activating NTP

Figure 62: HOPF6842 - Definition of Stratum for Crystal Mode

10.3 Connecting the HOPF6842 to the SPPA-T3000 System
After installing the HOPF6842 and entering the configuration data it is necessary to
connect the LAN board (7270 or 7271) with the Automation Highway. At this moment
the SPPA-T3000 system should not be in operational mode.
If the Automation Servers are already in operation mode when the first HOPF6842 is
connected to the Automation Highway, then the clock inside these components will be
set to the time value delivered by the time master. This operation will cause a time jump
depending on the difference to the time master. Time stamps inside the data delivered
to Application Server will make the same jump as the clock already has done.
If the Application Server is already operational when the first HOPF6842 is connected to
the Automation Highway, then the NTP-Daemon service will adjust or step the system
clock. To avoid this behavior and a time difference between the Application Server and
the complete system SPPA-T3000 should be (re)started after the connection of the two
time masters to the Automation Highway.
10.4 Accuracy of HOPF6842
The HOPF6842 GPS system can calculate data of up to 6 satellite signals in parallel,
received from an antenna installed with free view to the sky. After 0,5 hours of contin-
uous GPS reception the systems crystal will reach an accuracy of ±0, 1ppm.
In 3D-Position mode the HOPF6842 requires reception of data from minimum 4 satel-
lites and will reach an accuracy of ±1µsec.
In Position-Fix mode only data from one satellite are required and for an accuracy in
the position entry by ±1 minute degree the system achieves an accuracy of ±20µsec. If
in Position-Fix mode data from minimum 4 satellites are available, the HOPF6842 will
switch automatically to 3D-Position mode and calculate the accurate position.
If the antenna signal is lost, the internal clock will run in free mode and a short inter-
ruption will have no influence on the accuracy. Depending on the time of interruption
the accuracy will decrease to ±10ppm (864 msec drift per day) or even more.
The backup clock inside the GPS receiver works with an accuracy of ±25ppm at 25◦ C,
when the system loses the power supply. The backup clock works for up to 3 days
without maintenance and a restart will be executed with this time base.
Remark: After transporting the HOPF6842 to an alternate location, it may be necessary
to enter the new (approximate) position via the keypad and force the HOPF6842 for a
new initialization of the system by the reset function.

10.5 Operation of the HOPF6842
After connecting the antenna cable to HOPF6842 the system starts with calculation
of the position. This calculation requires reception of signals from 4 satellites and for
the first time it may take between 30 minutes and 4 hours until the correct position is
calculated. To shorten the initializing phase of the GPS receiver, it is possible to enter the
(approximate) position via the keypad. A warm start with the accurate position already
set requires approximately 1 minute. When installing the antenna, it is necessary to
control the number of seen satellites against the theoretical visible and their signal/noise
ratio (bad: 10 – 30 / sufficient : 30 – 70 / good > 70). If not enough satellites appear
in the display, the visible range of the antenna may be too small and a better position
has to be searched for. To enter the inspection mode of the HOPF6842 press the ENT
button at the keyboard of the HOPF6842. Now the display change from showing the
time information (example)
LT: 14:10:43 D-R
WE 10/OCT/2005
to display the main menu
SET=1 SHOW=2
S.CLOCK=3 INI=4
Now press the 2 button to start the inspection mode of the HOPF6842. The display will
change to show the entry display for the first inspection block. Now press the N button
to answer the questions until the question for showing the satellite data is displayed
SHOW SATELLITES
Y/N
show
V 28:063 08:125
07 : :
In this example 7 satellites are in the theoretical visible range and data are received only
from two of them. The first number is the pseudo random number of the satellite and
the second number behind the colon gives the signal/noise ratio. Six satellites can be
received by the HOPF6842 and only the ratio of 4 satellites can be displayed at a time,
therefore display will switch every five seconds to show the other ratio data. Finish the
inspection mode by pressing the BR button to avoid errors in the menu selection.
10.6 Using LAN board 7270 during Commissioning Phase without Antenna
Sometimes it is necessary to use the HOPF6842 during the commissioning phase as time
master, while no antenna is installed. To get all components synchronized to the same

time base only one HOPF6842 will be setup and configured. The time has to be entered
manual at the keyboard and the LAN board has to be configured.
10.6.1 Configuration of the LAN board during Operation without Antenna
A LAN board 7271 will answer the requests from the time clients with the stratum
defined for the crystal operation, no additional action is required.. The normal configured
LAN board 7270 will answer requests from the time clients with an error code and no
synchronization is done by the Automation Server and Application Server. To get answers
from the LAN board 7270 a special DIP-switch setting is required, which is only valid
for firmware version 6.01 or higher of the LAN board 7270. In this mode the LAN board
7270 will simulate the status “GPS sync” and will answer the requests independent of
the system status (e.g., without external synchronization to the GPS satellites).
10.6.2 Connecting the Antenna after Operation without Antenna
Because in this mode the HOPF6842 has no external synchronization by the satellites,
the drift of the crystal against the GPS system depends on the history of the component.
After a long period of operation without antenna signal, the time difference to UTC
may be several minutes. Connecting the antenna at this moment, the behaviour of the
HOPF6842 will depend on the actual seen satellites and the accuracy of the position
entry . When the HOPF6842 has a new calculated time, then the internal clock is set
to this new value. As result of this operation the SPPA-T3000 components will see
a time jump and continue as described above. To avoid this time jump, connecting
the antenna to the HOPF6842 should be done while the SPPA-T3000 system is not
running.
To shorten the period between operation mode without antenna and operation mode
with antenna, the second, not connected HOPF6842 can be prepared and connected to
the antenna. This HOPF6842 should not have the special DIP-switch setting described
above. When the HOPF6842 has reached the high accurate mode with external
synchronization,
• the SPPAT3000 system will be stopped
• the connection of the first HOPF6842 to the Automation Highway is plugged off
• the connection to the second HOPF6842 with external synchronization to the
Automation Highway is plugged in
• the SPPAT3000 system will be restarted
Now the first HOPF6842 will be prepared for operation with external synchronization,

.e.g. at the LAN board 7270 the special DIP-switch setting will be reset to the standard
mode. Then the HOPF6842 will be connected to the antenna and when the system
has reached the high accurate mode with external synchronization it can be reconnected
with the Automation Highway.
It may be a good way to make a master reset to set the system into a defined mode
and compare the time values of both HOPF6842 before connecting the HOPF6842 to
the Automation Highway.

11 APPENDIX - IEEE1588 (PTP) SUPPORTED BY SCALANCE SWITCHES
11 Appendix - IEEE1588 (PTP) supported by SCALANCE Switches
The feature IEEE 1588 (PTP) is available since firmware version 3.5.0 for the following
SCALANCE X-300 switches which are available for SPPA-T3000:
• SCALANCE X-308-2M
• SCALANCE XR-324-12M / -4M
The update of a SCALANCE switch is based on two steps:
1. Firmware file (*.lad)

2. FPGA file (*.bit)
Both files must be loaded by the regular firmware update of the switch. It is recom-
mended to load the firmware file first. After successfully loading and running the latest
firmware version, the FPGA can be updated to its latest version.
The following screenshots show the WBM menu of a SCALANCE switch where firmware
and FPGA versions are shown.
Figure 63: Scalance X-300 System Version Numbers
The latest firmware version for SCALANCE X-300 is V4.0.4 (wV404008.lad) The latest
FPGA revision is shown in the subsequent table:

11 APPENDIX - IEEE1588 (PTP) SUPPORTED BY SCALANCE SWITCHES
Product name Product number FPGA Update File

SCALANCE X-308-2M 6GK5308-2GG00-2_A2 x308_2m-V173003.bit (Rev. 4)
introduced with V3.9.3
SCALANCE X-324-4M / 12M 6GK5324-0GG00-__R2 xxr324-V162007_Rev9.bit
introduced with V3.9.3
Table 11: Product related FPGA version

LIST OF FIGURES
List of Figures
1 Previous View / Next View buttons in Adobe reader toolbar . . . . . . . 6

2 Sample SPPA-T3000 Network . . . . . . . . . . . . . . . . . . . . . . . 11
3 Buerk Mobatime DTS4138S Front View . . . . . . . . . . . . . . . . . 13
4 Buerk Mobatime DTS 4130S Front View . . . . . . . . . . . . . . . . . 15
5 Buerk Mobatime DTS 4128 Front View . . . . . . . . . . . . . . . . . . 16
6 Buerk Time Server in redundant configuration with one antenna, “Mas-
ter” / “Slave” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7 Buerk Time Server in redundant configuration, “Master” / “Slave” . . . 18
8 DTS4138NW.conf; DTS4148NW.conf . . . . . . . . . . . . . . . . . . . 20
9 Example: Plant Specific Network Adaptions on DTS4148NW.conf . . . . 21
10 DTS4148S Network Ports . . . . . . . . . . . . . . . . . . . . . . . . . 21
11 USB plugged in message . . . . . . . . . . . . . . . . . . . . . . . . . . 21
12 Copy and Rename the necessary Configuration File . . . . . . . . . . . . 24
13 Adaptions of the Network Settings in the Configuration File . . . . . . . 25
14 IP Address of the Redundant Time Server . . . . . . . . . . . . . . . . . 26
15 USB Plugged in Message . . . . . . . . . . . . . . . . . . . . . . . . . 26
16 Maintenance – Update Software . . . . . . . . . . . . . . . . . . . . . . 27
17 Maintenance Window - Update in Progress . . . . . . . . . . . . . . . . 28
18 Initial SSH Session DTS4138S . . . . . . . . . . . . . . . . . . . . . . . 29
19 MAIN SELECTION menu DTS4138S . . . . . . . . . . . . . . . . . . . 30
20 Serial Connection per HyperTerminal DTS4128 . . . . . . . . . . . . . . 31
21 MAIN SELECTION menu DTS4128 . . . . . . . . . . . . . . . . . . . . 32
22 General Settings Window DTS4138 . . . . . . . . . . . . . . . . . . . . 33
23 NETWORK Menu DTS4128 . . . . . . . . . . . . . . . . . . . . . . . . 34
24 NETWORK GENERAL Menu DTS4138S . . . . . . . . . . . . . . . . . 35
25 NETWORK IPV4 Menu DTS4138S . . . . . . . . . . . . . . . . . . . . 36
26 TIME ZONE Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

LIST OF FIGURES
27 SNMP CONFIGURATION menu DTS4130S . . . . . . . . . . . . . . . 38

28 SNMP V1/V2c CONFIGURATION menu DTS4130S . . . . . . . . . . . 39
29 NETWORK SERVICES menu DTS4130S . . . . . . . . . . . . . . . . . 40
30 GENERAL SETTINGS Menu DTS4130 . . . . . . . . . . . . . . . . . . 41
31 TIME SOURCE Menu DTS4128 . . . . . . . . . . . . . . . . . . . . . 42
32 TIME ADJUSTMENT CONFIGURATION Menu DTS4148S . . . . . . . 43
33 REDUNDANT OPERATION Menu DTS4138S . . . . . . . . . . . . . . 44
34 DCF Output Menu DTS4128 . . . . . . . . . . . . . . . . . . . . . . . 45
35 DTS4138S / DTS4148S Network Ports . . . . . . . . . . . . . . . . . . 46
36 PTP Configuration Page 1 . . . . . . . . . . . . . . . . . . . . . . . . . 47
37 PTP Configuration Page 2 . . . . . . . . . . . . . . . . . . . . . . . . . 48
38 SINEC menu DTS4148S . . . . . . . . . . . . . . . . . . . . . . . . . . 49
39 SINEC menu DTS4130 . . . . . . . . . . . . . . . . . . . . . . . . . . 50
40 IEEE 1588v2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
41 Transparent Clock Configuration . . . . . . . . . . . . . . . . . . . . . 55
42 Port Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
43 Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
44 Local Time Synchronization of 12 AS-S7 CPUs . . . . . . . . . . . . . . 59
45 Local and Remote Time Synchronization of 10 AS-S7 CPUs . . . . . . . 60
46 Local and Remote Time Synchronization of 10 AS-S7 CPUs . . . . . . . 61
47 Local and Remote Time Synchronization larger than 12 AS-S7 CPUs;
Additional Switches; Media Converters . . . . . . . . . . . . . . . . . . 62
48 Star Topology for best SOE accuracy (1ms-SOE) Local and Remote Time
Synchronization larger than 12 AS-S7 CPUs . . . . . . . . . . . . . . . 63
49 Ring Topology: SIMATIC Protocol for AS-S7 and PTP for AS/CS3000 . 64
50 PRP Network: SIMATIC Protocol for AS-S7 and PTP for AS/CS3000 . 65
51 Multi-Unit Configuration: SIMATIC Protocol for AS-S7 and NTP for all
other Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
52 Migration Configuration with two DTS4130S . . . . . . . . . . . . . . . 80

LIST OF FIGURES
53 Migration Configuration with two DTS4138S . . . . . . . . . . . . . . . 81

54 GPS Satellite Orbits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
55 GPS antenna installation with reduced view range . . . . . . . . . . . . 83
56 2D-Position calculation depending on transfer time . . . . . . . . . . . . 84
57 Unprecise position calculation depending on erroneous transfer time . . . 84
58 2D-Position calculation depending on data from 3 satellites . . . . . . . 85
59 Logical NTP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
60 HOPF6842 - Login Screen . . . . . . . . . . . . . . . . . . . . . . . . . 96
61 HOPF6842 - Activating NTP . . . . . . . . . . . . . . . . . . . . . . . 97
62 HOPF6842 - Definition of Stratum for Crystal Mode . . . . . . . . . . . 98
63 Scalance X-300 System Version Numbers . . . . . . . . . . . . . . . . . 103

Security information
Siemens provides products and solutions with industrial se-

curity functions that support the secure operation of plants,
systems, machines and networks.
Get more information
In order to protect plants, systems, machines and networks
Comprehensive information concerning against cyber threats, it is necessary to implement – and
the control system for power generation: continuously maintain – a holistic, state-of-the-art industrial
security concept. Siemens’ products and solutions only form
www.siemens.com/sppa-t3000 one element of such a concept.
Email: sppa-t3000.energy@siemens.com Customer is responsible to prevent unauthorized access to its
plants, systems, machines and networks. Systems, machines
and components should only be connected to the enterprise
Siemens AG network or the internet if and to the extent necessary and
with appropriate security measures (e.g. use of firewalls and
Process Industries and Drives network segmentation) in place.
Automation and Engineering Additionally, Siemens’ guidance on appropriate security mea-
76181 Karlsruhe sures should be taken into account. For more information
about industrial security with regard to SPPA-T3000, please
Germany visit the Siemens Customer Portal. Due to the character of
the information provided, the Customer Portal is exclusive to
c Siemens AG 2019 registered Siemens customers using SPPA-T3000. If you are
Subject to change without prior notice a SPPA-T3000 user, but not registered yet, please approach
your local Siemens partner or apply for registration by using
Administrator Manual the “Register” function on the Customer Portal website:
Time Synchronization http://www.siemens.com/cp4ic
If you are also using other Siemens systems in addition to
SPPA-T3000, please make sure to check this website, which
AL: N includes all of the information and the procedures recom-
mended by Siemens:
ECCN: N http://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous devel-
The information provided in this technical description merely opment to make them more secure. Siemens strongly recom-
contains general descriptions or characteristics of perfor- mends to apply product updates as soon as available and to
mance which in actual use do not always apply as described always use the latest product versions. Use of product ver-
or which may change as a result of further development of sions that are no longer supported, and failure to apply latest
the products. An obligation to provide the respective char- updates may increase customer’s exposure to cyber threats.
acteristics shall only exist if expressly agreed in the terms of To stay informed about product updates with regard to
contract. Availability and technical specifications are subject SPPA-T3000 please refer to the above mentioned Customer
to change without notice. Portal, with regard to other Siemens systems please sub-
All product designations may be trademarks or product scribe to the Siemens Industrial Security RSS Feed under
names of Siemens AG or supplier companies whose use by http://www.siemens.com/industrialsecurity.
third parties for their own purposes could violate the rights
of the owners.

AdminManual TimeSynchronization

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AdminManual TimeSynchronization

Uploaded by

Copyright:

Available Formats

.

2 Time Server in SPPA-T3000 Networks 11

3 Initial Configuration of Buerk Mobatime Time Servers 19

c Siemens AG 2019. Unrestricted. All rights reserved. 3

3.5.7 LAN Port Configurations on the DTS4138S / DTS4148S . . . 45

4 Usage of Network Components in the Time-Net 51

5 Appendix - Illustrations of Different Scenarios for HPT 59

6 Appendix - Basic Configurations provided on the USB Stick 67

7 Appendix - Migration SPPA-T2000 to SPPA-T3000 80

8 Appendix - Basics of GPS Time Synchronization 82

9 Appendix - Time Synchronization in Ethernet Networks 87

10 Appendix - HOPF Time Server - GPS Satellite Clock HOPF6842 91

4 c Siemens AG 2019. Unrestricted. All rights reserved.

10.1 Hardware of HOPF6842 . . . . . . . . . . . . . . . . . . . . . . . . . 91

11 Appendix - IEEE1588 (PTP) supported by SCALANCE Switches103

c Siemens AG 2019. Unrestricted. All rights reserved. 5

Within this document cross-reference links are used.

Figure 1: Previous View / Next View buttons in Adobe reader toolbar

6 c Siemens AG 2019. Unrestricted. All rights reserved.

The main aspects of this document are:

• Installing advices of the Time Server hardware

1.2 Purpose of the document

• NTP – Network Time Protocol

The pictures shown in Appendix 5 illustrate several scenarios. Initial information is

c Siemens AG 2019. Unrestricted. All rights reserved. 7

1.4 Notational Conventions

The following notational conventions are used in this manual:

Pay particular attention to texts marked with this symbol.

Additional notes and tips.

Table 1: Notational conventions

1. RFC 1305 - NTP Protocol Specification, Version 3 (http://rfc.net/rfc1503.

8 c Siemens AG 2019. Unrestricted. All rights reserved.

13. HOPF Elektronik GmbH : Technical Description LAN Board 7271

AS: Automation Server

c Siemens AG 2019. Unrestricted. All rights reserved. 9

SFTP: SSH File Transfer Protocol

10 c Siemens AG 2019. Unrestricted. All rights reserved.

2 Time Server in SPPA-T3000 Networks

2.1 Implementation at SPPA-T3000

A sample configuration for a SPPA-T3000-based solution is given in Figure 2.

Figure 2: Sample SPPA-T3000 Network

In SPPA-T3000 the following components have to be time-synchronized:

• Thin Clients connected to the Application Highway

c Siemens AG 2019. Unrestricted. All rights reserved. 11

2.2 Buerk Mobatime Time Servers

For time synchronization in SPPA-T3000, network Time Servers manufactured by Buerk

2.3 Buerk Mobatime DTS4138S and DTS4148S

12 c Siemens AG 2019. Unrestricted. All rights reserved.

Figure 3: Buerk Mobatime DTS4138S Front View

Both Time Servers are equipped with:

c Siemens AG 2019. Unrestricted. All rights reserved. 13

Further information is provided in [2] and [3].

2.3.1 PTP by DTS4148S

14 c Siemens AG 2019. Unrestricted. All rights reserved.

2.4 Buerk Mobatime DTS4130S

Figure 4: Buerk Mobatime DTS 4130S Front View

The Time Server DTS4130S is equipped with:

• 1x Terminal Sub-D 9pin RS232 for local operation control

Further information is provided in [4].

c Siemens AG 2019. Unrestricted. All rights reserved. 15

2.5 Buerk Mobatime DTS4128

Figure 5: Buerk Mobatime DTS 4128 Front View

The Time Server DTS4128 is equipped with: