Defining map variables
Now that you have added the table, you can create the input map.The input map will consist of a collection of map variables. The plant floor engineer will see these variables when defining the trigger. During runtime, the variables are mapped to physical PLC device variables (when a plant floor event occurs).
Since there are 5 required columns in the example table, you will want to map 5 data items (from the production line) into the table. These data items will be defined by using 5 logical names (not the real PLC device variable or alias names). The resolution of these map variables to production line data will occur when you create the trigger.
There are two methods for defining the map variables:
- Create each map variable separately.
- Create the map variables automatically at one time.
Since this example uses a database transport, the Map Table button can automatically create the map variables.
From the ToEnterprise section, click Map Table.
.
The map variables are automatically added to the
Input tab.
Output map: Because the transport map is based on a database Insert operation, an output map is not applicable. If a transport map is bi-directional then the trigger will expect data that is queried from an enterprise system to be sent to it in the output map. |