> For the complete documentation index, see [llms.txt](https://docs.wcproducts.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcproducts.com/welcome/greyt/greyt-telescope/misc/faq-and-trouble-shooting.md).

# FAQ & Trouble Shooting

<mark style="color:blue;">**Q: None of the bolts in any of my Top Blocks rub, but my Telescope still doesn't extend smoothly. What do I do?**</mark>

A: This may be because the square tube used for the sliding stages of your Telescope are slightly oversized. A way to fix this issue is to loosen the bolts holding the Top Block together until your Telescope extends smoothly.

<mark style="color:blue;">**Q: The bearings in the bottom block of my Telescope keep exploding. What can I do to keep this from happening?**</mark>

A: This may be happening because the bearings in the bottom block of your Telescope are too small for your current application. If you are using 1/2" OD bearings in your bottom block, then that means you will have to swap them out with 5/8" OD bearings and replace the tube they are sliding in with 1/16" wall tube.


---

# 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.wcproducts.com/welcome/greyt/greyt-telescope/misc/faq-and-trouble-shooting.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.