> 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-guidelines/wiring.md). # Wiring Good wiring doesn’t just look nice—it prevents damage, reduces electrical noise, and keeps your robot easy to service. Poor wire management is one of the top causes of robot failure in competition. #### Wiring Principles * **Secure:** No loose wires or plugs that can fall out or get snagged * **Labeled:** Each connection should be traceable and ideally labeled * **Bundled:** Use split loom, braided sleeving, or velcro to bundle similar wires * **Accessible:** Make sure every plug is reachable without full disassembly #### Best Practices * Run wires along the structure—not across open air * Use strain relief at all connectors (e.g., zip tie the wire to a nearby part) * Avoid sharp bends that can pinch or fatigue cables * Keep signal and power wires separate when possible #### Examples of Good Routing * A power distribution board mounted to a plate, pre-wired, and connected to the REV Hub with a short harness * Motor cables run through channels in extrusion or along inside faces of gussets * Sensors mounted on brackets with their wires zip-tied along an adjacent beam --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.ftcwiki.org/design-style/design-guidelines/wiring.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.