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

# StartDelay

## `StartDelay` (FB)

FUNCTION\_BLOCK StartDelay

### Short description

> Generation of signals after each CPU restart.\
> Use: Delayed enabling of actions after the CPU restart.

### Representation

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

### Interfaces

#### Outputs

| Name   | Data type | Value range | Initial value | Function       |
| ------ | --------- | ----------- | ------------- | -------------- |
| *xQ1*  | BOOL      |             |               | Output 1       |
| *xQ1p* | BOOL      |             |               | Pulse output 1 |
| *xQ2*  | BOOL      |             |               | Output 2       |
| *xQ2p* | BOOL      |             |               | Pulse output 2 |

#### Setpoints / Parameters

| Name           | Data type | Value range | Initial value | Function                        |
| -------------- | --------- | ----------- | ------------- | ------------------------------- |
| **TimeQ2Puls** | TIME      |             | T#1s          | Pulse duration - pulse output 2 |
| **TimeQ2**     | TIME      |             | T#20s         | Time delay - output 2           |
| **TimeQ1Puls** | TIME      |             | T#1s          | Pulse duration - pulse output 1 |
| **TimeQ1**     | TIME      |             | T#5s          | Time delay - output 1           |
| **xTest**      | BOOL      |             | FALSE         | Simulation of CPU restart       |

### Functional description

#### General

This function block is used to generate signals after each CPU restart.\
The CPU restart can be triggered by the simulation input **xTest** (= TRUE) independently of an actual CPU restart.\
\
The output *xQ1* switches after each CPU restart with a time delay **TimeQ1** from state FALSE permanently to state TRUE.\
At pulse output 1 *xQ1p* a one-time pulse with the pulse duration **TimeQ1Puls** is generated.\
\
The output *xQ2* switches after each CPU restart with a time delay **TimeQ2** from state FALSE permanently to state TRUE.\
At pulse output 2 *xQ2p* a one-time pulse with the pulse duration **TimeQ2Puls** is generated.

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

### CODESYS

InOut:

| Scope       | Name         | Type   | Initial     |
| ----------- | ------------ | ------ | ----------- |
| Input Const | `TimeQ2Puls` | `TIME` | TIME#1s0ms  |
| Input Const | `TimeQ2`     | `TIME` | TIME#20s0ms |
| Input Const | `TimeQ1Puls` | `TIME` | TIME#1s0ms  |
| Input Const | `TimeQ1`     | `TIME` | TIME#5s0ms  |
| Input Const | `xTest`      | `BOOL` | FALSE       |
| Output      | `xQ1`        | `BOOL` |             |
| Output      | `xQ1p`       | `BOOL` |             |
| Output      | `xQ2`        | `BOOL` |             |
| Output      | `xQ2p`       | `BOOL` |             |


---

# 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/time/startdelay.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.
