takeoff_to_point
DJI Services · drc · takeoff_to_point
Request Params
Fixed value
djiTarget device ID
Fixed value
takeoff_to_pointIdempotency key; repeated requests return the same command
Timeout in seconds, range
0~300Target point latitude (-90 to 90)
Target point longitude (-180 to 180)
Target point height (ellipsoidal height, WGS84)
Safe takeoff height (relative to dock ALT)
Method payload field
Return home altitude (relative to dock ALT)
RC lost action (0=hover, 1=land, 2=RTH)
[Deprecated] Wayline lost action (0=continue, 1=exit)
Method payload field
Method payload field
Method payload field
One-key takeoff mission UUID
Max speed (1-15 m/s, optional)
Method payload field
Create Response
Platform command acceptance identifier; globally unique UUID
Acceptance status:
ACCEPTEDCommand acceptance time (UTC)
Query Response
Platform command acceptance identifier; globally unique UUID
Execution status:
ACCEPTED / DELIVERED / SUCCEEDED / FAILED / TIMED_OUT / UNMATCHED_RESPONSEVendor identifier; fixed value
djiTarget device ID
Method name
Device-side execution code
Device-side execution message
Raw vendor response (passthrough)
DJI Services Reply Mapping
The device returns command results throughservices_reply. The platform correlates the reply to command_id through tid and updates the command lifecycle. Clients do not consume the MQTT reply channel directly.
| Open Platform field | DJI services_reply source |
|---|---|
response_code | Prefer data.code; fall back to data.result when code is absent |
response_message | data.message / data.msg / data.description |
vendor_response | Normalized DJI reply summary preserving result, code, message, output, and vendor extension fields |
data.result = 0 means device-side execution succeeded. Non-zero values mean device-side execution failed, and the platform moves the command to a failed terminal state.