Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If you want to send a KNX telegram, you can also use the sub fields. For example of DPT 238.600, if you want to request the status of a DALI ballast, you have to set the sub field . Address address to the corresponding address, and .LF and .BF to False. Afterwards, when you set the SEND item to True, the BMS Server combines the values of all sub fields and sends the calculated value to the KNX bus.

...

Now that the custom DPT is defined it has to be announced in the BMS Studio's configuration file for telegram definitions, which can be found in <install-dir>\System\Definitions\nxaTelegramDefinitions.35.tvd.

...

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. (warning) The most right bit's position is 0.

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

Offset to be added before scaling.

post_offset

offset

Offset to be added after scaling.

scale

The Sub_Type scaling factor.

min_max

define

Define the min and max value e.g. "0:10" min is 0 and max is 10.

Article applies to the following products:

...