> 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/turntable-template/fabrication.md).

# Fabrication

## Required Tools <a href="#vewyr39nhzfd" id="vewyr39nhzfd"></a>

* CNC router
* 9/16” wrench/socket
* 5/16” hex key
* Speed square or framing square
* Level
* Self-leveling laser, beam, or rotary
* 8-10 clamps, with at least 4-1/2" throat opening
* Screw gun with #2+3 Phillips bits
* Shims, as needed.

## CNC Cutting <a href="#uugg9woas1xg" id="uugg9woas1xg"></a>

The first step to fabricating your turntable is getting the plywood parts cut. Along with this guide is a package of drawings (DWGs and PDFs) detailing all the parts you will need to make the turntable.

If your plywood stock has a better face-grain on one side that side should be routed facing up, so that the counterbores or countersinks end up on that side. This should work out thus for the turntable parts when assembled from top to bottom:

* 2nd layer of lid: A-side up
* 1st layer of lid: A-side down
* Drive Ring: A-side down
* Spider: A-side down

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-93965b032e8144da129b2447952b70adea0555ef%2F0?alt=media)

## Building the Sub-Assemblies <a href="#bvz07f8io33r" id="bvz07f8io33r"></a>

Refer to the 20' Turntable Template Assembly Drawings as needed.

Now with your CNC cut plywood parts, install the t-nuts into the counterbored holes. The counterbores should allow the t-nuts’ flanges to sit flush or slightly recessed to the bottom of the plywood. The t-nuts will likely backout or be pushed out during assembly without a screw or 2 in each. If you do not add screws, do not worry if the t-nuts aren’t flush with the plywood - they will tighten up when assembled.

* Spider - Hub gets 3/8"-16 and 1/2"-13 t-nuts.
* Spider - Long Leg, Short Leg, Inner Rib, and Outer Rib get 3/8"-16 t-nuts.
* Lid 1st Layer gets 1/4"-20 t-nuts.
* 8x Drive Rings get 1/4"-20 t-nuts. Do not install t-nuts in the other Drive Rings.

Attach the casters to the Spider - Long Legs (4 casters per, 12 assemblies), Short Legs (2 casters per, 12 assemblies), and Outer Ribs (1 caster per, 24 assemblies) with the hardware stack as shown (9/16” wrench/socket). There is a 1/4" plywood Caster Shim that goes between the caster’s mounting plate and the Leg each caster is attached to. Use a speed square or framing square as you tighten the bolts to ensure that the wheels are perpendicular to each Leg.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-549e6b97aacb5ec0e389f763de77843baafddbe3%2F1?alt=media)

Attach the **Pivot** (top) to the Spider - Hub (bottom), Big Pivot Shim (bottom center), and Small Pivot Shim (top center) with the hardware stack as shown (3/4" wrench/socket).

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-6175ca71b8c6b9ee97ca522dc633dab46db1b5bc%2F2?alt=media)

Now your pre-assembled pieces are complete, so you are ready to begin assembling the turntable.

### &#x20;<a href="#vx24dnwchq1y" id="vx24dnwchq1y"></a>


---

# 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/turntable-template/fabrication.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.
