Betaflight
Connect to the board
Remove propellers and disconnect the battery. Connect the controller by USB with a data-capable cable. Open the Betaflight App in a supported browser and grant access to the board's USB/serial device. See Betaflight's connection instructions if the device is not listed.
Record and back up
Before editing settings or updating firmware, save a backup from the app's Presets tab. You can also record the output of these read-only commands from the CLI tab:
version
status
diff all
Save the output with the board revision and date. version identifies the installed build; status provides diagnostic information; diff all records configuration differences across profiles. These outputs describe what is installed, not independent proof that it is the correct MWE target. See the CLI reference.
Configure the installation
Work through the following checks after the board revision and peripheral wiring are verified. Keep propellers removed throughout bench configuration.
| Area | Check |
|---|---|
| Board orientation | The setup model moves in the same direction as the physical board. Account for the installed orientation. |
| Sensors | Expected sensors appear and respond. Investigate missing sensors before proceeding. |
| Ports | Functions match the actual UART connections. |
| Receiver | Channels, endpoints, and control directions match the radio setup. |
| Modes | Arming and selected flight modes respond to the intended switches. |
| Failsafe | Receiver loss produces the intended disarmed bench behavior for the installed configuration. |
| Motors | With propellers removed, check motor order and direction against the selected mixer. |
| Power monitoring | Compare displayed values with an appropriate independent measurement and use the verified sensor calibration. |
| Video / OSD | Confirm the selected video system and any on-screen telemetry work together. |
For detailed app controls, use the official Betaflight documentation. Peripheral choices determine the required protocols and settings; this guide does not prescribe one universal configuration.
Updating firmware
Follow Firmware before opening the flasher. Do not choose a related board's target as a substitute for a confirmed MW F722 target. After any update, recheck the complete setup before flight.
Troubleshooting
| Symptom | First checks |
|---|---|
| No USB connection | Data cable, another USB port, browser permission, and software holding the port open |
| Receiver has no channel movement | Peripheral power, confirmed wiring, selected UART function, and receiver protocol |
| GPS or video telemetry missing | Power requirements, signal direction, UART selection, and peripheral configuration |
| Sensor missing after an update | Stop setup and confirm the installed target and build with MWE |
| Unexpected resets | Disconnect power and inspect wiring, shorts, and the verified power budget |
For MWE support, include the board revision, version and status output, connected peripherals, and the steps that reproduce the issue.