> 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-elevator-cascade/assembly-instructions/bearing-blocks.md).
# Bearing Blocks
The Elevator Inline Clamping Bearing Block ([WCP-0897](https://wcproducts.com/collections/systems-structure/products/elevator-components)) can be assembled with bearings before assembly of the Elevator.
## Assembly Instructions
The following shows the General Assembly Instructions for the Inline Clamping Bearing Block.
{% hint style="info" %}
Half of all blocks blocks should be assembled without the 1/4" ID radial bearings as these would need to be removed and reinstalled in certain steps of assembly.
{% endhint %}
{% hint style="success" %}
Vibra-TITE VC-3 Threadmate ([Vibra-TITE](https://wcproducts.com/products/threadlocker)) is recommended on all bolts that thread into a tapped hole.
{% endhint %}
## Step 1
Slide all the appropriate bearings onto the Dowel Pin.
## Step 2
Slide the assembly from Step 1 into the Clamping Block. The bearing should fit in the slots on the block. The dowel pin will be constrained by the Shoulder Bolts installed in Step 3.
## Step 3
Bolt the bearing and spacer stack-up to the block as shown in the images below.
---
# 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-elevator-cascade/assembly-instructions/bearing-blocks.md?ask=&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.
