Skip to content

Telemetry

Available Charts

The cursor-linked charts in the analysis cockpit share one position: point at a moment in one and the others show the same moment. Zooming is narrower -- the channel stack and the track map share a zoom window, and stint evolution plots the session as a whole rather than following the cursor. This page lists what each chart shows and what to look for.

Synchronized cursor

Hover a channel trace, click the track map, or drag the scrubber -- the cursor moves across every cursor-linked chart at once. Distances are measured along the lap, so laps of different lengths stay aligned. Scroll-to-zoom and shift-drag pan the channel stack and the track map together; the other panels keep their own framing.


Track map

Your driving line on a track-shaped map with three visual styles (SAT / STR / HYB). SAT draws satellite imagery under the line for real-world context; STR draws the TrackOut street map under your GPS line, and the floating mini map follows that style; HYB is a tinted backdrop with no map tiles, for reading the line itself without surrounding detail.

  • Per-lap GPS lines -- each selected lap draws its real recorded GPS path in that lap's color, not a line snapped to the centerline
  • Car markers -- one marker per selected lap at the cursor position. On a recognized track with a curated layout they move along that centerline instead of jumping vertex to vertex
  • Turn markers -- when TrackOut recognizes the venue and has a curated layout for it, the layout's turns are labeled on the map, including nearby turns that used to stack on the same point
  • Overlays -- Δ colors the driving line by time gained or lost against the reference lap, Phases marks the braking, apex, and throttle-on points of each turn, and Off shows the raw lines only
  • Click anywhere on the map to set the cursor there

Drag the divider beside the map to make it wider or narrower.


Channel stack

Stacked plots draw a pane per channel group; Shared plot draws the groups together. Speed, throttle, brake, and lateral G open by default; Add trace lists every recorded numeric channel -- including ones that share a logger label -- plus Elapsed time, Distance, Reference gap, and derived channels such as Line curvature (how the line is opening or tightening -- the line, not the car's balance). Rename or remap a slot if the logger's channel names do not match.

  • Distance compares each lap at the same track position; Elapsed time compares each lap at the same time since its start
  • Hover to read every selected lap's value at the cursor -- missing coverage says No data and breaks the line
  • Scroll to zoom around the cursor, shift-drag to pan, double-click to reset
  • Map channels appears in the transport bar whenever one of the priority channels -- throttle, brake, steering angle, speed, RPM, gear, brake pressure -- is still unmapped. CAN and vendor names are assigned there and saved per car; Yaw rate takes a gyro only, and a GPS-computed channel such as GPS Gyro is refused. See Channel assignments

Speed is shown in mph, G-forces in g, and pedal channels as a percentage. See Channel analysis.


Reference comparison

A sticky strip under the transport bar plotting each selected lap's cumulative time delta against the reference lap, by the reference's distance or Elapsed time. The two laps are matched at the same place on track, so a different line through a corner does not add phantom time. The plotted line and hover are smoothed so GPS jitter does not look like time won or lost; finish time and the per-turn waterfall stay exact. On Elapsed time, the hover matches the line. The strip says Aligning laps… while that comparison is computed, and Gap unavailable if it cannot run.

  • Below zero -- ahead of the reference at that point on track
  • Above zero -- behind the reference
  • Steep slopes -- the sections where time is being gained or lost fastest

This is the quickest way to see where a lap diverged. See Lap comparison for reading deltas in detail.


G-force plot

A friction-circle widget on the track map: lateral G across, longitudinal G up and down, colored by turn phase. Expand it to full size from its corner control.

  • Trail braking shows as a smooth arc from the braking edge into the cornering edge
  • Grip usage -- points near the envelope mean most of the available grip is in use
  • Smoothness -- a tight pattern means steady inputs; scattered points mean abrupt ones

Tip

Compare the G-force pattern of your fastest lap with an average one. A fuller envelope on the fast lap confirms you were using more of the available grip.


Stint evolution

Lap time for every lap in the stint, with the best lap drawn as a reference line. Click a point to make that lap the reference. A compact copy lives inside the lap selector.


Delta waterfall

One bar per turn showing time gained or lost against the reference lap, so the corners that matter most stand out at a glance.


Corner performance matrix

A table with one row per turn and one value per selected lap:

ColumnDescription
Entry / Apex / ExitSpeed at each phase of the corner
Brake startWhere braking began
Throttle onWhere you returned to the throttle
Max lat GPeak cornering load through the turn
Peak brakePeak brake application
ConsistencyHow repeatable your segment time is, once three or more laps are selected

On a mapped venue the rows carry the layout's real turn labels; elsewhere TrackOut detects corners from your driving data and numbers them.


Turn inspector

Per-turn cards with mini traces and the expanded channels for that corner. Switch the view between braking, entry / exit, and minimum speed to focus on one part of the corner at a time.

Open Segments for a full turn or straight comparison -- Overview, Position, Speed, Acceleration, and Coaching. On a turn, Position adds a Line · A vs B strip under the map, with ticks on each lap's line; select a row or a tick to move the replay there. See Compare turns and straights.

Detected corners

On venues without a curated track map, corners are found from your GPS and G-force data. High-sample-rate loggers (for example AiM at 25 Hz) still produce a corner list -- if an older analysis showed none, open the session again. Occasionally one turn may be split or merged unexpectedly; use the track map and speed trace to cross-check anything that looks odd.