> 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/generic/simplewritecoils_fc15.md). # SimpleWriteCoils\_FC15 ## `SimpleWriteCoils_FC15` (FB) `FUNCTION_BLOCK` SimpleWriteCoils\_FC15 ### Representation
### **Transmission of the states of one or more coils (FC15) (1 - 64 coils) to an address range (range: wCoilAddr … (wCoilAddr + wNumberOfCoils - 1))** ### CODESYS InOut: | Scope | Name | Type | Initial | Comment | | ----------- | ---------------------------- | --------------------------------------- | ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Input | `xEn` | `BOOL` | TRUE | Enable / disable communication (TRUE = enable) | | Input | `byUnitId` | `BYTE` | 0 | Device address | | Input | `InputValue` | `__SYSTEM.AnyType` | | Input variable for determining the states of the coils (FC15) (`BOOL`, `BYTE`, `ARRAY` `OF` `BOOL`, `ARRAY` `OF` `BYTE`) | | Input | `xUpdateSetp` | `BOOL` | FALSE | Update of setpoints (on every rising edge) | | Input | `xResError` | `BOOL` | FALSE |

Reinitialization of the outputs eErrorCodeCom or
eErrorCodeDev to the error-free state (on every
rising edge)

| | Inout | `ModbusClient` | `ModbusClientBase` | | Client of the device | | Output | `wCoilAddrFb` | `WORD` | 0 |

Feedback - start address of the coil(s) for the Modbus-
telegram (0 - 65535)

| | Output | `wNumberOfCoilsFb` | `WORD` | 0 |

Feedback - number of coils to be written (range: 1
- 64, wNumberOfCoils <= InputValue.diSize)

| | Output | `wArrayStartIndexFb` | `WORD` | 0 |

Feedback - relative array element with the first coil to be
written (0 - (InputValue.diSize-1)) (only for the
data type ARRAY OF BOOL and ARRAY OF BYTE)

| | Output | `eInputValueDataType` | SIMPLE\_WRITE\_COILS\_FC15\_DATA\_TYPE | SIMPLE\_WRITE\_COILS\_FC15\_DATA\_TYPE.INVALID\_TYPE |

Internal classification of the data type of the variable with the
states of the coils (0 = invalid, 1 = BOOL, 2 = BYTE, 3 =
ARRAY)

| | Output | `xInputValueValid` | `BOOL` | FALSE |

Validity of the variable at the input InputValue (FALSE =
invalid, TRUE = valid)

| | Output | `xErrorFreeDataTransmission` | `BOOL` | FALSE |

Status of the data transmission (FALSE = faulty, LH-
transition = error-free)

| | Output | `xAlarm` | `BOOL` | FALSE | Collective fault (TRUE = fault) | | Output | `xAlarmCom` | `BOOL` | FALSE | Collective fault - communication (TRUE = fault) | | Output | `eErrorCodeCom` | ModbusErrorCode | ModbusErrorCode.NO\_ERROR | Error code - communication (0 = no error) | | Output | `eErrorCodeDev` | SIMPLE\_WRITE\_COILS\_FC15\_ERROR\_CODE | SIMPLE\_WRITE\_COILS\_FC15\_ERROR\_CODE.NO\_ERROR | Error code - device (0 = no error) | | Output | `xBusy` | `BOOL` | FALSE | Communication indicator (TRUE = communication) | | Input Const | `wArrayStartIndex` | `WORD` | 0 |

Relative array element with the first coil to be written
(0 - (InputValue.diSize-1)) (only for the data type ARRAY OF
BOOL and ARRAY OF BYTE)

| | Input Const | `wNumberOfCoils` | `WORD` | 1 |

Number of coils to be written (range: 1 - 64,
wNumberOfCoils <= InputValue.diSize)

| | Input Const | `wCoilAddr` | `WORD` | 1 |

Start address of the coil(s) for the Modbus telegram (0 -
65535)

| | Input Const | `tTimeUpdateSetp` | `TIME` | TIME#0ms |

Update interval for the processes influenced by the input
xUpdateSetp 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/generic/simplewritecoils_fc15.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.