> 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/belimo/belimo_epxxxx_fw_3_0_8_mod.md).
# BELIMO\_EPXXXX\_FW\_3\_0\_8\_MOD
## `BELIMO_EPXXXX_FW_3_0_8_MOD` (FB)
`FUNCTION_BLOCK` BELIMO\_EPXXXX\_FW\_3\_0\_8\_MOD
### **Representation**
### Guidelines - Software creation
The following function codes (FC) are supported: 3, 4 (in addition: 2, 4, 16)
For write operations on 32-bit data points (2 consecutive Modbus registers), FC16 must be used. No additional registers may then be written in this telegram.
Format of 32-bit data points: Register+0 (LSW): H-byte L-byte Register+1 (MSW): H-byte L-byte
FC 02 may only be used for register 105 (Malfunction and service information, start address = 1664).
* For addressing, the address specifications are to be used, not the register addresses.
* For unused registers, the value 65535 (dec.) is read / written
* Modbus addresses 1 - 247 can be set directly on the valve.
{% hint style="info" %}
All writable register addresses > 100 are persistent and must not be written cyclically
{% endhint %}
InOut:
| Scope | Name | Type | Initial | Comment |
| ----------- | ----------------------- | ------------------------------------------------ | --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Input | `xEn` | `BOOL` | TRUE | Enable / disable communication (TRUE = enable) |
| Input | `byUnitId` | `BYTE` | 1 | Device address (1 .. 247) |
| Input | `xUpdateActual` | `BOOL` | FALSE |
Update of actual values (on every rising edge )
|
| Input | `xUpdateSetp` | `BOOL` | FALSE |
Update of setpoints (on every rising edge )
|
| Input | `xUpdateConfig` | `BOOL` | FALSE |
Update of configuration (on every rising edge) (write and read access)
|
| Input | `xUpdateInfo` | `BOOL` | FALSE |
Information update (on every rising edge)
|
| Input | `xResError` | `BOOL` | FALSE |
Reinitialization of the outputs eErrorCodeCom or stErrorCodeDev to the fault-free state (at each rising edge)
|
| Input | `rRelSetp` | `REAL` | 0.0 |
Relative setpoint - position/flow in % (0.0 - 100.0 %)
Position control: 0.0 - 100.0% refer to the relative position Flow control: 0.0 - 100.0% refer to the range 0 - Vmax (address 106) Forced override of the control signal - position/flow (0 = None)
|
| Input | `eCommand` | BELIMO\_EPXXXX\_FW\_3\_0\_8\_COMMAND | BELIMO\_EPXXXX\_FW\_3\_0\_8\_COMMAND.None | Command for service functions (0 = None) |
| Inout | `ModbusClient` | `ModbusClientBase` | | Client of the device |
| Output | `eSetpSourceFb` | BELIMO\_EPXXXX\_FW\_3\_0\_8\_SETPOINT\_SOURCE | |
Feedback - source for the setpoint - position/flow (1 = Modbus)
Update interval for the operations that are 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.powerio.com/hub/codesys-hvac/en/hvac-modbus-library/functionblocks/belimo/belimo_epxxxx_fw_3_0_8_mod.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
