flighttask_create
DJI Services · wayline · flighttask_create
Request Params
Fixed value
djiTarget device ID
Fixed value
flighttask_createIdempotency key; repeated requests return the same command
Timeout in seconds, range
0~300Method payload field
Optional execution time (timestamp)
Task type: immediate, timed, conditional
Wayline type: wayline, mapping_2d, mapping_3d, mapping_strip
Wayline file URL
Number of execution times
Action when out of control: continue, execute_go_home, hover
Return to home altitude
Task name
Ready conditions (for conditional tasks)
Executable conditions
Simulation settings
Breakpoint information for resume
Return to home mode (0=smart, 1=preset)
Exit wayline when RC lost (0=continue, 1=exit)
Wayline precision type (0=GPS, 1=RTK)
Flight safety advance check
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.