> 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-as510-paddle-wheel-flowmeter-manual-en-v2/install-and-set-up.md).

# Installation and Set-up

* Verify that the manual version matches the hardware and firmware. To check the manual version, refer to the [version page](/qr/fp-as510-paddle-wheel-flowmeter-manual-en-v2/this-instruction-manual-version-is-v2.0.md).
* Ensure the installation environment meets standard measurement requirements. Provide sufficient straight pipe lengths upstream and downstream of the flowmeter to stabilize the flow profile.
* The optimal installation location is on the side of a horizontal pipe, or on a vertical pipe from downstream to upstream.
* Confirm the operating temperature, chemical resistance, pipe material and dimensions before installation.
* Please avoid measuring fluids with magnetic particles or placing the flowmeter near equipments generating strong magnetic field, like motors and electromagnetic valves, which may cause LORRIC’s paddle wheel flowmeter to work improperly, as the paddlewheel uses magnetic flow sensor technology. 


---

# 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-as510-paddle-wheel-flowmeter-manual-en-v2/install-and-set-up.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.