Settings
Field name | Description | Applies for | Applies for 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 following:
|
|
|
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 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 here. |
|
|
Bus connection |
An explicit connection (interface) per line can be specified here. If set, then it will then be used for access during bus operations. Background information: In addition to the explicit use of a connection for this line/area (e.g. diagnostics/download only in this line/area), this also allows simultaneous parallel download to different lines. For details on the use/priority of possible connections, see Connection options. |
|
|
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 for |
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 |
|