> 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-v2/1.-chan-pin-jie-shao-1/1.4-chan-pin-ying-yong.md).

# 1.4 產品應用

● 污水管（低顆粒密度）、海水管&#x20;

● 水源供給設備、排水系統&#x20;

● 發電廠（核能發電、地熱發電、水力發電）&#x20;

● 冰水、熱能、沸水、以及能源管理系統&#x20;

● 石油及化合物運輸監測、食物、飲料、藥品工業製程應用 &#x20;

● 能源節約及水資源節約、造紙（紙漿）業、漏水偵測


---

# 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-v2/1.-chan-pin-jie-shao-1/1.4-chan-pin-ying-yong.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.
