...
<WorkspaceDirectory>\DataFiles\nxaTelegramDefinitions.3540.dat
TODO: Recheck Names and Fields
Within this configuration files, the KNX datapoints i.e. the KNX group addresses are specified. The structure of the definition file is as follows:
'Syntax of the Telegram Definition Table:'log.KNX Address; IP Address; Priority; Data Size; EIS Type; Signed/Unsigned; Unit; Description; Path; Control Data; Alias; Read on Reconnect; Read Cyclically Interval;
' Persistent;Historical;Synchronize;IN Converter;OUT Converter
1/0;BROADCAST;LOW;1BIT;EIS1;;;Telegram Demo EIS1;;;;F;0;F;F;F;;
2/0;BROADCAST;LOW;4BIT;EIS2;;;Telegram Demo EIS2;;;;F;0;F;F;F;;
3/0;BROADCAST;LOW;3BYTE;EIS3;;;Telegram Demo EIS4;;;;F;0;F;F;F;;
4/0;BROADCAST;LOW;3BYTE;EIS4;;;Telegram Demo EIS4;;;;F;0;F;F;F;;
5/1;BROADCAST;LOW;2BYTE;EIS5;;°C;Telegram Demo EIS5 1;;;;F;0;F;F;F;;
5/21;BROADCAST;LOW;2BYTE;EIS5;;mA;Telegram Demo EIS5 2;;;;F;0;F;F;F;;
Each line – except comment lines that start with ' – defines a single KNX group address.
...
| Info |
|---|
! This definition file can also be generated using the ETS app import wizard (Studio → KNX → Inport 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:
| 1log | .KNX AddressKNX grp. adr. | It defines the logical KNX group address of the datapointdata 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). | |
| 2IP Address | KNX gateway name | It specifies the IP address 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 datapoint data point which is sent to all defined gateways. |
| Info |
|---|
| ! The logical KNX group address together with the IP address name of the KNXnet/IP device define the effective address of the KNX datapointdata 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 datapoints 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. Theoretically up to 1000 ETS projects with the same address space are possible within the system. |
| 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 datapointdata point. At least two of these attributes has to defined to specify the semantic of a datapointdata point. All possible combinations are listed in the data type table.
...
| 4 | Data Size | It defines the size of the datapointdata point. Possible values are: 1BIT, 2BIT, 4BIT, 1BYTE, 2BYTE, 3BYTE, 4BYTE, 5BYTE, 6BYTE, 7BYTE, 8BYTE, 10BYTE, 14BYTE. | ||||||||||
| 5 | EIS Data Type | Using this column, the data types is specify by defining the EIB Interworking Standard (EIS) typestandardized KNX data point type (KNX DPT). As an alternative, the old EIS types can be selected too. | ||||||||||
| 6 | Signed/Unsigned | This Signing | Only for EIS types: this attribute specifies whether the data type is a signed or unsigned one. | |||||||||
| 7 | Unit | It Only for EIS types: it defines engineering units of the KNX datapoint. It has to be selected from the list.data point. | ||||||||||
| 8 | Description | This attribute can be used to specify a human-readable text that further describes the datapointdata point. | ||||||||||
| 9 | (deprecated) Path | This attribute is used for the automatic PDA visualization to create a tree structure like "Home/Level1/living room". | 10 | (deprecated) Control Data | This attribute is used for additional input data for the automatic PDA visualization. | 11 | (deprecated) Alias | This attribute can be used to define an alias name for this KNX datapoint. This alias is shown within the server item tree under the sub tree "Alias". | 12 | 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. | |
| 1310 | Read Cyclically Interval | This attributed is used to define whether cyclic KNX Read telegrams be sent to retrieve the current value of the datapointdata 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 datapoints data points consumes bandwidth within the KNX lines. The allowed maximum Value is 65535 s with is identical to 18,20 h. | ||||||||||
| 1411 | Persistent | This parameter specifies whether the value of the datapoint data point is persistent (restored from the database after server start up ) or not. | 15 | Historical | This parameter specifies whether historical values of the datapoint are stored within the database or not. | |||||||
| 16 | 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 synchronize is enabled in the NMESH configuration of main/backup configuration is activated for the NETx BMS Core Server. | 17 | IN Converter | At this parameter you are able to define a LUA function, which can be used for INcoming conversion. E.g. InConv() | 18 | OUT Converter | At this parameter you are able to define a LUA function, which can be used for OUTgoing conversion. E.g. OutConv() |