Name the symptom.
Find the next check.

Read the exact arming-prevention information for your firmware. Check the documented conditions instead of bypassing them.

1. Find the exact reported flag.
2. Match its definition to the installed firmware.
3. Verify the specific input or condition it identifies.

Separate the radio/receiver link from the receiver/controller connection. Follow the evidence along the control path.

1. Verify the selected radio model and supported RF setup.
2. Check binding and model matching where applicable.
3. Use the board’s documentation for receiver interface and channel checks.

Name the symptom first: no picture, degraded picture, missing overlay, or a display/recording difference.

1. Confirm the exact camera-to-display hardware path.
2. Inspect the documented antenna, power, and cooling requirements.
3. Separate the camera feed from OSD configuration.

Stop flying and verify the mechanical and core configuration checks. Do not defeat protective behavior to force another attempt.

1. Inspect damage and recent physical changes.
2. Verify controller orientation, motor order, motor direction, and prop installation separately.
3. Follow official powered-bench precautions, including propeller removal.

Use the last known-good state and the most recent change as evidence. Capacity alone is not a diagnosis.

1. Describe the actual behavior and conditions.
2. Inspect the mechanical and power-system basics.
3. Preserve supported logs or recordings before changing settings.

A machine that still powers on has not necessarily recovered. Begin with safe handling and an appropriate inspection.

1. Disarm and follow the equipment’s power-disconnection instructions.
2. Handle any suspect battery under its manufacturer’s guidance.
3. Inspect the impact path and repeat checks relevant to any repair.