DJI telemetry
A Dock or Pilot 2 that only reports.
What it carries
Telemetry in. OSD.
Control out. Nothing. This protocol reports and is never commanded.
On this protocol you connect aircraft.
Connect one
- Turn the protocol on. Settings → Integrations → DJI telemetry → enable.
- Declare the device. Settings → Assets → ADD, find the product, pick this protocol. The address you set above is where it is expected to arrive.
The address format
DJI telemetry runs over MQTT, Push. These are the forms that parse:
| Transport | Form | What it means | Example |
|---|---|---|---|
| MQTT | mqtt:BROKER:PORT/TOPIC | A broker and a topic. For an inbound device the broker is ours, so you do not supply it. | mqtt:127.0.0.1:1883/ingest/TOKEN/# |
| Push | push | The device or a sidecar posts to us. No address to configure. | push |
When it is working
The aircraft appears in Settings → Assets with a live health state, and the Integrations row counts it. On the console, its returns start driving tracks within a few seconds.
If nothing arrives
| Symptom | Where to look |
|---|---|
| Nothing arrives, and the row looks healthy | The device is publishing to the wrong topic. Only the topic issued with the credential is routed; anything else is dropped without an error. |
| It connects, then drops | Two things are bound to the same port, or the device and the host disagree about which end dials. See the endpoint forms above. |
The protocol itself
This one has no public specification to link to.
Where to go next
- All integrations for the protocols this build speaks.
- Onboarding an asset for the add flow in full.
- Supported hardware for the products that use it.