> 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/hvac-modbus-library/datatypes/enumerations/expected_type.md).

# EXPECTED\_TYPE

## `EXPECTED_TYPE` (`ENUM`)

`TYPE` EXPECTED\_TYPE: TYPE\_BOOLEAN, `TYPE`\_BYTE, // 1 Word 0 - 255 2Byte TYPE\_SBYTE, // 1 Word -128 - 127 2Byte `TYPE`\_UINT16, // 1 Word 0 - 65535 TYPE\_INT16, // 1 Word -32768 - 32767 `TYPE`\_INT32, // 2 Word -2147483648 - 2147483647 TYPE\_UINT32, // 2 Word 0 - 4294967295 TYPE\_FLOAT32, // 2 Word 1.0E-44 - 3.402823E+38 `TYPE`\_UINT64, // 4 Word 0 - 2E+64 TYPE\_INT64, // 4 Word -2E+63 - 2E+63 TYPE\_DOUBLE, // 4 Word 5.0E-324 - 1.7E+308 `TYPE`\_STRING // x Word

)

This enum is definied to request a value, based on the expected type. Use this enum as a input of the function blocks “SimpleReadValue” to get the value in the expected format. e.g. If the register modbus value is expected as a UINT64 value, for example of long measurement values, then the request is splitted in 4 words

InOut:

| Name          | Comment                         |
| ------------- | ------------------------------- |
| TYPE\_BOOLEAN |                                 |
| TYPE\_BYTE    | 1 Word 0 - 255 2Byte            |
| TYPE\_SBYTE   | 1 Word -128 - 127 2Byte         |
| TYPE\_UINT16  | 1 Word 0 - 65535                |
| TYPE\_INT16   | 1 Word -32768 - 32767           |
| TYPE\_INT32   | 2 Word -2147483648 - 2147483647 |
| TYPE\_UINT32  | 2 Word 0 - 4294967295           |
| TYPE\_FLOAT32 | 2 Word 1.0E-44 - 3.402823E+38   |
| TYPE\_UINT64  | 4 Word 0 - 2E+64                |
| TYPE\_INT64   | 4 Word -2E+63 - 2E+63           |
| TYPE\_DOUBLE  | 4 Word 5.0E-324 - 1.7E+308      |
| TYPE\_STRING  | x Word                          |


---

# 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/hvac-modbus-library/datatypes/enumerations/expected_type.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.