> 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/shop-accessories/omio-cart-and-enclosure/assembly-instructions/omio-cnc-router-stand-mobile-cart/steps-5-8.md).

# Steps 5-8

{% 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 5

Install all tubes as shown in the locations shown below. Use four #10-32 x 3/8”L bolts to secure each end of tube in place. Rivnuts need to be facing up on each tube.

<figure><img src="https://821067574-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHbDvtJAuKgFVfi1IcxC0%2Fuploads%2FzGvCjaZhfbi7i5yXcLDF%2FOMIO%20Cart%20-%20Step%205.svg?alt=media&amp;token=f1ceec2a-0fb1-4ec3-979b-0fab3cadb57a" alt="" width="563"><figcaption></figcaption></figure>

## Step 6

Install all tubes as shown in the locations shown below. Use four #10-32 x 3/8”L bolts to secure each end of tube in place. Rivnuts need to be facing up on each tube.

<figure><img src="https://821067574-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHbDvtJAuKgFVfi1IcxC0%2Fuploads%2F3gTrn2tFtlSNGnuDwpEn%2FOMIO%20Cart%20-%20Step%206.svg?alt=media&amp;token=f8d48c29-1cde-47d7-8dd9-026bf795ac01" alt="" width="563"><figcaption></figcaption></figure>

## Step 7

Place the Short Shelf and Long Shelf on top of the aluminum structure from the previous step. Secure the shelves in place using #10-32 x 1/2"L bolts as shown below.

<figure><img src="https://821067574-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHbDvtJAuKgFVfi1IcxC0%2Fuploads%2FipSlpPdUTmIcrjkARzKv%2FOMIO%20Cart%20-%20Step%207.svg?alt=media&amp;token=1b2fd575-4687-4796-bcd5-f6a7db18f92c" alt="" width="563"><figcaption></figcaption></figure>

## Step 8

Install all tubes as shown in the locations shown below. Use four #10-32 x 3/8”L bolts to secure each end of tube in place. Install as many sets of dividers as desired.&#x20;

{% hint style="info" %}
Some angle iron may be installed on the wood base directly under each 1” x 1” piece of tubing to help prevent sheets from sliding around, if the cart will be moved often. This is an optional addition and parts are not included.
{% endhint %}

<figure><img src="https://821067574-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHbDvtJAuKgFVfi1IcxC0%2Fuploads%2FKwicf3K5HMt3qXQKR9C3%2FOMIO%20Cart%20-%20Step%208.svg?alt=media&amp;token=da13cf78-1ad3-4cd8-b1ca-1d6caae61be1" alt="" width="563"><figcaption></figcaption></figure>


---

# 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/shop-accessories/omio-cart-and-enclosure/assembly-instructions/omio-cnc-router-stand-mobile-cart/steps-5-8.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.