Your bench reference
Purpose, prerequisites, output and the next check for each tool. Use this guide alongside the application version and compatibility table.
Back to overview & pricingSee it in action
A real DJI Mini 4 Pro. One connected workflow. See how Odakon Next takes you from device identification to a diagnostic report.
Demonstrated on Mini 4 Pro. Available tools depend on the aircraft and firmware. Check compatibility
01 / ODAKON NEXT
Complete these preparations before starting a device operation.
02 / Calibration
The listed Mavic 3 family and Mavic 4 Pro, Air 3 / 3S, Mini 4 Pro / 5 Pro, Lito 1 / X1, Neo / Neo 2 and Flip models use the command-based workflow. Keep the aircraft still. Stages appear in one status area; success requires the device’s completion response.
On Mini 1 / SE / 2 / 2 SE / 3 / 3 Pro / 4K, Air 2 / 2S and the Mavic 2 family, the calibration button opens firmware guidance. A model with a disabled flasher cannot be flashed by the application. Installing service firmware alone does not finish calibration: calibrate from the controller, then restore normal user firmware with the correct DJI Assistant 2 edition.
This is separate from ordinary gimbal calibration. Use Control → Enter factory mode → Restart drone. After the same model / serial number and IMU permission are verified, data is uploaded and a save is requested. Rejected or incomplete replies do not trigger an automatic resend. Restart, check error 40021 and return to normal mode when servicing is finished.
03 / Aircraft control
Separate buttons request service mode and return to normal mode. Wait for device acceptance, then use Restart to apply the change. The recorded mode state is tied to the same aircraft identity.
After restart, the model and serial number are checked again. A different USB-connected aircraft is not treated as the continuation of the previous device. Do not use this button as a recovery action during firmware installation.
04 / Module & sensor identities
Drone SN reads aircraft identity again. Camera SN reads camera-sensor records and retains all valid records on multi-camera devices. There is no separate Gimbal SN button. Battery SN reads the installed battery identity; availability depends on the firmware response.
Available front, rear, downward, upward and depth sensors are listed by position. Sensor counts vary by aircraft. The Mavic 3 and Mini 4 Pro profiles differ. Missing or invalid content is not accepted as a serial number. Use Copy to export the displayed results.
Aircraft, camera, battery and seven vision / TOF sensor serial numbers were verified on Mini 4 Pro. Eight vision sensor serial numbers and two camera-sensor records were verified on Mavic 3 Thermal. These observations do not guarantee identical records on other aircraft or firmware.
05 / Diagnostics & PDF reports
The application reads flight-controller, gimbal and vision modules and evaluates component groups according to the model profile. If temporary service mode is needed, normal mode is requested afterwards. Explicitly enabled factory mode is retained.
Green: no fault reported for that link. Red: the device reported a fault. Amber: no or incomplete response, so status is unverified. The PDF retains the original device identity, start / finish times and completion state. A new diagnostic run starts a new report; an interrupted test is not presented as complete.
Starts aircraft pairing mode. Complete pairing on the appropriate controller; a missing acknowledgement is not successful pairing.
Sends a data-repair request with the aircraft stationary and propellers removed. Device acceptance is recorded. Restart and check the original fault afterwards. This command does not repair electronic or mechanical damage.
Requests exit from factory mode. Restart and recheck obstacle avoidance / vision warnings afterwards. This button does not imply optical sensor calibration or repair of physical damage.
In this version, factory mode, Link Test, pairing and Vision Recovery are unavailable on Mini 1, Mini SE, Mini 2, Mini 2 SE, Mini 4K and Mini 3. This does not indicate a device fault. The Mini 3 / 01.00.0500 trace shows successful aircraft, camera and battery serial reads but no factory-mode acknowledgement. Mini 3 Pro, Air 2 / 2S and Mavic 2 use separate profiles.
PDF
Sample diagnostic report
Aircraft details, firmware, test times and component results in one document. This sample is a Link Test report from a DJI Mini 4 Pro.
2 pages · English PDF · 11 September 2026
This sample: 32 of 32 checks normal
Results describe the device responses during this test only.
06 / Firmware flasher
The flasher opens only for the Mini 3, Mini 2 SE, Mini 4K and Mavic 3 Classic model gates. The account needs flashing permission. Select a complete .bin, .zip or .tar firmware package and review the model and file. Wrong-model packages, damaged / changed modules and unsafe archive paths are rejected.
ARB is the firmware’s anti-rollback level. A published service package must match the model, ARB level and file-integrity requirements. ARB must be preserved to allow restoration of normal firmware. Unknown, missing or mismatched ARB information blocks installation. The application does not bypass ARB.
A transfer reaching 100% does not mean device installation is complete. The final installation response is required. Once installation starts on the aircraft, do not disconnect power / USB or send the installation again. If completion cannot be verified, do not assume success; check the connection and aircraft state.
Transfer families, package checks and failure paths passed reference and replay tests. Physical installation using a real firmware package has not been validated for this release. Classic uses the Mavic 3 transfer routine with an exact model / package gate and requires separate target-hardware validation.
07 / Vision & TOF files
Open the file tool from Control and select a compatible .bin calibration image. After analysis and permission checks, the fix is saved separately, reopened and verified. This does not automatically upload anything to the aircraft.
Use a compatible uncompressed calibration .bin and the new sensor’s 14-character uppercase alphanumeric serial number. A separate output is created after record-family and integrity checks. This is not a tool for changing aircraft, camera or battery serial numbers.
Neither the original nor an existing output is overwritten. The suggested name is sourcename_fixed.bin; spaces and Unicode characters are preserved. The input limit is 512 MB. Unsupported / damaged filesystems, ambiguous records or failed integrity checks stop processing. Installing the resulting file on the aircraft is outside these tools’ scope.
08 / ODAKON NEXT
Accelerometer, gyroscope, primary and secondary sensor connections.
Barometer, compass, GPS, ESC communication / PWM, video link, fan and available battery / PPS status.
Gimbal accelerometer, gyroscope, flight-controller link and profile-specific voltage / electronic stabilisation / PPS synchronisation.
Pitch, roll and yaw motors, plus Hall A / B position sensors.
Downward, front, rear and upward left / right cameras, and supported depth / 3D-depth sensors.
Additional responses such as RTK RF, ADC and logic-device status in supported profiles. Unidentified components are not given an unverified hardware name.
Coverage depends on the device profile. Not every aircraft contains every listed component. Generic-profile results and incomplete replies are identified separately.
09 / ODAKON NEXT
Finish sign-in and the update check. Check the data cable, USB port, device power and driver. Close other tools using USB, then scan again.
If device-side firmware installation is not running, let the operation stop, allow the aircraft to cool, check cable / power and reconnect. If installation has started on the aircraft, keep power and USB connected.
Usually a session, active-operation or device-mode conflict; it is not by itself proof of overheating or excessive requests. Use the current release, let the previous operation finish and reconnect after about 30 seconds if needed. If it persists, share the operation time with support.
The request limit was reached. Do not repeatedly press the button; wait for the indicated retry interval.
Firmware may not provide the record, the connection may have dropped or the record format may be unsupported. A missing serial number alone is not proof of a failed sensor. Provide model, firmware and operation details to support.
Check free gimbal movement, a level / stable surface, aircraft temperature and power. Motor, ribbon-cable or sensor damage requires physical repair. Do not treat the operation as complete without an explicit success result.
10 / ODAKON NEXT
Use the official DJI source for your model when restoring normal firmware or following manufacturer calibration procedures. These references do not imply DJI endorsement of Odakon Next service tools.
Vision-sensor calibration in DJI Assistant 2 is not offered for every newer aircraft. Odakon’s Vision / TOF file-preparation tools are different from the manufacturer’s optical calibration procedure.
Scope reviewed: 11 September 2026
