A reliable timer starts with the connection. Choose the setup that fits your hardware, follow the video, then test it with the radios and distances you will actually use.
USB on Timer V3 keeps the app connection off Wi-Fi. A router or spare phone can improve wireless coverage. For Timer Multi events, use the kit's supported Ethernet connection to the race computer.
Start with the hardware you own. A USB power socket alone does not mean a timer supports USB data.
Connecting Solo for the first time? Start with the Solo setup and calibration walkthrough. A direct timer hotspot is useful for initial setup and close-range checks; test it again when other pilots' radios are active.
Use the V3 / Mahjong hardware variant intended for your host device, a data-capable cable, and an app version that supports Timer V3 USB.
Check that it receives stable power. A charge-only cable can power the timer without carrying its data.
Look for “Connect timer USB” or its current equivalent. Confirm that live RSSI appears and the connection mode reports USB.
If you need an extension, test that exact cable and host together. The video demonstrates an active extension; it does not establish a universal maximum length.
On iPhone, temporarily turning off Wi-Fi can help the app select USB. Some Android devices need a compatible OTG or powered hub. Follow the walkthrough for your hardware variant.
For the Solo setup shown in these videos, the timer joins 2.4 GHz Wi-Fi. Your phone or computer can use the router's 5 GHz network, with both bands on the same local network.
First connect directly to the timer hotspot. In the Timer app, enter the router's 2.4 GHz network name and password, save, and reboot the timer.
Use the router's 5 GHz network if supported. Guest or client isolation must not prevent the app from reaching the timer. Find the timer's current IP address and confirm live RSSI; a DHCP reservation can keep the address stable.
Moving the app device to 5 GHz can reduce its exposure to 2.4 GHz RC traffic. Choose a locally permitted Wi-Fi channel that works with your event's FPV video frequencies, then test with the radios on.
The timer's 2.4 GHz link still exists. Moving the app device to 5 GHz does not make the whole connection immune to interference.
A spare phone can provide a hotspot between Timer Solo and the separate device running the app. Place it between the two devices to shorten each wireless hop, and raise it above nearby obstructions.
Use a simple network name and your own strong password. Enable a band compatible with the timer; the Solo shown needs 2.4 GHz.
Use the timer's router settings to save the hotspot credentials, then reboot. Join the app device to the same hotspot and connect to the timer's assigned IP address.
Position the spare phone roughly between the two endpoints. Test for hotspot shutdowns and disconnects during the session, including when the phone screen is locked.
Phone and operating-system behavior varies. The Multi variation in the video needs a phone that can run a hotspot and join another Wi-Fi network at the same time; many phones cannot. Use the Solo arrangement above as the starting point.
For a supported Multi Events Edition kit, follow the kit's wired network layout and connect the race computer by Ethernet. This reduces the computer's dependence on a crowded Wi-Fi link.
Follow the wiring for your exact Multi hardware. Use a supported Ethernet adapter if your computer has no RJ45 port. USB power and Ethernet data are separate connections in the demonstrated kit.
Open “Set up Timer Multi” or its current equivalent. Save your existing workspace before using express setup, which can replace it.
Set the actual VTX channels, calibrate each node, and run a rehearsal with all pilots' radios and transmitters active.
The kit can still use internal wireless links. Keep its supplied Wi-Fi name unless model-specific instructions say otherwise; changing it can disconnect nodes. Ethernet to the computer does not eliminate every RF dependency.
First check whether live data is still reaching the app. A stable connection and accurate lap detection need separate checks.
Check timer power first. On USB, confirm the cable carries data and your hardware and app support USB. On Wi-Fi, confirm both devices share a reachable local network, then check the timer's current IP address. If setup changed, reconnect directly to the timer to verify its saved network settings.
Test the same setup at the intended distance with RC radios and VTX units active. Raise or reposition the router or bridge phone, check its power supply, and watch for hotspot shutdowns. For a USB setup, test the full cable run. Use a supported wired arrangement when the wireless path remains unreliable.
Verify the VTX channel, timer placement, and calibration on the actual flight line. Follow the calibration walkthrough for the app version you use. A connection change alone will not fix incorrect thresholds or timing-point placement.
A working local timer connection does not guarantee internet access. See how to keep internet access while connected to the timer for the relevant network arrangement.
Rehearse with the complete setup, not just the timer on your desk.
