> 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

<figure><img src="https://2592874069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQR4vCFzt6ixgsqlR3pdR%2Fuploads%2FQgsWkUgRHAKELWVokVL0%2FHVACModbus.SOLVIMUS_GE20_MBUS_VALUE.png?alt=media&amp;token=c0f3569f-2344-49e7-a6de-087cb87bb755" alt=""><figcaption></figcaption></figure>

InOut:

| Scope       | Name                          | Type                             | Initial      | Comment                                                                                                                                   |
| ----------- | ----------------------------- | -------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Input       | `xEn`                         | `BOOL`                           | TRUE         | Enable / disable communication (TRUE = enable)                                                                                            |
| Input       | `byUnitId`                    | `BYTE`                           | 255          | <p>Device address (defined by IP address) (<br>Default: 255)</p>                                                                          |
| Input       | `xUpdateActual`               | `BOOL`                           | FALSE        | <p>Update of actual values (on every rising edge<br>)</p>                                                                                 |
| Input       | `wBaseAdressMbusDevice`       | `WORD`                           | 10           | <p>Modbus - base register for the information of the MBus -<br>device</p>                                                                 |
| Input       | `wBaseAdressMbusValue`        | `WORD`                           | 20           | <p>Modbus - base register for the information of the MBus -<br>value</p>                                                                  |
| Input       | `xResError`                   | `BOOL`                           | FALSE        | <p>Reinitialization of the outputs <code>eErrorCodeCom</code> on the<br>error-free state (on each rising edge)</p>                        |
| Inout       | `ModbusClient`                | `ModbusClientBase`               |              | Client of the device                                                                                                                      |
| Output      | `liVal_Raw`                   | `LINT`                           |              | <p>Meter value in 64-bit integer format - signed -<br>unscaled</p>                                                                        |
| Output      | `rVal_Raw_SF`                 | `REAL`                           |              | Scaling factor for `liVal_Raw`                                                                                                            |
| Output      | `liVal`                       | `LINT`                           |              | <p>Meter value in 64-bit integer format - signed -<br>scaled (=  <code>liVal\_Raw</code> x scaling factor <code>rVal\_Raw\_SF</code>)</p> |
| Output      | `rVal`                        | `REAL`                           |              | <p>Meter value in 32-bit IEEE 754 floating-point format -<br>signed - scaled to <code>byValueUnit</code> (= final value<br>)</p>          |
| 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`                             |              | <p>Timestamp of the MBus - device (UTC, in Germany UTC +1 /<br>+2 h depending on daylight saving / standard time)</p>                     |
| 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           | <p>Offset for calculating the base address (prerequisite:<br>xBaseAdressMode = TRUE)</p>                                                  |
| Input Const | `xBaseAdressMode`             | `BOOL`                           | FALSE        | Type of defining the base address:                                                                                                        |
| Input Const | `diAdrOffset`                 | `DINT`                           | 0            | <p>Offset for calculating the Modbus addresses (from the Modbus<br>registers) (permitted range: -1, 0, +1)</p>                            |
| 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 | <p>Update interval for the operations that are influenced by the input<br><code>xUpdateActual</code> influenced</p>                       |


---

# 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/solvimus/solvimus_ge20_mbus_value.md?ask=<question>&goal=<user_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.
