Turn a compatible build into a safe first configuration.

• Target: select the exact FC target in the configurator before changing Ports or CLI settings.
• Processor family: STM32F405 is listed for this FC; match the firmware family before flashing or applying a backup.
• Backup: save an all-settings backup before changing Ports, Receiver, Modes, OSD, or CLI settings.

• likely UART1: enable Serial RX for elrs-nano-rx after the board manual confirms the port number.
• likely UART2: enable VTX control for analog-smart-audio-vtx after the board manual confirms the port number.
• likely UART3: enable GPS sensor input for m10-gps after the board manual confirms the port number.

• FC target: use the Ports table above for setup planning, but keep exact serial/resource CLI hidden until the UART resources are verified for this board.
• Betaflight target check: choose the exact target in the configurator before copying board-specific commands.
• UART resource check: exact board resources are still review-only, so no serial/resource commands are copyable yet.
• Command review: exact serial/resource lines need board-and-accessory review for this FC before they are copyable.
• 3 UART assignments need board-manual review before any remap command is copied.

• Receiver mode: Serial receiver.
• Provider: CRSF.
• Ports tab: Serial RX on likely UART1 after board-manual review.
• Receiver tab: verify channel order, endpoints, and switch ranges with props removed before assigning modes.
• Failsafe: bench-check receiver loss before first flight; motors should stop unless a reviewed rescue setup deliberately takes over.
• CRSF/ELRS should use a normal TX/RX UART pair.

• Motor protocol: start with DShot300 unless the selected ESC documentation calls for a different DShot rate.
• FC-to-ESC link: FC lists 4in1; ESC lists 4in1. Confirm the harness orientation before motor testing.
• ESC firmware: check the ESC documentation before changing motor output settings.
• RPM filtering: leave bidirectional DShot off until both FC and ESC support are confirmed.
• Use the motor tab only with props removed, then verify motor order and direction before arming.

• Setup tab: move the frame by hand and confirm the 3D model tilts and yaws the same way before arming.
• Accelerometer: calibrate on a level bench after the FC is mounted in its final orientation.
• Motor tab: with props removed, verify motor order and direction before enabling air mode or turtle mode.
• Final prop check: install props only after frame direction, motor direction, and prop orientation all match.

• analog-smart-audio-vtx is treated as analog video.
• analog-micro-camera feeds the FC video input before OSD overlay; confirm camera video lands on the CAM pad and video out leaves the VTX pad.
• likely UART2: use VTX control for band, channel, and power changes after board-manual review.
• Load the matching VTX table from the manufacturer before trusting channel or power labels.
• OSD bench check: verify battery voltage, timer, link-quality or RSSI, and warning text are visible in goggles or monitor before first hover.

• Modes: set arm on a deliberate switch, beeper on an easy-to-hit switch, and turtle mode only if the ESC setup supports it.
• Arming check: verify the arm switch stays inactive at boot and only arms when the intended transmitter switch is moved.
• Prearm: add a separate prearm or safety switch before the first hover if the radio has a spare switch.
• Beeper test: use the Modes tab to confirm the beeper switch triggers the physical buzzer or DShot beacon before leaving the bench.
• likely UART3: enable GPS with UBLOX provider for m10-gps after board-manual review.
• GPS rescue should stay review-only until satellite lock, failsafe behavior, and return direction are bench checked.

• Board-photo setup stays review-only until the selected FC has a matched silkscreen image for pad-label checking.

• Continuity-check VBAT to GND before plugging in a pack.
• First LiPo power: use a smoke stopper or current-limited bench supply before connecting the pack directly.
• Power-up watch: disconnect immediately if the smoke stopper trips, a regulator gets hot, an LED pattern looks wrong, or anything smells burnt.
• Power from USB first when possible, then add receiver, video, GPS, buzzer, and LEDs one at a time.
• Save a Betaflight backup before changing Ports, Receiver, Modes, or CLI settings.

CLI Review

CLI lines are held until the FC board photo is matched for pad-label checking.

• Target: select the exact FC target in the configurator before changing Ports or CLI settings.
• Processor family: STM32F405 is listed for this FC; match the firmware family before flashing or applying a backup.
• Backup: save an all-settings backup before changing Ports, Receiver, Modes, OSD, or CLI settings.

• likely UART1: enable Serial RX for sbus-nano-rx after the board manual confirms the port number.
• likely UART2: enable VTX control for digital-air-unit after the board manual confirms the port number.
• likely UART3: enable GPS sensor input for m10-gps after the board manual confirms the port number.

• FC target: use the Ports table above for setup planning, but keep exact serial/resource CLI hidden until the UART resources are verified for this board.
• Betaflight target check: choose the exact target in the configurator before copying board-specific commands.
• UART resource check: exact board resources are still review-only, so no serial/resource commands are copyable yet.
• Command review: exact serial/resource lines need board-and-accessory review for this FC before they are copyable.
• 3 UART assignments need board-manual review before any remap command is copied.

• Receiver mode: Serial receiver.
• Provider: SBUS.
• Ports tab: Serial RX on likely UART1 after board-manual review.
• Receiver tab: verify channel order, endpoints, and switch ranges with props removed before assigning modes.
• Failsafe: bench-check receiver loss before first flight; motors should stop unless a reviewed rescue setup deliberately takes over.
• Check inversion and half-duplex notes against the receiver manual.

• Motor protocol: start with DShot300 unless the selected ESC documentation calls for a different DShot rate.
• FC-to-ESC link: FC lists 4in1; ESC lists 4in1. Confirm the harness orientation before motor testing.
• ESC firmware: check the ESC documentation before changing motor output settings.
• RPM filtering: leave bidirectional DShot off until both FC and ESC support are confirmed.
• Use the motor tab only with props removed, then verify motor order and direction before arming.

• Setup tab: move the frame by hand and confirm the 3D model tilts and yaws the same way before arming.
• Accelerometer: calibrate on a level bench after the FC is mounted in its final orientation.
• Motor tab: with props removed, verify motor order and direction before enabling air mode or turtle mode.
• Final prop check: install props only after frame direction, motor direction, and prop orientation all match.

• digital-air-unit is treated as a digital video path.
• Hold MSP DisplayPort and OSD canvas settings until the air unit UART pair is verified.
• likely UART2 is reserved only as the first visible video assignment from the wiring plan.
• OSD bench check: verify MSP DisplayPort overlay, craft voltage, timer, and link-quality or RSSI fields are visible in goggles before first hover.

• Modes: set arm on a deliberate switch, beeper on an easy-to-hit switch, and turtle mode only if the ESC setup supports it.
• Arming check: verify the arm switch stays inactive at boot and only arms when the intended transmitter switch is moved.
• Prearm: add a separate prearm or safety switch before the first hover if the radio has a spare switch.
• Beeper test: use the Modes tab to confirm the beeper switch triggers the physical buzzer or DShot beacon before leaving the bench.
• likely UART3: enable GPS with UBLOX provider for m10-gps after board-manual review.
• GPS rescue should stay review-only until satellite lock, failsafe behavior, and return direction are bench checked.
• Beeper mode can still be mapped, but a physical buzzer needs assigned pads for lost-model sound.

• Digital video setup stays review-only until the MSP DisplayPort UART pair and OSD path are checked against the board manual.
• Board-photo setup stays review-only until the selected FC has a matched silkscreen image for pad-label checking.

• Continuity-check VBAT to GND before plugging in a pack.
• First LiPo power: use a smoke stopper or current-limited bench supply before connecting the pack directly.
• Power-up watch: disconnect immediately if the smoke stopper trips, a regulator gets hot, an LED pattern looks wrong, or anything smells burnt.
• Power from USB first when possible, then add receiver, video, GPS, buzzer, and LEDs one at a time.
• Save a Betaflight backup before changing Ports, Receiver, Modes, or CLI settings.

CLI Review

CLI lines are held until the FC board photo is matched for pad-label checking and the digital video UART and OSD path are checked.

• GPS pad assignment is blocked: No available FC pads satisfy uart_tx, uart_rx for m10-gps.

CLI Review

Betaflight snippets stay hidden until the selected pads and parts clear the blocking checks.