Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Introduction

The Precision Time Protocol (PTP) is a protocol used to synchronize clocks throughout a computer network. On a local area network, it achieves clock accuracy in the sub-microsecond range, making it suitable for measurement and control systems.

If LAN synchronization is used, PTP is used to synchronise the N870 base stations.

  • The N870 can be an PTP Master
  • PTP deviation must be lower then 500 ns
  • PTP deviation > 500 ns might just generate warnings. If deviation is continuously exceed 500 ns then PTP is considered broken and new synchronisation procedure is started and can take up to 30 seconds
  • Other devices can also be an PTP Master see for example the wikipedia page
  • Switches do not need to be PTP aware but the settings should consider the mentioned guidelines
  • Using PTP Domains, we can create multiple PTP domains in case the network topology is causing PTP delays or other PTP issues. See below for more info and examples.
Domains

A domain is an interacting set of clocks that synchronize to one another using PTP. Clocks are assigned to a domain by virtue of the contents of the Subdomain name fields in PTP messages they receive or generate. Domains allow multiple clock distribution systems to share the same communications medium.

In the N870 you can create Clusters : SETTINGS - Base stations - Synchronisation. These clusters are used for DECT and LAN synchronisation.

The settings below shows dependent on the selected cluster, which PTP domain will be used.

N870 Common PTP domainPTP Domain
Cluster 1-c21
Cluster 2-c21
Cluster 3-c21
Cluster 4-c21
Cluster 5-c21
Cluster 6-c21
Cluster 7-c21
N870 Isolated PTPPTP Domain
Cluster 8-i28
Cluster 9-i29
Cluster 10-i30
Cluster 11-i31
Cluster 12-i32
Cluster 13-i33
Cluster 14-i34
Cluster 15-i35


Below is an wireshark example: You can see that the dependent on the Cluster settings, the device will add the subdomainNumber.

Wireshark example

Precision Time Protocol (IEEE1588)
0000 .... = transportSpecific: 0x0
.... 0000 = messageId: Sync Message (0x0)
.... 0010 = versionPTP: 2
messageLength: 44
subdomainNumber: 21
flags: 0x0200
0... .... .... .... = PTP_SECURITY: False
.0.. .... .... .... = PTP profile Specific 2: False
..0. .... .... .... = PTP profile Specific 1: False
.... .0.. .... .... = PTP_UNICAST: False
.... ..1. .... .... = PTP_TWO_STEP: True
.... ...0 .... .... = PTP_ALTERNATE_MASTER: False
.... .... ..0. .... = FREQUENCY_TRACEABLE: False
.... .... ...0 .... = TIME_TRACEABLE: False
.... .... .... 0... = PTP_TIMESCALE: False
.... .... .... .0.. = PTP_UTC_REASONABLE: False
.... .... .... ..0. = PTP_LI_59: False
.... .... .... ...0 = PTP_LI_61: False
correction: 0.000000 nanoseconds
correction: Ns: 0 nanoseconds
correctionSubNs: 0 nanoseconds
ClockIdentity: 0x589ec6fffe0d8c73
SourcePortID: 1
sequenceId: 5275
control: Sync Message (0)
logMessagePeriod: -1
originTimestamp (seconds): 0
originTimestamp (nanoseconds): 0




  • No labels