> 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/solvimus/solvimus_ge20_mbus_value.md). # SOLVIMUS\_GE20\_MBUS\_VALUE ## `SOLVIMUS_GE20_MBUS_VALUE` (FB) `FUNCTION_BLOCK` SOLVIMUS\_GE20\_MBUS\_VALUE ### Representation
InOut: | Scope | Name | Type | Initial | Comment | | ----------- | ----------------------------- | -------------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------- | | Input | `xEn` | `BOOL` | TRUE | Enable / disable communication (TRUE = enable) | | Input | `byUnitId` | `BYTE` | 255 |

Device address (determined by IP address) (
Default: 255)

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

Update of actual values (on every rising edge
)

| | Input | `wBaseAdressMbusDevice` | `WORD` | 10 | Modbus - base register for the information of the MBus device | | Input | `wBaseAdressMbusValue` | `WORD` | 20 | Modbus - base register for the information of the MBus value | | Input | `xResError` | `BOOL` | FALSE |

Reinitialization of the outputs eErrorCodeCom in the
fault-free state (on each rising edge)

| | Inout | `ModbusClient` | `ModbusClientBase` | | Client of the device | | Output | `liVal_Raw` | `LINT` | |

Meter value in the format 64-bit integer - signed -
unscaled

| | Output | `rVal_Raw_SF` | `REAL` | | Scaling factor for `liVal_Raw` | | Output | `liVal` | `LINT` | |

Meter value in the format 64-bit integer - signed -
scaled (= liVal\_Raw x scaling factor rVal\_Raw\_SF)

| | Output | `rVal` | `REAL` | |

Meter value in the format 32-bit floating-point IEEE 754 -
signed - scaled to byValueUnit (= final value
)

| | Output | `rVal_kWh` | `REAL` | | (`rVal` in kWh) x scaling factor `rVal_kWh_SF` | | Output | `eValUnit` | SOLVIMUS\_GE20\_MBUS\_UNIT\_TYPE | | Unit of the meter value | | Output | `dtSysTime` | `DT` | |

Timestamp of the MBus device (UTC, in Germany UTC +1 /
+2 h depending on summer / winter time)

| | 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 | `xBusy` | `BOOL` | | Communication indicator (TRUE = communication) | | Input Const | `wBaseAdressMbusDeviceOffset` | `WORD` | 10 |

Offset for calculating the base address (prerequisite:
xBaseAdressMode = TRUE)

| | Input Const | `xBaseAdressMode` | `BOOL` | FALSE | Type of determination of the base address: | | Input Const | `diAdrOffset` | `DINT` | 0 |

Offset for calculating the Modbus addresses (from the Modbus
registers) (permitted range: -1, 0, +1)

| | Input Const | `rVal_kWh_SF` | `REAL` | 1.0 | Scaling factor for the output `rVal_kWh` | | Input Const | `rVal_SF` | `REAL` | 1.0 | Scaling factor for the output `rVal` | | Input Const | `tTimeUpdateActual` | `TIME` | TIME#1m0s0ms |

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/solvimus/solvimus_ge20_mbus_value.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.