# Page Not Found

The URL `motor-control/setting-up-recoil-usb-can-adapter/setting-up-recoil-usb-can-adapter-ubuntu` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Setting up Recoil USB-CAN Adapter](https://tk233.gitbook.io/notes/motor-control/setting-up-recoil-usb-can-adapter.md)
- [Setting up ROS 2 Jazzy on Ubuntu](https://tk233.gitbook.io/notes/ml-rl/ros-2/setting-up-ros-2-jazzy-on-ubuntu.md)
- [0x00. Theory of Operation](https://tk233.gitbook.io/notes/motor-control/recoil-foc-motor-controller/0x00.-theory-of-operation.md)
- [0x01. Components](https://tk233.gitbook.io/notes/motor-control/recoil-foc-motor-controller/0x01.-components.md)
- [0x03. Application](https://tk233.gitbook.io/notes/motor-control/recoil-foc-motor-controller/0x03.-application.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 following URL with the `ask` and `goal` query parameters:

```
GET https://tk233.gitbook.io/notes/motor-control/setting-up-recoil-usb-can-adapter.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.

### Option 2 — Browse the documentation index

Full index: https://tk233.gitbook.io/notes/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://tk233.gitbook.io/notes/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., `/notes/motor-control/setting-up-recoil-usb-can-adapter.md`).

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