03 - 07 - 02 Datapoint Types v1.5.00 As

KNX Standard
Interworking
Datapoint Types
System Specifications
Interworking
3 7 2
Datapoint Types
Summary: This Chapter specifies the KNX Datapoint Types for Interworking This Chapter describes the general usable and Functional Block specific, standard Datapoint Types that are to be used for transmission of data on the bus. Version 1.5.00 is a KNX Approved Standard.
Copyright 1998 - 2010, KNX Association
AS v1.5.00 - page 1 of 161
KNX Standard
Interworking
Datapoint Types
Document updates
Version v1.0 AS Date 2002.01.03 Description Preparation of the approved standard. The DPTs of the following documents are integrated. Chapter 7/1/3 (S12) Logical Functional Blocks Chapter 7/20 (S12) Lighting Chapter 7/50 (S12) Shutters and Blinds Supplement 11 HVAC Datapoint Types Supplement 12 Channel Codes Supplement 14 DPT_DateTime AN004 Additional HVAC data types AN006 Update of Supplement 14 DPT_DateTime AN027 TFI approved Datapoint Types for general usage AN035 DPT_Version AN079 TFI Accepted DPTs 05.03 Preparation of the Draft Proposal. Editorial correction of DPT_TempFlowWaterDemAbs (DPT_ID = 210.100): V16 and B8 B16 in detailed specification, acc. resolution of comments V15 to AN096 v01. Inclusion of resolution of comments from Final Voting. Preparation of the Approved Standard. DPT_Length_mm (7.011) added. DPT_Rotation_Angle (8.011) added. DPT_MBus_Address (230.1000) PDT corrected from PDT_GENERIC_09 to PDT_GENERIC_08. AN050 AN to Supplement 12 integrated. AN051 New channels integrated. AN087 New channels 2005.02 integrated. Integrated conclusion of WGI meeting of 2007.09.26 about use of DPT_Power and DPT_Value_Power. AN057 System B integrated (DPT_ErrorClass_System extension) AN096 WGI accepted DPTs 06.01 started and completed integration. AN098 Unicode started and completed integration. AN066 cEMI adaptations: extension of DPT_CommMode. PART_Logical, PART_Invert and PART_Input_Connected added (AN050) AN097 Eberle Status Byte: integration started and completed. Coding of DPT_CommMode replaced by reference to PID_COMM_MODE in 3/6/3. AN105 to AN110: removed TP0 and PL132 from possible values of DPT_Media Editorial update for inclusion in the KNX Specifications v2.0. 7/1/5 General Purpose I/O: added DPTs used in that specification. Editorial update in view of inclusion in the KNX Specifications v2.0. Correction of range of DPT_ErrorClass_System. AN120 WGI approved DPTs 07.01 integrated. AN128 WGI approved DPTs 09.01 integrated.
v1.3 AS
2007.03.14
v1.4 AS
2007.03.20 2007.10.03 2007.10.05 2007.10.19 2007.12.14 2008.03.13 2008.03.14 2008.04.28 2008.05.19 2008.06.04 2008.11.05 2009.02.03 2009.04.10 2009.06.25 2009.11.10 2009.11.18 2010.04.14
v1.4 AS v1.4.01 AS v1.5.00 AS
References
[01] [02] Chapter 3/6/3 Chapter 3/7/3 External Message Interface Standard Identifier Tables
AS v1.5.00 - page 2 of 161
KNX Standard
Interworking
Datapoint Types
Filename: Version: Status: Savedate: Number of pages:
03_07_02 Datapoint Types v1.5.00 AS.docx 1.5.00 Approved Standard 2010.04.14 161
AS v1.5.00 - page 3 of 161
KNX Standard
Interworking
Datapoint Types
Contents
1 Introduction ............................................................................................................................ 8 1.1 Classification and identification of Datapoint Types ..................................................... 8 1.2 Subtype ranges for Datapoint Type Identifiers ............................................................... 9 1.3 Datapoint Type specification style ............................................................................... 10 1.3.1 Notations and format......................................................................................... 10 1.3.2 Property Datatype ............................................................................................. 10 1.3.3 Use .................................................................................................................... 11 1.4 The transmission of DPT encoded data on the bus....................................................... 11 Overview ............................................................................................................................... 12 Datapoint Types for common use ....................................................................................... 19 3.1 Datapoint Types B1 ....................................................................................................... 19 3.2 Datapoint Types B2 ....................................................................................................... 21 3.3 Datapoint Types B1U3................................................................................................... 22 3.3.1 DPT_Control_Dimming ................................................................................... 22 3.3.2 DPT_Control_Blinds ........................................................................................ 23 3.4 Datapoint Types Character Set ................................................................................... 24 3.5 Datapoint Types 8-Bit Unsigned Value .................................................................... 25 3.5.1 Scaled values ..................................................................................................... 25 3.5.2 Non-scaled values ............................................................................................. 26 3.6 Datapoint Types V8....................................................................................................... 27 3.6.1 Signed Relative Value....................................................................................... 27 3.7 Datapoint Type Status with Mode............................................................................. 27 3.8 Datapoint Types 2-Octet Unsigned Value ................................................................ 28 3.8.1 2-octet unsigned counter value ......................................................................... 28 3.8.2 Time Period ....................................................................................................... 28 3.8.3 Other U16 Datapoint Types ............................................................................... 29 3.9 Datapoint Types 2-Octet Signed Value..................................................................... 30 3.9.1 2-octet signed counter value ............................................................................. 30 3.9.2 Delta Time ........................................................................................................ 30 3.9.3 Other V16 Datapoint Types ............................................................................... 31 3.10 Datapoint Types 2-Octet Float Value ....................................................................... 31 3.11 Datapoint Type Time ................................................................................................ 33 3.12 Datapoint Type Date ................................................................................................. 33 3.13 Datapoint Types 4-Octet Unsigned Value ................................................................ 34 3.14 Datapoint Types 4-Octet Signed Value..................................................................... 34 3.14.1 4 Octet signed counter value ............................................................................. 34 3.14.2 DPTs for electrical energy ................................................................................ 35 3.14.3 4 Octet signed time period ................................................................................ 35 3.15 Datapoint Types 4-Octet Float Value ....................................................................... 36 3.16 Datapoint Type DPT_Access_Data .............................................................................. 38 3.17 Datapoint Types "String" .............................................................................................. 40 3.18 Datapoint Type Scene Number ..................................................................................... 40 3.19 Datapoint Type DPT_SceneControl ............................................................................. 41 3.20 Datapoint Type DPT_DateTime ................................................................................... 41 3.20.1 Notes ................................................................................................................. 42 3.21 Datapoint Types N8....................................................................................................... 44 3.22 Datapoint Type B8 ........................................................................................................ 48 3.22.1 Datapoint Type General Status...................................................................... 48 3.22.2 Datapoint Type Device Control .................................................................... 49
System Specifications AS v1.5.00 - page 4 of 161
2 3
KNX Standard
Interworking
Datapoint Types
3.23 Datapoint Types N2....................................................................................................... 50 3.24 Datapoint Type DPT_VarString_8859_1 ..................................................................... 51 3.25 Datapoint Type DPT_SceneInfo................................................................................... 52 3.26 Datatype B32.................................................................................................................. 53 3.26.1 Datapoint Type Combined Info On Off ........................................................ 53 3.27 Datapoint Type Unicode UTF-8 String A[n]................................................................ 56 3.27.1 DPT_UTF-8 ...................................................................................................... 56 3.28 Datapoint Types V64 ..................................................................................................... 58 3.28.1 DPTs for electrical energy ................................................................................ 58 3.29 Datapoint Type DPT_AlarmInfo .................................................................................. 59 3.30 Datapoint Type DPT_SerNum ..................................................................................... 62 3.31 Datapoint Types Unsigned Relative Value ............................................................... 62 3.32 Datapoint Types Unsigned Counter Value ............................................................... 63 3.33 Datapoint Types Time Period..._Z ............................................................................ 64 3.34 Datapoint Types Unsigned Flow Rate l/h ................................................................. 65 3.35 Datapoint Types Unsigned Counter Value ............................................................... 65 3.36 Datapoint Types Unsigned Electric Current A ....................................................... 66 3.37 Datapoint Types Power in kW .................................................................................. 66 3.38 Datapoint Type Atmospheric Pressure with Status/Command ................................. 67 3.38.1 Datapoint Type DPT_PercentU16_Z ............................................................ 68 3.39 Datapoint Types Signed Relative Value ................................................................... 68 3.40 Datapoint Type DeltaTime...Z .................................................................................. 69 3.41 Datapoint Type DPT_Version ...................................................................................... 70 3.42 Datapoint Type Volume in Liter ............................................................................... 72 3.43 Datatype U16U8 ............................................................................................................. 72 3.43.1 Datapoint Type Scaling speed ....................................................................... 72 3.43.2 Datapoint Type Scaling step time ................................................................. 73 3.44 Datatype V32N8Z8 ......................................................................................................... 75 3.44.1 Datapoint Type MeteringValue ..................................................................... 75 3.45 Datatypes A8A8A8A8 .................................................................................................... 77 3.46 Datapoint Types A8A8 .................................................................................................. 78 3.47 Datapoint Type DPT_RegionCodeAlpha2_ASCII....................................................... 80 4 Datapoint Types for HVAC................................................................................................. 84 4.1 Simple Datapoint Types with STATUS/COMMAND Z8 field.................................... 84 4.1.1 Introduction ....................................................................................................... 84 4.1.2 Datatype format ................................................................................................ 85 4.1.3 OutOfService mechanism for a parameter ........................................................ 89 4.1.4 OutOfService mechanism for a runtime Datapoint (actual value).................... 89 4.1.5 Override mechanism ......................................................................................... 90 4.1.6 Alarming mechanism ........................................................................................ 91 4.2 Datapoint Types B1 ....................................................................................................... 92 4.3 Datapoint Types N8....................................................................................................... 93 4.4 Data Type 8-Bit Set ................................................................................................... 96 4.4.1 Datapoint Type Forcing Signal ..................................................................... 96 4.4.2 Datapoint Type Forcing Signal Cool............................................................. 97 4.4.3 Datapoint Type Room Heating Controller Status ......................................... 98 4.4.4 Datapoint Type Solar DHW Controller Status .............................................. 99 4.4.5 Datapoint Type Fuel Type Set..................................................................... 100 4.4.6 Datapoint Type Room Cooling Controller Status ....................................... 101 4.4.7 Datapoint Type Ventilation Controller Status ............................................. 101 4.5 Data Type 16-Bit Set ............................................................................................... 102
KNX Standard
Interworking
Datapoint Types
4.5.1 Datapoint Type DHW Controller Status ..................................................... 102 4.5.2 Datapoint Type RHCC Status ..................................................................... 103 4.6 Datapoint Types N2..................................................................................................... 106 4.7 Datapoint Types N3..................................................................................................... 107 4.7.1 Datapoint Type DPT_PB_Action_HVAC_Extended ..................................... 107 4.8 Data Type Boolean with Status/Command ............................................................. 108 4.8.1 Datapoint Type Heat/Cool_Z ...................................................................... 108 4.8.2 Datapoint Type DPT_BinaryValue_Z......................................................... 108 4.9 Data Type 8-Bit Enum with Status/Command........................................................ 109 4.9.1 Datapoint Type HVAC Operating Mode .................................................... 109 4.9.2 Datapoint Type DHW Mode ....................................................................... 110 4.9.3 Datapoint Type HVAC Controlling Mode .................................................. 110 4.9.4 Datapoint Type Enable Heat/Cool Stage..................................................... 111 4.9.5 Datapoint Type Building Mode ................................................................... 112 4.9.6 Datapoint Type Occupancy Mode ............................................................... 113 4.9.7 Datapoint Type HVAC Emergency Mode .................................................. 113 4.10 Data Type 16-Bit Unsigned Value with Status/Command ..................................... 114 4.10.1 Datapoint Type HVAC Air Quality ............................................................ 114 4.10.2 Datapoint Type Wind Speed with Status/Command ................................... 115 4.10.3 Datapoint Type Sun Intensity with Status/Command ................................. 115 4.10.4 Datapoint Type HVAC Air Flow Absolute Value ...................................... 116 4.11 Data Type 16-Bit Signed Value with Status/Command ......................................... 117 4.11.1 Datapoint Type HVAC absolute Temperature ............................................ 117 4.11.2 Datapoint Type HVAC relative Temperature ............................................. 118 4.11.3 Datapoint Type HVAC Air Flow Relative Value ....................................... 118 4.12 Data Type 16-Bit Unsigned Value & 8-Bit Enum ................................................. 119 4.12.1 Datapoint Type HVAC Mode & Time delay .............................................. 119 4.12.2 Datapoint Type DHW Mode & Time delay ................................................ 120 4.12.3 Datapoint Type Occupancy Mode & Time delay ....................................... 121 4.12.4 Datapoint Type Building Mode & Time delay ........................................... 122 4.13 Data Type 8-Bit Unsigned Value & 8-Bit Set ........................................................ 123 4.13.1 Datapoint Type Status Burner Controller .................................................... 123 4.13.2 Datapoint Type Locking Signal .................................................................. 124 4.13.3 Datapoint Type Boiler Controller Demand Signal ...................................... 124 4.13.4 Datapoint Type Actuator Position Demand ................................................ 125 4.13.5 Datapoint Type Actuator Position Status .................................................... 126 4.14 Data Type 16-Bit Signed Value & 8-Bit Set ........................................................... 127 4.14.1 Datapoint Type Heat Producer Manager Status .......................................... 127 4.14.2 Datapoint Type Room Temperature Demand ............................................. 128 4.14.3 Datapoint Type Cold Water Producer Manager Status ............................... 129 4.14.4 Datapoint Type Water Temperature Controller Status................................ 130 4.15 Data Type 16-Bit Signed Value & 16-Bit Set ......................................................... 131 4.15.1 Datapoint Type Consumer Flow Temperature Demand ............................. 131 4.16 Data Type 8-Bit Unsigned Value & 8-Bit Enum .................................................... 132 4.16.1 Datapoint Type EnergyDemWater .............................................................. 132 4.17 Data Type 3x 16-Bit Signed Value ........................................................................ 133 4.17.1 Datapoint Type 3x set of RoomTemperature Setpoint Shift values ............ 133 4.17.2 Datapoint Type 3x set of RoomTemperature Absolute Setpoint values ..... 134 4.18 Data Type 4x 16-Bit Signed Value ........................................................................ 135 4.18.1 Datapoint Type 4x set of RoomTemperature setpoints .............................. 135 4.18.2 Datapoint Type 4x set of DHWTemperature setpoints .............................. 136
Copyright 1998 - 2010, KNX Association System Specifications AS v1.5.00 - page 6 of 161
KNX Standard
Interworking
Datapoint Types
4.18.3 Datapoint Type 4x set of RoomTemperature setpoint shift values ............ 137 4.19 Data Type 16-Bit Signed & 8-Bit Unsigned Value & 8-Bit Set ............................. 137 4.19.1 Datapoint Type Heat Prod. Manager Demand Signal ................................. 137 4.19.2 Datapoint Type Cold Water Prod. Manager Demand Signal ...................... 138 4.20 Data Type V16 U8 B16 ............................................................................................ 139 4.20.1 Datapoint Type Status Boiler Controller ..................................................... 139 4.20.2 Datapoint Type Status Chiller Controller .................................................... 141 4.21 Data Type U16U8N8B8 ............................................................................................. 142 4.21.1 Datapoint Type Heat Producer Specification .............................................. 142 4.22 Data Type 16-Bit Unsigned Value & 16-Bit Signed Value ................................... 143 4.22.1 Datapoint Type Next Temperature & Time Delay ...................................... 143 4.23 Data Type 3x 16-Float Value ................................................................................. 144 4.23.1 Datapoint Type 3x set of RoomTemperature Setpoint Values ................... 144 4.23.2 Datapoint Type 3x set of RoomTemperature Setpoint Shift Values .......... 145 4.24 Data Type V8 N8 N8 .............................................................................................. 146 4.24.1 Datapoint Type EnergyDemAir .................................................................. 146 4.25 Data Type V16V16N8N8 ............................................................................................... 147 4.25.1 Datapoint Type TempSupplyAirSetpSet ..................................................... 147 5 6 Datapoint Types for Load Management .......................................................................... 149 Datapoint Types for Lighting ............................................................................................ 150 6.1 Datapoint Types N8..................................................................................................... 150 6.2 Datapoint Types U8U8U8 ............................................................................................ 151 6.2.1 DPT_Colour_RGB.......................................................................................... 151 Datapoint Types for System .............................................................................................. 152 7.1 Datapoint Types N8..................................................................................................... 152 7.2 Datapoint Types B8 ..................................................................................................... 153 7.2.1 Datapoint Type RF Communication Mode Info ......................................... 153 7.2.2 Datapoint Type cEMI Server Supported RF Filtering Modes .................... 154 7.2.3 Datapoint Type Channel Activation for 8 channels .................................... 155 7.3 Datatype B16................................................................................................................ 155 7.3.1 Datapoint Type Media ................................................................................. 155 7.3.2 Datapoint Type Channel Activation for 16 channels .................................. 156 7.4 Datatype U4U4 ............................................................................................................ 157 7.5 Datapoint Types B24 ................................................................................................... 157 7.5.1 Datapoint Type Channel Activation for 24 channels .................................. 157 7.6 Datapoint Type MBus Address ............................................................................... 158 Parameter Types ................................................................................................................ 159
AS v1.5.00 - page 7 of 161
KNX Standard
Interworking
Datapoint Types
1 Introduction
1.1 Classification and identification of Datapoint Types
Datapoint Type
Data Type
Dimension
Format
Encoding
Range
Unit
Figure 1 - Structure of Datapoint Types The Datapoint Types are defined as a combination of a data type and a dimension. It has been preferred not to define the data types separately from any dimension. This only leads to more abstract naming and identifications. Any Datapoint Type thus standardizes one combination of format, encoding, range and unit. The Datapoint Types will be used to describe further KNX Interworking Standards. The Datapoint Types are identified by a 16 bit main number separated by a dot from a 16-bit subnumber, e.g. "7.002". The coding is as follows: Stands for Format main number(left) Encoding Range subnumber (right) Unit Datapoint Types with the same main number thus have the same format and encoding. Datapoint Types with the same main number have the same data type. A different subnumber indicates a different dimension (different range and/or different unit). Field
AS v1.5.00 - page 8 of 161
KNX Standard
Interworking
Datapoint Types
1.2
Subtype ranges for Datapoint Type Identifiers
The assignment of Datapoint Type identifiers by KNX Association is done in a systematic way according the scheme below.
MAIN number Application Domain Common use 0 199 Subnumber 0 99 mainly unstructured DPT is standard mainly unstructured common use DPT is standardised unstructured HVAC specific use 200 299 structured DPT is standardised structured common use DPT is standardised structured HVAC LTE only DPT is standardised structured 300 59 999 60 000
reserved for future use
HVAC
100 499
managed by WGI Reserved. These DPT-IDs shall not be used.
Load Management
500 599
Lighting
600 999
System
1 0001 199
Reserved Manufacturer specific

a
1200 50 999 60 000
DPT is standardised unstructured LMM specific usage DPT is DPT is standardised standardised unstructured structured lighting lighting DPT is DPT is standardised standardised unstructured structured system system reserved for other applications (managed by WGI) manufacturer specific extensions a
manufacturer specific extensions a
For interpretation of these Datapoint Types the device type needs to be known.
These ranges are defined for DPTs for given application areas. Entire ranges of 500 entries are assigned in one go.
Subtype range From 100 500 600 1 000 1 200 To 499 599 999 1 199 50 999 HVAC Load Management Lighting System Reserved for other application domains Application area
AS v1.5.00 - page 9 of 161
KNX Standard
Interworking
Datapoint Types
1.3
1.3.1
Datapoint Type specification style

Notations and format
Field Character String of n characters Boolean / Bit set Control Exponent Floating point value Mantissa eNumeration Reserved bit or field Sign Unsigned value 2's Complement signed value Standardised Status/Command B8. Encoding as in DPT_StatusGen
Symbol A A[n] B C E F M N r S U V Z8
Numbers in suffix denote the length of a field in bit.

EXAMPLE 1 U16 indicates a 16 bit unsigned integer.
In the following, the format is described MSB first (most significant octet left) and msb first (most significant bit left) inside an octet. Please refer as well to clause 1.4. Datapoint Types shorter than 1 octet are transmitted in the data-field of the frame on the lower bit positions. The preceding bits shall be 0.
1.3.2
Property Datatype
Property values can be encoded according the DPTs specified in this document. Therefore, this document specifies a mandatory Property Datatype for every DPT. In each clause of this document, this Property Datatype is specified: for all DPTs in that clause in general, or for each DPT in that clause individually. If the Property Value is an array, then all elements of that array shall be encoded according this specified DPT. Please refer to [02] for the specification of the Property Datatypes. Interface Object Servers may encode the Property Datatypes on 5 bit or on 6 bit. This influences the Property Datatype that shall be used as specified below.
Property Datatype supported by the device Size 5 bit 6 bit Range 00h to 1Fh 00h to 3Fh The alternative Property Datatype as specified behind (Alt.: ) in the DPT definition. The Property Datatype as specified in the DPT definition. Property Datatype that shall be used
AS v1.5.00 - page 10 of 161
KNX Standard
Interworking
Datapoint Types
1.3.3
Use
Some DPTs can be used without any restriction. Other DPTs can only be used where this is allowed explicitly. This is specified in the DPT definitions. The following applies.
Abbreviation G FB Meaning General Functional Block Explanation This Datapoint Type can be used without any restrictions.
This Datapoint Type shall not be used in general. This Datapoint Type shall only be used for implementations of standard Functional Blocks where this DPT is used. This Datapoint Type is not allowed for any other purpose.
HVAC HWH TU
Application Domains
This Datapoint Type shall not be used in general. This Datapoint Type may only be used within the specified application domain. This Datapoint Type is not allowed for any other purpose.
1.4
The transmission of DPT encoded data on the bus

Octet 6
Data encoded according a DPT that is transmitted on the KNX system shall be transmitted with the most significant octet first in the frame and the least significant octet last. An example is shown in Figure 2.
Octet 7 Octet 8 Octet 9 Octet 10 APCI r r r Day r r r r Month r Year 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 APCI APCI APCI APCI 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 1 1 0 0 0 0 0 0 0 1 1 0 18 12 2006
Figure 2 December 12, 2006 encoded according DPT_Date in an A_GroupValue_Write-frame (example on TP1)
NOTE 1 The transmission order of the bits within an octet depends on the medium and may be most significant bit (msb) first or least significant bit (lsb) first.
AS v1.5.00 - page 11 of 161
KNX Standard
Interworking
Datapoint Types
2 Overview
DPT_ID 1.001 1.002 1.003 1.004 1.005 1.006 1.007 1.008 1.009 1.010 1.011 1.012 1.013 1.014 1.015 1.016 1.017 1.018 1.019 1.021 1.022 1.023 1.100 2.001 2.002 2.003 2.004 2.005 2.006 2.007 2.008 2.009 2.010 2.011 2.012 3.007 3.008 4.001 4.002 5.001 5.003 5.004 5.005 5.006 5.010 6.001 6.010 6.020 7.001 7.002 7.003 7.004 Format B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B1 B2 B2 B2 B2 B2 B2 B2 B2 B2 B2 B2 B2 B1U3 B1U3 A8 A8 U8 U8 U8 U8 U8 U8 V8 V8 B5N3 U16 U16 U16 U16 DPT_Name DPT_Switch DPT_Bool DPT_Enable DPT_Ramp DPT_Alarm DPT_BinaryValue DPT_Step DPT_UpDown DPT_OpenClose DPT_Start DPT_State DPT_Invert DPT_DimSendStyle DPT_InputSource DPT_Reset DPT_Ack DPT_Trigger DPT_Occupancy DPT_Window_Door DPT_LogicalFunction DPT_Scene_AB DPT_ShutterBlinds_Mode DPT_Heat/Cool DPT_Switch_Control DPT_Bool_Control DPT_Enable_Control DPT_Ramp_Control DPT_Alarm_Control DPT_BinaryValue_Control DPT_Step_Control DPT_Direction1_Control DPT_Direction2_Control DPT_Start_Control DPT_State_Control DPT_Invert_Control DPT_Control_Dimming DPT_Control_Blinds DPT_Char_ASCII DPT_Char_8859_1 DPT_Scaling DPT_Angle DPT_Percent_U8 DPT_DecimalFactor DPT_Tariff DPT_Value_1_Ucount DPT_Percent_V8 DPT_Value_1_Count DPT_Status_Mode3 DPT_Value_2_Ucount DPT_TimePeriodMsec DPT_TimePeriod10MSec DPT_TimePeriod100MSec
KNX Standard
DPT_ID 7.005 7.006 7.007 7.010 7.011 7.012 7.013 8.001 8.002 8.003 8.004 8.005 8.006 8.007 8.010 8.011 9.001 9.002 9.003 9.004 9.005 9.006 9.007 9.008 9.010 9.011 9.020 9.021 9.022 9.023 9.024 9.025 9.026 9.027 9.028 10.001 11.001 12.001 13.001 13.010 13.011 13.012 13.013 13.014 13.015 13.100 14.000 14.001 14.002 14.003 14.004 14.005 14.006 14.007 Format U16 U16 U16 U16 U16 U16 U16 V16 V16 V16 V16 V16 V16 V16 V16 V16 F16 F16 F16 F16 F16 F16 F16 F16 F16 F16 F16 F16 F16 F16 F16 F16 F16 F16 F16 N3N5r2N6r2N6 r3N5r4N4r1U7 U32 V32 V32 V32 V32 V32 V32 V32 V32 F32 F32 F32 F32 F32 F32 F32 F32
Interworking
DPT_Name DPT_TimePeriodSec DPT_TimePeriodMin DPT_TimePeriodHrs DPT_PropDataType DPT_Length_mm DPT_UElCurrentmA DPT_Brightness DPT_Value_2_Count DPT_DeltaTimeMsec DPT_DeltaTime10MSec DPT_DeltaTime100MSec DPT_DeltaTimeSec DPT_DeltaTimeMin DPT_DeltaTimeHrs DPT_Percent_V16 DPT_Rotation_Angle DPT_Value_Temp DPT_Value_Tempd DPT_Value_Tempa DPT_Value_Lux DPT_Value_Wsp DPT_Value_Pres DPT_Value_Humidity DPT_Value_AirQuality DPT_Value_Time1 DPT_Value_Time2 DPT_Value_Volt DPT_Value_Curr DPT_PowerDensity DPT_KelvinPerPercent DPT_Power DPT_Value_Volume_Flow DPT_Rain_Amount DPT_Value_Temp_F DPT_Value_Wsp_kmh DPT_TimeOfDay
Datapoint Types
DPT_Date
DPT_Value_4_Ucount DPT_Value_4_Count DPT_ActiveEnergy DPT_ApparantEnergy DPT_ReactiveEnergy DPT_ActiveEnergy_kWh DPT_ApparantEnergy_kVAh DPT_ReactiveEnergy_kVARh DPT_LongDeltaTimeSec DPT_Value_Acceleration DPT_Value_Acceleration_Angular DPT_Value_Activation_Energy DPT_Value_Activity DPT_Value_Mol DPT_Value_Amplitude DPT_Value_AngleRad DPT_Value_AngleDeg
KNX Standard
DPT_ID 14.008 14.009 14.010 14.011 14.012 14.013 14.014 14.015 14.016 14.017 14.018 14.019 14.020 14.021 14.022 14.023 14.024 14.025 14.026 14.027 14.028 14.029 14.030 14.031 14.032 14.033 14.034 14.035 14.036 14.037 14.038 14.039 14.040 14.041 14.042 14.043 14.044 14.045 14.046 14.047 14.048 14.049 14.050 14.051 14.052 14.053 14.054 14.055 14.056 14.057 14.058 14.059 14.060 14.061 Format F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32
Interworking
DPT_Name
Datapoint Types
DPT_Value_Angular_Momentum DPT_Value_Angular_Velocity DPT_Value_Area DPT_Value_Capacitance DPT_Value_Charge_DensitySurface DPT_Value_Charge_DensityVolume DPT_Value_Compressibility DPT_Value_Conductance DPT_Value_Electrical_Conductivity DPT_Value_Density DPT_Value_Electric_Charge DPT_Value_Electric_Current DPT_Value_Electric_CurrentDensity DPT_Value_Electric_DipoleMoment DPT_Value_Electric_Displacement DPT_Value_Electric_FieldStrength DPT_Value_Electric_Flux DPT_Value_Electric_FluxDensity DPT_Value_Electric_Polarization DPT_Value_Electric_Potential DPT_Value_Electric_PotentialDifference DPT_Value_ElectromagneticMoment DPT_Value_Electromotive_Force DPT_Value_Energy DPT_Value_Force DPT_Value_Frequency DPT_Value_Angular_Frequency DPT_Value_Heat_Capacity DPT_Value_Heat_FlowRate DPT_Value_Heat_Quantity DPT_Value_Impedance DPT_Value_Length DPT_Value_Light_Quantity DPT_Value_Luminance DPT_Value_Luminous_Flux DPT_Value_Luminous_Intensity DPT_Value_Magnetic_FieldStrength DPT_Value_Magnetic_Flux DPT_Value_Magnetic_FluxDensity DPT_Value_Magnetic_Moment DPT_Value_Magnetic_Polarization DPT_Value_Magnetization DPT_Value_MagnetomotiveForce DPT_Value_Mass DPT_Value_MassFlux DPT_Value_Momentum DPT_Value_Phase_AngleRad DPT_Value_Phase_AngleDeg DPT_Value_Power DPT_Value_Power_Factor DPT_Value_Pressure DPT_Value_Reactance DPT_Value_Resistance DPT_Value_Resistivity
KNX Standard
DPT_ID 14.062 14.063 14.064 14.065 14.066 14.067 14.068 14.069 14.070 14.071 14.072 14.073 14.074 14.075 14.076 14.077 14.078 14.079 15.000 16.000 16.001 17.001 18.001 19.001 20.001 20.002 20.003 20.004 20.005 20.006 20.007 20.008 20.011 20.012 20.013 20.014 20.017 20.100 20.101 20.102 20.103 20.104 20.105 20.106 20.107 20.108 20.109 20.110 20.111 20.112 20.113 20.600 20.601 20.1000 Format
Interworking
DPT_Name
Datapoint Types
F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 F32 U4U4U4U4U4U4B4N4 A112 A112 r2U6 B1r1U6 U8[r4U4][r3U5][U3U5][r2U6][r2U6]B16 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8
DPT_Value_SelfInductance DPT_Value_SolidAngle DPT_Value_Sound_Intensity DPT_Value_Speed DPT_Value_Stress DPT_Value_Surface_Tension DPT_Value_Common_Temperature DPT_Value_Absolute_Temperature DPT_Value_TemperatureDifference DPT_Value_Thermal_Capacity DPT_Value_Thermal_Conductivity DPT_Value_ThermoelectricPower DPT_Value_Time DPT_Value_Torque DPT_Value_Volume DPT_Value_Volume_Flux DPT_Value_Weight DPT_Value_Work DPT_Access_Data DPT_String_ASCII DPT_String_8859_1 DPT_SceneNumber DPT_SceneControl DPT_DateTime DPT_SCLOMode DPT_BuildingMode DPT_OccMode DPT_Priority DPT_LightApplicationMode DPT_ApplicationArea DPT_AlarmClassType DPT_PSUMode DPT_ErrorClass_System DPT_ErrorClass_HVAC DPT_Time_Delay DPT_Beaufort_Wind_Force_Scale DPT_SensorSelect DPT_FuelType DPT_BurnerType DPT_HVACMode DPT_DHWMode DPT_LoadPriority DPT_HVACContrMode DPT_HVACEmergMode DPT_ChangeoverMode DPT_ValveMode DPT_DamperMode DPT_HeaterMode DPT_FanMode DPT_MasterSlaveMode DPT_StatusRoomSetp DPT_Behaviour_Lock_Unlock DPT_Behaviour_Bus_Power_Up_Down DPT_CommMode
AS v1.5.00 - page 15 of 161
KNX Standard
DPT_ID 20.1001 20.1002 20.1003 21.001 21.002 21.100 21.101 21.102 21.103 21.104 21.105 21.106 21.1000 21.1001 21.1010 22.100 22.101 22.1000 22.1010 23.001 23.002 23.003 23.102 24.001 25.1000 26.001 27.001 28.001 29.010 29.011 29.012 30.1010 31.101 200.100 200.101 201.100 201.102 201.104 201.105 201.107 201.108 201.109 202.001 202.002 203.002 203.003 203.004 203.005 203.006 203.007 203.011 203.012 203.013 203.014 Format N8 N8 N8 B8 B8 B8 B8 B8 B8 B8 B8 B8 B8 B8 B8 B16 B16 B16 B16 N2 N2 N2 N2 A[n] U4U4 r1b1U6 B32 A[n] V64 V64 V64 B24 N3 B1Z8 B1Z8 N8Z8 N8Z8 N8Z8 N8Z8 N8Z8 N8Z8 N8Z8 U8Z8 U8Z8 U16Z8 U16Z8 U16Z8 U16Z8 U16Z8 U16Z8 U16Z8 U16Z8 U16Z8 U16Z8
Interworking
DPT_Name
Datapoint Types
DPT_AddInfoTypes DPT_RF_ModeSelect DPT_RF_FilterSelect DPT_StatusGen DPT_Device_Control DPT_ForceSign DPT_ForceSignCool DPT_StatusRHC DPT_StatusSDHWC DPT_FuelTypeSet DPT_StatusRCC DPT_StatusAHU DPT_RF_ModeInfo DPT_RF_FilterInfo DPT_Channel_Activation_8 DPT_StatusDHWC DPT_StatusRHCC DPT_Media DPT_Channel_Activation_16 DPT_OnOff_Action DPT_Alarm_Reaction DPT_UpDown_Action DPT_HVAC_PB_Action DPT_VarString_8859_1 DPT_DoubleNibble DPT_SceneInfo DPT_CombinedInfoOnOff DPT_UTF-8 DPT_ActiveEnergy_V64 DPT_ApparantEnergy_V64 DPT_ReactiveEnergy_V64 DPT_Channel_Activation_24 DPT_PB_Action_HVAC_Extended DPT_Heat/Cool_Z DPT_BinaryValue_Z DPT_HVACMode_Z DPT_DHWMode_Z DPT_HVACContrMode_Z DPT_EnablH/Cstage_Z DPT_EnablH/CStage DPT_BuildingMode_Z DPT_OccMode_Z DPT_HVACEmergMode_Z DPT_RelValue_Z DPT_UCountValue8_Z DPT_TimePeriodMsec_Z DPT_TimePeriod10Msec_Z DPT_TimePeriod100Msec_Z DPT_TimePeriodSec_Z DPT_TimePeriodMin_Z DPT_TimePeriodHrs_Z DPT_UFlowRateLiter/h_Z DPT_UCountValue16_Z DPT_UElCurrentA_Z DPT_PowerKW_Z
KNX Standard
DPT_ID 203.015 203.017 203.100 203.101 203.102 203.104 204.001 205.002 205.003 205.004 205.005 205.006 205.007 205.100 205.101 205.102 206.100 206.102 206.104 206.105 207.100 207.101 207.102 207.104 207.105 209.100 209.101 209.102 209.103 210.100 211.100 212.100 212.101 213.100 213.101 213.102 214.100 214.101 215.100 215.101 216.100 217.001 218.001 219.001 220.100 221.001 222.100 222.101 223.100 224.100 225.001 225.002 229.001 230.1000 Format U16Z8 U16Z8 U16Z8 U16Z8 U16Z8 U16Z8 V8Z8 V16Z8 V16Z8 V16Z8 V16Z8 V16Z8 V16Z8 V16Z8 V16Z8 V16Z8 U16N8 U16N8 U16N8 U16N8 U8B8 U8B8 U8B8 U8B8 U8B8 V16B8 V16B8 V16B8 V16B8 V16B16 U8N8 V16V16V16 V16V16V16 V16V16V16V16 V16V16V16V16 V16V16V16V16 V16U8B8 V16U8B8 V16U8B16 V16U8B16 U16U8N8B8 U5U5U6 V32Z8 U8N8N8N8B8B8 U16V16 N16U32 F16F16F16 F16F16F16 V8N8N8 V16V16N8N8 U16U8 U16U8 V32N8Z8 U16U32U8N8
Interworking
DPT_Name
Datapoint Types
DPT_AtmPressureAbs_Z DPT_PercentU16_Z DPT_HVACAirQual_Z DPT_WindSpeed_Z DPT_WindSpeed DPT_SunIntensity_Z DPT_HVACAirFlowAbs_Z DPT_RelSignedValue_Z DPT_DeltaTimeMsec_Z DPT_DeltaTime10Msec_Z DPT_DeltaTime100Msec_Z DPT_DeltaTimeSec_Z DPT_DeltaTimeMin_Z DPT_DeltaTimeHrs_Z DPT_TempHVACAbs_Z DPT_TempHVACRel_Z DPT_HVACAirFlowRel_Z DPT_HVACModeNext DPT_DHWModeNext DPT_OccModeNext DPT_BuildingModeNext DPT_StatusBUC DPT_LockSign DPT_ValueDemBOC DPT_ActPosDemAbs DPT_StatusAct DPT_StatusHPM DPT_TempRoomDemAbs DPT_StatusCPM DPT_StatusWTC DPT_TempFlowWaterDemAbs DPT_EnergyDemWater DPT_TempRoomSetpSetShift[3] DPT_TempRoomSetpSet[3] DPT_TempRoomSetpSet[4] DPT_TempDHWSetpSet[4] DPT_TempRoomSetpSetShift[4] DPT_PowerFlowWaterDemHPM DPT_PowerFlowWaterDemCPM DPT_StatusBOC DPT_StatusCC DPT_SpecHeatProd DPT_Version DPT_VolumeLiter_Z DPT_AlarmInfo DPT_TempHVACAbsNext DPT_SerNum DPT_TempRoomSetpSetF16[3] DPT_TempRoomSetpSetShiftF16[3] DPT_EnergyDemAir DPT_TempSupply AirSetpSet DPT_ScalingSpeed DPT_Scaling_Step_Time DPT_MeteringValue DPT_MBus_Address
KNX Standard
DPT_ID 231.001 232.600 234.001 234.002 Format A8A8A8A8 U8U8U8 A8A8 A8A8
Interworking
DPT_Name
Datapoint Types
DPT_Locale_ASCII DPT_Colour_RGB DPT_LanguageCodeAlpha2_ASCII DPT_RegionCodeAlpha2_ASCII
AS v1.5.00 - page 18 of 161
KNX Standard
Interworking
Datapoint Types
3 Datapoint Types for common use

3.1 Datapoint Types B1
1 bit: B1 1 b B b = {0,1} None. (not applicable) PDT_BINARY_INFORMATION (alt: PDT_UNSIGNED_CHAR)
octet nr field names encoding
Format:
Range: Unit: Resol.: PDT:
Datapoint Types ID: 1.001 1.002 1.003 1.004 1.005 1.006 1.007 1.008 1.009 1.010 1.011 1.012 1.013 1.014 1.015 1.016 1.017 1.018 Name: DPT_Switch DPT_Bool DPT_Enable DPT_Ramp DPT_Alarm DPT_BinaryValue DPT_Step DPT_UpDown DPT_OpenClose DPT_Start DPT_State DPT_Invert DPT_DimSendStyle DPT_InputSource DPT_Reset DPT_Ack DPT_Trigger DPT_Occupancy 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0, 1 0 1 = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Encoding: b Off On False True Disable Enable No ramp Ramp No alarm Alarm Low High Decrease Increase Up Down Open Close Stop Start Inactive Active Not inverted Inverted Start/stop Cyclically Fixed Calculated no action (dummy) reset command (trigger) no action (dummy) acknowledge command (trigger), e.g. for alarming trigger not occupied occupied Use: G G G FB FB FB FB G G G FB FB FB FB G G G G
AS v1.5.00 - page 19 of 161
KNX Standard
Format:
Interworking
Datapoint Types
1 bit: B1 1 b B b = {0,1} None. (not applicable) PDT_BINARY_INFORMATION (alt: PDT_UNSIGNED_CHAR)
Datapoint Types ID: 1.019 1.021 1.022 1.023 Name: DPT_Window_Door DPT_LogicalFunction DPT_Scene_AB
1)
Encoding: b 0 1 0 1 0 1 0 1 = = = = = = = = closed open logical function OR logical function AND scene A scene B only move Up/Down mode (shutter) move Up/Down + StepStop mode (blind)
Use: G FB FB FB
DPT_ShutterBlinds_Mode
1)
DPT_Scene_AB allows numbering the scenes with 0 and 1. KNX Association recommends displaying these scene numbers in ETS, other software and controllers as 1 and 2, this is, with an offset of 1 compared to the actual transmitted value.
KNX Standard
Interworking
Datapoint Types
3.2
Datapoint Types B2
2 bit: B2 1 cv BB c = v = None (not applicable) PDT_GENERIC_01 {0,1} {0,1}
octet nr
Format:
field names encoding
Datapoint Types ID: Name: Use: Encoding: c 0 = no control 1 = control 2.001 2.002 2.003 2.004 2.005 2.006 2.007 2.008 2.009 2.010 2.011 2.012 DPT_Switch_Control DPT_Bool_Control DPT_Enable_Control DPT_Ramp_Control DPT_Alarm_Control DPT_BinaryValue_Control DPT_Step_Control DPT_Direction1_Control DPT_Direction2_Control DPT_Start_Control DPT_State_Control DPT_Invert_Control G G FB FB FB FB FB FB FB FB FB FB c 0 0 1 1 v 0 1 0 1 v According to Type 1.xxx
No control No control Control. Function value 0 Control. Function value 1
AS v1.5.00 - page 21 of 161
KNX Standard
Interworking
Datapoint Types
3.3
3.3.1
Datapoint Types B1U3

DPT_Control_Dimming
4 bit: B1U3 1 c Code BUUU c StepCode none (not applicable) PDT_GENERIC_01 = {0,1} = [000b111b]
Step-
Format:
Datapoint Types ID: 3.007 Data fields c Name: DPT_Control_Dimming Description Increase or decrease the brightness. Encoding See 1.007 0 = Decrease 1 = Increase
1
Use: FB
StepCode
The amount of intervals into which the range of 0 % 100 % is subdivided, or the break indication.
001b111b: Step Number of intervals = 2^(stepcode-1) Break
- 000b:
AS v1.5.00 - page 22 of 161
KNX Standard
Interworking
Datapoint Types
3.3.2
Format:
DPT_Control_Blinds
4 bit: B1U3 1 c Code BUUU c StepCode none (not applicable) PDT_GENERIC_01 = {0,1} = [000b111b]
Step-
Datapoint Types ID: 3.008 Data fields c Name: DPT_Control_Blinds Description Move up or down. Encoding See 1.008 0 = Up 1 = Down
1
Use: FB
StepCode
The amount of intervals into which the range of 0 % 100 % is subdivided, or the break indication.
- 001b111b: Step
Number of intervals = 2^(stepcode-1)
- 000b:
Break
NOTE This DPT can be used both for the relative positioning of the vertical blinds positions as well as for the relative positioning of the angle of the slats.
AS v1.5.00 - page 23 of 161
KNX Standard
Interworking
Datapoint Types
3.4
Datapoint Types Character Set

8 bit: A8 1 Ch arac ter AAAAAAAA None (not applicable)
octet nr
Format:
Unit: Resol.:
Datapoint Types ID: 4.001 Name: DPT_Char_ASCII Range: Encoding: PDT: Use:
[0...127] See below. The most significant bit shall always be 0.
PDT_GENERIC_01 G (alt: PDT_UNSIGNED_CHAR) PDT_UNSIGNED_CHAR G
4.002
DPT_Char_8859_1 [0...255] See below.
Encoding:
AAAA MSN AAAA LSN = Least Significant Nibble LSN
2
MSN = Most Significant Nibble

3 0 1 2 3 4 5 6 7 8 9 : ; < = > ? 4 @ A B C D E F G H I J K L M N O 5 P Q R S T U V W X Y Z [ \ ] ^ _ 6 ` a b c d e f g h i j k l m n o 7 p q r s t u v w x y z { | } ~ 8 9 A B C D E F
4.001 4.002
DPT_Char_ASCII DPT_Char_8859_1
MSN 0 1 LSN 0 NUL DLE 1 SOH DC1 2 STX DC2 3 ETX DC3 4 EOT DC4 5 ENQNAK 6 ACK SYN 7 BEL ETB 8 BS CAN 9 HT EM A LF SUB B VT ESC C FF FS D CR GS E SO RS F SI US
! " # $ % & ' ( ) * + , . /
Decoding of 00h to 1Fh The support of the control characters in the range 00h to 1Fh is not mandatory. The receiver shall not react on reception of an unsupported value in this range. If the receiver supports any of the encoded controls (like backspace, clear screen ...) the encoding shall however be as indicated above.
AS v1.5.00 - page 24 of 161
KNX Standard
Interworking
Datapoint Types
3.5
3.5.1
Datapoint Types 8-Bit Unsigned Value

Scaled values
8 bit: U8 1 Unsigned Value UUUUUUUU binary encoded msb lsb U U U U U U U U 0 0 0 0 0 0 0 0 = range min. /off 0 0 0 0 0 0 0 1 = value low 1 1 1 1 1 1 1 1 = range max. U = [0255] Range: [0100] [0360] [0255] Unit: Resol.: % %
octet nr
Format:
field names
encoding
Encoding:
Range:
Datapoint Types ID: Name: PDT: Use: G 0,4 % PDT_SCALING (alt.: PDT_UNISIGNED_CHAR) 1,4 PDT_UNSIGNED_CHAR 1 % PDT_UNSIGNED_CHAR G FB
5.001 DPT_Scaling 5.003 DPT_Angle 5.004 DPT_Percent_U8 2)
NOTE 2 Differences between DPT_Scaling (5.001) and DPT_Percent_U8 (5.004) Datapoint Type 5.001 5.004 Encoded Value 50 % 80h 32h 100 % FFh 64h 255 % Out of encodable range. FFh Resolution 0,4 % 1%
5.005 DPT_DecimalFactor
ratio
PDT_UNSIGNED_CHAR
2)
This DPT was previously named DPT_RelPos_Valve.

KNX Standard
Interworking
Datapoint Types
3.5.2
Format:
Non-scaled values
8 bit: U8 1 Unsigned Value UUUUUUUU binary encoded UnsignedValue = [0255] PDT_UNSIGNED_CHAR
3.5.2.1 DPT_Value_1_Ucount
octet nr field names
encoding
Encoding: Range: PDT:
Datapoint Types ID: 5.010 Name: DPT_Value_1_Ucount Range: [0255] Unit: counter pulses Resol.: 1 counter pulse Use: G
3.5.2.2 DPT for tariff information

Format:
octet nr. field names
8 bit: U8 1 Unsigned Value UUUUUUUU 0: 1 to 254: 255: no tariff available current or desired value reserved; shall not be used (This value shall not be transmitted. On reception, the message with this value shall be ignored.) [0 254]
encoding
Encoding:
Range:: Unit: Resol.: PDT:
UnsignedValue = none (not applicable)
PDT_UNSIGNED_CHAR
Datapoint Types ID: 5.006 Name: DPT_Tariff Use: G
Usage This DPT shall be used for reading and setting tariff information. A large number of different tariffs are defined and these are specific to the country and even to the supplier. Therefore, the mapping between a tariff and this DPT is not standardised. For usability and interpretability of the tariff information by the end user, the product description should give clear information about this mapping
AS v1.5.00 - page 26 of 161
KNX Standard
Interworking
Datapoint Types
3.6
3.6.1
Datapoint Types V8
Signed Relative Value
8 bit 1 RelSigned Value VVVVVVVV -128 127 PDT_CHAR
Format:
encoding
Encoding: Two's complement notation Range: PDT:
Datapoint Types ID: 6.001 6.010 Name: DPT_Percent_V8 Range: -128 % 127 % Unit: % counter pulses Resolution 1% 1 counter pulse Use: G G
DPT_Value_1_Count -128 127
3.7
Datapoint Type Status with Mode

8 bit: B5N3 1 a b c d e f
Format:
encoding
B B B B B NNN a, b, c, d, e = {0,1} f = {001b,010b,100b} none (not applicable) PDT_GENERIC_01
Datapoint Types ID: 6.020 Name: DPT_Status_Mode3 Encoding: A,B,C,D,E: 0 = set 1 = clear FFF 001b = mode 0 is active 010b = mode 1 is active 100b = mode 2 is active Use: FB
AS v1.5.00 - page 27 of 161
KNX Standard
Interworking
Datapoint Types
3.8
3.8.1
Datapoint Types 2-Octet Unsigned Value

2-octet unsigned counter value
2 octets: U16 2 MSB 1 LSB
Format:
UnsignedValue UUUUUUUU UUUUUUUU
Encoding: Range: PDT
Binary encoded value UnsignedValue = [065535] PDT_UNSIGNED_INT
Datapoint Types ID: 7.001 7.010 Name: DPT_Value_2_Ucount DPT_PropDataType Range: [065 535] Identifier Interface Object Property data type. No Unit. Unit: pulses n.a. 3) Resol.: 1 pulse n.a. 4) Use: G FB
3.8.2
Format:
Time Period
2 octets: U16 2 MSB TimePeriod UUUUUUUU UUUUUUUU 1 LSB
Binary encoded value UnsignedValue = [065535] PDT_UNSIGNED_INT
Datapoint Types ID: 7.002 7.003 7.004 7.005 7.006 7.007 Name: DPT_TimePeriodMsec DPT_TimePeriod10Msec DPT_TimePeriod100Msec DPT_TimePeriodSec DPT_TimePeriodMin DPT_TimePeriodHrs Range: 0 ms 6 5535 ms 0 s 655,35 s 0 s 6 553,5 s 0 s 65 535 s 0 min 65 535 min 0 h 65 535 h Unit: ms ms ms ( 18,2 hours) s ( 45,5 days) min ( 7,4 years) h Resol.: 1 ms 10 ms 100 ms 1s 1 min 1h Use: G G 5) G 5) G G 5) G
3) 4) 5)
n.a. : not applicable n.a. : not applicable Not allowed for runtime communication. This DPT shall only be used for parameters and diagnostic data or if specified as such in a FB specification!
KNX Standard
Interworking
Datapoint Types
3.8.3
Format:
Other U16 Datapoint Types

2 octets: U16 2MSB 1LSB
octet nr. field names encoding
UnsignedValue UUUUUUUU UUUUUUUU
Encoding: See below Range: Unit: Resol.: PDT: ID: 7.011 7.012 UnsignedValue = See below. see below. PDT_UNSIGNED_INT Name: DPT_Length_mm DPT_UElCurrentmA Range, encoding 0 mm 65 535 mm 0 = no bus power supply functionality available Unit: mm none Resol.: 1 mm Use: FB SAB [0 65 535]
Datapoint Types
not applicable FB
1 65 535 = value binary encoded 7.013 DPT_Brightness 0 lux 65 535 lux value binary encoded
mA lux
1 mA 1 lux FB 6)
6)
DPT_Brightness shall solely be used for the encoding of the approved E-Mode parameters. For run-time communication, DPT_Value_Lux (F16) shall be used.
KNX Standard
Interworking
Datapoint Types
3.9
3.9.1
Datapoint Types 2-Octet Signed Value

2-octet signed counter value
2 octet: V16 2 MSB 1 LSB
Format:
SignedValue VVVVVVVV VVVVVVVV
Twos complement notation SignedValue = [-32 768 32 768] PDT_INT
Datapoint Types ID: 8.001 8.010

a) b)
Name: DPT_Value_2_Count DPT_Percent_V16
Range: [-32 768 32 767] a) -327,68 % ... 327,67 %
Unit: pulses %
Resol.: 1 pulse 0,01 %
Use: G G
Only for DPT_Value_2_Ucount, the value 7FFFh can be used to denote invalid data. For DPT_Percent_, the value 7FFFh shall be used to denote invalid data.
3.9.2
Format:
Delta Time
2 octet: V16 2 MSB DeltaTime VVVVVVVV VVVVVVVV 1 LSB
Twos complement notation SignedValue = [-32 768 32 768] PDT_INT
Datapoint Types ID: 8.002 8.003 8.004 8.005 8.006 8.007 Name: DPT_DeltaTimeMsec DPT_DeltaTime10Msec DPT_DeltaTime100Msec DPT_DeltaTimeSec DPT_DeltaTimeMin DPT_DeltaTimeHrs Range: -32 768 ms 32 767 ms -327,68 s 327,67 s -3 276,8 s 3 276,7 s -32 768 s 32 767 s Unit: ms ms ms ( 9,1 h) s Resol.: 1 ms 10 ms 100 ms 1s 1 min 1h Use: G G a) G a) G G a) G
-32 768 min 32 767 min ( 22,7 d) min -32 768 h 32 767 h ( 3,7 y) h
a) Not allowed for run-time communication. This DPT shall only be used for parameters and diagnostic data or if specified as such in a FB specification.
AS v1.5.00 - page 30 of 161
KNX Standard
Interworking
Datapoint Types
3.9.3
Format:
Other V16 Datapoint Types

2 octets: V16 2MSB SignedValue V V V V V V V V V V V V V V V V 1LSB
Encoding: Twos complement notation. Range: Unit: Resol.: PDT: ID: 8.011 SignedValue = [-32 768 32 768] See below See below PDT_INT Name: DPT_Rotation_Angle Range: [-32 768 32 768] Unit: Resol.: 1 Use: FB SAB
Datapoint Types
3.10 Datapoint Types 2-Octet Float Value

Format:
2 octets: F16 2 MSB FloatValue M E E E E MMM M MM M M MMM M 1 LSB
Encoding (E) FloatValue = (0,01*M)*2 : E = [0 15] M = [-2 048 2 047], twos complement notation For all Datapoint Types 9.xxx, the encoded value 7FFFh shall always be used to denote invalid data. Range: [-671 088,64 670 760,96] PDT: PDT_KNX_FLOAT
Datapoint Types ID: 9.001 9.002 9.003 9.004 9.005 9.006 Name: DPT_Value_Temp DPT_Value_Tempd DPT_Value_Tempa DPT_Value_Lux DPT_Value_Wsp DPT_Value_Pres Range: -273 C 670 760 C -670 760 K 670 760 K -670 760 K/h 670 760 K/h 0 Lux 670 760 Lux 0 m/s 670 760 m/s 0 Pa 670 760 Pa Unit: C 7) K K/h Lux m/s Pa Resol.: 0,01 C 0,01 K 0,01 K/h 0,01 Lux 0,01 m/s 0,01 Pa Use: G G G G G G
7)
KNX Association strongly recommends full implementation of this Datapoint Type in objects with actuator functionality (i.e. receiving values from the bus). However, it is allowed for objects sending on or receiving temperature values from the bus to only support this Datapoint Type with a fixed exponent of 3. In this case, an appropriate warning shall be made to the installer in the manufacturers product instruction sheet.
KNX Standard
Datapoint Types ID: 9.007 9.008 9.010 9.011 9.020 9.021 9.022 9.023 9.024 Name: DPT_Value_Humidity 8) DPT_Value_AirQuality DPT_Value_Time1 DPT_Value_Time2 DPT_Value_Volt DPT_Value_Curr DPT_PowerDensity DPT_KelvinPerPercent DPT_Power
Interworking
Datapoint Types
Range: 0 % 670 760 % 0 ppm 670 760 ppm -670 760 s 670 760 s -670 760 ms 670 760 ms -670 760 mV 670 760 mV -670 760 mA 670 760 mA -670 760 W/m2 670 760 W/m2 -670 760 K/% 670 760 K/% -670 760 kW 670 760 kW
Unit: % ppm s ms mV mA W/m2 K/% kW
Resol.: 0,01 % 0,01 ppm 0,01 s 0,01 ms 0,01 mV 0,01 mA
Use: G G G G G G
0,01 W/m2 FB 0,01 K/% 0,01 kW FB FB
NOTE 3 DPTs for power Two DPTs are specified for encoding electrical power. The DPT shall be chosen appropriately in function of the accuracy and range that shall be covered by the application. Table 1 DPTs for power ID 9.024 14.056 9.025 9.026 9.027 Name DPT_Power DPT_Value_Power Range -671 088,64 kW to 670 760,96 kW -671 088 640 W to 670 760 960 W ~10-44,85 to ~1038,53 l/h l/m2 F Resolution 10 W 1W 0,01 l/h 0,01 l/m2 0,01 F FB G G
DPT_Value_Volume_Flow DPT_Rain_Amount DPT_Value_Temp_F
-670 760 l/h 670 760 l/h -671 088,64 l/m2 to 670 760,96 l/m2 -459,6 F to 670 760,96 F
DPT_Value_Temp_F may be implemented only as extra DP next to a DP with DPT_Value_Temp (9.001). This applies both for Inputs as well as for Outputs. It shall be possible through a parameter to select the DP or its format; the default setting for this parameter shall enable DPT_Value_Temp (9.001). 9.028 DPT_Value_Wsp_kmh 0 km/h 670 760,96 km/h km/h 0,01 km/h G
DPT_Value_Wsp_kmh may be implemented only as extra DP next to a DP with DPT_Value_Wsp (9.005). This applies both for Inputs as well as for Outputs. It shall be possible through a parameter to select the DP or its format; the default setting for this parameter shall be DPT_Value_Wsp (9.005).
8)
This DPT is only used in case of universal I/O modules which can provide any sensor value in 2 octet float format.
KNX Standard
Interworking
Datapoint Types
3.11 Datapoint Type Time

Format:
3 octets: N3U5r2U6r2U6 3 MSB Day Hour 2 0 0 Minutes 1 LSB 0 0 Seconds
NNNUUUUU r r UUUUUU r r UUUUUU
Encoding: binary encoded PDT: ID: 10.001 PDT_TIME Name: Field: Encoding: 1 = Monday 7 = Sunday 0 = no day binary encoded binary encoded binary encoded Range: [07] Unit: none Resol.: none Use: G Datapoint Types DPT_TimeOfDay Day
Hour Minutes Seconds
[023] [059] [059]
hours minutes seconds
h min s
3.12 Datapoint Type Date

Format:
3 octets: r3U5r4U4r1U7 3 MSB 000 Day 2 0 0 0 0 Month 0 1 LSB Year
r r r UUUUU r r r r UUU U r UUUUUUU
Encoding: All values binary encoded. PDT: ID: 11.001 PDT_DATE Name: Field: Month Year Range: [131] [112] [099] Unit: Day of month Month Year Resol.: 1 day 1 month 1 year Use: G Datapoint Types DPT_Date Day
Century Encoding The following interpretation shall be carried out by devices receiving the Datapoint Type 11.001 and carrying out calculations on the basis of the entire 3rd octet: if Octet 3 contains value 90 : interpret as 20th century if Octet 3 contains value < 90: interpret as 21st century This format covers the range 1990 to 2089.
EXAMPLE 2 YYYYYYY YYYYYYY YYYYYYY = 99d equals 1999 = 0d equals 2000 = 4d equals 2004
AS v1.5.00 - page 33 of 161
KNX Standard
Interworking
Datapoint Types
3.13 Datapoint Types 4-Octet Unsigned Value

Format:
4 octets: U32 4 MSB 3 UnsignedValue U U U U U UU U Binary encoded UnsignedValue = [04 294 967 295] PDT_UNSIGNED_LONG U U U U U UUU UUUUUUUU UUUUUUUU 2 1 LSB
Datapoint Types ID: 12.001 Name: DPT_Value_4_Ucount Unit: counter pulses Resol.: 1 pulse Usage: G
3.14 Datapoint Types 4-Octet Signed Value

3.14.1 4 Octet signed counter value
Format:
4 octets: V32 4 MSB 3 SignedValue VVVVVVVV VVVVVVVV VVVVVVVV VVVVVVVV 2 1 LSB
Twos complement notation SignedValue = [-2 147 483 648 2 147 483 647] PDT_LONG
Datapoint Types ID: 13.001 Name: DPT_Value_4_Count Unit: counter pulses Resol.: 1 pulse Use: G
AS v1.5.00 - page 34 of 161
KNX Standard
Interworking
Datapoint Types
3.14.2 DPTs for electrical energy

Format:
4 octets: V32 4 MSB 3 SignedValue VVVVVVVV VVVVVVVV VVVVVVVV VVVVVVVV 2 1 LSB
Encoding: Twos complement notation. Range: PDT: SignedValue = [-2 147 483 648 2 147 483 647] PDT_LONG
Datapoint Types ID: Name: Range: [-2 147 483 648 2 147 483 647] Wh [-2 147 483 648 2 147 483 647] VAh [-2 147 483 648 2 147 483 647] VARh [-2 147 483 648 2 147 483 647] kWh [-2 147 483 648 2 147 483 647] kVAh Unit: Wh VAh Resol.: 1 Wh 1 VAh Use: G G G G G
13.010 DPT_ActiveEnergy 13.011 DPT_ApparantEnergy 13.012 DPT_ReactiveEnergy 13.013 DPT_ActiveEnergy_kWh 13.014 DPT_ApparantEnergy_kVAh
VARh 1 VARh kWh kVAh 1 kWh 1 kVAh
13.015 DPT_ReactiveEnergy_kVARh [-2 147 483 648 2 147 483 647] kVARh kVARh 1 kVARh G
NOTE 4 For electrical power, DPT_Power (9.024) or DPT_Value_Power (14.056) shall be used according NOTE 3.
3.14.3 4 Octet signed time period

Format:
4 octets: V32 4 MSB 3 SignedValue VVVVVVVV PDT_LONG VVVVVVVV VVVVVVVV VVVVVVVV 2 1 LSB
Encoding: PDT
Twos complement notation
Datapoint Types ID: 13.100

a)
Name:
Range:
a)
Unit: s
Resol.: 1s
Use: G b)
DPT_LongDeltaTimeSec -2 147 483 648 s 2 147 483 647 s
b)
This is approximately 68 years. Thanks to this large possible range, no binary overflow will be possible in practice. This DPT shall however only be used for diagnostic data, like operating hours. It shall not be used for run time communication (inputs and outputs) nor for parameters.
AS v1.5.00 - page 35 of 161
KNX Standard
Interworking
Datapoint Types
3.15 Datapoint Types 4-Octet Float Value

Format:
4 octets: F32 4 MSB S Exponent 3 2 Fraction 1 LSB
FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
Encoding: The values are encoded in the IEEE floating point format according IEEE 754. S (Sign) = {0,1} Range: Exponent = [0 255] Fraction = [0 8 388 607] PDT: PDT_FLOAT Datapoint Types ID: 14.000 14.001 14.002 14.003 14.004 14.005 14.006 14.007 14.008 14.009 14.010 14.011 14.012 14.013 14.014 14.015 14.016 14.017 14.018 14.019 14.020 14.021 14.022 14.023 14.024 14.025 14.026 14.027 Name: DPT_Value_Acceleration DPT_Value_Acceleration_Angular DPT_Value_Activation_Energy DPT_Value_Activity DPT_Value_Mol DPT_Value_Amplitude DPT_Value_AngleRad DPT_Value_AngleDeg DPT_Value_Angular_Momentum DPT_Value_Angular_Velocity DPT_Value_Area DPT_Value_Capacitance Unit: ms
-2 -2 -1
Resol.: 1 ms
-2 -2 -1
Comment: acceleration acceleration, angular activation energy activity (radioactive) amount of substance amplitude (unit as appropriate) angle, radiant angle, degree angular momentum
Use: G G G G G G G G G G G G G G G G G G G
rad s s rad Js rad s m F

2 -1
1 rad s 1s 1 rad 1 1Js

-1
J mol mol
1 J mol 1 mol
-1
1 rad s 1m 1F
2
-1
angular velocity area capacitance
DPT_Value_Charge_DensitySurface C m
-2
1Cm
-2
charge density (surface) charge density (volume) compressibility conductance
DPT_Value_Charge_DensityVolume C m-3 DPT_Value_Compressibility DPT_Value_Conductance DPT_Value_Electrical_Conductivity DPT_Value_Density DPT_Value_Electric_Charge DPT_Value_Electric_Current DPT_Value_Electric_DipoleMoment DPT_Value_Electric_Displacement DPT_Value_Electric_FieldStrength DPT_Value_Electric_Flux DPT_Value_Electric_FluxDensity DPT_Value_Electric_Polarization DPT_Value_Electric_Potential m2 N-1 S= Sm C A
-2 -1 -3 -1
1 C m-3 1 m2 N-1 1S 1Sm 1C 1A 1Am

-2 -1 -3
conductivity, electrical G density electric charge electric current
kg m
1 kg m
DPT_Value_Electric_CurrentDensity A m
electric current density G electric dipole moment G electric displacement electric field strength electric flux electric flux density electric polarization electric potential G G G G G G
Cm Cm Vm c Cm V
-2 -2 -2 -1
1Cm 1Cm 1Vm 1c 1Cm 1Cm 1V

-2 -2 -2 -1
Cm
AS v1.5.00 - page 36 of 161
KNX Standard
Datapoint Types ID: 14.028 14.029 14.030 14.031 14.032 14.033 14.034 14.035 14.036 14.037 14.038 14.039 14.040 14.041 14.042 14.043 14.044 14.045 14.046 14.047 14.048 14.049 14.050 14.051 14.052 14.053 14.054 14.055 14.056 14.057 14.058 14.059 14.060 14.061 14.062 Name:
Interworking
Datapoint Types
Unit:
Resol.: 1V 1 A m2 1V 1J 1N
-1
Comment: electric potential difference electromagnetic moment electromotive force energy force frequency
Use: G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G G
DPT_Value_Electric_PotentialDiffere V nce DPT_Value_ElectromagneticMoment A m2 DPT_Value_Electromotive_Force DPT_Value_Energy DPT_Value_Force DPT_Value_Frequency DPT_Value_Angular_Frequency DPT_Value_Heat_Capacity DPT_Value_Heat_FlowRate DPT_Value_Heat_Quantity DPT_Value_Impedance DPT_Value_Length DPT_Value_Light_Quantity DPT_Value_Luminance DPT_Value_Luminous_Flux DPT_Value_Luminous_Intensity DPT_Value_Magnetic_Flux DPT_Value_Magnetic_FluxDensity DPT_Value_Magnetic_Moment DPT_Value_Magnetic_Polarization DPT_Value_Magnetization DPT_Value_MagnetomotiveForce DPT_Value_Mass DPT_Value_MassFlux DPT_Value_Momentum DPT_Value_Phase_AngleRad DPT_Value_Phase_AngleDeg DPT_Value_Power
9)
V J N Hz = s rad s J K-1 W J m cd m lm cd
-1 -2 -1
1 Hz 1 rad s 1 J K-1 1W 1J 1 1m 1 cd m 1 lm 1 cd 1Am 1 Wb 1T

-1 -2 -1
frequency, angular (pulsatance) heat capacity heat flow rate heat, quantity of impedance length light, quantity of luminance luminous flux luminous intensity magnetic flux magnetic flux density
J or lm s 1 J
DPT_Value_Magnetic_FieldStrength A m Wb T Am T Am A kg
magnetic field strength G
1Am 1T
magnetic moment magnetic polarization magnetization magneto motive force mass
-1
1Am 1A 1 kg
-1
kg s Ns rad W
-1
1 kg s 1Ns 1 rad 1 1W
-1
mass flux momentum phase angle, radiant phase angle, degrees power power factor pressure reactance resistance resistivity self inductance
-1
-1
DPT_Value_Power_Factor DPT_Value_Pressure DPT_Value_Reactance DPT_Value_Resistance DPT_Value_Resistivity DPT_Value_SelfInductance
cos Pa = N m-2 m H
1 cos 1 Pa 1 1 1 m 1H
9)
Concerning the selection of the appropriate DPT for encoding electrical power, NOTE 2 shall be observed.
KNX Standard
Datapoint Types ID: 14.063 14.064 14.065 14.066 14.067 14.068 14.069 14.070 14.071 14.072 14.073 14.074 14.075 14.076 14.077 14.078 14.079 Name: DPT_Value_SolidAngle DPT_Value_Sound_Intensity DPT_Value_Speed DPT_Value_Stress DPT_Value_Surface_Tension
Interworking
Datapoint Types
Unit: sr Wm ms
-2 -1
Resol.: 1 sr 1 W m-2 1 m s-1 1 Pa 1 Nm-1 1C vK 1K
Comment: solid angle sound intensity speed stress surface tension
Use: G G G G G
Pa = N m-2 Nm-1 C K K JK
-1 -1
DPT_Value_Common_Temperature DPT_Value_Absolute_Temperature DPT_Value_TemperatureDifference DPT_Value_Thermal_Capacity DPT_Value_Thermal_Conductivity DPT_Value_ThermoelectricPower DPT_Value_Time DPT_Value_Torque DPT_Value_Volume DPT_Value_Volume_Flux DPT_Value_Weight DPT_Value_Work
temperature, common G temperature (absolute) G temperature difference G thermal capacity

-1
1 J K-1 1Wm K 1 V K-1 1s 1 Nm 1m

-1 3 3 -1 -1
G G G G G G G G G
Wm K-1 s Nm m N J
3 3
thermal conductivity thermoelectric power time

10)
V K-1
torque volume volume flux weight work
m s
1m s 1N 1J
3.16 Datapoint Type DPT_Access_Data

Format:
4 octets: U4U4U4U4U4U4B4N4 4 MSB D6 D5 D4 3 D3 D2 2 D1 1 LSB E P D C Index
UUUUUUUU UUUUUUUU UUUUUUUU b b b b NNNN binary encoded value binary encoded value See below
Encoding: D6, D5, D4, D3, D2, D1: N: E, P, D, C: Unit: Resol.: PDT: ID: Not applicable. Not applicable. PDT_GENERIC_04 Name: DPT_Access_Data
Datapoint Types Use: FB
15.000
10)
For proper usage see note!

KNX Standard
Field D6, D5, D4, D3, D2, D1 Description
Interworking
Encoding
Datapoint Types
Range [0 9]
digit x (16) of access identification code. Only a Values binary encoded. card or key number should be used. System number, version number, country code, etc are not necessary. Ciphered access information code should be possible in principle. If 24 bits are not necessary, the most significant positions shall be set to zero. Detection error
0 = no error {0,1} 1 = reading of access information code was not successful). {0,1} {0,1} {0,1} [0 15]
P D C Index
Permission (informs about the access decision made 0 = not accepted by the controlling device) 1 = accepted Read direction (e.g. of badge) If not used (e.g. electronic key) set to zero. Encryption of access information. Index of access identification code (future use) 0 = left to right 1 = right to left 0 = no 1 = yes Value binary encoded.
EXAMPLE 1 Transmission of the access identification code 123456, without error indication, permission accepted, badge read from left to right, no encryption and index 13. Octet 6 7 6 5 4 3 2 1 0 7 6 APCI 0 0 1 0 Octet 7 Octet 8 Octet 9 Octet 10 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 r r r r r r D6 D5 D4 D3 D2 D1 EP 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 1 1 0 1 0 0 0 1 0 1 0 1 1 0 0 1 1 2 3 4 5 6 Octet 11 5 4 3 2 1 0 D C Index 0 0 1 1 0 1 13
EXAMPLE 2 Transmission of the access identification code 6789, without error indication, permission not accepted, badge read from left to right, no encryption and index 14. Octet 6 7 6 5 4 3 2 1 0 7 6 APCI 0 0 1 0 Octet 7 Octet 8 Octet 9 Octet 10 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 r r r r r r D6 D5 D4 D3 D2 D1 EP 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 1 1 1 1 0 0 0 1 0 0 1 0 0 0 0 6 7 8 9 Octet 11 5 4 3 2 1 0 D C Index 0 0 1 1 1 0 14
AS v1.5.00 - page 39 of 161
KNX Standard
Interworking
Datapoint Types
3.17 Datapoint Types "String"

Format:
14 octets: A112 14 MSB Character 1 AAAAAAAA 1 LSB Character 14 AAAAAAAA
Encoding: These Datapoint Types are used to transmit strings of textual characters. The length is fixed to 14 octets. The contents are filled starting from the most significant octet. Each octet shall be encoded as specified for the chosen character set, as defined in clause 0. If the string to be transmitted is smaller then 14 octets, unused trailing octets in the character string shall be set to NULL (00h). Example: KNX is OK is encoded as follows : 4B 4E 58 20 69 73 20 4F 4B 00 00 00 00 00 Unit: Resol.: PDT: ID: 16.000 16.001 Not applicable. Not applicable. PDT_GENERIC_14 Name: DPT_String_ASCII DPT_String_8859_1 Range: See 4.001 (DPT_Char_ASCII) See 4.002 (DPT_Char_8859_1) Use: G G
Datapoint Types
3.18 Datapoint Type Scene Number

Format:
1 octet: r2U6 1 r r SceneNumber 0 0 U U U U U U PDT_GENERIC_01 Name: Encoding: Resol: Value binary encoded 1 Range: [0 63] Use: G
PDT: ID: 17.001
Datapoint Types DPT_SceneNumber SceneNumber
AS v1.5.00 - page 40 of 161
KNX Standard
Interworking
Datapoint Types
3.19 Datapoint Type DPT_SceneControl

Format:
1 octet: B1r1U6 1 CR SceneNumber
encoding
B r UUUUUU Not applicable. Not applicable. PDT_GENERIC_01 Name: DPT_SceneControl Encoding: C 0 = activate the scene corresponding to the field Scene Number 1 = learn the scene corresponding to the field Scene Number Reserved (0) Range: [0, 1] Use: G
Unit: Resol.: PDT: ID: 18.001
Datapoint Types
{0} [0 63]
Scene- Scene number Number
NOTE 5 DPT_SceneControl allows numbering the scene from 0 to 63. KNX Association recommends displaying these scene numbers in ETS, other software and controllers numbered from 1 to 64, this is, with an offset of 1 compared to the actual transmitted value.
3.20 Datapoint Type DPT_DateTime

Format:
8 octets: U8[r4U4][r3U5][U3U5][r2U6][r2U6]B16 8 MSB Year U U U U U U U U 4 0 0 Minutes 0 0 0 0 0 0 7 Month 6 0 0 0 DayOfMonth 5 DayOfHourOfDay Week
encoding octet nr. field names
r r r r U U U U 3 Seconds
r r r U U U U U U U U U U U U U 2 F WD NWD NY ND NDoW NT SUTI CLQ 1 LSB 0 0 0 0 0 0 0
encoding
r r U U U U U U PDT_DATE_TIME
r r U U U U U U B B B B B B B B B r r r r r r r
PDT:
Datapoint Types ID: 19.001 Field Year Name: DPT_DateTime Description Year Encoding Value binary encoded, offset 1900 0 = 1900 255 = 2155
Use: G Range [0255] Unit year Resol.: 1 year
AS v1.5.00 - page 41 of 161
KNX Standard
Field Month Description Month
Interworking
Encoding Value binary encoded 1 = January 12 = December Value binary encoded 1 = 1st day 31 = 31st day Value binary encoded 0 = any day 1 = Monday 7 = Sunday Value binary encoded. Value binary encoded. Value binary encoded. 0 = Normal (No fault) 1 = Fault 0 = Bank day (No working day) 1 = Working day 0 = WD field valid 1 = WD field not valid 0 = Year field valid 1 = Year field not valid 0 = Month and Day of Month fields valid 1 = Month and Day of Month fields not valid 0 = Day of week field valid 1 = Day of week field not valid 0 = Hour of day, Minutes and Seconds fields valid 1 = Hour of day, Minutes and Seconds fields not valid Range [112]
Datapoint Types
Unit Month Resol.: 1 month
DayOfMonth
[131]
none
none
DayOfWeek
Day of week
[07]
none
none
HourOfDay Minutes Seconds F WD NWD NY ND
Hour of day Minutes Seconds Fault Working Day No WD No Year No Date
[024] [059] [059] {0,1} {0,1} {0,1} {0,1} {0,1}
h min s none none none none none
1h 1 min 1s none none none none none
NDOW NT
No Day of Week No Time
{0,1} {0,1}
none none
none none
SUTI CLQ
Standard Summer 0 = Time = UT+X Time 1 = Time = UT+X+1 Quality of Clock 0 = clock without ext. sync signal 1 = clock with ext. sync signal
{0,1} {0,1}
none none
none none
3.20.1 Notes
Note 6 The year is encoded on 8 bits instead as on 7 bits as in DPT_Date. This encoding is taken from the BACnet standard. Note 7 The encoding of the hour is within the range [024] instead of [023]. When the hour is set to "24", the values of octet 3 (Minutes) and 2 (Seconds) have to be set to zero. Messages with invalid values ("Hour = 24", Minutes and Seconds not zero) have to be ignored by the receiver. Explanation: for normal clock information the range 0 23 would certainly be sufficient. But this Datapoint Type will also be used to encode e.g. schedule programs. In daily schedule programs usually "end of day" is encoded as 24:00:00 and not 23:59:59; otherwise there would be a 1 s "break" at midnight.
KNX Standard
Interworking
Datapoint Types
Example: comfort temperature level from 07:00 ... 24:00. Without the value 24:00:00 there is a problem to differentiate between a full 24 h period and a 0 h period. Examples: A daily program with 24 h comfort level is encoded as "start comfort: 00:00:00" and "end of comfort: 24:00:00". A daily program with 0 h comfort level ( all day economy level) is encoded as "start comfort: 00:00:00" and "end of comfort: 00:00:00".
Note 8 "Fault" is set if one ore more supported fields of the Date&Time information are corrupted. This is not the same as when the NY, ND, NW etc. attributes would be set (in this case the corresponding fields are not supported). "Fault" is set e.g. after power-down, if battery backup of the clock was not sufficient after 1st start-up of the device (clock unconfigured) radio-clock (DCF 77) had no reception for a very long time
"Fault" is usually cleared automatically by the device (producer) if the local clock is set or clock data is refreshed by other means (e.g. by reception of system clock message, reception of DCF 77 radio message etc.). The receiver (e.g. a room unit, MMI) will interpret Date&Time with "Fault" as corrupted and will either ignore the message or show --:--:-- or blinking 00:00:00 (as known from Video recorders after power-up). Note 9 SUTI is only an attribute for information / visualisation. In the hour field, summer-time correction is already considered. Therefore no hour offset shall be added by the receiver if SUTI is set. SUTI = 0 SUTI = 1 Note 10 NDoW = 1 means that the Day of Week-field ddd is invalid and the ddd information shall be ignored. A Clock not supporting Day of Week information shall set NdoW = 1. means that the ddd-field is valid and that ddd is a wildcard. This encoding feature is thought for use in for instance scheduling information. standard time summer daylight saving time
NDoW = 0 and ddd = 0 Note 11
Bit 7 of the octet 1 is used for Quality of Clock bit (CLQ). The other bits of this octet are reserved for future extensions. Their values shall be 0. If this Datapoint Type is used for transmitting data, transmitters shall set the lower 7 bits to 0. Receivers shall check these bits to be 0. This bit is called Quality of Clock (CLQ). Encoding 0: 1: Clock without an external synchronisation signal. The device sending date&time information has a local clock, which can be inaccurate ! Clock with an external synchronisation signal (like DCF77, videotext, etc.). The device sending date & time information sends signals which are synchronised (time to time) with external date & time information. The default value is 0.
KNX Standard
Interworking
Datapoint Types
Also an externally synchronised clock should send CLQ = 0 after start-up (until reception of first synchronisation signal) or after a synchronisation timeout. The Quality of Clock bit (CLQ) is used in datagrams transmitting date&time information during runtime. In the FB System Clock, CLQ information is used for resolution of system clock master conflicts: a system clock master sending CLQ = 1 displaces a system clock master sending CLQ = 0 (for further information see Chapter 7/1/1 "FB System Clock". If the Datapoint Type DPT_DateTime is used for parameters like scheduler information, use of this information bit makes no sense, CLQ bit should be set to 0.
3.21 Datapoint Types N8

Format:
1 octet: N8 1 field1 NNNNNNNN
Encoding: Encoding absolute value N = [0 255] Unit: Resol.: PDT: none none PDT_ENUM8 (alt: PDT_UNSIGNED_CHAR)
Datapoint Types ID: 20.001 Name: DPT_SCLOMode Encoding: field1 = SCLOMode 0 = autonomous 1 = slave 2 = master 3 255 not used; reserved field1 = BuildingMode 0 = Building in use 1 = Building not used 2 = Building protection field1 = OccMode 0 = occupied 1 = standby 2 = not occupied 3 255 not used; reserved field1 = Priority 0 is highest priority 0 = High 1 = Medium 2 = Low 3 = void 4 255 not used; reserved Range: [0 3] Use: FB
20.002
DPT_BuildingMode 11)
[0 3]
20.003
DPT_OccMode 12)
[0 3]
20.004
DPT_Priority 13)
[0 3]
FB
11) 12)
Same as DPT_BuildingMode_Z (201.107), but without Status/Command field. Same as DPT_OccMode_Z (201.108), but without Z8 field.
KNX Standard
Datapoint Types ID: 20.005 Name: DPT_LightApplicationMode
Interworking
Datapoint Types
Encoding: field1 = Application Mode 0 = normal 1 = presence simulation 2 = night round 3 16 = reserved 17 255 = manufacturer specific
Range: [0 3]
Use: FB
20.006
DPT_ApplicationArea 14)
field1 = ApplicationArea {0, 1, 10, 11, 0 = no fault 12, 13, 14} 1 = system and functions of common interest 29 = reserved 10 = HVAC general FBs 11 = HVAC Hot Water Heating 12 = HVAC Direct Electrical Heating 13 = HVAC Terminal Units 14 = HVAC VAC 15 19 = reserved (HVAC) 20 = Lighting 21 29 = reserved (Lighting) 30 = Security 31 39 = reserved (Security) 40 = Load Management 41 49 = reserved (Load Management) 50 = Shutters and blinds other values = reserved, shall not be used field1 = AlarmClassType 0 = reserved (not used) 1 = simple alarm 2 = basic alarm 3 = extended alarm 4 255 = reserved, shall not be used [0 3]
FB
20.007
DPT_AlarmClassType
FB
20.008
DPT_PSUMode
field1 = PSUMode [0 2] 0 = disabled (PSU/DPSU fixed off) 1 = enabled (PSU/DPSU fixed on) 2 = auto (PSU/DPSU automatic on/off) 3 255 = reserved, shall not be used
System
13) 14)
This Datapoint Type is used for parameters, not for runtime interworking. It is used e.g. to define the alarm priority of a configurable digital alarm input in a device. This coding corresponds to the numbering of parts in Volume 7 of KNX System Specification.
KNX Standard
Datapoint Types ID: 20.011 Name: DPT_ErrorClass_System
15)
Interworking
Datapoint Types
Encoding:
Range:
Use: FB
field1 = ErrorClass_System [0 18] 0 = no fault 1 = general device fault (e.g. RAM, EEPROM, UI, watchdog, ) 2 = communication fault 3 = configuration fault 4 = hardware fault 5 = software fault 6 = insufficient non volatile memory 7 = insufficient volatile memory 8 = memory allocation command with size 0 received 9 = CRC-error 10 = watchdog reset detected 11 = invalid opcode detected 12 = general protection fault 13 = maximal table length exceeded 14 = undefined load command received 15 = Group Address Table is not sorted 16 = invalid connection number (TSAP) 17 = invalid Group Object number (ASAP) 18 = Group Object Type exceeds (PID_MAX_APDU_L ENGTH 2) 19 255 = reserved, shall not be used field1 = AlarmClass_HVAC 0 = no fault 1 = sensor fault 2 = process fault / controller fault 3 = actuator fault 4 = other fault 5 255 = reserved, shall not be used [0 4]
20.012
DPT_ErrorClass_HVAC
16)
FB
15) 16)
This encoding is already used in FB Technical Alarm. This encoding is already used in FB Technical Alarm.
KNX Standard
Datapoint Types ID: 20.013 Name: DPT_Time_Delay (from PART_Time_Delay)
Interworking
Datapoint Types
Encoding: field1 = TimeDelay 0 = not active 1 =1s 2 =2s 3 =3s 4 =5s 5 = 10 s 6 = 15 s 7 = 20 s 8 = 30 s 9 = 45 s 10 = 1 min 11 = 1,25 min 12 = 1,5 min 13 = 2 min 14 = 2,5 min 15 = 3 min 16 = 5 min 17 = 15 min 18 = 20 min 19 = 30 min 20 =1h 21 =2h 22 =3h 23 =5h 24 = 12 h 25 = 24 h 26 255 = reserved, shall not be used field1 = Wind Force Scale 0 = calm (no wind) 1 = light air 2 = light breeze 3 = gentle breeze 4 = moderate breeze 5 = fresh breeze 6 = strong breeze 7 = near gale / moderate gale 8 = fresh gale 9 = strong gale 10 = whole gale / storm 11 = violent storm 12 = hurricane 13 to 255 = reserved field1 = SensorSelect 0 = inactive 1 = digital input not inverted 2 = digital input inverted 3 = analog input -> 0 % to 100% 4 = temperature sensor input
Range: [0 25]
Use: FB
20.014
DPT_Beaufort_Wind_Force _Scale
[0 12]
20.017
DPT_SensorSelect
[0 4]
AS v1.5.00 - page 47 of 161
KNX Standard
Interworking
Datapoint Types
3.22 Datapoint Type B8

3.22.1 Datapoint Type General Status
Format:
1 octet: Z8 1 Attributes b7b6b5b4b3b2b1b0
encoding
bbbbbbbb (not applicable) PDT_BITSET8 Name: DPT_StatusGen (alt: PDT_GENERIC_01) Encoding: See below Range: See below Encoding 0 = 1 = 0 = 1 = 0 = 1 = 0 = 1 = 0 = 1 = NA false true false true false true false true false true Unit none none none none none NA Use: G Range {0,1} {0,1} {0,1} {0,1} {0,1} NA
Resol.: PDT: ID: 21.001
Datapoint Types
Data fields Attributes - OutOfService - Fault - Overridden - InAlarm - AlarmUnAck - reserved
Description Bit b0 corresponding Datapoint value is out of service b1 corresponding Datapoint Main value is corrupted due to a failure b2 corresponding Datapoint Main value is overridden b3 corresponding Datapoint is in alarm b4 b5, b6, b7 alarm status of corresponding Datapoint is not acknowledged reserved, set 0
Standard mode: This DPT represents the STATUS information of the LTE Z8 information. In the LTE model, the Z8 field is always combined with a Datapoint main value (together thus building a compound structure). If in Standard Mode DPT_StatusGen is used, the corresponding Datapoint is always additional information to another Datapoint that represents the main value. EXAMPLE Datapoint 1: temperature sensor value with DPT_Value_Temp Datapoint 2: additional status of Datapoint 1 with DPT_StatusGen The 2 Datapoints Main value and Status value cannot be transmitted simultaneously. Therefore inconsistencies between the Main value and the Status information may occur. The Status information is mainly used for visualisation. Restriction: Only the STATUS part of the Z8 information can be transmitted. Execution of the Z8 COMMAND feature is not possible in Standard Mode.
Please refer as well to the description of STATUS/COMMAND Z8 in clause 4.1.
AS v1.5.00 - page 48 of 161
KNX Standard
Interworking
Datapoint Types
3.22.2 Datapoint Type Device Control

Format:
1 octet: B8 1 DeviceControl b7b6b5b4b3b2b1b0
encoding
bbbbbbbb
Encoding: See below Range:: Unit: Resol.: PDT: ID: 21.002 Bit b0 b1 b2 See below none (not applicable) PDT_BITSET8 Name: DPT_Device_Control Data fields - UserStopped - OwnIA - VerifyMode (alt: PDT_GENERIC_01) Encoding, range: See below Use: System: PID_DEVICE_CONTROL Encoding 0 = false 1 = true 0 = false 1 = true 0 = false 1 = true NA Unit none none none NA Range {0,1} {0,1} {0,1} NA
Datapoint Types
Description The user application is stopped. A datagram with the own Individual Address as Source Address has been received Verify Mode is on. reserved, set 0
b3b7 - Reserved
AS v1.5.00 - page 49 of 161
KNX Standard
Interworking
Datapoint Types

Format:
2 bit: N2 1 s NN None (not applicable) PDT_ENUM8 (alt: PDT_UNSIGNED_CHAR)
Unit: Resol.: PDT:
Datapoint Types ID: 23.001 Name: DPT_OnOffAction Range: [00b11b] Use: Encoding: FB s 00b = off 01b = on 10b = off/on 11b = on/off FB s 00b = no alarm is used 01b = alarm position is UP 10b = alarm position is DOWN (11b = reserved; shall not be used) FB s 00b = Up 01b = Down 10b = UpDown 11b = DownUp
23.002
DPT_Alarm_Reaction [00b10b]
23.003
DPT_UpDown_Action [00b11b]
AS v1.5.00 - page 50 of 161
KNX Standard
Interworking
Datapoint Types
3.24 Datapoint Type DPT_VarString_8859_1

Format: variable length: A[n] N MSB A ... 1 LSB 00
Encoding: This Datapoint Type shall be used to transmit strings of textual characters. The length is not fixed, but variable; the string shall be terminated by a single character NULL (00h). No length information shall be transmitted in the APDU a). Handling non-supported lengths: Data Link Layer: neglect the frame Application Layer: cut to the maximum supported length, keeping the characters at the beginning, i.e. starting with the MSB. Interface Object Server The implicit array strucure of a property value of an Interface Object property can be used to store multiple strings. Every array element shall contain exactly one string. These array elements can have a different length. The APDU's used to read/write these strings shall only contain entire strings; exactly one NULL-character shall appear between string elements and at the end of the last string 17). This means that strings that do not fit in the supported array length shall not be cut off. If a property value is read which would lead to an APDU longer than the length supported by the server, the server shall respond with a negative response; i.e. the APDU shall not be limited to the number of elements that does fit it, but instead contain no property value data. The client can then read a smaller number of array elements. Each character shall be encoded according ISO 8859-1. Example: KNX is OK is encoded as follows : 4Bh 4Eh 58h 20h 69h 73h 20h 4Fh 4Bh 00h Example: This format allows transmission of very long strings! is encoded as follows : 54h 68h 69h 73h 20h 66h 6Fh 72h 6Dh 61h 74h 20h 61h 6Ch 6Ch 6Fh 77h 73h 20h 74h 72h 61h 6Eh 73h 6Dh 69h 73h 73h 69h 6Fh 6Eh 20h 6Fh 66h 20h 76h 65h 72h 79h 20h 6Ch 6Fh 6Eh 67h 20 73h 74h 72h 69h 6Eh 67h 73h 21h 00h Unit: PDT: Datapoint Types ID: 24.001
a)
Not applicable.
Name: DPT_VarString_8859_1
Range Acc. DPT 4.002 (DPT_Char_8859_1)
Usage: General
Length information is implicitly in the frame (by the Data Link Layer)
17)
The NULL character is actually part of the DPT_VarString_8859_1 format.

KNX Standard
Interworking
Datapoint Types
3.25 Datapoint Type DPT_SceneInfo

Format:
1 octet: r1B1U6 1 RB SceneNumber
encoding
0 b UUUUUU
Encoding: All values binary encoded. Range: Unit: Resol.: PDT: ID: 26.001 See below. Not applicable. Not applicable. PDT_GENERIC_01 Name: DPT_SceneInfo Encoding: r B Reserved (0) info: 0 = scene is active 1 = scene is inactive Scene number Range: none [0, 1] Use: G
Datapoint Types
SceneNumber
[0 63]
NOTE 12 DPT_SceneInfo allows numbering the scene from 0 to 63. KNX Association recommends displaying these scene numbers in ETS, other software and controllers numbered from 1 to 64, this is, with an offset of 1 compared to the actual transmitted value.
AS v1.5.00 - page 52 of 161
KNX Standard
Interworking
Datapoint Types
3.26 Datatype B32

3.26.1 Datapoint Type Combined Info On Off
Format:
4 octets: B32 4 MSB 3 2 1 LSB
Encoding: Value of all fields binary coded Range: Unit: Resol.: PDT: ID: All fields: {0, 1} Not applicable. Not applicable. PDT_GENERIC_04 Name: Use: General a)
Datapoint Types 27.001 DPT_CombinedInfoOnOff a) This DPT shall only be used for status outputs. Datafields s0 s1 s2 s3 s4 s5 s6 s7 s8 s9 s10 s11 s12 s13 s14 s15 Bit # 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Description Info On Off Output 1 Info On Off Output 2 Info On Off Output 3 Info On Off Output 4 Info On Off Output 5 Info On Off Output 6 Info On Off Output 7 Info On Off Output 8 Info On Off Output 9 Info On Off Output 10 Info On Off Output 11 Info On Off Output 12 Info On Off Output 13 Info On Off Output 14 Info On Off Output 15 Info On Off Output 16
m15 m14 m13 m12 m11 m10 m9 m8 m7 m6 m5 m4 m3 m2 m1 m0 s15 s14 s13 s12 s11 s10 s9 s8 s7 s6 s5 s4 s3 s2 s1 s0
BBBBBBBB BBBBBBBB BBBBBBBB BBBBBBBB
Encoding 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On 0 = output state is Off 1 = output state is On
AS v1.5.00 - page 53 of 161
KNX Standard
Datafields m0 Bit # 16
Interworking
Description Mask Bit Info On Off Output 1
Datapoint Types
Encoding 0 = output state is not valid 1 = output state is valid m1 17 Mask Bit Info On Off Output 2 0 = output state is not valid 1 = output state is valid m2 18 Mask Bit Info On Off Output 3 0 = output state is not valid 1 = output state is valid m3 19 Mask Bit Info On Off Output 4 0 = output state is not valid 1 = output state is valid m4 20 Mask Bit Info On Off Output 5 0 = output state is not valid 1 = output state is valid m5 21 Mask Bit Info On Off Output 6 0 = output state is not valid 1 = output state is valid m6 22 Mask Bit Info On Off Output 7 0 = output state is not valid 1 = output state is valid m7 23 Mask Bit Info On Off Output 8 0 = output state is not valid 1 = output state is valid m8 24 Mask Bit Info On Off Output 9 0 = output state is not valid 1 = output state is valid m9 25 Mask Bit Info On Off Output 10 0 = output state is not valid 1 = output state is valid m10 26 Mask Bit Info On Off Output 11 0 = output state is not valid 1 = output state is valid m11 27 Mask Bit Info On Off Output 12 0 = output state is not valid 1 = output state is valid m12 28 Mask Bit Info On Off Output 13 0 = output state is not valid 1 = output state is valid m13 29 Mask Bit Info On Off Output 14 0 = output state is not valid 1 = output state is valid m14 30 Mask Bit Info On Off Output 15 0 = output state is not valid 1 = output state is valid m15 31 Mask Bit Info On Off Output 16 0 = output state is not valid 1 = output state is valid If one or more output bits are not used or the output states are not valid then the assigned mask bits of this outputs shall be set to the value = 0.
AS v1.5.00 - page 54 of 161
KNX Standard
Usage requirements
Interworking
Datapoint Types
This DPT may only be used for encoding the combined binary output information of a multiple channel binary actuator. It avoids the bus load that is caused by individual single bit state outputs, certainly in case of simultaneous changes (e.g. all off).
Multi Channel Binary Sensor
Conventional Switch / Push Button Switch On Off
DPT_Switch
Switch On Off Info On Off
Channel 1
Multi Channel Binary Actuator

DPT_Switch
(number of channels<=16)
Channel 2
DPT_Switch
Channel n 3
DPT_Switch
Channe4
DPT_Switch
Channel 5
DPT_Switch
Channel n (<=16)
Visualisation (e.g. DISPLAY)
Info On Off
Combined Info On Off
Info On Off Info On Off Info On Off Info On Off Info On Off
AS v1.5.00 - page 55 of 161
KNX Standard
Interworking
Datapoint Types
3.27 Datapoint Type Unicode UTF-8 String A[n]

3.27.1 DPT_UTF-8
Format: A[n] N MSB A ... 1 LSB 00
Encoding: This Datapoint Type shall be used to transmit Unicode strings, whereas the UTF-8 encoding scheme shall be used for Unicode Transformation to data contents for transmission. The data length for one character is variable from 1 octet to 4 octets. Each character shall be encoded according Unicode Transformation Format UTF-8: Char. number range (hexadecimal) U+0000 U+007F U+0080 U+07FF U+0800 U+FFFF U+10000 U+10FFFF UTF-8 octet sequence (binary) 0xxxxxxx 110xxxxx 10xxxxxx 1110xxxx 10xxxxxx 10xxxxxx 11110xxx 10xxxxxx 10xxxxxx 10xxxxxx Remark ASCII equivalent range; octet begins with zero 1st octet begins with 110, the second octet begins with 10. 1st octet begins with 1110, the following octets begin with 10. 1st octet begins with 11110, the following octets begin with 10.
For more information about Unicode please refer to www.unicode.org. The code charts are listed there under http://www.unicode.org/charts/. For more information about UTF-8 please refer to www.ietf.org / http://www.ietf.org/rfc/rfc3629.txt. Using UTF-8 the data length for a string (multiple characters) is also not fixed, but variable. The string shall be terminated by the NULL- character (00h). No length information shall be transmitted in the APDU a. Handling of non-supported lengths: Data Link Layer: neglect the frame Application Layer: cut to the maximum supported length, keeping the characters at the beginning, i.e. starting with the MSB. Interface Object Server The implicit array structure of a Property Value of an Interface Object Property can be used to store multiple strings. Every array element shall contain exactly one string. These array elements can have a different length. The APDUs used to read/write these strings shall only contain entire strings; exactly one NULL character shall appear between string elements and at the end of the last string. This means that strings that do not fit in the supported array length shall not be cut off. If a Property Value is read that would lead to an APDU longer than the length supported by the server, the server shall respond with a negative response; i.e. the APDU shall not be limited to the number of elements that does fit it, but instead contain no Property Value data. The client can then read a smaller number of array elements. Range: Unit:
a
U+000000 U+10FFFF (220+216)
None Length information is implicitly in the frame (by the Data Link Layer) b When writing about a Unicode character, it is normal to write "U+" followed by a hexadecimal number indicating the character's code point. For code points in the Basic Multilingual Plane (BMP), four digits are used; for code points outside the BMP, five or six digits are used, as required.
AS v1.5.00 - page 56 of 161
KNX Standard
Datapoint Types ID: 28.001 Name: DPT_UTF-8 Range
Interworking
Datapoint Types
Usage:
20 16
U+0000 U+10FFFF (2 +2 )
General
UTF-8 UTF-8 stands for Unicode Transformation Format-8. It is an octet (8 bit) lossless encoding of Unicode characters. UTF-8 is standardized as RFC 3629 / STD 63 (2003), which establishes UTF-8 as a standard Internet Protocol element. UTF-8 uses one to four octets per character, depending on the Unicode symbol. Only one octet is needed to encode the 128 US-ASCII characters (Unicode range U+0000 to U+007F). Two octets are needed for Latin letters with diacritics, combining diacritics and for Greek, Cyrillic, Armenian, Hebrew, Arabic, Syriac and Thanna (Unicode range U+0080-U+07FF). Three octets are needed for the rest of the Basic multilingual plane (which contains virtually all characters in common use). Four octets are needed for characters in other planes of Unicode. Four octets may seem like a lot for one character (code point). However code points outside the Basic Multilingual Plane are generally very rare. Furthermore, UTF-16 (the main alternative to UTF-8) also needs four octets for these code points. Whether UTF-8 or UTF-16 is more efficient depends on the range of code points being used. In UTF-8, characters from the range U+0000 to U+10FFFF (the UTF-16 accessible range) are encoded using sequences of 1 to 4 octets. The only octet of a "sequence" of one has the higher-order bit set to 0, the remaining 7 bits being used to encode the character number. In a sequence of n octets, n > 1, the initial octet has the n higher-order bits set to 1, followed by a bit set to 0. The remaining bit(s) of that octet contain bits from the number of the character to be encoded. The following octet(s) all have the higher-order bit set to 1 and the following bit set to 0, leaving 6 bit in each to contain bits from the character to be encoded. The table below summarizes the format of these different octet types. The letter x indicates bits available for encoding bits of the character number.
Char. number range (hexadecimal) U+0000 U+007F U+0080 U+07FF U+0800 U+FFFF U+10000 U+10FFFF UTF-8 octet sequence (binary) 0xxxxxxx 110xxxxx 10xxxxxx 1110xxxx 10xxxxxx 10xxxxxx 11110xxx 10xxxxxx 10xxxxxx 10xxxxxx
AS v1.5.00 - page 57 of 161
KNX Standard
Interworking
Datapoint Types
3.28 Datapoint Types V64

3.28.1 DPTs for electrical energy
Format:
octet nr field names encoding octet nr field names encoding
8 octets: V64 8 MSB 7 SignedValue VVVVVVVV 4 VVVVVVVV 3 SignedValue VVVVVVVV VVVVVVVV VVVVVVVV VVVVVVVV VVVVVVVV 2 VVVVVVVV 1 LSB 6 5
Twos complement notation SignedValue = [9 223 372 036 854 775 808 to 9 223 372 036 854 775 807] PDT_GENERIC_08
Datapoint Types ID: 29.010 29.011 29.012

a
Name: DPT_ActiveEnergy_V64 DPT_ApparantEnergy_V64 DPT_ReactiveEnergy_V64
Range: -9 223 372 036 854 775 808 Wh to 9 223 372 036 854 775 807 Wh -9 223 372 036 854 775 808 VAh to 9 223 372 036 854 775 807 VAh -9 223 372 036 854 775 808 VARh to 9 223 372 036 854 775 807 VARh
Unit: Wh VAh
Resol.: 1 Wh 1 VAh
Use: Ga Ga
VARh 1 VARh G a
Any Datapoint shall only be encoded with format V64 according either DPT_ActiveEnergy_V64, DPT_ApparantEnergy_V64 or DPT_ ReactiveEnergy_V64 if also a Datapoint with the V32 encoding according either DPT_ActiveEnergy, or DPT_ApparantEnergy or DPT_ReactiveEnergy respectively is implemented. No DPT with encoding V64 shall be encoded unless also a DP with the V32 and same unit and resolution is encoded.
AS v1.5.00 - page 58 of 161
KNX Standard
Interworking
Datapoint Types
3.29 Datapoint Type DPT_AlarmInfo

Format:
6 octets: U8N8N8N8B8B8
6 MSB LogNumber 5 AlarmPriority 4 ApplicationArea 3 ErrorClass 2 Attributes
encoding octet nr. field names
UUUUUUUU NNNNNNNN NNNNNNNN NNNNNNNN 0 0 B B B B B B 1 LSB AlarmStatusAttributes 0 0 0 0 0 BBB not applicable not applicable PDT_ALARM_INFO (alt: PDT_GENERIC_06) Range: Log Number Alarm Priority See DPT_Priority. 3 priorities 0 = highest priority; for no priority, 03h is used (=void) Application Area Error Class attributes: 0 = False, 1 = True 0 = False, 1 = True 0 = False, 1 = True 0 = False, 1 = True Fixed to 0 Alarm Status (attributes) 0 = False, 1 = True 0 = False, 1 = True 0 = False, 1 = True Fixed to 0 Use:
octet nr.
Encoding: binary encoded values Unit: Resol.: PDT: ID:
Datapoint Types Name: Encoding: 219.001 DPT_AlarmInfo LogNumber: U8 AlarmPriority: N8 [0 255] FBs Alarm [0 2] Source, Alarm Sink
ApplicationArea: N8 ErrorClass: N8 Attributes: B8 - B0: Ack_Sup - B1: TimeStamp_Sup - B2: AlarmText_Sup - B3: ErrorCode_Sup - B4 B7: reserved AlarmStatusAttributes: B8 - B0: InAlarm - B1: AlarmUnAck - B2: Locked - B3 B7: reserved
see Note 4 see Note 5 Boolean {0, 1} {0, 1} {0, 1} {0, 1} {0, 1} {0, 1} {0, 1} -
Note 1 Alarm messages contain an Application area information to allow filtering of alarm messages in subsystems. Coding of Application Areas see Note 4. Note 2 Examples of (HVAC) Alarm messages of different companies showed that many alarm informations are company specific and only more neutral error classes can be standardised. Company specific additional information (if necessary) is possible, e.g. in additional Datapoints. Examples of such additional Datapoints are timestamp and AlarmText_Log in this specification document.
KNX Standard
Note 3
Interworking
Datapoint Types
B0 in attributes field (Ack_Sup) indicates whether the alarm is a simple error which can never be acknowledged (0) or an alarm with acknowledge and/or alarm reset mechanism (1). If it is a simple error without acknowledge: the alarm source sends acknowledged (bit AlarmUnAck = 0) as status information in the alarm state attributes. Note 4 Coding of Application Area (Enumeration):
Code a) 0 1 29 10 11 12 13 14 15 19 20 21 ..29 30 31 39 50 255
a)
Application Area no fault System & functions of common interest reserved HVAC General FBs HVAC Hot Water Heating HVAC Direct Electrical Heating HVAC Terminal Units HVAC VAC reserved (HVAC) Lighting reserved (Lighting) Security reserved (Security) Shutters & Blinds not used
This coding corresponds to the numbering of parts in Volume 7 of KNX System Specification.
Faults in functions of common interest (Functional Blocks according to Part 7/1) shall be mapped to the application area System, e.g. a multiple system clock master conflict is a configuration fault (see error class coding in Note 6) within application area system. KNX Association Working Group Interworking is responsible for definition of additional application area codes. Note 5 Responsibility for Definition of Error Class Codes within the Application Areas is in the scope of the KNX Association Application Specification Groups. KNX Association Working Group Interworking is responsible for definition of the Error Class Codes within the Application Area System. Note 6 of this document contains the error class coding within application area system as a proposal to the HVAC ASG. Note 7 of this document contains an error class coding within HVAC as a proposal to the HVAC ASG.
AS v1.5.00 - page 60 of 161
KNX Standard
Interworking
Datapoint Types
Note 6- Technical Alarm Error Class Coding within Application Area System
Code 0 1 2 3 4 5 6 255 Error Class no fault general device fault (e.g. RAM, EEPROM, UI, Watchdog, ) communication fault configuration fault HW fault SW fault not used not used not used
Faults in functions of common interest (Functional Blocks according to Vol. 7-1) should be mapped to the application area System, e.g. a multiple system clock master conflict is a configuration fault. KNX Association Working Group Interworking is responsible for definition of additional error class codes within application area system. Examples: Detection of two devices with same individual address causes a configuration fault. Detection of a multiple system clock master conflict (without automatic resolution) causes a configuration fault. Detection of failure of a (formerly present) communication partner causes a communication faul.t Timeout detection on the System Clock Signal (heartbeat) causes a communication fault. Note 7 - Technical Alarm Error Class Coding within HVAC Application Area(s)
Code 0 1 2 3 4 5 255 Error Class no fault sensor fault process fault /controller fault actuator fault other faults not used not used not used
The coding above is a proposal and has to be approved by the HVAC Application Specification Group. The HVAC ASG is also responsible for definition of additional error class codes within 'HVAC application area(s).
AS v1.5.00 - page 61 of 161
KNX Standard
Interworking
Datapoint Types
3.30 Datapoint Type DPT_SerNum

Format:
octet nr. field names encoding octet nr. field names encoding
6 octets: N16U32 6 MSB 5
ManufacturerCode NNNNNNNN NNNNNNNN 4 3 2 1 LSB
IncrementedNumber UUUUUUUU UUUUUUUU UUUUUUUU UUUUUUUU
Encoding: ManufacturerCode, IncrementedNumber: binary encoded Range: Unit: Resol.: PDT: ID: 221.001 ManufacturerCode: IncrementedNumber: none not applicable PDT_GENERIC_06 Name: DPT_SerNum Range: See above. Unit: See above. Resol.: See above. Use: G [0 65 535] [0 4 294 967 295]
Datapoint Types
IncrementedNumber shall be incremented with each BAU. The owner of the microcontroller shall ensure the global uniqueness of the leading 4 octets within the specific manufacturers code space.
3.31 Datapoint Types Unsigned Relative Value

LTE: compound structure
Format:
2 octets: U8Z8 2 MSB RelValue 1 LSB Status Command
encoding
UUUUUUUU Z Z Z Z Z Z Z Z PDT_GENERIC_02
PDT:
Datapoint Types ID: 202.001 Name: DPT_RelValue_Z Description Unsigned relative value Encoding U8 Z8 Unit % none Range 0 % 255 % none Resol. 1% none Use: G
Data fields RelValue
Status/Command standard Status/Command
AS v1.5.00 - page 62 of 161
KNX Standard
Standard Mode
Interworking
Datapoint Types
Datapoint Type 202.001 shall in Standard Mode be encoded as a percentage value without the Z8 field. The actually used DPT depends on the Datapoint and shall be defined in the Datapoint specification in the Functional Block. Multiple solutions are possible. Solution B) is preferred because there is no mapping of the % value. A) DPT_Scaling (5.001) Encoding: 0 %100 %. Full Datapoint Type value: 0 255, i.e. 1 % = value 255/100 ! To be used for valve position control in order to be backwards compatible with EIB valves. B) DPT_Percent_U8 (5.004) Encoding: 0 %255 %. Full Datapoint Type value: 0 255, i.e. 1 % = value 1. To be used for % energy demand etc. C) DPT_Value_Humidity (9.0xx) float F16 encoding To be used for air humidity only.
3.32 Datapoint Types Unsigned Counter Value

Format:
2 octets: U8Z8 2 MSB CounterValue 1 LSB Status Command
encoding
UUUUUUUU Z Z Z Z Z Z Z Z PDT_GENERIC_02
PDT:
Datapoint Types ID: 202.002 Name: DPT_UCountValue8_Z Description Unsigned counter value standard Status/Command Encoding U8 Z8 Unit none none Range 0 255 none Use: G Resol. 1 none
Data fields CounterValue Status/Command
Standard Mode DPT_Value_1_Ucount (DPT_ID = 5.010), this is, only the field CounterValue without the Z8 field.
AS v1.5.00 - page 63 of 161
KNX Standard
Interworking
Datapoint Types
3.33 Datapoint Types Time Period..._Z

Format:
3 octets: U16Z8 3 MSB TimePeriod 2 LSB 1 Status Command
encoding
UUUUUUUU UUUUUUUU Z Z Z Z Z Z Z Z
Encoding: TimePeriod: Values shall be binary coded. Status/Command: Z8 PDT: PDT_GENERIC_03 Datapoint Types ID: 203.002 203.003 203.004 203.005 203.006 203.007 Name: DPT_TimePeriodMsec_Z DPT_TimePeriod10Msec_Z DPT_TimePeriod100Msec_Z DPT_TimePeriodSec_Z DPT_TimePeriodMin_Z DPT_TimePeriodHrs_Z Description Unsigned time value standard Status/Command Range: 0 ms 65 535 ms 0 s 655,35 s 0 s 6 553,5 s 0 s 65 535 s Unit: ms ms ms ( 18,2 hours) s Resol.: 1 ms 10 ms 100 ms 1s 1 min 1h Use: G G G G G G
0 min 65 535 min ( 45,5 days) min 0 h 65 535 h ( 7,4 years) h
Data fields TimePeriod Status/Command
Standard Mode DPT_TimePeriod... (7.002 ... 7.007), only TimePeriod without Z8 field.
AS v1.5.00 - page 64 of 161
KNX Standard
Interworking
Datapoint Types
3.34 Datapoint Types Unsigned Flow Rate l/h

Format:
3 octets: U16Z8 3 MSB FlowRate 2 LSB 1 Status Command
encoding
UUUUUUUU UUUUUUUU Z Z Z Z Z Z Z Z
Encoding: FlowRate: U16 (Values shall be binary coded). Status/Command: Z8 PDT: PDT_GENERIC_03 Datapoint Types ID: 203.011 Name: DPT_UFlowRateLiter/h_Z Description flow rate Encoding U16 Z8 Unit l/h none Range 0 l/h 655,35 l/h none Use: G Resol. 0,01 l/h none
Data fields FlowRate
Status/Command standard Status/Command
In case of a detected sensor failure the Status Flag Fault shall be set. This is a mandatory feature of this DPT. In this case in addition the reason of Fault may be encoded in the FlowRate field (optional feature): see standard Z8 mechanism in 4.1.2. Standard Mode DPT_Value_Volume_Flux (14.077), without Z8 field.
3.35 Datapoint Types Unsigned Counter Value

Format:
3 octets: U16Z8 3 MSB 2 LSB 1 Status Command
CounterValue
encoding
UUUUUUUU UUUUUUUU Z Z Z Z Z Z Z Z PDT_GENERIC_03
PDT:
Datapoint Types ID: 203.012 Name: DPT_UCountValue16_Z Description Unsigned counter value Encoding value binary encoded Unit none none Range 0 65 535 none Use: G Resol.: 1 none
Data fields RelValue
Status/Command standard Status/Command Z8
AS v1.5.00 - page 65 of 161
KNX Standard
Standard Mode
Interworking
Datapoint Types
DPT_Value_2_Ucount (7.001), only CounterValue without Z8 field.
3.36 Datapoint Types Unsigned Electric Current A

Format:
3 octets: U16Z8 3 MSB ElCurrent 2 LSB 1 Status Command
encoding
PDT:
Datapoint Types ID: 203.013 Name: DPT_UElCurrentA_Z Description electric current value Encoding U16 Unit A none Range 0 A 655,35 A none Resol. 0,01 A none Use: G
Data fields ElCurrent
In case of a detected sensor failure the Status Flag Fault shall be set. This is a mandatory feature of this DPT. In this case in addition the reason of Fault may be encoded in the ElCurrent field (optional feature): see standard Z8 mechanism in 4.1.2. Standard Mode DPT_Value_Electric_Current (DPT_ID = 14.019), without Z8 field.
3.37 Datapoint Types Power in kW

Format:
3 octets: U16Z8 3 MSB Power 2 LSB 1 Status Command
encoding
PDT:
Datapoint Types ID: 203.014 Name: DPT_PowerKW_Z Use: G
AS v1.5.00 - page 66 of 161
KNX Standard
Interworking
Datapoint Types
Data fields Power Status/Command
Description Electrical power
Encoding U16
Unit kW none
Range 0 kW 65535 kW none
Resol. 1 kW none
standard Status/Command Z8
Standard Mode DPT_Power (DPT_ID = 9.024, format: F16) shall be used.
3.38 Datapoint Type Atmospheric Pressure with Status/Command

Format:
3 octets: U16Z8 3 MSB 2 LSB 1 Status Command
AtmPressure
encoding
PDT:
Datapoint Types ID: 203.015 Data fields Name: DPT_AtmPressureAbs_Z Description Encoding Unit mbar none Range Resol. Use: G
AtmosphericPressure Atmospheric Pressure U16 absolute value mbar Status/Command standard Status/Command Z8
0 mbar to 1200 mbar 0,05 mbar *) (and more) none none
In case of a detected sensor failure the Status Flag Fault shall be set. This is a mandatory feature of this DPT. In this case in addition the reason of Fault may be encoded in the AtmosphericPressure field (optional feature): see standard Z8 mechanism Standard Mode DPT_Value_Pres (9.006), unit Pa; only pressure value without Z8 field
NOTE -2 1 Pa = 0,01 mbar = 0,000001 bar = 1 Nm 100 Pa = 1 hPa = 1 mbar
*)
AS v1.5.00 - page 67 of 161
KNX Standard
Interworking
Datapoint Types
3.38.1 Datapoint Type DPT_PercentU16_Z

Format: 3 octet: U16Z8 3 MSB PercentValue UUUUUUUU Encoding: Range: Unit: See below See below See below 2 LSB PercentValue UUUUUUUU 1 Status Command ZZZZZZZZ
Datapoint Types ID: 203.017 Data fields PercentValue Name: DPT_PercentU16_Z Description Range: See below Unit: See below Unit / Range U16, 0,01 % resolution 0 % to 655,35 % standard Status/Command Z8 Usage: FOCI
Status/Command
Standard Mode DPT_Scaling (5.001), percent value with ~04 % resolution; without Z8 field.
3.39 Datapoint Types Signed Relative Value

Format:
2 octets: V8Z8 2 MSB RelSigned Value 1 LSB Status Command
encoding
VVVVVVVV Z Z Z Z Z Z Z Z PDT_GENERIC_02
PDT:
Datapoint Types ID: 204.001 Name: DPT_RelSignedValue_Z Description Relative signed value % Encoding V8 Unit % none Range -100 % 100 % none Use: G Resol. 1% none
Data fields RelSignedValue Status/Command
standard Status/Command Z8
Standard Mode DPT_Percent_V8 (6.001); only RelSignedValue without Z8 field.
AS v1.5.00 - page 68 of 161
KNX Standard
Interworking
Datapoint Types
3.40 Datapoint Type DeltaTime...Z

Format:
3 octets: V16Z8 3 MSB DeltaTime 2 LSB 1 Status Command
encoding
VVVVVVVV VVVVVVVV Z Z Z Z Z Z Z Z
Encoding: DeltaTime: V16 Status/Command: Z8 PDT: PDT_GENERIC_03 Datapoint Types ID: 205.002 205.003 205.004 205.005 205.006 205.007 Name: DPT_DeltaTimeMsec_Z DPT_DeltaTime10Msec_Z DPT_DeltaTime100Msec_Z DPT_DeltaTimeSec_Z DPT_DeltaTimeMin_Z DPT_DeltaTimeHrs_Z Description signed delta time value, twos complement encoding standard Status/Command Range: -32 768 ms 32 767 ms -327,68 s 327,67 s -3 276,8 s 3 276,7 s Unit: ms ms ms Resol.: 1 ms 10 ms Use: G G
100 ms G 1s 1 min 1h G G G
-32 768 s 32 767 s ( 9,1 hours) s -32 768 min ... 32 767 min( 22,7 da min -32 768 h ... 32 767 h ( 3,7 years) h
Data fields DeltaTime Status/Command
Unit / Range V16, see above Z8
Standard Mode DPT_DeltaTime...(DPT 8.002 ... 8.007), without Z8 field.
AS v1.5.00 - page 69 of 161
KNX Standard
Interworking
Datapoint Types
3.41 Datapoint Type DPT_Version

Format:
2 octet: U5U5U6 2 MSB Magic Version Number Number 1 LSB Revision Number
encoding
UUUUUUUU UUUUUUUU
Encoding: All values binary encoded. Unit: PDT: ID: 217.001 none PDT_VERSION(alt: PDT_GENERIC_02) Name: DPT_Version Use: G
Datapoint Types
Field Magic Number
Description
Encoding
Range 0 31
Resol.: 1
An increment of the Magic Number means an U5 incompatible change: no forward or backwards compatibility. This field of the version information is used for compatibility checks but it is normally not displayed (invisible). If the Magic Number is incremented the Version Number shall also be incremented (i.e. higher number). Recommendation: Start with 0. Version Number is incremented (i.e. higher number) if U5 a new version has new features. Usage: If the Magic Number is incremented, the Version Number shall be incremented as well. This shall denote an incompatible change. If the Magic Number is not incremented and the Version Number is incremented, this shall denote a backwards compatible extension. Recommendation: Start with 1. Revision Number is incremented (i.e. higher number) because of minor changes without effects on forward and backward functional compatibility between newer and older version. Recommendation: Start with 0. U6
Version Number
0 31
Revision Number
0 63
DPT_Version is the standardised encoding format of version information e.g. used for software version, hardware version, data-interface version etc. DPT_Version supports encoding of Version.Revision information and of a compatibility identifier called Magic Number. In practice the available encoding range of M.V.R 0.0.0 ... 31.31.63 is sufficient.
AS v1.5.00 - page 70 of 161
KNX Standard
EXAMPLES M.V.R. previous version 0.1.0 0.1.1 0.2.0 M.V.R. new version 0.1.1 0.2.0 1.3.0
Interworking
Datapoint Types
Meaning minor modification without effect on compatibility backwards compatible change incompatible change
Encoding of invalid version information If the version information that is transferred using DPT_Version is invalid, void or undefined, this shall be indicated by setting the values of each individual field to its maximum encodable value. Invalid version information shall thus be encoded as M.V.R. = 31.31.63. Compatibility rules Table 2 below specifies the compatibility rules.
Table 2 Compatibility rules M = = = > V = = > = R = > any value any value Compatibility compatible version minor changes without effects on forward and backward functional compatibility between previous and new version new version has new features but is still backwards compatible to the previous version (all old features are supported) combination is not allowed: in case of change of the magic number also the version number shall be incremented
any value no forward or backwards compatibility > > Legend > This field has been incremented compared to the previous version. = This field did not change compared to the previous version.
AS v1.5.00 - page 71 of 161
KNX Standard
Interworking
Datapoint Types
3.42 Datapoint Type Volume in Liter

Format:
5 octets: V32Z8 5 MSB 4 VolumeLiter 3 2 LSB 1 Status Command
VVVVVVVV VVVVVVVV VVVVVVVV VVVVVVVV Z Z Z Z Z Z Z Z PDT_GENERIC_05
PDT:
Datapoint Types ID: 218.001 Data fields VolumeLiter Name: DPT_VolumeLiter_Z Description volume in liter Encoding Unit V32 l Range -2 147 483 648 l 2 147 483 647 l Use: G Resol. 1l none
none none
Standard Mode DPT_Value_Volume (14.076), float value without Z8 field.
3.43 Datatype U16U8

3.43.1 Datapoint Type Scaling speed
Format:
3 octets: U16U8 3 MSB TimePeriod 2 1 LSB Percent
U U UU U U U U U U U U U U U U U U U U U U U U
Encoding: value of all fields binary encoded. Range:: Unit: Resol.: PDT: ID: 225.001
a)
See below. See below. See below. PDT_GENERIC_03 Name: DPT_ScalingSpeed Use:
Datapoint Types General a) Not allowed for run-time communication. This DPT shall only be used for parameters and diagnostic data or if specified as such in a FB specification.
AS v1.5.00 - page 72 of 161
KNX Standard
Data Fields TimePeriod Description
Interworking
Range [165535] Unit
Datapoint Types
Resol. 100 ms
Unsigned time-value for calculating speed. (see also DPT_TimePeriod100Msec; DPT_ID = 7.004) Unsigned percent value for calculating speed. (see also DPT_Scaling; DPT_ID = ID 5.001)
100 ms
Percent
[0,4100]
0,4 %
Examples a. Only a single Datapoint of type DPT_ScalingSpeed is used. The speed for changing the value of a Datapoint of type DPT_Scaling is constant over the whole range of DPT_Scaling.
3 MSB 00h 2 28h 1 LSB FFh
Encoded value 25 %/s
b. Two Datapoints DP0 and DP1 of type DPT_ScalingSpeed are used for two different speeds in two subranges: Rule in the FB: subrange0: speed in subrange0: subrange1: speed in subrange1:
Encoded values
DP0 3 MSB 00h 2 78h DP1 3 MSB 00h 2 14h 1 LSB FFh 1 LSB COh
0 % DP0.percentvalue DP0.percentvalue/DP0.timevalue DP0.percentvalue DP1.percentvalue (DP1.percentvalue DP0.percentvalue) / DP1.timevalue
subrange0: 0 % 75 % speed0: 6,25 %/s
subrange1: 75 % 100 % speed1: 12,5 %/s
3.43.2 Datapoint Type Scaling step time

Format:
3 octets: U16U8 3 MSB TimePeriod 2 1 LSB Percent
UU U UUUUU UU U U U U UU U UU U U U U U
Encoding: value of all fields binary encoded. PDT: ID: 225.002

a)
PDT_GENERIC_03 Name: DPT_Scaling_Step_Time Use:
Datapoint Types General a) Not allowed for run-time communication. This DPT shall only be used for parameters and diagnostic data or if specified as such in a FB specification.
AS v1.5.00 - page 73 of 161
KNX Standard
Data Fields TimePeriod Description
Interworking
Range
Datapoint Types
Unit Resol. 1 ms
Unsigned time-value (time needed for changing data point of Type DPT_Scaling by its resolution) (see also DPT_TimePeriodMsec; DPT_ID = 7.002) Range in within time-value is valid (see also DPT_Scaling; DPT_ID = ID 5.001)
[165535] ms
Percent
[0,4100] %
0,4 %
Examples a. Only a single Datapoint of type DPT_Scaling_Step_Time is used. The speed for changing the value of a Datapoint of type DPT_Scaling is constant over the whole range of DPT_Scaling.
3 MSB 00h 2 0Fh 1 LSB FFh
Encoded value 15 ms/step
b. Two Datapoints DP0 and DP1 of type DPT_Scaling_Step_Time are used for two different time values in two subranges: Rule in the FB: subrange0: 0 % DP0.percentvalue time per step in subrange0: DP0.timevalue subrange1: DP0.percentvalue DP1.percentvalue time per step in subrange1: DP1.timevalue
Encoded values
DP0 3 MSB 00h 2 3Eh DP1 3 MSB 00h 2 1Fh 1 LSB FFh 1 LSB COh
subrange0: 0 % 75 % time0: 62 ms/step
subrange1: 75 % 100 % time1: 31 ms/step
AS v1.5.00 - page 74 of 161
KNX Standard
Interworking
Datapoint Types
3.44 Datatype V32N8Z8

3.44.1 Datapoint Type MeteringValue
Format:
octet nr. field names encoding octet nr. field names encoding
6 octets: V32N8Z8 6 MSB 5 CountVal VVVVVVVV VVVVVVVV VVVVVVVV VVVVVVVV 2 ValInfField 1 LSB Status/Command 4 3
NNNNNNNN Z Z Z Z Z Z Z Z PDT_GENERIC_06
PDT:
Datapoint Types ID: 229.001 Name: DPT_MeteringValue Description Counter value 32 bit Signed value Encoding of void value, fault, overridden etc. using Z8 Field Encoding of unit and resolution of the counter value Unit / Range V32, -2 147 483 648 to 2 147 483 647 unit and resolution according to ValInfField N8, 00h to 7Fh subset of M-Bus VIF table, and the subset of VIFE table for MWh, GJ, MW, GJ/h mapped to: 80h, 81h 88h, 89h A8h, A9h B0h, B1h encoding see table below Z8 Use: FB
Data fields CountVal
ValInfField
Status/Command
Standard Status/Command.
AS v1.5.00 - page 75 of 161
KNX Standard
ValInfField
Interworking
Datapoint Types
This field shall contain the indications about the encoding of unit and resolution of the counter value. A part of the encoding range < 80h is a subset of the primary VIF Table according to the M-Bus specification in EN13757-3. ValInfField vales 80h contain the mapping of VIFE range for GWh, GJ, MW and MJ/h.
coding 00000nnn 1000000n 00001nnn 1000100n 00010nnn 00011nnn 00101nnn 1010100n 00110nnn 1011000n 00111nnn 01000nnn 01001nnn 01010nnn 01101110 Others description energy energy energy energy volume mass power power power power volume flow volume flow volume flow mass flow Units for HCA reserved range coding 10(nnn-3) 10(n+5) 10(nnn) 10(n+8) 10(nnn-6) 10(nnn-3) 10(nnn-3) 10(n+5) 10(nnn) 10(n+8) 10(nnn-6) 10(nnn-7) 10(nnn-9) 10(nnn-3) Wh Wh J J m3 kg W W J/h J/h m3/h m3/min m3/sek kg/h range 0,001 0,1 0,001 0,1 0,001 0,001 0,001 0,1 0,001 0,1 0,001 0,000 1 0,001 0,001 Wh to 10 000 Wh MWh to GJ to 1 MWh 1 GJ kJ to 10 000 kJ l to 10 000 l kg to 10 000 kg W to 10 000 W MW to GJ/h to l/min to 1 MW 1 GJ/h 1000 l/min kJ/h to 10 000 kJ/h l/h to 10 000 l/h ml/s to 10 000 ml/s kg/h to 10 000 kg/h
dimensionless
AS v1.5.00 - page 76 of 161
KNX Standard
Interworking
Datapoint Types
3.45 Datatypes A8A8A8A8

3.45.1 DPT_Locale_ASCII
Format:
4 octets: A8A8A8A8 4 MSB

Language
2
Region
1 LSB
Ch arac ter 4
encoding
Ch arac ter 3
Ch arac ter 2
Ch arac ter 1
AAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAA none (not applicable) PDT_GENERIC_04
Unit: Resol.: PDT:
Datapoint Types ID: 231.001 Name: Encoding: Range: Language acc. to ISO 639-1 alpha-2 Region acc. to ISO 3166-1 alpha-2 Use: G DPT_Locale_ASCII A8A8A8A8 Datapoint Type is used to transmit a locale (location ISO 639-1 alpha-2 and region ISO 3166-1 alpha-2) code. The length is fixed to 4 octets (2 characters in ASCII for the location/language and 2 characters in ASCII for the location/region). The encoding is not case sensitive. The contents are filled from the most significant octet
EXAMPLE 3: de-DE German (GERMANY): 64h 65h 44h 45h EXAMPLE 4: en-GB English (UNITED KINGDOM): 65h 6Eh 47h 42h
AS v1.5.00 - page 77 of 161
KNX Standard
Interworking
Datapoint Types
3.46 Datapoint Types A8A8

3.46.1 DPT_LanguageCodeAlpha2_ASCII
Format:
2 octets: A8A8 2 MSB Character 1 1 LSB Character 2
AAAAAAAA AAAAAAAA
Encoding: Both Characters shall be ASCII-coded. This coding shall not be case sensitive. Range: Unit: Resol.: PDT: For every Character: as in DPT_Char_ASCII (4.001) not applicable not applicable PDT_GENERIC_02
Datapoint Types ID: 234.001

EXAMPLE 5 EXAMPLE 6
Name:
Use: G
DPT_LanguageCodeAlpha2_ASCII
German de shall be encoded as 6465h. English en shall be encoded as 656Eh.
The languages shall be encoded according ISO 639-1, of which the definitions are given in Table 3. Table 3 ISO 639-1 language codes
ISO 639-1 language code aa ab ae af ak am an ar as av ay az ba be bg bh bi bm bn Language name Afar Abkhazian Avestan Afrikaans Akan Amharic Aragonese Arabic Assamese Avaric Aymara Azerbaijani Bashkir Belarusian Bulgarian Bihari Bislama Bambara Bengali ISO 639-1 language code bo br bs ca ce ch co cr cs cu cv cy da de dv dz ee el en Language name Tibetan Breton Bosnian Catalan Chechen Chamorro Corsican Cree Czech Church Slavic Chuvash Welsh Danish German Divehi Dzongkha Ewe Greek English
ISO 639-1 language code eo es et eu fa ff fi fj fo fr fy ga gd gl gn gu gv ha he
Language name Esperanto Spanish Estonian Basque Persian Fulah Finnish Fijian Faroese French Western Frisian Irish Scottish Gaelic Galician Guaran Gujarati Manx Hausa Hebrew
AS v1.5.00 - page 78 of 161
KNX Standard
ISO 639-1 language code hi ho hr ht hu hy hz ia
Interworking
ISO 639-1 language code li ln lo lt lu lv mg mh mi mk ml mn mo mr ms mt my na nb nd ne ng nl nn no nr nv ny oc oj om or os pa pi pl ps pt qu rm rn ro ISO 639-1 language code ru rw sa sc sd se sg sh si sk sl sm sn so sq sr ss st su sv sw ta te tg th ti tk tl tn to tr ts tt tw ty ug uk ur uz ve vi
18)
Datapoint Types
Language name Hindi Hiri Motu Croatian Haitian Hungarian Armenian Herero Interlingua (International Auxiliary Language Association) Indonesian Interlingue Igbo Sichuan Yi Inupiaq Indonesian Ido Icelandic Italian Inuktitut Hebrew Japanese Yiddish Javanese Georgian Kongo Kikuyu Kwanyama Kazakh Kalaallisut Khmer Kannada Korean Kanuri Kashmiri Kurdish Komi Cornish Kirghiz Latin Luxembourgish Ganda
Language name Limburgish Lingala Lao Lithuanian Luba-Katanga Latvian Malagasy Marshallese Mori Macedonian Malayalam Mongolian Moldavian Marathi Malay Maltese Burmese Nauru Norwegian Bokml North Ndebele Nepali Ndonga Dutch Norwegian Nynorsk Norwegian South Ndebele Navajo Chichewa Occitan Ojibwa Oromo Oriya Ossetian Panjabi Pli Polish Pashto Portuguese Quechua Raeto-Romance Kirundi Romanian
Language name Russian Kinyarwanda Sanskrit Sardinian Sindhi Northern Sami Sango SerboCroatian 18) Sinhalese Slovak Slovenian Samoan Shona Somali Albanian Serbian Swati Sotho Sundanese Swedish Swahili Tamil Telugu Tajik Thai Tigrinya Turkmen Tagalog Tswana Tonga Turkish Tsonga Tatar Twi Tahitian Uighur Ukrainian Urdu Uzbek Venda Vietnamese
id ie ig ii ik in io is it iu iw ja ji jv ka kg ki kj kk kl km kn ko kr ks ku kv kw ky la lb lg
depricated
AS v1.5.00 - page 79 of 161
KNX Standard
ISO 639-1 language code vo wa wo xh yi
Interworking
ISO 639-1 language code yo za zh zu
Datapoint Types
Language name Volapk Walloon Wolof Xhosa Yiddish
Language name Yoruba Zhuang Chinese Zulu
3.47 Datapoint Type DPT_RegionCodeAlpha2_ASCII

Format:
2 octets: A8A8 2 MSB Ch arac ter 1 1 LSB Ch arac ter 2
AAAAAAA A A A A A A A A A None (not applicable) PDT_GENERIC_02
Unit: Resol.: PDT:
Datapoint Types ID: 234.002 Name: Encoding: Range: Use:

DPT_RegionCodeAlp A8A8 ha2_ASCII
Datapoint Type is used to transmit a region ISO 3166-1 G alpha-2 via ISO 3166-1 alpha-2 code. The length is fixed to 2 octets for the location/region. The encoding is not case sensitive. The contents are filled from the most significant octet
EXAMPLE 1: DE (Germany): 44h 45h EXAMPLE 2: GB (United Kingdom): 47h 42h
The regions shall be encoded according ISO 3166-1, of which the definitions are given in Table 4. Table 4 ISO 3166-1 region codes
ISO 3166-1 region code AD AE AF AG AI AL AM AN AO AQ Country name ANDORRA UNITED ARAB EMIRATES AFGHANISTAN ANTIGUA AND BARBUDA ANGUILLA ALBANIA ARMENIA NETHERLANDS ANTILLES ANGOLA ANTARCTICA ISO 3166-1 region code AR AS AT AU AW AX AZ BA BB BD
Country name ARGENTINA AMERICAN SAMOA AUSTRIA AUSTRALIA ARUBA LAND ISLANDS AZERBAIJAN BOSNIA AND HERZEGOVINA BARBADOS BANGLADESH
AS v1.5.00 - page 80 of 161
KNX Standard
ISO 3166-1 region code BE BF BG BH BI BJ BL BM BN BO BR BS BT BV BW BY BZ CA CC CD CF CG CH CI CK CL CM CN CO CR CS CU CV CX CY CZ DE DJ DK DM DO DZ
Interworking
ISO 3166-1 region code EC EE EG EH ER ES ET FI FJ FK FM FO FR GA GB GD GE GF GG GH GI GL GM GN GP GQ GR GS
Datapoint Types
Country name BELGIUM BURKINA FASO BULGARIA BAHRAIN BURUNDI BENIN SAINT BARTHLEMY BERMUDA BRUNEI DARUSSALAM BOLIVIA BRAZIL BAHAMAS BHUTAN BOUVET ISLAND BOTSWANA BELARUS BELIZE CANADA COCOS (KEELING) ISLANDS CONGO, THE DEMOCRATIC REPUBLIC OF THE CENTRAL AFRICAN REPUBLIC CONGO SWITZERLAND CTE D'IVOIRE COOK ISLANDS CHILE CAMEROON CHINA COLOMBIA COSTA RICA SERBIA AND MONTENEGRO (TRANSITIONALLY RESERVED) CUBA CAPE VERDE CHRISTMAS ISLAND CYPRUS CZECH REPUBLIC GERMANY DJIBOUTI DENMARK DOMINICA DOMINICAN REPUBLIC ALGERIA
Country name ECUADOR ESTONIA EGYPT WESTERN SAHARA ERITREA SPAIN ETHIOPIA FINLAND FIJI FALKLAND ISLANDS (MALVINAS) MICRONESIA, FEDERATED STATES OF FAROE ISLANDS FRANCE GABON UNITED KINGDOM GRENADA GEORGIA FRENCH GUIANA GUERNSEY GHANA GIBRALTAR GREENLAND GAMBIA GUINEA GUADELOUPE EQUATORIAL GUINEA GREECE SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS GUATEMALA GUAM GUINEA-BISSAU GUYANA HONG KONG HEARD ISLAND AND MCDONALD ISLANDS HONDURAS CROATIA HAITI HUNGARY INDONESIA IRELAND
AS v1.5.00 - page 81 of 161
GT GU GW GY HK HM HN HR HT HU ID IE
KNX Standard
ISO 3166-1 region code IL IM IN IO IQ IR IS IT JE JM JO JP JE JM JO JP KE KG KH KI KM KN KP KR KW KY KZ LA LB LC LI LK LR LS LT LU LV LY MA MC MD ME ISRAEL ISLE OF MAN INDIA BRITISH INDIAN OCEAN TERRITORY IRAQ
Interworking
ISO 3166-1 region code MF MG MH MK ML MM MN MO MP MQ MR MS MT MU MV MW MX MY MZ NA NC NE NF NG NI NL NO NP NR NU NZ OM PA PE PF PG PH PK PL PM PN PR
Datapoint Types
Country name
Country name SAINT MARTIN MADAGASCAR MARSHALL ISLANDS MACEDONIA, THE FORMER YUGOSLAV REPUBLIC OF MALI MYANMAR MONGOLIA MACAO NORTHERN MARIANA ISLANDS MARTINIQUE MAURITANIA MONTSERRAT MALTA MAURITIUS MALDIVES MALAWI MEXICO MALAYSIA MOZAMBIQUE NAMIBIA NEW CALEDONIA NIGER NORFOLK ISLAND NIGERIA NICARAGUA NETHERLANDS NORWAY NEPAL NAURU NIUE NEW ZEALAND OMAN PANAMA PERU FRENCH POLYNESIA PAPUA NEW GUINEA PHILIPPINES PAKISTAN POLAND SAINT PIERRE AND MIQUELON PITCAIRN PUERTO RICO
IRAN, ISLAMIC REPUBLIC OF ICELAND ITALY JERSEY JAMAICA JORDAN JAPAN JERSEY JAMAICA JORDAN JAPAN KENYA KYRGYZSTAN CAMBODIA KIRIBATI COMOROS SAINT KITTS AND NEVIS KOREA, DEMOCRATIC PEOPLE'S REPUBLIC OF KOREA, REPUBLIC OF KUWAIT CAYMAN ISLANDS KAZAKHSTAN LAO PEOPLE'S DEMOCRATIC REPUBLIC LEBANON SAINT LUCIA LIECHTENSTEIN SRI LANKA LIBERIA LESOTHO LITHUANIA LUXEMBOURG LATVIA LIBYAN ARAB JAMAHIRIYA MOROCCO MONACO MOLDOVA, REPUBLIC OF MONTENEGRO
AS v1.5.00 - page 82 of 161
KNX Standard
ISO 3166-1 region code PS PT PW PY QA RE RO RS RU RW SA SB SC SD SE SG SH SI SJ SK SL SM SN SO SR ST SV SY SZ TC TD TF TG TH TJ TK TL TM TN TO TR TT
Interworking
ISO 3166-1 region code TV TW TZ UA UG UM US UY UZ VA VC VE VG VI VN VU WF WS YE YT ZA ZM ZW TUVALU
Datapoint Types
Country name PALESTINIAN TERRITORY, OCCUPIED PORTUGAL PALAU PARAGUAY QATAR RUNION ROMANIA SERBIA RUSSIAN FEDERATION RWANDA SAUDI ARABIA SOLOMON ISLANDS SEYCHELLES SUDAN SWEDEN SINGAPORE SAINT HELENA SLOVENIA SVALBARD AND JAN MAYEN SLOVAKIA SIERRA LEONE SAN MARINO SENEGAL SOMALIA SURINAME SAO TOME AND PRINCIPE EL SALVADOR SYRIAN ARAB REPUBLIC SWAZILAND TURKS AND CAICOS ISLANDS CHAD FRENCH SOUTHERN TERRITORIES TOGO THAILAND TAJIKISTAN TOKELAU TIMOR-LESTE TURKMENISTAN TUNISIA TONGA TURKEY TRINIDAD AND TOBAGO
Country name
TAIWAN, PROVINCE OF CHINA TANZANIA, UNITED REPUBLIC OF UKRAINE UGANDA UNITED STATES MINOR OUTLYING ISLANDS UNITED STATES URUGUAY UZBEKISTAN HOLY SEE (VATICAN CITY STATE) SAINT VINCENT AND THE GRENADINES VENEZUELA VIRGIN ISLANDS, BRITISH VIRGIN ISLANDS, U.S. VIET NAM VANUATU WALLIS AND FUTUNA SAMOA YEMEN MAYOTTE SOUTH AFRICA ZAMBIA ZIMBABWE
AS v1.5.00 - page 83 of 161
KNX Standard
Interworking
Datapoint Types
4 Datapoint Types for HVAC

4.1
4.1.1
Simple Datapoint Types with STATUS/COMMAND Z8 field

Introduction
This clause gives a general introduction to the subject of extended Datapoint Types used in HVAC applications including a standardised Z8 field with STATUS / COMMAND information besides the main data value. The Datapoint Types containing a Z8 field always have the structure MZ8. This is, one main value (M) is followed by the Z8 field. Datapoint Types with a Z8 field have the naming format DPT_....._Z. These Datapoint Types are based on a more object oriented approach. This is the following. If such a Datapoint is accessed using the A_PropertyValue_Read-service 19) the response shall contain the Z8 field that is interpreted as a generic STATUS information that contains attributes of the Datapoint; If such a Datapoint is distributed using the service A_GroupPropertyValue_InfoReport 19), the Z8 field shall be interpreted as a generic STATUS information that contains attributes of the Datapoint (same as Response); If such a Datapoint is accessed using the services A_PropertyValue_Write 19) or A_GroupPropertyValue_Write 19), the additional field shall be interpreted as a COMMAND that contains methods to be executed on the Datapoint. STATUS - field For many HVAC objects a status information must be provided in addition to the main value for Readaccess or InfoReport service.
EXAMPLES sensor fault value is invalid Datapoint is not used by the application (out of service) value is invalid sensor value is overridden sensor alarm level is exceeded etc.
This Status information shall be transmitted together with the main value in the same A_PropertyValue_Response-PDU, A_GroupPropertyValue_Response-PDU or A_GroupPropertyValue_InfoReport-PDU (no different Datapoints or properties) for reasons of data consistency, support of generic Datapoint descriptions and minimised bus load. The KNX protocol does not offer the possibility to read different Datapoints in the same Application Layer PDU therefore structured DPT are used.
19)
The services A_PropertyValue_Read (A_PropertyValue_Read-PDU, A_PropertyValue_Response-PDU) or the service A_PropertyValue_Write (A_PropertyValue_Write-PDU) using point-to-point connectionless or connection-oriented communication mode or the LTE services A_GroupPropertyValue_Read (A_GroupPropertyValue_Read-PDU, A_GroupPropertyValue_Response-PDU), A_GroupPropertyValue_InfoReport, A_GroupPropertyValue_Write.
KNX Standard
COMMAND field
Interworking
Datapoint Types
On the other hand, execution of specific commands using the Application Layer services A_PropertyValue_Write and A_GroupPropertyValue_Write to change the status and behaviour of a Datapoint is often required.
EXAMPLES set Datapoint out of service normal write of a parameter override sensor value acknowledge alarm etc.
This Command shall also be transmitted together with the main value in the same A_PropertyValue_Write-PDU or A_GroupPropertyValue_Write-PDU (no different Datapoints or properties) for reasons of data consistency, generic Datapoint descriptions and minimal bus load. The KNX protocol does not offer specific Application Layer services to execute these different write commands. It is also not possible to write different Datapoints in the same Application Layer PDU. Therefore additional datatypes are proposed to allow transmission of the Z8 STATUS/COMMAND field in the same PDU.
4.1.2
Datatype format
Table 5 summarizes the general structure of new elementary datatypes with STATUS/COMMAND field in data octet 1. Table 5 Interpretation of the Z8-field in function of the Application Layer service
Property Access Application Layer Service PDU point-to-point addressing A_PropertyValue_Response-PDU A_PropertyValue_Write-PDU A_GroupPropertyValue_InfoReport-PDU LTE A_GroupPropertyValue_Response-PDU A_GroupPropertyValue_Write-PDU data octet n..2 data octet 1 Z8 STATUS COMMAND STATUS elementary datatype STATUS COMMAND
Constraint The Z8 datatype format is not applicable to the Shared Variable model or standard Group Objects because the Shared Variable model does not differentiate between InfoReport and Write service. The A_GroupValue_Write service is used for reporting of information (e.g. sensor values) and writing of information (e.g. write a actuator setpoint). Therefore the interpretation of the Z8 field would be ambiguous.
AS v1.5.00 - page 85 of 161
KNX Standard
Interworking
Datapoint Types
STATUS field: Z8 contains a 8 bit bitset (also following TC247 Field Level Objects status) in case of InfoReport or Read/Response service
Bit # Bit 0 Function OutOfService Main value Valid Invalid Remark Typical usage: optional sensor is not connected (out of service), sensor data is invalid configuration parameter is void (function disabled) Datapoint is accessible and the main value is valid X Datapoint is accessible but out of service, i.e. the main value is void and may contain any value. The sender shall support the OutOfService flag if the main value may be out of service. The receiver shall detect that the main value is invalid due to OutOfService condition Typical usage: sensor value is corrupted due to a hardware problem, data is invalid a database value is corrupted, e.g. due to loss off backup power, erased EEPROM etc. Datapoint main value is valid no failure Datapoint main value is corrupted due to failure. The sender shall support the Fault flag if the main value may be corrupted. The receiver shall detect that the main value is corrupted due to fault condition. The main value field contains failure information instead of the data value if Fault = true: main value failure information = 0 : general fault (unspecified) = 1 : sensor open circuit (optional detection) = 2 : sensor short circuit (optional detection) all other values are reserved The sender shall set the main value = 0 if the reason for the fault cannot be specified. Bit 2 Overridden Typical usage: sensor value is temporarily overridden for service actuator setpoint is temporarily overridden for service normal operation of the Datapoint, actual value actual Datapoint value is overridden Usage: for Datapoints with Alarming capability only X* X* X* X* Datapoint not in alarm status some alarm condition for this Datapoint occurred Usage: for Datapoints with Alarming capability only alarm is acknowledged by operator alarm is not yet acknowledged by operator set to 0,0,0
0: false 1: true
X*
Bit 1
Fault
0: false 1: true
X X
0: false 1: true Bit 3 InAlarm 0: false 1: true Bit 4 AlarmUnAck 0: acknowledged Bit 5-7 1: unacknowledged reserved
X* X*
X* validity of Datapoint value depends on other STATUS attributes
AS v1.5.00 - page 86 of 161
KNX Standard
Combination of Status bits
STATUS Bits OutOfService InAlarm; AlarmUnAck Overridden
Interworking
Datapoint Types
Fault
Main value
Remarks
false false false false
false false true true
false true false true
X X X X
valid valid failure info ! valid !

*)
Normal case value is overridden Datapoint failure, main value contains a failure information Datapoint failure but e.g. a corrupted (sensor-) value is overridden. Overridden has priority over Fault. The main value is valid.
-
true true
false true
false X
X X
invalid -----
actual (sensor-) value not available parameter out of service
illegal combination: if a Datapoint is out of service there is no reason for a Fault because also failure detection is out of service illegal combination: if a Datapoint is out of service there is no possibility to override it
true
true
-----
Remarks
-
Setting of the Status flags OutOfService and Fault is mutually exclusive. If a Datapoint is out of service (i.e. void, function disabled), a fault condition cannot arise and vice versa. Currently the flags InAlarm and AlarmUnAck are not used (i.e. 0, 0) in all Datapoints except simple AlarmInfo Datapoint ( see FB Technical Alarm) because Alarms are generated at device level but not at Datapoint level. But the STATUS enables Alarm generation and acknowledgement at Datapoint level in future applications. Depending on the features of a property only a subset of STATUS flags may be supported. The other flags are set to 0 (default) Features to be defined in the Datapoint description. Support of this combination of 'Fault' and 'Overridden' is optional. It is allowed that the override of the Datapoint value automatically clears the 'Fault' attribute, see also clause 4.1.5 'Fault' = false / 'Overridden' = true After execution of the COMMAND 'Release', the 'Overridden' attribute is cleared and the 'Fault' attribute is set again if the failure still persists.
*)
AS v1.5.00 - page 87 of 161
KNX Standard
Interworking
Datapoint Types
COMMAND field: Z8 contains a 8 bit enumeration value in case of a write service.

enum value COMMAN D Main value dont care Remark Typical support in LTE Write Client 1) LTE Write Server 2) Property Write Typical usage: normal write of a setpoint, parameter, configuration value not applicable for sensor values ! no change of the STATUS flags Typical usage: temporary override of a sensor value for service temporary override of a actuator setpoint for service sets STATUS Overridden may clear STATUS 'Fault' (optional, see above) Typical usage: together with Override. Undo Override, leads to normal operation of the Datapoint using the actual value resets STATUS Overridden Typical usage: disable functionality of a Datapoint configuration parameter is void (function disabled) sensor is disabled SetOSV data object is unused, function disabled sets STATUS OutOfService Typical usage: together with SetOSV The main value field is valid but may be ignored by the receiver (e.g. sensor) resets STATUS OutOfService Usage: for Datapoints with Alarming capability only Acknowledgement of Alarm STATUS resets STATUS AlarmUnAck Typical usage: parameters Sets the main value to the default value X X X X X X X (X) X (X) X X X X
=0
NormalWrit e
=1
Override
=2
Release
Valid X X =3 SetOSV =4 ResetOSV X =5 AlarmAck SetToDefa ult reserved =6 =7-255

1) 2) 3)
X: (X):
LTE runtime interworking Write Output, e.g. a HVAC zone controller valve setpoint output LTE runtime interworking Write Input, e.g. a Valve setpoint input Property (parameter in a device, server) accessible by a tool (client) usage possible and useful; support to be decided for each Datapoint individually very limited usage in practice.
KNX Standard
Remarks
Interworking
Datapoint Types
The usage of the Commands NormalWrite and Override/ Release is usually but not always mutually exclusive. E.g. a parameter may be written but an override of a parameter does not make sense. EXCEPTION EXAMPLE The valve setpoint is a LTE write input on the valve. A HVAC controller sends the valve setpoint periodically to the valve using the NormalWrite Command. A tool could execute an override to the setpoint on the valve. The valve uses from then on the override value and not the value from the HVAC controller. Reception of a COMMAND in the Datapoint server may change the STATUS of the Datapoint in the database. The Command itself is not stored in the database. COMMAND features except NormalWrite are mainly applicable for properties with Write access in client/server mode with point-to-point addressing. The Sender (i.e. Datapoint client) using A_PropertyValue_Write is normally a (Service-) Tool. During runtime communication the sender (i.e. a process device) of a LTE A_GroupPropValue_Write-PDU will usually have the COMMAND field fixed to NormalWrite (=0) because most other commands have no practical usage for process data communication. A tool will use A_PropertyValue_Write and point-to-point addressing, see above. Depending on the features of a property only a small subset of COMMANDS may be supported in the Datapoint server. Features to be defined in the Datapoint description.
4.1.3
OutOfService mechanism for a parameter
A parameter and the functionality behind the parameter can be disabled using the SetOSV command. EXAMPLE
Command 'Override' no action Command 'NormalWrite' Store main value Command 'SetOSV' Status 'OutOfService' = true; function(parameter) is disabled Command 'SetOSV' no action
Command 'Override' no action
'OutOfService' = false
'OutOfService' = true
Command 'ResetOSV' Store main value; Status 'OutOfService'= false function(parameter) is enabled Command 'NormalWrite' Command 'ResetOSV' no action Store main value
The parameter is changed using NormalWrite Command. The Command ResetOSV resets the Status OutOfService to false and the main value is written to the parameter. Override Command and Status Overridden are not supported on parameter Datapoints.
4.1.4
OutOfService mechanism for a runtime Datapoint (actual value)
A runtime Datapoint (e.g. a sensor value) and the functionality behind the Datapoint may be automatically disabled by the application program for various reasons (e.g. an optional sensor is not connected). This is indicated by the Status OutOfService.
AS v1.5.00 - page 89 of 161
KNX Standard
Interworking
Datapoint Types
The Datapoint value may be overridden only if OutOfService = false. If OutOfService = true, the Override feature is inhibited. EXAMPLE 1 Commands SetOSV and Reset OSV are supported, i.e. the actual value can be set out of service by a tool.
Command 'Override' no action Command 'SetOSV' no action
Command 'Release' Status 'Overridden'=false Command 'SetOSV' Status 'OutOfService' = true; function(datapoint) is disabled
Command 'Override' Store main value Status 'Overridden'=true
Command 'Release' no action
Command 'ResetOSV' no action
Command 'ResetOSV' Status 'OutOfService'= false function(datapoint) is enabled
EXAMPLE 2
The application program changes the OutOfService Status automatically depending on local application conditions. E.g. an optional sensor is not connected to a HVAC controller Status OutOfService = true (and not Fault = true) Property Write Commands SetOSV and ResetOSV sent via bus are not supported on such Datapoints.
Command 'Override' no action Command 'SetOSV' no action
Command 'Release' Status 'Overridden'=false Application condition X Status 'OutOfService' = true; function(datapoint) is disabled
Command 'Override' Store main value Status 'Overridden'=true
Command 'ResetOSV' no action Command 'SetOSV' no action
Application condition Y Status 'OutOfService'= false function(datapoint) is enabled
Command 'Release' no action
4.1.5
Override mechanism
Override is used for a temporary service operation on device level or system level. Usually sensor values or actuator setpoints may support the override feature.
InfoReport Read/Response
datapoint value
CMD 'Release' / 'Override'

'Overridden' = false 'Overridden' = true
internal value
e.g. from sensor
override value
NOTE In case of a sensor failure (STATUS 'Fault') it may be useful to override the sensor value temporarily for service reasons. Execution of the COMMAND 'Override' disconnects the data flow from the sensor to the Datapoint value and the override value is used instead. Since the actual sensor value is no more considered, it is allowed for the implementation of the Datapoint to clear the STATUS 'Fault' when 'Overridden' is set. See also clause 4.1.2
AS v1.5.00 - page 90 of 161
KNX Standard
EXAMPLE 1
Interworking
Datapoint Types
Override of a sensor value, e.g. the LTE InfoReport sensor output (Datapoint server); local override of the output by a tool using Property Write service (individual addressing).
Command 'Override' Store main value Command 'Override' Status 'Overridden'=true Store main value
Command 'NormalWrite' no action
Command 'SetOSV' no action
'Overridden' = false
Command 'Release' Status 'Overridden'=false Command 'Release' no action
'Overridden' = true
In the state Overridden = true the actual value of the sensor is replaced by the override value, which is distributed in the system using LTE InfoReport service. In the state Overridden = true the Commands SetOSV / ResetOSV have no effect (Override has in this case higher priority). EXAMPLE 2 Override of a valve setpoint on the valve, i.e. a LTE Write input (Datapoint server) on the valve is overridden from a tool by using LTE Write service or Property Write service.
Command 'Override' Store main value Command 'NormalWrite' Store main value Command 'Override' Status 'Overridden'=true Store main value
Command 'SetOSV' no action
'Overridden' = false
Command 'Release' Status 'Overridden'=false Command 'Release' no action
'Overridden' = true
In state Overridden = true the override value is used and the received value (LTE Write service) with Command NormalWrite is ignored. After the Release Command the actual value of the Datapoint is undefined until the reception of the next NormalWrite LTE Write update (the valve will use either a default value or keeps the override value). Override Timeout: Overridden status shall be self clearing based on a timeout, because the override condition shall not remain forever if the operator / installer forgets to Release the overridden Datapoint. The implementation of the timeout is company specific, e.g. individual timeout per Datapoint or automatic Release of all Datapoints in a device at midnight or re-trigger a common timeout for all Datapoints after reception of each Override Command timeout executes a Release on all Datapoints. Power-up condition will normally reset the Overridden attribute (manufacturer specific solution).
4.1.6
Alarming mechanism
An Alarm at Datapoint level indicates that a serious fault condition occurred or still occurs on the Datapoint.
AS v1.5.00 - page 91 of 161
KNX Standard
Interworking
Datapoint Types
EXAMPLES transient error event (e.g. critical sensor level exceeded) persistent error state (e.g. sensor fault; corrupted memory value) Alarms can be acknowledged by an operator (write service to a property). Datapoints with Alarm feature therefore therefore a corresponding 2 bit state machine in the Status field (InAlarm / AlarmUnAck). Alarm State Machine
Command AlarmAck InAlarm = false; AlarmUnAck = acknowledged Normal, Acked disturbance appears InAlarm = false; AlarmUnAck = unacknowledged Normal, UnAcked disturbance appears
Command AlarmAck
disturbance disappears
disturbance disappears
InAlarm = true; AlarmUnAck = acknowledged
Alarm, Acked
disturbance appears Command AlarmAck
Alarm, UnAcked
Command AlarmAck
disturbance appears
InAlarm = true; AlarmUnAck = unacknowledged
NOTE Currently Alarm messages are provided for the system only on device-level (not on functional or Datapoint level) using the AlarmInfo Datapoint ( see FB Technical Alarm). I.e. individual Datapoints except the device alarm Datapoint AlarmInfo do not support this feature.
4.2
Datapoint Types B1
1 bit: B1 1 b B See below b = {0,1} See below (not applicable) PDT_BINARY_INFORMATION (alt: PDT_UNSIGNED_CHAR)
octet nr
Format:
Encoding: Range: Unit: Resol.: PDT:
Datapoint Types ID: 1.100 Name: DPT_Heat/Cool 0 1 = cooling = heating Encoding: b Use: FB
AS v1.5.00 - page 92 of 161
KNX Standard
Interworking
Datapoint Types
4.3
Datapoint Types N8
octet nr.
Format:
Datapoint Types ID: 20.100 Name: DPT_FuelType Encoding: field1 = FuelType 0 = auto 1 = oil 2 = gas 3 = solid state fuel 4 255 = not used, reserved field1 = BurnerType 0 = reserved 1 = 1 stage 2 = 2 stage 3 = modulating 4 255 = reserved field1 = HVACMode 0 = Auto 1 = Comfort 2 = Standby 3 = Economy 4 = Building Protection 5 255 = reserved Range: [0 3] Use: HWH
20.101
DPT_BurnerType
[0 3]
HWH
20.102
DPT_HVACMode
[0 4]
HVAC
NOTE 13
DPT_HVACMode is the same as DPT_HVACMode_Z (201.100), but without Z8 field.
In HVAC Room Controllers in KNX Standard Mode, DPT_HVACMode shall be used to set the HVAC Mode. The HVAC Room controller may have in addition to the DPT_HVACMode individual Datapoints of 1 bit to set the HVAC Mode. (This means that additional HVAC Mode via individual 1 bit DPs is allowed.) For reporting the currently set HVAC Mode by means of a status/diagnostic Datapoint, the HVAC Room controllers shall use DPT_StatusRHCC or possibly DPT_HVACStatus (see Appendix A). 20.103 DPT_DHWMode 20) field1 = DHWMode 0 = Auto 1 = LegioProtect 2 = Normal 3 = Reduced 4 = Off/FrostProtect 5 255 = reserved [0 4] HWH
20)
Same as DPT_DHWMode_Z (201.102), but without Z8 field.

KNX Standard
Datapoint Types ID: 20.104 Name: DPT_LoadPriority
Interworking
Datapoint Types
Encoding: field1 = LoadPriority 0 = None 1 = Shift load priority 2 = Absolute load priority 3 255 = reserved
Range: [0 2]
Use: HVAC
20.105
DPT_HVACContrMode 21)
field1 = HVACContrMode {[0 17], 20} HVAC 0 = Auto 1 = Heat 2 = Morning Warmup 3 = Cool 4 = Night Purge 5 = Precool 6 = Off 7 = Test 8 = Emergency Heat 9 = Fan only 10 = Free Cool 11 = Ice 12 = Maximum Heating Mode 13 = Economic Heat/Cool Mode 14 = Dehumidification 15 = Calibration Mode 16 = Emergency Cool Mode 17 = Emergency Steam Mode 18 19 = reserved 20 = NoDem 21 255 = reserved [0 5] HVAC
20.106
DPT_HVACEmergMode 22) field1 = HVACEmergMode 0 = Normal 1 = EmergPressure 2 = EmergDepressure 3 = EmergPurge 4 = EmergShutdown 5 = EmergFire 6 255 = reserved DPT_ChangeoverMode field1 = ChangeoverMode 0 = Auto 1 = CoolingOnly 2 = HeatingOnly 3 255 = reserved
20.107
[0 2]
HVAC
21) 22)
Same as DPT_HVACContrMode_Z (201.104), but without Z8 field. Same as DPT_HVACEmergMode_Z (201.109), but without Z8 field.
KNX Standard
Datapoint Types ID: 20.108 Name: DPT_ValveMode
Interworking
Datapoint Types
Encoding:
Range:
Use: HVAC
field1 = ValveMode [1 5] 0 = reserved 1 = Heat stage A for normal heating 2 = Heat stage B for heating with two stages (A + B) 3 = Cool stage A for normal cooling 4 = Cool stage B for cooling with two stages (A + B) 5 = Heat/Cool for changeover applications 6 255 = reserved field1 = DamperMode 0 = reserved 1 = Fresh air, e.g. for fancoils 2 = Supply Air. e.g. for VAV 3 = Extract Air e.g. for VAV 4 255 = reserved [1 3]
20.109
DPT_DamperMode
HVAC
20.110
DPT_HeaterMode
field1 = HeaterMode [1 3] 0 = reserved 1 = Heat Stage A On/Off 2 = Heat Stage A Proportional 3 = Heat Stage B Proportional 4 255 = reserved field1 = FanMode 0 = not running 1 = permanently running 2 = running in intervals 3 255 = reserved field1 = MasterSlaveMode 0 = autonomous 1 = master 2 = slave 3 255 = reserved [0 2]
HVAC
20.111
DPT_FanMode
TU
20.112
DPT_MasterSlaveMode
[0 2]
TU
20.113
DPT_StatusRoomSetp
field1 = StatusRoomSetp [0 2] 0 = normal setpoint 1 = alternative setpoint 2 = building protection setpoint 3 255 = reserved
TU DEH
AS v1.5.00 - page 95 of 161
KNX Standard
Interworking
Datapoint Types
4.4
4.4.1
Data Type 8-Bit Set

Datapoint Type Forcing Signal
1 octet: B8 1 Attributes BBBBBBBB

Format:
Encoding: See below. Range: Unit: Resol.: PDT: ID: 21.100 See below. Not applicable. Not applicable. PDT_BITSET8 Name: DPT_ForceSign Encoding: See below (alt: PDT_GENERIC_01) Range: See below Use: HWH
Datapoint Types
Data fields
Attributes - ForceRequest - Protection
Description
Bit # 0 1 indicates if forced power consumption is necessary (validity of the remaining attributes) Protection indicates that a critical overheat condition occurs (e.g. too high boiler temp.). The interpretation of the attributes DHWNorm, DHWLegio, RoomHComf and RoomHMax depends on the type of overheat: the addressed heat consumers shall consume energy Oversupply indicates that an uncritical overheat condition occurs (e.g. boiler temperature is much higher than requested by heat demand). The interpretation of the attributes DHWNorm, DHWLegio, RoomHComf and RoomHMax depends on the type of overheat: the addressed heat consumers may consume energy indicates that remaining energy is available (e.g. in the boiler after load shutdown). All heat consumers which were active immediately before the overrun condition occurred continue their energy consumption with their last setpoint. This attribute is completely independent from the attributes Protection, Oversupply, DHWNorm, DHWLegio, RoomHComf and RoomHMax Load DHW to Normal Level in case of overheat: additional info about the type of overheat is contained in the Protection and Oversupply attributes
Range
Bitset B8, true / false true / false
- Oversupply
true / false
- Overrun
true / false
- DHWNorm
true / false
- DHWLegio - RoomHComf
5 6
Load DHW to LegioProtect Level in case of overheat (Protection true / false or Oversupply) Load Room Heating to Comfort Level in case of overheat (Protection or Oversupply) true / false
AS v1.5.00 - page 96 of 161
KNX Standard
Data fields
Attributes - RoomHMax
Interworking
Description
Bit # 7 Load Room Heating with maximum flow temperature in case of overheat (Protection or Oversupply)
Datapoint Types
Range
Bitset B8, true / false
Depending on the usage of this DPT in a given Datapoint, some bit-fields may be unused and set to 0 by the sender and will be ignored by the receiver Standard Mode The information of this DPT is not available in Standard Mode.
4.4.2
Format:
Datapoint Type Forcing Signal Cool


Encoding: See below. Range: Unit: Resol.: PDT: ID: 21.101 See below. Not applicable. Not applicable. PDT_BITSET8 Name: DPT_ForceSignCool Description Bit # 0 1 to 7 (alt: PDT_GENERIC_01) Encoding: See below. Range: See below. Unit / Range Bitset B8 indicates if forced power consumption is true / false necessary (validity of the remaining attributes) default 0 Use: VAC
Datapoint Types
Data fields Attributes - ForceRequest reserved
Standard Mode The information of this DPT is not available in Standard Mode.
AS v1.5.00 - page 97 of 161
KNX Standard
Interworking
Datapoint Types
4.4.3
Format:
Datapoint Type Room Heating Controller Status

LTE: structured DPT

Encoding: See below. Range: Unit: Resol.: PDT: ID: 21.102 See below. Not applicable. Not applicable. PDT_BITSET8 Name: DPT_StatusRHC Description Bit # 0 1 2 3 4 5 6 7 Room Heating Controller as a failure (mainly for monitoring) ECO status; temporary energy saving mode; e.g. due to high room temperature or high outside temperature Flow temperature limitation active Return temperature limitation active morning boost active start optimization active stop optimization active room heating is disabled due to local summer/winter mode (alt: PDT_GENERIC_01) Encoding: See below. Range: See below. Use: HWH Unit / Range Bitset B8 true / false true / false true / false true / false true / false true / false true / false true / false
Datapoint Types
Data fields Attributes - Fault - StatusECO - TempFlowLimit - TempReturnLimit - StatusMorningBoost - StatusStartOptim - StatusStopOptim - SummerMode
Depending on the usage of this DPT in a given Datapoint, some bit-fields may be unused and set to 0 by the sender and will be ignored by the receiver Standard Mode Separate Boolean DPs.
AS v1.5.00 - page 98 of 161
KNX Standard
Interworking
Datapoint Types
4.4.4
Format:
Datapoint Type Solar DHW Controller Status

1 octet: B8 1 Attributes 0 0 0 0 0 BBB
LTE: structured DPT

Encoding: See below. Range: Unit: Resol.: PDT: ID: 21.103 See below. Not applicable. Not applicable. PDT_BITSET8 Name: DPT_StatusSDHWC Description Bit # 0 1 2 3 to 7 SDHWC has a failure SDHW load currently active, solar pump is running enough solar energy available for DHW load to reach the DHW temperature setpoint (alt: PDT_GENERIC_01) Encoding: See below. Range: See below. Use: DHW control Unit / Range Bitset B8 1 = fault 0 = ok true / false true / false default 0
Datapoint Types
Data fields Attributes - Fault - SDHWLoadActive - SolarLoadSufficient - reserved
Standard Mode Separate Boolean DPs.
AS v1.5.00 - page 99 of 161
KNX Standard
Interworking
Datapoint Types
4.4.5
Format:
Datapoint Type Fuel Type Set

1 octet: B8 1 Fuel Type Set 0 0 0 0 0 BBB
LTE: structured DPT

Encoding: See below. Range: Unit: Resol.: PDT: ID: 21.104 See below. Not applicable. Not applicable. PDT_BITSET8 Name: DPT_FuelTypeSet Description Bit # 0 1 2 3 to 7 oil fuel supported gas fuel supported solid state fuel supported (alt: PDT_GENERIC_01) Encoding: See below. Range: See below. Use: HWH Unit / Range Bitset B8 true / false true / false true / false default 0
Datapoint Types
Data fields FuelType - Oil - Gas - SolidState reserved
AS v1.5.00 - page 100 of 161
KNX Standard
Interworking
Datapoint Types
4.4.6
Format:
Datapoint Type Room Cooling Controller Status

1 octet: B8 1 Attributes 0000000B
LTE: structured DPT

Encoding: See below. Range: Unit: Resol.: PDT: ID: 21.105 Data fields Attributes - Fault reserved See below. Not applicable. Not applicable. PDT_BITSET8 Name: DPT_StatusRCC Description Bit # 0 1 to 7 for features implemented in the future (alt: PDT_GENERIC_01) Encoding: See below. Range: See below. Use: VAC Unit / Range Bitset B8 Room Cooling Controller has a failure (mainly for monitoring) true / false default 0
Datapoint Types
4.4.7
Format:
Datapoint Type Ventilation Controller Status

1 octet: B8 1 Attributes 0 0 0 0 BBBB
LTE: structured DPT

Encoding: See below. Range: Unit: Resol.: PDT: ID: 21.106 See below. Not applicable. Not applicable. PDT_BITSET8 Name: DPT_StatusAHU (alt: PDT_GENERIC_01) Encoding: See below Range: See below Use: VAC
Datapoint Types
AS v1.5.00 - page 101 of 161
KNX Standard
Data fields Attributes - Fault - FanActive - Heat - Cool reserved Description Bit # 0 1 2 3 4 to 7
Interworking
Datapoint Types
Unit / Range Bitset B8 true / false true / false true / false true / false default 0
Ventilation Controller has a failure (mainly for monitoring) Supply and / or exhaust air fans are operating Ventilation Controller is in heating mode Ventilation Controller is in cooling mode for features implemented in the future
4.5
4.5.1
Data Type 16-Bit Set

Datapoint Type DHW Controller Status
2 octets: B16 2MSB Attributes 0 0 0 0 0 0 0 B BBBBBBBB 1LSB

Format:
Encoding: Range: Unit: Resol.: PDT: ID: 22.100 Not applicable. Not applicable. PDT_BITSET16 Name: DPT_StatusDHWC Encoding: See below (alt: PDT_GENERIC_02) Range: See below Use: DHW control
Datapoint Types
AS v1.5.00 - page 102 of 161
KNX Standard
Data fields Attributes - Fault - DHWLoadActive - LegioProtActive - DHWPushActive - OtherEnergySourceActive - SolarEnergyOnly - SolarEnergySupport - TempOptimShiftActive reserved
Interworking
Description Bit # 0 1 2 3 4 5 6 7 8 to 15 DHWC has a failure DHW load currently active legionella protection procedure active (load & hold) true during DHW load triggered by a DHWPush command
Datapoint Types
Unit / Range Bitset B16 true / false true / false true / false true / false true / false true / false true / false true / false default 0
load by DHWC is disabled due to other active energy source (e.g. electrical) load by DHWC is disabled due to sufficient solar energy DHW load is partly done by solar energy actual DHW temp setpoint is influenced by TempDHWSetpOptimShift 0 reserved
4.5.2
LTE
Datapoint Type RHCC Status
Not available. Standard Mode

Format:
2 octets: B16 2 MSB Attributes 0 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0 1 LSB
encoding Range: Unit: Resol.: PDT:
r B B B B B B B all fields: {0,1} Not applicable. Not applicable. PDT_BITSET16
B B B B B B B B
(alt: PDT_GENERIC_02)
Datapoint Types ID: 22.101 Name: DPT_StatusRHCC Use: HVAC
AS v1.5.00 - page 103 of 161
KNX Standard
Data fields Bit # Attributes 0 Fault 1 StatusEcoH Description
Interworking
Datapoint Types
Sup Encoding Bitset B16
Room Temperature Controller has a failure. This is a status information, mainly for monitoring. ECO status of the room heating temperature controller; If true, the heating controller is temporary in energy saving mode and there is no heat demand although the controller is in heating mode (HeatCoolMode=heating) e.g. due to high room temperature because of internal or solar heat gains or due to high outside temperature Flow temperature limitation is active. E.g. max. flow temperature limitation for floor heating protection Return temperature limitation is active e.g. min return temperature is maintained for boiler protection
M O
0 = false 1 = true 0 = false 1 = true
2 TempFlowLimit 3 TempReturnLimit
O O O O
0 = false 1 = true 0 = false 1 = true 0 = false 1 = true 0 = false 1 = true 0 = false 1 = true 0 = false 1 = true
4 StatusMorningBoostH Heating morning boost is active, plant is operated at maximum heating output 5 StatusStartOptim optimum early start control in the morning is active in order to reach the comfort setpoint according to schedule optimum early shutdown control in the evenig is active in order to maintain the comfort setpoint until the end of the comfort schedule period room heating is disabled due to local summer/winter mode. E.g. heating is disabled if - the attenuated outside temperature is above a threshold - current date is in programmed summer-period HeatCoolMode of the controller default: heating ECO status of the room cooling temperature controller; If true, the cooling controller is temporary in energy saving mode and there is no cooling demand although the controller is in cooling mode (HeatCoolMode=cooling) e.g. due to energy savings regulations cooling is not allowed if the room temperature is below a defined limit. Pre cooling mode in the morning, , plant is operated at maximum cooling output Cooling is disabled due to (examples) - calendar regulations: current date is out of cooling period - the attenuated outside temperature is below a threshold DewPointStatus of the controller Frost alarm status of the controller: in alarm if the room temperature drops below a critical threshold Overheat alarm status of the controller: in alarm if the room temperature exceeds a critical threshold
6 StatusStopOptim
7 HeatingDisabled
8 HeatCoolMode 9 StatusEcoC
M O
0 = cooling 1 = heating 0 = false 1 = true
10 StatusPreCool 11 CoolingDisabled
O O
0 = false 1 = true 0 = false 1 = true
12 DewPointStatus 13 FrostAlarm 14 OverheatAlarm 15 reserved
O O O --
0 = no alarm 1 = alarm 0 = no alarm 1 = alarm 0 = no alarm 1 = alarm default 0
AS v1.5.00 - page 104 of 161
KNX Standard
Interworking
Datapoint Types
Usage requirements DPT_StatusRHCC shall be used by an HVAC Room controller to report the currently set HVAC Mode by means of a status/diagnostic Datapoint.
NOTE 14 An alternative coding is allowed to report the currently set HVAC Mode. For the description and the usage conditions, please refer to the description of DPT_HVACStatus in Appendix A.
Encoding Most of the status fields are optional. The coding of the optional fields is defined so that the default value 0 represents the normal case and 1 represents the exception. Displays will usually only indicate the exception but not the normal case. Therefore depending on the usage of this DPT in a given Datapoint, some bit-fields may be unused and set to 0 by the sender and will be ignored by the receiver. Remarks - DPT_StatusRHCC is derived from DPT_StatusRHC (21.102) and the Eberle Status Octet and extended by some additional attributes - DPT_StatusRHC is extended to 16 bit and the information of DPT_StatusRHC is a subset of DPT_StatusRHCC - Except HVAC mode information, all relevant attributes of the Eberle Status Octet are included - The actual HVAC mode of the controller is encoded as enum value in a separate Datapoint. - The cooling control sequence of the controller is active if - HeatCoolMode = cooling - CoolingDisabled = false - The heating control sequence of the controller is active if - HeatCoolMode = heating - HeatingDisabled = false - The controller is neither heating nor cooling if - HeatCoolMode = dont care - CoolingDisabled = true - HeatingDisabled = true
AS v1.5.00 - page 105 of 161
KNX Standard
Interworking
Datapoint Types
4.6
Datapoint Types N2
2 bit: N2 1 s NN None (not applicable) PDT_ENUM8 (alt: PDT_UNSIGNED_CHAR)
octet nr
Format:
Unit: Resol.: PDT:
Datapoint Types ID: 23.102 Name: DPT_HVAC_PB_Action Range: Use: Encoding: s 00b = Comfort/Economy 01b = Comfort/Nothing 10b = Economy/Nothing 11b = Building prot/Auto [00b11b] FB
AS v1.5.00 - page 106 of 161
KNX Standard
Interworking
Datapoint Types
4.7
4.7.1
Datapoint Types N3
Datapoint Type DPT_PB_Action_HVAC_Extended
3 bit: N3 1 s NNN None (not applicable) PDT_ENUM8 (alt: PDT_UNSIGNED_CHAR)
Format:
Unit: Resol.: PDT:
Datapoint Types ID: 31.101 Name: Range: Use: Encoding:
Name: DPT_PB_Action_HVAC_Extended Range: [000b to 111b] Use: CH_PB_HVAC_Mode_1 Encoding: s This DPT shall not be used for runtime communication. This DPT shall only be used for encoding Parameter values in CH_PB_HVAC_Mode_1. For the proper interpretation, please refer to the specification of this Channel in the E-Mode specifications. This DPT allows designing a switch to control the HVAC Mode with an Output HVAC Mode (DPT_HVACMode, 20.102). This DPT_PB_Action_HVAC_Extended encodes a parameter value to configure which HVAC Mode shall be activated on press of the switch and which HVAC Mode shall be activated on release of the switch. Value of DPT_PB_Action_HVAC_Extended 000b 001b 010b 011b 100b 101b 110b 111b Value transmitted on the Output HVAC Mode when the switch is pressed Comfort Comfort Economy Building prot. Building prot. Auto Standby Comfort released Economy (no transmission) (no transmission) Auto (no transmission) (no transmission) (no transmission) Standby
AS v1.5.00 - page 107 of 161
KNX Standard
Interworking
Datapoint Types
4.8
4.8.1
Data Type Boolean with Status/Command

Datapoint Type Heat/Cool_Z
2 octets: B1Z8 2 Heat/Cool 0000000B 1 Status Command ZZZZZZZZ

Format:
Encoding: See below Range: Unit: See below See below
Datapoint Types ID: 200.100 Name: DPT_Heat/Cool_Z Range: See below Unit: See below Usage: HVAC
Data fields Heat/Cool - Heat/Cool Status/Command
Description Bit # 0 standard Status/Command
Unit / Range Bitset B8, 0= cooling 1= heating Z8
Standard Mode DPT_Heat/Cool (01.100); without Z8 field
4.8.2
Format:
Datapoint Type DPT_BinaryValue_Z

2 octets: B1Z8 2 BinaryValue 0000000B 1 Status Command ZZZZZZZZ
Datapoint Types ID: 200.101 Name: DPT_BinaryValue_Z Range: See below Unit: See below Usage: FOCI
AS v1.5.00 - page 108 of 161
KNX Standard
Data fields BinaryValue - Low/High Description Bit # 0
Interworking
Datapoint Types
Unit / Range Bitset B8 0 = low 1 =high Z8
Status/Command
standard Status/Command
Standard Mode DPT_BinaryValue (1.006) without Z8 field/
4.9
4.9.1
Data Type 8-Bit Enum with Status/Command

Datapoint Type HVAC Operating Mode
2 octets: N8Z8 2 HVACMode 1 Status/ Command

Format:
encoding
NNNNNNNN Z Z Z Z Z Z Z Z none PDT_GENERIC_02 Name: DPT_HVACMode_Z Encoding: See below Range: See below Unit: See below Use: HVAC
Resol.: PDT: ID: 201.100
Datapoint Types
DPT_HVACMode_Z
Data fields HVACMode Description HVAC operating mode Depending on the type of Datapoint the value Auto is allowed or not to be defined per Datapoint Unit / Range enum. N8 Encoding absolute value N = {0, 255} 0 = Auto 1 = Comfort 2 = Standby 3 = Economy 4 = Bldg.Prot 5-255: reserved Z8
Status/Command
Standard Mode DTP_HVACMode (20.102), without Z8 field.
AS v1.5.00 - page 109 of 161
KNX Standard
Interworking
Datapoint Types
4.9.2
Format:
Datapoint Type DHW Mode

2 octet N8Z8 2 DHWMode NNNNNNNN 1 Status/ Command ZZZZZZZZ
Datapoint Types ID: 201.102 Name: DPT_DHWMode_Z Range: See below Unit: See below Usage: HWH
DPT_DHWMode_Z: Data fields DHWMode Description DHW operating mode Depending on the type of Datapoint the value Auto is allowed or not to be defined per Datapoint Unit / Range enum. N8 Encoding absolute value N = {0, 255} 0 = Auto 1 = LegioProtect 2 = Normal 3 = Reduced 4 = Off/FrostProtect 5 to 255: reserved Z8
Status/Command
Standard Mode DPT_DHWMode (20.103) without Z8 field.
4.9.3
Format:
Datapoint Type HVAC Controlling Mode

2 octets: N8Z8 2 HVACContrMode 1 Status/Command

encoding
NNNNNNNN Z Z Z Z Z Z Z Z PDT_GENERIC_02 Name: DPT_HVACContrMode_Z Encoding: See below. Unit: See below. Range: See below. Resol.: Use:
PDT: ID: 201.104
Datapoint Types See below. TU
AS v1.5.00 - page 110 of 161
KNX Standard
Data fields HVACContrMode Description
Interworking
Unit / Range
Datapoint Types
Status/Command
enum.: N8 Encoding absolute value N = {0, 255} 0 = Auto 1 = Heat 2 = Morning Warmup 3 = Cool 4 = Night Purge 5 = Precool 6 = Off 7 = Test 8 = Emergency Heat 9 = Fan only 10 = Free Cool 11 = Ice 12 = Maximum Heating Mode 13 = Economic Heat/Cool Mode 14 = Dehumidification 15 = Calibration Mode 16 = Emergency Cool Mode 17 = Emergency Steam Mode 18 to 19 = reserved 20 = NoDem 21 to 255 = reserved Z8
Standard Mode DPT_HVACContrMode (20.105), without Z8 field.
4.9.4
Format:
Datapoint Type Enable Heat/Cool Stage

2 octets: N8Z8 2 EnableH/CStage 1 Status/Command

encoding
NNNNNNNN Z Z Z Z Z Z Z Z none none PDT_GENERIC_02 Name: DPT_EnableH/Cstage_Z Encoding: See below. Range: See below. Use: HVAC
Unit: Resol.: PDT: ID: 201.105
Datapoint Types
AS v1.5.00 - page 111 of 161
KNX Standard
Data fields EnableH/CStage Description
Interworking
Unit / Range
Datapoint Types
enum.: N8 Encoding absolute value N = {0, 255} 0 = disabled 1 = enable stage A 2 = enable stage B 3 = enable both stages standard Status/Command Z8
Status/Command
Standard Mode Not available.
4.9.5
Format:
Datapoint Type Building Mode

2 octets: N8Z8 2 BuildingMode NNNNNNNN 1 Status/ Command ZZZZZZZZ
Datapoint Types ID: 201.107 Name: DPT_BuildingMode_Z Range: See below Unit: See below Usage: general
Data fields BuildingMode
Description
Unit / Range enum. N8 Encoding absolute value N = {0, 255} 0 = Building in use 1 = Building not used 2 = Building Protection
Status/Command
Z8
Standard Mode DPT_BuildingMode (20.002), without Z8 field.
AS v1.5.00 - page 112 of 161
KNX Standard
Interworking
Datapoint Types
4.9.6
Format:
Datapoint Type Occupancy Mode

2 octets: N8Z8 2 OccMode NNNNNNNN 1 Status/ Command ZZZZZZZZ
Datapoint Types ID: 201.108 Name: DPT_OccMode_Z Range: See below Unit: See below Usage: HVAC
Data fields OccMode
Description
Unit / Range enum. N8 Encoding absolute value N = {0, 255} 0 = Occupied 1 = Standby 2 = Not occupied
Status/Command
Z8
Standard Mode DPT_OccMode (20.003) without Z8 field.
4.9.7
Format:
Datapoint Type HVAC Emergency Mode

2 octets: N8Z8 2 HVACEmerg Mode NNNNNNNN 1 Status/ Command ZZZZZZZZ
Datapoint Types ID: 201.109 Name: DPT_HVACEmergMode_Z Range: See below Unit: See below Usage: HVAC
AS v1.5.00 - page 113 of 161
KNX Standard
Data fields HVACEmergMode Description
Interworking
Unit / Range enum. N8 Encoding absolute value N = {0, 255} 0 = Normal 1 = EmergPressure 2 = EmergDepressure 3 = EmergPurge 4 = EmergShutdown 5 = EmergFire 6 to 255: reserved
Datapoint Types
Status/Command
Z8
Standard Mode HVACEmergMode (20.106), without Z8 field
4.10 Data Type 16-Bit Unsigned Value with Status/Command

4.10.1 Datapoint Type HVAC Air Quality
Format: 3 octets: U16Z8 3 MSB HVACAirQual UUUUUUUU Encoding: See below Range: Unit: See below See below 2 LSB HVACAirQual UUUUUUUU 1 Status Command ZZZZZZZZ
Datapoint Types ID: 203.100 Name: DPT_ HVACAirQual_Z Description Range: See below Unit: See below Unit / Range U16, 1ppm resolution 0 ppm to 65535 ppm standard Status/Command Z8 Usage: TU, VAC
Data fields HVACAirQual
Status/Command
In case of a detected sensor failure the Status Flag Fault shall be set. This is a mandatory feature of this DPT. In this case in addition the reason of Fault may be encoded in the HVACAirQual field (optional feature): see standard Z8 mechanism in 4.1.2. Standard Mode DPT_Value_AirQuality (9.008), only HVACAirQual without Z8 field.
AS v1.5.00 - page 114 of 161
KNX Standard
Interworking
Datapoint Types
4.10.2 Datapoint Type Wind Speed with Status/Command

Format: 3 octets: U16Z8 3 MSB WindSpeed UUUUUUUU Encoding: See below Range: Unit: See below See below 2 LSB WindSpeed UUUUUUUU 1 Status Command ZZZZZZZZ
Datapoint Types ID: 203.101 Name: DPT_WindSpeed_Z Range: See below Unit: See below Usage: HVAC
Data fields WindSpeed
Description wind speed absolute value m/s
Unit / Range U16, 0,01 m/s resolution 0 km/h 200 km/h (and more) Z8
Status/Command
In case of a detected sensor failure the Status Flag Fault shall be set. This is a mandatory feature of this DPT. In this case in addition the reason of Fault may be encoded in the WindSpeed field (optional feature): see standard Z8 mechanism in 4.1.2. Standard Mode DPT_Value_Wsp (9.005 ), only WindSpeed without Z8 field.
4.10.3 Datapoint Type Sun Intensity with Status/Command

Format: 3 octets: U16Z8 3 MSB SunIntensity UUUUUUUU Encoding: See below Range: Unit: See below See below 2 LSB SunIntensity UUUUUUUU 1 Status Command ZZZZZZZZ
Datapoint Types ID: 203.102 Name: DPT_SunIntensity_Z Range: See below Unit: See below Usage: HVAC
AS v1.5.00 - page 115 of 161
KNX Standard
Data fields SunIntensity Description Sun intensity W/m2
Interworking
Unit / Range
Datapoint Types
U16, 0,05 W/m2 resolution 0 W/m2 1400 W/m2 (theoretical max. sun intensity) Z8
Status/Command
In case of a detected sensor failure the Status Flag Fault shall be set. This is a mandatory feature of this DPT. In this case in addition the reason of Fault may be encoded in the SunIntensity field (optional feature): see standard Z8 mechanism in 4.1.2. Standard Mode DPT_PowerDensity (9.022); only SunIntensity without Z8 field.
4.10.4 Datapoint Type HVAC Air Flow Absolute Value

Format: 3 octets: U16Z8 3 MSB HVACAirFlow UUUUUUUU Encoding: See below Range: Unit: See below See below 2 LSB HVACAirFlow UUUUUUUU 1 Status Command ZZZZZZZZ
Datapoint Types ID: 203.104 Data fields HVACAirFlow Name: DPT_HVACAirFlowAbs_Z Description Range: See below Unit: See below Usage: TU Unit / Range U16, 1m/h resolution 0 m/h to 65535 m/h standard Status/Command Z8
Status/Command
Standard Mode DPT_Value_AirFlow (9.009) in m3/h, only HVACAirFlow without Z8 field.
AS v1.5.00 - page 116 of 161
KNX Standard
Interworking
Datapoint Types
4.11 Data Type 16-Bit Signed Value with Status/Command

4.11.1 Datapoint Type HVAC absolute Temperature
Format: 3 octets: V16Z8 3 MSB Temp VVVVVVVV Encoding: See below Range: Unit: See below See below 2 LSB Temp VVVVVVVV 1 Status Command ZZZZZZZZ
Datapoint Types ID: 205.100 Name: DPT_TempHVACAbs_Z Range: See below Unit: See below Usage: HVAC
DPT_TempHVACAbs_Z
Data fields Temp Description temperature absolute value C Unit / Range V16, 0,02C resolution 273C to 655,34 C Z8
Status/Command
Exception handling In case of a detected sensor failure the Status Flag Fault shall be set. This is a mandatory feature of this DPT. In this case in addition the reason of Fault may be encoded in the Temp field (optional feature): see standard Z8 mechanism in 4.1.2. Standard Mode DPT_Value_Temp (9.001), without Z8 field.
AS v1.5.00 - page 117 of 161
KNX Standard
Interworking
Datapoint Types
4.11.2 Datapoint Type HVAC relative Temperature

Format: 3 octets: V16Z8 3 MSB Temp VVVVVVVV Encoding: See below Range: Unit: See below See below 2 LSB Temp VVVVVVVV 1 Status Command ZZZZZZZZ
Datapoint Types ID: 205.101 Name: Range: Unit: See below Usage: HVAC
DPT_TempHVACRel_Z See below
DPT_TempHVACRel_Z
Data fields Temp Description temperature relative value / offset K Unit / Range V16, 0,02 K resolution 273 K to 655,34 K Z8
Status/Command
Standard Mode DPT_Value_Tempd (9.002), without Z8 field.
4.11.3 Datapoint Type HVAC Air Flow Relative Value

Format: 3 octets: V16Z8 3 MSB HVACAirFlow VVVVVVVV Encoding: See below Range: Unit: See below See below 2 LSB HVACAirFlow VVVVVVVV 1 Status Command ZZZZZZZZ
Datapoint Types ID: 205.102 Name: DPT_HVACAirFlowRel_Z Range: See below Unit: See below Usage: TU
AS v1.5.00 - page 118 of 161
KNX Standard
Data fields HVACAirFlow Description
Interworking
Unit / Range
Datapoint Types
V16, 1m/h resolution 32768 m+/h to 32767 m/h standard Status/Command Z8
Status/Command
Standard Mode DPT_Value_AirFlow (9.009) in m3/h, only HVACAirFlow without Z8 field
4.12 Data Type 16-Bit Unsigned Value & 8-Bit Enum

4.12.1 Datapoint Type HVAC Mode & Time delay
Format: 3 octets: U16N8 3 MSB Delay Time UUUUUUUU Encoding: See below Range: Unit: See below See below 2 LSB Delay Time UUUUUUUU 1 HVACMode NNNNNNNN
Datapoint Types ID: 206.100 Name: DPT_HVACModeNext Range: See below Unit: See below Usage: HVAC
DPT_HVACModeNext:
Data fields Time Description delay time Unit / Range U16, 1 min resolution 1 min to 65 535 min 0 = undefined delay time *) enum. N8 Encoding absolute value N = {0, 255} 0 = Undefined*) 1 = Comfort 2 = Standby 3 = Economy 4 = Bldg.Prot 5 to 255: reserved
HVACMode
This DPT can be used to encode: the next active HVACMode after expiration of the delay time the currently active HVACMode which will be active during the delay time
-
AS v1.5.00 - page 119 of 161
KNX Standard
*)
Interworking
Datapoint Types
The following combinations are in principle possible: HVACMode defined and valid HVACMode but the delay time is undefined (unknown) undefined (unknown) HVACMode during a defined delay time in practice this combination is normally useless defined and valid HVACMode and delay time
Time
= 0 (Undefined) = 0 (Undefined) the content of the Datapoint is void / undefined = 0 (Undefined) = {1..4} >0 >0 = 0 (Undefined) = {1..4}
Allowed combinations and their usage/interpretation are defined at the level of Datapoint specifications
4.12.2 Datapoint Type DHW Mode & Time delay

Format: 3 octets: U16N8 3 MSB Delay Time UUUUUUUU Encoding: See below Range: Unit: See below See below 2 LSB Delay Time UUUUUUUU 1 DHWMode NNNNNNNN
Datapoint Types ID: 206.102 Name: DPT_DHWModeNext Range: See below Unit: See below Usage: DHW control
DPT_DHWModeNext:
Data fields Time Description delay time Unit / Range U16, 1 min resolution 1 min 65535 min 0 = undefined delay time *) enum. N8 Encoding absolute value N = {0, 255} 0 = Undefined*) 1 = LegioProtect 2 = Normal 3 = Reduced 4 = Off/FrostProtect 5-255: reserved
DHWMode
This DPT can be used to encode: - the next active DHWMode after expiration of the delay time - the currently active DHWMode which will be active during the delay time
AS v1.5.00 - page 120 of 161
KNX Standard
*)
Interworking
Datapoint Types
The following combinations are in principle possible: DHWMode = 0 (Undefined)
Time = 0 (Undefined)
the content of the Datapoint is void / undefined defined and valid DHWMode but the delay time is undefined = 0 (Undefined) = {1..4} (unknown) undefined (unknown) DHWMode during a defined delay time >0 = 0 (Undefined) in practice this combination is normally useless >0 = {1..4} defined and valid DHWMode and delay time Allowed combinations and their usage/interpretation are defined at the level of Datapoint specifications
4.12.3 Datapoint Type Occupancy Mode & Time delay

Format: 3 octets: U16N8 3 MSB Delay Time 2 LSB Delay Time 1 OccMode
UUUUUUUU UUUUUUUU UUUUUUUU Encoding: See below Range: Unit: See below See below
Datapoint Types ID: 206.104 Name: DPT_OccModeNext Range: See below Unit: See below Usage: TU
DPT_OccModeNext:
Data fields Time Description delay time Unit / Range U16, 1 Min resolution 1 min 65535 min 0 = next mode not available enum. N8 Encoding absolute value N = {0, 255} 0 = Occupied 1 = Standby 2 = Not occupied 3-255: reserved
OccMode
AS v1.5.00 - page 121 of 161
KNX Standard
Interworking
Datapoint Types
4.12.4 Datapoint Type Building Mode & Time delay

Format: 3 octets: N8U16 3 MSB Delay Time UUUUUUUU Encoding: See below Range: Unit: See below See below 2 LSB Delay Time UUUUUUUU 1 BuildingMode NNNNNNNN
Datapoint Types ID: 206.105 Name: DPT_BuildingModeNext Range: See below Unit: See below Usage: TU
DPT_BuildingModeNext:
Data fields Time Description delay time Unit / Range U16, 1 Min resolution 1 min 65535 min 0 = next mode not available enum. N8 Encoding absolute value N = {0, 255} 0 = Building in use 1 = Building not used 2 = Building Protection 3-255: reserved
BuildingMode
AS v1.5.00 - page 122 of 161
KNX Standard
Interworking
Datapoint Types
4.13 Data Type 8-Bit Unsigned Value & 8-Bit Set

4.13.1 Datapoint Type Status Burner Controller
Format: 2 octets: U8B8 2 PrelBurner UUUUUUUU Encoding: See below Range: Unit: See below See below 1 Attributes 00BBBBBB
Datapoint Types ID: 207.100 Name: DPT_StatusBUC Description Actual relative power % Bit # 0 1 2 3 4-7 validity of PrelBurnerField burner failure stage 1 or base stage active stage 2 / modulation active Range: See below Unit: See below Unit / Range U8, 0..100%, 1% resolution Bitset B8 true / false true / false on / off on / off default 0 Usage: HWH
Data fields PrelBurner Attributes - PrelBurnerValid - Fault - StatusStage1 - StatusStage2 reserved
Standard Mode 6 separate Datapoints

-
PrelBurner: DPT_RelPos_Valve (5.004) Fault: DPT_Bool (1.002) StatusStage1, StatusStage2: DPT_Switch (1.001)
AS v1.5.00 - page 123 of 161
KNX Standard
Interworking
Datapoint Types
4.13.2 Datapoint Type Locking Signal

Format: 2 octets: U8B8 2 PwrReduction UUUUUUUU Encoding: See below Range: Unit: See below See below 1 Attributes 000000BB
Datapoint Types ID: 207.101 Name: DPT_LockSign Range: See below Unit: See below Usage: HVAC
Data fields PwrReduction
Description Requested power reduction 0 % no reduction 100 % max. reduction Bit # 0 indicates if power reduction is necessary (validity of PwrReduction) 1 indicates whether overload is critical (e.g. too low boiler temp.) or uncritical (e.g. requested boiler temperature can not be provided but boiler temperature is above critical lower limit) 2-7
Unit / Range U8, 0 % 100 %, 1 % resolution Bitset B8, true / false 1= critical 0= uncritical default 0
Attributes - LockRequest - Type
reserved
4.13.3 Datapoint Type Boiler Controller Demand Signal

Format: 2 octets: U8B8 2 RelBurnerDem UUUUUUUU Encoding: See below Range: Unit: See below See below 1 Attributes 000000BB
Datapoint Types ID: 207.102 Name: DPT_ValueDemBOC Range: See below Unit: See below Usage: Burner control
AS v1.5.00 - page 124 of 161
KNX Standard
Data fields RelBurnerDem Attributes - Stage1Control - Stage2Control reserved Description
Interworking
Unit / Range
Datapoint Types
Relative demand %: for modulating burner Bit # 0 controls operation of stage 1 or base stage 1 controls stage 2 for two stage burner 2-7
U8, 0 % 100 %, 1 % resolution Bitset B8, 1= on / 0= off 1= on / 0= off default 0
4.13.4 Datapoint Type Actuator Position Demand

Format: 2 octets: U8B8 2 ActPosDem UUUUUUUU Encoding: See below Range: Unit: See below See below 1 Attributes 0000BBBB
Datapoint Types ID: 207.104 Name: DPT_ActPosDemAbs Range: See below Unit: See below Usage: HVAC
Data fields ActPosDe mAbs Attributes - DemValid - AbsLoadPriority - ShiftLoadPriority - EmergDem reserved
Description Absolute actuator position demand (setpoint, valve linearized) Bit # 0 1 2 3 4-7 Validity of ActPosDem false means also no demand absolute load priority shift load priority emergency demand (heating or cooling) for room frost protection or de-icing
Unit / Range U8, 0 % 100 %, 1 % resolution Bitset B8, true / false true / false true / false true / false default 0
Remark: depending on the usage of this DPT per Datapoint, some of the attributes (except DemValid) may not be supported and shall then be set to false (=0) Standard Mode: % value, without attributes The DPT in standard mode is depending on the Datapoint and is defined in the Datapoint specification. Two solutions are possible. Solution B) is preferred because there is no mapping of the % value. A) DPT_Scaling (5.001) Encoding 0 % 100 % full datatype value 0...255, i.e. 1 % = value 255/100! To be used in heating individual room control systems for backwards compatibility with actuator position demand in the EIB HWH ObIS.
KNX Standard
Interworking
Datapoint Types
B) DPT_Percent_U8 (5.004) Encoding 0 % 255 % full datatype value 0 255, i.e. 1 % = value 1 To be used in ventilation and cooling applications.
4.13.5 Datapoint Type Actuator Position Status

Format: 2 octets: U8B8 2 ActPos UUUUUUUU Encoding: See below Range: Unit: See below See below 1 Attributes 0000BBBB
Datapoint Types ID: 207.105 Name: DPT_StatusAct Range: See below Unit: See below Usage: HVAC
Data fields ActPos Attributes - Failure - ManualOverride - CalibrationMode - ValveKick reserved
Description actual actuator position Bit # 0 1 2 3 4-7 actuator has a failure actuator position is manually overridden actuator is currently in calibration mode valve is currently executing a valve kick
Unit / Range U8, 0 % 100 %, 1 % resolution Bitset B8, true/false true/false true/false true/false default 0
Standard Mode 5 separate Datapoints

-
ActPosition: DPT_Scaling (5.001)
ActStatus: 4 individual Boolean Datapoints
AS v1.5.00 - page 126 of 161
KNX Standard
Interworking
Datapoint Types
4.14 Data Type 16-Bit Signed Value & 8-Bit Set

4.14.1 Datapoint Type Heat Producer Manager Status
Format: 3 octets: V16B8 3 MSB TempFlow ProdSegmH VVVVVVVV Encoding: See below Range: Unit: See below See below 2 LSB TempFlow ProdSegmH VVVVVVVV 1 Attributes 000BBBBB
Datapoint Types ID: 209.100 Name: DPT_StatusHPM Range: See below Unit: See below Usage: HWH
Data fields
Description
Unit / Range V16, 273C to 655,34C 0,02C resolution Bitset B8
TempFlowProdSeg common flow temperature of ProdSegmH mH Attributes - TempFlowValid - Fault - SummerMode - OffPerm - NoHeatAvailable reserved Bit # 0 1 2 3 4 5-7 validity of TempFlowProdSegmH field some failure in boiler sequence: HPM itself or boiler(s) have a failure (mainly used for monitoring) boiler sequence switched off due to local summer/winter mode (mainly used for monitoring) boiler sequence is permanently off (manual switch or failure) boiler sequence is temporary not producing heat
true / false true / false true / false true / false true / false default 0
Standard Mode Separate Datapoints

-
TempFlowWaterProdSegmH: DPT_Value_Temp (9.001) Fault: DPT_Bool (1.002) SummerMode: DPT_Bool (1.002) OffPerm: DPT_Bool (1.002) NoHeatAvailable: DPT_Bool (1.002)
AS v1.5.00 - page 127 of 161
KNX Standard
Interworking
Datapoint Types
4.14.2 Datapoint Type Room Temperature Demand

Format: 3 octets: V16B8 3 MSB TempRoom Dem VVVVVVVV Encoding: See below Range: Unit: See below See below 2 LSB TempRoom Dem VVVVVVVV 1 Attributes 0000BBBB
Datapoint Types ID: 209.101 Name: Range: Unit: See below Unit / Range V16, 273C to 655,34C 0,02C resolution Bitset B8 true / false true / false true / false true / false default 0 Usage: HWH
DPT_TempRoomDemAbs See below Description requested room temperature setpoint
Data fields TempRoomDem Attributes - DemValid - AbsLoadPriority - ShiftLoadPriority - EmergDem reserved
Bit # 0 Validity of TempRoomDem false means also no demand 1 absolute load priority 2 shift load priority 3 emergency demand (heating or cooling) for room frost protection or de-icing 4-7
Remark: depending on the usage of this DPT per Datapoint, some of the attributes (except DemValid) may not be supported and shall then be set to false (=0) Standard Mode TempRoomDem only: DPT_Value_Temp (9.001). No support of load priority functionality.
AS v1.5.00 - page 128 of 161
KNX Standard
Interworking
Datapoint Types
4.14.3 Datapoint Type Cold Water Producer Manager Status

Format: 3 octets: V16B8 3 MSB TempFlow ProdSegmC VVVVVVVV Encoding: See below Range: Unit: See below See below 2 LSB TempFlow ProdSegmC VVVVVVVV 1 Attributes 0000BBBB
Datapoint Types ID: 209.102 Name: DPT_StatusCPM Range: See below Unit: See below Usage: VAC
Data fields TempFlowProdSegmC Attributes - TempFlowValid - Fault - OffPerm - NoCoolAvailable reserved
Description chilled water flow temperature in the cooling production segment Bit # 0 1 2 3 4-7 validity of TempFlowProdSegmH field some failure in the chiller permanently off (manual switch or failure) temporarily no cooling in the production segment available
Unit / Range V16, 273C to 655,34C 0,02C resolution Bitset B8 true / false true / false true / false true / false default 0
Standard Mode: separate Datapoints

-
TempFlowWaterProdSegmC: DPT_Value_Temp (9.001) Fault: DPT_Bool (1.002) OffPerm: DPT_Bool (1.002) NoCoolAvailable: DPT_Bool (1.002)
AS v1.5.00 - page 129 of 161
KNX Standard
Interworking
Datapoint Types
4.14.4 Datapoint Type Water Temperature Controller Status

Format: 3 octets: V16B8 3 MSB TempWater VVVVVVVV Encoding: See below Range: Unit: See below See below 2 LSB TempWater VVVVVVVV 1 Attributes 00000BBB
Datapoint Types ID: 209.103 Name: DPT_StatusWTC Range: See below Unit: See below Usage: HVAC
Data fields TempWater Attributes - TempWaterValid - Fault - CtrlStatus
Description actual temperature (flow or return) of the water temperature controller Bit # 0 1 2 validity of TempWater field some failure in the water temperature controller Controller status on: controller is working (default if not supported) off: controller is stopped; no control of water temperature
Unit / Range V16, 273C to 655,34C 0,02C resolution Bitset B8 true / false true / false on / off
reserved
3-7
default 0
Standard Mode: separate Datapoints TempWater: DPT_Value_Temp (9.001) Fault: DPT_Bool (1.002) CtrlStatus: DPT_Switch (1.001)
AS v1.5.00 - page 130 of 161
KNX Standard
Interworking
Datapoint Types
4.15 Data Type 16-Bit Signed Value & 16-Bit Set

4.15.1 Datapoint Type Consumer Flow Temperature Demand
Format: 4 octet; V16B16 4 MSB 3 LSB TempFlowDem TempFlowDem VVVVVVVV Encoding: See below Range: Unit: See below See below VVVVVVVV 2 MSB Attributes 0000BBBB 1 LSB Attributes BBBBBBBB
Datapoint Types ID: 210.100 Name: DPT_TempFlowWaterDemAbs Range: See below Unit: See below Usage: HVAC
Data fields TempFlowDem Attributes - DemValid - AbsLoadPriority - ShiftLoadPriority - MaxTempLimit - MinTempLimit - DHWReq - RoomCtrlReq - VentReq AuxAllSeasonReq - SystemPumpReq - EmergDem - DHWLegioReq reserved
Description flow temperature demand (setpoint) Bit # 0 1 2 3 4 5 6 7 8 9 10 11 12-15
Unit / Range V16, 273C to 655,34C 0,02C resolution Bitset B16 true / false true / false true / false true / false true / false true / false true / false true / false true / false true / false true / false true / false default 0
Validity of TempFlowDem false means also no demand absolute load priority shift load priority TempFlowDem contains max. temperature limit TempFlowDem contains min. temperature limit Heat demand from DHW for DHW preparation during summer (room heating off) demand from Room Heating or Cooling demand from Ventilation (Heating or Cooling) demand from auxiliary heat or cool consumer; all season request for water circulation in the primary distribution segment (common system pump on) emergency demand (heating or cooling) for room frost protection or de-icing demand from DHW while legionella function is active (can only be true if DHWReq = true)
Remark: depending on the usage of this DPT per Datapoint, some of the attributes (except DemValid) may not be supported and shall then be set to false (=0) Standard Mode The information of this DPT is not available in Standard Mode.
AS v1.5.00 - page 131 of 161
KNX Standard
Interworking
Datapoint Types
4.16 Data Type 8-Bit Unsigned Value & 8-Bit Enum

4.16.1 Datapoint Type EnergyDemWater
Format: 2 octets: U8N8 2 1 EnergyDem HVACContr Mod UUUUUUUU Encoding: see below Range: Unit: see below see below NNNNNNNN
Datapoint Types ID: 211.100 Name: Range: Unit: see below Usage: HVAC
DPT_EnergyDemWater see below
Data fields EnergyDem ContrModeAct
Description Energy demand of terminal unit controller Actual controller Mode
Unit / Range U8, 0 %..100 % 1 % resolution enum. N8 Encoding absolute value N = {0, 255} 0: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12 to 19: 20: 21-255: Auto Heat Morning Warmup Cool Night Purge Precool Off Test Emergency Heat Fan only Free Cool Ice reserved NoDem reserved
Standard Mode Splitting in 2 separate Datapoints: DPT_Percent_U8 (5.004) DPT_HVACContrMode (20.105)
AS v1.5.00 - page 132 of 161
KNX Standard
Interworking
Datapoint Types
4.17 Data Type 3x 16-Bit Signed Value

4.17.1 Datapoint Type 3x set of RoomTemperature Setpoint Shift values
Format: 6 octet; V16V16V16 6 MSB TempSetp ShiftComf VVVVVVVV 2 MSB TempSetp ShiftEco VVVVVVVV Encoding: see below Range: Unit: see below K 5 LSB TempSetp ShiftComf VVVVVVVV 1 LSB TempSetp ShiftEco VVVVVVVV 4 MSB TempSetp ShiftStdby VVVVVVVV 3 LSB TempSetp ShiftStdby VVVVVVVV
Datapoint Types ID: 212.100 Name: DPT_TempRoomSetpSetShift[3] Range: see below Unit: see below Usage: HVAC
Data fields
Description
Unit / Range V16, 655,34 K to 655,34 K 0,02C resolution V16, 655,34 K to 655,34 K 0,02C resolution V16, 655,34 K to 655,34 K 0,02C resolution
TempSetpShiftComf room temperature setpoint shift comfort (delta value) TempSetpShiftStdby room temperature setpoint shift standby (delta value) TempSetpShiftEco room temperature setpoint shift economy (delta value)
Standard Mode DPT_TempRoomSetpSetShiftF16[3] (222.101), float encoding.
AS v1.5.00 - page 133 of 161
KNX Standard
Interworking
Datapoint Types
4.17.2 Datapoint Type 3x set of RoomTemperature Absolute Setpoint values

Format: 6 octets: V16V16V16 6 MSB TempSetp Comf VVVVVVVV 2 MSB TempSetp Eco VVVVVVVV Unit: C 5 LSB TempSetp Comf VVVVVVVV 1 LSB TempSetp Eco VVVVVVVV 4 MSB TempSetp Stdby VVVVVVVV 3 LSB TempSetp Stdby VVVVVVVV
Datapoint Types ID: 212.101 Name: DPT_TempRoomSetpSet[3] Usage: HVAC
Data fields TempSetpComf TempSetpStdby TempSetpEco
Description room temperature setpoint comfort room temperature setpoint standby room temperature setpoint economy
Unit / Range V16, 273C to 655,34 C 0,02C resolution V16, 273C to 655,34 C 0,02C resolution V16, 273C to 655,34 C 0,02C resolution
Standard Mode DPT_TempRoomSetpSetF16[3] (222.100), float encoding
AS v1.5.00 - page 134 of 161
KNX Standard
Interworking
Datapoint Types
4.18 Data Type 4x 16-Bit Signed Value

4.18.1 Datapoint Type 4x set of RoomTemperature setpoints
Format: 8 octet; V16V16V16V16 8 MSB TempSetp Comf VVVVVVVV 4 MSB TempSetp Eco VVVVVVVV Encoding: see below Range: Unit: see below C 7 LSB TempSetp Comf VVVVVVVV 3 LSB TempSetp Eco VVVVVVVV 6 MSB TempSetp Stdby VVVVVVVV 2 MSB TempSetp BProt VVVVVVVV 5 LSB TempSetp Stdby VVVVVVVV 1 LSB TempSetp BProt VVVVVVVV
Datapoint Types ID: 213.100 Name: DPT_TempRoomSetpSet[4] Range: see below Unit: see below Usage: HVAC
Data fields TempSetpComf TempSetpStdby TempSetpEco TempSetpBProt
Description room temperature setpoint comfort room temperature setpoint standby room temperature setpoint economy room temperature setpoint building protection
Unit / Range V16, 273C to 655,34C 0,02C resolution V16, 273C to 655,34C 0,02C resolution V16, 273C to 655,34C 0,02C resolution V16, 273C to 655,34C 0,02C resolution
AS v1.5.00 - page 135 of 161
KNX Standard
Interworking
Datapoint Types
4.18.2 Datapoint Type 4x set of DHWTemperature setpoints

Format: 8 octet; V16V16V16V16 8 MSB TempSetp LegioProtect VVVVVVVV 4 MSB TempSetp Reduced VVVVVVVV Encoding: see below Range: Unit: see below C 7 LSB TempSetp LegioProtect VVVVVVVV 3 LSB TempSetp Reduced VVVVVVVV 6 MSB TempSetp Normal VVVVVVVV 2 MSB TempSetpOff/ FrostProtect VVVVVVVV 5 LSB TempSetp Normal VVVVVVVV 1 LSB TempSetpOff/ FrostProtect VVVVVVVV
Datapoint Types ID: 213.101 Name: DPT_TempDHWSetpSet[4] Range: see below Unit: see below Usage: HVAC DHW Unit / Range V16, 273C to 655,34C 0,02C resolution
Data fields TempSetpLegio Protect TempSetpNormal TempSetpReduced TempSetpOff/ FrostProtect
Description DHW temperature setpoint for LegioProtect operating mode
DHW temperature setpoint for Normal operating mode V16, 273C to 655,34C 0,02C resolution DHW temperature setpoint for Reduced operating V16, 273C to 655,34C mode 0,02C resolution DHW temperature setpoint for Off/FrostProtect V16, 273C to 655,34C operating mode 0,02C resolution
AS v1.5.00 - page 136 of 161
KNX Standard
Interworking
Datapoint Types
4.18.3 Datapoint Type 4x set of RoomTemperature setpoint shift values

Format: 8 octets: V16V16V16V16 8 MSB TempSetp ShiftComf VVVVVVVV 4 MSB TempSetp ShiftEco VVVVVVVV Unit: K 7 LSB TempSetp ShiftComf VVVVVVVV 3 LSB TempSetp ShiftEco VVVVVVVV 6 MSB TempSetp ShiftStdby VVVVVVVV 2 MSB TempSetp ShiftBProt VVVVVVVV 5 LSB TempSetp ShiftStdby VVVVVVVV 1 LSB TempSetp ShiftBProt VVVVVVVV
Datapoint Types ID: 213.102 Name: DPT_TempRoomSetpSetShift[4] Description room temperature setpoint shift comfort (delta value) room temperature setpoint shift standby (delta value) room temperature setpoint shift economy (delta value) room temperature setpoint shift building protection (delta value) Usage: HVAC Unit / Range V16, 655,34 K to 655,34 K 0,02 K resolution V16, 655,34 K to 655,34 K 0,02 K resolution V16, 655,34 K to 655,34 K 0,02 K resolution V16, 655,34 K to 655,34 K 0,02 K resolution
Data fields TempSetpShiftComf TempSetpShiftStdby TempSetpShiftEco TempSetpShiftBProt
4.19 Data Type 16-Bit Signed & 8-Bit Unsigned Value & 8-Bit Set
4.19.1 Datapoint Type Heat Prod. Manager Demand Signal
Format: 4 octet; V16U8B8 4 MSB 3 LSB TempFlowDem TempFlowDem VVVVVVVV Encoding: See below Range: Unit: See below See below VVVVVVVV 2 RelDemLimit UUUUUUUU 1 Attributes 00BBBBBB
Datapoint Types ID: 214.100 Name: DPT_PowerFlowWaterDemHPM Range: See below Unit: See below Usage: HWH
AS v1.5.00 - page 137 of 161
KNX Standard
Data fields TempFlowDem RelDemLimit Attributes - TempFlowDemValid - Stage1Enabled - Stage1Forced - Stage2Enable - Stage2Forced - BoilerEnable reserved Description
Interworking
Datapoint Types
Unit / Range V16, 273C to 655,34C 0,02C resolution U8, 0 % to 100 % 1 % resolution Bitset B8 true / false 1= Enabled 0= Disabled 1= Forced 0= Auto 1= Enabled 0= Disabled 1= Forced 0= Auto 1= Enabled 0= Disabled default 0
flow temperature demand / requested boiler temperature Relative demand %: max. limitation for modulating burner, used in boiler Bit # 0 Validity of TempFlowDem false means also no demand 1 if enabled, stage 1 can be activated by the BoC forced or auto 2 - if forced: stage 1 is generally on - if auto: stage 1 is activated if necessary according to boiler temperture 3 stage 2 control: see stage 1 4 5 6-7 stage 2 control: see stage 1 boiler pump is on (water flow) must be enabled before burner is turned on
4.19.2 Datapoint Type Cold Water Prod. Manager Demand Signal

Format: 4 octet; V16U8B8 4 MSB 3 LSB TempFlowDem TempFlowDem VVVVVVVV Encoding: See below Range: Unit: See below See below VVVVVVVV 2 RelDemLimit UUUUUUUU 1 Attributes 00000BBB
Datapoint Types ID: 214.101 Name: DPT_PowerFlowWaterDemCPM Range: See below Unit: See below Usage: VAC
AS v1.5.00 - page 138 of 161
KNX Standard
Data fields TempFlowDem RelDemLimit Description
Interworking
Datapoint Types
Unit / Range V16, 273C to 655,34C 0,02C resolution U8, 0 % 100 %, 1 % resolution Bitset B8 true / false true / false true / false default 0
chilled water flow temperature demand This value sets the relative demand limit in percent, used in chiller sequences controlled by the Cold Water Production Manager CPM (0% = no stages, 100% = all stages) Bit # 0 validity of chilled water flow temperature false means also no demand 1 validity of relative demand limit 2 chilled water pump enabled (must be enabled before chiller compressor is started, only applicable when chilled water pump available) 3-7
Attributes TempFlowDemValid RelDemLimitValid Chiller Enable reserved
4.20 Data Type V16 U8 B16

4.20.1 Datapoint Type Status Boiler Controller
Format: 5 octet; V16U8B16 5 MSB TempBoiler VVVVVVVV Encoding: See below Range: Unit: See below See below 4 LSB TempBoiler VVVVVVVV 3 PrelBurner UUUUUUUU 2 MSB Attributes 0000BBBB 1 LSB Attributes BBBBBBBB
Datapoint Types ID: 215.100 Name: DPT_StatusBOC Range: See below Unit: See below Usage: HWH
AS v1.5.00 - page 139 of 161
KNX Standard
Data fields TempBoiler PrelBurner Attributes TempBoilerValid PrelBurnerValid Fault SummerMode OffPerm NoHeatAvailable StatusBurnerStage1Enable StatusBurnerStage2Enable ReqNextStage
Interworking
Description Boiler temperature Actual relative power of the burner Bit # 0 1 2 3 4 5 6 7 8 validity of TempBoiler field validity of PrelBurner field boiler failure boiler switched off due to local summer/winter mode permanently off (manual switch or failure) boiler is temporary not providing heat stage 1 or base stage enabled stage 2 / modulation enabled for boiler with two stage burner: power limit of stage 1 is reached, HPM is requested to enable stage 2 power limit of boiler is reached, HPM is requested to enable next boiler in cascade boiler is in principle available but other boilers should be used with preference ChimneySweep function active Unit / Range
Datapoint Types
V16, 273C to 655,34C 0,02C resolution U8, 0 % to 100 % 1 % resolution Bitset B16 true / false true / false true /false true / false true / false true / false enable (=1) / disable (=0) enable / disable true / false
ReqNextBoiler ReducedAvailability ChimneySweep reserved
9 10 11 12-15
true / false true / false true / false default 0
AS v1.5.00 - page 140 of 161
KNX Standard
Standard Mode
Interworking
Datapoint Types
The information of this Datapoint Type is in Standard Mode available through DPs with different DPTs as follows. TempBoiler: DPT_Value_Temp (9.001) PrelBurner: DPT_RelPos_Valve (5.004) Fault: DPT_Bool (1.002) StatusBurnerStage1Enable: DPT_Enable (1.003) StatusBurnerStage2Enable: DPT_Enable (1.003)
4.20.2 Datapoint Type Status Chiller Controller

Format: 5 octet; V16U8B16 5 MSB TempChiller VVVVVVVV Encoding: See below Range: Unit: See below See below 4 LSB TempChiller VVVVVVVV 3 PrelChiller UUUUUUUU 2 MSB Attributes 00000000 1 LSB Attributes BBBBBBBB
Datapoint Types ID: 215.101 Name: DPT_StatusCC Range: See below Unit: See below Usage: VAC Unit / Range V16, 273 to 655,34C 0,02C resolution U8, 0 % 100 %, 1 % resolution Bitset B16 true / false true / false true /false true / false true / false true / false true / false true / false default 0
Data fields TempChiller PrelChiller Attributes TempChillerValid PrelChillerValid Status Fault OffPerm ReqNextStage ReqNextChiller ReducedAvailability reserved
Description chilled water flow temperature Actual relative power of the chiller (stages in percent) Bit # Bitset containing status info 0 validity of TempChiller field 1 validity of PrelChiller field 2 chiller running status 3 chiller failure 4 permanently off (manual switch of failure) 5 power limit of current stage is reached, next stage required 6 power limit of chiller is reached, next chiller required 7 reduce availability, chiller is in principle available, but preferably an other chiller is used 8-15
AS v1.5.00 - page 141 of 161
KNX Standard
Standard Mode
Interworking
Datapoint Types
The information of this Datapoint Type is in Standard Mode available through DPs with different DPTs as follows. TempChiller: PrelChiller: Fault: StatusChiller: DPT_Value_Temp (9.001) DPT_RelPos_Valve (5.004) DPT_Bool (1.002) DPT_Bool (1.002)
4.21 Data Type U16U8N8B8

4.21.1 Datapoint Type Heat Producer Specification
Format: 5 octet; U16U8N8B8 5 MSB Pnom UUUUUUUU Encoding: See below Range: Unit: See below See below 4 LSB Pnom UUUUUUUU 3 BstageLimit UUUUUUUU 2 BurnerType NNNNNNNN 1 FuelType 00000BBB
Datapoint Types ID: 216.100 Name: DPT_SpecHeatProd Range: See below Unit: See below Usage: HWH
Data fields Pnom BstageLimit BurnerType
Description Nominal power of burner/boiler relative power limit % of stage 1 resp. base stage void (value 100%) for 1stage burner 1 stage, 2 stage, modulating burner
Unit / Range U16, 0 kW to 65535 kW resolution 1 kW U8, 0 % to 100 %, 1 % resolution enum. N8 Encoding absolute value N = {0, 255} 0: reserved 1: 1 stage 2: 2 stage 3: modulating 4 to 255: reserved Bitset B8 true / false true / false true / false default 0
FuelType - Oil - Gas - SolidState reserved
Bit # 0 oil fuel supported 1 gas fuel supported 2 solid state fuel supported 3-7
AS v1.5.00 - page 142 of 161
KNX Standard
Interworking
Datapoint Types
4.22 Data Type 16-Bit Unsigned Value & 16-Bit Signed Value
4.22.1 Datapoint Type Next Temperature & Time Delay
Format: 4 octet; U16V16 4 MSB Delay Time UUUUUUUU Encoding: See below Range: Unit: See below See below 3 LSB Delay Time UUUUUUUU 2 MSB Temp VVVVVVVV 1 LSB Temp VVVVVVVV
Datapoint Types ID: 220.100 Name: DPT_TempHVACAbsNext Range: See below Unit: See below Usage: TU, DEH
Data fields DelayTime
Description Time delay
Unit / Range U16, 1Min resolution 1 min to 65535 min 0: next temperature value not available V16, 0,02C resolution -273C to 655,34C
Temp
absolute temperature value
AS v1.5.00 - page 143 of 161
KNX Standard
Interworking
Datapoint Types
4.23 Data Type 3x 16-Float Value

4.23.1 Datapoint Type 3x set of RoomTemperature Setpoint Values
Format: 6 octet; F16F16F16 6 MSB TempSetp Comf FFFFFFFF 2 MSB TempSetp Eco FFFFFFFF 5 LSB TempSetp Comf FFFFFFFF 1 LSB TempSetp Eco FFFFFFFF 4 MSB TempSetp Stdby FFFFFFFF 3 LSB TempSetp Stdby FFFFFFFF
Encoding: see below For all fields Comfort, Standby and Economy, only the value 7FFFh shall be used to denote invalid data. Range: Unit: see below C
Datapoint Types ID: 222.100 Name: DPT_TempRoomSetpSetF16[3] Range: see below Unit: see below Usage: HVAC
Data fields TempSetpComf TempSetpStdby TempSetpEco
Description room temperature setpoint comfort room temperature setpoint standby room temperature setpoint economy
Unit / Range -273C to 670 760C -273C to 670 760C -273C to 670 760C
Similar to DPT_TempRoomSetpSet[4] (213.100) but only 3 values with float encoding
AS v1.5.00 - page 144 of 161
KNX Standard
Interworking
Datapoint Types
4.23.2 Datapoint Type 3x set of RoomTemperature Setpoint Shift Values

Format: 6 octet; F16F16F16 6 MSB TempSetp ShiftComf FFFFFFFF 2 MSB TempSetp ShiftEco FFFFFFFF 5 LSB TempSetp ShiftComf FFFFFFFF 1 LSB TempSetp ShiftEco FFFFFFFF 4 MSB TempSetp ShiftStdby FFFFFFFF 3 LSB TempSetp ShiftStdby FFFFFFFF
Encoding: see below For all fields Comfort, Standby and Economy, only the value 7FFFh shall be used to denote invalid data. Range: Unit: see below K
Datapoint Types ID: 222.101 Name: Range: Unit: see below Usage: HVAC
DPT_TempRoomSetpSetShiftF16[3] see below
Data fields TempSetpShiftComf TempSetpShiftStdby TempSetpShiftEco
Description room temperature setpoint shift comfort (delta value) room temperature setpoint shift standby (delta value)
Unit / Range -670 760 K670 760 K -670 760 K670 760 K
room temperature setpoint shift economy (delta value) -670 760 K670 760 K
Same as DPT_TempRoomSetpSetShift[3] (212.100) but with float encoding
AS v1.5.00 - page 145 of 161
KNX Standard
Interworking
Datapoint Types
4.24 Data Type V8 N8 N8

4.24.1 Datapoint Type EnergyDemAir
Format: 3 octets: V8N8N8 3 2 EnergyDem HVACContr Mod VVVVVVVV Encoding: see below Range: Unit: see below see below NNNNNNNN 1 HVACEmerg Mode NNNNNNNN
Datapoint Types ID: 223.100 Name: DPT_EnergyDemAir Range: see below Unit: see below Usage: HVAC
Data fields EnergyDem
Description Energy demand of terminal unit controller - 100 %: full heating demand 100 %: full cooling demand Actual controller Mode
Unit / Range
V8, -100 % to 100 %

1 % resolution enum. N8 Encoding absolute value N = {0, 255} 0: Auto 1: Heat 2: Morning Warmup 3: Cool 4: Night Purge 5: Precool 6: Off 7: Test 8: Emergency Heat 9: Fan only 10: Free Cool 11: Ice 12 to 19: reserved 20: NoDem 21 to 255: reserved enum. N8 Encoding absolute value N = {0, 255} 0: Normal 1: EmergPressure 2: EmergDepressure 3: EmergPurge 4: EmergShutdown 5: EmergFire 6 to 255: reserved
ContrModeAct
HVACEmergMode
Acutal HVAC Emergency Mode
AS v1.5.00 - page 146 of 161
KNX Standard
Standard Mode Splitting in 3 separate Datapoints: DPT_Percent_V8 (6.001) DPT_HVACContrMode (20.105) DPT_HVACEmergMode (20.106)
Interworking
Datapoint Types
4.25 Data Type V16V16N8N8

4.25.1 Datapoint Type TempSupplyAirSetpSet
Format: 6 octet; V16V16N8N8 6 MSB TempSetp Cooling VVVVVVVV 2 HVACContr Mod NNNNNNNN Encoding: see below Range: Unit: see below see below 5 LSB TempSetp Cooling VVVVVVVV 1 HVACEmerg Mode NNNNNNNN 4 MSB TempSetp Heating VVVVVVVV 3 LSB TempSetp Heating VVVVVVVV
Datapoint Types ID: 224.100 Name: DPT_TempSupplyAirSetpSet Range: see below Unit: see below Usage: HVAC
Data fields TempSetpCooling TempSetpHeating
Description Supply air temperature cooling setpoint Supply air temperature heating setpoint
Unit / Range V16, 273C to 655,34C 0,02C resolution V16, 273C to 655,34C 0,02C resolution
AS v1.5.00 - page 147 of 161
KNX Standard
Data fields ContrModeAct
Interworking
Description Actual controller Mode
Datapoint Types
Unit / Range enum. N8 Encoding absolute value N = {0, 255} 0: Auto 1: Heat 2: Morning Warmup 3: Cool 4: Night Purge 5: Precool 6: Off 7: Test 8: Emergency Heat 9: Fan only 10: Free Cool 11: Ice 12 to 19: reserved 20: NoDem 21 to 255: reserved enum. N8 Encoding absolute value N = {0, 255} 0: Normal 1: EmergPressure 2: EmergDepressure 3: EmergPurge 4: EmergShutdown 5: EmergFire 6 to 255: reserved
HVACEmergMode
Acutal HVAC Emergency Mode
AS v1.5.00 - page 148 of 161
KNX Standard
Interworking
Datapoint Types
5 Datapoint Types for Load Management

No Datapoint Types for Load Management have been specified so far. This clause is a placeholder.
AS v1.5.00 - page 149 of 161
KNX Standard
Interworking
Datapoint Types
6 Datapoint Types for Lighting

Format:
Datapoint Types ID: 20.600 Name: Encoding: Range: Use: FB DPT_Behaviour_Lock_Unl field1 = Behaviour_Lock_Unlock [0 6] ock 0 = off 1 = on 2 = no change 3 = value according additional parameter 4 = memory function value 5 = updated value 6 = value before locking 7 255 = reserved DPT_Behaviour_Bus_Pow field1 = er_Up_Down Behaviour_Bus_Power_Up_Down 0 = off 1 = on 2 = no change 3 = value according additional parameter 4 = last (value before bus power down) 5 255 = reserved [0 4]
20.601
FB
AS v1.5.00 - page 150 of 161
KNX Standard
Interworking
Datapoint Types
6.2
6.2.1
Datapoint Types U8U8U8

DPT_Colour_RGB
3 octets: U8U8U8 3 MSB R 2 G 1 LSB B
Format:
UUUUUUUU UUUUUUUU UUUUUUUU
Encoding: All values binary encoded. Range:: Unit: Resol.: PDT: R, G, B: 0 to 255 None 1 PDT_GENERIC_03
Datapoint Types
ID: 232.600 Name: DPT_Colour_RGB Range: R: G: B: 0 to 255 0 to 255 0 to 255 Resol.: R: G: B: 1 1 1 Use: G
NOTE 15
This is useful for simple colour control.
NOTE 16 Because of the device dependent interpretation of RGB, this coding is only suitable for point-to-point communication, this is, if there is only a single receiver. NOTE 17 This DPT specification does not tend to give a definition of RGB. Aspects as linearity and influence on brightness are the scope of the specification of a distributed application or a FB specification. For a definition of RGB, please refer to ISO/IEC 8632-1 Information technology Computer graphics Metafile for the storage and transfer of picture description information Part 1: Functional specification
AS v1.5.00 - page 151 of 161
KNX Standard
Interworking
Datapoint Types
7 Datapoint Types for System

Format:
Datapoint Types ID: 20.1000 Name: DPT_CommMode Encoding: Range: Use: System field1 = CommMode See reference Reference: DPT_CommMode shall be encoded according the specification of PID_COMM_MODE in [01]. field1 = AddInfoType 00h = reserved 01h = PL medium Domain Address 02h = RF Control Octet and Serial Number or DoA 03h = Busmonitor Error Flags 04h = Relative timestamp 05h = Time delay 06h = Extended Relative Timestamp 07h = BiBat information 08h FEh = reserved, shall not be used FFh = reserved for future system extensions (ESC code)
20.1001
DPT_AddInfoTypes
System
20.1002
DPT_RF_ModeSelect
field1 = RF_ModeSelect [00h 02h] System 00h = asynchronous 01h = asynchronous + BiBat Master 02h = asynchronous + BiBat Slave 03h FFh = reserved, shall not be used
AS v1.5.00 - page 152 of 161
KNX Standard
Datapoint Types ID: 20.1003 Name: DPT_RF_FilterSelect
Interworking
Datapoint Types
Encoding:
Range:
Use:
field1 = RF_FilterSelect [00h 03h] System 00h = no filtering, all supported received frames shall be passed to the cEMI client using L_Data.ind 01h = filtering by Domain Address 02h = filtering by KNX Serial Number table 03h = filtering by Domain Address and by Serial number table 04h FFh = reserved, shall not be used
7.2
7.2.1
Datapoint Types B8
Datapoint Type RF Communication Mode Info
1 octet: B8 1 RFCommInfo b7b6b5b4b3b2b1b0
Format:
encoding
bbbbbbbb
Encoding: See below Range:: Unit: Resol.: PDT: ID: 21.1000 See below none (not applicable) PDT_BITSET8 Name: DPT_RF_ModeInfo (alt: PDT_GENERIC_01) Encoding, range: See below Use: System
Datapoint Types
Bit b0 b1 b2
Data fields Asynchronous BiBat Master BiBat Slave
Description asynchronous mode support BiBat Master mode supported BiBat Slave mode supported reserved, set to 0
Encoding (0 = value not allowed) 1 = true 0 1 0 1 = false = true = false = true
Unit
Range
none {0,1} none {0,1} none {0,1} n.a. n.a.
b3b7 reserved
not applicable
AS v1.5.00 - page 153 of 161
KNX Standard
Interworking
Datapoint Types
7.2.2
Format:
Datapoint Type cEMI Server Supported RF Filtering Modes

1 octet: B8 1 RFFilterInfo b7b6b5b4b3b2b1b0
encoding
bbbbbbbb
Encoding: See below Range:: Unit: Resol.: PDT: ID: 21.1001 See below none (not applicable) PDT_BITSET8 Name: DPT_RF_FilterInfo (alt: PDT_GENERIC_01) Encoding, range: See below Use: System
Datapoint Types
Bit b0 b1 b2
Data fields DoA KNX SN DoA and KNX SN
Description Filtering by Domain Address supported
Encoding 0 1 = false = true = false = true = false = true
Unit
Range
none {0,1} none {0,1} none {0,1}
Filtering by KNX Serial Number 0 supported 1 Filtering by Domain Address and KNX Serial Number supported reserved, set to 0 0 1
b3b7 reserved
not applicable
n.a.
n.a.
AS v1.5.00 - page 154 of 161
KNX Standard
Interworking
Datapoint Types
7.2.3
Format:
Datapoint Type Channel Activation for 8 channels

1 octet: B8 1 Channel Activation b7 b6 b5 b4 b3 b2 b1 b0
encoding
b b b b b b b b PDT_BITSET8 (alt: PDT_GENERIC_01)
PDT:
Datapoint Types ID: 21.1010 Name: DPT_Channel_Activation_8 Encoding, range: See below Use: System
Bit bn (n = 0 to 7)
Data fields Activation state of channel n+1.
Description
Encoding
Unit
Range
Indicates the acti- 0 = The visual effect of channel vation state of this n+1 is inactive. channel n+1 1 = The visual effect of channel n+1 is active.
none {0,1}
7.3
7.3.1
Datatype B16
Datapoint Type Media
2 octets: B16 2 MSB Media b15b14b13b12b11b10b9B8b7b6b5b4b3b2b1b
0
Format:
1 LSB
encoding
bbbbbbbb bbbbbbbb
Encoding: See below Range:: Unit: Resol.: PDT: See below none not applicable PDT_BITSET16 (alt: PDT_GENERIC_02)
AS v1.5.00 - page 155 of 161
KNX Standard
Datapoint Types ID: Name: Bit Name:
Interworking
Datapoint Types
Meaning
Coding: 0 0 = false 1 = true 0 = false 1 = true 0 0 = false 1 = true default 0
Use: System
22.1000 DPT_Media
b0 (reserved) reserved b1 TP1 b2 PL110 TP1 is supported PL110 is supported
b3 (reserved) reserved b4 RF b5 b15 none RF is supported reserved
7.3.2
Format:

2 octets: B16 2 MSB Channel Activation b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0 b b b b b b b b (alt: PDT_GENERIC_02) 1 LSB
encoding
b b b b b b b b PDT_BITSET16
PDT:
Datapoint Types ID: 22.1010 Bit Name: DPT_Channel_Activation_16 Data fields Encoding, range: See below Encoding 0 1 = = The visual effect of channel n+1 is inactive. The visual effect of channel n+1 is active. Use: System Unit Range
Description Indicates the activation state of this channel n+1
bn Activation state of (n = 0 to 15) channel n+1.
none {0,1}
AS v1.5.00 - page 156 of 161
KNX Standard
Interworking
Datapoint Types
7.4
Datatype U4U4
1 octet: U4U4 1 Busy Nak
Format:
UUUUUUUU
Encoding: All field values binary encoded. Range: Unit: Resol.: PDT: See below. none not applicable PDT_GENERIC_01
Datapoint Types ID: 25.1000 Name: DPT_DoubleNibble Field: Busy Nak Description Number of busy repetitions. Number of inack repetitions. Range: [0 3] [0 3] Use: System
7.5
7.5.1
Datapoint Types B24

3 octets: B24 3 MSB 2 Channel Activation b23 b22 b21 b20 b19 b18 b17 b16 b15 b14 b13 b12 b11 b10 b9 b8 b b b b b b b b b7 b6 b5 b4 b3 b2 b1 b0 b b b b b b b b 1 LSB
Format:
encoding
b b b b b b b b PDT_GENERIC_03
PDT:
Datapoint Types ID: 30.1010 Bit Name: DPT_Channel_Activation_24 Data fields Encoding, range: See below Encoding 0 1 = = The visual effect of channel n+1 is inactive. The visual effect of channel n+1 is active. Use: System Unit Range
Description Indicates the activation state of this channel n+1
bn Activation state of (n = 0 to 23) channel n+1.
none {0,1}
AS v1.5.00 - page 157 of 161
KNX Standard
Interworking
Datapoint Types
7.6
Datapoint Type MBus Address

8 octets: U16U32U8N8 8 MSB
MSB octet nr.
Format:
7 ManufactID
LSB MSB
5 IdentNumber
field names encoding octet nr. field names encoding
UUUUUUUU UUUUUUUU UUUUUUUU UUUUUUUU UUUUUUUU 3

LSB
2 Version
1 LSB Medium
UUUUUUUU UUUUUUUU NNNNNNNN
Encoding: All values binary encoded. PDT: PDT_GENERIC_08 Datapoint Types ID: 230.1000 Name: DPT_MBus_Address Use: 7.6.1 Meter ing
Data fields ManufactID IdentNumber Version Medium
Description Manufacturer identification Identification number Device Version Measured medium
Unit / Range According to M-Bus manufacturer codes. Full range, encoding is manufacturer specific. Full range, manufacturer specific. Enum according to MBus, See EN 13757-3 and Table 1 Supported physical media in Part 10/3 RF metering protocol.
AS v1.5.00 - page 158 of 161
KNX Standard
Interworking
Datapoint Types
8 Parameter Types
Name
PART_Switch_Value PART_Boolean PART_UpDown_Action PART_Invert PART_Logical PART_Scene_Value PART_Blind_Mode PART_OnOff_Action PART_Alarm_Reaction PART_Scene_Number PART_Byte_Value PART_COV_Lux PART_Cycle_Time PART_Time_Delay PART_Prewarning_Delay PART_Adaptive_Selection PART_Adjustable_Selection PART_Light_Value PART_Render_Value PART_Date_Time PART_UpDown_Switch_Action PART_PB_Action_HVAC PART_PB_Action_HVAC_Extended PART_Dimming_Value PART_Input_Connected
Size
1 bit 1 bit 1 bit 1 bit 1 bit 1 bit 1 bit 2 bit 2 bit 6 bit 1 octet 2 octets 1 octet 1 octet 1 octet 1 octet
1 1 1 1 1 1 1 1 1 1
Coding
DPT_Switch DPT_Bool DPT_UpDown (1.001) (1.002) (1.008) (1.012) (1.021) (1.022) (1.023) (23.001) (23.002) (17.001)
1 1 1 1 1 1 1
Range
As in DPT. As in DPT. As in DPT. As in DPT. As in DPT. As in DPT. As in DPT. As in DPT. As in DPT. [0 7] As in DPT. {5, 8, 9, 10, 13, 15} As in DPT. {0, 6, 8, 10} Prio: As in DPT. Size: {001b, 010b, 011b} As in DPT. 0 = none As in DPT. As in DPT. As in DPT. As in DPT. As in DPT. As in DPT. As in DPT. All 4 bits {0,1}
DPT_Invert
DPT_LogicalFunction DPT_Scene_AB DPT_ShutterBlinds_Mode DPT_OnOffAction DPT_Alarm_Reaction DPT_SceneNumber Value DPT_Value_Lux (9.004) DPT_Time_Delay (20.013) DPT_Time_Delay (20.013) DPT_Time_Delay (20.013) DPT_Adaptive_Selection (228.1000)
1 1 1
1 octet
1
DPT_Value_1_Ucount
(5.010)
1 1
2 octets 2 octets 8 octets 2 bit 2 bit 3 bit 8 bit 4 bit
(7.013) DPT_Value_2_Ucount (7.001) DPT_DateTime (19.001) DPT_UpDown_Action (23.003) DPT_HVAC_PB_Action (23.102) DPT_HVAC_PB_Action_Extended
1 1 1 1 1
DPT_Brightness
DPT_Scaling (5.001) No DPT is defined. Coding: for bit 0 (lsb) to bit 3 bit n = 0: Input n is not connected bit n = 1: Input n is connected
AS v1.5.00 - page 159 of 161
KNX Standard
Interworking
Datapoint Types
Appendix A
(normative)
DPT_HVACStatus
DPT_HVACStatus is a non-standard DPT that is used by an HVAC Room controller to report the currently set HVAC Mode by means of a status/diagnostic Datapoint. The use of the possible DPTs to this purpose shall comply with Table 6. Table 6 Use conditions of DPT_HVACStatus and DPT_StatusRHCC
DPT DPT_HVACStatus (Eberle status octet) DPT_StatusRHCC
a)
Until April 2010 may

a)
After April 2010 may shall
may a)
At least one of DPT_HVACStatus or DPT_StatusRHCC shall be used.
It may use the following non-standardised but common coding, sometimes referred to as the Eberle status octet (but only until April 2010, if this DPT is the only status/diagnostic Datapoint included in the respective application for this purpose).
Format:
1 octet: B8 1 Attributes b7b6b5b4b3b2b1b0
encoding
bbbbbbbb not applicable PDT_BITSET8 Name: DPT_HVACStatus Description Indicates whether comfort mode is active or not Indicates whether standby mode is active or not Indicates whether night mode is active or not Indicates whether frost/heat protection is active or not Indicates whether dew point mode is active or not Indicates whether the controller is heating or cooling (alt: PDT_GENERIC_01) Encoding: See below Range: See below Encoding 0 = false 1 = true 0 = false 1 = true 0 = false 1 = true 0 = false 1 = true 0 = false 1 = true 0 = cooling 1 = heating Unit none none none none none none Use: HVAC Range {0,1} {0,1} {0,1} {0,1} {0,1} {0,1}
Resol.: PDT: ID: --
Datapoint Types
Data fields Bit b0 b1 b2 b3 b4 b5 Attributes Comfort Standby Night Frost/Heat protection Dew Point Heat/Cool
AS v1.5.00 - page 160 of 161
KNX Standard
Data fields b6 b7 Description
Interworking
Encoding 0 = active 1 = inactive 0 = inactive 1 = active
Datapoint Types
Unit none none Range {0,1} {0,1}
Controller Status Indicates whether the controller is active or inactive Frost alarm Indicates whether the frost alarm is active
AS v1.5.00 - page 161 of 161

03 - 07 - 02 Datapoint Types v1.5.00 As

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

03 - 07 - 02 Datapoint Types v1.5.00 As

Încărcat de

Drepturi de autor:

Formate disponibile

KNX Standard

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 1 of 161

v1.4 AS v1.4.01 AS v1.5.00 AS

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 2 of 161

Filename: Version: Status: Savedate: Number of pages:

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 3 of 161

Copyright 1998 - 2010, KNX Association

Copyright 1998 - 2010, KNX Association

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 7 of 161

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 8 of 161

Subtype ranges for Datapoint Type Identifiers

reserved for future use

managed by WGI Reserved. These DPT-IDs shall not be used.

Reserved Manufacturer specific

1200 50 999 60 000

manufacturer specific extensions a

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 9 of 161

Datapoint Type specification style

Numbers in suffix denote the length of a field in bit.

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 10 of 161

The transmission of DPT encoded data on the bus

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 11 of 161

Copyright 1998 - 2010, KNX Association

Copyright 1998 - 2010, KNX Association

Copyright 1998 - 2010, KNX Association

Copyright 1998 - 2010, KNX Association

Copyright 1998 - 2010, KNX Association

Copyright 1998 - 2010, KNX Association

DPT_Locale_ASCII DPT_Colour_RGB DPT_LanguageCodeAlpha2_ASCII DPT_RegionCodeAlpha2_ASCII

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 18 of 161

3 Datapoint Types for common use

Range: Unit: Resol.: PDT:

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 19 of 161

1 bit: B1 1 b B b = {0,1} None. (not applicable) PDT_BINARY_INFORMATION (alt: PDT_UNSIGNED_CHAR)

Range: Unit: Resol.: PDT:

Copyright 1998 - 2010, KNX Association

field names encoding

Range: Unit: Resol.: PDT:

No control No control Control. Function value 0 Control. Function value 1

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 21 of 161

Datapoint Types B1U3

Range: Unit: Resol.: PDT:

001b111b: Step Number of intervals = 2^(stepcode-1) Break

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 22 of 161

octet nr field names encoding

Range: Unit: Resol.: PDT:

Copyright 1998 - 2010, KNX Association

AS v1.5.00 - page 23 of 161

Datapoint Types Character Set

field names encoding