> 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-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 defined to request a value, based on the expected type. Use this enum as an input to 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 for long measurement values, then the request is split into 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.powerio.com/hub/codesys-hvac/en/hvac-modbus-library/datatypes/enumerations/expected_type.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.