Sending custom MAVLink commands in Drone Programming - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a MAVLink command in drone programming?

A MAVLink command is a specific instruction sent to a drone to perform an action, like moving, changing mode, or controlling hardware. It uses a standard message format for communication.

intermediate

Why would you send a custom MAVLink command instead of a standard one?

Custom MAVLink commands let you control special features or hardware not covered by standard commands. They allow you to extend drone capabilities for unique tasks.

beginner

What are the key parts of a MAVLink command message?

A MAVLink command message includes the command ID, target system and component IDs, and parameters that define the command's details.

intermediate

How do you send a custom MAVLink command using a programming library?

You create a command message with the right command ID and parameters, then send it through the drone's communication channel using the library's send function.

beginner

What should you check after sending a custom MAVLink command?

You should check for an acknowledgment message from the drone to confirm the command was received and executed successfully.

What does a MAVLink command ID represent?

A The specific action the drone should perform

B The drone's battery level

C The GPS coordinates

D The drone's speed

The command ID tells the drone what action to perform, like takeoff or change mode.

Which part of a MAVLink command message specifies which drone component to control?

A Parameter 1

B Command ID

C Target component ID

D System time

The target component ID tells the command which part of the drone to control, like the camera or autopilot.

Why is it important to receive an acknowledgment after sending a MAVLink command?

A To confirm the drone received and understood the command

B To check the drone's battery

C To update the drone's firmware

D To start the drone's camera

Acknowledgment confirms the command was received and processed, ensuring reliable control.

What is a common use of custom MAVLink commands?

A Changing the drone's color

B Updating the drone's GPS

C Checking weather conditions

D Controlling special hardware not covered by standard commands

Custom commands let you control unique hardware or features beyond standard commands.

Which programming step is essential before sending a custom MAVLink command?

A Resetting the drone's memory

B Setting the correct command ID and parameters

C Disconnecting from the drone

D Turning off the drone

You must set the right command ID and parameters to tell the drone exactly what to do.

Explain how to send a custom MAVLink command to a drone step-by-step.

Think about preparing the message and confirming it was received.

Why is it useful to create custom MAVLink commands in drone programming?

Consider what standard commands might not cover.

Practice

1. What is the main purpose of sending custom MAVLink commands to a drone?

easy

A. To update the drone's firmware automatically

B. To control the drone with commands beyond the standard set

C. To recharge the drone's battery remotely

D. To change the drone's GPS coordinates manually

Solution

1. Step 1: Understand MAVLink command basics

   MAVLink commands include standard and custom commands to control drones.

2. Step 2: Identify the role of custom commands

   Custom commands allow sending special instructions not covered by standard commands.

3. Final Answer:

   To control the drone with commands beyond the standard set -> Option B

4. Quick Check:

   Custom MAVLink commands extend control [OK]

Hint: Custom commands add new controls beyond defaults [OK]

Common Mistakes:

• Confusing custom commands with firmware updates
• Thinking commands recharge battery
• Assuming manual GPS change via commands

2. Which of the following is the correct way to send a custom MAVLink command with 3 parameters in Python using pymavlink?

easy

A. vehicle.mav.command_long_send(target_system, target_component, command_id, 0, param1, param2, param3, 0, 0, 0, 0)

B. vehicle.send_command(command_id, param1, param2, param3)

C. vehicle.mav.send_command_long(command_id, param1, param2, param3)

D. vehicle.command_long_send(command_id, param1, param2, param3)

Solution

1. Step 1: Recall pymavlink command_long_send syntax

   The correct method is vehicle.mav.command_long_send with parameters: target_system, target_component, command, confirmation, and up to 7 params.

2. Step 2: Match the correct parameter order

   vehicle.mav.command_long_send(target_system, target_component, command_id, 0, param1, param2, param3, 0, 0, 0, 0) correctly uses target_system, target_component, command_id, 0 (confirmation), then params, filling unused with zeros.

3. Final Answer:

   vehicle.mav.command_long_send(target_system, target_component, command_id, 0, param1, param2, param3, 0, 0, 0, 0) -> Option A

4. Quick Check:

   Use command_long_send with full parameters [OK]

Hint: Use command_long_send with all 11 parameters [OK]

Common Mistakes:

• Omitting target_system or target_component
• Using wrong method names
• Not filling unused params with zeros

3. Given this Python snippet using pymavlink:

vehicle.mav.command_long_send(
    1, 1, 300, 0, 10, 20, 30, 0, 0, 0, 0
)

What does the number 300 represent in this command?

medium

A. The command ID for the custom command

B. The first parameter value

C. The confirmation flag

D. The target system ID

Solution

1. Step 1: Identify parameter positions in command_long_send

   Parameters are: target_system, target_component, command, confirmation, param1...param7.

2. Step 2: Locate the third argument

   The third argument (300) is the command ID, which specifies which command to execute.

3. Final Answer:

   The command ID for the custom command -> Option A

4. Quick Check:

   Third argument = command ID [OK]

Hint: Third argument is always command ID [OK]

Common Mistakes:

• Confusing command ID with target system
• Mixing confirmation flag with command ID
• Thinking parameters come before command ID

4. You wrote this code to send a custom MAVLink command but the drone does not respond:

vehicle.mav.command_long_send(1, 1, 400, 1, 5, 10, 15)

What is the likely problem?

medium

A. The command ID 400 is invalid

B. Target system and component IDs must be zero

C. The confirmation flag should be 0, not 1

D. Missing required parameters; command_long_send needs 11 arguments

Solution

1. Step 1: Check command_long_send argument count

   command_long_send requires 11 arguments: target_system, target_component, command, confirmation, and 7 params.

2. Step 2: Identify missing arguments

   The code only provides 7 arguments; missing the last 4 parameters which should be zero if unused.

3. Final Answer:

   Missing required parameters; command_long_send needs 11 arguments -> Option D

4. Quick Check:

   command_long_send needs 11 args [OK]

Hint: Always provide 11 arguments to command_long_send [OK]

Common Mistakes:

• Passing fewer than 11 arguments
• Assuming confirmation must be zero
• Using invalid target IDs

5. You want to send a custom MAVLink command that sets a drone's LED color using command ID 2100 with parameters for red, green, and blue values. Which Python code snippet correctly sends this command assuming target system and component IDs are 1 and 1, and you want red=255, green=100, blue=50?

hard

A. vehicle.mav.send_command(2100, 255, 100, 50)

B. vehicle.mav.command_long_send(1, 1, 2100, 1, 255, 100, 50)

C. vehicle.mav.command_long_send(1, 1, 2100, 0, 255, 100, 50, 0, 0, 0, 0)

D. vehicle.command_long_send(2100, 1, 1, 0, 255, 100, 50, 0, 0, 0, 0)

Solution

1. Step 1: Use correct method and argument order

   command_long_send requires target_system, target_component, command_id, confirmation, then 7 params.

2. Step 2: Fill unused parameters with zeros

   Only 3 parameters used for RGB; remaining 4 must be zero to complete 7 params.

3. Step 3: Confirm target IDs and confirmation flag

   Target system and component are 1, confirmation is 0 (no confirmation needed).

4. Final Answer:

   vehicle.mav.command_long_send(1, 1, 2100, 0, 255, 100, 50, 0, 0, 0, 0) -> Option C

5. Quick Check:

   Correct method, full params, proper IDs [OK]

Hint: Fill unused params with zeros, use confirmation=0 [OK]

Common Mistakes:

• Omitting zeros for unused parameters
• Using wrong method name
• Swapping target system and component order