> 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-r-english-v5/parameters/e-commute.md).

# E Commute

<table data-header-hidden><thead><tr><th width="160.20001220703125"></th><th width="209.79998779296875"></th><th width="399.5999755859375"></th></tr></thead><tbody><tr><td><strong>No.</strong></td><td><strong>Name</strong></td><td><strong>Description</strong></td></tr><tr><td>E04</td><td>Modbus ID</td><td><p>Set up Modbus ID location, default 1. </p><p><mark style="color:purple;">(Only applicable to Model FP-AS310R)</mark></p></td></tr><tr><td>E05</td><td>Baud</td><td>Sets the Modbus communication baud rate for the flow meter. The Master and Slave must use the same baud rate for communication. Default: Off.<br><mark style="color:purple;">(Only applicable to Model FP-AS310R)</mark></td></tr><tr><td>E15</td><td>Byte format</td><td><p>Sets the data format for Modbus RTU communication. Default: N,8,1 (No parity, 8 data bits, 1 stop bit).</p><p><mark style="color:purple;">(Only applicable to Model FP-AS310R)</mark></p></td></tr><tr><td>E16</td><td>Bit order</td><td><p>Sets the bit order for each byte during Modbus RTU transmission. </p><p><mark style="color:purple;">(Only applicable to Model FP-AS310R)</mark></p></td></tr><tr><td>E17</td><td>Endianness</td><td><p>Sets the <strong>byte order</strong> for multi-byte data during RX (flow meter response) transmission. </p><p><mark style="color:purple;">(Only applicable to Model FP-AS310R)</mark></p></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 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-as310-r-english-v5/parameters/e-commute.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.