Run Qualifiers and Elimination Brackets in Timer V5
Build a complete race in FPVSIM Timer V5, from qualifying rounds through seeded elimination brackets.
Use FPVSIM Timer's visual history to inspect a race and correct missed or extra laps accurately.
What this tutorial covers
Timer 3.0 added a visual race history that preserves the complete RSSI trace, marks detected events, and helps an operator investigate a missed or incorrect lap before editing the result. The video also previews statistics, CSV import, group generation, and the timing server.
The editing screens are version-specific. In a newer release, labels and automatic calibration may differ, but a correction should still be based on saved signal evidence rather than a guess.
Prepare useful timing evidence
- Place the timer where the intended gate produces a distinct signal peak.
- Shield or orient the receiver only as recommended for your hardware and venue; never block cooling or connectors.
- Confirm every racer is on the assigned channel before starting.
- Keep an event policy for who may edit a lap and how a correction is recorded.
- Preserve the unedited result or note the original value before changing it.
Investigate and correct a lap
- Run and finish the race normally.
Let the timer record the full session, including the baseline before flight and every detected crossing.
- Open the visual race history.
Use the overview and horizontal scrollbar to locate the relevant racer, time range, and event markers.
- Compare detections with the RSSI trace.
A valid missed crossing should resemble the other timing-point peaks and occur at a physically plausible interval.
- Mark the candidate point.
Place a marker on the graph and use the displayed interval to calculate the corrected lap from known neighboring events.
- Edit only the supported value.
Enter the corrected time in the race editor, finish the edit, and review rankings and downstream results before submission.
- Use the history to improve setup.
If the same error repeats, adjust timer placement or recalibrate. Treat manual correction as recovery, not a substitute for reliable detection.
A visible bump is not automatically a missed lap.
Nearby flight, another transmitter, or RF noise can also change RSSI. Correct a result only when the trace, expected lap interval, race observation, and event rules support the same conclusion.
Edited transcript
This transcript was cleaned from the public English captions. Demonstration chatter was shortened, while the graph-reading and editing workflow was retained.
About 00:00
Timer 3.0 introduces visual race history so a missed lap can be reconstructed from the saved signal. The physical timer is placed under the timing flag and shielded from side signals so the intended crossing produces a stronger, cleaner peak. Adapt placement to your own hardware and course.
About 01:30
During the test, the live RSSI graph appears automatically and multiple racers are simulated from the same timing node. The trace records the complete session so the operator can inspect more than the short live window.
About 03:00
After finishing, open View Race History. The scrollbar moves through the session and the overview shows the whole recording. A flat region represents startup, the changing region represents flight, and vertical event lines mark the race start and detected passes. Different racers can have events at different positions.
About 04:30
To investigate a missed lap, click the graph and add a marker. The red line and cursor interval help measure the time between known points. Use that evidence to calculate the corrected lap, open Edit Time, replace the incorrect value, and finish the edit.
About 06:00
The statistics view was also revised with trend analysis, plus export or print options mentioned in the walkthrough. Calibration values such as peak, enter, and leave can be adjusted while viewing the evidence, making it easier to connect a detection problem to a setting.
About 07:40
Racer management can import a CSV using the supplied template, create groups automatically from a chosen group size, and clear groups or racers in bulk. These tools reduce setup work for a larger event.
About 09:10
Timer 3.0 also adds a timing-server feature for showing timing information in OBS and for connecting another Timer app as a client. A separate video explains that streaming workflow in more detail.
Frequently asked questions
How can I tell whether a lap was really missed?
Compare the candidate peak with valid crossings, the expected lap interval, direct race observations, and any video evidence allowed by your event policy. One noisy RSSI bump is not enough.
Should I edit the lap before submitting the race?
Review and correct it before final submission when possible. Record the original and corrected values and check whether the change affects rankings or a bracket.
Can visual history replace calibration?
No. It helps diagnose and recover from a problem. Repeated missed or duplicate laps call for better placement, RF control, or recalibration.
Are these controls identical in Timer 5?
Not necessarily. This tutorial shows Timer 3.0. Newer releases add automatic calibration and reorganize parts of the interface, so use the current control that serves the same purpose.
