Item alias definitions
- dominik.kurfner (Unlicensed)
- Robert Schneider
- Wolfgang Granzer
File location of configuration:
<WorkspaceDirectory>\DataFiles\nxaAliases.40.dat
Aliases can be used to give any server item a user-defined name. Aliases can be seen as a short-cut to the original server item. Therefore, an alias is not a copy of the source item – it is just alternative way to access an item. Aliases can be used to give physical datapoints a more descriptive name. Furthermore, aliases can also be arranged in a user-defined hierarchy.
The structure of the alias definition file is as follows:
' Aliases Definition File
'
' SourceItemID;Name;Path;Comment
NETx\XIO\KNX\BROADCAST\03/0/002;LightOff;BuildingA\Floor1\;
NETx\XIO\BACnet\Device1\ANALOG_VALUE_0\ANALOG_VALUE_0 - PRIO 15;HeatingSetpoint;BuildingA\Floor1\RoomA;
Each line – except comment lines that start with ' – defines a single alias.
FieldNo | Field | Mandatory/Optional | Description |
|---|---|---|---|
1 | SourceItemID | M | This is the source ItemID of the alias. |
2 | Name | M | Here, the name of the alias has to be specified. |
3 | Path | O | Optionally, the alias can be arranged in a hierarchy which can be defined here. The different levels of the hierarchy must be delimited with backslashes |
4 | Comment | O | Optional comment of the alias definition. The value is only used for documentation purposes. |