> For the complete documentation index, see [llms.txt](https://docs.lorric.com/qr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lorric.com/qr/fu-lt-english-v1/communication/modbus-rtu-protocol/single-bit-data-read-write-commands-01-05-common-for-hmi.md).

# Single Bit Data Read/Write Commands (01 / 05) – Common for HMI

### Function Code 01 Example – Single Bit Read

{% hint style="info" %}
This command **does not reset** the C02.Del.Total (Totalizer Clear) option. It is used for **reading a single bit via HMI** (01/05). When the 01 command is sent correctly, the slave responds by returning the requested bit status only.
{% endhint %}

### Master Sends 01 (TX) Example

```
TX: 01 01 00 0A 00 01 A4 0E
```

* **Slave Address:** 01 (Flow meter address)
* **Function Code:** 01 (Read 1 bit)
* **Starting Address:** 02 01 (C02.Del.Total memory address)
* **Quantity:** 00 01 (Read 1 bit)
* **CRC:** A4 0E (Error check)

### Slave Response 01 (RX) Example

```
RX: 01 01 01 00 51 88
```

* **Slave Address:** 01
* **Function Code:** 01 (Read)
* **Data:** 01 00 (Bit value, slave is online and responding)
* **CRC:** 51 88

## Function Code 05 Example – Single Bit Write (Trigger Totalizer Clear)

{% hint style="info" %}
This command **activates** the C02.Del.Total clear option, immediately resetting the totalizer to zero.
{% endhint %}

### Master Sends (TX) Example

```
TX: 01 05 02 01 FF 00 DC 42
```

* **Slave Address:** 01
* **Function Code:** 05 (Write single register)
* **Starting Address:** 02 01 (C02.Del.Total memory address)
* **Data:** FF 00 (Trigger clear)
* **CRC:** DC 42

### Slave Response (RX) Example

```
RX: 01 05 02 01 FF 00 DC 42
```

* **Slave Address:** 01
* **Function Code:** 05
* **Starting Address:** 02 01
* **Data:** FF 00 (Echoes successful write)
* **CRC:** DC 42


---

# 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://docs.lorric.com/qr/fu-lt-english-v1/communication/modbus-rtu-protocol/single-bit-data-read-write-commands-01-05-common-for-hmi.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.