Documentation

Getting Started

FPVGate is an RSSI-based lap timing solution for FPV drones. It measures lap times by detecting your drone's video transmitter signal strength as you fly through the gate.

Existing SPI receiver builds remain supported. For a C5 build, start with the C5 receiver guide; it covers multi-pilot UART, direct USB to RotorHazard, and C5RX single-pilot SPI.

Hardware Setup

Choose your receiver

The diagrams below are for the traditional SPI receiver build. Select your S3 board to see its wiring. C5MK uses its own UART wiring tables and does not need an analog RSSI filter.

3D Printed Parts

If you are building your own timer, these parts are free to download and print. Each one can be previewed in 3D on the 3D print files page, along with its recommended print settings.

Flashing Firmware

Use our web-based flasher for the easiest installation experience. No command line required!

SD Card Setup

FPVGate uses an SD card to store voice announcement files and race data. Setting up the SD card correctly is essential for audio features.

Automatic Setup (Recommended)

Use the SD Card Setup tool on the Flasher page to automatically download and extract the correct folder structure to your SD card:

1. Insert your FAT32-formatted SD card into your computer
2. Go to the Web Flasher page
3. Find the "SD Card Setup" section in the sidebar
4. Select your firmware version
5. Click "Select SD Card & Setup" and choose your SD card folder
6. The tool will download and extract all required files automatically

Manual Setup

Alternatively, you can manually set up the SD card:

1. Download the SD_Card.zip from the GitHub releases page
2. Extract the contents to the root of your SD card
3. Ensure the folder structure matches the expected layout (audio files in the correct directories)

Configuration

After flashing, reach the web interface either over the FPVGate WiFi network or, on firmware 1.8.0 and later, straight down the USB cable.

Calibration

Proper calibration is essential for accurate lap detection.

Manual Calibration

You can also manually set thresholds:

• Enter Threshold: RSSI level when crossing starts
• Exit Threshold: RSSI level when crossing ends
• Peak Detection: RSSI must peak between enter and exit

Using the Lap Timer

Starting a Race

1. Ensure calibration is complete
2. Power on your drone
3. Click "Start Race" on the web interface
4. Fly through the gate - laps will be recorded automatically
5. Click "Stop Race" when finished

Features During Race

• Real-time lap display
• Fastest lap highlighting
• Gap analysis
• Voice announcements for each lap
• LED feedback (if configured)
• On-screen displays (OSD) for live stats

Multi-Timer Race Sync

Sync separate single-pilot timers using multi-timer sync, or use one C5MK receiver for up to eight pilots. These are separate operating modes.

After Race

• View race statistics
• Export race data
• Compare with previous sessions
• Edit laps if needed (Marshalling Mode)

Event Mode: Pilots, Groups & Heats

Event Mode adds a race-director workspace to your FPVGate S3 timer. Build a pilot roster, organise groups, choose how races are scored and plan the running order. An event can contain several groups, with up to eight pilots in each heat using one C5MK receiver.

Enable Event Mode

On the timer's web interface, open Settings → User Interface → Event Mode and turn it on. The Event tab appears. First make sure C5MK is connected, the C5 receiver mode is selected and pilot calibration works.

Build your event

1. Add or import pilots. Set names, spoken names, colours, channels and enter/exit thresholds. Import an existing roster from CSV or JSON, or export a roster to reuse at another session.
2. Create groups. Choose a group size up to eight and select roster order, random, Elo rating, fastest lap or best three consecutive laps as the seeding method. Click Build groups, or edit groups yourself.
3. Assign channels. Choose a band and use Assign channels to spread each group's frequencies. You can override a pilot's channel within a group. Check assignments and calibrate on the channels you will race.
4. Choose a race format. Set a lap limit, heat time, minimum lap time, start countdown and win condition. Assign the appropriate format to each group.
5. Plan the heat order. Open Heat order to repeat a group or rotate through several groups. Drag blocks to reorder them, or tap to add them on a touchscreen.

Run the heats

Click a heat to load its group into the C5's pilot slots. FPVGate applies the pilots' channels and thresholds together with the group's race format. Check the loaded heat, then start the race from the Race tab.

When the race is saved, its results are recorded against that heat. Enable Load the next heat after each race to prepare the following heat automatically, or use Next Heat to select it yourself. Loading a heat does not start a race: start each race when the pilots and track are ready.

Example: twelve pilots split into groups A, B and C of four can rotate A → B → C three times for a nine-heat schedule. Each heat uses four of the C5's available pilot slots.

Results, seeding & backups

Review individual heat results, group standings and pilot statistics, including fastest lap, best three consecutive laps and Elo rating. Elo is calculated from recorded event races; lap-time seeding uses the results recorded in the event.

The event is saved on the gate. Export the whole event as JSON to back up pilots, groups, formats, heat order and results; import it to restore an event. Results can also be exported as CSV or as a standalone HTML report for sharing or printing. Export a backup before replacing an event or choosing New event.

Keep the web race page open: the current Multi-Alpha build relies on the browser for race completion and heat timeout. Event Mode is part of the S3 timer interface; a C5 connected directly to RotorHazard uses RH's event tools instead.

Install compatible timer firmware · Set up the C5 receiver · Multi-Alpha-3 release notes

FPVGateC5MK Multi-Pilot

Up to 8 pilots with one ESP32-C5 receiver. C5MK scans each pilot's channel and sends timestamped RSSI to your S3 over UART. FPVGate provides individual calibration, race results and per-pilot Visual Marshal editing in compatible Multi-Alpha firmware.

1. Flash FPVGateC5MK onto your C5 using the C5 Radio flasher.
2. Install a compatible Multi-Alpha build on the S3. Multi-Alpha-3 is packaged for XIAO S3 and Waveshare S3-ETH; check the flasher for your board.
3. Connect host TX to C5 RX and host RX to C5 TX, plus ground and 5V power, using the C5 wiring guide.
4. Select ESP32-C5 Multi-Pilot in Settings → Configuration → Receiver Module, save, and check that the radio is online in Calibration.
5. Assign each pilot's channel and calibrate their thresholds. Keep the web race page open during racing.

C5MK tunes 5180–5917 MHz, including Raceband R1–R8. Current C5 mode does not use Master/Slave sync or daisy-chaining. Full physical eight-pilot race validation is still outstanding; review the current status and test your setup.

Using RotorHazard? C5MK 1.2.0+ also supports direct native USB timing without an S3 or plugin. Existing S3 timers still use the network plugin.

Multi-Timer Sync (SPI Receivers)

FPVGate supports synchronizing multiple timers for multi-pilot racing. Each pilot has their own FPVGate device, and one device acts as the Master to control the race.

Step 1: Connect All Devices to Same Network

All FPVGate devices must be on the same WiFi network:

• Option A: Connect all devices to your home/external WiFi network via Configuration → WiFi & Connection
• Option B: Keep one device in AP mode (FPVGate network), connect all other devices and your phone to that network

Step 2: Add Sync Devices (on Master)

1. Go to Configuration → WiFi & Connection → Race Synchronization
2. Find the "Add Device" input field
3. Enter each slave device's IP address (e.g., 192.168.4.100)
4. Click "Add Device" - it will appear in the sync devices list

Step 3: Set Device Roles

For each device in the list:

• This Device: Set to "Master" on the controlling timer
• Other Devices: Set to "Slave"

Role options: Personal (solo timing), Master (controls race), Slave (follows master), RotorHazard (syncs with RH server - see RotorHazard Integration)

Step 4: Test Connections

Click "Test All Connections" to verify all devices can communicate:

• Green checkmark = Ready to race
• Red X = Check network connectivity

Racing in Multi-Pilot Mode

Once configured:

• Start/Stop race from the Master device only - all slaves sync automatically
• Each pilot's laps appear side-by-side in the Master's race view
• Lap Times Chart and Consistency Chart compare all pilots
• Voice announcements include all pilots' lap times
• Race history saves complete multi-pilot data

RotorHazard Integration

FPVGate v1.7.0+ can operate as an external RSSI node for RotorHazard, enabling bidirectional race control and lap submission.

How It Works

• FPVGate to RH: Gate crossings are submitted as laps; race start/stop commands are forwarded
• RH to FPVGate: RotorHazard race events (stage, start, stop) are relayed back to control FPVGate
• Clock Sync: NTP-style synchronization keeps timing aligned between both systems

Setup Steps

For full technical details, endpoint reference, and troubleshooting, see the complete RotorHazard Integration guide.

Screenshots

Race Screen

Real-time lap display with fastest lap highlighting and gap analysis

Configuration - Pilot Info

Configure your pilot details and preferences

Configuration - LED Setup

Customize LED behavior and colors

Calibration Wizard

Guided calibration process for optimal lap detection

Calibration Screen

Real-time RSSI visualization and threshold adjustment

Race History

Detailed analysis of all your races

Troubleshooting