> 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/6-other-conditions.md).

# 6. Other Conditions

A. The measured value jumps sharply Under some conditions, when the fluid flow rate is fast the measured value may jump sharply. This may be caused by a poor startup of the ultrasonic signal waveform as shown in the following figure:

![](https://2386771058-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LvhKtBvsv-DVMTySk5A%2F-Lvhwos_1k1YKHiNY1lj%2F-LviHoj34gl54g0hYFOB%2F%E5%85%B6%E4%BB%96%E7%8B%80%E6%B3%81.png?alt=media\&token=2e3810af-0bfa-42da-8930-e56665cda484)

The figure on the left shows poor signal waveform startup. The wave heights near the trigger level are all similar, a phenomenon which can easily lead to a trigger time point error, which in turn leads to a jump in the value due to the resulting time difference calculation error. The correct signal waveform should be as shown on the right, with sufficient drop height between waves. Possible causes of a poor initial waveform are shown below:

1\. Z-type configuration : Probe axis is off-center. Adjust the probe position.

![](https://2386771058-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LvhKtBvsv-DVMTySk5A%2F-Lvhwos_1k1YKHiNY1lj%2F-LviHsCUAJ_EvlCtwdnr%2F%E5%85%B6%E4%BB%96%E7%8B%80%E6%B3%81_1.png?alt=media\&token=20d765a9-21f7-495a-a4fb-b2e8989faf75)

2\. V type configuration : Probe distance error. Adjust the probe distance according to the signal strength.

![](https://2386771058-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LvhKtBvsv-DVMTySk5A%2F-Lvhwos_1k1YKHiNY1lj%2F-LviHyLkYkuStuwjDHsI%2F%E5%85%B6%E4%BB%96%E7%8B%80%E6%B3%81_2.png?alt=media\&token=cb9a6361-3035-4b35-b84d-f089ba0f3dbe)

3\. V-type configuration: Probe axis and pipeline are not parallel. Adjust the position.

![](https://2386771058-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LvhKtBvsv-DVMTySk5A%2F-Lvhwos_1k1YKHiNY1lj%2F-LviI1rXtGNGCrYhB6r6%2F%E5%85%B6%E4%BB%96%E7%8B%80%E6%B3%81_3.png?alt=media\&token=a7602875-4a7b-488d-b231-875543751461)

It is also possible that in the initial settings, the pipe’s outer diameter setting is larger than the actual diameter. If this is the case, re-measure and adjust the setting, then fine-tune the configuration according to the displayed probe distance. If there is still a jump after this operation is completed, then the Meter → 16.Anti-noise​ function in the setting options can be switched on to control the problem.


---

# 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/6-other-conditions.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.