Set Up FPVSIM Timer V3 with Mahjong USB
Install and configure the FPVSIM Timer V3 Mahjong USB edition for reliable lap timing.
See how the FPVSIM Timer Multi Events Edition supports larger race operations and repeated event setup.
The FPVSIM Timer Multi Events Edition combines individual timing nodes with a wired Ethernet network for multi-pilot events. The video shows the kit connections, express four- or eight-channel setup, RSSI calibration, access-point settings, and over-the-air firmware updates.
The walkthrough was recorded for Timer software newer than 4.1 at that time. Hardware revisions and current firmware packages may differ, so match every update to the exact kit you own.
Power each timer node as instructed for the kit and connect the event network by RJ45. Connect the timing computer to that local network, using an adapter if required.
Confirm that the app discovers the expected nodes before changing the workspace or calibration.
Select the four- or eight-channel express setup that matches the event, knowing that the recorded action overwrites the current workspace.
Set the actual VTX channels, fly representative passes, and verify RSSI separately for each node rather than assuming identical values.
The video warns that changing the supplied kit SSID can disconnect the timing nodes. Change only the access-point channel when interference requires it and current documentation allows it.
Download the correct official package, apply it through the app, and wait for every node to return. Green indicates a live node in the recorded UI; gray indicates a lost connection.
Test all channels together with the real race computer, RC radios, VTX units, and power arrangement before opening registration.
Save the current event first. Also avoid renaming the kit's Wi-Fi network unless current model-specific instructions explicitly require it, because the nodes may no longer find the access point.
This transcript was cleaned from the public English captions. Connection colors and setup labels describe the app release shown in the video.
About 00:00
The Timer Multi Events Edition kit includes four individual timer units and uses wired Ethernet as the core event connection. The design is modular. Power the units over USB, connect the RJ45 network to the laptop or desktop, and use an Ethernet adapter when the computer does not have a built-in port.
About 01:00
Install a Timer app version newer than 4.1 for the release shown here and open Set up Timer Multi. The express setup can create a four- or eight-channel layout. It will overwrite the current workspace, so save that workspace first.
About 01:50
The demonstration finds four connected timing units. Assign and verify the channels, then calibrate RSSI for the actual event layout. Each node should be checked with representative flight rather than relying on the bench connection alone.
About 03:00
In the access-point settings, do not change the Wi-Fi SSID supplied for the kit because the timer nodes can lose their connection. If the local environment is crowded, choose a different permitted Wi-Fi channel instead and test all nodes again.
About 03:20
Firmware can now be updated over the air from the official download rather than with the older flashing tool. Use the package intended for this hardware and wait for reconnection. In the status display shown, green means a timer is live and gray means its connection has been lost.
The recorded app says it overwrites the current workspace. Save or export that workspace before creating the four- or eight-channel layout.
The video specifically warns against changing the kit SSID because the nodes may lose the access point. Follow current hardware-specific documentation before altering it.
In the interface shown, green is live and gray is lost. Check node power, Ethernet or access-point connectivity, and whether a firmware update completed.
No. Use only an official package for the exact Events Edition hardware and app version. A convenient update method does not make incompatible firmware safe.
The event computer's wired path improves reliability in a crowded RF environment, while the kit can still use its managed access point for internal node connectivity as designed.