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

# FireDamperMotSmoke

## `FireDamperMotSmoke` (FB)

FUNCTION\_BLOCK FireDamperMotSmoke

### Short description

> Control of a motorized fire damper with two position feedback signals\
> Additional functions: functional test of the fire damper\
> Typical application: control of a fire damper in an HVAC system

### Representation

<figure><img src="https://2592874069-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQR4vCFzt6ixgsqlR3pdR%2Fuploads%2F6a6PLr0DJ4zAamDGR2DY%2FFireDamperMotSmoke.png?alt=media&amp;token=5f99658e-7fc6-4f31-85d6-3ce2ad1edeeb" alt=""><figcaption></figcaption></figure>

### Functional description

#### General

This function block controls a binary motorized fire damper(*xEn* = TRUE), monitors the runtime during the opening and closing process and can perform a complete fire damper test.\
The function block can be operated either in normal mode or in test mode.\
Test mode has a higher priority than normal mode and can be triggered by a rising edge at the input *xTestEx* and / or at the setpoint / parameter **xRunTest** be triggered.

#### Release opening / closing of the fire damper before manual override *xAB*

The release of opening / closing of the fire damper before manual override *xAB* remains unchanged from the request for opening / closing of the fire damper *xEn* if the fire damper test is not active.

#### Enable opening / closing of the fire damper after manual override *xHB*

The release of opening / closing of the fire damper after manual override *xHB* corresponds to the release of opening / closing of the fire damper before manual override *xAB* additionally extended by a manual override module

| *xAB* | **eManModeB**  | *xHB* | Notes                                     |
| ----- | -------------- | ----- | ----------------------------------------- |
| FALSE | eMANBIN.Auto   | FALSE | Manual override module in automatic mode  |
| TRUE  | eMANBIN.Auto   | TRUE  | Manual override module in automatic mode  |
| X     | eMANBIN.ManOn  | TRUE  | Manual override module in manual mode On  |
| X     | eMANBIN.ManOff | FALSE | Manual override module in manual mode Off |

Legend: X = any

#### Collective fault *xAlarm*

The collective fault *xAlarm* is activated (= TRUE) if at least one of the following conditions is met:

1\) The fault message for the opening feedback *xAlarmOpen* is active (= TRUE).\
\
2\) The fault message for the closing feedback xAlarmClosed is active (= TRUE).\
\
3\) The fire damper is not fully open (xOpen = FALSE).\
(Background: Any fire damper that is not fully open represents a faulty state in normal operation).\
\
4\) The input \*xAlarmIn\* is active (= TRUE).\
\
5\) The input \*xSmokeAlarm\* is active (= TRUE).\
\
In all other cases, the collective fault xAlarm is not activated (= FALSE).

#### Enable / disable the fault message for the opening feedback *xAlarmOpen*

Monitoring the damper runtime during the opening process to an adjustable maximum value (**tOpen**) starts if, in normal mode, at least one of the following conditions is met:

1\) A rising edge (FALSE > TRUE) is detected at the output *xHB* detected (= normal case).\
\
2\) The opening request is active (xEn = TRUE) and at the same time at the input **xQuit** a rising edge (FALSE > TRUE) is detected.\
\
3\) The output xHB is active (= TRUE) and at the same time a falling edge (TRUE > FALSE) is detected at the input **xOpen** detected.\
\
The fault message for the opening feedback **xAlarmOpen** is activated (= TRUE) if, after the maximum runtime has elapsed **tOpen** when the output is active (xHB = TRUE) at least one of the following conditions is met:\
\
1\) The feedback for full opening is not active (xOpen = FALSE) (= normal case).\
\
2\) The feedback signals **xOpen** or **xClosed** have the same state.\
\
The fault message for the opening feedback **xAlarmOpen** is deactivated (= FALSE) if at the input **xQuit** a rising edge (FALSE > TRUE) is detected.

#### Enable / inhibit of the fault message for the closing feedback *xAlarmClosed*

Monitoring the damper runtime during the closing process to an adjustable maximum value (**tclose**) starts if, in normal mode, at least one of the following conditions is met:

1\) A falling edge (TRUE > FALSE) is detected at the output *xHB* detected (= normal case).\
\
2\) The closing request is active (xEn = FALSE) and at the same time at the input **xQuit** a rising edge (FALSE > TRUE) is detected.\
\
The fault message for the closing feedback **xAlarmClosed** is activated (= TRUE) if, after the maximum runtime has elapsed **tClose** when the output is inactive (xHB = FALSE) at least one of the following conditions is met:\
\
1\) The feedback for full closing is not active (xClosed = FALSE) (= normal case).\
\
2\) The feedback signals **xOpen** or **xClosed** have the same state.\
\
The fault message for the closing feedback **xAlarmClosed** is deactivated (= FALSE) if at the input **xQuit** a rising edge (FALSE > TRUE) is detected.

#### Duration of the last complete opening *tLastOpen*

The duration measurement begins whenever at least one of the following conditions is met:

1\) A rising edge (FALSE > TRUE) is detected at the input *xOpen* detected.\
\
2\) A falling edge (TRUE > FALSE) is detected at input xOpen.\
\
3\) A rising edge (FALSE > TRUE) is detected at input xClosed.\
\
4\) A falling edge (TRUE > FALSE) is detected at input xClosed. (normal case)\
\
5\) A rising edge (FALSE > TRUE) is detected at output xHB.\
\
6\) A falling edge (TRUE > FALSE) is detected at output xHB.\
\
At this output, after each rising edge at the feedback for full opening **xOpen** (FALSE > TRUE) the runtime is available.

#### Duration of the last complete closing *tLastClosed*

The duration measurement begins whenever at least one of the following conditions is met:

1\) A rising edge (FALSE > TRUE) is detected at the input *xOpen* detected.\
\
2\) A falling edge (TRUE > FALSE) is detected at input xOpen. (normal case)\
\
3\) A rising edge (FALSE > TRUE) is detected at input xClosed.\
\
4\) A falling edge (TRUE > FALSE) is detected at input xClosed.\
\
5\) A rising edge (FALSE > TRUE) is detected at output xHB.\
\
6\) A falling edge (TRUE > FALSE) is detected at output xHB.\
\
At this output, after each rising edge at the feedback for full closing **xClosed** (FALSE > TRUE) the runtime is available.

#### Duration of the current opening / closing in *tRunTime*

At this output, the current runtime is available during each runtime measurement.

#### Testing the functions of the fire damper (test mode)

Test mode is always generally triggered if at least one of the following conditions is met:

1\) A rising edge (FALSE > TRUE) is detected at the input *xTestEx* detected.\
\
2\) The active state (= TRUE) is detected at the setpoint / parameter **xRunTest** detected. The active state is reset immediately after detection (= FALSE).\
\
However, the actual test mode is only performed if the feedback of automatic mode **eAOO** (0 = automatic, >0 = manual operation) contains the value 0 and at the same time the manual override mode for the digital output **xHB** signals automatic mode (eMANBIN = eMANBIN.Auto).\
\
In test mode, the fire damper is closed and then opened, each with runtime monitoring. At the beginning of test mode, the outputs **xAlarmOpen**, **xAlarmClosed**, **tTestOpen**, **tTestClosed** and **xTestOK** are reset (= FALSE).\
\
Now the control command for closing is triggered and the runtime is monitored for exceeding the maximum value **tClosed** is monitored. If the correct feedback situation (xClosed = TRUE and xOpen = FALSE) is reached without exceeding the maximum value, then the output **xAlarmClosed** is not activated (= FALSE). In all other situations, the output **xAlarmClosed** is activated (= TRUE).\
\
Now the control command for opening is triggered and the runtime is monitored for exceeding the maximum value **tOpen** is monitored. If the correct feedback situation (xOpen = TRUE and xClosed = FALSE) is reached without exceeding the maximum value, then the output **xAlarmOpen** is not activated (= FALSE). In all other situations, the output **xAlarmOpen** is activated (= TRUE).\
\
The result display for the fire damper test **xTestOK** is activated (= test successful) if neither of the two outputs **xAlarmOpen** or **xAlarmClosed** is active (= TRUE). The achieved values **tLastOpen** and **tLastClosed** are each assigned to the outputs **tTestOpen** and **tTestClosed** and stored until the next fire damper test.\
\
The test mode ends automatically as soon as the fire damper test is completed.

#### Requirements

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

### CODESYS

InOut:

| Scope       | Name           | Type     | Initial      |
| ----------- | -------------- | -------- | ------------ |
| Input       | `xEn`          | `BOOL`   |              |
| Input       | `xAlarmIn`     | `BOOL`   | FALSE        |
| Input       | `eAOO`         | eManBin  | eManBin.Auto |
| Input       | `xOpen`        | `BOOL`   |              |
| Input       | `xClosed`      | `BOOL`   |              |
| Input       | `xQuit`        | `BOOL`   | FALSE        |
| Input       | `xTestEx`      | `BOOL`   | FALSE        |
| Input       | `xSmokeAlarm`  | `BOOL`   | FALSE        |
| Output      | `sLine1`       | `STRING` |              |
| Output      | `sLine2`       | `STRING` |              |
| Output      | `sText`        | `STRING` |              |
| Output      | `xHB`          | `BOOL`   |              |
| Output      | `xAB`          | `BOOL`   |              |
| Output      | `xAlarm`       | `BOOL`   |              |
| Output      | `xAlarmOpen`   | `BOOL`   |              |
| Output      | `xAlarmClosed` | `BOOL`   |              |
| Output      | `xTestOK`      | `BOOL`   |              |
| Output      | `tLastOpen`    | `TIME`   |              |
| Output      | `tLastClosed`  | `TIME`   |              |
| Output      | `tTestOpen`    | `TIME`   |              |
| Output      | `tTestClosed`  | `TIME`   |              |
| Output      | `tRunTime`     | `TIME`   |              |
| Output      | `xAuto`        | `BOOL`   |              |
| Input Const | `udiOpen`      | `UDINT`  | 150          |
| Input Const | `udiClose`     | `UDINT`  | 25           |
| Input Const | `eManModeB`    | eMANBIN  | eMANBIN.Auto |
| Input Const | `xRunTest`     | `BOOL`   | FALSE        |
| Input Const | `sEditLine2`   | `STRING` | ‘’           |
| Input Const | `sEditLine1`   | `STRING` | ‘Room’       |


---

# 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/firedampermotsmoke.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.
