This Device Info function is mainly used to check whether the:
- correct application program has been downloaded to a bus device or
- the appropriate application module has been mounted
ETS will automatically activate the bus connection to read out parts of the device memory. The data will be analyzed, and the result will be displayed.
The Device info operation can be invoked via the:
- right mouse click on a device 'Info > Device Info or Device Info (With Group Communication)'
- context toolbar 'Info > Device Info or Device Info (With Group Communication)'
- menu bar 'Diagnostics > Device Info'
To read out the group addresses that have been assigned to all the group objects of a device, one can select the option '... with Group Communication', so that the result includes this information too. In concrete, there are two execution types for Device Info, i.e. 'Device Info' and 'Device info (with group communication)'. When the latter option is selected, the group addresses assigned to the group objects are also read out.
Result display
Once the Device Info is triggered, the 'Pending Operations' in the sidebar is opened and the action (i.e. Device Info: Finished) is shown. Click the 'History' tab and then the icon to display the Device Info results. This opens a new modal window.
Menu bar
| Menu item | Description |
| Save | Allows saving the results in HTML file format. |
| Allows to print the results. | |
| Close | Closes the result window. |
Content
The device information is shown in formatted and unformatted form, i.e. once as numerical value and once as interpretation of the numerical value. Details on how to interpret the results are included in the KNX Specifications. Depending on the mask version of the device, there will be more or less elements. Here, only the general meanings are listed:
| Element (General) | Description |
| Mask version | Current mask version of the bus device |
| Individual Address | Individual address of the bus device |
| Device manufacturer | Name of the manufacturer of the bus device |
| Order number | Order number, if provided by the manufacturer in readable/decodable form (otherwise hexadecimal) |
| Serial number | Unique device hardware ID |
| Firmware Version | Firmware version of the device |
| Bus Voltage | Bus voltage measured by the device |
| Programming Mode | Status of the programming LED |
| Run error | Error in the device while executing the program (if no error → OK) |
| Hardware PEI type | Adapter type of the hardware |
| Element (Application Program) | Description |
| Application program | Application program name + version |
| Load state | Status of the device's loading procedure |
| Run state | Status of the application program (e.g. stopped, running, paused) |
| Software PEI type | Designation of the configured adapter type (if PEI type = 01, then invalid adapter type) |
| Element (Group Communication) | Description |
|
Loaded status of the tables with text/value (if available in device because group address/group object has been created) |
| Group Objects |
Object number; (object size/flags/priority)
|
For couplers, you will see here information about the coupler type and its capabilities, such as the 'max. routing APDU length', the current routing configuration (e.g. main line --> sub line), security settings (if any) etc.
For some devices, it is not possible to read the group communication at all, independently of whether group addresses and group objects exist for this device. In this case, the information on the group communication (group object) is displayed as "not implemented".
Devices with different properties and functions are differentiated in KNX using the so-called mask version, which means that consequently, every KNX device has a defined identifier. Unknown mask versions (e.g. those of new devices in development) are not shown when the Device Info function is used in ETS.