---
alias: user-guide-automation-task-secsgem-mapupdated
tags:
- automation tasks
description: "This task processes SECS/GEM messages for map updates, triggering various data outputs and settings"
---

# Map Updated (S12F1 + S12F5 + S12F9)

![1562150204114](images/mapupload-lg.svg)

When activated, the `Map Updated` task will handle `S12F1` (Map Setup), `S12F5` (Map Transmit Inquire) and `S12F9` (Map Data Send) SECS/GEM messages from the equipment.

![Screenshot showing a map update settings page with fields for string, integer, and boolean values.](./images/mapupdated_01.png)

## Inputs

| Name           | Data Type | Description                                                  |
| -------------- | --------- | ------------------------------------------------------------ |
| Enable/Disable | `Boolean` | Enable/Disable listeners for specific mapping SECS/GEM messages |

## Outputs

| Name               | Data Type | Description                                          |
| ------------------ | --------- | ---------------------------------------------------- |
| materialId         | `String`  | Material identified by the equipment                 |
| idType             | `Integer` | materialId type                                      |
| mapFormat          | `Integer` | Map format requested                                 |
| notchLocation      | `Integer` | Location of Notch                                    |
| frameRotation      | `Integer` | Rotation of the Frame                                |
| originLocation     | `Integer` | Location of the Origin                               |
| processAxis        | `Integer` | Axis to process                                      |
| nullBinCode        | `String`  | Null bin codes                                       |
| referencePoints    | `Object`  | Reference Point of the map data                      |
| unitsOfMeasurement | `String`  | Units of measurement                                 |
| xDies              | `Integer` | Size of die (x axis)                                 |
| yDies              | `Integer` | Size of die (y axis)                                 |
| rowCount           | `Integer` | Number of rows in map                                |
| colCount           | `Integer` | Number of columns in map                             |
| processDieCount    | `Integer` | Total number of dies                                 |
| startingPosition   | `Object`  | Starting position coordinates                        |
| mapString          | `String`  | Map data as string                                   |
| mapArray           | `Object`  | Map data as array of strings                         |
| mapData            | `Object`  | Object with entire representation of the updated map |
| 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, you have the usual settings and the following settings:

| Name                        | Data Type | Values   | Default      | Description                                                  |
| --------------------------- | --------- | -------- | ------------ | ------------------------------------------------------------ |
| Auto Enable Events Handling | `Boolean` |          | `true`       | Automatically enable listeners for expected messages at start-up |
| Timeout                     | `Integer` |          | 10 (minutes) | Maximum amount of time allowed to keep the map data          |
| Bin List Format Data Type   | `Enum`    | `A`, `L` | `A`          | Data type expected in `BINLT` field when reading map         |

![Screenshot showing a settings page with an option to update map data.](./images/mapupdated_02.png)

## Behavior

In this task you choose a driver when dropping it into the workflow (if you have more than one driver associated with the controller).

This task automatically handles the `S12F1`, `S12F5` and `S12F9` messages when sent from the equipment in order to receive the updated map information. When all data is received, all outputs are emitted with the corresponding data for processing

## Remarks

{% include-markdown 'includes/pages/automation_zones_note.md' %}