Get Pick Map#
This task implements to request and pre-process maps from the MES system.
Details#
| Fields | Details |
|---|---|
| Scope | Connect IoT Data Platform Enterprise Integration Factory Automation |
| Workflow | Data flow Control flow |
IsProtocol flag |
Inputs#
| Name | Data Type | Optional | Description |
|---|---|---|---|
| materialName | String | No | Name of material that identifies the processing material |
| mapName | String | Yes/No | Name of the Map in MES (optional if mapContent is filled) |
| mapContent | String[][] as Object | Yes/No | Content of the map to process (optional if mapName is filled) |
| mapNotch | Integer | Yes/No | The map notch. Must be provided if the map content is provided as well |
| notchLocation | Integer | Yes | The notch location the equipment is requesting |
| frameRotation | Integer | Yes | The film frame rotation the equipment is requesting |
| originLocation | Integer | Yes | The origin location of the equipment system coordinates |
| processAxis | Integer | Yes | The process axis the equipment is requesting |
| nullPickCode | String | Yes | The null pick code the equipment is requesting |
| pickRules | object[] as object | Yes | The pick rules to generate the map |
| referenceDies | Integer[] as Object | Yes | The list of reference dies |
| Activate | Any | Activate the task |
Outputs#
| Name | Data Type | Description |
|---|---|---|
| pickMap | Object | The pick map object |
| pickMapMatrix | String[][] as Object | The pick map content in matrix format |
| pickMapArray | String[] as Object | The pick map content in array format, in the sequence defined by the processAxis |
| pickMapString | String | The pick map content in string format, in the sequence defined by the processAxis |
| Success | Boolean | Triggered when the task is executed with success |
| Error | Error | Triggered when the task failed for some reason |
Settings#
On the General Tab, there are the following settings:
| Name | Data Type | Values | Default | Description |
|---|---|---|---|---|
| Notch Location | Enum | 090180270 | 0 | Angle where the notch is located in the material |
| Frame Rotation | Enum | 090180270 | 0 | Angle of the frame rotation relative to the material |
| Origin Location | Enum | 01234 | 0 | Origin Location of the refences.0 - Center die of substrate1 - Upper right2 - Upper left3 - Lower left4 - Lower right |
| Process Axis | Enum | 01234567 | 0 | Based on the axis, how to generate the resulting map.0 - 1 2 3 4 5, 6 7 8 9 A, B C D E F1 - 5 4 3 2 1, A 9 8 7 6, F E D C B2 - B C D E F, 6 7 8 9 A, 1 2 3 4 53 - F E D C B, A 9 8 7 6, 5 4 3 2 14 - 1 4 7 A D, 2 5 8 B E, 3 6 9 C F5 - 3 6 9 C F, 2 5 8 B E, 1 4 7 A D6 - D A 7 4 1, E B 8 5 2, F C 9 6 37 - F C 9 6 3, E B 8 5 2, D A 7 4 1 |
| Null Pick Code | String | The null pick codes to use for the map |
And the following retries settings:
| Setting | Data Type | Default | Description |
|---|---|---|---|
| Number of Retries | integer | 30 | The maximum number of attempts the IoT process (client) makes to call the MES backend if the connection or execution fails. |
| Sleep Time between retries (ms) | integer | 1000 | Number of milliseconds to wait between retries. It only applies when the previous call fails |
| Number of System Retries | integer | 10 | The maximum number of attempts the MES backend makes to call the target service if the execution fails. |
Multiplicative Retry Effect
Retry limits are cumulative. In the event of a persistent target service failure, the total number of requests generated will be the product of the Client Retries (N) and the Backend Retries (M). For example, if both are set to 10, a single IoT request could result in up to 100 total attempts (N x M), which may lead to system congestion or high latency.
Behavior#
This task is responsible for receiving requests for maps from an equipment or to simply pre-process a previously acquired map, transform it according to the rules and return the resulting map data.

