File location
<WorkspaceDirectory>\DataFiles\nxaTelegramDefinitions.40.dat
Within this configuration files, the KNX data points, i.e. the KNX group addresses, are specified.
This definition file can also be generated using the ETS app import wizard (Studio > KNX > Import NETx ETS App file...) which generates the KNX group address definitions from an exported ETS project.
The structure of the definition file is as follows:
| Col# | Parameter | Description |
|---|---|---|
| 1 | KNX grp. adr. | It defines the KNX group address of the data point. The KNX group address can be specified either in three level form (e.g. 0/2/1) or in tow level form (e.g. 0/513). |
| 2 | KNX gateway name | It specifies the name of the KNXnet/IP device to which the specified KNX group address is assigned. Thus, it defines KNXnet/IP device that is used to send and receive KNX telegrams that are originated to this group address. The name "BROADCAST" defines a KNX data point which is sent to all defined gateways. ! The KNX group address together with the name of the KNXnet/IP device define the effective address of the KNX data point. This effective address is internally used by the server. Using this addressing scheme, it is possible to use the same KNX group address for multiple KNX data points as long as they are assigned to different KNXnet/IP devices. This means that behind each gateway an independent ETS address space can exist. |
| 3 | Priority | It defines the KNX priority that is used to send KNX group telegrams. Possible values are SYSTEM, HIGH, ALARM and LOW. The standard value "LOW" should be used in general. |
Columns 4 to 7 define how to interpret the received data of a KNX data point. At least two of these attributes has to defined to specify the semantic of a data point. All possible combinations are listed in the data type table. | ||
| 4 | Data Size | It defines the size of the data point. Possible values are: 1BIT, 2BIT, 4BIT, 1BYTE, 2BYTE, 3BYTE, 4BYTE, 5BYTE, 6BYTE, 7BYTE, 8BYTE, 10BYTE, 14BYTE. |
| 5 | Data Type | Using this column, the data types is specify by defining the standardized KNX data point type (KNX DPT). As an alternative, the old EIS types can be selected too. |
| 6 | Signing | Only for EIS types: this attribute specifies whether the data type is a signed or unsigned one. |
| 7 | Unit | Only for EIS types: it defines engineering units of the KNX data point. |
| 8 | Description | This attribute can be used to specify a human-readable text that further describes the data point. |
| 9 | Read on Reconnect | This attribute is used to define whether a KNX Read telegram shall be sent when the corresponding KNXnet/IP gateway reconnects or when the server is started. If this functionality is activated, the read flag has to be set within the corresponding KNX device using ETS. |
| 10 | Read Cyclically Interval | This attributed is used to define whether cyclic KNX Read telegrams be sent to retrieve the current value of the data point. If this functionality is activated, the read flag has to be set within the corresponding KNX device using ETS. Note that cyclically reading KNX data points consumes bandwidth within the KNX lines. The allowed maximum Value is 65535 s with is identical to 18,20 h. |
| 11 | Persistent | This parameter specifies whether the value of the data point is persistent (restored from the database after server start up ) or not. |
| 12 | Synchronize | If this parameter is set to "True (T)", the value is synchronized between the main and backup server (if present). This will work only if main/backup configuration is activated for the NETx BMS Core Server. |