IRIG-B To NTP/SNTP Time Code Converter

IRIG-B To NTP/SNTP Time Code Converter
zoom Zoom image

IRIG-B To NTP/SNTP Time Code Converter

  • SY-B-N-01 Irig-B to NTP Converter can transform IRIG-B to NTP/SNTP time code and finally to the server to synchronize the time.
  • Time input: BNC or RS-485/422 block terminal
  • Time output: NTP/SNTP(RJ-45 connector IEEE 802.3 - shielded data line) & RS-232(DB9 Connector)
  • Time accuracy: LAN: ±1ms
  • WAN: ±1~10ms
  • The maximum servers it can support: 22nos
  • Power input: - 110-240V AC 50/60 Hz(Main Power) or 24~72V DC(Redundancy Power)
  • Fuse: - 1 electronic
  • Output: - +5V / 3A
  • Total load ≤15 Watt


  • IRIG-B:

Inter-range instrumentation group time codes, commonly known as IRIG timecodes, were created by the TeleCommunications Working Group of the Inter-Range Instrumentation Group, the standards body of the Range Commanders Council. Work on these standards started in October 1956, and the original standards were accepted in 1960.

The original formats were described in IRIG Document 104-60, later revised and reissued in August 1970 as IRIG Document 104-70, upgraded later that year as the IRIG Document to the status of a Standard, IRIG Standard 200-70. The latest version of the Standard is IRIG Standard 200-04.

The different time codes defined in the Standard have alphabetic designations. A, B, D, E, G, and H are the standards currently defined by 200-04.C was in the original specification, but was replaced by H.

The main difference between codes is their rate, which varies between one pulse per second and 10,000 pulses per second.

  • NTP:

Network Time Protocol (NTP) is a networking protocol for clock synchronization between computer systems over packet-switched, variable-latency data networks

NTP is intended to synchronize all participating computers to within a few milliseconds of Coordinated Universal Time (UTC). It uses a modified version of Marzullo's algorithm to select accurate time servers and is designed to mitigate the effects of variable network latency. NTP can usually maintain time to within tens of milliseconds over the public Internet, and can achieve better than one millisecond accuracy in local area networks under ideal conditions. Asymmetric routes and network congestion can cause errors of 100ms or more.

The protocol is usually described in terms of a client-server model, but can as easily be used in peer-to-peer relationships where both peers consider the other to be a potential time source.Implementations send and receive timestamps using the User Datagram Protocol (UDP) on port number. They can also use broadcasting or multicasting, where clients passively listen to time updates after an initial round-trip calibrating exchange. NTP supplies a warning of any impending leap second adjustment, but no information about local time zones or daylight saving time is transmitted.



  • Five years warranty & life long maintenance
  • Small quantity OEM is acceptable
  • Work Temperature:-20˚C to 75˚C
  • Storage Temperature:-40 to 85℃
  • Ambient Relative Humidity: 10 to 95%(Non-condensing)





Request a quote

Powered by ChronoForms - ChronoEngine.com