> For the complete documentation index, see [llms.txt](https://docs.wingbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wingbits.com/byod/grandfathered-byod-diy-info/debug-your-station.md).

# Debug your station

Please note that this debug functionality is now included with [wb-config](/byod/grandfathered-byod-diy-info/install-wb-config-tool.md), but can be run independently with either of the below commands.

{% hint style="warning" %}
If your status is offline, make sure all the hardware is connected, including the antenna/cable being attached to the usb receiver, and the device is powered on.
{% endhint %}

Start by running this command that will check for the most common issues:

```sh
curl -sL https://gitlab.com/wingbits/config/-/raw/master/debug.sh | sudo bash
```

If that fails with an error like "command not found" (different Linux distributions may include different tools by default), try this instead:

```sh
wget -q -O- https://gitlab.com/wingbits/config/-/raw/master/debug.sh | sudo bash
```

For more checks, like power, USB and GPS problems, see [BYOD troubleshooting](/byod/grandfathered-byod-diy-info/byod-troubleshooting.md).

If you still need help with debugging, please join our Discord and open a support ticket.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.wingbits.com/byod/grandfathered-byod-diy-info/debug-your-station.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.