# Wifi / network config



<figure><img src="https://3611896438-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mf7j4nUAIpHY72_rYOl-1703796690%2Fuploads%2F1qv4yyRm5TMxlz6pUHDo%2Fimage.png?alt=media&#x26;token=4ba5eb3c-10a8-46d9-971a-bb03c91ce3b0" alt=""><figcaption></figcaption></figure>

### 1. Mode

In _Mode_, you choose how the Autopilot’s WiFi operates.\
By default, the Autopilot is set to function as a WiFi Access Point _**Master (AP)**_.

When you select _**Master (AP)**_, the option _**Managed (Client mode)**_ becomes available.\
In Managed mode, the Autopilot connects to an existing WiFi network, such as a router, BoatController, OpenPlotter, or a similar system.

{% hint style="info" %}
We recommend using Managed mode only if you are confident that the external network is reliable.\
If WiFi access to the Autopilot becomes unavailable, you can restore the WiFi Access Point via the _ControlHead_.
{% endhint %}

### 2. SSID

In **Master (AP)** mode, this is the name of the WiFi network broadcast by the autopilot as an access point — by default, `pcnautic_AP`.

<figure><img src="https://3611896438-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mf7j4nUAIpHY72_rYOl-1703796690%2Fuploads%2FrOeCNEVOKQKZgRSyt7zw%2Fimage.png?alt=media&#x26;token=4bc2ab7c-df57-41b0-b4a2-f3e478d6c87c" alt=""><figcaption></figcaption></figure>

In **Managed (Client) mode**, enter the SSID of the existing WiFi network that the autopilot should connect to.

### **3. Key**

In **Master (AP) mode**, we strongly recommend setting a password to prevent unauthorized access to your system.\
The password must be at least **8 characters** long.

In **Managed (Client) mode**, enter the **password** of the existing WiFi network the autopilot should connect to.

***

### **4. Client Mode Address**

* In **Master (AP) mode**, leave this field empty.
* In **Managed (Client) mode**, enter the **static IP address** you want the autopilot to use within the network.\
  An IP address consists of four numbers separated by dots, for example: `192.168.14.1`.

**Note:**

* The first three numbers must match the network you’re connecting to.
* The last number must be a free address within that range (between 1 and 254) not already used by another device.
* If your network supports DHCP, you may leave this field empty, and the autopilot will automatically obtain an IP address.

***

### **5. IP addr:**

Displays the current IP address of the _ControlHead_.

***

### **6. Submit**

After making any changes, always click **Submit** to save and apply the settings.

***

### **Ethernet**

If you are using a Realtek RTL8153 USB LAN adapter, an Ethernet section will appear on this page.

Here, you can set the mode of the LAN adapter:

* **DHCP Client (default):** The adapter automatically receives an IP address from a DHCP server in the network.
* **DHCP Server:** The adapter assigns IP addresses to devices connected via Ethernet.

You will also see the current IP address assigned to the LAN adapter, depending on the selected mode.

#### **Internet Sharing via WiFi and Ethernet**

* If the autopilot is connected to the internet via WiFi, this connection can be shared with wired network devices by setting the Ethernet mode to DHCP Server.
* Conversely, a wired internet connection via the LAN adapter can be shared with WiFi clients, provided the WiFi mode is set to _Master (AP)_.

## **Configure Serial Devices**

Although these are USB devices, they are handled internally as serial devices.

In this section, you can set the type of connected serial devices, such as our remote control receiver.\
Only serial devices that are not automatically recognized will be listed here and can be configured manually.

For each device, you can choose from the following modes:

* **None** – Device is not used.
* **Remote** – Select this if it is a Pcnautic Remote Receiver.
* **NMEA OUT** – Sends NMEA data from the Autopilot to the external device.

## **NMEA data clients**

To exchange NMEA data between various devices or software, the NMEA device typically connects to the Autopilot’s NMEA data server. This is the standard method, as described under [TCP NMEA Data Connection](../../../wifi-verbindingen#tcp-nmea-data-connection).

However, some NMEA devices do not support this method. In such cases, the Autopilot must initiate the connection in order to receive NMEA data. The Autopilot then functions as an **NMEA data client**.\
An example of this is the Quark-elec QK-A032 converter.

Enter the IP address and port of the relevant NMEA device, then click 'Submit'.\
The Autopilot will then attempt to establish a connection to receive NMEA data.

<figure><img src="https://3611896438-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mf7j4nUAIpHY72_rYOl-1703796690%2Fuploads%2FIfw9lHk6ONR78KZ39czh%2Fimage.png?alt=media&#x26;token=cb1fd3f6-e25b-4860-a2ed-14a1ef902339" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Leave these fields empty if the other device _does_ send data to the Autopilot on its own.
{% endhint %}

## Host for Remote Controlhead

Configure this Controlhead to operate as a remote by entering the IP address of the host (Master) Controlhead. In most cases, you should connect the remote Controlhead as a [Managed (client)](#id-4.-client-mode-address) to the host (Master) Controlhead and use IP address `192.168.14.1`.

Once enabled, it will connect over the network to the host and display its real-time data, such as heading, GPS, and status. Ensure that the host is on the same network.

<figure><img src="https://3611896438-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mf7j4nUAIpHY72_rYOl-1703796690%2Fuploads%2FQEHX827gJ1gQODX9vnP3%2Fremote_controlhead.png?alt=media&#x26;token=aabdcb3e-6bf2-40eb-abf4-95dd35ddea8f" alt=""><figcaption></figcaption></figure>

## IP leases

At the bottom of the page, you’ll find an overview of the so-called **IP leases** of connected (WiFi) clients.\
For each device, the following information is displayed:

* **IP address**
* **MAC address**
* **Hostname**
* **Lease expiration time**

<figure><img src="https://3611896438-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mf7j4nUAIpHY72_rYOl-1703796690%2Fuploads%2FniP3vRPtErp1U8grg3WU%2FIp-address.jpg?alt=media&#x26;token=871a22f7-f381-4020-b6e5-143a3978cdba" alt=""><figcaption></figcaption></figure>

## Connecting to Both the Autopilot and the Internet

When your smartphone connects to the Autopilot via WiFi (in **Master (AP)** mode), it will typically lose its mobile data connection (4G/5G), even though the mobile network is available. This is standard behavior: smartphones prioritize WiFi over mobile data, even if the WiFi network has no internet access.

If you want to be connected to the Autopilot and the internet at the same time, you can switch the Autopilot to **Managed (Client)** mode and let it connect to your phone’s personal **hotspot** instead.

### **Setting up the Autopilot**

1. **Mode**: Select **Managed (Client)**.
2. **SSID**: Enter the **name** of your phone’s WiFi hotspot.
3. **Key**: Enter the **password** of your phone’s hotspot.
4. **Client Mode Address**:
   * Leave this field empty if your phone supports DHCP (this is usually the case).
   * Or enter a static IP address within the phone’s network range (e.g., `192.168.43.100` for Android or `172.20.10.5` for iPhone).

### **Setting up the Phone’s Hotspot**

**On Android**:

* Go to **Settings > Network & internet > Hotspot & tethering**.
* Enable **Wi-Fi hotspot**.
* Take note of the network name (SSID) and password.

**On iPhone**:

* Go to **Settings > Personal Hotspot**.
* Enable **“Allow Others to Join”**.
* Take note of the network name and password.

{% hint style="info" %}
Note: Menu structure and terminology may vary slightly depending on your device model and Android/iOS version.
{% endhint %}

Make sure the Autopilot is within range of your phone’s hotspot signal.

### Result:

* The Autopilot connects to your phone's WiFi hotspot.
* Your phone stays connected to the internet via 4G/5G.
* You can access the Autopilot's web interface from your phone using its local IP address, while maintaining internet access on your phone.
