> For the complete documentation index, see [llms.txt](https://docs.holybro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holybro.com/gps-and-rtk-system/f9p-h-rtk-series/standard-f9p-uart/f9p-rover-lite.md).

# F9P Rover Lite

### H-RTK F9P Rover Lite&#x20;

{% hint style="info" %}
There are two version available.&#x20;

***Standard*****&#x20;version** comes with 10 Pin connector for Pixhawk **GPS1** port. (Connector not compatible with CubePilot)\
\
***2nd GPS*****&#x20;version** comes with 8 pin connector for Pixhawk **GPS2** Port or **GPS2** Port on the CubePilot
{% endhint %}

This model is low profile, lower cost, and has high performance, It can meet the needs of general DIY users. Due to the lower cost, this model can also greatly minimize the cost of large swarm drone projects such as swarm light shows.

&#x20;It has an integrated safety switch and a tri-colored LED indicator, and it is compatible with the open source *Pixhawk* series flight controller.

![H-RTK F9P Rover lite (SKU12017)
H-RTK F9P Rover lite 2nd GPS (SKU12025) ](https://2367252986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLIgtGDAvVGkCKGOJb1bR%2Fuploads%2FYboMGnY4dxwTrs8eoub9%2F%2312017-5.jpg?alt=media\&token=ae214a1b-8c20-4018-b6cb-841079546a42)


---

# 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.holybro.com/gps-and-rtk-system/f9p-h-rtk-series/standard-f9p-uart/f9p-rover-lite.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.
