FPV Flight Controller Bench Setup Checklist

An FPV flight controller bench setup checklist should follow the command path: physical aircraft orientation, receiver inputs, assigned modes, then motor outputs. Keep the propellers removed for powered bench work. A connected configurator, a bound receiver or four spinning motors each proves only part of the system.

This review is useful after a new build, a flight-controller replacement or a configuration change. On a prebuilt aircraft, inspect and back up its existing settings before deciding to reflash. A generic tutorial is not a reason to discard a manufacturer’s tested configuration.

FPV flight controller bench setup checklist: record the starting configuration

Identify the frame, FC hardware revision, ESC, receiver, radio model, video system and installed firmware. Distinguish the flight firmware running on the board from the application used to configure it. Menu names, features and available settings vary with versions and build options.

Save a readable backup with the firmware version and board target. The Betaflight setup guide describes a configuration backup before changes. A backup is an aid to recovery, not a promise that settings can be pasted unchanged into a different firmware or hardware target. Keep a separate note of the wiring and the reason for each change.

Verify orientation before interpreting motor behavior

With the flight battery disconnected, use the manufacturer’s supported setup connection and move the aircraft by hand while watching the model in the configurator. Confirm that nose-up, nose-down, roll and yaw move the displayed model in the same direction. A board can be physically rotated in the frame if the supported orientation setting correctly describes it.

If the model moves incorrectly, stop and resolve the mounting orientation and configuration. Do not compensate with transmitter reversals or PID adjustments. Board alignment describes how the controller is mounted; calibration deals with the sensor readings. The flight controller sensor guide explains what those readings can and cannot tell you.

How to check FPV receiver channel mapping

Binding establishes a radio connection; it does not prove that the FC sees the intended input. To check FPV receiver channel mapping, remove the propellers and move one stick at a time in the receiver display. Check throttle, roll, pitch and yaw, their direction, endpoints and neutral behavior against the radio and firmware instructions.

Then inspect the auxiliary channels used for arming, flight modes and other functions. Confirm the actual positions transmitted by each switch. Radio channel resolution and switch behavior depend on the selected system and configuration, so do not assume a switch has a smoothly variable output just because a bar is drawn on screen.

The ExpressLRS preflight documentation provides system-specific preparation. If the receiver has telemetry but the FC sees no channel movement, investigate its power, wiring, UART and serial protocol in order. Before changing port settings, compare the wiring and protocol to the board documentation. Once inputs appear, repeat the FPV receiver channel mapping check for all four sticks.

How to verify FPV arm and disarm switches

To verify FPV arm and disarm switches, identify the intended arming and disarming positions with the propellers removed. Confirm the indicated state, allowed throttle position and any startup interlock. Read the actual arming-disable reason if the aircraft will not arm. Do not remove protections simply to get past a warning.

For every assigned mode switch, record the auxiliary channel, active range and exact mode name shown by the installed firmware. Move the switch through each position and verify that only the intended mode indicator changes. This check proves the switch-to-mode mapping; the mode’s airborne performance and any navigation prerequisites require their own acceptance procedure.

How to check FPV motor order and direction

Use the mixer diagram for the installed firmware and airframe layout. To check FPV motor order and direction, keep all props off, secure the aircraft and follow the documented motor test. Identify which physical motor responds to each output. Then verify its actual rotation without touching the moving motor. Correct numbering with incorrect rotation, or correct rotation on the wrong output, is still a failed check.

FPV props in vs props out setup checks

For FPV props in vs props out setup checks, keep three records aligned: the controller’s expected layout, the ESC/motor’s actual direction, and the propeller that will eventually be fitted. Changing a mixer expectation does not necessarily reprogram an ESC. The Motors Tab reference distinguishes direction tools from 3D mode, which concerns reversible thrust. Enabling 3D is not the ordinary fix for a motor turning the wrong way.

Only after powered tests are complete and all power is disconnected should the correct propellers be installed for the field stage. Match rotation, blade orientation and mounting hardware to the verified layout. Record which layout passed the FPV props in vs props out setup checks, then follow the fastener instructions for the installed hardware.

Save, restart and verify the command-to-output map

Save the configuration and reconnect through the documented procedure. Repeat the FPV flight controller bench setup checklist after restart. Check orientation and all four receiver channels, verify FPV arm and disarm switches and assigned modes, and check FPV motor order and direction again using the documented props-off test. A value seen before saving is not evidence that it persisted.

Illustrative acceptance row: “Receiver replacement; UART documented; four stick channels, two assigned switches and arm/disarm indication rechecked after restart; motor position and rotation unchanged.” This is more useful than “radio works” and does not claim that return or loss-link behavior has been tested.

Keep return, failsafe and loss-response verification as a separate required record. That work has different triggers, warnings, aircraft actions and recovery decisions, so its absence should remain visible instead of being compressed into this general bench setup. If a hardware mismatch remains unresolved, consult the ESC compatibility checklist rather than modifying software until symptoms disappear.

Sources and scope

Book basis: Jason Goss, FPV Drone Handbook (3 and 15); Patrick Sherman, Getting Started with Drones and Model Airplanes (5 and 8). Exact component, aircraft, firmware and local operating requirements remain specific to the system and mission.