UWB Creator Kit Q1
You can find answers to your GrowSpace questions on this page. This guide is made from real user feedback. It explains common problems that happen during testing and setup. You will learn how to install anchors, start the app, measure distance, and see location using RTLS (Real-Time Location System).
This page has all the FAQs you need. You can learn how to set up your test environment and make your measurements more accurate. You don't need to read any other documents.
📦 Kit Contents and Setup Steps
What is included in the GrowSpace Kit?
Creator Kit – For basic RTLS testing
3 Anchors
1 Listener
1 Developer Tag → This kit is good for users who are new to RTLS (Real-Time Location System) or want to test it in a simple indoor space.
Creator Expansion Kit – For advanced RTLS testing
4 Anchors
1 Gateway
1 Developer Tag → This kit is for users who want to test more complex setups. You can try service integration, server connection, and testing in detailed space layouts.
How is the GrowSpace system structured?
Creator Kit Q1 (Fixed type)
System flow: [Tag] → [Anchor Q1] → [Listener or Gateway] → [Server] → [Monitoring Software]
Tag (Q1-WT, Q1-AT, etc.): Attached to a person or object. It sends real-time location signals.
Anchor (Q1-AN): A fixed device that measures distance to the tag.
Listener (Q1-LS) or Gateway (Q1-GW): Sends distance data from the anchors to the server.
Server and Software: Calculates location from the data and shows it on a screen.
Local PC-based monitoring program
Web-based cloud service
The Q1 system is designed to build an RTLS (Real-Time Location System) inside buildings. It is good for tracking and analyzing the location of people or assets.
What is the main difference between the Creator Kit and the Mobile Kit?
Use case
Fixed indoor setup
Works with mobile devices
Connection
PC Viewer (Serial)
SDK (BLE/UART)
Main purpose
RTLS testing and location tracking
Build location-based services, connect robots
Components
Anchor + Tag + Listener
Anchor + SDK
What is the difference between a Listener and a Gateway?
Connection
USB direct connection
Wi-Fi / LAN
Usage
For testing
For real-time data operation
Target device
PC, MCU
Cloud, Server
Where can I check what's included in the GrowSpace kit?
You can see the list of items and detailed descriptions on the official GrowSpace website.
🧭 Anchor Installation and Placement
What is the difference between a Reference Anchor (Initiator) and a Regular Anchor?
Role
The anchor that sends the start signal (trigger) for the network
Receives the signal from the initiator and measures distance
Setup Required
You must set exactly one Reference Anchor per PAN ID
All other anchors are set as Regular Anchors
Function
Synchronizes all devices (UWB tags, anchors) in the same PAN ID
Participates in distance measurement using received signals
Limit
Only one per PAN ID (as the Initiator)
Up to 30 per PAN ID, including the Reference Anchor
Why is a reference anchor needed?
The GrowSpace UWB system uses a PAN ID (UWB network ID) to manage communication between devices.
Each network (PAN ID) must have one reference anchor, also called the Initiator.
This anchor is required to start UWB sessions with all devices in sync.
The reference anchor does not define a physical location.
It simply provides a time reference to begin communication.
You can set the reference anchor easily using the Space-Lite or Space-Cloud software, or with the setup tool. Only one reference anchor is needed per network (PAN ID).
Does the Reference Anchor (Initiator) need to be at coordinate (0, 0)?
-The Reference Anchor does not need to be placed at (0, 0). However, setting it at (0, 0) is generally recommended for the reasons below.
✅ Why the Reference Anchor is often placed at (0, 0)
In many RTLS (Real-Time Location System) setups, the reference anchor is used as the origin of the coordinate system.
Placing it at (0, 0) makes it easier to define the full coordinate space.
It also helps you understand the positions of other anchors and tags more clearly.
For example, in a simple rectangular space with 3 anchors:
Reference Anchor → (0, 0)
Second Anchor → (X, 0)
Third Anchor → (0, Y)
This makes it easier to analyze and visualize the system.
✅ When (0, 0) is not required
The Reference Anchor only sends the start signal (trigger) for communication.
It works regardless of its actual position.
So, if you cannot place the reference anchor at (0, 0) due to space or layout limits, you can place it elsewhere and assign (0, 0) to another anchor or a virtual point.
As long as all anchors follow the same coordinate system, the positioning will work correctly.
What is the recommended distance between anchors?
We recommend placing anchors within 20 meters of each other. If the distance is too long, positioning accuracy may decrease. Please adjust the spacing based on your test environment.
✅ Anchor Installation Tips
Anchor spacing
Within 15–20 meters
Coverage layout
Square or rectangular placement recommended
Minimum anchors
3 or more (based on trilateration)
Reference anchor(Initiator)
1 anchor (used as the coordinate origin)
It is best to install anchors in open areas where they can clearly see each other. Mounting them on the ceiling or high walls improves signal stability and coverage.
Can I install anchors near metal walls or glass?
It is best to avoid installing anchors near materials like metal or glass. UWB signals can reflect or bend on these surfaces, which may cause multipath interference. This can reduce the accuracy of location tracking.
Recommended installation tips:
Avoid placing anchors near metal poles or elevators
Use normal walls (like drywall or concrete) instead of glass walls
After installation, test the actual measured distance to check signal performance
※ If you must install an anchor near metal or glass, check the error in actual position and apply correction if needed. You can also add another anchor to improve accuracy.
What is the minimum number of anchors needed?
The number of anchors depends on your purpose.
If you only need distance measurement, you can use just 1 anchor. (It calculates the distance from the tag to the anchor.)
For 2D location tracking (RTLS), you need at least 3 anchors. (This uses trilateration to calculate X and Y coordinates.)
For 3D tracking (including height), we recommend 4 or more anchors. Using more anchors can improve both accuracy and stability.
📐 Coordinate Measurement and Input
How do I measure anchor coordinates?
You need to enter anchor coordinates manually by measuring real distances in the space. The accuracy of these coordinates directly affects the overall RTLS performance.
The most common method is to set the reference anchor at (0, 0, Z), then measure the relative distances (X, Y, Z) to other anchors using a tape measure or laser distance meter.
Make sure to measure from the center of each anchor.
The reference anchor does not have to be at (0, 0). You can choose a different starting point if needed.
To improve accuracy, we recommend measuring at least twice.
👉 For detailed steps and examples, see the installation guide: Anchor Installation and Coordinate Measurement Manual
Is the coordinate unit mm or m?
Coordinates must be entered in millimeters (mm). For example, if the anchor is installed at a height of 2.5 meters, enter Z = 2500.
The Web Console and RTLS engine use mm as the standard unit, so please be careful not to enter values in meters by mistake.
Can I use floor plan data instead of real measurements for coordinates?
Yes, but real measurements are more accurate.
If you only use values from the floor plan, there may be small differences between the drawing and the actual space. Also, the exact anchor position may not match the plan. These can cause errors in RTLS performance.
We recommend using a tape measure or laser distance meter to measure the real distances, then enter the coordinates based on those values.
What is the typical positioning range for indoor and outdoor environments?
The basic measurement range is similar for both indoor and outdoor use. However, the recommended anchor spacing is different due to structural differences in the environment.
✅ Installation guide by environment
Indoor
15m
25m
Within 10–30 cm
Outdoor
20m
25m
Within 10–30 cm
Indoor:
Indoor spaces often have walls, furniture, and ceiling structures that can block or reflect signals.
We recommend placing anchors closer together, within 15 meters.
Outdoor:
Outdoor spaces are more open with fewer obstacles.
Anchor spacing of up to 20 meters is usually stable for positioning.
📲 Tag / Device Testing
Can a smartphone replace a physical tag?
Yes. If you use the GrowSpace Mobile Kit (N1-CK-01), a smartphone with UWB can be used to test distance and positioning without a physical tag.
The smartphone acts like a tag. It sends and receives distance and direction data with the anchors, and joins the RTLS calculation in real time.
To use this feature, you need the following:
A smartphone that supports UWB (e.g. Galaxy S21+ or later, iPhone 11 or later)
GrowSpace Mobile app installed
At least 3 powered N1 anchors
Correct anchor coordinates entered
If you want to run tests using a smartphone, please purchase the GrowSpace Mobile Kit (N1-CK-01). It includes 3 anchors and an SDK, so you can start indoor distance and positioning tests using only the app.
Distance measurement works, but RTLS positioning does not. What could be the problem?
RTLS (Real-Time Location System) positioning requires more than just distance measurements. Several conditions must be met for the system to calculate a location. Please check the following:
Number of Anchors At least 3 anchors must be connected at the same time for RTLS to work. With only 1 or 2 anchors, trilateration is not possible, so the system cannot calculate a position.
Anchor Coordinates Each anchor must have accurate X, Y, Z coordinates entered in the app or system. If any coordinates are missing or incorrect, RTLS will not work.
Real-Time Session Status If some anchors are not connected in real time or have weak signals, the system may fail to show any location. Check that your BLE connection and UWB sessions are active.
Test Area Settings The RTLS system needs a defined test area (in meters) to show position on the screen. If the grid size is missing or too small, the location point may not appear.
If all of the above are correct but positioning still does not work, check your environment for possible issues such as metal interference or signal reflection.
What is the difference between the rechargeable and non-rechargeable Developer Tags?
Both versions have the same features and performance. The only difference is the power supply method.
🔋 Rechargeable Type
Can be charged via USB port
Has a built-in battery for easy wireless use
🔌 Non-Rechargeable Type
No USB charging circuit; requires an external power source
Best suited for fixed setups in labs or environments with constant power
How long does the rechargeable tag last?
The hardware is the same, but battery life depends on how you use the tag.
Wearable Tag (for tracking people): Up to 7 days of use → Battery life may vary depending on the update rate (e.g. 1Hz, 10Hz)
Asset Tag (for tracking assets or logistics): Up to 70 days of use → Uses a low-power transmission mode, suitable for long-term operation
※ Actual usage time may vary based on update rate, movement frequency, and transmission interval. For detailed specifications, please visit the official GrowSpace website.
📊 Data
Can I customize the format of the collected data?
Yes, you can.
By default, location data is sent via MQTT in JSON format with X, Y, and Z coordinates. After receiving the data, you can add timestamps or convert it into any format you need.
However, if you want to change the original JSON format sent from the system, you will need to customize the gateway firmware, which may require an additional cost.
Can you show an example of the data received via MQTT in JSON format?
Yes. Data received via MQTT is structured in JSON format as shown below.
Each message is grouped by gatewayID, and contains either tag or anchor data.
✅ Example: Tag data
json{
"gatewayID": "GR209C",
"tags": [
{"id": "GR2eba", "panID": "0001", "x": -4.45, "y": -0.19, "z": -2.22},
{"id": "GR1012", "panID": "0001", "x": -1.44, "y": 3.68, "z": 0.72},
{"id": "GR2c3c", "panID": "0001", "x": -3.91, "y": 0.22, "z": -2.45},
{"id": "GR2cb4", "panID": "0001", "x": -3.44, "y": -0.06, "z": -2.52},
{"id": "GR2eb9", "panID": "0001", "x": -4.95, "y": 0.65, "z": 1.36}
]
}✅ Example: Anchor data
json{
"gatewayID": "GR209C",
"anchors": [
{"id": "GR2fcc", "panID": "0001", "initiator": false, "x": -5.45, "y": 2.58, "z": 0.00}
]
}gatewayID: Identifier of the gateway that received the data
Tags / Anchors: Separated by device type; each is sent as a separate packet under the same gateway ID
List order:
tagsandanchorsare listed in the order received by the gatewayx, y, z: Position coordinates of the device, in meters (m)
How fast is the data processed?
Location data is updated at a rate of up to 10 times per second (10Hz). The gateway can handle up to 150 communications per second.
This means multiple tags can be processed quickly and reliably at the same time.
At 10Hz, up to 15 tags can be processed simultaneously
At 1Hz, up to 150 tags can be processed simultaneously
What format is the location data delivered in?
Location data is delivered in JSON format via the MQTT protocol. Each data packet includes the X, Y, Z coordinates of each tag, along with the gatewayID to identify the sending gateway.
You can process the received JSON data and connect it to your web service, database, or visualization system.
Can the GrowSpace system be integrated with external development environments like Python?
Yes, it can.
Since the GrowSpace system uses MQTT, it can work with various development environments such as Python, Node.js, and Java.
Using an MQTT client, you can receive and analyze real-time data.
We also provide documentation for integrating with our API or SDK if needed.
If you want to learn how to connect, please check this guide. It explains the MQTT connection method with practical examples.
What format is the real-time location data provided in?
The GrowSpace system provides location data collected from actual devices in two main ways:
1. MQTT data from the gateway
Location data received by the gateway is delivered in JSON format via MQTT.
This data can be easily integrated with visualization systems, external servers, or analytics platforms.
✅ Example: Tag location data
{
"gatewayID": "GR1234",
"tags": [
{
"id": "GR8a8",
"panID": "0001",
"x": -1.25,
"y": 10.12,
"z": 1.57
}
]
}✅ Example: Anchor location data
{
"gatewayID": "GR1234",
"anchors": [
{
"id": "GR1027",
"panID": "0001",
"initiator": false,
"x": -1.00,
"y": 11.48,
"z": 0.00
}
]
}✅ Example: Gateway information
{
"uwbID": "GR1234",
"panID": "0001",
"ip": "172.30.1.133"
}📌 Note:
x,y, andzrepresent the 3D coordinates of each device (unit: meters)
panIDis the zone identifier
initiatorindicates whether the anchor is the time synchronization starting point
2. String data from the Listener device
When using a Listener device, location data is provided in a simple string format. This method is useful for low-latency streaming or high-speed analytics systems.
✅ Example: Listener data
POS,0,08A8,-1.22,10.14,1.60,61,x0D
POS,0,08A8,-1.20,10.15,1.60,61,x0D
POS,0,08A8,-1.21,10.13,1.59,60,x0D
...POS
Data type
0
PAN ID
08A8
Tag ID
-1.22, 10.14, 1.60
X, Y, Z coordinates
61
Signal quality or internal indicator
x0D
End of data marker
⚙ This data can be processed in real time using various environments such as Python, C++, or Node.js.
🖥️ Operation and Management
Can I set multiple PAN IDs in one space?
Yes, you can.
The GrowSpace system allows you to set multiple PAN IDs within the same physical space. This lets you create separate tracking groups by zone or team, so you can manage location data more efficiently in shared areas.
How can I manage a space by dividing it into zones?
To divide and manage a space, you can separate zones using different PAN IDs. For example, assign PAN ID 0001 to Zone A and PAN ID 0002 to Zone B. This allows each zone to operate without interference.
You can also place separate anchors in each zone and set up zone definitions in the system. This makes your space management more organized and scalable.
Can positioning still work if one anchor fails?
Yes. As long as 3 or more anchors are still active, positioning will continue.
The GrowSpace system can calculate location as long as at least three anchors are working. So even if one anchor is turned off or fails, basic tracking will still function.
However, depending on the position of the failed anchor and the layout of the anchors, accuracy or coverage in some areas may be affected. For important spaces, we recommend placing 1–2 extra anchors as a backup.
Can I receive real-time location data through an API?
Yes, you can.
The GrowSpace system provides real-time location data using an MQTT-based API. Each device sends data through a unique MQTT topic, and developers can subscribe to these topics to receive live location updates.
✅ MQTT Topic Types Used
Gateway configuration info
uwb/gateway/config/{projectId}/{deviceId}
Tag / Anchor location data
uwb/gateway/devices/{projectId}/{deviceId}
Sent once at gateway boot
uwb/gateway/Start/{projectId}/{deviceId}
{projectId}refers to your API key.{deviceId}is the UWB ID of each gateway and serves as the device identifier.
※ When a gateway boots up, a Start topic is sent once. You can use this to check the initial connection status.
📚 Others
Can I only configure the system using GrowSpace Web?
Not necessarily.
GrowSpace Web is the easiest tool for configuration, but you can also set up devices locally via USB without an internet connection.
Devices can be configured by connecting them to a PC with USB
GrowSpace Web is a Progressive Web App (PWA), so it can also run offline
You can use it safely even in environments where internet access is limited
How can I update the firmware?
Currently, GrowSpace products do not support user-initiated firmware updates. All devices come with the latest stable firmware pre-installed.
In normal usage, you can use the product without needing any updates.
If you suspect a firmware-related issue, please contact the RTLS Support Team at contact@freegrow.io for inspection or replacement support.
Last updated