> 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/oppermann/oppermann_pv_mod_adx.md).

# OPPERMANN\_PV\_MOD\_ADX

## `OPPERMANN_PV_MOD_ADX` (FB)

`FUNCTION_BLOCK` OPPERMANN\_PV\_MOD\_ADX

### Representation

<figure><img src="/files/e35632dc3eb5339740269d5d4d7c10ea1bac6318" alt=""><figcaption></figcaption></figure>

### General

> This is a differential pressure - volume flow - transmitter with different measuring ranges:

> PV `MOD` AD1: 0 - 1000 Pa PV `MOD` AD4: 0 - 4000 Pa

> The Modbus interface and other parameters are configured via NFC and app when a display is present (variant 1). The Modbus interface and other parameters are configured via buttons when a display is present (variant 2).

> The measured value offset can be set in 10 stages using a rotary switch on the device. A manual zero-point adjustment is possible on the device. A termination resistor (120 ohms) can be activated / deactivated.

> The Modbus interface is parameterized as follows without any further settings:

> RTU 9600 baud 8 data bits even parity 1 stop bit device address = 1

InOut:

| Scope       | Name                    | Type               | Initial    | Comment                                                                                                                                                             |
| ----------- | ----------------------- | ------------------ | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Input       | `xEn`                   | `BOOL`             | TRUE       | Enable / disable communication (TRUE = enable)                                                                                                                      |
| Input       | `byUnitId`              | `BYTE`             | 0          | Device address (1 .. 127)                                                                                                                                           |
| Input       | `xUpdateActual`         | `BOOL`             | FALSE      | <p>Updating the actual values (at every rising edge<br>) (range: operation)</p>                                                                                     |
| Input       | `xResError`             | `BOOL`             | FALSE      | <p>Reinitialization of the output <code>eErrorCodeCom</code> (with every<br>rising edge)</p>                                                                        |
| Inout       | `ModbusClient`          | `ModbusClientBase` |            | Client of the device                                                                                                                                                |
| Output      | `rDifPressure`          | `REAL`             |            | Differential pressure in Pa                                                                                                                                         |
| Output      | `rVolumeFlow`           | `REAL`             |            | Volume flow in m3/h                                                                                                                                                 |
| Output      | `rDevVoltage`           | `REAL`             |            | Supply voltage for the device in volts                                                                                                                              |
| Output      | `xSensorOffsetInDevice` | `BOOL`             |            | <p>Indication of whether the sensors must be calibrated in the device<br>(TRUE = calibration in the device required, FALSE = calibration in the<br>FB required)</p> |
| Output      | `xAlarm`                | `BOOL`             |            | Collective fault (TRUE = fault)                                                                                                                                     |
| Output      | `xAlarmCom`             | `BOOL`             |            | Collective fault - communication (TRUE = fault)                                                                                                                     |
| Output      | `eErrorCodeCom`         | ModbusErrorCode    |            | Error code - communication (0 = no error)                                                                                                                           |
| Output      | `xBusy`                 | `BOOL`             |            | Communication indicator (TRUE = communication)                                                                                                                      |
| Input Const | `tTimeUpdateActual`     | `TIME`             | TIME#3s0ms | <p>Update interval for the processes 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 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/oppermann/oppermann_pv_mod_adx.md?ask=<question>&goal=<endgoal>
```

`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.