Wayline Management

Overview

Wayline management feature is crucial for the autonomous operations of drones, allowing for batch and intelligent tasks in various industries. The cloud API provides relevant interfaces to enable sharing, viewing, issuing, canceling, and progress reporting of wayline tasks via the cloud. Users must follow the Wayline File Format Specification (WPML) to write wayline files and define wayline tasks. Multiple waylines can be defined in one wayline task.

Refer to the "Detailed Interface Implementation" section for the specific wayline task interfaces, the fields used, and their descriptions. If any errors occur while using the wayline management feature, check the corresponding error description using the error codes listed in the Error Codes section.

Interaction Sequence Diagram

Wayline tasks are divided into immediate tasks and scheduled tasks.

Immediate Tasks and Scheduled Tasks

Detailed Interface Implementation

Note：

• If the task_type is specified as "immediate execution," the device limits the time difference to 30 seconds. If the difference between the time the device receives the instruction and the execute_time exceeds 30 seconds, an error will be reported, and the task will not execute properly.
• If the device is already executing a wayline task and receives another task execution command, the new wayline task will not execute, and an error will be reported.
• Wayline task commands currently require the drone to be powered off or have its propellers stopped before execution.

Wayline Management (MQTT)

• Reporting Wayline Task Progress
  Wayline task progress can be reported, including both progress and additional information.
• Issuing Tasks
  Wayline management now includes the concept of "pre-release." Tasks can be issued to the ground station and drone ahead of time to allow for preparation. After the issue task interface is called, the execute task interface must be called to start the task. The task_type specifies the task type, and execute_time is required for both scheduled and immediate tasks, but not for conditional tasks. The ready_conditions field is mandatory for conditional tasks, and if all conditions are met, a flighttask_ready event notification will be sent. The executable_conditions field is not limited to any task type; it applies to all task types and can be used to restrict execution conditions. If left empty, there are no restrictions.
• Executing Tasks