How to synchronize a Q.station with an external time source

Overview of supported time synchronization protocols and setup instructions

Overview

It is not only for test & measurement of great importance to synchronize clocks of networked devices to timely coordinate data acquisition. In case multiple systems are used during a measurement it is important to have the measurement data synchronized between the systems. Or you can use an external time source to correlate and synchronize measurements anywhere in the world with absolute timing, without requiring a direct connection between the measurement systems.

There are several other techniques for synchronizing controllers to an external clock, each with advantages and disadvantages. In the following sections, the different protocols that are supported by the Q.series controllers will be presented.

Time protocols

*Overview of supported time protocols*
Type	Accuracy	Distance	Medium	Recommended for
GPS	< 1 s	-	USB, RS-232	Long-distance and mobile measurement applications
NTP	< 10 ms (local) < 100 ms (internet)	100 m	Ethernet	Low-speed, distributed measurement systems
PTPv2	< 100 ns	1 km	Ethernet	High-speed, networked measurement systems
IRIG-B	< 100 ns	50 m	TTL, RS-485	Installations with existing IRIG-B signal generator
AFNOR	< 100 ns	50 m	TTL, RS-485	Installations with existing AFNOR signal generator
EtherCAT DC	< 100 ns	100 m	Ethernet	High-precision measurement and control application

Depending on the controller type, up to 3 different time sources can be configured. Depending on availability, the most accurate time source will be selected. The accuracy of the signals is according to this order:

PTPv2/IRIG/AFNOR
NTP
GPS NMEA 0183

GPS NMEA 0183

GPS receivers communicate using several protocols. Of all message standards that are used with GPS receivers, the NMEA 0183 is the most widely used messaging standard. NMEA is the acronym for the National Marine Electronics Association.

The controller supports the following NMEA sentence codes:

$GPRMC (Recommended minimum specific GPS/Transit data)
$GPGGA (Global Positioning System Fix Data)

For more information about setting up NMEA 0183 synchronization see: How to bring GPS signals into a controller.

The NMEA 0183 sentences are not synchronized to be generated at specific intervals. These GPS receivers therefore can only provide an accuracy of plus or minus 1 second.

NTP

NTP stands for Network Time Protocol, and it is an internet protocol used to synchronize the clocks of devices to a certain time reference. NTP uses UTC as reference time.

The pool.ntp.org project is a big virtual cluster of timeservers providing one of the most reliable NTP servers on the internet.

You can install and run an NTP server in your local network when not connected to the internet. Download the free Meinberg NTP installation for Windows here: https://www.meinbergglobal.com/english/sw/ntp.htm.

The controller is set up to synchronize with an NTP server at approx 1 Hz. This can cause up to ~9 MB/day of data traffic. When using an internet NPT server this could result in additional charges depending on your cellular data plan.

To set up the controller as an NTP client, go to Controller settings -> Synchronization in GI.bench. select standard NTP mode and enter the IP address or URL of the NTP server. Optionally you can enter a UTC offset in the Timezone offset parameter.

PTPv2

PTP stands for Precision Time Protocol and is a time synchronization protocol for nodes distributed across a network. Its hardware timestamp feature provides greater accuracy than other time synchronization protocols such as NTP.

PTP is a distributed protocol that specifies how real-time PTP clocks in the system synchronize with each other. These clocks are organized into a master-slave synchronization hierarchy with the grandmaster clock, which is the clock at the top of the hierarchy, determining the reference time for the entire system. An example of a PTPv2 time server is the IEEE-1588 Grandmaster Clock from Meinberg.

Using PTP in a network requires Ethernet switches that support PTP IEEE 1588 V2

To set up the controller as an NTP client, Controller settings -> Synchronization in GI.bench. Select the Controlled sync signal over PTP and set the PTP clock parameters.

After a reboot of the controller, the controller performs a single step to synchronize its local clock with the PTP master clock. If the PTP master clock changes during operation, the controller will adjust its local time in smaller multiples of steps if the time difference is <2 seconds. However, if the time difference exceeds 2 seconds, the controller will execute a single-step synchronization instead.

IRIG-B003/B005

IRIG stands for Inter-Range Instrumentation Group, which refers to a whole group of serial time codes that use a continuous stream of binary data to transmit information on date and time. Individual IRIG code formats are distinguished by names consisting of a letter followed by a 3-digit number. The individual name determines the transmission speed and frame rate, whether the time code is modulated or unmodulated, and the kind of information included in the transmitted data.

The Q.station controllers support the following IRIG signals:

Format	Encoding	Modulation	Carrier	Expressions	Bit rate	Interval
IRIG-B	B003	DCLS	N/A	BCDTOY, SBS	100 pps	1 s
IRIB-B	B005	DCLS	N/A	BCDTOY, BCDYEAR, CF	100 pps	1 s

BCD - Binary Coded Decimal code contains time information including seconds, minutes, hours, and days, recycling yearly (HH, MM, SS, DDD). The BCD time-of-year code (BCDTOY) reads zero (0) hours, minutes, seconds, and the fraction of seconds at 2400 each day and reads day 001 at 2400 of day 365, or day 366 in a leap year. The BCD year code (BCDYEAR) counts years and cycles to the next year on January 1st and will count to the year 2099.
SBS - SBS time-of-day code consists of the total elapsed seconds, recycling daily (0….86400). SBS reads zero (0) seconds at 2400 each day excluding leap second days when a second may be added or subtracted.
CF - The CF group code contains the year, time quality, leap year, pending leap seconds, and parity. Other CF bits are reserved for user-defined purposes, depending on the application.

The Q.station supports IRIG TTL (over I/Os) or IRIG RS-485. To select IRIG time synchronization go to Controller settings -> Synchronization in GI.bench and select IRIG B003 over IOs or IRIB B003 over RS485.

The IRIG-B signal should be connected to DI1 (pin 2) and GND (pin 8) on the digital input connector on the Q.station X. The digital inputs should be configured for TTL logic level.

AFNOR NFS 87-500

The AFNOR stands for Association Française de Normalisation and is a French time code variant of IRIG-B. Within the IRIG-B signal, are 16 bits available for user-definable bits outside of the IRIG standard. These control bits can tell you the health of the clock if a leap second is pending, or the daylight savings offset. AFNOR NFS 87-500 defines what these IRIG-B control bits should be.

EtherCAT Distributed Clock

The basis for deterministic behavior is precise time synchronization. EtherCAT uses a distributed clock (DC) technology per the IEEE 1588 Precision Time Protocol standard. The EtherCAT master acts as the highest-ranking clock, called the grandmaster clock, and synchronizes all other slave clocks. The distributed clock method ensures that the latency offset is compensated between all slave clocks.

Time synchronization via EtherCAT Distributed Clock is available on the Q.station X EC and Q.station 101).

To enable the Distributed Clock in the EtherCAT master, the Sync0 parameter must be activated.

To select EtherCAT DC time synchronization go to Controller settings -> Synchronization in GI.bench and select EtherCAT DC time. Just so you know, no additional configuration settings are required.