> 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-en-v3/1-product-introduction/1.3-product-features.md).
# 1.3 Product features
● High-precision picosecond time difference measurement improves measuring accuracy
● Patented multi-stage trigger technology enhances anti-interference performance
● Automatic signal conditioning circuit adapts to a variety of applications
● Analogy 4-20 milliampere communications technology **(**The 4-20mA output resolution is specified as 12-bit, ensuring precise analog signal representation**)**
● Can be extended to use Modbus, OPC Server, and other industry control protocols
● Simple interface
● In addition, metal/plastic probe bracket can be purchased to significantly improve the ease of installation and reliability of the probe, and to overcome the disadvantages of the straps being dislodged due to temperature and vibration loosening and shifting. At the same time, it improves the accuracy of traffic detection and stabilizes the detection result.
---
# 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-en-v3/1-product-introduction/1.3-product-features.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.