Masterclock GMR5000
GMR5000
<tc>Prix régulier</tc>
Masterclock GMR5000 High-Precision, Multi-Function NTP & PTP Master Clock
The GMR5000 is a master clock that can reference a variety of timing sources and provide a range of outputs including NTP, PTP, SMPTE, and IRIG-B. The internal modular design allows the unit to be factory-configured per the user's requirements. The base model includes both NTP server and client functionality compatible with IPv4/IPv6 networks and offers AES 256 SSH encryption for secure communications.
Optionally, the device can act as a IEEE1588v2 PTP grandmaster or slave clock, time code generator, NENA time server, frequency generator, and more. Optionally, an OCXO or Rubidium oscillator enhances holdover stability to minimize timing drift.
Robust
- Mission-critical Stratum 1 timing solution
- Capability of synchronizing to GPS, GNSS, IRIG-B, or PTP reference
- High-stability oscillator options available including Rubidium Holdover
Resilient
- Internal-disciplined high-stability oscillator options allow for critical holdover resiliency
- Optional modules provide flexible input/output signal support
- SNMP v3 with custom MIB
Scalable
- Supports enterprise-grade PTP/NTP server application
- Backward compatible with legacy signals
Standard Features
• 13-digit display (Date/Time or Day of year/Time)
• Programmable relay closure - NO/NC dry contact relay
• Relay alerts loss of sync by default
• Fully configurable offsets for time zone and DST
• Secure configuration and monitoring with SSH SHA2 AES256 encryption
• SNMPv3 with custom MIB
• IPv4/IPv6 compatible
• WinDiscovery configuration software included
REFERENCE DOCUMENTS:
Specifications
GMR5000 NTP & PTP GRANDMASTER CLOCK
Display
- IPv4 and IPv6 compatible
- SSH secure communication
- SNMP with Masterclock MIB
- MD5 authentication
- Internal TCXO maintains time during loss of external sync within ± 3 seconds/year
Inputs/Reference
Sources
- Base Model
- NTP client with 10/100 Mb Ethernet (Dual-port)
- NMEA 0183 via RS-232 or RS-422/485
- NENA Format 0, 1 and 8 via RS-232 or RS-422/485
- Additional Options
- Time Code Option: SMPTE 24fps (Film), 25fps (EBU), 30fps and 29.97 drop frame
- Time Code Option: IRIG-B0 (DCLS) and IRIG-B1 (AM)
- Time Code Option: IRIG-A0 (DCLS) and IRIG-A1 (AM)
- Time Code Option: IRIG-E0 (DCLS) and IRIG-E1 (AM)
- GPS and GNSS receiver options
- Synchronizing signals: PPS, PPM, PPH
- IEEE 1588v2 Precision Time Protocol
- 10 MHZ Input (CMOS or Sinusoidal)
Outputs
- Base Model
- NTP client with 10/100 Mb Ethernet (Dual-port)
- NMEA 0183 via RS-232 or RS-422/485
- NENA Format 0, 1 and 8 via RS-232 or RS-422/485
- Additional Options
- Time Code Option: SMPTE 24fps (Film), 25fps (EBU), 30fps and 29.97 drop frame
- Time Code Option: SMPTE 24fps (Film), 25fps (EBU), 30fps and 29.97 drop frame
- Time Code Option: IRIG-B0 (DCLS) and IRIG-B1 (AM)
- Time Code Option: IRIG-A0 (DCLS) and IRIG-A1 (AM)
- Time Code Option: IRIG-E0 (DCLS) and IRIG-E1 (AM)
- 5V at 100mA Programmable Pulse Output (PPO)
- IEEE 1588v2 Precision Time Protocol
- 10 MHZ Output (Sinusoidal)
- HAVEQUICK & NASA36
High-Stability
Oscillator Options
- Internal high-stability OCXO oscillator ±0.25 sec/year
- Rubidium oscillator ±1 ms/year
Dimensions,
Power, Operating
Parameters
- AC input (90-264VAC, 47-63Hz)
- 18.9w x 1.750h x 5.174d in (48w x 4.445h x 13.14d) cm
- Temperature: 0 to +60°C (32 to +140°F)
- Humidity: up to 90%, non-condensing
Other Options
- 13-Digit display (Date/Time or Day of year/Time)
- Programmable relay closure, one event per day with SPDT dry contact relay
- Optical Fiber LAN
Notice
Masterclock Devices Do Not Use Treck TCP/IP Stack
A recent update to many network security monitoring platforms incorrectly identifies many Masterclock network devices as having a critical vulnerability to a set of attack vectors called Ripple20, attributed to the Treck TCP/IP stack. The vulnerabilities are present in a widely-used TCP/IP stack from Treck, Inc. and affect hundreds of millions of devices of all types around the world where vendors utilized this stack in their embedded systems. Masterclock devices do not use the Treck TCP/IP stack and the fingerprinting methodology deployed by the scans provides a false positive.