Understanding Commands

Introduction

Dronelink unlocks full, programmatic control of your drone, gimbal(s), and camera(s) through the use of commands. Commands represent individual instructions, such as setting the RTH altitude of the drone or starting video capture on the camera, and they usually require inputs. The Dronelink flight controller is built out of commands at the code level, and you can extend the flight controller by accessing these same commands though command components.

Inputs

Command components allow you to specify and save command inputs during the planning phase. For example, the camera mode command takes the mode as an input (photo, video, etc), and you may need multiple camera mode command components in a single plan to change the camera from photo to video and back again.

Failure Mode

Commands are not always required for the success of a mission. For example, you may prefer a 3:2 photo aspect ratio, but not all cameras support this aspect ratio. You can mark command components as not required, meaning that if the command fails, the mission will continue as normal. Conversely, if a required command component fails, the Dronelink flight controller will immediately fail the entire mission and stop execution.

Continue to Collaborating