> 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/fpas310-zhong-wen-v5/parameters/e-tong-xun-xiang-guan-she-ding.md).

# E 通訊相關設定

### &#x20;                                                                                                                                                                                                                            E 通訊 參數列表

| **序號** | **英文名稱**    | **中文名稱**    | **功能**                                                                                                                                              |
| ------ | ----------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| E04    | Modbus ID   | Modbus ID   | 設定 Modbus ID，預設 1。<mark style="color:purple;">(適用在FP-AS310R)</mark>                                                                                 |
| E05    | Baud        | 鮑率          | <p>設定 Modbus 通訊 baud 速度，</p><p>可選 關閉、9600、19200、38400、</p><p>預設關閉。</p><p><mark style="color:purple;">(適用在FP-AS310R)</mark></p>                      |
| E15    | Byte format | Byte format | 此功能用於設定 Modbus RTU 通訊協定中，數據傳輸的格式化規則，預設 N.8.1 (無校驗、8 數據位、1 停止位)。<mark style="color:purple;">(適用在FP-AS310R)</mark>                                    |
| E16    | Bit order   | Bit order   | 設定 Modbus RTU 傳輸時，一個位元組 (Byte) 內的 8 個位元 (bits) 按照什麼順序發送，可選最低有效位元優先或最高有效位元優先，預設 LSB first 最低有效位元優先。<mark style="color:purple;">(適用在FP-AS310R)</mark> |
| E17    | Endianness  | Endianness  | 設定位元組順序，可選大端序(最高有效位元組)、小端序(最低有效位元組)、暫存器交換或位元組和暫存器皆交換，預設Big Endian大端序。<mark style="color:purple;">(適用在FP-AS310R)</mark>                              |


---

# 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/fpas310-zhong-wen-v5/parameters/e-tong-xun-xiang-guan-she-ding.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.
