# Page Not Found

The URL `files/Gv0NiASvVXumHR9bQZQp` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Programming Raspberry Pi Pico W](https://hirurobotics.gitbook.io/xrp/experiential-robotics-platform-xrp/programming-raspberry-pi-pico-w.md)
- [Reading from the Encoder](https://hirurobotics.gitbook.io/xrp/use-xrp-to-practice/reading-from-the-encoder.md)
- [Building the XRP Robo](https://hirurobotics.gitbook.io/xrp/experiential-robotics-platform-xrp/building-the-xrp-robo.md)
- [Programming with XRPCode IDE](https://hirurobotics.gitbook.io/xrp/experiential-robotics-platform-xrp/programming-with-xrpcode-ide.md)
- [Experiential Robotics Platform (XRP) ](https://hirurobotics.gitbook.io/xrp/experiential-robotics-platform-xrp.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://hirurobotics.gitbook.io/xrp/experiential-robotics-platform-xrp/programming-raspberry-pi-pico-w.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.

### Option 2 — Browse the documentation index

Full index: https://hirurobotics.gitbook.io/xrp/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://hirurobotics.gitbook.io/xrp/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/xrp/experiential-robotics-platform-xrp/programming-raspberry-pi-pico-w.md`).

You may also use `Accept: text/markdown` header for content negotiation.