...
| 4 | Data Size | It defines the size of the datapoint. Possible values are: 1BIT, 2BIT, 4BIT, 1BYTE, 2BYTE, 3BYTE, 4BYTE, 10BYTE, 14BYTE. | |
| 5 | EIS Type | Using this column, the data types is specify by defining the EIB Interworking Standard (EIS) type. | |
| 6 | Signed/Unsigned | This attribute specifies whether the data type is a signed or unsigned one. | |
| 7 | Unit | It defines engineering units of the KNX datapoint. It has to be selected from the list. | |
| 8 | Description | This attribute can be used to specify a human-readable text that further describes the datapoint. | |
| 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" (cf. Section 1.3.2). | |
| 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. | |
| 13 | Read Cyclically Interval | This attributed is used to define whether cyclic KNX Read telegrams be sent to retrieve the current value of the datapoint. 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 consumes bandwidth within the KNX lines. The allowed maximum Value is 65535 s with is identical to 18,20 h. | |
| 14 | Persistent | This parameter specifies whether the value of the datapoint 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 | 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 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() |
...