- Properties
- Topology & KNX Secure
- Add/Edit elements
- List view- Topology elements
- List View - Device elements
Properties
The properties of each element can be found below.
Settings
| Field name | Description | Applies for | Applies to medium type |
| Name |
|
|
|
| Address |
|
|
|
| Description |
User-friendly, longer description (max. 64k characters). The content is included in exports and imports. |
|
|
| Status |
Optional status of the currently selected item (for the purpose of sorting information in multi-user applications).
|
|
|
| Medium |
Media type of the element; when an element is created, it first inherits the element type from the higher-level main line provided that it does not cause a conflict. The following media are available:
Depending on the element selected, the 'Medium' field is renamed as follows:
|
|
|
| Main Line Name | Name of the Main Line (the properties are analogous to Area, if present) |
|
|
| Domain Address | Precise ID of open media for distinction. Clicking the 'Generate new' button generates a new Domain Address. |
|
|
| Network Latency |
This is used to define the maximum latency (in connection with an additional % parameter), with which old telegrams can still be accepted so that they are not considered as 'Replay Attack'. The following options are available:
Why is this setting needed? The delay times that normally occur in networks because of their topology. In mobile radio networks, correct or valid query (client) > response (server) scenarios take longer than in local networks (LAN). For example, if the client and the server operate with the exact same time, which is sent along in the telegrams, the server’s response at the client lags about 2 seconds behind the real time in the mobile radio network (telegram run time in the network), but in the LAN, this is only 100 ms. |
|
|
| Multicast Address |
The multicast address of a KNX backbone line can be set here. Background information If Security is activated on the Backbone Line and the Multicast Address is (coincidentally) changed, but the change is undone afterwards, then the old security key of the ETS project is taken again. Therefore, it is not necessary to load again any (already loaded) KNX IP Secure Coupler. |
|
|
| Security |
The desired KNX IP Security mode can be defined with this setting. The following options are available:
For information about those options, see Topology & KNX Secure. |
|
|
| Bus connection |
An explicit connection (interface) per Backbone line can be specified here. If set, then it will then be used for access during bus operations. |
|
|
Comment
Here you can add a comment with the formatting options BOLD; ITALIC; UNDERLINED (max. 64k characters). The content is included in project exports and imports.
Information
| Field name | Description | Applies to |
| Number of devices |
Number of devices on this line segment (and only on this line segment, i.e. Area Main Line, or Line). There is no summary of devices from any subordinate lines/areas. |
|
| Bus current |
This indicates the total sum of bus current (mA) of all devices in this line. The indicated value is the total of all individual values of every device in the selected element (Backbone Line/Main Line/Line) excluding any power supplies and parked devices. If the current value of a device is not available (because it has not been defined in the KNX product entries by the manufacturer), then the value of 10 mA is assumed for the calculation. Subsequently, the additional message (estimated) will be displayed, even if only one value is unknown. If there is no indication of the maximum current for the power supply in the product entry (or it is 0), the value of 320 mA is used as a preset for the supply/availability. Subsequently, the additional note (estimated) is shown in the display. |
|
|
Manual filter table entries |
Manage manual filter entries. Possible entries in the area line are oriented towards the IP world |
|
Add/Edit elements
When clicking on an 'Add' button, a modal dialog is shown, in which the number and the names of the elements to be added can be defined.
Use the + button in the input window to add several elements at once but give them different names.
Areas
In the Tree View, select the top line (Topology backbone) in order to add areas by...
- ...clicking the 'Add Areas' button in the Context Tool Bar
- ...using the menu Edit>Add Areas
- ...right-clicking on the 'Topology backbone'>Add Areas
In the List View, when the top line (Topology backbone) from the Tree View is selected, by...
- ...right-clicking on any white space and then > Add Areas
Lines
In the Tree View, select the area to which an additional line shall be added by...
- ...clicking the 'Add Lines' button in the Context Tool Bar
- ...using the menu Edit>Add Lines
- ...right-clicking on an Area to which the Line shall be added>Add Lines
In the List View, when an area from the Tree View is selected, by...
- ...right-clicking on any white space and then > Add Line
Segments
In the Tree View, select the line to which a segment shall be added by...
- ...clicking the 'Add Segments' button in the Context Tool Bar
- ...using the menu Edit>Add Segments
- ...right-clicking on a Line to which the Segment shall be added>Add Segment
In the List View, when an area from the Tree View is selected, by...
- ...right-clicking on any white space and then > Add Segments
Devices
In the Tree View, select the area or the line to which a device shall be added by...
- ...clicking the 'Add Devices' button in the Context Tool Bar
- ...using the menu Edit>Add Devices
- ...right-clicking on an Area or Line to which the device shall be added>Add Devices
In the List View, when an area or a line from the Tree View is selected, by...
- ...right-clicking on any white space and then > Add Devices
Areas, lines and devices can also be inserted outside of the topology panel. If you set or edit the Individual Address of a device in any of the other ETS panels, ETS will automatically create the corresponding Area/Line combination (unless it already exists). The default names are 'New area' and 'New line'.
All the elements regardless of their availability can be edited by...
- ...pressing the ALT + ENTER keys; the Sidebar Settings dialog will open.
- ...slow double-clicking on the element, which allows a direct modification in the List View.
List view- Topology elements
| Name | Description |
| Security | Device supports KNX Secure if security shield/icon ( |
| Address |
Refers to the Individual Address of a device, which defines the location of the device within the topology. |
| Room | Refers to the building location. |
| Description | The Description column is empty. Users can provide description details if required, according to their needs. |
| Application Program | Description of application program function. |
| Manufacturer | Name of the manufacturer. |
| Serial Number |
Refers to device serial number which we will help to commission the device. You can Add, edit or delete serial number using in place editor option (List view (Detailed)). For more details, see here. |
|
Order Number |
Is a unique identifier assigned by manufacturer to a purchase product when an order is placed. |
|
Adr Prg Par Grp Cfg |
These are the download status flags. For more details, see here. |
|
Product |
Product/Device name |
|
Trade |
Refers to the trade location |
|
Name |
Product/Device name |
|
Adr |
Status of Individual address loaded. For more details, see here. |
|
Prg |
Status of Application Program(s) loaded. For more details, see here. |
|
Par |
Status of Parameters loaded. For more details, see here. |
|
Grp |
Status of Group addresses + links between the group objects (called 'associations') loaded. For more details, see here. |
|
Cfg |
Status of Medium type specific settings loaded. For more details, see here. |
|
Last Modified |
The date on which the project was last edited in ETS. |
|
Last Downloaded |
The date on which the project was downloaded/commissioned in ETS. |
|
Re-Import Required |
For more details, see here. |
|
Bus Current |
Indication (if provided by the manufacturer) about the bus current that the device draws from the bus line. |
List view- Device elements
| Name | Description |
| Number | Group object number defined by manufacturer. |
| Name | Group object name defined by manufacturer. |
| Description | User-friendly, longer description (max. 64k characters). You can enter a description manually as per your requirement. The content is included in exports and imports. |
| Object Function | Group object function defined by manufacturer. |
| Linked With |
The 'Linked With' column displays the group address name by default after an object is linked to a group address. To view the main and middle group addresses as well, enable the option under Settings → Presentation → Show main and middle groups in the 'Linked With' column. For more information, you can click here: Presentation |
| Group Address |
Shows all the Group Addresses linked to this Group Object. |
| Length | Length of the Group Object |
| C |
The Communication flag If C-flag set: All other flags are enabled for this object. |
| R |
The Read flag If R-flag set: The device will for this object react to a GroupValueRead telegram coming from the bus, i.e. it will send a GroupValueResponse telegram to the bus. |
| W |
The Write flag If W-flag set:The device will for this object react to a GroupValueWrite telegram coming from the bus, i.e. it will overwrite the object value. For a switch actuator this e.g. means that a relay representing this object will be opened or closed. |
| T |
The Transmit flag If T-flag set: The device will for this object transmit any updated object value, i.e. it will send a GroupValueWrite telegram to the bus. For a push button object this e.g. means that a rocker representing this object was manipulated. |
| U |
The Update flag If U-flag set: The device will for this object react to a GroupValueResponse telegram coming from the bus, i.e. it will overwrite the object value. For a switch actuator this e.g. means that a relay representing this object will be opened or closed. |
| I |
The Initialization flag If I-flag set: The device will for this object after device reset send a GroupValueRead telegram. The purpose is to get the object value via a GroupValueResponse. The reason for the device reset could be a power failure, an explicit bus reset or an explicit device reset request via a telegram |
| Data Type |
The Datapoint Type lets you choose a special format for the Group Object.
|
| Priority | Priority of telegrams when sending via this Group Object
|
| No.of Associations | Total number of number of linked group address. |