> 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-library/functionblocks/numeric/absa.md).

# AbsA

## `AbsA` (FB)

FUNCTION\_BLOCK AbsA

### Short description

> Anti-blocking protection for an analog signal

### Representation

<figure><img src="https://2592874069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQR4vCFzt6ixgsqlR3pdR%2Fuploads%2Fgit-blob-f21f0a26ee12cc2da47b6fbb0c172a97c9223b8c%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

### Interfaces

#### Inputs

| Name     | Data type | Value range | Initial value | Function          |
| -------- | --------- | ----------- | ------------- | ----------------- |
| *rPosFb* | REAL      |             |               | Position feedback |

#### Outputs

| Name          | Data type       | Value range | Initial value | Function                                          |
| ------------- | --------------- | ----------- | ------------- | ------------------------------------------------- |
| *rOut*        | REAL            |             |               | Analog - output                                   |
| *xAbsOn*      | BOOL            |             |               | Display - anti-blocking process                   |
| *dtAbsLastOn* | DATE\_AND\_TIME |             |               | Start date/time of the last anti-blocking process |

#### Setpoints / Parameters

| Name             | Data type | Value range | Initial value | Function                                 |
| ---------------- | --------- | ----------- | ------------- | ---------------------------------------- |
| **rMinChange**   | REAL      |             | 10.0          | Minimum position change                  |
| **tTime**        | TIME      |             | 180s          | Duration of the anti-blocking process    |
| **eDay**         | eDoW      |             | eDow\.Monday  | Weekday of the anti-blocking process     |
| **todStartTime** | TOD       |             | 08:00:00      | Start time of the anti-blocking process  |
| **rMinLimit**    | REAL      |             | 0             | Lower limit for the analog output *rOut* |
| **rMaxLimit**    | REAL      |             | 100           | Upper limit for the analog output *rOut* |

### Functional description

#### General

This function block is used to monitor the position feedback *rPosFb* for activity. The test period always covers 168 hours (= 1 week).\
The position feedback *rPosFb* is active if its value changes during the test period by an amount greater than the minimum position change **rMinChange** changed.\
The anti-blocking process is thus inhibited (= anti-blocking process not active), the test period starts again.\
\
If no activity was detected during the test period, the anti-blocking process is triggered with the duration **tTime** on the weekday **eDay** at the time **todStartTime** triggered. (= anti-blocking process active).\
At the same time, the test period starts again.\
\
During the anti-blocking process, at the analog output *rOut* depending on the current value of the position feedback *rPosFb* different signals are output at the start of the anti-blocking process.\
\
Condition 1: *rPosFb* > 51% of the upper limit for the analog output *rOut*:\
\
*rOut* = **rMinLimit**\
\
Condition 2: *rPosFb* <= 51% of the upper limit for the analog output *rOut*:\
\
*rOut* = **rMaxLimit**\
\
When the anti-blocking process is not active, at the analog output *rOut* the value 0.0 is output.\
\
The initial triggering of the anti-blocking process may, depending on the relevant settings (weekday **eDay** and **todStartTime**) be delayed (example: test period ended on Tuesday morning, triggering of the anti-blocking process only on the following Monday).\
\
At the output *dtAbsLastOn* the start date and start time of the last anti-blocking process are available.

{% hint style="info" %}
**Requirement for using the function block AbsA**

For correct operation, the use of the TimeRead2 function block is required.
{% endhint %}

#### Display - anti-blocking process *xAbsOn*

This output is used to indicate an active anti-blocking process (*xAbsOn* = TRUE).

#### Setpoint / parameter **eDay**

The anti-blocking function can be **eDay** = eDow\.Inactive globally disabled.

#### Setpoint / parameter **tTime**

The anti-blocking function can be **tTime** = 0s globally disabled.

### CODESYS

InOut:

| Scope       | Name           | Type   | Initial           |
| ----------- | -------------- | ------ | ----------------- |
| Input       | `rPosFb`       | `REAL` |                   |
| Input Const | `rMinChange`   | `REAL` | 10                |
| Input Const | `tTime`        | `TIME` | TIME#3m0s0ms      |
| Input Const | `eDay`         | eDoW   | eDow\.Monday      |
| Input Const | `todStartTime` | `TOD`  | TIME\_OF\_DAY#8:0 |
| Input Const | `rMinLimit`    | `REAL` | 0                 |
| Input Const | `rMaxLimit`    | `REAL` | 100               |
| Output      | `rOut`         | `REAL` |                   |
| Output      | `xAbsOn`       | `BOOL` |                   |
| Output      | `dtAbsLastOn`  | `DT`   |                   |


---

# 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-library/functionblocks/numeric/absa.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.
