# System Health

The Micro VPS exposes system health indicators for three key system services and hardware components. An overview of the system health is present on the main dashboard.

<figure><img src="/files/CPbAhpj0wu9KkOsKByaH" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Recording service is not required for operation of the VPS.
{% endhint %}

## Health Indicator Overview

Services break down as follows:

* MAVProxy service, connects with autopilot over MAVLink.
* VPS service, core VPS software.
* Recording service, records sensor and system data.

Only the MAVProxy and VPS services are required for operation of the VPS.

Both hardware components are required for normal operation of the VPS:

* NVMe storage, disk storage to save maps and logs on the device.
* Sensor connectivity, connection to the sensor module.

<figure><img src="/files/nCkuonb1fVUor0zxaskm" alt=""><figcaption></figcaption></figure>

## Home Position Outside Map Bound

If the current home position is outside of the bounds of the currently selected map, you might see an error like this at the top of the page.

<figure><img src="/files/3j0sFN9Cc52Qc1SpBckb" alt=""><figcaption></figcaption></figure>

When the VPS service is unhealthy, the error logs will be printed out in the system diagnostics. To fix the bad initial fix error, visit [Home Position Setting](/gcs-software/legacy-software/theseus-gcs-app/feature-list/home-position-setting.md).

## Troubleshooting

Use the "System Health" tab to diagnose issues with your Micro VPS.

| Issue                         | Troubleshooting Steps                                                                                                                                                                                                                                                                                                                          |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Unhealthy NVMe storage        | Issue with firmware setup or hardware failure. Contact your Theseus point of contact immediately.                                                                                                                                                                                                                                              |
| Unhealthy sensor connectivity | <p>Is the sensor powered on?<br>Is the Ethernet cable connected to the compute module?</p>                                                                                                                                                                                                                                                     |
| Unhealthy MAVProxy service    | <p>Is the serial cable connected between the compute module and flight controller? See <a data-mention href="/pages/lmO1ZMulAZRFUNEaq9zm">/pages/lmO1ZMulAZRFUNEaq9zm</a>.<br>Is the serial port configured for MAVLink in the ArduPilot settings? See <a data-mention href="/pages/kITZHqxqBpnINYbZ3c2O">/pages/kITZHqxqBpnINYbZ3c2O</a>.</p> |
| Unhealthy VPS service         | <p>Is your MAVProxy service healthy?</p><p>Is the launch location set? See <a data-mention href="/pages/1bjRAvJkpANoflWxpK16">/pages/1bjRAvJkpANoflWxpK16</a>.<br>Are maps uploaded on your device? See <a data-mention href="/pages/8iZRqGvYbyz7HeG76sqb">/pages/8iZRqGvYbyz7HeG76sqb</a>.</p>                                                |
| Unhealthy recording service   | Not an issue unless you are trying to record sensor data for log sharing. See [Recording Management](/gcs-software/legacy-software/theseus-gcs-app/feature-list/recording-management.md).                                                                                                                                                      |


---

# 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://docs.theseus.us/gcs-software/legacy-software/theseus-gcs-app/feature-list/system-health.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.