> 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/components/firedampertest.md).

# FireDamperTest

## `FireDamperTest` (FB)

FUNCTION\_BLOCK FireDamperTest

### Short description

> Anti-blocking protection for a binary signal

### Representation

<figure><img src="https://2592874069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQR4vCFzt6ixgsqlR3pdR%2Fuploads%2FaDxtHbCiJ46PGEPSlSqN%2FFireDamperTest.png?alt=media&amp;token=25cf02d2-2089-47e7-9bcf-cb3e28ad53e4" alt=""><figcaption></figcaption></figure>

### Interfaces

#### Inputs

| Name  | Data type | Value range | Initial value | Function            |
| ----- | --------- | ----------- | ------------- | ------------------- |
| *xFb* | BOOL      |             |               | Operational message |

#### Outputs

| Name          | Data type       | Value range | Initial value | Function                                                |
| ------------- | --------------- | ----------- | ------------- | ------------------------------------------------------- |
| *xOut*        | BOOL            |             |               | Enable - Output                                         |
| *xAbsOn*      | BOOL            |             |               | Display - blocking protection process                   |
| *dtAbsLastOn* | DATE\_AND\_TIME |             |               | Start date/time of the last blocking protection process |

#### Setpoints / Parameters

| Name             | Data type | Value range | Initial value | Function                                      |
| ---------------- | --------- | ----------- | ------------- | --------------------------------------------- |
| **tMinFbTime**   | TIME      |             | T#30s         | Minimum operating duration                    |
| **tTime**        | TIME      |             | 120s          | Duration of the blocking protection process   |
| **eDay**         | eDoW      |             | eDow\.Monday  | Weekday of the blocking protection process    |
| **todStartTime** | TOD       |             | 08:00:00      | Start time of the blocking protection process |

### Functional description

#### General

This function block is used to monitor the operating message *xFb* for activity. The test period is 168 hours each time (= 1 week).\
The operating message *xFb* is active if it is continuously active once during the test period for the minimum operating duration **tMinFbTime** is continuously active.\
The blocking protection process is thus suppressed; the test period starts again.\
If no operating message is available, the request / enable can alternatively be connected.\
\
If no activity was detected during the test period, the blocking protection process (enable - output *xOut* = TRUE) with the duration **tTime** on the weekday **eDay** at the time **todStartTime** triggered.\
At the same time, the test duration starts again.\
The initial triggering of the blocking protection process may, depending on the relevant settings (weekday **eDay** and **todStartTime**) be delayed.

> **Example**
>
> Test period ended on Tuesday morning, triggering of the blocking protection process only on the following Monday.

At output *dtAbsLastOn* the start date and start time of the last blocking protection process are available.

> **Prerequisite for using the function block AbsB**
>
> For correct operation, the use of the TimeRead2 function block is required.

#### Enable - Output *xOut*

| *xFb* | Anti-blocking protection process | *xOut* | Notes                                  |
| ----- | -------------------------------- | ------ | -------------------------------------- |
| X     | FALSE                            | FALSE  | Blocking protection process not active |
| X     | TRUE                             | TRUE   | Blocking protection process active     |

Legend: X = any

#### Display - blocking protection process *xAbsOn*

| *xFb* | Anti-blocking protection process | *xAbsOn* | Notes                                  |
| ----- | -------------------------------- | -------- | -------------------------------------- |
| X     | FALSE                            | FALSE    | Blocking protection process not active |
| X     | TRUE                             | TRUE     | Blocking protection process active     |

Legend: X = any

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

The blocking protection function can be blocked by setting **eDay** = eDow\.Inactive in general.

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

The blocking protection function can be blocked by setting **tTime** = 0s in general.

### CODESYS

InOut:

| Scope       | Name              | Type    | Initial |
| ----------- | ----------------- | ------- | ------- |
| Input       | `xAlarmSteuerSpg` | `BOOL`  | FALSE   |
| Input       | `xTestOK`         | `BOOL`  | FALSE   |
| Output      | `xTestEx`         | `BOOL`  | FALSE   |
| Output      | `dtTestLastStart` | `DT`    |         |
| Output      | `dtTestLastOK`    | `DT`    |         |
| Input Const | `udiMaxTime`      | `UDINT` | 5       |
| Input Const | `xVisuStart`      | `BOOL`  | FALSE   |
| Input Const | `xVisuStop`       | `BOOL`  | FALSE   |


---

# 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/components/firedampertest.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.
