​
do_land_start

PX4 capability domain: do-control. PX4 mapping: MAV_CMD_DO_LAND_START. Mission item to mark the start of a mission landing pattern, or a command to land with a mission landing pattern. When used in a mission, this is a marker for the start of a sequence of mission items that represent a landing pattern. It should be followed by a navigation item that defines the first waypoint of the landing sequence. The start marker positional params are used only for selecting what landing pattern to use if several are defined in the mission (the selected pattern will be the one with the marker position that is closest to the vehicle when a landing is commanded). If the marker item position has zero-values for latitude, longitude, and altitude, then landing pattern selection is instead based on the position of the first waypoint in the landing sequence. When sent as a command it triggers a landing using a mission landing pattern. The location parameters are not used in this case, and should be set to 0.

​
Request Params

​
vendor
string
必填
Fixed value px4
​
device_id
string
必填
Target PX4 device ID
​
command_type
string
必填
Fixed value do_land_start
​
idempotency_key
string
必填
Idempotency key; repeated requests return the same command
​
timeout_seconds
integer
Timeout in seconds, range 0~300
​
payload
object
必填
Typed request payload for this command. Field names are generated from PX4 MAVLink XML labels, but callers do not send raw param1..param7 fields.
​
payload.latitude
number
Meaning: Latitude; maps to MAVLink parameter 5 in the PX4 frame.
​
payload.longitude
number
Meaning: Longitude; maps to MAVLink parameter 6 in the PX4 frame.
​
payload.altitude
number
Meaning: Altitude, units m; maps to MAVLink parameter 7 in the PX4 frame.

​
PX4 Frame Mapping

  • MAVLink command: MAV_CMD_DO_LAND_START
  • Command ID: 189
  • Default transport: COMMAND_INT
  • Source XML: common.xml
  • Completion: COMMAND_ACK
  • Guard: real PX4 downlink is disabled by default; guarded mode requires explicit authorization and a ready transport.

​
Create Response

​
command_id
string
Platform command ID, used for follow-up queries
​
status
string
Acceptance status: ACCEPTED
​
accepted_at
string(datetime)
Command acceptance time (UTC)

​
Query Response

​
command_id
string
Platform command ID
​
status
string
Execution status: ACCEPTED / DELIVERED / SUCCEEDED / FAILED / TIMED_OUT / UNMATCHED_RESPONSE
​
vendor
string
Vendor identifier; fixed value px4
​
device_id
string
Target PX4 device ID
​
command_type
string
PX4 command type
​
response_code
string
Mapped COMMAND_ACK.result value
​
response_message
string
PX4 acknowledgement summary
​
vendor_response
object
Raw PX4 acknowledgement summary, including MAVLink command ID and transport

​
PX4 ACK Mapping

After sending the frame, the PX4 agent waits for COMMAND_ACK and correlates the response by command id. Disabled mode sends no frame and completes with a rejected lifecycle result. 
curl -X POST "/api/v1/open/downlink/commands" \
  -H "Content-Type: application/json" \
  -H "X-Api-Id: YOUR_API_ID" \
  -H "X-Api-Timestamp: YOUR_UNIX_SECONDS" \
  -H "X-Api-Nonce: YOUR_NONCE" \
  -H "X-Api-Signature: YOUR_SIGNATURE" \
  -d "{\"vendor\":\"px4\",\"device_id\":\"px4-real-1\",\"command_type\":\"do_land_start\",\"payload\":{\"latitude\":473566000,\"longitude\":85432100,\"altitude\":30.0},\"idempotency_key\":\"req-do_land_start-001\",\"timeout_seconds\":30}"

curl "/api/v1/open/downlink/commands/8cdb5bf3-8902-c5f7-f9aa-dc7fa0af1de0"

{
  "command_id": "8cdb5bf3-8902-c5f7-f9aa-dc7fa0af1de0",
  "status": "ACCEPTED",
  "accepted_at": "2026-06-15T00:00:00Z"
}