> 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/tracking-bar-coordinate-system.md). # Tracking Bar Coordinate System The OptiTrack Duo/Trio tracking bars are factory calibrated and there is no need to calibrate the cameras to use the system. By default, the tracking volume is set at the center origin of the cameras and the axis are oriented as shown in the following image (Z forward, Y up, X left):

If you wish to change the location and orientation of the global axis, you can use the Coordinate Systems Tool which can be found under the Tools tab. ## Coordinate Systems Tool *** When using the Duo/Trio tracking bars, you can set the coordinate origin at desired location and orientation using a calibration square. Make sure the calibration square is oriented properly. Adjusting the Coordinate System Steps: 1. First set place the calibration square at the desired origin. 2. \[Motive] Open the Coordinate System Tools pane under the Tools tab. 3. \[Motive] Select the Calibration square markers from the Perspective View pane 4. \[Motive] Click Set Set Ground Plane button from the Coordinate Systen Tools pane, and the global origin will be adjusted.

--- # 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/tracking-bar-coordinate-system.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.