> 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/fp-as310-english-v5/communication/modbus-rtu-protocol/read-only-memory-rom/read-only-memory-rom-list.md).

# Read-Only Memory (ROM) – List

## Read-Only Memory (ROM) – List

### Memory Location and Definition

| **Read-write memory type** | **Function**                                                      |
| -------------------------- | ----------------------------------------------------------------- |
| Register Address           | Read-write memory locations are not shared with read-only memory. |
| Register length            | The length of variable memory. The unit is Register(2Byte).       |
| Memory content             | Describe the memory content function.                             |
| Bytes                      | Indicates the total number of Bytes occupied by the variable.     |
| Data type                  | The format of sending and receiving data type.                    |
| Remarks                    | Notes and details                                                 |

## **Read-Only Memory List**

<table><thead><tr><th>Register Address</th><th>Register length</th><th>Memory content</th><th>Bytes</th><th width="102.125">Data type</th><th>Remarks</th></tr></thead><tbody><tr><td>0000</td><td>2</td><td>Flowrate</td><td>4</td><td>float</td><td></td></tr><tr><td>0004</td><td>2</td><td>Total</td><td>4</td><td>float</td><td></td></tr><tr><td>0006</td><td>2</td><td>Flowrate*100</td><td>4</td><td>int 32</td><td>×100</td></tr><tr><td>000A</td><td>2</td><td>Total*100</td><td>4</td><td>int 32</td><td>×100</td></tr><tr><td>000E</td><td>1</td><td>error code a</td><td>2</td><td>int</td><td>See Alarm A definition</td></tr><tr><td>000F</td><td>1</td><td>error code b</td><td>2</td><td>int</td><td>See Alarm B definition</td></tr><tr><td>0010</td><td>1</td><td>error code c</td><td>2</td><td>int</td><td>See Alarm C definition</td></tr><tr><td>0011</td><td>1</td><td>error code d</td><td>2</td><td>int</td><td>See Alarm D definition</td></tr><tr><td>0012</td><td>1</td><td>System Status</td><td>2</td><td>int</td><td>See System Status definition</td></tr><tr><td>0013</td><td>4</td><td>Total(64)</td><td>8</td><td>int 64</td><td>×100,000 rounded to integer</td></tr><tr><td>0017</td><td>2</td><td>Dosing(float)</td><td>4</td><td>float</td><td></td></tr><tr><td>0019</td><td>2</td><td>Dosing100(32)</td><td>4</td><td>int 32</td><td>×100 rounded</td></tr><tr><td>001B</td><td>4</td><td>Dosing(64)</td><td>8</td><td>int 64</td><td>×100,000 rounded</td></tr><tr><td>0053</td><td>1</td><td>M</td><td>2</td><td>int</td><td></td></tr><tr><td>0054</td><td>1</td><td>m</td><td>2</td><td>int</td><td></td></tr><tr><td>0055</td><td>2</td><td>flow*100_2</td><td>4</td><td>int 32</td><td></td></tr><tr><td>0057</td><td>2</td><td>na</td><td>4</td><td>-</td><td></td></tr><tr><td>0059</td><td>2</td><td>total*100_2</td><td>4</td><td>int32</td><td></td></tr></tbody></table>


---

# 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://docs.lorric.com/qr/fp-as310-english-v5/communication/modbus-rtu-protocol/read-only-memory-rom/read-only-memory-rom-list.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.