DJI Neo 2
Part of the protocol is documented (e.g. telemetry, not control).
Experimental MIT-licensed Linux/Python client for local BLE setup, SWUDP/DUML communication, video reception and selected telemetry on stock firmware. Development reports describe a short takeoff/landing cycle and yaw rotations. Full flight control, link-loss behavior and physical calibration remain incomplete; original hardware captures are private.
- ID
- dji/neo-2
- Category
- drone
- Vendor support
- Unknown
- Updated
- 2026-11-04
Being worked on
No live claim. If you start working on this device, claim it so nobody duplicates your work.
Interfaces
| Interface | Transport | Status | Confidence | Spec / notes |
|---|---|---|---|---|
| BLE setup over GATT/DUML | ble | partial | medium | spec · Selected setup messages implemented; device-specific identities and credentials remain local. |
| Wi-Fi SWUDP/DUML | wifi | partial | medium | spec · Video reception and selected telemetry/control implemented; complete flight control remains unvalidated. |
Projects
| Project | Kind | Origin | License | Freedom |
|---|---|---|---|---|
| DJI Neo 2 LAN client | library | community | MIT | Still non-free: stock firmware · Cloud: unknownSessions use the local BLE/Wi-Fi link; initial vendor activation/account requirements on a new device have not been established. |
What "still non-free" and "cloud" mean
What "still non-free" and "cloud" meanWhat stays proprietary or depends on the vendor's cloud once the project is in use, from the project's own documentation.
- vendor blobs
- proprietary files extracted from the stock firmware
- stock firmware
- the stock firmware stays on the device; the project only talks to it
- modem
- cellular modem firmware
- GPU
- graphics driver or firmware
- Wi-Fi
- Wi-Fi driver or firmware
- Bluetooth
- Bluetooth firmware
- camera
- camera driver or image processing
- sensors
- sensor hub or sensor drivers
- bootloader
- boot firmware
- other
- another proprietary part
- Cloud: none
- works fully locally
- Cloud: only at setup
- a vendor account is needed once, e.g. to obtain a local key
- Cloud: optional
- cloud features exist but are not needed
- Cloud: required
- does not work without the vendor's cloud
- Cloud: unknown
- not known
Verification
Not verified. A "verified on hardware" badge requires a replayable test (hardware-replay) run on a real device with a stated firmware version.
Provenance
- https://github.com/smichea/dji-neo2-lan-client/blob/014e3ad0d3ee98fecba94dfa48fe512a217a155f/docs/PROTOCOL.md
- https://github.com/smichea/dji-neo2-lan-client/blob/014e3ad0d3ee98fecba94dfa48fe512a217a155f/docs/VALIDATION.md
AI-assisted Parts of this record were produced with AI tools (Codex); check the confidence of each interface.
Status and claims as of the build date (2026-11-04). Data licensed CC BY-SA 4.0; imported data keeps its upstream license.