MeshCore icon

MeshCore

Interact with a MeshCore device over TCP/WiFi

Diagnostic → Trace Path

AI-generated

Summary

Trace a non-empty route by sending a MeshCore diagnostic trace packet and waiting for the device's trace response, using the configured hop hash size and an additional reply timeout.

Inputs

  • Path (required) — Route as hex path-hash bytes, one byte per hop (for example, dd4c). Must contain at least one hop.
  • Path Hash Size — Bytes per hop: Auto (From Device), 1, 2, 4, or 8. The size must match the route's encoding; trace packets cannot encode 3 bytes per hop.
  • Extra Timeout (Ms) — Additional milliseconds to wait beyond the device's airtime estimate. Increase for long or slow routes, whose trace replies can take longer than the outbound estimate.

Output shape

A single trace response from the device.

The response includes trace data with per-hop SNR information. Device errors and timeouts are reported as errors; the wait accounts for the device's airtime estimate plus the configured extra timeout.

Links

Discussion