7.9 Task Execution Section

7.9.1 Overview

AimMaster provides a guided task feature, allowing users to create guided tasks on AimMaster and use programmatic interfaces for invocation and other operations.

Note that task creation, editing, deletion, and other operations still need to be performed through the AimMaster software. The programmatic interface only provides basic functions such as starting, pausing, and canceling tasks.

7.9.2 Single Task Information RPC Interface

{
  "task_id": "1"
}

{
  "data": [
    {
      "task_id": "1",
      "name": "task1",
      "is_valid": true,
      "state": "StateType_IDLE",
      "duration": "0",
      "setting": "task_type: interaction_1 xxx YAML content"
    }
  ]
}

7.9.3 All Tasks Information RPC Interface

{}

{
  "data": [
    {
      "task_id": "1",
      "name": "task1",
      "is_valid": true,
      "state": "StateType_IDLE",
      "duration": "0",
      "setting": "task_type: interaction_1 xxx YAML content"
    }
  ]
}

7.9.4 Task Execution RPC Interface

The task execution interface requires the use of two interfaces: first, call SetCurrentTask to set the current task, then call LaunchTask to start the task.

Before calling LaunchTask to start a task, you must switch the SM (System State Management) module to the Auto functional group. This is achieved by executing the following synchronous interface:

curl -i -H 'content-type:application/json' -X POST 'http://192.168.100.110:51056/rpc/aimdk.protocol.SystemService/MigrateSystemStateSync' -d '{"state": "Auto"}'

If this step is not performed, the call may return the result res: ReturnType_FAIL_UNKNOWN.

{
  "task_id": "15"
}

{
  "task_id": "15",
  "is_success": true
}

{
  "task_id": "15"
}

{
  "task_id": "15",
  "res": "ReturnType_SUCCEED"
}

7.9.5 Task Control RPC Interface

{
  "task_id": "15",
  "type": "Type_PAUSE"
}

{
  "task_id": "15",
  "res": "ReturnType_SUCCEED"
}