A firmware prompt that appears beside a launch site creates the wrong kind of urgency. The screen says an update is available; the weather window is closing; everyone is waiting. It is tempting to tap “Update” and treat the progress bar as a short delay before take-off.

That is a poor place to discover a weak battery, unreliable mobile data or a controller that also needs attention. Firmware is maintenance. It deserves a calm bench, stable power and enough time to verify the whole aircraft system after the installation—not a hurried patch on the ground.

An update touches more than one screen

On many consumer platforms, “the drone” is a set of devices: aircraft, remote controller, intelligent batteries, goggles or other accessories, plus the phone and app used to manage them. A version change can involve several of those components. Finishing one download does not prove that every battery or controller in the kit is ready.

DJI’s official firmware update guide describes two common paths: updating through the relevant app or using the correct DJI Assistant 2 software on a computer. It tells users to keep the mobile device connected to the network during the download and not to power off the aircraft or leave the app during installation. The aircraft may restart as part of the process.

Those are ordinary requirements at home. At a rural take-off point, they can become the failure list: marginal reception, a phone switching tasks, a cable being moved, or a battery starting the update with less charge than expected.

Make the update a separate maintenance session

Choose a place where the aircraft can sit safely with propellers unable to start accidentally. Charge the aircraft and controller above the minimum specified for the exact model. DJI’s general update-failure guidance tells users to keep both above 50 percent, while some model-specific support pages state a different minimum. The model manual and current product page should win over a remembered rule of thumb.

Then allow time for four separate jobs:

1. Read the release notes and decide whether the update is relevant now. Do not assume every manufacturer offers rollback.
2. Update the aircraft and controller using the method named for that model. Keep power, network and cables stable until the system reports completion.
3. Insert and check each flight battery if the platform distributes battery firmware through the aircraft.
4. Restart everything and let the app reconnect before changing settings or packing the kit.

If an update fails repeatedly, stop treating retries as progress. Record the error, confirm that the software version matches the aircraft family, and use the manufacturer’s documented recovery path or support channel. Randomly downloading an Assistant package intended for another product line is not troubleshooting.

The post-update check is part of the update

A successful installation message is not a pre-flight inspection. Firmware can reset or expose settings that deserve a fresh look. Before the next operation, check the app-reported versions, control mode, return-to-home altitude, maximum altitude and distance settings, obstacle-sensing behaviour, camera storage, Remote ID status where applicable, and any geospatial or authorization data used by the platform.

Next, perform the manufacturer’s normal pre-flight checks in an open, legal area. Confirm that the correct home point is recorded, satellite and compass indications are normal, the controller inputs respond as expected, and the battery data is plausible. A short, low-risk check flight may be appropriate where rules and the manual allow it; it is not a substitute for reading warnings on the screen.

There is also a simple operational reason to update early: if something is wrong, postponing the flight remains an easy decision. At the launch point, sunk travel time and social pressure make people more likely to rationalise an unfamiliar warning.

This is not an argument for ignoring updates. It is an argument for giving them their own time. Check for firmware before packing, complete it on stable power and connectivity, verify the settings that matter, and arrive with a known configuration rather than a progress bar.