telemetry-correlation-debugging

Aligning telemetry logs with different timestamps requires normalizing varying sampling rates to a shared time base, then applying event-plateau matching to produce confidence-labeled cross-domain comparisons.

Normalize VCP and robot battery telemetry timestamps by mapping both domains to a shared time base, then apply event-plateau matching and lag estimation to produce confidence-labeled matches.

Comparing EdgeTX VCP logs with robot battery telemetry from docker logs is supported by collecting both sources and running a correlation workflow to generate a timing-aligned report.

Telemetry correlation fails with differing sampling rates because domain mismatches cause misalignment; applying lag estimation and event-plateau matching resolves these gaps to generate accurate comparisons.

Debugging cross-domain telemetry timing gaps involves aligning VCP and robot battery logs in a shared time base, detecting voltage steps and direction changes to highlight gaps from coarse sampling.

Collecting VCP logs from telemetry-captures and robot battery telemetry from docker logs is required before running the correlation workflow to generate a timing-aligned report with matched plateaus.