# Z-Axis Installation Notes ### **In This Guide** we explain the **anchor installation structure and placement strategy** for improving **Z-axis (height) positioning accuracy** using the **GrowSpace Q1 Kit** in indoor environments. In spaces where Z-axis accuracy is critical, a simple flat (XY-plane) anchor layout is not sufficient.\ To achieve precise 3D positioning, a **spatial (multi-level) installation structure** is required. *** ### 3D Position Output with the GrowSpace Q1 Kit With the **GrowSpace Q1 Kit**, you can use a **developer tag** or **listener device** to monitor real-time **3D position data**, including X, Y, and Z coordinates. #### Example: Serial communication output ``` X: 12.34, Y: 56.78, Z: 9.01 ``` For listener devices, this data is provided in the form of **POS messages**, which include X, Y, and Z values. ![](/files/0XGgUF8xM4hBvJvX8hEN)\ This allows you to track not only flat XY positions, but also the **height (floor or level)** of a person or asset in real time. *** ### Installation Structure Affecting Z-Axis Accuracy The **GrowSpace Q1** system calculates tag positions using **TWR (Time of Flight)**-based distance measurements.\ However, if **all anchors are installed at the same height** (e.g., on the ceiling), the system may encounter the following issues when calculating **Z-axis (height)** values: #### Problem Scenario * Even if the tag is located 1 meter above or below the ceiling plane, the measured distance to each anchor remains nearly the same. * Because there is little to no difference in distance, the system cannot accurately determine the tag’s **Z-axis (height)** position.

→ As a result, the **Z-coordinate may be fixed at zero** or its accuracy may be significantly reduced. *** ### Anchor Installation for Improved Z-Axis Accuracy To detect changes along the Z-axis, **anchors must be installed at different heights**. #### Recommended Placement Strategy * Place **2 anchors on the ceiling** and **2 on the floor**, arranged in a crisscross pattern * Alternatively, install anchors at **varied heights** on pillars, walls, or other vertical surfaces

This layout creates measurable **distance differences** between the tag and each anchor based on height, which helps the system **reduce Z-axis positioning errors** *** ### Installation Tips for Large Spaces (40m × 20m or Larger) In wide areas, using only the four corners for anchor placement may result in reduced accuracy. #### Recommended Placement Strategy

Item	Details
Basic Setup	Install 4 anchors at the four corners of the space
Additional Anchors	Add 2–3 anchors at the center or along the middle of walls
Height Variation	Distribute anchors at different levels such as ceiling, pillars, and floor
Distance Spacing	Keep the distance between anchors at 15–20 meters or less

Install anchors at **varied heights and distributed positions**, as described above.\ This approach ensures a **balanced distribution of distance differences** between the tag and each anchor, improving not only **Z-axis accuracy**, but overall **3D positioning performance**. *** ### Conclusion The **GrowSpace Q1 Kit** supports 3D positioning by default, but to achieve **accurate Z-axis measurements**, a **spatial anchor layout** is essential.
* Installing all anchors at the same height can lead to significant errors in Z-axis positioning * Placing anchors at **different vertical levels** helps minimize Z-coordinate errors * In large spaces, it's also important to **add supplementary anchors** and **maintain balanced spacing** If your use case requires **precise 3D tracking**, make sure to go beyond flat layouts and apply a **multi-level anchor installation strategy**. --- # Agent Instructions: 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: ``` GET https://freegrow-1.gitbook.io/product-docs-en/en-creator-kit-q1/learn-more/z-axis-installation-notes.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.