---
alias: user-guide-automation-task-fa-transportcommand
tags:
- automation tasks
description: "The Transport Command task manages fleet operations via a message bus, offering requester, receiver, and replier modes"
---

# Transport Command

The task `Transport Command` is a Task that performs fleet management (AGV) through the message bus. It supports several fleet managing platforms and commands and has three different operation modes:

* **Requester**
    * Sends a command request (to a "Receiver"), typically to other tasks of fleet managing related workflows (that have the specific vendor drivers), waits for and handles the reply.
* **Receiver**
    * Receives commands (typically from factory automation workflows) and relays the data to the fleet managing driver
* **Replier**
    * Receives data from the fleet managing driver and sends the reply to the "Requester"

![transportcommand_parameters][transportcommand_parameters]

## Inputs

| Name        | Data Type | Values | Description                          |
|-------------|-----------|--------|--------------------------------------|
| id          | `any`     |        | request id                           |
| rawValues   | `any`     |        | values to be included in the payload |
| source      | `any`     |        | source of the request                |
| destination | `any`     |        | destination task for the request     |
| priority    | `Integer` |        | request priority                     |
| unit        | `any`     |        | input data for the job to create     |
| Activate    | `Any`     |        | Activates the task execution         |

Table: Transport Command inputs

## Outputs

| Name     | Data Type | Values | Description                                                  |
| -------- | --------- | ------ | ------------------------------------------------------------ |
| data  | `any`  |        | data for the job  |
| message    | `any`     |         | command output message   |
| Success  | `Boolean` |        | If there was no problem emits a true                         |
| Error    | `Error`   |        | Error that occurred during the processing of this task       |

Table: Transport Command outputs

## Settings

On the `General` Tab, you have the usual settings and the following options settings:

| Name          | Data Type | Values   | Default  | Description                                                  |
| ------------- | --------- | -------- | -------- | ------------------------------------------------------------ |
| Task Type      |  `enum`    | `Requester`<br />`Receiver`<br />`Replier` | `Requester` |  Task type to determine the behavior. |
| Fleet Manager Type      |  `enum`    | `KNAPP`<br />`MIR`<br />`Custom` | `KNAPP`  |  Fleet manager type (to differentiate between implementations). If *Custom* selected, Fleet Manager Type must be specified |
| Command      |   `enum`    | `Transportation`<br />`Interaction`<br />`CancelTransportation`<br />`StatusUpdate` | `Transportation`   |  Command to send to the Fleet manager. |
| Attempts      |  `Integer` |          | 100 |  Number of attempts before quitting |
| Sleep between attempts |  `Integer` |          | 5000 | Waiting time between attempts (in milliseconds) |
| Command timeout |  `Integer` |          | 7200000 |  Command waiting time between attempts (in milliseconds) |
| Include Id in Command |  `Boolean` |          | `false` | Defines if is to include id in the command request |
| Clear Inputs (on activate) |  `Boolean` |          | `true` | Defines if it is to clear the input values after receiving an activate |

Table: Transport Command settings

![transportcommand_settings_step_one][transportcommand_settings_step_one]

Additional inputs can be defined in the `Inputs` tab:

![transportcommand_settings_step_two][transportcommand_settings_step_two]

Additional outputs can be defined in the `Outputs` tab:

![transportcommand_settings_step_three][transportcommand_settings_step_three]

## Behavior

This task is supposed to be used within the WorkerManager-nested workflows (during a job execution).
The user should provide task-related configurations (task type), fleet-related configurations (fleet manager type and command to perform) and also communication-related settings (timeouts)

!!! info
	The TransportCommand task is only activated when a value different from *False* is sent to the *Activate* input.

## Remarks

None.

[transportcommand_parameters]: ./images/transportcommand_parameters.png
[transportcommand_settings_step_one]: ./images/transportcommand_settings_step_one.png
[transportcommand_settings_step_two]: ./images/transportcommand_settings_step_two.png
[transportcommand_settings_step_three]: ./images/transportcommand_settings_step_three.png