User manual

DJI enterprise drones (Pilot 2)

Enterprise-range drones — Matrice 4T and 4E, Matrice 30 and 30T, Matrice 300 and 350 RTK, Mavic 3 Enterprise — are not flown with DJI Fly but with DJI Pilot 2, and that changes two things for the better: they can stream RTMP on their own, and they have a cloud module that links the remote controller to the platform. Once that link is up, the logbook fills itself in when you land and the live stream is started from the panel: nothing to type in the field.

If you fly with DJI Fly (Mini, Air, consumer Mavic, Avata, Neo) this section is not for you: your route is Live, with native RTMP or screen-cast.

What you need first

The remote controller needs its own connectivity — SIM, phone hotspot or Wi-Fi: the cloud link is an outbound Internet connection from the controller, it does not go through the aircraft. You also need DJI Pilot 2 up to date and, on the platform, the owner or admin role, because the pairing address carries your organisation's token.

The channel to the platform is encrypted (TLS, port 8883) and you do not have to configure it: the pairing page hands it over. If the controller works behind a company or agency network, that outbound port must be open.

Linking the controller (once)

1. In the panel open Fleet → DJI devices and press «Connect DJI Pilot 2»: the dialog shows the address to open on the controller, with a button to copy it. That address contains your organisation's token — treat it like a password.
2. On the controller open DJI Pilot 2 → Cloud Service and enter the address. The page that opens is Dronetrake's and carries your organisation's name: if it doesn't, the address is incomplete.
3. Press «Activate the link». The page runs licence verification, organisation identity, workspace and broker connection in sequence, and shows the raw result of every step: if something fails, what you see on screen is exactly what's needed to tell where it broke — photograph it and send it to us.
4. On the first connection a ten-minute pairing window opens: the first unknown controller that shows up is attached to your organisation. If you'd rather leave nothing to chance, pre-register the controller's serial with «Create» in DJI devices: the match becomes deterministic and the window is not needed.
5. From then on controller and aircraft appear under DJI devices with model, last contact and available camera views. The link persists: you only redo it if you change controller or use «Detach».

The logbook fills itself in

With the controller linked there is nothing left to import. The platform follows the telemetry and recognises the flight by itself: it opens the entry when the aircraft leaves the ground — above two metres — and closes it on landing, or after a minute of silence if the link drops first. What lands in the logbook is the whole flight: aircraft matched by serial number, take-off and landing times and coordinates, track you can replay on the map, batteries used (unknown ones are registered automatically) and, on thermal models, the highest temperature seen.

Two things to know, so they aren't surprises. First: flights shorter than ten seconds are not recorded — those are motor checks and taxiing, not flights. Second: the controller does not say who was flying, so the entry is created under an organisation manager; if someone else flew it, fix it from the logbook with «Create correction», because the register is append-only and corrections stay visible (that is the EASA rule, not a choice of ours).

The same flight arriving twice still leaves a single entry.

Live: from the panel or by hand

With the cloud link active the stream is commanded from the platform: the «DJI live» action appears on the drone channel, where you pick controller, camera view and quality (Adaptive, Smooth, Standard 720p, HD 1080p, Ultra HD), and the aircraft starts transmitting within seconds. If the platform says the controller has not reported its camera views yet, open the camera view in Pilot 2 and try again: it is the controller that declares them.

Without the cloud link the manual route remains, and Pilot 2 does it well: Transmission → Live streaming → Custom RTMP, paste the channel address (you'll find it in the «How to stream» dialog) and start. It is the same road as consumer drones, except here you need neither HDMI nor screen-cast.

Either way, minutes are counted on the channel that transmits, never on viewers.

When something doesn't add up

• «JSBridge not found», or a page that does nothing: the address was opened in a normal browser. It must be opened inside DJI Pilot 2, from Cloud Service.
• Licence verification failed: almost always Pilot 2 out of date, or a controller with no connectivity. Check the controller really browses.
• Linked but no flights in the logbook: the aircraft may be attached to another organisation — use «Detach» in DJI devices and pair again — or the ten-minute window had already expired when it showed up.
• The commanded live doesn't start: open the camera view in Pilot 2 as above, and check you have minutes left.
• Agency and corporate networks: if pairing never completes, have outbound port 8883 opened.

What it doesn't do (yet)

The cloud link brings flights and live, not media: photos and video are uploaded to Media as usual. It doesn't recover the past either — for flights already flown, the Airdata import and CSV files are still there. And it only applies to Pilot 2 aircraft: the consumer range has no cloud module, and for that the right guide is Live.