...
After saving the custom DPT in nxaKNXDataTypeDefinitions.xml and the modified nxaTelegramDefinitions.35.tvd the BMS Studio needs to be restarted to be aware of the new DPT. After that the new DPT is ready to use in the telegram definition table:
XML format description
| data_type attributes | Description |
|---|---|
name | The name of the custom DPT which will be used later. |
descr | Data type description. |
length_type | Type length of DPT, 1BIT, 2BIT, 4BIT, 1BYTE, 2BYTE, etc. |
set_flag | Set the DPT flag. |
sub_type attributes | Description |
|---|---|
id | The ID of the Sub_Type. |
desc | Sub_Type description. |
start_index | The start index of the Sub_Type. |
length | The length of the Sub_Type in bits. |
length_type | The length type of the Sub_Type. |
input_type | The input type EIS1, EIS2, EIS5, etc.... |
su | S (signed) or U (unsigned); default is signed |
output_type | The Sub_Type output type. |
unit | The Sub_Type unit type °C, K/h, m/s, %, etc... |
pre_offset | offset to be added before scaling |
post_offset | offset to be added after scaling |
scale | Sub_Type scaling factor |
min_max | define the min and max value e.g. "0:10" min is 0 and max is 10. |
Article applies to the following products:
- NETx BMS Platform
- NETx Multi Protocol Server
- NETx BMS Server 2.0