MyLMU Logo
Documentation
Sign inGet Started
Overview TabData Export
Getting Started
Product Overview
MyLMU App
MyLMU Telemetry
MyLMU Coach (AI)
MyLMU Sync Agent
Sessions
Getting Started
Session History
Session Details
Import
Sync Agent
Analytics
Milestones
MyLMU Telemetry
Getting Started
File Library
Telemetry Viewer
Overview Tab
Data Export
Track Map
Pit Wall
Setup Tab
Leaderboard
Teams
Plans & Limits
AI Coach
Troubleshooting
MyLMU Sync Agent
Getting Started
Sessions Sync
Telemetry Sync
Daily Usage
Troubleshooting
Privacy & Security
MyLMU Coach (AI)
Getting Started
Coaching Modes
Coach Features
Troubleshooting
Privacy & Terms
Teams
Getting Started
Team Dashboard
Sharing with Your Team
Discord & Alerts
Team Calendar
Profile
Plans & Limits
Rankings
Getting Started
Skill & Discipline
Placement & Tiers
Community Leaderboard
Driver Profiles
Sessions & Imports
Notifications
Plans & Limits
Troubleshooting
Community
Getting Started
Activity
Leaderboards
Friends
Friend Groups
Lap Records
Track & Car Stats
Weekly Meta
Overall Community Stats
Feature Requests
Privacy
Troubleshooting
Misc
Opening Settings
Account & Data Lifecycle
Profile
Notifications
Appearance
Feedback
Using the Documentation
DocsMyLMU TelemetryTelemetry ViewerOverview TabData Export

Data Export

Export telemetry channels from Overview as CSV, JSON, or MoTeC .ld, or download the original .duckdb file (Pro).

Last updated July 24, 2026

Summarize this page with AI

Pro subscribers can export session data from the Overview tab → Data Export. Shared / guest views do not show this panel. Free plans see an upgrade prompt instead of the export controls.

Use Overview export for bulk channel downloads and backups. For a quick visible-window CSV or PNG of the driver traces, use Track Map → Traces panel instead. Pit Wall charts do not export PNG/CSV yet — use Overview for raw data.

Open Data Export

  1. Open a telemetry file in the viewer
  2. Click Overview in the tab bar
  3. Scroll to Data Export

Requirements

RequirementDetail
ProCSV, JSON, MoTeC .ld, and .duckdb download require Pro
Own / library fileExport is hidden on public share links and guest views
Channels loadedThe picker lists channels that are already loaded in the viewer; use search and Select all as needed

Scope

Choose how much of the session to include:

ScopeWhat it exports
Full sessionEntire recording
Selected lapsOne or more laps (Out lap + flying laps). Defaults to flying laps when you switch to this mode
Selected stintsOne or more auto-detected stints

Lap chips match Track Map numbering: Out for the out lap, then L1, L2, … for flying laps. Click to toggle; Shift-click to select a range. Use Flying only, Select all, or Clear as needed.

Channels

  • Search the list and tick the channels you need
  • Select all / Clear apply to the current search results (or the full list when search is empty)
  • Soft limit of 200 channels per export
  • GPS channels are included when available
  • Multi-wheel / multi-slot channels expand in CSV/JSON/MoTeC as Name, Name_1, Name_2, … when those slots have data

The counter shows selected / available for the channels currently loaded in the viewer.

Formats

Export CSV

Two layouts:

LayoutBest for
Aligned grid (wide)Spreadsheets — one row per time step, one column per channel
Native rate (long)Preserving each channel’s own sample times — columns time_s, channel, value

For aligned CSV you can also pick the sample rate:

  • Max selected channel Hz — denser grid matching the fastest selected channel
  • 10 Hz — lighter file, good default for long sessions

Tip: on long races with many high-rate channels, prefer 10 Hz or native long, or export fewer channels / a lap scope, so the download stays manageable.

Export JSON

Native sample times per channel, with optional scope metadata (laps or stints you selected). Useful for scripts and custom tools.

MoTeC .ld

Creates a MoTeC log you can open in i2 or i2 Pro. Channel names follow what LMU records (for example Throttle Pos, Brake Pos, Engine RPM).

Important details:

  • The file is generated from your MyLMU session, not a Motec logger recording
  • MoTeC rebuilds time from each channel’s sample rate — prefer full session or a single contiguous lap/stint range for the cleanest timeline in i2
  • Selecting multiple non-adjacent laps still exports, but i2 may show those segments as one continuous timeline
  • Time and Distance in i2 are Motec’s own channels; open the full channel list if a channel is not on the default graph

Download .duckdb

Downloads the original uploaded recording for this file (same format LMU writes). Use this for backups or when you want the full source file rather than a channel subset.

vs Traces export

Overview Data ExportTrack Map Traces
WhereOverview tabTrack Map → Traces → Export
DataSelected channels, session or lap/stint scopeVisible time window, fixed driver channels
FormatsCSV, JSON, MoTeC .ld, .duckdbCSV, PNG, copy playhead
Best forExternal analysis, Motec, backupsQuick compare snapshots

Tips

  • Export before Pro ends if you need a local backup — see Free vs Pro
  • For Motec workbooks, start with a small set (throttle, brake, RPM, speed) to confirm the log, then add more channels
  • Community and share links stay view-only — export stays on your own Pro library files

Related

  • Overview Tab — session info and linking
  • Traces panel — windowed CSV / PNG
  • Export Setup to SVM — car setup download (separate from channel export)
  • Free vs Pro

Was this page helpful?

PreviousOverview TabNextTrack Map

On this page

  • Open Data Export
  • Requirements
  • Scope
  • Channels
  • Formats
  • Export CSV
  • Export JSON
  • MoTeC .ld
  • Download .duckdb
  • vs Traces export
  • Tips
  • Related

Was this page helpful?

Documentation

  • Getting started
  • Product overview
  • Sessions
  • MyLMU Telemetry
  • MyLMU Sync Agent
  • MyLMU Coach (AI)
  • Teams
  • Rankings
  • Community
  • Misc

Product

  • Open dashboard
  • Sync Agent
  • Contact
  • Pricing
  • Changelog
  • FAQs
  • Branding

Community

  • Instagram
  • Community forum
  • YouTube
  • X

© 2026 MyLMU

•Privacy Policy•Terms of Service•Cookie Policy