> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/codesys-hvac/en/hvac-modbus-library/functionblocks/kieback_und_peter/kp_md15_mod_n_he_easy.md). # KP\_MD15\_MOD\_N\_HE\_EASY ## `KP_MD15_MOD_N_HE_EASY` (FB) `FUNCTION_BLOCK` KP\_MD15\_MOD\_N\_HE\_EASY ### Representation
InOut: | Scope | Name | Type | Initial | Comment | | ----------- | ------------------- | ------------------------------------- | --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Input | `xEn` | `BOOL` | TRUE | Enable / disable communication (TRUE = enable) | | Input | `byUnitId` | `BYTE` | 0 |

Device address (1… 247, default =
factory setting)

| | Input | `xUpdateActual` | `BOOL` | FALSE |

Update of actual values (on every rising edge
)

| | Input | `xUpdateSetp` | `BOOL` | FALSE |

Update of setpoints (on every rising edge
)

| | Input | `xResError` | `BOOL` | FALSE |

Reinitialization of the outputs eErrorCodeCom or
sErrorCodeDev to the fault-free state (on every rising edge)

| | Input | `rSetpPos` | `REAL` | 0.0 | Setpoint - Position in % (0.0 - 100.0 %) (0.0% = spindle extended) | | Inout | `ModbusClient` | `ModbusClientBase` | | Client of the device | | Output | `rSetpPositionFb` | `REAL` | | Setpoint - Position in % (0.0 - 100.0 %) (0.0% = spindle extended) — feedback | | Output | `rPosition` | `REAL` | | Current position in % (0.0 - 100.0 %) (0.0% = spindle extended) | | Output | `xAlarm` | `BOOL` | FALSE | Collective fault (TRUE = fault) | | Output | `xAlarmCom` | `BOOL` | FALSE | Collective fault - communication (TRUE = fault) | | Output | `eErrorCodeCom` | ModbusErrorCode | | Error code - communication (0 = no error) | | Output | `sErrorCodeDev` | `STRING` | | String with the numbers of the active device errors (Bit 0 = number 1, Bit 1 = number 2, etc.) | | Output | `xBusy` | `BOOL` | | Communication indicator (TRUE = communication) | | Input Const | `eOpMode` | KP\_MD15\_MOD\_N\_HE\_OP\_MODE | KP\_MD15\_MOD\_N\_HE\_OP\_MODE.SETPOINT |

Current operating mode
0 = control via setpoint
1 = Open
2 = Close
3 = Parameter rMinPos
5 = Parameter rMaxPos
6 = room temperature control loop

| | Input Const | `rBusFailPos` | `REAL` | 100.0 | Current position in % (0.0 - 100.0 %) (0.0% = spindle extended) in the event of a bus error (120 s) | | Input Const | `eBusFailMode` | KP\_MD15\_MOD\_N\_HE\_BUS\_FAIL\_MODE | KP\_MD15\_MOD\_N\_HE\_BUS\_FAIL\_MODE.NO\_DETECTION |

Current operating mode in the event of a bus error
0 = no monitoring
1 = Close after 120s without communication
2 = Open after 120s without communication
3 = Parameter rBusFailPos after 120s without communication

| | Input Const | `tTimeUpdateSetp` | `TIME` | TIME#45s0ms |

Update interval for the processes influenced by the input
xUpdateSetp influenced

| | Input Const | `tTimeUpdateActual` | `TIME` | TIME#3s0ms |

Update interval for the processes influenced by the input
xUpdateActual influenced

| --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.powerio.com/hub/codesys-hvac/en/hvac-modbus-library/functionblocks/kieback_und_peter/kp_md15_mod_n_he_easy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.