> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidsystems/robot/robot-in-3d.md).

# The robot in 3D

**Robot › 3D** shows the robot's CAD with a CAN ID label on every tagged device and a line along each CAN bus in wire order. Layers turn each bus on and off; mechanisms can be solid, faded or hidden. Tap a device for its card.

## Get the CAD in

The CAD comes from Fusion through the RAIDSystems add-in (`tools/fusion-addin` in the RAIDSystems repo; its README says how to install it). It's never edited in the app.

1. In Fusion, use **Tag device** to link each motor and sensor to its device.
2. Use **Export** to write one `.glb` file.
3. On **Robot › 3D**, click **Upload the CAD (.glb)**.

The app keeps the last 3 exports. The file is tens of megabytes, so it loads only on this page.

## What it finds

* Untagged electrical parts, and tags with no matching device, show up on [Open items](https://docs.raidrobotics.org/raidsystems/robot/open-items.md).
* Devices with no tagged part are listed under the viewer.
* The Wiring page's **Top view** uses the same export.


---

# 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.raidrobotics.org/raidsystems/robot/robot-in-3d.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.
