TTEDEVTelemetry V2
Checking APIDashboard

Lap analysis · Preview

Lap comparison

Compare SD logs or VPS CSV exports. Imported files stay in this browser. Starting a live watch sends only the selected reference route and sector boundaries to the VPS.

Use a saved VPS session

Or import SD / CSV files above

Load recorded data directly from your account. The saved circuit timing gate is selected automatically. No manual download or upload.

Log in to the VPS in this browser to load saved sessions.

1 · Timing gate

Same gate and direction for both laps

Silverstone gate uses the existing VPS coordinates. Confirm the plotted gate crosses the start/finish straight.

Import telemetry.065–070 together, or a VPS CSV export, to begin.

Load data to inspect unique GPS fix rate and UTC increments.

2 · Choose laps

Only complete laps passing the gap and GPS checks can be selected.

3 · Distance overlay

Scroll over a graph to zoom · drag to select a distance range · double-click to reset. Positive delta means the comparison lap is behind. Smoothing affects the displayed traces and cursor readings only; lap/sector times, live predictions and CSV exports use unsmoothed data. Discrete status channels are not smoothed.

Choose channels · up to four

Your speed traces and time delta will appear here.

Full sector comparison

Where the comparison lap gains or loses time

← Faster / gainedSlower / lost →Select a row to highlight the sector on the map and zoom the traces.

Compare laps to time fixed sector-gate crossings.

Theoretical best lap

Shows the raw sum of fastest sectors from compatible, eligible loaded laps. It is not a validated target lap: GPS timing errors and different sector entry/exit conditions can make it optimistic.

Compare laps, then calculate your dataset’s potential.
Edit sector boundaries

Internal boundaries as % of reference distance. Ten equal sectors are a starting point, not official timing sectors. The same boundary positions apply to live timing; live timing still uses the existing distance-projection method.

Differences are comparison minus reference. Timing is GPS-derived; tiny differences may be measurement noise. Sector times use unsmoothed data.

Live sector timing

REFERENCE-BASED ESTIMATE

Select and compare a clean reference lap above. Then choose a vehicle and start watching. The VPS processes every new stored sample; this panel refreshes about twice a second.

Log in to the VPS in this browser to use live timing.

Current sector—
Delta to reference—
Estimated lap—

Timing begins at the next forward gate crossing. The estimate assumes the remaining lap matches the reference. GPS loss, a reboot, a data gap or leaving the reference route invalidates the current lap. Keep this page open; watches expire after 15 minutes without polling and are lost when the HTTP service restarts.

Lap quality and excluded intervals

Timing is GPS-derived, not official timing. Reboots split runs; partial first/last laps are omitted. Gaps over 2 seconds, GPS jumps and stopped laps are excluded. A passing check does not identify every pit or safety-car lap—review the map and traces.