OPEN TELEMETRY / ESP32-C3

Every lap.
Your data.

Build an open-source GPS lap timer and vehicle telemetry system on ESP32-C3. Turn your phone into a local dashboard for circuits, stages and ordinary drives. Record, review and keep your data.

Try the dashboardInstall firmwareHow it works →
Rust firmware / Local Wi-Fi / MIT licensed
25 Hz M9N GPS TARGET200 Hz CONFIGURABLE IMU OUTPUTLOCAL DATAMIT SOURCE
THE VIEW FROM YOUR SEAT

Your phone.
Your instrument panel.

Turn your phone sideways. Tap the instrument name to choose Speed, G-meter, Peaks or Runs, or swipe to switch. Timing stays in place with a track selected. Without one, Drive shows recording duration, partial GPS distance and data health. Controls brings back the toolbar when you need it.

01 / LANDSCAPE CLUSTERACTUAL INTERFACE · SIMULATED DATA
Landscape dashboard with a large speed readout beside elapsed lap time, reference delta and route progress
Tap the instrument name or swipe: Speed / G-meter / Peaks / Runs.View full size ↗
Explore the G-meter viewG-meter with a fixed one-g scale, three-second trace and signed force estimates beside lap timing

A fixed scale keeps the trace comparable through a turn. Missing data clears the live readings; over-scale forces are marked.

Explore the Peaks viewPeak acceleration, braking, left and right half-second force averages beside lap timing

Review the strongest half-second averages from this page session. Fresh moving samples qualify; isolated spikes do not become instant records.

Explore the Runs viewRuns instrument with last and best estimates from labelled synthetic 50–100 km/h evidence

Review 30–60 / 45–70 mph or 50–100 / 80–120 km/h runs. The menu follows your units; each named test keeps its own times, GPS evidence and rejected attempts. Timing rules and limits → · See the opened interval picker ↗

Record an ordinary driveNo-track Drive panel showing recording duration, partial GPS observed distance and storage health beside speed

No track required. Start a recording, see duration and qualified GPS distance, then Stop to freeze the summary. Gaps stay explicit. Try the Drive panel → · How distance and recovery work →

Review a saved driveSaved synthetic circuit recording with maximum speed and sustained acceleration, braking, left and right force estimates, qualified sample counts and provenance

Review a recording’s maximum qualified speed, strongest half-second force estimates, data gaps and sample quality. Values stay tied to that recording. Read the summary rules →

01

Time comes first.

Elapsed time stays prominent. Best and last laps give it context.

02

A reference, not a guess.

Compare time at a matched position on your saved route. Negative is ahead; positive is behind. Detected gaps and ambiguous matches hide the estimate.

03

Know where you stand.

Route progress, connection and recording status share the screen. No digging through menus to find them.

Portrait Blackbox dashboard showing track and recording controls above lap timing and speed
02 / PORTRAIT DASHBOARD
PARK. REVIEW. GO AGAIN.

Everything else,
within reach.

Choose a circuit or stage. Start a recording. Bring back a saved session. Portrait keeps your setup controls close without losing the timing display.

  • Your session, saved locally. Export session and GPS timestamp CSVs, keep firmware and sensor context with new recordings, and download a backup of recordings and tracks.
  • A record of your drive. Open a saved recording’s Summary for maximum speed, sustained forces and data gaps. Analysis shows the live force detail while parked.
  • A place on your dashboard. Use Full screen where supported, or Phone setup for Android and iPhone Home Screen guidance.
Try the dashboard ↗

See recording context ↗ · See a saved drive summary ↗ · Synthetic examples.

Captured from the actual dashboard with synthetic telemetry. The device bundles the same fonts for offline use. Rotate between portrait setup and the landscape cluster.

Feel the drive.
See the details.

Lap time, reference delta, and speed at a glance. G-forces when you want more detail. No app installation or cloud account.

Lap Timer

Time circuits and stages. Compare elapsed time against a saved reference.

Force Analysis

Open optional Analysis to inspect lateral and longitudinal forces with a recent-motion trail.

Mode Detection

See estimated acceleration, braking, and cornering states.

Mobile Dashboard

Runs in a modern browser on local Wi-Fi

Position Tracking

GPS velocity and inertial measurements combined in Rust

Open Source

MIT license, Rust firmware, modify freely

BUILD OR BUY

Know what you’re comparing.

25 Hz GPS configuration. Interpolated circuit and stage timing. Local recordings you can restore. An instrument you can inspect and extend.

Own the implementation

MIT-licensed firmware, readable timing logic, configurable sensors, and a local browser dashboard. No project subscription or cloud login.

Compare the whole package

RaceBox adds packaged GPS hardware and drag modes. RaceChrono Pro brings video and data analysis. Performance Box Touch has a dedicated display and performance tests. Blackbox gives you a DIY stack to shape.

Separate rate from accuracy

25 Hz is the M9N configuration target; 200 Hz is configurable IMU output. Check delivered rates in Diagnostics. Reference-timed hardware accuracy is the next evidence to publish.

Capabilities, costs, and sourced product comparison →

What you need

One controller. Two sensors. A status LED. Start with the wiring guide.

ESP32-C3

Controller + Wi-Fi

WT901 IMU

Acceleration + orientation

GPS Module

NEO-6M or NEO-M9N

WS2812 LED

Device status

GPS model and update rate must match your firmware build. Check wiring and compatibility

MADE BY YOU

From components
to cockpit.

The build is part of the project. Follow the parts, wiring and mounting decisions, then keep a record of the installation that produced your data.

01 / ON THE BENCH

Know your hardware.

Identify the controller and sensor variants. Check the USB pin arrangement, wire the serial links, and establish fresh sensor data before closing the enclosure.

02 / IN THE CAR

Make the mount count.

Keep the sensor parallel to the car floor, position the antenna and learn the car-forward direction. A sloping dash may need a rigid support. See the mounting diagrams.

03 / THE BUILD JOURNAL

Show the details.

A dedicated assembly journal for wiring, enclosure and installation photos as the build is documented. Each stage includes the details a fellow builder needs to reproduce it.

Parts, wiring and build journal →

FROM BENCH TO DASHBOARD

Three steps to your first session.

  1. 01

    Build & flash

    Wire the ESP32-C3, WT901, GPS, and LED. Choose firmware for your GPS model and connect over USB.

  2. 02

    Connect & settle

    Keep the sensor stationary for startup calibration; use level ground for the initial baseline. Join its Wi-Fi, open the dashboard, and wait for a fresh GPS fix outdoors.

  3. 03

    Record & return

    Start Record session for an ordinary drive. For circuit or stage timing, record a route and arm it on a later pass.

In active development. Timing accuracy depends on GPS reception, update rate, and line geometry. Validate your setup before relying on lap results. Setup and timing guide

OPEN BY DESIGN

More insight.
Full ownership.

For drivers who want to understand their tools as well as their laps. Inspect the firmware, export your CSV recordings, and shape the project with us.

Try a simulated circuit session
  • Your hardware. ESP32-C3, WT901, and a supported GPS configuration. Review the board pinout before you build.
  • Your data. Recordings live in your browser. Download a backup and restore it as new copies before changing browsers or devices. Keep the file somewhere safe.
  • Visible limits. Inspect configuration targets, regression evidence, and the hardware test plan. Follow the project as measured results become available.

Before your first lap.

Can Blackbox replace a paid GPS lap timer?

Evaluate it for circuit/stage timing, reference pace, local recordings, and editable firmware. Packaged systems may offer dedicated displays, autonomous storage, video/OBD analysis, and vendor support. Use the sourced capability comparison to choose, then measure your installed setup with the hardware checklist.

Can I try it without hardware?

Yes. The interactive dashboard demo uses explicitly simulated telemetry. Try recording, saved data, lap feedback, and a connection interruption. Demo values do not demonstrate sensor accuracy.

Which GPS and controller should I use?

The firmware targets ESP32-C3 with a 4 MiB flash image. Published candidates distinguish NEO-6M at 5 Hz and NEO-M9N at 25 Hz. Update rate is not timing accuracy, and board wiring matters: GPIO18/19 currently conflict with native USB. Read the compatibility FAQ.

Does it identify corners or coach my braking?

Not yet. Progress is an estimated fraction of reference-lap distance, not a pinpoint track position. Automatic turn callouts need validated position matching and repeatable corner identification. See the measurement limits.

Does it need a subscription or cloud account?

The project requires neither. The device serves its dashboard over local Wi-Fi, and browser recordings can be exported as CSV. Hardware costs, assembly, and validation are your responsibility.

Flash firmware

Published release via USB. Use desktop Chrome or Edge with Web Serial.

Install a release

Choose the GPS variant that matches your receiver. Release candidates contain newer fixes and still need hardware validation. Read release notes

Status

Ready
Select firmware to begin
Ready.
BUILD. RECORD. UNDERSTAND.

Start with the question you have.