> For the complete documentation index, see [llms.txt](https://docs.theseus.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theseus.us/cyclops/troubleshooting.md).

# Troubleshooting

* When encountering an issue with Cyclops, first check the Diagnostics panel on the Vozilla home screen for high-level information on the system's health.

<figure><img src="https://2060891120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhzvlBbeiwnrjdGDAaBcQ%2Fuploads%2FUu1HAf3vTVIq0RqUGccw%2Fimage.png?alt=media&amp;token=e96abd6d-1884-4f02-92a1-0396911b30e6" alt=""><figcaption></figcaption></figure>

#### Connecting to the MAV network

To add a MAVLink source in Vozilla, from the home screen click the dropdown next to the **Connect** button. Then click **+ Add source**

<figure><img src="https://2060891120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhzvlBbeiwnrjdGDAaBcQ%2Fuploads%2FuyAReynrhk9l2Elw7o6c%2FScreenshot%202026-08-31%20160931.png?alt=media&amp;token=1860535e-22a9-476d-94e7-dc23d1eba56d" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="https://2060891120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhzvlBbeiwnrjdGDAaBcQ%2Fuploads%2FbApzYSvH70y7kd4TJNkj%2FScreenshot%202026-08-31%20160700.png?alt=media&amp;token=a5621567-a2c3-4ce3-b88f-73d25ab3df97" alt="" width="563"><figcaption></figcaption></figure>

#### Debug MAVLink Router issues

To check MAVLink Router service status:

```bash
pi@pi5:~$ sudo systemctl status mavlink-router.service
● mavlink-router.service - MAVLink Router Service
     Loaded: loaded (/usr/lib/systemd/system/mavlink-router.service; enabled; preset: enabled)
     Active: active (running) since Wed 2026-08-05 18:25:52 UTC; 3min 8s ago
   Main PID: 725 (mavlink-routerd)
      Tasks: 2 (limit: 1910)
     Memory: 4.5M (peak: 29.8M swap: 144.0K swap peak: 156.0K)
        CPU: 9.797s
     CGroup: /system.slice/mavlink-router.service
             └─725 /usr/lib/vns-sdk/bin/mavlink-routerd -c /home/pi/recordings/latest/mavlink-router/main.conf

Aug 05 18:25:58 pi5 mavlink_router_launcher.sh[725]: Opened UART [4]configured_uart_0: /dev/ttyAMA0
Aug 05 18:25:58 pi5 mavlink_router_launcher.sh[725]: UART [4]configured_uart_0: speed = 921600
Aug 05 18:25:58 pi5 mavlink_router_launcher.sh[725]: Opened UDP Server [5]external_clients: 0.0.0.0:14599
Aug 05 18:25:58 pi5 mavlink_router_launcher.sh[725]: Opened UDP Client [6]mav_monitor: 127.0.0.1:14563
Aug 05 18:25:58 pi5 mavlink_router_launcher.sh[725]: Opened UDP Client [8]vps_bridge_legacy: 192.168.218.1:14721
Aug 05 18:25:58 pi5 mavlink_router_launcher.sh[725]: Opened UDP Client [10]api_legacy: 127.0.0.1:14562
Aug 05 18:25:58 pi5 mavlink_router_launcher.sh[725]: Opened UDP Client [12]companion_gps: 127.0.0.1:14561
Aug 05 18:25:58 pi5 mavlink_router_launcher.sh[725]: Opened UDP Client [14]vps_process: 127.0.0.1:14560
Aug 05 18:25:58 pi5 mavlink_router_launcher.sh[725]: Logging target system_id=1 on 00000-2026-08-05_18-25-58.bin
Aug 05 18:25:58 pi5 mavlink_router_launcher.sh[725]: Logging target system_id=1 on 00001-2026-08-05_18-25-58.tlog
```

### Common connection issues

Several factors can cause similar MAVLink connection issues. If this sounds like your issue, please check the following settings are properly configured on your system:

1. SYS/COMP ID are set properly (on both Vozilla/Cyclops and GCS/FC)

<figure><img src="https://2060891120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhzvlBbeiwnrjdGDAaBcQ%2Fuploads%2FbtomKmt7ot0JECnkNhy6%2FScreenshot%202026-08-31%20163548.png?alt=media&amp;token=475bbc0d-0272-40ee-9957-dc0204e0834e" alt="" width="563"><figcaption></figcaption></figure>

2. Device URL and SSH credentials match your Cyclops computer

<figure><img src="https://2060891120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhzvlBbeiwnrjdGDAaBcQ%2Fuploads%2FCbtTVDKRJbbQ64h2Nx4n%2FScreenshot%202026-08-31%20163840.png?alt=media&amp;token=6e5aa492-740b-47dc-a98b-5c3fb1179a96" alt="" width="563"><figcaption></figcaption></figure>

### Remote support

If your issue requires direct support from the Theseus team, you can use our remote support tool build into Vozilla. This gives us remote access to your Cyclops computer to help you troubleshoot. Using this tool requires three things:

1. Your Cyclops computer is connected to Vozilla over Ethernet
2. Your GCS computer has an internet connection
3. Your UAV is powered on

To enable remote support in Vozilla, navigate to *Settings>Diagnostics>Enable Remote Support*

<figure><img src="https://2060891120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhzvlBbeiwnrjdGDAaBcQ%2Fuploads%2F69rtkVocVCTtX5AxesXO%2FScreenshot%202026-09-02%20160450.png?alt=media&amp;token=e93d8f46-9cf9-4272-863f-2e460bd0d6ca" alt=""><figcaption></figcaption></figure>