TODO: Still exist ?? YES
Location:
<WorkspaceDirectory>\DataFiles\nxaKNXObjectDefinitions.dat
| Info |
|---|
! This definition file can also be generated using the ETS app import wizard (Studio → KNX → Inport NETx ETS App file ...) which generates the ETS object definitions from an exported ETS project. |
Within this configuration file, the KNX communication objects as represented in the item tree are specified. The structure of the definition file is as follows:
'Syntax of the ETS Object Definition Table:
'Name;Object function;Device name;Path;Communication flag;Read flag;Write flag;Transmit flag;Update flag;Read on init flag;Physical address;IP address;Group addresses (first one is sending)
Output A;10: Switch;Room1 - Light HVAC Actuator;Demo_Case_Large\Buildings\BuildingA\Floor1\Cabinet1\3.1.1;T;F;T;F;F;F ;3.1.1;192.168.1.15;0/0/1@192.168.1.15
Output A;29: Status Switch;Room1 - Light HVAC Actuator;Demo_Case_Large\Buildings\BuildingA\Floor1\Cabinet1\3.1.1;T;T;F ;T;F;F;3.1.1;192.168.1.15;0/0/2@192.168.1.15
Output B;30: Switch;Room1 - Light HVAC Actuator;Demo_Case_Large\Buildings\BuildingA\Floor1\Cabinet1\3.1.1;T;F;T;F;F;F ;3.1.1;192.168.1.15;0/0/3@192.168.1.15
Output B;49: Status Switch;Room1 - Light HVAC Actuator;Demo_Case_Large\Buildings\BuildingA\Floor1\Cabinet1\3.1.1;T;T;F ;T;F;F;3.1.1;192.168.1.15;0/0/4@192.168.1.15
Each line – except comment lines that start with ' – defines a single communication object.
! The ETS object definitions within this file are automatically created by the NETx BMS App. Therefore, editing it manually is not necessary in general.
...
| 1 | Name | This parameter refers to the name of the communication object. | |||||
| 2 | Object function | Here the name of the function of the communication object is specified. | |||||
| 3 | Device name | This is the device name to which the communication object belongs to. | |||||
| 4 | Path | This column defines the path within the ETS view where the communication object is shown. | |||||
| 5 | Communication flag | The KNX communication flag of the communication object. For more information see ETS documentation. | |||||
| 6 | Read flag | The KNX read flag of the communication object. For more information see ETS documentation. | |||||
| 7 | Write flag | The KNX write flag of the communication object. For more information see ETS documentation. | |||||
| 8 | Transmit flag | The KNX transmit flag of the communication object. For more information see ETS documentation. | |||||
| 9 | Update flag | The KNX update flag of the communication object. For more information see ETS documentation. | |||||
| 10 | Read on init flag | The KNX read on init flag of the communication object. For more information see ETS documentation. | |||||
| 11 | Physical address | The physical address of the device where the communication object is located. | |||||
| 12 | Reserved | Not used. | |||||
| 13 | Group addresses (first one is sending) | The KNX group addresses that are linked to the communication object. The first group address is the sending group address i.e. the address which is used for send whenever the communication object changes its value. |
...