> For the complete documentation index, see [llms.txt](https://www.ftcwiki.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.ftcwiki.org/design-style/design-methodologies/plate-and-standoff-construction.md). # Plate and standoff construction A favorite among FTC teams, plate and standoff construction uses 2D-cut flat plates spaced apart using standoffs or stacked plastic spacers. It’s intuitive, easy to service, and perfect for custom drivetrains or slide guides. #### How It Works * Two parallel plates form the "walls" of a structure. * Standoffs, spacers, or bearings are used to connect and align them. * Motors, shafts, and other hardware are mounted between the plates. #### Pros * **Serviceable:** Remove screws to open the assembly like a sandwich. * **Strong and Rigid:** Parallel plates resist torsion well. * **Easy to Design:** Plates can be laid out in 2D and stacked. #### Cons * **Space-Hungry:** Can get bulky in tight robots. * **Heavy:** Metal plates and many screws/standoffs add mass. * **Limited Adjustability:** Mounting patterns are fixed after cutting. #### FTC Tips * Use ⅛” aluminum or ⅛”/¼” polycarbonate plates. * Design mounting holes on a 16mm grid to align with common FTC components. * Add inspection holes to see bearings and shafts inside. * Offset holes to match standoff centers—always model screw heads to check clearance. --- # 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://www.ftcwiki.org/design-style/design-methodologies/plate-and-standoff-construction.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.