- Source release: August 18, 2026.
- Review the generated route in the actual environment.
- A software feature does not establish hardware or operating readiness.
What the release changes
DJI’s August 18, 2026 announcement describes Copilot route generation from supported inputs, including text, waypoints, areas and points. It also discusses O4 Ground Station integration and changes to analysis and automation.
This is a review of that dated release, not a claim that it is the latest release or that every function is available in every U.S. account or deployment edition. Verify the required feature in the organization’s actual environment.
- 01GenerateSupported mission inputs
- 02ReviewSite + aircraft + capture behavior
- 03VersionNamed operator + accepted route
Generated does not mean accepted
Compare the proposed route with the job before saving it as an operating plan. Review the area, aircraft, altitude references, capture actions and the mission’s end behavior. A route that looks plausible in a preview can still be wrong for a particular site.
Keep the operator’s changes with the task record. When the same mission is repeated, the team should know which version was reviewed and what changed after generation.
A release check for an existing team
| Check | What to establish |
|---|---|
| Account and deployment | Feature is present in the actual environment. |
| Aircraft and mission type | The proposed workflow supports the selected hardware. |
| Site and capture behavior | Generated actions match the task and operating plan. |
| Review and version | A named operator accepts the final route. |
| Output path | The data reaches the expected review location. |
Keep hardware scope separate
A software integration announcement does not place the required device in an existing hardware order. Check the needed device, configuration and U.S. availability independently.
Test the feature with a bounded representative task before changing recurring missions. Note which manual steps it removes and which review steps remain. That gives the team an implementation decision instead of an unqualified “AI makes it automatic” promise.