Repository navigation
Radio Link
Purpose: Review aircraft-side RC failsafe episodes and ArduPlane's recorded response from one DataFlash BIN. An optional EdgeTX CSV can add transmitter-side RF and telemetry evidence without changing the aircraft result.
- One ArduPlane DataFlash
.binor.BINlog. - For optional transmitter evidence, the corresponding EdgeTX telemetry
.csvfile. - The APT desktop GUI. See the README installation instructions if needed.
The BIN is the authoritative source for RC-input failsafe episodes, short and long failsafe actions, aircraft mode response and recovery. An EdgeTX CSV is supplementary; Radio Link Analysis works without one.
- Click Choose BIN… beside Source BIN: at the top of the APT window.
- Select the aircraft BIN, then open Radio Link from Overview or select the Radio Link tab.
- Click Analyse.
- Read the compact aircraft result. Use Show detailed evidence for episode-by-episode timing, state and response evidence, or Show summary to return to the compact view. These controls use the same completed BIN analysis.
- Click Docs for the in-app description and glossary. Click Test Procedure before conducting a deliberate ground test.
The aircraft BIN summary remains the authoritative episode record. It shows the sampled invalid spans, observed short and long actions, mode responses and timing assessment without treating RF telemetry as the episode boundary.
After the BIN analysis has completed:
- Click Discover nearby to list EdgeTX CSV files located beside the BIN.
- Select each candidate to read its diagnostic hint. A hint can identify an automatically eligible candidate, a file that requires explicit selection or an unusable candidate. It is diagnostic evidence, not proof that the recordings match.
- Click Auto pair only when APT reports exactly one eligible nearby candidate.
- If automatic pairing is unavailable, select a candidate and click Use selected, or click Browse CSV… to choose a CSV elsewhere.
- Review the reported pairing status, alignment status, warnings and telemetry availability.
- Click Remove CSV evidence to return to the unchanged BIN-only report. This does not delete the CSV or rerun the aircraft analysis.
Manual selection permits APT to examine the chosen file. It does not prove that the CSV and BIN record the same test session. Pairing and precise timeline alignment remain separate evidence decisions.
Optional transmitter evidence is presented below the aircraft result with its own pairing and alignment status. Here the session-wide RF observations are retained, while the report explicitly withholds an RF value at the aircraft RC-input event.
The summary identifies confirmed armed RC-input loss episodes and counts logged short and long failsafe actions. For each supported episode it can show the sampled invalid start, duration, observed response and armed state. The detailed view can also show:
- The preceding valid and subsequent revalidated RC-input samples.
- Logged short- and long-failsafe messages and associated mode changes.
- Recovery or clearing evidence, or an open episode at the end of the log.
- Failsafe timing parameters applicable at the episode and a conservative timing assessment.
- Commanded throttle PWM and throttle-suppression state where supported.
Both short and long failsafe timers originate from the last acceptable RC input. The logged short-failsafe message is therefore not the start of the configured long-failsafe timer. Logged command or PWM evidence does not prove physical motor operation.
The EdgeTX section identifies its source CSV and distinguishes pairing from alignment. Where supported, it can describe session-wide RQly, 1RSS, RSNR, RF mode and transmitter-power observations, telemetry disappearance or return, and qualified context around an aircraft episode.
APT only attaches numeric RF values to a specific aircraft episode when alignment and telemetry-age evidence are strong enough. Coarse alignment may support a statement that telemetry was unavailable around an episode without proving the exact RF value or physical loss instant.
- Unavailable telemetry means no usable transmitter-side RF observation was present. It is not a measured zero.
- Zero-filled placeholder rows are excluded from RF measurements.
- Repeated values may have been held between telemetry updates rather than independently measured again.
- Aircraft
RXLQmay remain stale during complete loss. A high value does not override the aircraft's asserted RC failsafe state.
Radio Link has a Test Procedure describing two separate propeller-off tests:
- Bench transmitter-off/on — switch the transmitter fully off long enough to observe the configured short and long response, then switch it back on and observe recovery. EdgeTX logging stops when the transmitter is switched off; recording after restart is a separate transmitter session.
- Ground walk to link loss — keep the secured aircraft stationary while walking away until RC input is lost, then return until it recovers. The transmitter normally remains powered and recording throughout this test.
For either test, remove the propeller, secure the aircraft, keep people clear, verify DataFlash logging, review the configured failsafe actions and configure a receiver failsafe signal that ArduPlane recognizes. No Pulses is recommended where the receiver supports it; digital protocols can provide their own indication. Start fresh aircraft and transmitter sessions for each test and record relevant RF settings. Armed tests require deliberate additional precautions and are not equivalent to disarmed tests.
These tests examine particular controlled loss and recovery paths. Transmitter shutdown does not reproduce every possible RF-link failure mode, and a ground walk does not establish a physical range unless distance is measured independently.
Radio Link reports logged aircraft and transmitter evidence. It cannot derive the exact physical RF-loss instant, instantaneous RF values at sampled failsafe boundaries, transmitter distance, RF margin or physical motor activity from the BIN. Optional CSV evidence cannot repair a weak or ambiguous session pairing.
Sampling and message timing can place logged observations after the underlying firmware transition. Missing messages or telemetry are reported as unavailable rather than reconstructed. The analysis supports investigation of the recorded response; it does not certify the radio installation or replace safe range and failsafe testing.
- Back to the Wiki Home
- Range-Walk Comparison — compare transmitter telemetry along a repeatable five-landmark route without deliberately requiring failsafe.
- Events — inspect supported messages and mode changes in chronological order.
- Radio Link in-app Help source
- Radio Link glossary
- Radio Link Test Procedure
- APT project README
Getting started
Battery & packs
Flight analysis
Radio & diagnostics
Reference

