KNX device definitions.
- dominik.kurfner (Unlicensed)
- Wolfgang Granzer
- Nahel Falhout (Unlicensed)
Location:
<WorkspaceDirectory>\DataFiles\nxaDeviceDefinitions.35.dat
The KNX device manager can check the availability of KNX devices. It tries to connect to the defined devices to verify whether they can be reached or not. If the connection fails, the value of the corresponding server item of the device is set to false. This feature is mainly used to check the availability for important devices. Note that the monitoring of KNX devices consumes network bandwidth within the KNX network, so it should only be used when necessary. Note that the telegrams that are used to verify the availability of KNX devices are not group telegrams and so they are not shown in the telegram monitor.
! This definition file can also be generated using the ETS app import wizard (Studio → KNX → Inport NETx ETS App file ...) which generates the KNX device definitions from an exported ETS project.
The device definition file specifies all the devices that shall be checked. The structure of this file is as follows:Â
'Syntax of the Device Definition Table:
'physical KNX Address;Name of Gateway;Polling interval (sec);Description;Alias '
1.1.1;Router1;20;Device 1;Switch 1
1.1.2;Router2;40;Device 2;
Each line – except comment lines that start with ' – defines a single KNX device.
| 1 | Physical KNX Address | This attribute specifies the physical KNX Address of the device which shall be monitored. | |
| 2 | Name of Gateway | This attribute defines the name of the gateway via the device is reachable. "BROADCAST" is not supported in this case. | |
| 3 | Polling interval | This attribute defines the polling interval in seconds. | |
| 4 | Description | This attribute can be used to specify a human-readable text that further describes the device (can be any user-defined string). |