> 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/functionblocks/daikin/daikin_ekmbdxb7v1_idu_error_states.md). # DAIKIN\_EKMBDXB7V1\_IDU\_ERROR\_STATES ## `DAIKIN_EKMBDXB7V1_IDU_ERROR_STATES` (FB) `FUNCTION_BLOCK` DAIKIN\_EKMBDXB7V1\_IDU\_ERROR\_STATES ### Representation
### Short description > Collection of the error states of up to 64 Daikin indoor units > > Typical application: Central control of Daikin indoor units via the Daikin Modbus interface EKMBDXB7V1 #### Guidelines - Software creation The following function codes (FC) are supported: 3, 4, 6 and 16. The following transmission rates are supported: 9600 and 19200 bit/s. For addressing, use the address specifications, not the register addresses (address = register - 1). The Modbus addresses 1 - 15 can be set directly on the DIP switches in the interface. In FC03, a maximum of 32 registers may be requested in one request telegram (deviating from the Modbus standard). In FC04, a maximum of 32 registers may be requested in one request telegram (deviating from the Modbus standard). In FC16, a maximum of 30 registers may be written in one request telegram (deviating from the Modbus standard). The following transmission parameters were tested: 19200 baud, 8-N-1. The interface supports the following exception codes: 0x81, 0x82 and 0x83. The number of control commands per indoor unit is limited to 7000/year!!! Taking the tested transmission parameters into account, the time between the end of the response telegram and the next request telegram must be at least 22.5 ms All registers read with FC04 are always available up to date. All registers read with FC03 are only available once up to date during each restart of the gateway. Procedure for changing a setpoint (FC06 or FC16): \&#xNAN;**\*\*\*\*\*\*\*\*\*\*\*\*\*\*** \&#xNAN;**\* Functions \*** \&#xNAN;**\*\*\*\*\*\*\*\*\*\*\*\*\*\*** In this FB, the error states of all up to 64 indoor units are collected and evaluated (FC04: addresses 3600 - 3727). They are available in the array `arstIndoorUnits_ErrorStates` separately for each indoor unit as a structure element. The structure element of an indoor unit is updated only if the corresponding write/read permission is present (input `arxIndoorUnits_ReadWriteState`). InOut: | Scope | Name | Type | Initial | Comment | | ----------- | ------------------------------- | ----------------------------------------------------------------------------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Input | `xEn` | `BOOL` | TRUE | Enable / disable communication (TRUE = enable) | | Input | `byUnitId` | `BYTE` | 0 | Address of the device (interface) (1 .. 15) | | Input | `xUpdateActual` | `BOOL` | FALSE |

Update of actual values (on every rising edge
)

| | Input | `xResError` | `BOOL` | FALSE |

Reinitialization of the output eErrorCodeCom (with every
rising edge)

| | Input | `arxIndoorUnits_ReadWriteState` |

ARRAY \[1 .. 4, 0 .. 15] OF
BOOL

| |

Array with the read/write permissions of the indoor units of all groups (1-00 … 4-15)
1st dimension: group, 2nd dimension: number of the indoor unit
Array element = FALSE: no read/write permission
Array element = TRUE: read/write permission

| | Inout | `ModbusClient` | `ModbusClientBase` | | Client of the device | | Output | `arstIndoorUnits_ErrorStates` |

ARRAY \[1 .. 4, 0 .. 15] OF
EKMBDXB7V1\_ERROR\_STATES

| |

Array with the error states of the indoor units of all groups (1-00 … 4-15)
1st dimension: group, 2nd dimension: number of the indoor unit
Array element = structure with the individual error states

| | Output | `xAlarm` | `BOOL` | FALSE | Collective fault (TRUE = fault) | | Output | `xAlarmCom` | `BOOL` | FALSE | Collective fault - communication (TRUE = fault) | | Output | `eErrorCodeCom` | ModbusErrorCode | | Error code - communication (0 = no error) | | Output | `xBusy` | `BOOL` | | Communication indicator (TRUE = communication) | | Input Const | `tTimeUpdateActual` | `TIME` | TIME#3s0ms |

Update interval for the processes influenced by the input
xUpdateActual influenced

| --- # 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/functionblocks/daikin/daikin_ekmbdxb7v1_idu_error_states.md?ask=&goal= ``` `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.