Transport Receiver#
The task Transport Receiver is a Task that performs fleet management (AGV) through the message bus. It receives commands (typically from factory automation workflows) and relays the data to the fleet managing driver
Inputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
| fleetManagerType | string | Fleet manager type (to differentiate between implementations) | |
| Activate | Any | Activates the task execution |
Table: Transport Receiver inputs
Outputs#
| Name | Data Type | Values | Description |
|---|---|---|---|
| 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 | |
| id | any | job id | |
| data | any | data for the job | |
| jobId | any | job id | |
| Success | Boolean | If there was no problem emits a true | |
| Error | Error | Error that occurred during the processing of this task |
Table: Transport Receiver outputs
Settings#
On the General Tab, you have the usual settings and the following options settings:
| Name | Data Type | Values | Default | Description |
|---|---|---|---|---|
| Fleet Manager Type | enum | KNAPPMIRCustom | KNAPP | Fleet manager type (to differentiate between implementations). If Custom selected, Fleet Manager Type must be specified. |
| Command | enum | TransportationInteractionCancelTransportationStatusUpdate | Transportation | Command to send to the Fleet manager. |
| Working Mode | enum | UntilDeactivationNumberOfOccurrences | UntilDeactivation | Working Mode for the command execution. |
| Emit in New Context | boolean | true | Create a new execution context when emitting outputs. | |
| Auto Activate | Boolean | false | Determines if the activation should be done when the entity is received. | |
| Number of Occurrences | Integer | 1 | Defines a maximum number of commands in the same topic (typically used by the receiver to count the number of occurred commands). If the number is less than 1, it is considered that there is no maximum number of commands. |
Table: Transport Receiver settings
Additional outputs can be defined in the Outputs tab:
Behavior#
This task is suppose to be used within the workerManager nested workflows (during a job execution). You should provide task related configurations, fleet related configurations (fleet manager type and command to perform) and also communication related settings (timeouts).
Info
The Transport Receiver task is only activated when a value different from False is sent to the Activate input.
Remarks#
None.