When Device Info is selected, 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.
How to invoke it?
The Device info operation can be invoked via...
- ... Bus tab > 'Diagnostics > Device Info'
- ... right mouse click on a device 'Info > Device Info' or 'Info > Device Info with Group Communication'
- ... context toolbar 'Info > 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.
1. Device Info
- General
- Application Program
2. Device Info (with Group Communication)
- General
- Application Program
- Group Communication
Result display
Within a project
Once the Device Info is triggered, the 'Pending Operations' in the sidebar is opened and the action (i.e. Device Information read) is shown. Click the 'History' tab and then the icon .
to display the Device Info results. This opens a new modal window.
Without a project
An Individual Address shall be first entered manually and then click the 'Read' button. The results are displayed on the same place.
Menu bar
| Menu item | Description |
| Save | Allows to save the results in either HTML or txt format. |
| Copy to clipboard | Copies the results to the clipboard so that it can be pasted elsewhere. |
| Allows to print the results. | |
| Close | Closes the result window. |
Content
Details on how to interpret the results are included in the KNX Specifications; Here, only the general meanings are listed:
General
| Element | Description |
| Mask version | Current mask version of the device |
| Individual Address | Individual Address of the device |
| Device manufacturer | Name of the manufacturer of the device |
| Order number | Order number, if provided by the manufacturer in readable/decodable form (otherwise hexadecimal) |
| Serial number | Unique device hardware ID |
| Bus voltage | Bus voltage measured by the device |
| Download mode | Status of the download LED |
| Run error | Error in the device while executing the program (if no error ->OK) |
| Hardware PEI type | Adapter type of the hardware |
| MAC Address | MAC address for IP devices/couplers |
Application Program
| Element | Description |
| Application | Application ID, consisting of "Manufacturer ID" of the device manufacturer, "Device Type" and "Version" |
| Device type | Manufacturer-specific Application number typically stored in the device memory |
| 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) |
Group Communication
| Element | 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) All the Group Addresses assigned to the Group Object The Group Address display style is based on the defined project's style. In case of a Device Info without a project, the 3-level Group Address style is used by default. |
For couplers, the information shown is about the Coupler Type and their capabilities, as well as the current 'routing' configuration (main line > subline), security settings (if applicable), etc.
For some devices 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.