# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [How to level DexArm manually?](https://manual.rotrics.com/faq-troubleshooting/faqs/how-to-level-dexarm-manually.md)
- [Why my 3D printing module is clogged?](https://manual.rotrics.com/faq-troubleshooting/faqs/why-my-3d-printing-module-is-clogged.md)
- [The Arm doesn't move, only filament comes out](https://manual.rotrics.com/faq-troubleshooting/troubleshooting/the-arm-doesnt-move-only-filament-comes-out.md)
- [DexArm movement accuracy problem](https://manual.rotrics.com/faq-troubleshooting/troubleshooting/dexarm-movement-accuracy-problem.md)
- [3D printing module won't heat up](https://manual.rotrics.com/faq-troubleshooting/troubleshooting/3d-printing-module-wont-heat-up..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://manual.rotrics.com/faq-troubleshooting/faqs/how-to-level-dexarm-manually.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://manual.rotrics.com/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://manual.rotrics.com/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., `/faq-troubleshooting/faqs/how-to-level-dexarm-manually.md`).

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