> For the complete documentation index, see [llms.txt](https://docs.phoenixlidar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/toolbars/rover/connect-to-rover.md).

# Connect to Rover

<figure><img src="/files/5JtXrnqklKFpaFpuinu7" alt=""><figcaption></figcaption></figure>

To control and configure the lidar system, you must first connect to it. Click the **Connect** icon.

### Connect using Wi-Fi or Ethernet

<figure><img src="/files/15U7UwsW8nL6bgbBusAS" alt=""><figcaption><p>Example: Using NavBox IP Address to connect Wired via ethernet</p></figcaption></figure>

Typically, the lidar system is connected over **Ethernet** or **Wi-Fi**. The lidar system has several IP addresses. The table below shows the different NavBox IP Addresses used with different connection types. Example Laptop IP Addresses are also shown. When connecting via ethernet or M12, you must manually set your laptop's IP address.

{% hint style="warning" %}
When connecting via a wired connection, you must configure your computer's network interface with an address on the same subnet as the lidar system. Refer to this [documentation regarding network adapter configuration](/hardware-and-interfaces/connecting-and-interfacing-with-phoenix-lidar-systems/iface_se/base-station-notebook-setup/wired-ethernet-network-card-setup.md) in Microsoft Windows. More information about connecting to rover can be found [here](/hardware-and-interfaces/connecting-and-interfacing-with-phoenix-lidar-systems.md).&#x20;
{% endhint %}

| Connection type    | NavBox IP Address | Applicable systems                       | Laptop IP Address |
| ------------------ | ----------------- | ---------------------------------------- | ----------------- |
| Wired via ethernet | 192.168.200.10    | All systems                              | 192.168.200.20    |
| Wi-Fi              | 192.168.20.10     | All systems                              | Auto via DHCP     |
| Wired via M12      | 192.168.101.1     | Systems designed for helicopter use only | 192.168.101.10    |

{% hint style="info" %}
When connecting via Wi-Fi, it is not necessary to manually set your computer's IP address.
{% endhint %}

{% hint style="info" %}
You can add shortcuts for the NavBox IP Address by following [Modify Hosts File](/hardware-and-interfaces/connecting-and-interfacing-with-phoenix-lidar-systems/iface_se/base-station-notebook-setup/modify-hosts-file.md) documentation.
{% endhint %}

### Connect to rover via Phoenix LiDAR System connection service

If you lidar system has a 4G/5G Cellular dongle connected, or is able to connect to the internet via some other means, you can reach the lidar system by entering the license key in this field.&#x20;

<figure><img src="/files/ih3yfBdE6IK3Ik4HAh0p" alt=""><figcaption><p>Example: Connecting to rover via 4G/5G or router.</p></figcaption></figure>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/toolbars/rover/connect-to-rover.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
