This article covers the following topics:
This app allows more in-depth diagnostics at the device level. The read out data can be also be saved, however to be able to interpret this data, one shall have deep KNX system knowledge.
The following, basic functions are offered in this ETS App:
- Open device data (from a file or the device).
- Save device data to a file.
Follow these instructions in order to activate the app:
Use of the Device Reader app in ETS
- Invoke the App within a project (How to start an ETS App)
- In the ETS App window, it is possible to toggle between the 'Properties' and 'Memory' view on a tab.
The 'Properties' tab deals with device properties and allows to read device properties.
The App panel is divided into two parts. The objects (including the object number) are displayed in the left-hand part (1) and the associated properties are displayed in the right-hand part (2).
|Description||Contains the plain text name of the property.||Contains the numerical property ID.||Indicates the property type.||Property Value|
Additional properties are also stored in the Properties container.
|Index||The consecutive index of the properties relative to the selected object (0...n).|
|Type ID||The ID of the property type according to KNX specifications or a custom definition using a type file (see below) for the Device Editor|
|Name...||The actual (more intelligible) name of the Type ID (in the Sidebar) or Type (in the Panel)|
|Type Text||The name in text form (default PID--xyz/xyz). A custom name can be assigned in the Device Editor using Definition and a type file (see below)|
|Identifier||Name; identical to Property in the Panel|
|Access||Defines the minimum read and write access rights ("access level") required for a property. Depending on the device type (mask version), there can be up to 16 (0 = highest ...15 = lowest) different levels which can be enabled using an Access Key. The precondition for this is that the manufacturer has even defined levels in this manner for the device using a key for a corresponding level. This means that a display of 3/2 requires Level 3 for reading and Level 2 for writing. In other words, to write data, at least Level 2 must be established either by the default key or with a manufacturer-specific key. The Read/Write function can be used to input a key.|
- Properties can be edited directly in the associated field (in-place editing), either by double clicking on the respective cell (or using F2) or in the Sidebar (Properties Container).
- If the properties are not writable, editing is not possible and a double-click on the cell will have no effect.
- Entire arrays can be edited in a separate dialog, which can be opened by double clicking on the property.
- If an invalid value is entered, the entry is ignored and the original value is again displayed.
Open from a device
Open from file
Write to a file
This view allows the editing of a memory area of a device; the structure is similar to that of common hex editors.
The width of the display is fixed at 16 bytes and is not variable. The base addresses (hexadecimal form) are listed in the left column; to the right in the header are the 16 different memory locations (hexadecimal form).
Modified bytes are displayed in red while read-only bytes are grayed out. Input is made in hexadecimal form.
In addition to the Device Reader, there is also the Device Editor which, in addition to offering further functions, provides write access/data transfer to devices. The following table lists the differences (R = read access, W = write access).
Which memory areas even allow read/write access depends on the respective device model (mask version). Writing rights (W) are subject to an access encoding; a (memory) resource cannot be written to if the (Write) access rights contain the following:
•<AccessRights Read="xyz" Write="None"/>
•<AccessRights Read="xyz" Write="Manufacturer"/>
The data is all stored in the ETS administrative data (master data).
There are three (3) file formats which KNX ETS Apps can work with and store. These are described in the following:
•Property Files (*.knxprop); Saves (read) data in files
•Save Files (*.sxx); Saves (read) memory contents in files
•Type Files (*.xml); Defines the interpretation of (possibly unknown) property types
•The Access Key is predefined using a key of the ETS project that may already exist; otherwise, the default key (0xFFFFFFFF) is used. ETS attempts to use the "higher value" level on the basis of these two keys.
▪Project key exists; Level from the winner project key <> default key; If the first query with the default key immediately achieves the maximum level (= 0), the second query can be omitted.
▪There is no project key; The level from the default key is used.
•This KNX ETS App can be called more than once in ETS (see Call Types for ETS Apps).