An Autel Firmware Mismatch occurs when an EVO series aircraft, handheld remote controller, or camera payload runs incompatible operational software builds. This issue is especially common on Autel platforms due to the co-existence of distinct hardware generations (such as EVO II V1, V2, and V3) that use different chip architectures and transmission frequencies. When a mismatch occurs, the system locks control links, drops video downlinks, or blocks takeoff entirely.
Quick Fix
Check the hardware generation label on your aircraft and controller (V1, V2, or V3). Download the exact, matching
.binfirmware file from Autel Robotics’ official support page, copy it to the root of a freshly formatted exFAT micro-SD card, and reboot the drone to perform a clean manual offline sync.
Understanding Autel Hardware Generations
The most common cause of persistent firmware conflicts on Autel equipment is the split across hardware generations. Due to global supply-chain shifts and regulatory requirements, Autel released three distinct iterations of its flagship EVO series:
Generation RF Transmission Protocol Chipset Family
──────────────────────────────────────────────────────────────────────────
EVO II V1 Autel Skylink (Original 2.4/5.8) First-Gen SoC
EVO II V2 Autel Skylink 2.0 (Enhanced RF) Second-Gen SoC
EVO II V3 Autel Skylink 3.0 (Cross-Band) Third-Gen SoC
These hardware generations cannot cross-flash firmware.
Attempting to install a V1 .bin file on a V2 aircraft triggers a signature verification block. Similarly, connecting an original V1 Smart Controller to a V2 or V3 airframe will fail to link because their underlying transmission microcode is incompatible.
Autel Compatibility Reference Matrix
Use this matrix to confirm that your ground equipment matches your airframe:
| Aircraft Model | Compatible Remote Controllers | Incompatible Controllers |
|---|---|---|
| EVO II V1 (Standard, Pro 6K, Dual) | Standard V1 Remote (black frame), First-Gen Smart Controller | V2/V3 Smart Controllers, V2 Standard Remotes |
| EVO II V2 (Standard, Pro 6K, Dual) | Standard V2 Remote (marked “V2”), Smart Controller V2 | V1 Standard Remotes, V1 Smart Controller, V3 Controllers |
| EVO II V3 (Pro, Dual 640T V3) | Autel Smart Controller SE, Autel Smart Controller V3 | All V1 and V2 Controllers |
| EVO Lite / Lite+ | Autel Lite Remote (White/Orange accents) | EVO II Controllers, EVO Nano Remotes |
| EVO Nano / Nano+ | Autel Nano Remote | EVO II Controllers, EVO Lite Remotes |
Diagnostic Branches: Identifying Your Mismatch
To resolve a mismatch, first identify where the conflict is occurring:
Where is the conflict visible?
│
├── Controller Screen / App shows "Disconnected"
│ └── Cause: Aircraft and Controller running mismatched RF protocol builds.
│ Action: Follow Method A (Synchronize Controller & Aircraft).
│
├── App shows "Aircraft Connected" but Camera is Black / Unresponsive
│ └── Cause: Swapped payload (e.g., swapping 8K sensor for 6K Pro) with mismatched CMU code.
│ Action: Follow Method B (Payload Synchronization).
│
└── App displays "Firmware Inconsistency" or Code 20005 / 20011
└── Cause: Partial flash via Over-The-Air (OTA) update.
Action: Follow Method C (Clean Offline SD Refresh).
Step-by-Step Resolution Procedures
Method A: Synchronize Controller and Aircraft Firmware
If your controller and drone fail to link after an update, one unit is likely lagging behind on its radio driver version.
- Power on the remote controller and check its current system version under Settings > System > About.
- Power on the aircraft and inspect the rear LED indicator pattern:
- A slow, flashing yellow pattern indicates the drone is waiting for a compatible control link.
- Alternating red and green flashes indicate an active write or internal error state.
- If using an Autel Smart Controller, connect it to Wi-Fi, open the Autel Explorer or Autel Enterprise app, tap Settings > Firmware Update, and install all pending system updates.
- If wireless syncing fails, identify your controller’s manual update process using Autel Controller Firmware Update Failed.
Method B: Resolving Camera / Payload Swapping Conflicts
The EVO II platform allows operators to swap camera payloads (e.g., swapping an 8K sensor for a 6K Pro or Dual 640T thermal unit).
When you mount a new camera, the drone’s main flight controller must synchronize with the Camera Management Unit (CMU):
- Power off the drone and verify that all four payload mounting screws and the flex-ribbon connector are completely seated.
- Insert a high-speed micro-SD card containing the full unified
.binpackage for your specific generation (V1, V2, or V3). - Power on the drone. The bootloader detects the mismatched camera board and extracts the matching camera sub-firmware from the
.binpackage on the SD card. - Allow 10 to 15 minutes for the camera LEDs to finish cycling before opening the Autel Explorer app.
Method C: The Offline SD Card Refresh (The Universal Clean Fix)
Over-The-Air (OTA) updates pushed through a mobile device can drop data packets and leave internal modules out of sync. An offline SD-card flash overwrites every internal module cleanly:
Step 1: Format an SD card (16-64 GB, UHS-I) to exFAT on your PC/Mac.
Step 2: Go to Autel Robotics' official website and select your EXACT airframe model and generation.
Step 3: Download the clean, official .bin firmware package.
Step 4: Copy the file to the SD card's root directory without renaming it.
Step 5: Insert the card into the powered-off drone.
Step 6: Power on the controller, then the drone. Wait 20 minutes for LED flashing to finish.
If the aircraft rejects the package or flashes an error code during the offline check, consult Autel Error Code 20011 Firmware Verification Failed or check for installation stalls using Autel Firmware Update Stuck.
Hard Stops & Warning Flags
Stop troubleshooting and contact Autel Support if:
- You accidentally flashed a modified or incorrect generation
.binfile, and the aircraft now powers on with a solid red rear indicator light, no cooling fan activity, and an unresponsive power button. In this situation, review Autel Drone Not Starting After Update. - The aircraft throws persistent numerical hardware failure alerts (such as Error Code 20005) across multiple fresh SD cards. For this error code, see Autel Error Code 20005 Firmware Update Failed.