> 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.3-flight-time.md).

# 2.4.3 Flight time

The seventh interface of the display output interface displays all values related to ultrasonic signal flight time (Time of Flight, or ToF). TOM (as shown in the picture) represents measured flight time, and TOS the calculated theoretical flight time. Ideally, the two values should be equal. If TOM/TOS yields a value that exceeds 100% ± 3%, the following steps should be taken: 

● Check if the relevant setting parameters are correct. Check pipe material, pipe diameter, whether there is a liner, fluid type, and other relevant parameters. Check to ensure that the probe is mounted correctly. 

● Check to ensure that the probe mounting distance is correct. 

If> 100%, adjust upstream and downstream probes and bring them closer together. 

If <100% adjust distance of probe, by moving them further apart.


---

# 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.3-flight-time.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.