> 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-v2/2-installation-method/2.4-installation-check/2.4.1-rssi-signal-strength.md).

# 2.4.1 RSSI (Signal Strength)

There are two sets of RSSI values on the meter screen; these represent the signal strength received by the upstream and downstream probes. It is recommended that signal strength should be maintained at above 10% to ensure the normal operation of the system. If RSSI is found to be excessive or unstable, please refer to the following adjustment methods: 

● Try to fine-tune the distance between the probes. 

● Select a different site for mounting the probe. 

● To confirm if there is any sediment in the pipe. 

● Check whether the outer wall of the pipe is too thick with rust, oil, paint, or other substances. Afterwards, evenly apply more coupling agent. 

● The signals from the two probes may not align. Try moving the probes slowly until the unit has a better RSSI value; check the probe for misalignment. 

● After taking any of the above actions, be sure to double check whether the probe distance deviates too much; an excessive offset will result in flow measurement error. 

● Check the setting in the MeterRx Peak Level settings. If the diameter of the pipe is large, the wire is too long, or other factors cause the RSSI to always be biased, try to adjust the relevant setting values. For related setting information, refer to the following instructions.


---

# 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-v2/2-installation-method/2.4-installation-check/2.4.1-rssi-signal-strength.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.