Table of Contents

1. Introduction ........................................................................................................................................... 2
2. Methods for Network Time Synchronization ........................................................................................... 2
2.1 Network Time Protocol....................................................................................................................... 2
2.1.1 Time Server Scheme using NTP .................................................................................................. 2
2.1.2 Hardware Requirements............................................................................................................... 3
2.2 Precision Time Protocol (PTP) ........................................................................................................... 3
2.2.1 Time Server Scheme using PTP................................................................................................... 3
2.2.2 Hardware Requirements............................................................................................................... 4
2.3 IRIG-B Protocol .................................................................................................................................. 4
2.3.1 Time Server Scheme using IRIG-B ............................................................................................. 5
 1. Introduction
A standard PC’s real-time clock is based on a crystal oscillator, identical to the components found in an
everyday watch or clock. Like a watch or clock, they typically drift over time. In a network environment,
this can cause real problems. Distributed computer systems initially synchronized to the same time, over a
period of only a few hours will have significantly differing system times. Networks of computers all need
to be synchronized to the same time, so that events occur in an organized, predetermined manner.

2. Methods for Network Time Synchronization

2.1 Network Time Protocol

NTP synchronizes servers and network devices using a reliable time source,such as a dedicated network
time server that references the GPS. It uses the UDP. A client initiated packet is time-stamped by the
client and the time server; the result is that the client removes its time offset relative to the network time
server. Many operating systems and network devices already incorporate support for NTP.

2.1.1 Time Server Scheme using NTP

The architecture for the implementation of NTP sever will be as follows

NMEA
GPS Data Master Network All Other
with PPS Controller Switch Systems
(QNX)
NTP Stratum-1 Server NTP Stratum-2 Servers/ NTP Clients
 GPSd is a software application that receives timing and positioning information from a generic GPS
receiver and provides the information to other applications via a standard software interface. In this
manner NTPd can be used to pass timing information from a range of GPS receivers to the NTP
application to provide timing.

GPS satellite has a very accurate atomic clock onboard which are synchronized to a ground based
stations, so that each satellite has the same time. So here we are using reference clock as GPS (Stratum-
0).

We need to configure a controller as NTP Server. The NTP protocol was originally developed for the
LINUX operating system. Traditionally a GPS NTP server would be based on x86 PC type architecture
running LINUX or similarly derived operating systems. However, recently the move towards lower cost
ARM based technology with the ability to run LINUX there has been a surge of GPS referenced NTP
installations on ARM processors.
Low cost processor boards such as the Raspberry Pi have seen implementations of GPS referenced NTP
servers, particularly with hobbyist developers.

2.1.2 Hardware Requirements

GPS module: Garmin GPS-18x

2.2 Precision Time Protocol (PTP)

The IEEE 1588 standard specifies a protocol to synchronize independent clocks running on separate
nodes of a distributed control system to a high degree of accuracy and precision. The clocks communicate
with each other over a communication network. In its basic form, the protocol is intended to be
administration-free. The protocol generates a master-slave relationship among the clocks in the system by
determining which of the possible sources has the better accuracy. All clocks ultimately derive their time
from a clock known as the grandmaster clock.
Once all the clocks in a control system share a synchronized, common understanding of system time,
events being monitored in the control system can be time stamped to a very high degree of accuracy.

2.2.1 Time Server Scheme using PTP

The architecture for the implementation of PTP for time server will be as follows

NMEA
GPS Data Master Network All Other
with PPS Controller Switch Systems
(QNX)
GrandMaster Clock Client Systems
PTP is multicast from the time server. The server multicasts transmits a packet to a number of clients,
who timestamp the packet the packet as it arrives (T2).The server then multicasts a follow-up message
contain the timestamp (T1) of the first message at the time of transmission. Each client then sends unicast
a packet to the server, timestamping it with the time of transmission (T3). When the server receives the
packet, it timestamps it (T4) and sends the value T4 to that client as a follow-up message. The client then
has all four timestamps.

2.2.2 Hardware Requirements

GPS module: Garmin GPS-18x

2.3 IRIG-B Protocol

IRIG-B is a complete serial time code that occurs once per second and, depending on the configuration,
contains the day of year, hours, minutes, seconds, year and other important information. All Arbiter
clocks transmit Format B with four variations as seen in Table 2. Note that with the newer IRIG Standard
200-04, new code designations have appeared: BCD YEAR is now part of the 30 bits of BCD code.
Arbiter Systems is not currently using BNC YEAR in its clocks.

The IRIG-B time code consists of 100 bits produced every second, 74 bits of which contain various time,
date, time changes and time quality information of the time signal. Consisting of logic ones, zeros and
reference bits, the time code provides a reliable method of transmitting time to synchronize a variety
equipment.
 2.3.1 Time Server Scheme using IRIG-B

The IRIG 200-04 standard does not define specific signal levels for IRIG-B.
Typical techniques for transmission of unmodulated IRIG-B (DCLS) include:
 Point to point connection of a 5V signal over coaxial cable
 Multi-point distribution of a 5V signal over shielded twisted-pair cable
 Multi-point distribution using 24 Vdc for signal and control power
 Multi-point RS-485 differential signal over shielded twisted-pair cable
 RS-232 signal over shielded cable (point to point, short distances only)
 Optical fiber
Typical techniques for transmission of modulated IRIG-B include:
 Coaxial cable, terminated in 50 ohms or higher, point-to-point
 Shielded twisted-pair cable, with optional termination (100 ohms)

Make IRIG-B as time source, then sync all systems with each other using PTP. A PTP slave can also
output IRIG-B to devices that do not support PTP.

PPS
GPS IRIGB- Master Ethernet All other
with PPS Source Controller Switch systems

Grand Master Clock Client Systems