Overview
The Alias Group object allows custom item names to be linked to protocol item names. This is particularly useful with numeric item names. An Alias Group can be created for use with a single device, a group of devices of the same protocol (if the item names are the same for devices of the protocol), or for the ACM server. Device level alias groups are assigned on the "Options" tab of the device, and a server level alias group is assigned on the Aliasing tab of the $Server object. Device objects may have multiple alias groups while the $Server object can have only one.
...
| Info |
|---|
| In an OPC Client, the item must include the device name. e.g. To retrieve the Mass value from a device named "ModbusOmniDevice", the OPC Item would be "ModbusOmniDevice.Mass". |
| Anchor | ||||
|---|---|---|---|---|
|
When an alias group is assigned to the $Server object, it is the only alias group used by ACM - overriding all other alias group assignments. To create an alias for use at the server level, the item name property must include both the device name and the item name. A $Server alias object can use a string in any format for the alias name, but the item name must contain the device name and the item name. Using the same example from above, an alias for register 5176 could be entered as "ModbusOmniDevice.Mass" or "MassFromOmniDevice". The item name would be entered as ‘ModbusOmniDevice.5176’ (including the device name).
...
ACM Mobile: Sends the items to ACM Mobile app user
Auto Poll: Activate the items internally without waiting for a client to connect and activate them. This is only available if MQTT or ACM Mobile option is not selected.
Interval
This is the schedule interval that is applied to the items in the alias group.
...