> 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-tx310-ultrasonic-flowmeter-manual-chinese-v3/untitled-6/untitled-2.md).

# 4.5 Other（其他設定）

| ​Title                            | ​Title                           |
| --------------------------------- | -------------------------------- |
| <p>聲音設定</p><p>Buzzer Setup</p>    | 開啟或關閉裝置聲音，包含按鍵聲響及警報音             |
| <p>液晶螢幕背光</p><p>LCD Backlight</p> | 持續開啟，持續關閉，或15秒未操作時關閉             |
| <p>液晶螢幕對比</p><p>LCD Contrast</p>  | 調整黑色文字與背景1-10的對比值，數字越大對比越高，預設值為4 |
| <p>版本資訊</p><p>Version Info.</p>   | 顯示裝置韌體，硬體的版本                     |


---

# 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-tx310-ultrasonic-flowmeter-manual-chinese-v3/untitled-6/untitled-2.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.