diff --git a/static/data/telegram_metadata.json b/static/data/telegram_metadata.json
index 9d64236..112de95 100644
--- a/static/data/telegram_metadata.json
+++ b/static/data/telegram_metadata.json
@@ -1,6 +1,6 @@
 {
   "0x0001": {
-    "name": "ELECTRONICS-MODULE PRODUCTION INFORMATION BLOCK",
+    "name": "Electronics-Module Production Information Block",
     "usedIn": "Various controllers, thermostats and boilers",
     "description": "This block contains production information of the *electronics module* hardware (e.g. ACU-LO, ACU-MH, HRV_CU, ...).",
     "class": "Const",
@@ -10,7 +10,7 @@
     "type": "info"
   },
   "0x0002": {
-    "name": "MODULE IDENTIFICATION BLOCK",
+    "name": "Module Identification Block",
     "usedIn": "Various controllers, thermostats and boilers",
     "description": "This block is used to universally identify the module on the bus when a bus data logger is connected.  **Note: Distribution**: ``BROADCAST-ON-POWER-UP``: Only valid for bus members, which could change the content of the constants during the runtime of the EMS system and do not require a reset of the system (e.g. iCom).",
     "class": "Const",
@@ -20,22 +20,22 @@
     "type": "info"
   },
   "0x0003": {
-    "name": "Product Data Appliance",
+    "name": "Appliance Production Information Block",
     "usedIn": "Various controllers, thermostats and boilers",
-    "description": "Holds ASCII coded device information",
-    "class": "Constant",
-    "emsCategory": "EMS1.0 & EMS2.0",
-    "distribution": "unicast-on-request",
+    "description": "Holds ASCII coded device information. This block contains production information data of the *appliance* (e.g. gas/oil boiler, heat pump, pump station, etc.).",
+    "class": "Const",
+    "emsCategory": "EMS1.0 and EMS2.0: detail in bus variable description",
+    "distribution": "UNICAST-ON-REQUEST",
     "notes": "",
     "type": "info"
   },
   "0x0005": {
     "name": "Special Commands",
     "usedIn": "Various controllers, thermostats and boilers",
-    "description": "Collection of different special functions/commands",
+    "description": "Collection of different special functions/commands. In this block special commands are given. The commands are coded with a special value. Wrong codes will be neglected.  **Note**: Only one command at a time may be sent, therefore there is always an offset of 2 between the variables!",
     "class": "Command",
-    "emsCategory": "EMS1.0",
-    "distribution": "unicast-write-request",
+    "emsCategory": "EMS1.0 and EMS2.0: detail in bus variable description",
+    "distribution": "UNICAST-WRITE-REQUEST",
     "notes": "",
     "type": "warning",
     "extraWarning": "These commands can affect device operation and should be used carefully."
@@ -84,9 +84,9 @@
     "name": "EMS service tool heating parameters",
     "usedIn": "HT3 Junkers systems",
     "description": "This telegrams contains HT3 configuration parameters for Netcom service tools",
-    "class": "parameter",
+    "class": "Parameter",
     "emsCategory": "EMS1.0",
-    "distribution": "unicast-on-request, broadcast-on-change, broadcast-on-power-up, unicast-write-request",
+    "distribution": "BROADCAST-ON-CHANGE, BROADCAST-ON-POWER-UP, UNICAST-ON-REQUEST, UNICAST-WRITE-REQUEST",
     "notes": "",
     "type": "info"
   },
@@ -388,10 +388,11 @@
   "0x0004" : {
     "name" : "Boiler Identification Block",
     "usedIn" : "tbd",
-    "description" : "In this block a definition of the boiler is given. The information is used for external devices which need information about the possibilities of the boiler.  **Important**: Values in this block cannot be changed via the bus!  **Note: EMSType** - ``EMS1.0-AND-EMS2.0``: I0-1, I2, I3.0-3.2, I3.5, I3.6, I3.7, I4, I5, I7, I8, I9, I10, I12, I18-19, I22, I23, I24, I25-26, I27, I28, I29, I30, I31, I32 - ``EMS1.0``: all other indexes",
+    "description" : "In this block a definition of the boiler is given. The information is used for external devices which need information about the possibilities of the boiler.  **Important**: Values in this block cannot be changed via the bus!  **Note: EMSType** - ``EMS1.0-AND-EMS2.0``: offset 0-1, offset 2, offset 3.0-3.2, offset 3.5, offset 3.6, offset 3.7, offset 4, offset 5, offset 7, offset 8, offset 9, offset 10, offset 12, offset 18-19, offset 22, offset 23, offset 24, offset 25-26, offset 27, offset 28, offset 29, offset 30, offset 31, offset 32 - ``EMS1.0``: all other indexes",
     "class" : "Const",
     "emsCategory" : "EMS1.0 and EMS2.0: detail in bus variable description",
     "distribution" : "BROADCAST-ON-POWER-UP, UNICAST-ON-REQUEST",
+    "notes" : "",
     "type" : "info"
   },
   "0x0018" : {
@@ -401,6 +402,7 @@
     "class" : "Monitor",
     "emsCategory" : "EMS1.0 and EMS2.0: detail in bus variable description",
     "distribution" : "BROADCAST-ON-POWER-UP; distribution duration = 10s; timeout = 240s, UNICAST-ON-CHANGE, BROADCAST-PERIODICALLY, UNICAST-ON-REQUEST",
+    "notes" : "",
     "type" : "info"
   },
   "0x0016" : {
@@ -415,11 +417,20 @@
   "0x0014" : {
     "name" : "EMS Simulated System Time",
     "usedIn" : "tbd",
-    "description" : "This block contains the simulated system time of the EMS. The simulated system time is a relative time, which starts counting after the first power up and is incremented each minute as long as the power is available. This timer is stored in EEPROM once an hour.  This timer is to be used as a reference for the relative time, if this is stored in the locking and blocking error register and in the maintenance request register, i.e. if no absolute time from DT6 is available.  **Note: Distribution** Legacy products (EMS1.0) only implemented ``UNICAST-ON-REQUEST``. For backwards compatibility, in this case an HMI needs to request DT20 to reflect the runtime of the system. New products shall support distribution ``BROADCAST-PERIODICALLY`` with a periodicity of *one hour*.",
+    "description" : "This block contains the simulated system time of the EMS. The simulated system time is a relative time, which starts counting after the first power up and is incremented each minute as long as the power is available. This timer is stored in EEPROM once an hour.  This timer is to be used as a reference for the relative time, if this is stored in the locking and blocking error register and in the maintenance request register, i.e. if no absolute time from telegram 0x0006 is available.  **Note: Distribution** Legacy products (EMS1.0) only implemented ``UNICAST-ON-REQUEST``. For backwards compatibility, in this case an HMI needs to request telegram 0x0014 to reflect the runtime of the system. New products shall support distribution ``BROADCAST-PERIODICALLY`` with a periodicity of *one hour*.",
     "class" : "Monitor",
     "emsCategory" : "EMS1.0 and EMS2.0: detail in bus variable description",
     "distribution" : "BROADCAST-ON-CHANGE; distribution duration = 3600s, UNICAST-ON-REQUEST, BROADCAST-PERIODICALLY",
     "type" : "info"
+  },
+  "0x0033" : {
+    "name" : "DHW 1 Parameters backward heating appliance + IHM(@8)",
+    "usedIn" : "tbd",
+    "description" : "This block contains variables to configure the first hot water system of the DHW-controller",
+    "class" : "Parameter",
+    "emsCategory" : "EMS1.0",
+    "distribution" : "BROADCAST-ON-CHANGE, BROADCAST-ON-POWER-UP, UNICAST-ON-REQUEST, UNICAST-WRITE-REQUEST",
+    "notes" : "",
+    "type" : "info"
   }
-
 }
diff --git a/static/data/telegrams.csv b/static/data/telegrams.csv
index dccf96a..8f02a75 100644
--- a/static/data/telegrams.csv
+++ b/static/data/telegrams.csv
@@ -1,8 +1,8 @@
 Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x0001,0-26,Electronics Module production data (part 1),0,255,1,ASCII,"Sequence of numbers. Examples: HMC310 25303763146288737718903, RC100.2 H 05704801002367738112973, MX300 25303394051798738806124. This block contains production information of the electronics module (e.g. ACU-LO ACU-MH HRV_CU etc.) ASCII encoded '\0' terminated.  **Note1**: A reader should always ask for *part1* first. *part2* needs to be requested only in case the production information string in *part1* does not contain the '\0' terminator! **Note2**: In case *part2* needs to be requested the '\0' termination is located at the end of the string (somewhere in *part2*) i.e. *part1* does NOT contain the '\0' terminator. **Note3**: Byte-0 at index 0 is the first character of the string. **Note4**: Legacy products support only *part1* and the content is coded depending on the product (e.g. ASCII coded for Nefit/Buderus or BCD coded for Junkers)."
-0x0001,27-42,Identification product name,0,255,1,ASCII,"Should be \0 terminated, but is not always. i.e. Heat Pump responds with 43 55 48 50 ='CUHP', but \0 is missing. The product name corresponds with the identification byte defined in telegram 2 offset 0.  **Note**: String formatted as ASCII '\0' terminated."
-0x0001,43-69,Electronics Module production data (part 2),0,255,1,-,"Some devices send more data after offset 43. Either a series of 00 or FF. This block contains production information of the electronics module (e.g. ACU-LO ACU-MH HRV_CU etc.). ASCII encoded '\0' terminated.  **Note1**: A reader should always ask for *part1* first. *part2* needs to be requested only in case the production information string in *part1* does not contain the '\0' terminator. **Note2**: In case *part2* needs to be requested the '\0' termination is always at the end of the string (somewhere in *part2*) i.e. *part1* does NOT contain the '\0' terminator. The reader of telegram 1 has to properly concatenate the received content of *part2* (until the '\0' terminator) with the received content of *part1* to get the final string. **Note3**: Legacy products support only *part1* and the content is coded depending on the product (e.g. ASCII coded for Nefit/Buderus or BCD coded for Junkers)."
-0x0002,0,Product ID,0,255,1,-,"1st identification byte, specifies the module type. **NSC**: content from: <LocalDevice.ModuleID_PE>, INVALID = 0, Variant_detection_still_busy_or_in_error = 0, UBA3 = 64, BFE1 = 65, RC10 = 65, BFE2 = 66, RC20 = 66, BFA1 = 67, RC30 = 67, BCxx = 68, BC10 = 68, MM10 = 69, GWP = 70, WM10 = 71, MC10 = 72, SM10 = 73, EM10 = 74, SAFE = 75, ES73 = 76, M300 = 77, M400 = 78, M100 = 79, M200 = 80, Cascade_KSE = 81, CM10 = 81, VM10 = 82, Service_key = 83, DBA = 84, Easycom = 85, RC34 = 86, Easycom_Pro = 87, Gateway = 88, BC10_USA = 89, RC10_USA = 90, RC20_USA = 91, UM10 = 92, RC20F = 93, RFM20 = 94, HTIII = 95, RT10_Fx10 = 96, TD200_Fx100 = 97, AM10 = 98, ZR01 = 99, IPM1 = 100, ISM1 = 101, IPM2 = 102, ISM2 = 103, IUM1 = 104, FW100_Fx100 = 105, FW200_Fx100 = 106, FR100_Fx100 = 107, FR110_Fx100 = 108, FB10_Fx10 = 109, FB100_Fx100 = 110, FR10_Fx10 = 111, RC10V2 = 112, RC20V2 = 113, BC15 = 114, UBA3_50 = 115, FW500_Fx100 = 116, Modulink250_Receiver = 117, BRM10 = 118, FR110F_RM = 119, FR110F_EM = 120, MCC_ICM = 121, CBN_CUx_platform = 122, CBS_CUx_platform = 123, HIN_CUx_platform = 124, HIS_Trim_Full_IO_CUx_platform = 125, UBA_HT_Heatronic_for_Buderus_devices = 126, IGM1 = 127, Buderus_4000_System = 128, IEM = 129, HRU_Heat_Recovery_Unit = 130, MC100 = 131, MX25_Junkers = 132, MC110_Buderus = 133, FR50_Fx100 = 147, eS63_Room_Controller_Sieger = 148, HKM63_Gateway_EMS_EBV_Modules = 149, PM10 = 150, RC25 = 151, HIS_Skin_Mid_Combi_Full_CUx_platform = 152, HIS_Skin_Low_Full_CUx_platform = 153, CBS_Regular_CUx_platform = 154, MX15_MC10_Junkers = 155, eS79_RC35_Sieger = 156, LOW = 157, MID = 158, HC_ClipIn = 159, HC_A = 160, HC_B = 161, SOLAR_CLIPIN = 162, SOLAR_A = 163, SOLAR_B = 164, xLow = 165, Bx15_Junkers = 166, CBS_Hybrid_CUx_platform = 167, IHM = 168, BC40_HIS_for_FB = 169, MC40 = 170, EMS2OT_converter_slave = 171, CUHP = 172, iCOM_KM200_KM50 = 189, HIS_X_Line_CUx_platform = 190, FR120 = 191, FW120 = 192, HC_Z = 193, BC100_HMI_of_control_unit_MC100 = 194, ACU_MH = 195, HMI_Skin_Top_based_on_CU_PL = 196, HMI_Skin_Mid_based_on_CU_PL = 197, NSC_Switch_A = 198, xLow_Sensor_No_HMI = 199, xLOW_HMtelegram Y = 200, Connected_Boiler_clip_in_IFP = 201, RRC_Remote_Room_Controller = 202, RRC2_Remote_Room_Controller2 = 203, NSC_Pool_Module = 204, EMS2OT_converter_master = 205, EMS2IRT_converter_UBA1_UBA1_5 = 206, MID_SOLAR = 207, CU_DNA_1_0 = 208, HMI_Skin_Low_based_on_CU_DNA_1_0 = 209, NSC_MHSMC = 210, EMS2ON_OFF_converter_master = 211, NSC_BG_Clipin_RF = 212, NSC_IO_Module = 213, CR10M_RF = 214, CR20D_RF = 215, CR50E_RF = 216, GHPSC = 217, NSC_RF_Coordinator = 218, HDU = 219, HMI_Xs_belt = 220, Fuel_Cell_CU = 221, iCom_prof_Web_KM300 = 222, CMS_burner_module = 223, DNA1_HMI = 224, HPC_Florida_Heat_Pump = 225, EMS_Dongle_EDO = 226, LOW_RF = 227, AHSM = 228, DNA2_HMI_ST = 229, DNA1_HMI_FB = 230, HRV_CU = 231, MID_HRV_Standalone = 233, ACU_LO_Pneumatic_with_internal_HMI = 234, TIMER_PLUX = 235, eQ3_PLUX = 236, BG_PLUX = 237, DeltaDore_PLUX = 238, Pneumatic_burner_module = 239, HMoffset 800HP_LIGHT = 240, HMoffset 300 = 241, CMS_enhanced_burner_module = 242, EM100_UM100 = 243, DeltaDore_xLow_RF_no_timer = 244, DeltaDore_xLow_RF_timer_enabled = 245, DeltaDore_Low_RF = 246, EMSLeaks = 247, HYBRID_MOD = 248, NextGenControl_xLowRF = 249, NextGenControl_LowRF = 250, OIL_BURNER_MODULE = 251, K30_PLUX = 252, HMoffset 800_2_HP = 253, ACU_HTG = 254"
+0x0001,27-42,Identification product name,0,255,1,ASCII,"Should be \0 terminated, but is not always. i.e. Heat Pump responds with 43 55 48 50 ='CUHP', but \0 is missing. The product name corresponds with the identification byte defined in telegram 0x0002 offset 0.  **Note**: String formatted as ASCII '\0' terminated."
+0x0001,43-69,Electronics Module production data (part 2),0,255,1,-,"Some devices send more data after offset 43. Either a series of 00 or FF. This block contains production information of the electronics module (e.g. ACU-LO ACU-MH HRV_CU etc.). ASCII encoded '\0' terminated.  **Note1**: A reader should always ask for *part1* first. *part2* needs to be requested only in case the production information string in *part1* does not contain the '\0' terminator. **Note2**: In case *part2* needs to be requested the '\0' termination is always at the end of the string (somewhere in *part2*) i.e. *part1* does NOT contain the '\0' terminator. The reader of telegram 0x0001 has to properly concatenate the received content of *part2* (until the '\0' terminator) with the received content of *part1* to get the final string. **Note3**: Legacy products support only *part1* and the content is coded depending on the product (e.g. ASCII coded for Nefit/Buderus or BCD coded for Junkers)."
+0x0002,0,Product ID,0,255,1,-,"1st identification byte, specifies the module type. **NSC**: content from: <LocalDevice.ModuleID_PE>, INVALID = 0, Variant_detection_still_busy_or_in_error = 0, UBA3 = 64, BFE1 = 65, RC10 = 65, BFE2 = 66, RC20 = 66, BFA1 = 67, RC30 = 67, BCxx = 68, BC10 = 68, MM10 = 69, GWP = 70, WM10 = 71, MC10 = 72, SM10 = 73, EM10 = 74, SAFE = 75, ES73 = 76, M300 = 77, M400 = 78, M100 = 79, M200 = 80, Cascade_KSE = 81, CM10 = 81, VM10 = 82, Service_key = 83, DBA = 84, Easycom = 85, RC34 = 86, Easycom_Pro = 87, Gateway = 88, BC10_USA = 89, RC10_USA = 90, RC20_USA = 91, UM10 = 92, RC20F = 93, RFM20 = 94, HTIII = 95, RT10_Fx10 = 96, TD200_Fx100 = 97, AM10 = 98, ZR01 = 99, IPM1 = 100, ISM1 = 101, IPM2 = 102, ISM2 = 103, IUM1 = 104, FW100_Fx100 = 105, FW200_Fx100 = 106, FR100_Fx100 = 107, FR110_Fx100 = 108, FB10_Fx10 = 109, FB100_Fx100 = 110, FR10_Fx10 = 111, RC10V2 = 112, RC20V2 = 113, BC15 = 114, UBA3_50 = 115, FW500_Fx100 = 116, Modulink250_Receiver = 117, BRM10 = 118, FR110F_RM = 119, FR110F_EM = 120, MCC_ICM = 121, CBN_CUx_platform = 122, CBS_CUx_platform = 123, HIN_CUx_platform = 124, HIS_Trim_Full_IO_CUx_platform = 125, UBA_HT_Heatronic_for_Buderus_devices = 126, IGM1 = 127, Buderus_4000_System = 128, IEM = 129, HRU_Heat_Recovery_Unit = 130, MC100 = 131, MX25_Junkers = 132, MC110_Buderus = 133, FR50_Fx100 = 147, eS63_Room_Controller_Sieger = 148, HKM63_Gateway_EMS_EBV_Modules = 149, PM10 = 150, RC25 = 151, HIS_Skin_Mid_Combi_Full_CUx_platform = 152, HIS_Skin_Low_Full_CUx_platform = 153, CBS_Regular_CUx_platform = 154, MX15_MC10_Junkers = 155, eS79_RC35_Sieger = 156, LOW = 157, MID = 158, HC_ClipIn = 159, HC_A = 160, HC_B = 161, SOLAR_CLIPIN = 162, SOLAR_A = 163, SOLAR_B = 164, xLow = 165, Bx15_Junkers = 166, CBS_Hybrid_CUx_platform = 167, IHM = 168, BC40_HIS_for_FB = 169, MC40 = 170, EMS2OT_converter_slave = 171, CUHP = 172, iCOM_KM200_KM50 = 189, HIS_X_Line_CUx_platform = 190, FR120 = 191, FW120 = 192, HC_Z = 193, BC100_HMI_of_control_unit_MC100 = 194, ACU_MH = 195, HMI_Skin_Top_based_on_CU_PL = 196, HMI_Skin_Mid_based_on_CU_PL = 197, NSC_Switch_A = 198, xLow_Sensor_No_HMI = 199, xLOW_HMIY = 200, Connected_Boiler_clip_in_IFP = 201, RRC_Remote_Room_Controller = 202, RRC2_Remote_Room_Controller2 = 203, NSC_Pool_Module = 204, EMS2OT_converter_master = 205, EMS2IRT_converter_UBA1_UBA1_5 = 206, MID_SOLAR = 207, CU_DNA_1_0 = 208, HMI_Skin_Low_based_on_CU_DNA_1_0 = 209, NSC_MHSMC = 210, EMS2ON_OFF_converter_master = 211, NSC_BG_Clipin_RF = 212, NSC_IO_Module = 213, CR10M_RF = 214, CR20D_RF = 215, CR50E_RF = 216, GHPSC = 217, NSC_RF_Coordinator = 218, HDU = 219, HMI_Xs_belt = 220, Fuel_Cell_CU = 221, iCom_prof_Web_KM300 = 222, CMS_burner_module = 223, DNA1_HMI = 224, HPC_Florida_Heat_Pump = 225, EMS_Dongle_EDO = 226, LOW_RF = 227, AHSM = 228, DNA2_HMI_ST = 229, DNA1_HMI_FB = 230, HRV_CU = 231, MID_HRV_Standalone = 233, ACU_LO_Pneumatic_with_internal_HMI = 234, TIMER_PLUX = 235, eQ3_PLUX = 236, BG_PLUX = 237, DeltaDore_PLUX = 238, Pneumatic_burner_module = 239, HMI800HP_LIGHT = 240, HMI300 = 241, CMS_enhanced_burner_module = 242, EM100_UM100 = 243, DeltaDore_xLow_RF_no_timer = 244, DeltaDore_xLow_RF_timer_enabled = 245, DeltaDore_Low_RF = 246, EMSLeaks = 247, HYBRID_MOD = 248, NextGenControl_xLowRF = 249, NextGenControl_LowRF = 250, OIL_BURNER_MODULE = 251, K30_PLUX = 252, HM800_2_HP = 253, ACU_HTG = 254"
 0x0002,1,1st Version number Before column.,0,255,1,-,"Major software version. Shows major changes to Hard- and Software. 0 is development."
 0x0002,2,1st Version number after column.,0,255,1,-,"Minor software version. Indicates minor changes to Hard- and Software. For instance small bug fixes. During the development, this value is incremented as well."
 0x0002,3,2nd Identification byte of indirect bus member,0,255,1,-,"In some systems, this is the identification byte of the integrated *burner module*."
@@ -10,22 +10,47 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x0002,5,2nd Version number of indirect bus member (After column).,0,255,1,-,"In some systems, this is the minor version of the integrated *burner module*."
 0x0002,6,3rd Identification byte of indirect bus member,0,255,1,---,""
 0x0002,7,3rd version byte of indirect bus member (Before column),0,255,1,---,""
-0x0002,8,3rd Version number of indirect bus member (After column),0,255,1,---,"**Junkers**: *Fx system* interprets this byte as Feature ID. Due to expansion of some new functionalities a feature marking should be implemented. This marking has to be transmitted on EMS bus after power-up and on request. telegram 2 offset 3-7 shall be filled with '0x00'.  In telegram 2 offset 8 the so called 'FeatureID' must be added:     - ISM software which supports 'Solar system 4 and Solar option F' => telegram 2 offset 8 = 0x64 = 100     - IPM software which supports 'Actuator tests' => telegram 2 offset 8 = 0x64 = 100"
+0x0002,8,3rd Version number of indirect bus member (After column),0,255,1,---,"**Junkers**: *Fx system* interprets this byte as Feature ID. Due to expansion of some new functionalities a feature marking should be implemented. This marking has to be transmitted on EMS bus after power-up and on request. telegram 0x0002 offset 3-7 shall be filled with '0x00'.  In telegram 0x0002 offset 8 the so called 'FeatureID' must be added:     - ISM software which supports 'Solar system 4 and Solar option F' => telegram 0x0002 offset 8 = 0x64 = 100     - IPM software which supports 'Actuator tests' => telegram 0x0002 offset 8 = 0x64 = 100"
 0x0002,9,Brand ID,0,255,1,-,"Specifies the brand of a module.  A module can use this information to block communication or to adapt to the master slave inverse if required. No_brand_identification = 0, Bosch = 1, Junkers = 2, Buderus = 3, Nefit = 4, Sieger = 5, Tata = 6, Dakon = 7, Elm = 8, Boulter = 9, Vulcano = 10, Worcester = 11, British_Gas = 12, IVT = 13, Geminox = 14, Neckar = 15, Zeus = 16, Milton = 17"
 0x0002,10-11,Installation Country,0,65535,1,---,"Delivered from ACU for DNA2 HMIs. Content: country code following the `ISO3166-1 <https://en.wikipedia.org/wiki/ISO_3166-1>`_ standard in numeric code format e.g. Germany = 'DE' = '276' on EMS. UNDEFINED = 0"
-0x0003,0-26,ASCII coded numbers,0,255,1,ASCII,Example heat pump 26003750000018738212162
-0x0003,27-54,More data,0,255,1,-,Some appliances return a series of 00 or FF
-0x0005,0,Reset Error,0,255,1,enum,"90=error reset, also 153 and 245 do a reset (maybe on a different level)"
-0x0005,2,Reset burner timer and starts,0,255,1,enum,165=reset burner timer and restarts
-0x0005,4,Chimney sweeper mode,0,255,1,enum,"100=activate, 0=off"
-0x0005,6,Reset to factory setting,0,255,1,enum,154=do a reset
-0x0005,8,Reset maintenance message,0,255,1,enum,255=resets maintenance request
-0x0005,12,Erase error history,0,255,1,enum,169=erase error history
-0x0005,42,Clear error history,0,255,1,enum,"1=local history, 2=global history, 3=both"
-0x0005,44,Thermal desinfection,0,255,1,enum,"255=start, 254=stop"
-0x0005,52,Force manual defrost,0,255,1,enum,1=start
-0x0005,68,Standby mode,0,255,1,enum,"85=activate if standby can be selected in the menu, 170=deactivate, status is visible in 0x00E4 offset 12.0"
-0x0005,70,DHW ECO,0,255,1,enum,"85=activate, 170=deactivate"
+0x0003,0-26,Appliance production data (part 1),0,255,1,ASCII,"This block contains production information of the appliance (e.g. gas/oil boiler, heat pump, pump station, etc.) ASCII encoded, '\0' terminated.  **Note 1**: A reader should always ask for *part1* first. *part2* needs to be requested only in case the production information string in *part1* does not contain the '\0' terminator! **Note 2**: In case *part2* needs to be requested, the '\0' termination is located at the end of the string (somewhere in *part2*), i.e. *part1* does NOT contain the '\0' terminator. **Note 3**: Byte-0 at index 0 is the first character of the string. Content of telegram 0x0003 offset 00-26 can be written with command telegram 0x00FB offset 00-26. **Note 4**: Legacy products support only *part1* and the content is coded depending on the product (e.g. ASCII coded for Nefit/Buderus, or BCD coded for Junkers). Example heat pump 26003750000018738212162"
+0x0003,27-53,Appliance production data (part 2),0,255,1,ASCII,"This block contains production information of the appliance (e.g. gas/oil boiler, heat pump, pump station, etc.) ASCII encoded, '\0' terminated.  **Note 1**: A reader should always ask for *part1* first. *part2* needs to be requested only in case the production information string in *part1* does not contain the '\0' terminator. **Note 2**: In case *part2* needs to be requested, the '\0' termination is always at the end of the string (somewhere in *part2*), i.e. *part1* does NOT contain the '\0' terminator. **Note 3**: Content of telegram 0x0003 offset 27-53 can be written with command telegram 0x00FB offset 27-53. The reader of telegram 0x0003 has to properly concatenate the received content of *part2* (until the '\0' terminator) with the received content of *part1* to get the final string. **Note 4**: Legacy products support only *part1* and the content is coded depending on the product (e.g. ASCII coded for Nefit/Buderus, or BCD coded for Junkers). Some appliances return a series of 0x00 or 0xFF"
+0x0005,0,Reset error,0,255,1,enum,"Used to remove a lockout on the device. For the EMS this unlock request may only be send when the EMS is in a lockout, otherwise this unlock device will be neglected., manual_error_reset = 0x5A, super_reset = 0x99, remote_reset = 0xF5"
+0x0005,2,Reset Burner timer and starts,0,255,1,enum,"Both the counters for the 1st and 2nd burner are cleared., RESET_BURNER_TIMER_STARTS = 0xA5"
+0x0005,4,Chimney sweeper mode,0,255,1,%,"This variable is used to switch on the burner on a specified load. This function is used for emission measurements at nominal load. In addition, for adjusting of gas valves at minimum load. Value ranges: 0 = off (means boiler goes back to normal operation) 1-min.burnerload = Burner on with load is minimum burner load min.burnerload   100 = Burner on with load as is requested., STOP = 0, OFF = 0, ACTIVATE = 100"
+0x0005,6,Reset Factory setting,0,255,1,enum,"All the configurable variables are reset to the factory settings. For NSC Solar: no reset of heat count values. This is handled extra via telegram 0x0390 offset 0, RESET = 0x9A"
+0x0005,8,Reset maintenance request,0,255,1,enum,"Used to reset an active maintenance request, displayed as 'Hxx' where xx is the number of the request, which is reported in telegram 0x001C, offset 1-offset 2 (EMS1) and via telegram 0x00BF, error class 18 (EMS2). The value ranges from 1 to 32 for EMS1 (linked to maintenance request register flags of telegram 0x001C) and from 1 to 99 in EMS2. A transmitted value in this range resets the corresponding request. With value 0xFF all requests can be reset at once., RESET_MAINTENANCE = 0xFF"
+0x0005,10,Call for all blocks,0,255,1,enum,"This command enables a data logger or modules to obtain datatypes with a broadcast message, from the EMS or another module with a single call. Especially a data logger using this command does not need to have any system knowledge. The EMS or a module is only allowed to transmit datatypes of which they are master and secondly blocks which are only input will not be transmitted."
+0x0005,12,Erase Error history,0,255,1,enum,"This command should only be send during production! The entire error register and the maintenance request register will be cleared., ERASE = 0xA9"
+0x0005,14,Calibration start,0,255,1,enum,"Starts calibration procedure. The UBA3 only accepts this command from the PC token. The CU-CMS has no restriction on the token that sends this command, but only accepts it in combination with a heat request (calibration can only be executed while burning)., START = 0xCA"
+0x0005,16,Stop calibration of UBA3,0,255,1,enum,"Locks reading and writing in calibration datatype telegram 0x0009 and starts storing calibration data in EEPROM if calibration has been started. The UBA3 only accepts this command from the PC token."
+0x0005,18,Service marker,0,255,1,enum,""
+0x0005,20,Pump_and_Mixer_kick,0,255,1,enum,""
+0x0005,22,Reset operating timer Solar,0,255,1,enum,""
+0x0005,24,Production test start,0,255,1,enum,"0x5A = production test start any other value = production test stop"
+0x0005,26,Production locking error,0,255,1,enum,""
+0x0005,28,Burner start release,0,255,1,enum,"After receiving the burner start request (telegram 0x0018,offset 24,b4) a module like the IUM can release the burner start with this service, after it has opened for instance the Abgassperrklappe. The release command must be transmitted at least every 30 seconds; otherwise the burner will be blocked again (default condition)., blocked = 0, release = 0xAA"
+0x0005,30,Return byte of program flow supervision,0,255,1,enum,""
+0x0005,32,STB test start Code,0,255,1,enum,"0x4B Start command for STB test, STOP = 0"
+0x0005,34,Control byte for program flow supervision,0,255,1,enum,"HTIII will transmit a control byte to IUM every one minute. IUM uses this byte as start value for program flow counter and sends back the end value of the counter (telegram 0x0005,offset 30). HTIII changes the start value with every new burner start demand, and if this occurs HTIII sends a single additional message in between of the 1 min cycle."
+0x0005,36,JUPII protocol EMS protocol,0,255,1,enum,"JUPII_protocol = 0x37, EMS_protocol = 0x73"
+0x0005,38,Diverter valve in middle position (HMI code greater than 7.b.),0,255,1,enum,"[middle position In the middle position it will fall back to the default position after 15 minutes] = 0xFF; [default position] = 0x00"
+0x0005,40,Code plug misusage protection,0,255,1,enum,"Enable Elephant memory check. Code: 0xD5. This command should only be send during production! It is not possible to disable the Elephant memory check via the EMS bus"
+0x0005,42,Clearing error history,0,255,1,enum,"LOCAL = 1, Clearing_the_local_error_history_LEH = 1, GLOBAL = 2, Clearing_the_global_error_history_GEH = 2, BOTH = 3, Clearing_both_error_histories_GEH_and_LEH = 3"
+0x0005,44,Thermal Disinfection start / stop,0,255,1,enum,"STOP = 0xFE, START = 0xFF"
+0x0005,46,Daily Heat Up Start,0,255,1,enum,"START = 0xFF"
+0x0005,48,Chimney sweeper mode,0,255,1,%,"chimney sweeper mode is activated. The percentage value indicates the requested power for the chimney sweeper function., STOP = 0, OFF = 0, ACTIVATE = 100"
+0x0005,50,Reset error class 19,0,255,1,enum,"This command is used to reset an active maintenance request, which is reported with error class 'Resettable Maintenance request Type 2'.  Note: Resetting of single errors is not possible! With code value 0xFF all requests can be reset at once."
+0x0005,52,Force manual defrost,0,255,1,enum,"START = 1"
+0x0005,54,Appliance quick start,0,255,1,enum,"START = 1"
+0x0005,56,Reset energy monitoring values,0,255,1,enum,"Impacts telegram 0x17 and telegram 0x2E, RESET = 0xFF"
+0x0005,58,CommissioningFreeze,0,255,1,enum,"1. Storing the 'Commissioning Freeze' parameter data set Every parameter-owning device (CUHP or Mid-HP) copies event-triggered (on reception of a particular 'Store Commissioning Freeze' command or when processing an appropriate HMI interaction) its current parameter settings (out of the original parameter area in the non-volatile memory) into the 'shadow' memory area.  A possible EMS mechanism was e.g. telegram 0x0005 offset 58 = 0xFF.   2. Restoring the 'Commissioning Freeze' parameter data set Every parameter-owning device restores event-triggered (on reception of a particular 'Restore Commissioning Freeze' command or when processing an appropriate HMI interaction) its current parameter data set out of the previously stored 'Commissioning Freeze' parameter data set.  A possible EMS mechanism was e.g. telegram 0x0005 offset 58 = 0x00. Of course restoring is only possible if previously a 'Commissioning Freeze' data set has been stored (e.g. non-volatile flag 'CommissioningFreezeDone' == TRUE).  On reset to factory defaults (telegram 0x0005 offset 6 = 0x9A) it must be ensured that the mentioned flag 'CommissioningFreezeDone' is reset to FALSE., RESTORE = 0, STORE = 0xFF"
+0x0005,60,Reset energy generation values,0,255,1,enum,"Impacts telegram 0x0036 and telegram 0x003B, RESET = 0xFF"
+0x0005,62,Super factory reset,0,255,1,enum,"0x5A = RESET, only accepted from token 0x0B any other value = do nothing Collection of all possible reset commands:  -Reset all the timers and counters are reset to zero (telegram 0x0005 offset 2)  -Reset all the configurable variables are reset to factory settings (telegram 0x0005 offset 6)  -Reset maintenance requests (telegram 0x0005 offset 8)  -Reset the entire error registers and maintenance request register will be cleared (telegram 0x0005 offset 12, telegram 0x0005 offset 42, telegram 0x0005 offset 50)  -Reset the energy monitoring values will be reset (telegram 0x0005 offset 56, telegram 0x0005 offset 60)  -Reset elephant memory (telegram 5 offset 40)"
+0x0005,64,Hydraulic Settings Indication,0,255,1,enum,"When in hydraulic settings change mode, appliance is not allowed to start burner or activate outputs. Mode times out after 5 min if no stop is send. Optionally: Timer restarts after receiving one of the hydraulic settings in telegram 0x00E6 (offset 11, offset 20, offset 24, offset 25)., STOP = 0, START = 1"
+0x0005,66,Reset auto filling function,0,255,1,enum,"resets number of refills (shown in telegram 0x00E5,offset 27) and unlocks function when it was locked due to pressure loss faster than 'Auto filling refill blocking time' (telegram 0x00E6 offset 34)., RESET = 0x9A"
+0x0005,68,Standby mode,0,255,1,enum,"This command activates/deactivates the Standby mode / Soft-off function of the appliance. Its status is reported in telegram 0x00E4 offset 12.0, activate_Standby = 0x55, deactivate_Standby = 0xAA"
+0x0005,70,DHW ECO command,0,255,1,enum,"This command activates/deactivates the ECO mode in the ACU (reflected in telegram 0x00E4 offset 12.1) and is typically transmitted when the ECO button is pressed on the appliance HMI., activate_ECO = 0x55, deactivate_ECO = 0xAA"
 0x0010,0-1,Error 1 display code,0,255,1,ASCII,displayed error code
 0x0010,2-3,Error 1 cause code,0,65535,1,-,"numbers >= 200, list used in Nefit and Buderus"
 0x0010,4,Error 1 Start year,0,255,1,-,"Bit 7 (=1) of this number indicates if the year is absolute. Bit 7=0 indicates relative time, then is offset 4 is unused"
@@ -94,7 +119,7 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x00BF,10-16,Error 2,,,,,"next lower prio error; offsets see 3-9"
 0x00BF,17-23,Error 3,,,,,"next lower prio error; offsets see 3-9"
 0x00C0,0,Error 1 source address,0,127,1,,"if 0x00, then no error"
-0x00C0,1,Error 1 module ID,0,255,1,,same as in telegram 0x02 offset 0
+0x00C0,1,Error 1 module ID,0,255,1,,same as in telegram 0x0002 offset 0
 0x00C0,2,Error 1 module ID extension?,0,255,1,,"is always 0, but maybe used if offset 1 is more than 255"
 0x00C0,3,Error 1 reason,0,255,1,enum,"found so far: 0x00=fatal, 0x02/0x04/0x06=locked, 0x08=safety shutdown with restart, 0x0A=safety shutdown blocking, 0x0C=controlled shutdown, 0x0E=standard, 0x10=minor, 0x12/0x13=reset after maintenance, 0x14=maintenance"
 0x00C0,4.0,Error 1 Log error,0,1,1,bool,"1=yes, 0=no"
@@ -121,7 +146,7 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x00C0,160-179,Error 9,,,,,same as offset 0 ff. for error 1
 0x00C0,180-199,Error 10,,,,,same as offset 0 ff. for error 1
 0x00C2,0,Error 1 source address,0,127,1,,"if 0x00, then no error"
-0x00C2,1,Error 1 module ID,0,255,1,,same as in telegram 0x02 offset 0
+0x00C2,1,Error 1 module ID,0,255,1,,same as in telegram 0x0002 offset 0
 0x00C2,2,Error 1 module ID extension?,0,255,1,,"is always 0, but maybe used if offset 1 is more than 255"
 0x00C2,3,Error 1 reason,0,255,1,enum,"found so far: 0x00=fatal, 0x02/0x04/0x06=locked, 0x08=safety shutdown with restart, 0x0A=safety shutdown blocking, 0x0C=controlled shutdown, 0x0E=standard, 0x10=minor, 0x12/0x13=reset after maintenance, 0x14=maintenance"
 0x00C2,4.0,Error 1 Log error,0,1,1,bool,"1=yes, 0=no"
@@ -149,7 +174,7 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x00C2,180-199,Error 10,,,,,same as offset 0 ff. for error 1
 0x00C6,0,Error UID,0,254,1,,ID of error 1
 0x00C6,1,Error 1 source address,0,127,1,,"if 0x00, then no error"
-0x00C6,2,Error 1 module ID,0,255,1,,same as in telegram 0x02 offset 0
+0x00C6,2,Error 1 module ID,0,255,1,,same as in telegram 0x0002 offset 0
 0x00C6,3,Error 1 module ID extension?,0,255,1,,"is always 0, but maybe used if offset 1 is more than 255"
 0x00C6,4,Error 1 reason,0,255,1,enum,"found so far: 0x00=fatal, 0x02/0x04/0x06=locked, 0x08=safety shutdown with restart, 0x0A=safety shutdown blocking, 0x0C=controlled shutdown, 0x0E=standard, 0x10=minor, 0x12/0x13=reset after maintenance, 0x14=maintenance"
 0x00C6,5.0,Error 1 Log error,0,1,1,bool,"1=yes, 0=no"
@@ -177,7 +202,7 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x00C6,189-209,Error 10,,,,,same as offset 0 ff. for error 1
 0x00C7,0,Error UID,0,254,1,,ID of error 11
 0x00C7,1,Error 11 source address,0,127,1,,"if 0x00, then no error"
-0x00C7,2,Error 11 module ID,0,255,1,,same as in telegram 0x02 offset 0
+0x00C7,2,Error 11 module ID,0,255,1,,same as in telegram 0x0002 offset 0
 0x00C7,3,Error 11 module ID extension?,0,255,1,,"is always 0, but maybe used if offset 1 is more than 255"
 0x00C7,4,Error 11 reason,0,255,1,enum,"found so far: 0x00=fatal, 0x02/0x04/0x06=locked, 0x08=safety shutdown with restart, 0x0A=safety shutdown blocking, 0x0C=controlled shutdown, 0x0E=standard, 0x10=minor, 0x12/0x13=reset after maintenance, 0x14=maintenance"
 0x00C7,5.0,Error 11 Log error,0,1,1,bool,"1=yes, 0=no"
@@ -216,7 +241,7 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x00BF,10-16,Error 2,,,,,"next lower prio error; offsets see 3-9"
 0x00BF,17-23,Error 3,,,,,"next lower prio error; offsets see 3-9"
 0x00C0,0,Error 1 source address,0,127,1,,"if 0x00, then no error"
-0x00C0,1,Error 1 module ID,0,255,1,,same as in telegram 0x02 offset 0
+0x00C0,1,Error 1 module ID,0,255,1,,same as in telegram 0x0002 offset 0
 0x00C0,2,Error 1 module ID extension?,0,255,1,,"is always 0, but maybe used if offset 1 is more than 255"
 0x00C0,3,Error 1 reason,0,255,1,enum,"found so far: 0x00=fatal, 0x02/0x04/0x06=locked, 0x08=safety shutdown with restart, 0x0A=safety shutdown blocking, 0x0C=controlled shutdown, 0x0E=standard, 0x10=minor, 0x12/0x13=reset after maintenance, 0x14=maintenance"
 0x00C0,4.0,Error 1 Log error,0,1,1,bool,"1=yes, 0=no"
@@ -243,7 +268,7 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x00C0,160-179,Error 9,,,,,same as offset 0 ff. for error 1
 0x00C0,180-199,Error 10,,,,,same as offset 0 ff. for error 1
 0x00C2,0,Error 1 source address,0,127,1,,"if 0x00, then no error"
-0x00C2,1,Error 1 module ID,0,255,1,,same as in telegram 0x02 offset 0
+0x00C2,1,Error 1 module ID,0,255,1,,same as in telegram 0x0002 offset 0
 0x00C2,2,Error 1 module ID extension?,0,255,1,,"is always 0, but maybe used if offset 1 is more than 255"
 0x00C2,3,Error 1 reason,0,255,1,enum,"found so far: 0x00=fatal, 0x02/0x04/0x06=locked, 0x08=safety shutdown with restart, 0x0A=safety shutdown blocking, 0x0C=controlled shutdown, 0x0E=standard, 0x10=minor, 0x12/0x13=reset after maintenance, 0x14=maintenance"
 0x00C2,4.0,Error 1 Log error,0,1,1,bool,"1=yes, 0=no"
@@ -271,7 +296,7 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x00C2,180-199,Error 10,,,,,same as offset 0 ff. for error 1
 0x00C6,0,Error UID,0,254,1,,ID of error 1
 0x00C6,1,Error 1 source address,0,127,1,,"if 0x00, then no error"
-0x00C6,2,Error 1 module ID,0,255,1,,same as in telegram 0x02 offset 0
+0x00C6,2,Error 1 module ID,0,255,1,,same as in telegram 0x0002 offset 0
 0x00C6,3,Error 1 module ID extension?,0,255,1,,"is always 0, but maybe used if offset 1 is more than 255"
 0x00C6,4,Error 1 reason,0,255,1,enum,"found so far: 0x00=fatal, 0x02/0x04/0x06=locked, 0x08=safety shutdown with restart, 0x0A=safety shutdown blocking, 0x0C=controlled shutdown, 0x0E=standard, 0x10=minor, 0x12/0x13=reset after maintenance, 0x14=maintenance"
 0x00C6,5.0,Error 1 Log error,0,1,1,bool,"1=yes, 0=no"
@@ -299,7 +324,7 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x00C6,189-209,Error 10,,,,,same as offset 0 ff. for error 1
 0x00C7,0,Error UID,0,254,1,,ID of error 11
 0x00C7,1,Error 11 source address,0,127,1,,"if 0x00, then no error"
-0x00C7,2,Error 11 module ID,0,255,1,,same as in telegram 0x02 offset 0
+0x00C7,2,Error 11 module ID,0,255,1,,same as in telegram 0x0002 offset 0
 0x00C7,3,Error 11 module ID extension?,0,255,1,,"is always 0, but maybe used if offset 1 is more than 255"
 0x00C7,4,Error 11 reason,0,255,1,enum,"found so far: 0x00=fatal, 0x02/0x04/0x06=locked, 0x08=safety shutdown with restart, 0x0A=safety shutdown blocking, 0x0C=controlled shutdown, 0x0E=standard, 0x10=minor, 0x12/0x13=reset after maintenance, 0x14=maintenance"
 0x00C7,5.0,Error 11 Log error,0,1,1,bool,"1=yes, 0=no"
@@ -332,14 +357,14 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x099A,11-13,HP starts heating,0,16777215,1,,3 byte unsigned int
 0x099A,14-16,HP starts dhw,0,16777215,1,,3 byte unsigned int
 0x099A,17,Smart grid mode,0,3,1,enum,"0=Mode1 (I1 closed, I4 open = Heat pump blocked by energy supplier); 1=Mode2 (I1 open, I4 open = Normal operation); 2=Mode3 (I1 open, I4 closed = Heatpump prefered); 3=Mode4 (I1 closed, I4 closed = Forced operation of heatpump)"
-0x0026,0,CH pump speed,1,10,1,enum,"1 = No predefined settings. Minimum pump speed telegram 0x16,offset 10 and maximum pump speed telegram 0x16 offset 9 manually adjustable; 2-7 = Constant speeds (minimum pump speed telegram 0x16 offset 10 and maximum pump speed telegram 0x16 offset 9 are the same). 8-10 = Predefined minimum pump speed 0x16 offset 10 and maximum pump speed 0x16 offset 9 settings."
-0x0026,1,pump switch mode,0,5,1,enum,"auto = 0, according burner = 1, acc room temp control = 2, acc outdoor temp control = 3, acc outdoor temp control optimized = 4, energy saving = 4, acc CH heat request = 5"
-0x0026,2,automatic anti cycle mode,-1,0,1,bool,"time delay between switching the boiler off and on again, 0 = off, FF = on"
-0x0026,3,Min appliance power for CH and dhw,0,100,1,percent,
-0x0026,4,Fan overrun time,1,18,1,10 sec,
-0x0026,5,min flow temp setpoint,30,90,1,°C,
-0x0026,6,max flow temp setpoint,30,90,1,°C,
-0x0026,7,max appliance power in CH mode,0,100,1,percent,
+0x0026,0,CH pump speed,1,10,1,enum,"1 = No predefined settings. Minimum pump speed telegram 0x0016,offset 10 and maximum pump speed telegram 0x0016,offset 9 manually adjustable; 2-7 = Constant speeds (minimum pump speed telegram 0x0016,offset 10 and maximum pump speed telegram 0x0016,offset 9 are the same). 8-10 = Predefined minimum pump speed telegram 0x0016,offset 10 and maximum pump speed telegram 0x0016,offset 9 settings."
+0x0026,1,Pump switch mode,0,5,1,enum,"Pump switch mode (pump run while burner is off), As_mode__2_ = 0, AUTO = 0, depends_on_burner = 1, depends_on_room_temp_control = 2, depends_on_outdoor_based_control = 3, depends_on_outdoor_based_control_with_optimization = 4, ENERGY_SAVE = 4, depends_on_CH_heat_request_CUx_only = 5, HEAT_REQ = 5"
+0x0026,2,Automatic anti-cycle mode,0,255,1,---,"off = 0, on = 0xFF"
+0x0026,3,Min. appliance power (both CH and DHW),0,100,1,%,"The 100% means max. appliance power."
+0x0026,4,Fan overrun time,1,18,10,s,""
+0x0026,5,Min. primary flow temperature set point,30,90,1,°C,""
+0x0026,6,Max. primary flow temperature set point,30,90,1,°C,""
+0x0026,7,Max. appliance power in CH mode,0,100,1,%,""
 0x0027,0,thermal desinfection,-1,0,1,bool,"0 = no, FF = yes"
 0x0027,1,anti cycle time for dhw,20,60,1,min,time delay between switching the boiler off and on again
 0x0027,2,dhw standby time after tapping,0,30,1,min,
@@ -1076,63 +1101,61 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x001A,2,Pump speed setpoint / frost danger,0,100,1,%,"Frost danger. no = 0yes = 100"
 0x001A,3,High efficiency pre heat-up,-1,0,1,---,"Enables the boiler to pre heat with the highest possible efficiency.  The three lowest variables are stored (of different tokens) of which the lowest variable will be used.  When this function is activated without a set point (Power = 0 and Supply Temperature = 0) being transmitted  the maximum values of both set points will be used by the heat supplier.  The control algorithm of the heat supplier (i.e. the heat pump) always limits both set points only if they exceed the high efficiency set points."
 0x001A,4,Heating circuit temperature level for pump save function.,0,3,1,---,"Depending on the required heating circuit temperature level the pump will be switched off more or less often in order to save energy.  The 3 highest are stored.  The highest is used.  0: None. The internal setting will be used in this case.  1: Frost.  2: Low.  3: High. not used for Buderus xLow can use DT26 I4: high => roomtemp setpoint != off; frost: if roomtep setpoint ==off"
-0x0004,0-1,BCM_number,1000,65535,1,---,"The BCM numbers for EMS will start with 1000 to prevent mismatches with UBA1 numbers (0-255). The BIM numbers will start with 5000. The HTIII coding module range: 11000 – 14352 (real codeplug number + an offset of 10000). The WB-Dev based applications have the range: 20000 - 29999 refined in detail:    - CU-PF:   20000-24999    - ACU_Lo:  25000-28999    - Special: 29000-29999 Special:    - RI:34 - 45    - LPP LPP-Bu: 84 - 87 and 148 - 151  **Important**: - Default value: 0xFFFF (no codeplug) - If a product doesn't have a BCM it shall report 0xFFFF as BCM number. This number is then reported/forwarded by the connectivity gateway to the backend. The product that has no BCM shall additionally mark this index as *unused* (see DT247 data handling). - A connectivity gateway can still report 0x0000 as value towards the backend in case the product does not support the BCM number (i.e. DT4 I0-1 is not transmitted on EMS)."
+0x0004,0-1,BCM_number,1000,65535,1,---,"The BCM numbers for EMS will start with 1000, to prevent mismatches with UBA1 numbers (0-255). The BIM numbers will start with 5000. The HTIII coding module range: 11000 – 14352 (real codeplug number + an offset of 10000). The WB-Dev based applications have the range: 20000 - 29999, refined in detail:    - CU-PF:   20000-24999    - ACU_Lo:  25000-28999    - Special: 29000-29999 Special:    - RI:34 - 45    - LPP, LPP-Bu: 84 - 87 and 148 - 151  **Important**: - Default value: 0xFFFF (no codeplug) - If a product doesn't have a BCM, it shall report 0xFFFF as BCM number. This number is then reported/forwarded by the connectivity gateway to the backend. The product that has no BCM shall additionally mark this index as *unused* (see telegram 0x00F7 data handling). - A connectivity gateway can still report 0x0000 as value towards the backend, in case the product does not support the BCM number (i.e. telegram 0x0004 offset 0-1 is not transmitted on EMS)."
 0x0004,2,BCM_version_number,0,255,1,---,"Under the same BCM number small changes can be made. (UBA 1 has a safety and a miscellaneous version number)"
 0x0004,3.0-3.2,NumberBurnerStages,0,7,1,enum,"- 0 = modulating burner - 1-7 = stages of the burner MODULATING = 0"
-0x0004,3.5,Atmospheric_burner,0,1,1,---,"FALSE = 0 TRUE = 1"
+0x0004,3.5,Atmospheric_burner,0,1,1,---,"FALSE = 0, TRUE = 1"
 0x0004,3.6,Gas_burner,0,1,1,---,""
-0x0004,3.7,Oil_Burner,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,4,Nominal power CH (low byte),0,255,1,kW,"Maximal power for Central Heating in kW (maximale Leistung).  This value must be consistent with value calculated from ["Maximum appliance power" (DT4 I25-26) times"Maximum relative power CH" (DT4 I23)]. Domestic Hot Water can have another maximum. Used if power <=255kW; **High byte**: DT4 I12 - Must be supported for legacy reasons."
-0x0004,5,Minimal appliance power,0,100,1,%,"For a boiler the max. appliance power and max. CH power can be different! This minimal burner load value is based on max. CH power for UBA/CUx and on max. appliance power for HT3/MC10 /ACUs (same as DT4 I22)."
+0x0004,3.7,Oil_Burner,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,4,Nominal power CH (low byte),0,255,1,kW,"Maximal power for Central Heating in kW (maximale Leistung).  This value must be consistent with value calculated from ['Maximum appliance power' (telegram 0x0004 offset 25-26) times 'Maximum relative power CH' (telegram 0x0004 offset 23)]. Domestic Hot Water can have another maximum. Used if power <=255kW; **High byte**: telegram 0x0004 offset 12 - Must be supported for legacy reasons."
+0x0004,5,Minimal appliance power,0,100,1,%,"For a boiler the max. appliance power and max. CH power can be different! This minimal burner load value is based on max. CH power for UBA/CUx and on max. appliance power for HT3/MC10 /ACUs (same as telegram 0x0004 offset 22)."
 0x0004,6,Fixed CH power limit,0,100,1,%,""
 0x0004,7,Src.MinOperatingTemp,0,70,1,°C,"Under this temperature the pump will be switched off when the burner is on. When the burner is on it will stay on for at least that this temperature (+hysteresis 5K) is reached.  *Note*: Only for floor standing boilers."
 0x0004,8,minimum_water_temperature,0,70,1,°C,"When there is a heat request and the boiler temperature is below this value the burner will switch on. The set point for the temperature controller will be lifted up when this function is active. *Note*: Only for floor standing boilers."
 0x0004,9,overheating_temperature,80,120,1,°C,""
 0x0004,10,maximum_boiler_efficiency,0,255,1,%,"This value can be used in automatic cascade controller where a preference for efficiency is chosen."
-0x0004,11.0,Dialog_pump_present,0,1,1,---,"This information is needed in the human interface to blank out not used parameters. FALSE = 0 TRUE = 1"
-0x0004,11.1,Fluegas_sensor_present,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,11.2,Pump_functionality_switch__DT22__I7__disabled,0,1,1,---,"This information is needed in the human interface to blank out not used parameters. FALSE = 0 TRUE = 1"
-0x0004,11.3,Pressure_sensor_present,0,1,1,---,"This bit indicates if a sensor is connected to the system. When this bit is set the sensor value can be read in DT24 I17. FALSE = 0 TRUE = 1"
+0x0004,11.0,Dialog_pump_present,0,1,1,---,"This information is needed in the human interface to blank out not used parameters., FALSE = 0, TRUE = 1"
+0x0004,11.1,Fluegas_sensor_present,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,11.2,Pump_functionality_switch__telegram 0x0016__offset7__disabled,0,1,1,---,"This information is needed in the human interface to blank out not used parameters. FALSE = 0, TRUE = 1"
+0x0004,11.3,Pressure_sensor_present,0,1,1,---,"This bit indicates if a sensor is connected to the system. When this bit is set the sensor value can be read in telegram 0x0018 offset 17. FALSE = 0, TRUE = 1"
 0x0004,11.4,Fan_speed_adjustable,0,1,1,---,"This bit indicates if the fan speed is adjustable with the BC10. FALSE = 0 TRUE = 1"
-0x0004,11.5,Maintenance_adjustable,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,11.6,Return_sensor_present,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,11.7,Air_pressure_sensor_present,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,12,Nominal power CH (high byte),0,255,1,kW,"Must be supported for legacy reasons! **Low byte**: DT4 I4"
-0x0004,13.0,Bitfield_to_indicate_boiler_data_There_is_fan_speed,0,1,1,---,"Bitfield to indicate boiler data: there is fan speed (DT24 I27-31) *Note*: Buderus specific"
-0x0004,13.1,Bitfield_to_indicate_boiler_data__burner_delay_time,0,1,1,---,"Bitfield to indicate boiler data: burner delay time (DT31) *Note*: Buderus specific"
-0x0004,13.2,Bitfield_to_indicate_boiler_data_low_flame_signal,0,1,1,---,"Bitfield to indicate boiler data: low flame signal (DT32) *Note*: Buderus specific"
-0x0004,13.3,Flame_off_from_the_last_32_burner_starts,0,1,1,---,"Bitfield to indicate boiler data: flame off from the last 32 burner starts (DT28 I11-14) *Note*: Buderus specific"
-0x0004,13.4,Low_Flame_signal_from_the_last_32_burner_starts,0,1,1,---,"Bitfield to indicate boiler data: Low Flame signal from the last 32 burner starts (DT28 I15-18) *Note*: Buderus specific"
-0x0004,13.5,High_Flame_signal_from_the_last_32_burner_starts,0,1,1,---,"Bitfield to indicate boiler data: High Flame signal from the last 32 burner starts (DT28 I15-18) *Note*: Buderus specific"
-0x0004,13.6,There_is_an_integral_for_switching_the_burner_on_off,0,1,1,---,"Bitfield to indicate boiler data: There is an integral for switching the burner on/off (DT24 I33-34) *Note*: Buderus specific"
+0x0004,11.5,Maintenance_adjustable,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,11.6,Return_sensor_present,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,11.7,Air_pressure_sensor_present,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,12,Nominal power CH (high byte),0,255,1,kW,"Must be supported for legacy reasons! **Low byte**: telegram 0x0004 offset 4"
+0x0004,13.0,Bitfield_to_indicate_boiler_data_There_is_fan_speed,0,1,1,---,"Bitfield to indicate boiler data: there is fan speed (telegram 0x0018 offset 27-31) *Note*: Buderus specific"
+0x0004,13.1,Bitfield_to_indicate_boiler_data__burner_delay_time,0,1,1,---,"Bitfield to indicate boiler data: burner delay time (telegram 0x001F) *Note*: Buderus specific"
+0x0004,13.2,Bitfield_to_indicate_boiler_data_low_flame_signal,0,1,1,---,"Bitfield to indicate boiler data: low flame signal (telegram 0x0020) *Note*: Buderus specific"
+0x0004,13.3,Flame_off_from_the_last_32_burner_starts,0,1,1,---,"Bitfield to indicate boiler data: flame off from the last 32 burner starts (telegram 0x001C offset 11-14) *Note*: Buderus specific"
+0x0004,13.4,Low_Flame_signal_from_the_last_32_burner_starts,0,1,1,---,"Bitfield to indicate boiler data: Low Flame signal from the last 32 burner starts (telegram 0x001C offset 15-18) *Note*: Buderus specific"
+0x0004,13.5,High_Flame_signal_from_the_last_32_burner_starts,0,1,1,---,"Bitfield to indicate boiler data: High Flame signal from the last 32 burner starts (telegram 0x001C offset 15-18) *Note*: Buderus specific"
+0x0004,13.6,There_is_an_integral_for_switching_the_burner_on_off,0,1,1,---,"Bitfield to indicate boiler data: There is an integral for switching the burner on/off (telegram 0x0018 offset 33-34) *Note*: Buderus specific"
 0x0004,13.7,//free,0,1,1,---,"Bitfield to indicate boiler data: free"
-0x0004,14.0,Gas_pressure_sensor_present,0,1,1,---,"*Note*: I14 = Bitfield to indicate some system parts FALSE = 0 TRUE = 1"
-0x0004,14.1,Air_temperature_sensor_present,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,14.2,Flow_sensor_present,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,14.3,External_cutoff_present,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,14.4,Fluegas_STB_present,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,14.5,Supply_temperature_STB_present,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,14.6,On_off_roomthermostat_input_present,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,14.7,Solar buffer tank present,0,1,1,---,"Indicates the presence of a Solar Buffer Tank (incl. solar mixer valve and sensors). It is needed to provide an alternative to datahandling for the RC35 to know if the applicable menu items should be displayed. FALSE = 0 TRUE = 1"
-0x0004,15.0,Pump_Switch_off_temperature_adjustable,0,1,1,---,"Buderus specific; If this bit is set the pump switch off temperature (DT22 I23) is adjustable (for example with the BC10). FALSE = 0 TRUE = 1"
-0x0004,15.1,STB_test_present,0,1,1,---,"If this bit is set the STB test (DT5 I30) can be started (for example with the BC10). FALSE = 0 TRUE = 1"
-0x0004,15.2,DHW_functionality_during_night_mode,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,15.3,Energy monitoring supported flag,0,1,1,---,"If this bit is set DT23 (Appliance Energy Monitoring Values (for HMI)) is supported. E.g. a HMI device can use this flag to show/hide menus for energy monitoring values. FALSE = 0 TRUE = 1"
-0x0004,15.4,Energy generation supported flag,0,1,1,---,"If this bit is set DT54 (Appliance Energy Generation Values (for HMI)) is supported. E.g. a HMI device can use this flag to show/hide menus for energy monitoring values. FALSE = 0 TRUE = 1"
+0x0004,14.0,Gas_pressure_sensor_present,0,1,1,---,"*Note*: offset 14 = Bitfield to indicate some system parts, FALSE = 0, TRUE = 1"
+0x0004,14.1,Air_temperature_sensor_present,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,14.2,Flow_sensor_present,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,14.3,External_cutoff_present,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,14.4,Fluegas_STB_present,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,14.5,Supply_temperature_STB_present,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,14.6,On_off_roomthermostat_input_present,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,14.7,Solar buffer tank present,0,1,1,---,"Indicates the presence of a Solar Buffer Tank (incl. solar mixer valve and sensors). It is needed to provide an alternative to datahandling for the RC35 to know if the applicable menu items should be displayed. FALSE = 0, TRUE = 1"
+0x0004,15.0,Pump_Switch_off_temperature_adjustable,0,1,1,---,"BBuderus specific; If this bit is set, the pump switch off temperature (telegram 0x0016 offset 23) is adjustable (for example with the BC10)., FALSE = 0, TRUE = 1"
+0x0004,15.1,STB_test_present,0,1,1,---,"If this bit is set, the STB test (telegram 0x0005 offset 30) can be started (for example with the BC10)., FALSE = 0, TRUE = 1"
+0x0004,15.2,DHW_functionality_during_night_mode,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,15.3,Energy monitoring supported flag,0,1,1,---,"If this bit is set, telegram 0x0017 (Appliance Energy Monitoring Values (for HMI)) is supported. E.g. a HMI device can use this flag to show/hide menus for energy monitoring values., FALSE = 0, TRUE = 1"
+0x0004,15.4,Energy generation supported flag,0,1,1,---,"If this bit is set, telegram 0x0036 (Appliance Energy Generation Values (for HMI)) is supported. E.g. a HMI device can use this flag to show/hide menus for energy monitoring values., FALSE = 0, TRUE = 1"
 0x0004,16,Chimney_sweeper_step_size,0,100,1,%,""
 0x0004,17,Default_language_setup,0,255,1,---,"0 = DE Germany 1 = NL Netherlands 2 = DK Denmark 3 = FR France 4 = IT Italy 5 = GB United Kingdom 6 = ES Spain 7 = PT Portugal 8 = SE Sweden 9 = NO Norway 10 = LT Lithuania 11 = LV Latvia 12 = EE Estonia 13 = UA Ukraine 14 = CZ Czech Republic 15 = SK Slovakia 16 = HU Hungary 17 = HR Croatia 18 = SR Serbia 19 = RO Romania 20 = SI Slovenia 21 = TR Turkey 22 = GR Greece 23 = PL Poland 24 = RU Russian Federation 25 = US United States of America"
-0x0004,18-19,Nominal power DHW,0,65535,1,kW,"Value must be consistent with value calculated from ["Maximum appliance power" (DT4 I25-26) times"Maximum relative power DHW" (DT4 I24)]. Signal is kept for symmetry reasons."
-0x0004,20.0,HW_control_bitfield_support_DT53_I0_4_supported,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,20.1,HW_control_bitfield_support_DT53_I0_5_supported,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,20.2,HW_control_bitfield_support_DT53_I0_6_supported,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,20.3,HW_control_bitfield_support_DT53_I0_7_supported,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,20.4,HW_control_bitfield_support_DT53_I1_4_supported,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,20.5,HW_control_bitfield_support_DT53_I1_5_supported,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,20.6,HW_control_bitfield_support_DT53_I1_6_supported,0,1,1,---,"FALSE = 0 TRUE = 1"
-0x0004,20.7,HW_control_bitfield_support_DT4_I20__this_byte__supported,0,1,1,---,"FALSE = 0 TRUE = 1"
+0x0004,18-19,Nominal power DHW,0,65535,1,kW,"Value must be consistent with value calculated from ['Maximum appliance power' (telegram 0x0004 offset 25-26) times 'Maximum relative power DHW' (telegram 0x0004 offset 24)]. Signal is kept for symmetry reasons."
+0x0004,20.0,HW_control_bitfield_support_telegram_0x0035_offset0_4_supported,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,20.1,HW_control_bitfield_support_telegram_0x0035_offset0_5_supported,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,20.2,HW_control_bitfield_support_telegram_0x0035_offset0_6_supported,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,20.3,HW_control_bitfield_support_telegram_0x0035_offset0_7_supported,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,20.4,HW_control_bitfield_support_telegram_0x0035_offset1_4_supported,0,1,1,---,"FALSE = 0, TRUE = 1"
+0x0004,20.7,HW_control_bitfield_support_telegram_0x0004_offset20__this_byte__supported,0,1,1,---,"FALSE = 0, TRUE = 1"
 0x0004,21.0,Support_bitfield_modulating_oil_components_supported,0,1,1,---,""
-0x0004,22,Minimal relative power appliance,0,100,1,%,"This is the absolute minimum power in % related to the max. appliance power (DT4 I25-26). Same as DT4 I5 for HT3/MC10/ACUs."
-0x0004,23,Maximum relative power CH,0,100,1,%,"This is the maximum power for CH in % related to the max. appliance power (DT4 I25-26). If max. CH power is less than the max. appliance power the value reported here is less than 100%. It can e.g. be used to start Chimney Sweeper mode with 100% CH power where required."
+0x0004,22,Minimal relative power appliance,0,100,1,%,"This is the absolute minimum power in %, related to the max. appliance power (telegram 0x0004 offset 25-26). Same as telegram 0x0004 offset 5 for HT3/MC10/ACUs."
+0x0004,23,Maximum relative power CH,0,100,1,%,"This is the maximum power for CH in %, related to the max. appliance power (telegram 0x0004 offset 25-26). If max. CH power is less than the max. appliance power, the value reported here is less than 100%. It can e.g. be used to start Chimney Sweeper mode with 100% CH power where required."
 0x0004,24,Maximum relative power DHW,0,100,1,%,"This is the maximum power for DHW in % related to the max. appliance power. If max. DHW power is less than the max. appliance power the value reported here is less than 100%."
 0x0004,25-26,Maximum power appliance,0,65535,1,kW,"This is the highest power the appliance can deliver. It does not matter if that is archived in CH or DHW."
 0x0004,27,Min. system water pressure,0,255,0.1,bar,"This is the absolute minimum possible water pressure in the heating system."
@@ -1141,95 +1164,95 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x0004,30,System water pressure high threshold,0,255,0.1,bar,"This is the system water pressure threshold above that the pressure is"high"."
 0x0004,31,System water pressure too high threshold,0,255,0.1,bar,"This is the system water pressure threshold above that the pressure is"too high"."
 0x0004,32,Max. system water pressure,0,255,0.1,bar,"This is the absolute maximum possible water pressure in the heating system."
-0x0004,33,Critical supply temperature threshold,0,90,1,°C,"This temperature threshold is used with high power appliances to trigger a warning. *Note 1*: *used* only TRUE if code plug indicates the existence of a critical value for the flow temperature which is *lower* than what can maximally be set with DT230 I3 (max of DT230 I1). If this is not the case *used* shall be set to FALSE and value to 0. *Note 2*: If *used* is set to TRUE then the value *must* be > 0; NA = 0"
+0x0004,33,Critical supply temperature threshold,0,90,1,°C,"This temperature threshold is used with high power appliances to trigger a warning. *Note 1*: 'used' only TRUE if code plug indicates the existence of a critical value for the flow temperature, which is *lower* than what can maximally be set with telegram 0x00E6 offset 3 (max of telegram 0x00E6 offset 1). If this is not the case, 'used' shall be set to FALSE and value to 0. *Note 2*: If 'used' is set to TRUE, then the value *must* be > 0', NA = 0"
 0x0018,0,Supply_temperature_setpoint,0,90,1,°C,""
-0x0018,1-2,Sys.SupplyTemp_X,-32768,32767,0.1,°C,"NA_OPEN = -32768NA_SHORT = 32767"
+0x0018,1-2,Sys.SupplyTemp_X,-32768,32767,0.1,°C,"NA_OPEN = -32768, NA_SHORT = 32767"
 0x0018,3,Power_setpoint,0,255,1,%,"Because of the boost function for hot water this value can be higher than 100%."
 0x0018,4,Actual_Power,0,255,1,%,"Because of the boost function for hot water this value can be higher than 100%."
-0x0018,5.0,Operating_status_flags_1____CH,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,5.1,Operating_status_flags_1___HW,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,5.2,Operating_status_flags_1___Service,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,5.3,Operating_status_flags_1___Flame,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,5.4,Operating status flags 1 Boiler in heat-up phase,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,5.5,Operating status flags 1 Error Locking,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,5.6,Operating status flags 1 Error Blocking,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,5.7,Operating_status_flags_1__Maintenance_request,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,6.0,Heat_request_and_status_flags___CH_bus,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,6.1,Heat_request_and_status_flags___CH_Switch,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,6.2,Heat_request_and_status_flags___CH_Frost,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,6.3,Heat_request_and_status_flags___HW_Frost,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,6.4,Heat_request_and_status_flags___HW_detection_internal,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,6.5,Heat_request_and_status_flags____HW_detection_via_the_bus,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,6.6,Heat_request_and_status_flags,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,6.7,Heat_request_and_status_flags___Test_Mode,0,1,1,bool,"CH-High Efficiency pre heat-up FALSE = 0 TRUE = 1"
-0x0018,7.0,Relay_status_flags_1__Gasvalve_1st_burner,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,7.1,Relay_status_flags_1__Gasvalve_2nd_burner,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,7.2,Relay_status_flags_1__Fan,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,7.3,Relay_status_flags_1__Ignition,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,7.4,Relay_status_flags_1__Oilheater,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,7.5,Relay_status_flags_1__CH_pump,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,7.6,Relay_status_flags_1__3WV,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,7.7,Relay_status_flags_1__HW_circulation_pump,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,8.0,Oelfreigabe__Abgassperrklappe__always_zero_in_UBA3,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,8.1,Digital_inputs____Airflow_switch,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,8.2,Digital_inputs____LPG_burner,0,1,1,bool,"Indicates that a LPG set is installed in the field (always zero in UBA3) FALSE = 0 TRUE = 1"
-0x0018,8.3,Digital_inputs____Gas_pressure_switch,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,8.4,Digital_inputs____External_cut_off_switch,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,8.5,Digital_inputs,0,1,1,bool,"Combustion products discharge safety device (TTB) FALSE = 0 TRUE = 1"
-0x0018,8.6,Digital_inputs___Safety_Temperature_Limiter__MAX,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,8.7,Digital_inputs___RTH_switch,0,1,1,bool,"FALSE = 0 TRUE = 1"
+0x0018,5.0,Operating_status_flags_1____CH,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,5.1,Operating_status_flags_1___HW,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,5.2,Operating_status_flags_1___Service,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,5.3,Operating_status_flags_1___Flame,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,5.4,Operating status flags 1 Boiler in heat-up phase,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,5.5,Operating status flags 1 Error Locking,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,5.6,Operating status flags 1 Error Blocking,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,5.7,Operating_status_flags_1__Maintenance_request,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,6.0,Heat_request_and_status_flags___CH_bus,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,6.1,Heat_request_and_status_flags___CH_Switch,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,6.2,Heat_request_and_status_flags___CH_Frost,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,6.3,Heat_request_and_status_flags___HW_Frost,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,6.4,Heat_request_and_status_flags___HW_detection_internal,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,6.5,Heat_request_and_status_flags____HW_detection_via_the_bus,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,6.6,Heat_request_and_status_flags,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,6.7,Heat_request_and_status_flags___Test_Mode,0,1,1,bool,"CH-High Efficiency pre heat-up FALSE = 0, TRUE = 1"
+0x0018,7.0,Relay_status_flags_1__Gasvalve_1st_burner,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,7.1,Relay_status_flags_1__Gasvalve_2nd_burner,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,7.2,Relay_status_flags_1__Fan,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,7.3,Relay_status_flags_1__Ignition,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,7.4,Relay_status_flags_1__Oilheater,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,7.5,Relay_status_flags_1__CH_pump,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,7.6,Relay_status_flags_1__3WV,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,7.7,Relay_status_flags_1__HW_circulation_pump,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,8.0,Oelfreigabe__Abgassperrklappe__always_zero_in_UBA3,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,8.1,Digital_inputs____Airflow_switch,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,8.2,Digital_inputs____LPG_burner,0,1,1,bool,"Indicates that a LPG set is installed in the field (always zero in UBA3) FALSE = 0, TRUE = 1"
+0x0018,8.3,Digital_inputs____Gas_pressure_switch,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,8.4,Digital_inputs____External_cut_off_switch,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,8.5,Digital_inputs,0,1,1,bool,"Combustion products discharge safety device (TTB) FALSE = 0, TRUE = 1"
+0x0018,8.6,Digital_inputs___Safety_Temperature_Limiter__MAX,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,8.7,Digital_inputs___RTH_switch,0,1,1,bool,"FALSE = 0, TRUE = 1"
 0x0018,9-10,1st_Hot_water_temperature,-32768,32767,0.1,°C,""
 0x0018,11-12,2nd_Hot_water_temperature,-32768,32767,0.1,°C,""
-0x0018,13-14,Return_temperature,-32768,32767,0.1,°C,"NA_OPEN = -32768NA_SHORT = 32767"
+0x0018,13-14,Return_temperature,-32768,32767,0.1,°C,"NA_OPEN = -32768, NA_SHORT = 32767"
 0x0018,15-16,Flame_current,0,65535,0.1,µA,"Not_valid = 65535"
 0x0018,17,System_pressure,0,255,0.1,bar,"( 0 - 5 Bar resolution 0.1 Bar) Values between 0 and 254 are normal measurement values 255 means the sensor is not connected or defect. INVALID = 255"
 0x0018,18-19,Display_code,0,65535,1,---,""
 0x0018,20-21,Cause_code,0,65535,1,---,"Typical range: 200-65535"
 0x0018,22,EMS_MN_FAST_VL_WW_DURCHFLUSS,0,250,0.1,l/min,""
-0x0018,23.0,Storage_charge_pump,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,23.1,LPG_valve,0,1,1,bool,"This flag indicates whether currently the relays for liquid gas valve (LPG) shall be switched on (TRUE) or off (FALSE). FALSE = 0 TRUE = 1"
-0x0018,23.2,Source_pump,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,23.3,UM10_relay,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,23.4,HW_pump,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,23.5,Burner release relay,0,1,1,bool,"only for external burner control units FALSE = 0 TRUE = 1"
+0x0018,23.0,Storage_charge_pump,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,23.1,LPG_valve,0,1,1,bool,"This flag indicates whether currently the relays for liquid gas valve (LPG) shall be switched on (TRUE) or off (FALSE). FALSE = 0, TRUE = 1"
+0x0018,23.2,Source_pump,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,23.3,UM10_relay,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,23.4,HW_pump,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,23.5,Burner release relay,0,1,1,bool,"only for external burner control units FALSE = 0, TRUE = 1"
 0x0018,23.6,TT-FB reserved bits,0,0,1,---,"This bit is always fixed to zero"
 0x0018,23.7,TT-FB reserved bits,0,0,1,---,"This bit is always fixed to zero"
-0x0018,24.0,Fill_mode,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,24.1,UM10 in the system,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,24.2,UM10 input for burner blocking,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,24.3,Burner_start_released,0,1,1,bool,"Indication that a module like the UM10 or IUM has released the burner start. For the HTIII it means that it has received the release command (DT5I28) from the IUM. It does imply that the burner is on. FALSE = 0 TRUE = 1"
-0x0018,24.4,Burner_start_request,0,1,1,bool,"Indication for module like UM10 or IUM to activate the abgassperrklappe or LPG valve. FALSE = 0 TRUE = 1"
-0x0018,24.5,Central_heating_blocked__HTIII_only,0,1,1,bool,"Indication that external inputs like the external cut-off switch mechanical clock or central heating on/off switch (DT22I0) have blocked the central heating mode. FALSE = 0 TRUE = 1"
-0x0018,24.6,STB test is active. The burner tries to reach the STB temperature,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,24.7,Holiday_mode__HTIII_only,0,1,1,bool,"FALSE = 0 TRUE = 1"
+0x0018,24.0,Fill_mode,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,24.1,UM10 in the system,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,24.2,UM10 input for burner blocking,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,24.3,Burner_start_released,0,1,1,bool,"Indication that a module like the UM10 or IUM has released the burner start. For the HTIII it means that it has received the release command (telegram 0x0005,offset 28) from the IUM. It does imply that the burner is on., FALSE = 0, TRUE = 1"
+0x0018,24.4,Burner_start_request,0,1,1,bool,"Indication for module like UM10 or IUM to activate the abgassperrklappe or LPG valve. FALSE = 0, TRUE = 1"
+0x0018,24.5,Central_heating_blocked__HTIII_only,0,1,1,bool,"Indication that external inputs like the external cut-off switch, mechanical clock or central heating on/off switch (telegram 0x0016,offset 0) have blocked the central heating mode., FALSE = 0, TRUE = 1"
+0x0018,24.6,STB test is active. The burner tries to reach the STB temperature,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,24.7,Holiday_mode__HTIII_only,0,1,1,bool,"FALSE = 0, TRUE = 1"
 0x0018,25-26,air_temperature,-32768,32767,0.1,°C,""
 0x0018,27-28,Fan_speed_setpoint,0,900,10,rpm,""
 0x0018,29-30,Fan_speed,0,900,10,rpm,""
 0x0018,31,Fan_PWM_signal,0,255,1,---,""
 0x0018,32-33,Integral,0,65535,1,---,""
 0x0018,34,Setpoint_of_the_integral,0,255,1,---,""
-0x0018,35.0,Facilities errors Air temperature sensor defect,0,1,1,bool,"The burner control unit only has an error protocol for the locking and blocking errors. The human interfaces (e.g. RC35) store the facilities errors in its error protocol. FALSE = 0 TRUE = 1"
-0x0018,35.1,Facilities errors Boiler stays cold,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,35.2,Facilities errors Oil heater short,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,35.3,Facilities errors Oil heater broke,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,35.4,Facilities_errors,0,1,1,bool,"FALSE = 0 TRUE = 1"
-0x0018,35.5,Facilities_errors,0,1,1,bool,"FALSE = 0 TRUE = 1"
+0x0018,35.0,Facilities errors Air temperature sensor defect,0,1,1,bool,"The burner control unit only has an error protocol for the locking and blocking errors. The human interfaces (e.g. RC35) store the facilities errors in its error protocol. FALSE = 0, TRUE = 1"
+0x0018,35.1,Facilities errors Boiler stays cold,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,35.2,Facilities errors Oil heater short,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,35.3,Facilities errors Oil heater broke,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,35.4,Facilities_errors,0,1,1,bool,"FALSE = 0, TRUE = 1"
+0x0018,35.5,Facilities_errors,0,1,1,bool,"FALSE = 0, TRUE = 1"
 0x0018,35.6,Facilities_errors,0,1,1,bool,"FALSE = 0 TRUE = 1"
 0x0018,35.7,Facilities_errors,0,1,1,bool,"FALSE = 0 TRUE = 1"
 0x0018,36,Digital inputs 2,0,255,1,---,"36.0 External blocking (one more input for blocking the burner) (used by BRM10). 36.1 External burner control unit has locked (used by BRM10)."
-0x0018,37,Chimney Sweeper power setpoint,0,100,1,%,"This is the last requested Chimney Sweeper power setpoint during Chimney Sweeper (DT5 I4) or Burner Test (DT29 I1) mode. The 100% means max. appliance power. Therefore CH can have a maximum lower than 100%."
-0x0016,0,CH switch on/off,-1,0,1,bool,"YES = -1NO = 0"
+0x0018,37,Chimney Sweeper power setpoint,0,100,1,%,"This is the last requested Chimney Sweeper power setpoint during Chimney Sweeper (telegram 0x0005 offset 4) or Burner Test (telegram 0x001D offset 1) mode. The 100% means max. appliance power. Therefore CH can have a maximum lower than 100%."
+0x0016,0,CH switch on/off,-1,0,1,bool,"YES = -1, NO = 0"
 0x0016,1,Maximal_supply_temperature,30,90,1,°C,"in case of HTIII:min value can be=0 in case of summer mode NSC:"
 0x0016,2,Max__central_heating_power,0,100,1,%,"The control knob (poti) on the Bx must not have a dead-zone. Thus the output of the Bx poti must be recalculated."
-0x0016,3,Fixed_power_limitation,-1,0,1,---,"A fixed power limitation in the field is still needed. On the UBA 1 it was the 11 kW jumper.  This function is changed to a fixed power limitation.  The power limit is stored in the BCM and depends on the boiler.  For instance for boilers up to 32 kW the limit is 11 kW for boilers up to 70 kW it can be 50 kW. The limited CH power can be read in the Boiler identification block.  0 = off -1 = on on = -1off = 0"
+0x0016,3,Fixed_power_limitation,-1,0,1,---,"A fixed power limitation in the field is still needed. On the UBA 1 it was the 11 kW jumper.  This function is changed to a fixed power limitation. The power limit is stored in the BCM and depends on the boiler. For instance for boilers up to 32 kW the limit is 11 kW for boilers up to 70 kW it can be 50 kW. The limited CH power can be read in the Boiler identification block. 0 = off, -1 = on"
 0x0016,4,Supply_temp__Pos_tolerance,2,15,1,°C,""
 0x0016,5,Supply_temp__Neg_tolerance,-15,-2,1,°C,""
 0x0016,6,Anti_fast_cycle_time,0,60,1,min,""
-0x0016,7,Pump_functionality_switch,0,2,1,---,"0: No pump available.    When the pump is removed from the boiler this value can be set to no. The pump relay will never be    switched on even when a request comes over the bus.  1: Internal pump.    Normal CH pump (Factory setting). During a central heating or a hot water demand and in the post purge    time the EMS will control the pump. During the other moments the bus settings will be used.  2: External pump.    No pump available inside the boiler. Central heating group 1 will use the (external) pump and the controller    of this group has to activate this pump. The EMS only activates this pump if a Burner test (Abgastest) is    active or when a central heating demand from the on/off room thermostat (RTH switch) is active. NO = 0INTERNAL = 1EXTERNAL = 2"
+0x0016,7,Pump_functionality_switch,0,2,1,---,"0: No pump available.    When the pump is removed from the boiler this value can be set to no. The pump relay will never be switched on even when a request comes over the bus.  1: Internal pump. Normal CH pump (Factory setting). During a central heating or a hot water demand and in the post purge time the EMS will control the pump. During the other moments the bus settings will be used.  2: External pump. No pump available inside the boiler. Central heating group 1 will use the (external) pump and the controller of this group has to activate this pump. The EMS only activates this pump if a Burner test (Abgastest) is active or when a central heating demand from the on/off room thermostat (RTH switch) is active. NO = 0, INTERNAL = 1, EXTERNAL = 2"
 0x0016,8,Pump_post_purge_time,0,61,1,min,"0 – 60: Normal post purge time in minutes.  61: Post purge time is 24 hours. 24_Hours = 61"
 0x0016,9,Pump_speed_maximum,0,100,1,%,""
 0x0016,10,Pump_speed_minimum,0,100,1,%,""
-0x0016,11,Pump_head_selection,0,8,1,enum,"Only possible if a dialog pump is available (see DT4 I11 bit0).  Options other than option 0 will keep the pressure difference at a constant level. 0 = Normal modulating pump function 1 = Low 2 = Standard 3 = High 4 = Extra high 5 = Maximal 6-8 = Free MODULATING = 0DELTA_P_1 = 1DELTA_P_2 = 2DELTA_P_3 = 3DELTA_P_4 = 4DELTA_P_5 = 5DELTA_P_6 = 6Delta_P_7 = 7Delta_P_8 = 8"
+0x0016,11,Pump_head_selection,0,8,1,enum,"Only possible if a dialog pump is available (see telegram 0x0004, offset 11, bit0).  Options other than option 0 will keep the pressure difference at a constant level. 0 = Normal modulating pump function 1 = Low 2 = Standard 3 = High 4 = Extra high 5 = Maximal 6-8 = Free, MODULATING = 0, DELTA_P_1 = 1, DELTA_P_2 = 2, DELTA_P_3 = 3, DELTA_P_4 = 4, DELTA_P_5 = 5, DELTA_P_6 = 6, Delta_P_7 = 7, Delta_P_8 = 8"
 0x0016,12,Supply_temp__pos_tolerance_for_second_stage,2,15,1,K,"Switching off limit for two stage burners."
 0x0016,13,Supply_temp__neg_tolerance_for_second_stage,-15,-2,1,K,"Switching off limit for two stage burners."
 0x0016,14,Burner_off_limit_for_the_integral,4,75,400,---,"If the temperature is hotter then the setpoint and only 1 stage is on  this limit will be used by the integral for switching the burner on/off."
@@ -1239,11 +1262,24 @@ Telegram_ID,Offset,Variable_Name,Min,Max,Resolution,Unit,Comment
 0x0016,18,Setpoint_switch_time_for_the_integral,0,60,1,min,"After switching on or on a stage the integral for switching the burner on/off uses its own setpoint for this time."
 0x0016,19,off_time_for_the_integral,0,15,1,min,"After switching on or off a stage the integral for switching the burner on/off is not counted for this time."
 0x0016,20,Maximum_approach_speed_for_the_integral,0,10,1,---,"If the temperature is with speed or faster approaching the setpoint  the integral for switching the burner on/off is not counted for this time."
-0x0016,21,Correction_factor_minimum_power_for_the_fan,-9,9,1,---,"This factor changes the setpoint of the fanspeed at minimum power.  The amount of change depends on the boiler. If the bit in DT4I11b4 is set you can change this factor."
-0x0016,22,Correction_factor_minimum_power_for_the_fan,-9,9,1,---,"This factor changes the setpoint of the fanspeed at maximum power.  The amount of change depends on the boiler.  If the bit in DT4I11b4 is set you can change this factor."
-0x0016,23,Pump_Switch_off_temperature,0,65,1,°C,"If the bit in DT4I15b0 is set you can change the operating temperature.  The value will send under DT4I7 too but in DT4 you can’t change any parameter."
+0x0016,21,Correction_factor_minimum_power_for_the_fan,-9,9,1,---,"This factor changes the setpoint of the fanspeed at minimum power. The amount of change depends on the boiler. If the bit in telegram 0x0004,offset 11,b4 is set, you can change this factor."
+0x0016,22,Correction_factor_minimum_power_for_the_fan,-9,9,1,---,"This factor changes the setpoint of the fanspeed at maximum power. The amount of change depends on the boiler. If the bit in telegram 0x0004,offset 11,b4 is set, you can change this factor."
+0x0016,23,Pump_Switch_off_temperature,0,65,1,°C,"If the bit in telegram 0x0004,offset 15,b0 is set, you can change the operating temperature.  The value will send under telegram 0x0004,offset 7 too, but in telegram 0x0004 you can’t change any parameter."
 0x0016,24,Building_Dry_setpoint,30,90,1,°C,""
-0x0016,25,Manual_Mode,-1,0,1,---,"The burner controller only acts as a server for this variable and stores it non volatile.  When the system is in manual mode the human interface will periodically send the Manual Mode setpoint  (as it is stored in DT22I26) trough DT26I0.     0x00 = Disabled     0xFF = Enabled     0 = off     -1 = on ON = -1OFF = 0"
-0x0016,26,Manual_Mode_setpoint,30,90,1,°C,"The burner controller only acts as a server for this variable and stores it non volatile. This is the setpoint used during manual mode which is enabled with DT22I25.  The value may be altered using the human interface.  The initial value is obtained from the HCM and may be brand/boiler specific."
-0x0016,27,Resistive_system_present,-1,0,1,bool,"Resistive system present This function is created for appliances with a modulating pump and modulating burner load.  In cases when the appliance has been installed within a small central heating (CH) system  the system resistance can become too high.  High resistance in a heating system can cause the temperature difference across the system to increase. High resistance in a CH system can be recognized by a larger temperature delta between the supply and the return.  In case a certain delta limit will be exceed after a debounce time  the pump speed must be increased with a fixed step to overcome the system resistance and reduce the temperature delta.  After a defined time the result of the increased pump speed must be checked based on the temperature delta.     0 = OFF    -1 = ON ON = -1OFF = 0"
+0x0016,25,Manual_Mode,-1,0,1,---,"The burner controller only acts as a server for this variable and stores it non volatile. When the system is in manual mode, the human interface will periodically send the Manual Mode setpoint  (as it is stored in telegram 0x0016,offset 26) trough telegram 0x001A,offset 0. 0x00 = Disabled, 0xFF = Enabled, 0 = off, -1 = on"
+0x0016,26,Manual_Mode_setpoint,30,90,1,°C,"The burner controller only acts as a server for this variable and stores it non volatile. This is the setpoint used during manual mode, which is enabled with telegram 0x0016,offset 25. The value may be altered using the human interface.  The initial value is obtained from the HCM and may be brand/boiler specific."
+0x0016,27,Resistive_system_present,-1,0,1,bool,"Resistive system present This function is created for appliances with a modulating pump and modulating burner load.  In cases when the appliance has been installed within a small central heating (CH) system  the system resistance can become too high.  High resistance in a heating system can cause the temperature difference across the system to increase. High resistance in a CH system can be recognized by a larger temperature delta between the supply and the return. In case a certain delta limit will be exceed after a debounce time  the pump speed must be increased with a fixed step to overcome the system resistance and reduce the temperature delta. After a defined time the result of the increased pump speed must be checked based on the temperature delta. 0 = OFF, -1 = ON"
 0x0014,0-2,Simulated system time,0,16777215,1,min,""
+0x0033,0,Token number which contains the DHW function,0,127,1,token,"Value 8 is interpreted as YES Token number, which contains the functionality for the hot water system, NO = 0, EMS = 8, YES = 8"
+0x0033,1,Hot water switch (on/off).,-1,0,1,bool,"This is a BCxx function! For systems with storage tank a frost protection stays active.  If hot water is switched off the hot water circulation pump will be switched off as well., ON = 0xFF, OFF = 0x00"
+0x0033,2,Hot water temperature setpoint,30,80,1,°C,"This value is the setpoint for the hot water temperature getting out the hot water system.  For flow through systems, this is the setpoint for the outlet temperature. For system with a storage tank this is the setpoint for the storage.  And therefore the outlet temperature."
+0x0033,3,Hot water storage hysteresis,-20,-2,1,K,"(in Kelvin relative to HW-setpoint)  This value is the hysteresis for the storage tank."
+0x0033,4,Hot water rest energy switch,-1,0,1,bool,"YES = 0xFF, NO = 0x00"
+0x0033,5,Hot water supply temperature offset/Kesselanhebung,25,40,1,K,"Defines the supply temperature setpoint to heat-up the storage tank"
+0x0033,6,Circulation pump on/off ,-1,0,1,bool,"The HW-circulation pump can be switched off., YES = 0xFF, NO = 0x00"
+0x0033,7,Circulation pump is active x times per hour,1,7,1,N/hour,"1..6 = no. of interval with 3 minutes 'on' 7 = always on Defines how many starts per hour the circulation pump runs. Factory default is 2. Pump running time is fixed 3 minutes., ALWAYS_ON = 7"
+0x0033,8,Thermal disinfecting setpoint,60,80,1,°C,"When the Thermal disinfecting function is activated, this value is the setpoint for the storage.  The function is activated with a bit in the HW control values block.  The EMS will heat-up the HW-system to this temperature, and will keep it there for a certain time.  The time depends on the requested temperature. The higher the temperature the shorter the time, etc.  At the end of the heat-up time, the HW circulation pump will run, for a certain time to disinfect the HW pipes as well."
+0x0033,9,Economy,-40,0,1,°C,"when this function is active, the storage temperature for Bottich systems will be reduced.  This function is not available for large (> 2 ltr) HW systems."
+0x0033,10,Hot water Three-way valve/Chargepump,-1,0,1,bool,"This parameter can be used for single boilers to inform the EMS what is externally connected.  If Three-way valve is selected, both the internal and external ?three-way valve/chargepump? outputs are controlled (parallel).  This will be the default condition. If Chargepump is selected, only the ?three-way valve/chargepump? output is controlled and not the internal three-way valve output (Priority).  NSC default = 0 = [CHARGEPUMP], 3WAYVALVE = 0xFF, CHARGEPUMP = 0"
+0x0033,11,DHW priority,-1,0,1,enum,"(partly/full). Like alternating mode (telegram 0x0033,offset 12), but on system level.  Only used for DHW tanks behind the low loss header controlled by an IPM., full = 0xFF, partly = 0"
+0x0033,12,Alternating mode,-1,0,1,bool,"(Yes/No). If this function is active (Yes) the appliance switches between CH and DHW operating mode in case both requests are active.  The switching time is appliance dependant, but is normally 10 minutes., YES = 0xFF, NO = 0x00"