IEEE-1588 PTP Grandmaster - DTS 4163

HSR (High-availability Seamless Redundancy) is a fault-tolerant Ethernet protocol specified in IEC 62439-3, designed for applications where continuous data transmission is critical. It operates using a ring or mesh topology, where each node simultaneously sends duplicate Ethernet frames in both directions. This ensures that even if one link fails, the other path still delivers the data with zero recovery time, making HSR highly suitable for real-time, mission-critical systems such as substation automation, industrial control, and transportation.

A key difference between HSR and PRP (Parallel Redundancy Protocol) lies in their network topology and implementation approach:

• HSR uses a single network infrastructure with a ring or mesh configuration, allowing for compact or space-constrained installations without the need for separate switches or links. Each device must be HSR-capable and interconnected in the ring.

• PRP, by contrast, requires two completely separate LANs (LAN A and LAN B), with each device transmitting duplicate frames over both networks.

Only few devices like the DTS 4163.grandmaster support both HSR and PRP protocols as defined in IEC 62439-3. This allows the device to be used in a range of redundant network configurations, including HSR ring topologies, PRP dual-network setups, and in some cases, hybrid environments.

PRP (Parallel Redundancy Protocol) is a fault-tolerant Ethernet protocol defined in IEC 62439-3. It ensures zero recovery time by transmitting identical Ethernet frames simultaneously over two separate and independent LANs—referred to as LAN A and LAN B. Each PRP-capable device uses two network interfaces and remains fully operational even if one of the networks fails. The receiving device accepts the first-arriving frame and discards the duplicate, avoiding retransmissions or delays and maintaining uninterrupted communication.

Compared to HSR (High-availability Seamless Redundancy), PRP offers full physical separation of network paths, which provides enhanced fault isolation and the ability to reuse existing network infrastructure. However, this comes at the cost of double the cabling, switches, and ports, which can increase system complexity and space requirements.

• PRP is ideal for larger or existing installations where dual independent networks are already in place or where redundancy with maximum physical separation is required.

• HSR, in contrast, uses a single-ring or mesh topology and achieves redundancy by sending duplicate frames in opposite directions through the same network infrastructure, making it more suitable for compact, distributed systems.

Only few devices like the DTS 4163.grandmaster support both HSR and PRP protocols as defined in IEC 62439-3. This allows the device to be used in a range of redundant network configurations, including HSR ring topologies, PRP dual-network setups, and in some cases, hybrid environments.

PTP profiles are standardized sets of configuration parameters tailored to specific industries or use cases. For example:

• The Power Profile (IEC 61850-9-3) is used in substations and utility automation, prioritizing reliability and deterministic behavior.
• The Telecom Profiles (ITU-T G.8275.1 and G.8275.2) are used in mobile networks for phase and frequency synchronization.

These profiles ensure interoperability and simplify deployment within each domain.

The Precision Time Protocol (PTP), defined by IEEE 1588, is a network protocol that synchronizes clocks throughout a network with sub-microsecond accuracy. It is critical in applications where precise timing is essential, such as energy systems, industrial automation, financial trading, and broadcasting. PTP achieves this high accuracy through hardware timestamping and delay compensation techniques.

Such considerations are important for hierarchically structured time server structures. The stratum level “0” always refers to the time server on the top level, which functions as the reference time source of the overall system, for example, by means of exact DCF / GPS synchronization. The level below, along with the time servers located there – which in turn synchronize themselves to level “0” – is given the stratum level “1” accordingly. Levels further below therefore add up the stratum level “n + 1”. As a rule, a maximum of 16 stratum levels are defined.

You’ll find it directly on the license web site – After entering the license number and filling out the registration form you will be able to download the license file and the newest MOBA-NMS software 32-bit or 64-bit version.

Link to the license page: https://nms-webportal.mobatime.com/license/login

To get a valid license you need to order a MOBA license from us. As soon as we receive the request, we will send you a PDF including the license key. In the PDF you will find a link, which leads to a landing page of us, which asks you to enter the license key. As soon as you have entered the key, your license is activated.

ATTENTION: a license is only for one workstation and should be activated by the responsible employee.

As a rule, NTP clients send a request packet every 64 seconds at most. With a device code of 100 “requests per second”, 6,400 NTP clients could already be synchronized in the network. For example, if you use the DTS 4160 time server with 10,000 “requests per second”, there are even 640,000 clients that could be synchronized with this type of time server in the network. Since more current NTP versions increase the polling interval by a factor of 16 with stable time synchronization, this results in an even greater number of possible NTP end devices. One should therefore take this fact into account when selecting the device specification that is really necessary for the specific need. For larger networks, it is also common that hierarchical time server structures – consisting of several network segments or levels, each with an assigned time server – are created. In this way, the time servers of the lower level always synchronize to the higher level right down to the central time server. This central time server typically has the highest performance features and is often redundant.

Our tutorial videos will help you with the procedure for commissioning a DTS device in a network without dynamic IP address assignment DHCP. You will be shown how to make the settings on the DTS device and how to assign the IP address.

What is supplied by MOBATIME?

• DTS device (e.g. DTS 4801.masterclock)
• Rack mounting material
• Terminal opener-tool

What do you need to be ready?

• PC or Laptop
• Switch
• Serial cable (SUB.D9 pole, 0-modem (crossed))
• USB Serial Adapter (only if you don’t have a serial input on your device)
• Power cable
• Network (LAN) cable

You need to download the following software:

• PuTTY
• MOBA NMS !Attention, you need a valid license! (How to I get a valid MOBA-NMS licence?)

Below you will find our six tutorial videos that will help you complete the initial installation:

1. Identify PC COM Port
2. Open PuTTY
3. Configuration of DTS Menu IP in PuTTY
4. Define PC/Laptop IP
5. Add Single Device in MOBA-NMS
6. Select synchronization source in MOBA-NMS