> 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-as510-paddle-wheel-flowmeter-manual-chinese-v2/communication/modbus-rtu-protocol/du-xie-xing-ji-yi-ti/read-write-memory-list.md).
# 讀寫型記憶體列表
{% hint style="info" %}
讀取較大數值（如 **Float32**）時，因內部運算方式不同，可能出現極小誤差，通常在 **萬分之一以內**，屬於正常現象。
**讀取指令**單次要求的暫存器數量不可超過 **20 個**，超過則該指令將被**忽略**。詳見下方列表。
{% endhint %}
### 讀寫記憶體列表使用方法
| 欄位名稱 | 功能說明 |
| ----------- | -------------------------------------------- |
| Register 位址 | 讀寫記憶體位址，與唯讀記憶體不共用。 |
| Register 長度 | 該變數的資料長度，單位為 Register（2 Byte）。 |
| 記憶體內容 | 說明該記憶體的名稱或用途。有連結者可點入該參數專屬頁面，查看完整選項值、範圍與設定步驟。 |
| 資料型式 | 標明收發數據的格式。 |
| 讀取指令 | 標明可用的讀取指令。 |
| 寫入指令 | 標明可用的寫入指令。此欄位為 X 表示該暫存器不支援遠端寫入。 |
## 讀寫記憶體列表
### **範例：C02 清除累計（歸零累計流量）**
| 步驟 | 數值 |
| --------------------- | ------------------------ |
| 表格中的 Register 位址（Hex） | 0x0201 |
| 換算為十進位 | 0x0201 = 2×256 + 1 = 513 |
| 換算為主機位址（4xxxx 慣例） | 40001 + 513 = 40514 |
| 訊息中的位址位元組 | 02 01 |
| 完整寫入訊息（站號 01） | 01 06 02 01 00 01 18 72 |
若誤輸入 `40201`，主機會送出十進位 `200`（`0x00C8`），該位址並不存在。流量計將不會回應，或回傳例外碼 02；在 PLC 端會顯示為「寫入無回應」。
### 自我核對小技巧
若不確定主機使用哪一種位址慣例，可先用功能碼 03 讀取對應 Modbus ID 的暫存器。若讀回的數值與本機的站號相符，代表位址基準正確，即可將同一慣例套用到其他位址上。
---
# 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/fp-as510-paddle-wheel-flowmeter-manual-chinese-v2/communication/modbus-rtu-protocol/du-xie-xing-ji-yi-ti/read-write-memory-list.md?ask=&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.