SpeedyDrone Enterprise Reference
Current aircraft, controller, Dock, payload, Terra and PSDK branches—plus the checks that matter before a production update.
DJI Enterprise firmware is a system, not one version number. An operational stack can include an aircraft, controller, battery station, payload, Pilot 2, Terra, FlightHub 2 and a branch-specific Payload SDK. This tracker consolidates the current DJI-published versions and shows which compatibility checks still have to happen before an update reaches a production fleet.
“Current download” means the version DJI lists on the linked page when we checked it. It does not mean every aircraft, payload, controller and third-party integration combination has been tested by SpeedyDrone. A PSDK release baseline is also not automatically the same as today's newest downloadable firmware.
Current DJI Enterprise firmware and software versions
The table below is a dated snapshot, not an instruction to update. The source link is the place to recheck immediately before deployment, especially if this page's last-verified date is no longer recent.
| Component | Current DJI download | DJI date | Compatibility action | Official source |
|---|---|---|---|---|
| Matrice 400 UAV | 17.02.50.07 | Jun. 16, 2026 | Check controller, station, payload and target PSDK release | M400 downloads |
| M400 RC Plus 2 Enterprise | 01.64.08.18 | Jun. 16, 2026 | Pair with the intended aircraft release | M400 downloads |
| M400 BS100 | 01.00.00.13 | Jun. 16, 2026 | Include the station in the fleet inventory | M400 downloads |
| Matrice 4E / 4T | 17.02.05.01 | Jun. 16, 2026 | Check controller and current release notes | Matrice 4 downloads |
| M4 RC Plus 2 Enterprise | 01.64.08.20 | Jul. 10, 2026 | Do not infer aircraft version from controller version | Matrice 4 downloads |
| Dock 3 / Matrice 4D / 4TD | 17.02.05.21 | Jun. 16, 2026 | Validate the complete Dock stack and remote workflow | Dock 3 downloads |
| Dock 3 D-RTK 3 | 17.01.05.02 | Jun. 16, 2026 | Track separately from Dock and aircraft | Dock 3 downloads |
| Dock 3 RC Plus 2 | 01.64.08.18 | Jun. 16, 2026 | Check the exact Dock deployment package | Dock 3 downloads |
| Matrice 350 RTK | 17.03.00.05 | Aug. 11, 2026 | Use the M350 PSDK branch, not latest by default | M350 downloads |
| M350 RC Plus | 06.02.13.14 | Aug. 11, 2026 | Confirm aircraft/controller pair | M350 downloads |
| M350 BS65 | 07.00.01.08 | Apr. 16, 2025 | Record even when unchanged | M350 downloads |
| Payload / software | Current DJI download | DJI date | Relevant compatibility baseline | Official source |
|---|---|---|---|---|
| Zenmuse H30 / H30T | 10.06.01.06 | Mar. 31, 2026 | Aircraft support plus applicable SDK/release notes | H30 downloads |
| Zenmuse L2 | 06.00.01.04 | Nov. 4, 2025 | Aircraft + Pilot 2 + Terra workflow | L2 downloads |
| Zenmuse L3 | 17.02.00.04 | Aug. 3, 2026 | M400 + Pilot 2 + Terra; check target PSDK release if integrated | L3 downloads |
| DJI Terra | 5.3.5 | Aug. 20, 2026 | Check processing workflow and payload requirements | Terra downloads |
| Payload SDK | 3.16.0 latest release | Mar. 31, 2026 | Branch-specific by aircraft generation | DJI PSDK |
Recent updates to watch
These are the most recent changes in this tracker snapshot, not a complete release history. For example, the M350 page now lists an August 11 aircraft build, so an older article that quoted a May firmware date may still be historically accurate while no longer being the current reference. That is why individual buying and workflow guides should link here instead of each becoming a separate version tracker.
Firmware compatibility means checking the whole system
Matrice 400 stack
An M400 operator should not stop after checking the aircraft line. Record the controller and BS100 Intelligent Battery Station, identify the attached payload, and include Terra or Modify if they are part of the deliverable. If a third-party payload or onboard computer is used, add the relevant PSDK branch and integration build to the same change record. The Matrice 400 E-Port V2 and PSDK guide explains those integration paths in more detail.
DJI Dock 3 stack
DJI's Dock 3 page publishes separate entries for the Dock aircraft, D-RTK 3 and controller because this is a multi-component system. A post-update test therefore needs the Dock 3, the correct Matrice 4D or Matrice 4TD, the D-RTK 3 Multifunctional Station, FlightHub 2 and the remote mission path—not just the aircraft boot screen. The DJI Enterprise App guide and O4 Ground Station guide cover adjacent deployment layers.
Mapping and LiDAR stack
A current payload does not make the complete processing workflow current. For L2 or L3, validate acquisition on the aircraft and then process representative data in the Terra version the team actually intends to use. Keep mission settings and output checks with the version record so a change in deliverables is not incorrectly diagnosed as “just firmware.”
DJI PSDK branch matrix: latest is not universal
DJI's current Payload SDK documentation divides aircraft into recommended branches. This is one of the easiest areas to get wrong because the newest SDK release is not the prescribed starting point for every aircraft generation.
| Aircraft generation | DJI recommended PSDK | Tracker status | Operational note |
|---|---|---|---|
| Manifold 3, M400, M4D / M4TD, M4E / M4T and later models | Latest PSDK | CURRENT | Still check the target release's supported-product and firmware table |
| FlyCart 30 / 100 | 3.14.1 | BRANCH-SPECIFIC | Do not substitute the newest branch without validation |
| Mavic 3TA | 3.13.1 | BRANCH-SPECIFIC | Keep aircraft and integration build records together |
| M350, M300, M30, Mavic 3 Enterprise, M3D / M3TD | 3.9.2 | BRANCH-SPECIFIC | M350 should not be moved to 3.16 merely because 3.16 is newer |
| M210 V2 generation | 2.2.1 | LEGACY | Older supported branch; preserve a known working toolchain |
| M200 / M210 generation | 1.5.3 | LEGACY | Verify documentation and support before changing the environment |
PSDK 3.16.0 release documentation can name supported products and reference firmware versions for that SDK release. Those are compatibility baselines for that release; they are not automatically the same as every component's newest download today. Compare both columns before changing a working integration.
For M400 development, the DJI E-Port V2 Development Kit is the relevant SpeedyDrone product reference. Its current store record was unavailable when this tracker was prepared, so the link is for exact product details rather than a stock promise.
Release notes and known-issue checks
A version number alone is not enough to approve a change. Release notes explain the intended change; a Known Issue List can expose limitations that matter more than the headline feature. “Not observed” below means we did not see a separately labelled Known Issue List on that public downloads page when checked—it does not assert that the product has no known issues.
| Product | Release notes | Known Issue List observed | Last checked | Action |
|---|---|---|---|---|
| Matrice 400 | Yes — Aug. 11, 2026 | Not separately listed | Sep. 25, 2026 | Read current release notes and support notices |
| Matrice 4 Series | Yes — Jul. 10, 2026 | Yes — Apr. 15, 2025 | Sep. 25, 2026 | Review both documents |
| Dock 3 | Yes | Not separately listed | Sep. 25, 2026 | Include FlightHub and remote-operation checks |
| Matrice 350 RTK | Yes | Not separately listed | Sep. 25, 2026 | Review payload and PSDK branch |
| Zenmuse H30 Series | Yes — Mar. 31, 2026 | Yes — Jul. 18, 2024 | Sep. 25, 2026 | Read both even when issue list is older |
| Zenmuse L2 | Yes — Nov. 4, 2025 | Yes — Jul. 18, 2024 | Sep. 25, 2026 | Test acquisition and Terra processing |
| Zenmuse L3 | Yes — Jul. 30, 2026 | Yes — Mar. 31, 2026 | Sep. 25, 2026 | Check payload, aircraft and Terra together |
| DJI Terra | Yes | Yes — Aug. 20, 2026 | Sep. 25, 2026 | Validate representative processing project |
SpeedyDrone operational planning framework
This is a SpeedyDrone change-planning framework, not a DJI risk rating and not a claim about defect probability. “High” means the validation scope should be wider because more operational functions can be affected.
Low change impact
Documentation refresh or a minor application update that does not alter the production aircraft configuration. Confirm access and expected workflow.
Medium change impact
Payload firmware, controller firmware or Terra processing version. Test the affected sensor, connection or output pipeline.
High change impact
Aircraft firmware, Dock firmware, production PSDK environment or a multi-component fleet update. Use staged validation and rollback planning.
Enterprise firmware change-control checklist
Before the update
- Record every current component version.
- Read release notes and the available Known Issue List.
- Confirm aircraft, payload and controller compatibility.
- Confirm the correct PSDK branch for third-party hardware.
- Check Terra and other software requirements.
- Export or save required mission data and configuration records.
- Charge aircraft, controller and station batteries adequately.
- Schedule work outside the critical mission window.
After the update
- Confirm normal aircraft boot and controller connection.
- Confirm every payload is detected and video feeds work.
- Verify RTK, obstacle sensing and required flight modes.
- Load a representative mission route.
- Capture and save photos, video and mission files.
- Verify FlightHub 2 connectivity and synchronization.
- Test Dock remote operations where applicable.
- Test third-party payloads and PSDK functions.
- Process representative L2/L3 data in the intended pipeline.
Should you update immediately before a mission?
Do not treat a production fleet firmware update like routine phone-app maintenance. Treat it as a configuration change that needs validation. If tomorrow's work is a utility shutdown, corridor survey, emergency deployment or expensive industrial inspection, a fleet-wide untested change the night before creates avoidable operational uncertainty.
This sequence is an operational recommendation, not a statement that DJI prohibits mission-adjacent updates. Emergency fixes and mandated changes can alter the decision; document that reason and increase the validation effort accordingly.
Downgrade availability, permitted versions and required tools vary by product. Verify rollback support for the exact aircraft, controller, payload or Dock before changing a production system. A backup of settings or data is not the same as firmware rollback capability.
Firmware troubleshooting matrix
| Symptom | First compatibility check | Then validate |
|---|---|---|
| Payload suddenly not recognized | Aircraft + payload firmware | Mount, cable/interface and supported-payload documentation |
| Controller shows an inconsistency | Aircraft + controller versions | Pilot 2, account/network and update completion |
| Third-party payload stops working | PSDK branch + aircraft firmware | Integration build, E-Port/SkyPort/X-Port path and vendor release |
| L2/L3 processing changes or fails | Payload firmware + Terra version | Mission settings, calibration, data integrity and output settings |
| Dock mission fails after an update | Dock + aircraft + FlightHub stack | D-RTK 3, network, route and remote-operation health |
| Expected feature is missing | Release notes + region + hardware support | Required application, entitlement and exact model |
| Unexpected behaviour appears | Known Issue List | Reproduce on the staged system and preserve logs |
| Fleet units behave differently | Exact firmware inventory for each unit | Controller, payload, app, configuration and branch differences |
This is a diagnostic starting point, not a substitute for DJI support or engineering investigation. Preserve version inventories, timestamps, logs, example files and the steps needed to reproduce the problem before changing more components.
Use one canonical DJI source region
DJI regional or language pages can be indexed or refreshed at different times. A stale regional page does not by itself prove that DJI maintains a separate regional firmware build. To avoid creating a mixed matrix, this tracker uses the linked English/global product downloads and developer documentation as its defined source set and records the checked date. If a Canadian account, controller or DJI tool presents a different eligible build, treat that as a specific environment to verify—not a number to silently merge into this table.
For broader hardware fit, use SpeedyDrone's DJI Enterprise payload compatibility matrix. The Matrice 400 vs Matrice 350 RTK guide retains the platform-selection question; this page owns the current-version and change-control question.
Current SpeedyDrone enterprise product references
Use these exact Canadian product pages when the firmware decision is part of a purchase, fleet refresh or integration review. Product availability can change, so the linked page—not this article—is the current commercial record.
DJI Matrice 4E
Compact enterprise mapping platform tracked with its controller.
View DJI Matrice 4E →
DJI Enterprise firmware FAQ
What is the latest DJI Matrice 400 firmware?
As checked on September 25, 2026, DJI's Matrice 400 downloads page lists aircraft firmware 17.02.50.07 dated June 16, 2026. The same page lists RC firmware 01.64.08.18 and BS100 firmware 01.00.00.13. Recheck the official page before updating.
What is the latest DJI Matrice 4E and Matrice 4T firmware?
DJI's current Matrice 4 Series page lists 17.02.05.01 for both M4E and M4T, dated June 16, 2026. It lists RC Plus 2 Enterprise firmware 01.64.08.20 dated July 10, 2026.
What is the latest DJI Matrice 350 RTK firmware?
DJI's Matrice 350 RTK downloads page lists aircraft firmware 17.03.00.05 and RC Plus firmware 06.02.13.14, both dated August 11, 2026, when this tracker was checked.
What is the latest Zenmuse H30T firmware?
The Zenmuse H30 Series downloads page lists firmware 10.06.01.06 dated March 31, 2026. Check its release notes, Known Issue List and aircraft support before deployment.
What is the latest Zenmuse L3 firmware?
DJI's Zenmuse L3 downloads page lists 17.02.00.04 dated August 3, 2026. The complete workflow also includes the M400, Pilot 2 and DJI Terra.
What is the current DJI Terra version?
DJI's Terra downloads page lists version 5.3.5 dated August 20, 2026. A production mapping team should process representative data before changing the standard workflow.
Should Matrice 350 use the latest PSDK?
Not by default. DJI's current recommended-version table places M350, M300, M30, Mavic 3 Enterprise, M3D and M3TD on PSDK 3.9.2. M400, Matrice 4, Manifold 3 and later models are in the latest-PSDK group.
Should I update enterprise firmware immediately before a mission?
Usually, allow time for validation. Review the change, test one representative system, validate the real mission workflow and then roll it out. The exact decision depends on the release, mission and urgency.
Can DJI Enterprise firmware always be downgraded?
No universal rollback promise should be made. Downgrade availability and supported versions depend on the exact product and current DJI tools. Verify rollback before changing a production system.
Tracker maintenance log
September 25, 2026: Initial local tracker package prepared. Verified Matrice 400, Matrice 4 Series, Dock 3, Matrice 350 RTK, H30 Series, L2, L3, Terra and PSDK documentation.
Planned maintenance: Recheck at least monthly and after major DJI Enterprise releases. A planned cadence is not evidence that a future check occurred; this log will record each completed review.
Plan the stack, not just the update
Tell SpeedyDrone which aircraft, controller, Dock, payload, software and third-party integrations are in your workflow. We can help frame the compatibility and procurement questions before you change a production fleet.
Request an enterprise compatibility reviewSource note: Versions were checked against the linked DJI Enterprise downloads and DJI Developer pages on September 25, 2026. This reference tracks published information; it is not a guarantee for every mixed-version configuration. Recheck the exact official pages, release notes, known issues and the software presented by your device before updating.
