Timers & hardware
Plug it in.
How dd-pits connects to your timer and to every screen, speaker and goggle, and what you need to run it.
How it works
One source of truth.
Every screen, speaker and goggle.
RotorHazard plugin
Racing on RotorHazard? It's all here too.
Install dd-pits as a RotorHazard plugin and the timer itself runs everything: the phone dashboard with up-next heats and the leaderboard, the TV view, every OBS overlay, race calls, commentary and goggle OSD. No laptop needed beside it.
1 · Upload the plugin
On RotorHazard 4.3 or later, open Settings → Plugins, upload the zip and restart. On 4.0 to 4.2, copy the dd_pits folder into src/server/plugins.
2 · Start it once online
The plugin downloads the right dd-pits for your Pi (32- or 64-bit), checks it against the release checksums, and keeps it running. After that, no internet is needed.
3 · Share the dashboard
Pilots open http://<timer>:8088. RotorHazard's Settings → dd-pits panel links to the dashboard, the overlays and dd-pits' settings, behind your RotorHazard login.
Download the RotorHazard plugin Read the guide
Works with RotorHazard 4.0 and later. Heats, rounds, classes, laps and results come straight from the timer; the next heats show as "up next" with their lineups and channels.
Works with ELRS Netpack
One Ethernet cable.
Every goggle on the field.
ELRS Netpack is firmware for Ethernet ESP32 boards that acts as the ELRS timer backpack over the network. dd-pits talks to it over TCP — and it tells you whether each message actually reached the goggles.
elrs-netpack.local:8080http://elrs-netpack.local/
ELRS Netpack was originally created by i-am-grub, and forked and extended by bob9. Not affiliated with the ExpressLRS project.
Running it
No internet.
No account. No drama.
Everything runs on the venue laptop. Settings live in one JSON file beside the app — copy it to another laptop and the whole setup moves with it.
Browser setup
Everything is configured at /setup, with a guided first run and help at /setup/help.
Debug page
The log in the browser at /setup/debug, with API keys removed, plus a downloadable report to send when something goes wrong.
Meeting editor
On FPVTrackside (alpha), change the meeting from any browser: event rules and channels, rounds, races, line-ups and pilots. Name races your way and dd-pits shows those names everywhere.
JSON API
Meeting, race, round, leaderboard, pilot and channel data at /docs — with an OpenAPI spec and a live event stream for your own displays.
What you need
Probably what you already have.
See it all working together.