# Configuring the rover manually

You may want to configure the U-blox chip if you're using a dedicated telemetry link to connect your base and rover module, instead of encapsulating it in the MAVLink protocol.

You can use the U-center software in order to configure precisely the behavior of the M8P chip so that it will achieve exactly what you want.

In order to configure the rover, you'll need:

* 1 Computer, used as ground control station
* 1 Micro USB cable
* **Latest** version of U-Center Software (available [here](https://www.u-blox.com/en/product/u-center-windows))

## Configuring the U-blox chip

First of all, **install the U-Center software** on your computer. When done, you can connect your rover module to your computer. Open the U-Center software after that, and connect it to your rover module using the button in the upper-left corner (receiver toolbar).

![](/files/-Lk4ofQRT8oq9gpnph97)

After connecting, you should be able to enter the **Configuration view** from the top hotbar.

![](/files/-Lk4ohRGg16bsD9B-Jp8)

> *After any modification made in the Configuration panel, always remember to hit the Send button at the bottom of the configuration view panel, or your modifications won't be stored!*

In the Configuration panel, scroll down to the *PRT (Port)* section. Here, you need to enter **your autopilot's GPS port's baudrate** to allow it to communicate correctly. It's necessary, as the link between your GPS and the telemetry is purely serial, and there's no other protocol to stipulate a baudrate.

![](/files/-Lk4opWeyCzt1x0FH5l8)

It's also necessary to modify the frequency of the chip. To do this, on the left panel, look for the ***RATE** (Rates)* menu and modify the *Measurement period* to 200 ms.

{% hint style="warning" %}
*Don't forget to click Send!*
{% endhint %}

![](/files/-Lk4ouAffz7m4ylDTUWi)

Next, get into the ***MSG** (Messages)* menu and disable all NMEA messages.

![](/files/-Lk4ovWP3f04V96G2YM6)

After disabling the **NMEA** messages, you should also enable the following messages for the UART1 link:

* NAV-POS-LLH
* NAV-STATUS
* NAV-SOL
* NAV-VELNED

To do so, find each messages in the drop-down list and check the ***UART1*** box for each of these messages, without omitting to click ***Send*** for each message.

Modifying the dynamic filter can also help. You can change it in the ***NAV5** (Navigation 5)* menu, using the first droplist at the top of the menu.

![](/files/-Lk4ppSzfEZiQI4UIFHq)

After doing this tweak, save the whole configuration you've done, by getting into the ***CFG** (Configuration)* menu on the left panel, selecting all four memories on the right, and clicking ***Send***.

![](/files/-Lk4rKQevTU9M8whmqqd)

{% hint style="success" %}
Now that the configuration is stored into the chip, you can disconnect your RTK module from the computer and plug it to your autopilot!
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://drotek.gitbook.io/rtk-f9p-positioning-solutions/the-rtk-rover/configuring-the-rover-manually.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.