Showing results for 
Search instead for 
Did you mean: 
Cisco Employee
Cisco Employee

Quick Reference: Cisco IE5000 IRIG-B Support

Cisco Industrial Ethernet 5000 series switches (IE 5000) have integrated hardware support for external time sources: GPS antenna and IRIG-B (analog and digital timing I/O) interfaces. These interfaces are complemented with network time distribution protocols like Precision Time Protocol (PTP) and Network Time Protocol (NTP) making the IE 5000 a robust hardened industrial platform with strong precision timing capabilities.

This quick reference document focuses on the IE 5000’s IRIG-B capabilities: support, configuration, and verification.

IRIG-B: Background information

The Inter-Range Instrumentation Group (IRIG) time codes are the result of the US military’s need to standardize test ranges’ timing codes towards the end of the 1950s. This standardization resulted in a common set of time codes that eliminated incompatibility challenges and allowed for the exchange of synchronized test data across ranges. Six IRIG codes variations were developed (A, B, D, E, G, H) of which IRIG time code B (IRIG-B) became widely accepted for time distribution with power, industrial automation, and control industries.

Quick Note on IRIG-B

  • The IRIG standard was first published in 1960 with the latest version, IRIG standard 200-04, “IRIG Serial Time Code Formats,” updated in September 2004.
  • The IRIG-B time protocol is widely used by electric utilities and other verticals to establish and maintain time synchronization between system devices (e.g., power breakers, relays, meters, etc.)
  • IRIG sends a complete time frame once per second, and each frame is composed of 100 bits
  • It contains time-of-year and year information in a BCD format, and (optionally) seconds-of-day in SBS.
  • Though it is considered to be a reliable and predictable timing source distribution framework (dedicated timing signals) it traditionally relies on a precise timing source, e.g., GPS.

Today, it is believed that ~90% of substations have IRIG-B installations. Modern substation automation networking devices, especially those providing timing / synchronization, should include support IRIG-B. This support in combination with newer, more precise, cost effective, and reliable timing technologies, should safely accelerate substation automation modernization efforts.

IRIG-B: IE 5000 Support Overview

The IRIG protocol in the IE 5000 has been implemented for format-B (IRIG-B) per IRIG standard 200-04 with capabilities to receive (INPUT) or transmit (OUTPUT) 4x Analog (AM) and 4x Digital (TTL) time code formats, see table below.

IE5000 IRIG-B Modes

Format ID

IRIG Signal

Analog (AM)



Amplitude Modulated, 1kHz / 1ms resolution, BCDTOY



Amplitude Modulated, 1kHz / 1ms resolution, BCDTOY, SBS



Amplitude Modulated, 1kHz / 1ms resolution, BCDTOY, BCDYEAR



Amplitude Modulated, 1kHz / 1ms resolution, BCDTOY, BCDYEAR, SBS


Digital (TTL)



Unmodulated, DCLS, pulse-width-coded, BCDTOY



Unmodulated, DCLS, pulse-width-coded, BCDTOY, SBS



Unmodulated, DCLS, pulse-width-coded, BCDTOY, BCDYEAR



Unmodulated, DCLS, pulse-width-code, BCDTOY, BCDYEAR, SBS


IRIG-B INPUT and OUTPUT vs. Time Sources

The IE 5000 hardware has 2 physical interfaces (details in a following section), one for analog (AM) and one for digital (TTL), with INPUT or OUTPUT signal capabilities per interface.

This IRIG-B INPUT / OUTPUT signaling support allows the IE 5000 to be a central timing device in multiple use-cases:

  • INPUT: The IE 5000 receives IRIG-B timing signaling (AM or TTL) from an IRIG-B time source if only available or so required. In this case IRIG-B can be used as the IE 5000’s clock source for PTP (only) - IE 5000 configured as Grand Master Clock (GMC) for time distribution.

  • OUTPUT: The IE 5000 utilizes other precise timing sources, e.g., GNSS/GPS, PTP, NTP, as a clock source. The IRIG-B interface(s) can be used to transmit timing signal to IRIG-B dependent devices in location.

Basically, the IE 5000 supports IRIG-B IN and IRIG-B OUT in addition to the GNSS/GPS interface. The following table shows the mapping of Time Source to time distribution protocol alignment (i.e. one will serve as time source to the other).

Time Source


Time Distribution








IRIG-B: IE 5000 Software and Hardware

IOS Software Requirements

As of this publication the latest IE 5000 IOS software supports IRIG-B INPUT and OUTPUT capabilities. However, the following table shows the minimum IOS versions required to support either IRIG-B signaling direction. As always, please review version release notes and follow Cisco’s recommendations before upgrading IOS versions in your IE 5000.

IRIG-B Direction

Minimum IOS support






IRIG-B Physical Interface Characteristics

As mentioned earlier, the IE 5000 has two IRIG-B physical interfaces. The following image and table describe the physical characteristics. Customers will need to purchase or build cables for their IRIG-B connectivity following the IRIG-B standard and IE 5000’s specifics. These cables are NOT provided with the platform.

Screen Shot 2021-03-31 at 2.27.55 PM.png

IRIG-B Interface


Input High Impedance

Digital Timing I/O

mini-BNC (female)

~1 mega-Ohm

Analog Timing I/O

mini-BNC (female)

~8 kilo-Ohm


Note: IRIG Impedance and mini-BNC connectors


Configuration Scenario: IRIG-B OUT and IRIG-B IN

Screen Shot 2021-04-08 at 7.02.52 AM.png

This configuration scenario shows two IE 5000 platforms configured to use IRIG-B signaling in different ways. Scenario context:

  1. Time source GNSS/GPS, IRIG-B TTL07 OUT for time distribution - IE 5000 (v23-ie5000-2)
  2. Time source IRIG-B TTL07 IN, PTP for time distribution - IE 5000 (v23-ie5000-4)

NOTE: Please check the reference section for links to the IE 5000's GNSS/GPS and PTP configuration guides.

IRIG-B Configuration Statement

A single IRIG-B configuration command statement is used for IRIG-B mode and signal direction (IN and OUT) per interface - a total of two possible IRIG-B configuration statements.

Configuration Command >> irig mode <mode> dir <in/out>

CLI view of configuration options:

v23-ie5000-4(config)#irig mode ?
AM02 AM-B122 format
AM03 AM-B123 format
AM06 AM-B126 format
AM07 AM-B127 format
TTL02 TTL-B002 format
TTL03 TTL-B003 format
TTL06 TTL-B006 format
TTL07 TTL-B007 format

v23-ie5000-4(config)#irig mode TTL07 dir ?
in input direction
out output direction


A. Time Source GNSS/GPS, IRIG-B OUT for Time Distribution

This IE 5000 (v23-ie5000-2) is configured to use its GNSS/GPS interface and consequently GPS as its time source - IRIG-B will source its time from GPS. The IRIG-B digital interface is configured to provide timing signal (OUT) to the other IE 5000 (v23-ie5000-4).

v23-ie5000-2(config)#gnss <<<--- Enabling GNSS

v23-ie5000-2(config)#irig mode TTL07 dir out <<<--- IRIG-B mode TTL07 signal, OUTPUT direction


Verifying IRIG-B OUTPUT and GNSS being used as IRIG-B's time source:

v23-ie5000-2#show irig
IRIG-B Digital mode TTL07 dir out <<<--- Confirms IRIG-B mode and direction as configured (OUT)
IRIG-B Analog mode disabled

IRIG-B Clk Id 3 Source GNSS time: Year: 2021 Day: 98 Hour 15 Min 7 Sec 20 <<-- GNSS Clock source
                            ns 1617894440419015968 (0x1673EA6BED413D20)

IRIG-B Virtual Clock State: INACTIVE <<<--- IRIG-B clock inactive, not an internal time source

*** IRIG-B input is disabled ***


B. Time Source IRIG-B IN, PTP for Time Distribution

This IE 5000 (v23-ie5000-4) is configured to receive IRIG-B TTL07 (IN) timing signal from the other IE 5000 (v23-ie5000-2) and use it as its time source. This in turn will be used as the timing source for PTP for time network distribution. No other timing sources or protocols are configured.

v23-ie5000-4(config)#ptp mode gmc-bc delay-req <<<--- IE5000 configured for PTP as GMC-BC

v23-ie5000-4(config)#irig mode TTL07 dir in <<<--- IRIG-B mode TTL07 signal, INPUT direction


Verifying IRIG-B INPUT as time source and PTP sourcing time from IRIG-B:

v23-ie5000-4#show irig
IRIG-B Digital mode TTL07 dir in <<<--- Confirms IRIG-B mode and direction as configured (IN)
IRIG-B Analog mode disabled
IRIG-B Clk Id 2 Source IRIG-B time: Year: 2021 Day: 98 Hour 15 Min 7 Sec 20 <<-- IRIG-B source
                            ns 1617894440918157031 (0x1673EA6C0B0186E7)
IRIG-B Virtual Clock State: ACTIVE <<<--- IRIG-B clock active, time source possible for PTP
*** IRIG-B TTL input mode ***
B007 : Year 21 Day 98 Hour 15 Min 7 Sec 19 SBS 0xD4A7(54439) <<-- TTL-B007 signal received
NOTE: Input time shown is the last received frame time


Verifying PTP protocol recognizing IRIG-B as its clock source:

v23-ie5000-4#sh ptp time-property
  Current UTC offset valid: FALSE
  Current UTC offset: 0
  Leap 59: FALSE
  Leap 61: FALSE
  Time Traceable: FALSE
  Frequency Traceable: FALSE
  PTP Timescale: FALSE
  Time Source: Other <<--- This denotes IRIG-B (see NOTE below)

NOTE: Time source "Other" is used to identify IRIG-B as there is no IRIG classification in PTP messaging. If NTP was configured as as the source then it would show "Time Source: NTP".


Additional Resources

Level 1
Level 1

Ok, thanks.

just to get re-asurance: the IE5000 when sync'd with IRIG-B can not be configured to distribute the time as NTP clock source to attached computers, only PTP is supported.
Is that correct? That is what I understand from the description. It would be ok, just has influence on the time system design.

Cisco Employee
Cisco Employee
That is correct. Please reach out if you have any questions or want to discuss your timing deployment designs.
Level 1
Level 1

Great content! Related question: The IRIG connectors visually do look like BNC (Mini-BNC?); but what about the GNSS port?   Are they mini BNC? Normal BNC?  Micro BNC?  I checked the normally extremely detailed Cisco hardware installation guide for the IE-5000 and to my surprise no mention

Level 1
Level 1

> but what about the GNSS port?

They are SMA connectors (female).

Level 1
Level 1

Thanks for this article. Related question: We are trying to distribute IRIG-B with PTP from a satellite clock as the time source. However, we noticed that the IE5000 does not apply the TAI to UTC offset (37 seconds as of today) to the IRIG-B time out. Since IRIG-B is always UTC, all end devices are receiving a time different than UTC causing problems in the system. Is there something that we are missing to fix this?





Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links