> For the complete documentation index, see [llms.txt](https://docs.optitrack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optitrack.com/v1.1/hardware-setup/hardware-setup-overview.md). # Hardware Setup Overview Multiple cameras and components are involved in a motion capture system setup, and correct setup will have a significant impact on the quality of data that your system produces. These hardware setup workflow pages provide detailed instructions on how to properly set up the mocap volume for capturing motion. An optimized capture volume will not only ensure good system performance and accuracy but will also prevent marker occlusions and mislabeling of markers. Thus, a well-configured setup can save a significant amount of time and effort in data post-processing. For preparing captures in Motive, read through the Capture Setup pages. *** *** Hardware Setup Workflow Pages 1. Prepare Setup Area 2. Camera Placements 3. Camera Mount Structures 4. Cabling and Wiring 5. Aiming and Focusing --- # 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.optitrack.com/v1.1/hardware-setup/hardware-setup-overview.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.