Skip to main content
Skip table of contents

Data point types in the LOGIK EDITOR

Contents

KNX - Data Point Types

Note: The list shown here is a selection of supported data point types and is not complete.

DPT

Sub type

EIS

Descriptor

Length

Value range

Output / Input

1.*

 

EIS 1

 

1 Bit

1/0 resp. true/false

1/1 - Boolean

1.001 - 1.100

2.*

 

EIS 8

1-bit controlled

2 bit

See below

3/4

2.001

switch control

3.*

 

EIS 2

3-bit controlled

4 bit

See below

3/4

3.007

dimming control

3.008

blind control

5.*

 

EIS 14u

8-bit unsigned value

1 Byte

0 - 255

1/1 - Integer

5.001

EIS 6

percentage (0..100%)

0 - 100 %

1/1

5.010

counter pulses (0..255)

0 - 255

1/1

6.*

 

EIS 14s

8-bit signed value

1 Byte

-128 - 127

1/1 - Integer

6.010

counter pulses (-128..127)

7.*

 

EIS 10u

2-byte unsigned value

2 Bytes

0 - 65535

1/1 - Integer

7.001

pulses

8.*

 

EIS 10s

2-byte signed value

2 Bytes

-32768 - 32767

1/1 - Float

8.001

pulses difference

9.*

 

EIS 5

2-byte float value

2 Bytes

-671088.64 - 670760.96

1/1 - Float

9.001

temperature (°C)

10.*

 

EIS 3

time

3 Bytes

See below

4/6 - Integer

10.001

 11.*

 

EIS 4

date

3 Bytes

See below

3/5 - Integer

11.001

12.*

 

EIS 11u

4-byte unsigned value

4 Bytes

0 - 4294967295

1/1 - Integer

12.001

counter pulses (unsigned)

12.600

RGBW value 4x(0..255)DUODMX

4 Bytes

See below

5/6 - Integer

13.*

 

EIS 11s

4-byte signed value

4 Bytes

-2147483648 - 2147483647

1/1 - Integer

13.001

counter pulses (signed)

14.*

 

EIS 9

4-byte float value

4 Bytes

IEEE 754

1/1 - Float

14.000

acceleration (m/s²)

16.*

 

EIS 15

character string

14 Bytes

 

1/1 - String

16.000

character (ASCII)

ASCII character

16.001

character (ISO 8859-1)

ISO 8859-1 / win-1252

17.001

17.001

scene number

1 Byte

1 - 64 (0 - 63 on bus)

1/1 - Integer

18.001

18.001


scene control

1 Byte

See Below

2/3 - Integer / Boolean

232.*

 

 

3-byte colour RGB

3 Bytes

See below

4/5 - Integer

232.600

RGB value 3x(0..255)

242.*

xyY colour

6 Bytes

See below

4/5 - Integer

242.600

xyY colour

243.*

xyY colour fade

8 Bytes

See below

5/6 - Integer

243.600

xyY colour fade

249.*

colour temperature fade

6 Bytes

See below

4/4 - Integer

249.600

colour temperature fade

251.*

RGBW colour

6 Bytes

See below

5/6 - Integer

251.600

RGBW colour


DPT 2 - Priority Switch

DPT 2 has three outputs in Value Inputs and four inputs in Value Outputs. To set a value on a Value Output, you can either send one integer on IN (recommended), or two booleans to SWITCH and PRIORITY (in this case, additionally using the TRIGGER input is recommended).

Name

Output / Input 

Description 

TRIGGER

No / Yes

See /wiki/spaces/LEHC/pages/28050156

IN

Yes / Yes

Combined value 0-3 Integer 

S 

P 

  

0

0

0 

0

1

1 

1

0

2 

1

1

3 

SWITCH

Yes / Yes

Switch command -  boolean 

PRIORITY

Yes / Yes

Priority data -  boolean 

DPT 3 - Dimming  

DPT 3 has three outputs in Value Inputs and four inputs in Value Outputs.

  • Direction as boolean. True for upwards and false for downwards.  

  • Step width as Integer. For the sending, the exact values for the step width are expected.

    • Possible values: 1 

    • 16 

    • 32 

    • 64

  • Stop as boolean. A true is sent / received for stop. For the start, a false is also issued.

DPT 10 - time

DPT 10 has four outputs in Value Inputs but six input values in Value Outputs. For the conversion into a KNX telegram, the transfer of a timestamp is possible.

Name

Output / Input

Description

TRIGGER

No / Yes

See Value in-/output

TS

No / Yes

Timestamp - the timestamp is used in order to send the timestamp in compressed form in one go. The timestamp can be taken from the Clock, for example. This is a so-called UNIX timestamp which corresponds to the seconds since 01.01.1970.

DOW

Yes / Yes

Day of week. 1 for Monday to 7 for Sunday

HOUR

Yes / Yes

Hour 0 - 23

MINUTE

Yes / Yes

Minute 0 - 60

SECOND

Yes / Yes

Second 0 - 60

DPT 11 - date

DPT 11 has three outputs in Value Inputs but five input values in Value Outputs. For the conversion into a KNX telegram, the transfer of a timestamp is possible.

 Name

Output / Input

Description

TRIGGER

No / Yes

See Value in-/output

TS

No / Yes

Timestamp - the timestamp is used in order to send the timestamp in compressed form in one go. The timestamp can be taken from the Clock, for example. This is a so-called UNIX timestamp which corresponds to the seconds since 01.01.1970.

YEAR

Yes / Yes

The period between 1990 and 2089 can be processed via KNX

MONTH

Yes / Yes

Month of the year 1 for January until 12 for December

DAY

Yes / Yes

Day of the month 1 - 31

DPT 18.001 - scene control

DPT 18.001 has two outputs in Value Inputs but three input values in Value Outputs.

 Name

Output / Input

Description

TRIGGER

No / Yes

See Value in-/output

SAVE

Yes / Yes

Indicated whether this is an Activate or Save command as boolean (false: activate, true: save)

SCENE

Yes / Yes

The number of the scene. Note: in accordance with the recommendation from the KNX specifications, LOGIKEDITOR uses the 1..64 range, while supporting 0..63 on the KNX side. Thus, if you send or receive value 1, the actual telegram will contain value 0.

To send a scene control command, the use of the TRIGGER input is recommended. Otherwise a telegram is issued with every incoming value, which can lead to the activation or saving of the wrong scene number.

DPT 232 and DPT 12.600 - Colour

Three and four byte colour.

The 12.600 type is not part of the KNX specification. It is required for the DUODMX GATEWAY in order to be able to control the corresponding RGBW light there.

Name

Output / Input

Description

TRIGGER

No / Yes

See Value Input / Value Output

COLOUR

Yes / Yes

Coded RGB(W) colour value

RED

Yes / Yes

Red channel (0 - 255)

GREEN

Yes / Yes

Green channel (0 - 255)

BLUE

Yes / Yes

Blue channel (0 - 255)

WHITE

Yes / Yes

White channel (0 - 255) - only with 12.600

To send a colour value, the use of either the COLOUR input or the TRIGGER input is recommended. Otherwise a telegram is issued with every incoming value.

DPT 242 - xyY Colour

Name

Output / Input

Description

TRIGGER

No / Yes

See Value Input / Value Output

COLOUR

Yes / Yes

Coded colour value

X

Yes / Yes

x value of the xyY color spectrum (0 - 65535)

Y

Yes / Yes

y value of the xyY color spectrum (0 - 65535)

BRIGHTNESS

Yes / Yes

Percentage (0 - 100)

To send a xyY colour value, the use of the TRIGGER input is recommended. Otherwise a telegram is issued with every incoming value.

DPT 243 - xyY Colour Fade

Name

Output / Input

Description

TRIGGER

No / Yes

See Value Input / Value Output

COLOUR

Yes / Yes

Coded colour value

X

Yes / Yes

x value of the xyY color spectrum (0 - 65535)

Y

Yes / Yes

y value of the xyY color spectrum (0 - 65535)

BRIGHTNESS

Yes / Yes

Percentage (0 - 100)

DURATION

Yes / Yes

Fade Duration in seconds (0 - 6553.5)

To send a xyY colour fade value, the use of the TRIGGER input is recommended. Otherwise a telegram is issued with every incoming value.

DPT 249 - Colour Temperature Fade

Name

Output / Input

Description

TRIGGER

No / Yes

See Value Input / Value Output

COLOUR TEMP.

Yes / Yes

Kelvin (0 - 65535)

BRIGHTNESS

Yes / Yes

Percentage (0 - 100)

DURATION

Yes / Yes

Fade Duration in seconds (0 - 6553.5)

COLOUR

Yes / No

Coded RGB colour value

To send a colour temperature fade value, the use of the TRIGGER input is recommended. Otherwise a telegram is issued with every incoming value.

DPT 251 - RGBW Colour

Name

Output / Input

Description

TRIGGER

No / Yes

See Value Input / Value Output

COLOUR

Yes / Yes

Coded RGBW colour value

RED

Yes / Yes

Red channel (0 - 255)

GREEN

Yes / Yes

Green channel (0 - 255)

BLUE

Yes / Yes

Blue channel (0 - 255)

WHITE

Yes / Yes

White channel (0 - 255)

To send a colour value, the use of either the COLOUR input or the TRIGGER input is recommended. Otherwise a telegram is issued with every incoming value.

///

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.