TALON OS TALON OS
Performance Evidence

Teleoperation Latency Benchmarks: How TALON OS Measures Control Response

This page documents the benchmark approach used in TALON OS demo operations so partners can evaluate teleoperations performance against repeatable methodology.

42 msBest-case Wi-Fi demo measurement (controlled environment)
≤58 msCurrent demonstrated control-latency ceiling (controlled baseline)
A/B/C runsIndoor and exterior benchmark pattern

Test Environment

  • Robot connected through TALON OS teleoperation stack.
  • Controlled Wi-Fi scenario before LTE bonding rollout.
  • Live operator command and return video confirmation loop.

Measurement Process

  • Record command issue timestamp at operator console.
  • Observe robot response frame and control effect timing.
  • Repeat across static, walking, and higher-motion runs.

Evidence Handling

  • Log scenario metadata (network condition, route, run type).
  • Store mission-level export artifacts for review.
  • Separate best-case measurements from expected field envelopes.

Interpretation guidance for diligence

Important: 42 ms reflects a controlled Wi-Fi demonstration. Production-grade field operations should be evaluated by route, network profile, and mission constraints with repeated benchmark sets.

As LTE multi-link bonding is introduced, this page will be expanded with packet-loss, jitter, and failover recovery metrics.

Review benchmark context

Use this methodology with the benchmark and FAQ pages to evaluate present capability vs staged roadmap.