> 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/parameters-table/f-simulate.md).

# F Simulate

### F Simulate **parameter list** <a href="#f-parameter-list" id="f-parameter-list"></a>

<table data-header-hidden><thead><tr><th width="110.33333333333331">Serial number</th><th width="192">Name</th><th>Function</th></tr></thead><tbody><tr><td><strong>Serial number</strong></td><td>Name</td><td>Function</td></tr><tr><td>F01</td><td>Sim. Volume (Simulation Volume)</td><td>Set up simulate value of instantaneous flow speed, the unit will be the one set in parameter group B.</td></tr><tr><td>F02</td><td>Sim. Mode (Simulation Mode)</td><td><p>Simulation function will be activated after selecting “ on ”, default off.</p><p>OCT (besides pulse), RS485 and Analog current output will be operated according to the changes of simulated data and cumulative flow.</p><p>Please be noted that cumulative flow and history data will be affected.</p><p>Simulate mode will be reminded on the screen.</p><p><strong>The corresponding communication function will work normally only after being turned on.</strong></p></td></tr><tr><td>F03</td><td>Sim. PulseHz (Simulation PulseHz)</td><td><p>Under this page, pulse signal will be outputted according to set frequency within value 0 to 700. Please set up NC/NO of pulse according to parameter E01, and pulse width according to parameter E03.</p><p><strong>It operates whether OCT info is turned on or not.</strong></p></td></tr></tbody></table>

**The video about F parameter setup.**

Watch the video or scan the the QR code below. \
(\*Please refer to the parameter list of this version of the manual for the new and modified parameters)

{% embed url="<https://youtu.be/XCxmjdOIegU>" %}
The video about F parameter setup
{% endembed %}

![The video about F parameter setup](https://498068148-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M7fZsO11LItbPHrVN6W%2F-MKd5NvM3QEV2qX0PxZS%2F-MKdHaM-4jdPKwyTsfS-%2F%E5%8F%83%E6%95%B8%20F%20%E5%88%86%E9%A1%9E%E8%A8%AD%E5%AE%9A%E5%BD%B1%E7%89%87_en.jpg?alt=media\&token=46654f60-7561-4ecb-a7ea-9e6ef941e9e9)


---

# 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/parameters-table/f-simulate.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.