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

# EditDate

## `EditDate` (FB)

FUNCTION\_BLOCK EditDate

### Short description

> Input of a date in DATE format (d#2017-11-21)\
> Typical application: defining a date for a switching operation

### Representation

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

### Interfaces

#### Outputs

| Name   | Data type | Value range | Initial value | Function                    |
| ------ | --------- | ----------- | ------------- | --------------------------- |
| *dOut* | DATE      |             |               | Output value in DATE format |

#### Setpoints / Parameters

| Name          | Data type | Value range | Initial value | Function                   |
| ------------- | --------- | ----------- | ------------- | -------------------------- |
| **dSetPoint** | DATE      |             |               | Input value in DATE format |

### Functional description

#### General

This function block is used to transfer an input value in DATE format **dSetPoint** and direct transfer to the output value in DATE format *dOut*.

{% hint style="warning" %}
**Behavior in the event of power failure**

The input value in Date format **dSetPoint** is stored in a power-fail-safe manner and automatically restored.
{% endhint %}

### Visualization

Suitable visualization element from the HVACV Visu Library: **EditDate1** and **EditDate2**

#### Representation

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

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

#### Interfaces visualization element

| Name             | Data type | Type         | Initial value | Function                                                                  |
| ---------------- | --------- | ------------ | ------------- | ------------------------------------------------------------------------- |
| **datDate**      | DATE      | VAR\_IN\_OUT |               | Enter the DATE variable here, e.g. from the block HVAC.EditDate.dSetPoint |
| **DisableInput** | BOOL      | VAR\_INPUT   | FALSE         | The input can be disabled here. The element will then be greyed out.      |

{% hint style="info" %}
Note: VAR\_IN\_OUT interfaces must be assigned; VAR\_INPUT is optional.
{% endhint %}

### CODESYS

InOut:

| Scope       | Name        | Type   |
| ----------- | ----------- | ------ |
| Input Const | `dSetPoint` | `DATE` |
| Output      | `dOut`      | `DATE` |


---

# 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/setpoint/editdate.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.
