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.
! The system parameter "SYS.EnableDeviceManager" has to be set to "ON".
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;IP Address of Gateway;Polling interval (sec);Description;Alias '
1.1.1;192.168.1.7;20;Device 1;Switch 1
1.1.2;192.168.1.8;40;Device 2;
Each line – except comment lines that start with ' – defines a single KNX device.
<tr> <td>1</td> <td>Physical KNX Address</td> <td></td> <td> This attribute specifies the physical KNX Address of the device which shall be monitored. </td> </tr>
<tr> <td>2</td> <td>IP Address of Gateway</td> <td></td> <td> This attribute defines the
IP address of the gateway via the device is reachable. "BROADCAST" is not supported in this case. </td>
</tr>
<tr> <td>3</td> <td>Polling interval</td> <td></td> <td> This attribute defines the polling interval in seconds. </td> </tr>
<tr> <td>4</td> <td>Description</td> <td></td> <td> This attribute can be used to specify a human-readable text that further describes the device (can be any user-defined string). </td> </tr>
<tr> <td>5</td> <td>Alias</td> <td></td> <td> It defines an alias name for the server item that represents the KNX device. This alias is shown within the server item tree under the sub tree "Alias" (cf. Section 1.3.2). </td> </tr>
General
Content
Integrations