Entity Instance#
The Entity Instance task loads the MES instance associated and makes it possible to access all its attributes. Typically, this is task is used along with equipment setup to correctly identify the specific parameters.
Inputs#
| Name | Data Type | Description |
|---|---|---|
| Activate | any | Activates the task |
Outputs#
| Name | Data Type | Description |
|---|---|---|
| instance | Resource | The Resource instance |
<custom list> | <custom> | Selected list of Resource attributes |
| Error | Error | Error that occurred during the processing of this task |
Settings#
On the General Tab, you have the usual settings and the following load instance options settings:
| Name | Data Type | Default | Description |
|---|---|---|---|
| Auto Activate | Boolean | false | Determines if the activation should be done when the entity is received |
| Load all attributes | Boolean | false | Loads all the attributes for the Entity |
| Reload in every change | Boolean | true | Flag indicates if the Entity is to be updated every time the tasks receives an Activate input |
| Levels to load | Integer | 0 | Levels to load from the Entity associated |
On the Attributes Tab, you have all the attributes of the Entity. The selected attributes will be the one's available for outputs.
Behavior#
The typical configuration is when the Equipment Setup task starts, which means it has connected to a driver process, it will activate the entity instance task. Then the necessary attributes are retrieved and are used to activate the connect input of the Equipment Setup task, sending all the connection parameters to the driver. This is done this way, because most of the times parameters such as ports or Ip addresses needed for the driver connection are stored as an attribute of an entity, and therefore, reuse the same controller with more than one equipment of the same time.
Remarks#
It is possible to have multiple drivers and therefore multiple Equipment Setup tasks on the same controller, when this is the case you would have to use the onInitialize output of one of the Equipment Setup tasks to activate the Entity Instance task and then use the output of the Entity Instance task to activate both the Equipment Setups, this is assuming both your drivers have dependencies on the resource attributes.
