> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/machinery/floorpocket-v2/assembly/roller-chain.md).
# Roller Chain
### Step 1: Remove Lower Chain Gaurds
### Step 2: Attach both chains to the top of the carriage
Attached the masterlink to the mount on top of the carriage
### Step 3: Run First Chain
Run the first chain over the top of the idler sprocket on **Column Extension**.
### Step 4: Connect First Chain to Bottom Carriage
### Step 5: Run Second Chain
Run the second chain over the white bushing between idler sprockets. Once chain is run, lift it onto the sprocket.
### Step 6: Connect Second Chain to Bottom Carriage
Connect the chains to the bottom of the carriage.
### Step 7: Re-Attach Chain Gaurds
Torque Spec: 112 ft/lbs
---
# 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.creativeconners.com/docs/machinery/floorpocket-v2/assembly/roller-chain.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.
