Atomic Clock Precision for Your Facility. GPS-Locked. Network-Synchronized

Aion’s master clock is disciplined by GPS (atomic clock accuracy) and synchronized across your entire facility via NTP and PTP. Every device locked to the same nanosecond-precise reference. No external atomic clock needed.

THE PROBLEM AION SOLVES:

Broadcast facilities need a master clock that everything synchronizes to:

  • GPS/NTP master clocks are expensive ($15-50k)
  • Network synchronization requires expert configuration
  • Timing drift across devices = sync failures
  • External Cesium atomic clocks ($20-100k+) overkill for most facilities
  • Facility expansion means more sync hardware

Aion IS your master clock. GPS receiver. NTP daemon. PTP server. All in one device.

THE AION DIFFERENCE:

Professional-grade timing at accessible pricing.

Aion locks to GPS satellites (atomic clock reference). Uses Chrony daemon to discipline the system clock to GPS. Broadcasts NTP (Network Time Protocol) to every computer on your network and PTP (Precision Time Protocol) to specialized devices.

Result: nanosecond-level accuracy across your entire facility. Everything from servers to graphics systems to IP cameras stays synchronized.

HOW IT WORKS:

GPS RECEIVER Aion includes GPS receiver (SMA antenna connector):

  • Locks to GPS satellite constellation (typically 5-12 satellites)
  • Atomic clock reference (GPS signals from USNO atomic clock standard)
  • Provides absolute time and position
  • Works anywhere with clear sky view (outdoor antenna mount)
  • Backup if network sync is unavailable

NTP (NETWORK TIME PROTOCOL) System clock disciplined to GPS via Chrony daemon:

  • Stratum 1 accuracy (directly locked to atomic clock reference)
  • Broadcasts NTP on port 123 to facility network
  • Every computer synchronizes to Aion’s clock
  • Typical accuracy: milliseconds across local network
  • Updates multiple times per second for continuous disciplining

PTP (PRECISION TIME PROTOCOL) For devices needing nanosecond accuracy:

  • Aion operates as PTP Master
  • Ethernet-based synchronization (ports 319/320)
  • Accuracy: nanoseconds (suitable for broadcast, audio sync, real-time systems)
  • Broadcasts to TSL displays, ArtNet devices, specialized timing receivers
  • Multicast or unicast delivery

AUTOMATIC CALIBRATION One-click calibration measures your facility’s actual network characteristics:

  • Runs for user-specified duration (typical: 10-30 minutes)
  • Measures timing symmetry between Aion and all clients
  • Automatically compensates for asymmetric network paths
  • Updates NTP configuration with learned offset
  • Improves network timecode delivery accuracy

FOR ENGINEERS:

GPS RECEIVER:

  • Type: NMEA-compatible GPS receiver
  • System accepts any standard USB type external antenna. (included)
  • Signal reception: 5-12 satellites typical (depends on antenna placement)
  • Lock time: 15-30 minutes cold start, seconds for warm start
  • Accuracy: ±100 nanoseconds when locked (GPS atomic clock reference)
  • Backup: Facility clock stable for hours without GPS if needed

NTP SYNCHRONIZATION:

  • Daemon: Chrony (drift correction, disciplining, frequency stability)
  • Stratum: Stratum 1 (directly disciplined by GPS)
  • Broadcast port: 123/UDP (standard NTP)
  • Update frequency: Multiple per second (continuous adjustment)
  • Network accuracy: milliseconds on local network, microseconds on fast networks
  • Leap second handling: Automatic (announced by GPS satellites)
  • Frequency stability: ±5 PPM (parts per million) typical

PTP MASTER CLOCK:

  • Protocol: IEEE 1588v2 (Precision Time Protocol)
  • Role: Master (Aion is the timing reference all devices sync to)
  • Ports: 319/UDP (event messages), 320/UDP (general messages)
  • Timing: Nanosecond precision
  • Multicast: Default (configurable to unicast for specific networks)
  • Clock ID: Unique identifier broadcast to all clients
  • Sync interval: Configurable (typical: once per second)
  • Delay asymmetry: Measured and compensated by calibration

CLOCK DISCIPLINING:

  • Master oscillator: Aion’s disciplined system clock
  • Feedback loop: Chrony continuously measures GPS offset and adjusts
  • Thermal stability: OS manages thermal compensation
  • System uptime: Clock discipline maintained across restarts
  • Jitter: Sub-microsecond (network timing jitter dominates)

CALIBRATION PROCESS:

  1. User selects duration (10-30 minutes typical)
  2. Aion enables NTP statistics logging
  3. Measures offset variance between system and all GPS measurements
  4. After duration expires, calculates average network asymmetry
  5. Updates Chrony config with measured offset
  6. System automatically learns facility network characteristics
  7. Downstream timecode delivery compensates for learned asymmetry

Example: Measured average offset of +245 nanoseconds (network delay asymmetry). All future NTP deliveries pre-compensate for this 245ns delay. Result: clients receive time 245ns earlier, compensating for network transit.

MONITORING & DIAGNOSTICS:

GPS STATUS DISPLAY: ✓ Stratum (should be 1 when locked to GPS) ✓ Satellite count (should be 5+ for good lock) ✓ Signal strength (20+ indicates good antenna) ✓ Reference time (last GPS update timestamp) ✓ System time offset (error relative to GPS) ✓ Leap status (upcoming leap second if any)

PTP STATUS DISPLAY: ✓ PTP available (service running and broadcasting) ✓ Role (should be Master) ✓ Timer source (System = GPS-disciplined clock, correct) ✓ Auto-sync active (continuous GPS recalibration) ✓ Last auto-sync (timestamp of most recent calibration)

Typical healthy status:

  • Stratum = 1 (locked to GPS)
  • usedSatellites >= 3 (minimum for 2D solution)
  • signalStrength >= 20 (good lock)
  • systemTimeOffset < 1 millisecond (excellent disciplining)
  • ptpAvailable = true (broadcasting to network)
  • autoSyncActive = true (continuous calibration)

REAL-WORLD APPLICATIONS:

BROADCAST CENTER (Multi-Building Facility)

  • Aion on main router: GPS antenna on building roof
  • All computers sync to Aion’s NTP (automatic, no configuration)
  • Graphics systems use PTP (nanosecond timing for overlay precision)
  • Remote building: uses Aion’s NTP over WAN (millisecond accuracy sufficient)
  • Results: Entire facility locked to same master clock (atomic reference)

LIVE EVENT (Stadium, Arena, Multi-Site)

  • Aion at main production control room
  • All cameras, graphics, lighting sync to Aion’s PTP
  • Remote trucks access via PTP over fiber (pre-compensated for latency)
  • Backup: if Aion loses GPS, system clock stable for hours (event completion)
  • Accuracy: nanosecond timing for all synchronized devices

FACILITY UPGRADE (Adding IP-based Systems)

  • Legacy facility: LTC timecode infrastructure
  • New systems: IP cameras, video servers (need NTP)
  • Aion provides both: LTC outputs for legacy + NTP/PTP for new systems
  • Single master clock serves both old and new simultaneously
  • No forklift upgrade required (gradual IP migration possible)

MULTI-TIMEZONE BROADCAST (Distributed Centers)

  • Aion master clock at primary facility
  • Remote facilities sync to Aion’s NTP (even across continents)
  • Automatic leap second handling (coordinated UTC standard)
  • Each facility displays local time via software offset (time zone handling)
  • All locked to same atomic clock reference (perfect sync across time zones)