Distance error, angle error, position error and following behaviour are different acceptance questions. Define the output the host needs and the reference used to judge it before comparing UWB figures. A catalogue distance or angle accuracy is not a guarantee of a robot path, dynamic tracking result or safety function.
30 cm distance accuracy
±3° angle accuracy
Message format, age and validity
Following, interruption handling and system requirements
The GC-P2304-GS-2 entry supplies component figures. Measurement accuracy is not a guarantee of following or obstacle-detection performance.
Name the output and its reference
| Required output | Reference to define | Keep separate from |
|---|---|---|
| Distance | Known separation and reference method | Angle error and final equipment path |
| Bearing/angle | Reference orientation and angular convention | Distance error and coordinate error |
| Coordinates | Origin, axes and known reference points | A single distance or angle figure |
| Following behaviour | Target motion, host controller and acceptable task behaviour | The sensor’s catalogue measurement precision |
FiRa’s explanation of UWB describes general ranging and positioning concepts. It does not establish that every UWB product uses the same architecture, radio channel, profile or certification.
Keep the listed module facts together
The GC-P2304-GS-2 entry lists 30 m open-space range at 2 dBm, 30 cm distance accuracy, ±3° angle accuracy, UART and up to three simultaneous tags. These are separate manufacturer-stated quantities for the listed configuration.
Its frequency entry is CH2. Do not infer FiRa certification or interoperability from the general reference above. Request the supported tags, antenna configuration, firmware, messages and destination-market documentation for the actual hardware.
The GC-P2304-Q base station and GC-P2303-Q tag represent a different, site-oriented review. Do not transfer the embedded module’s figures to that combination.
Use a record that separates static and moving cases
Measurement output and units:
Board, antenna, tag and firmware revisions:
Reference positions/orientation and reference method:
Static arrangement and line-of-sight conditions:
Representative path, turn or occlusion:
Timestamped measurement and data age/absence:
Host-controller response:
Acceptance criterion, observations and unresolved questions:No update rate, speed limit or statistical percentile is filled in by this template. Those values need a project requirement or actual observations, with the method recorded.
Add motion only after the reference is clear
Start with a repeatable arrangement so the coordinate origin and error definition are unambiguous. Then select paths, turns, mounting changes and obstructions relevant to the equipment. Retain missing or old data alongside the measurements; a neat set of surviving points may hide an availability problem.
The host team owns the response to implausible or unavailable measurements. A UWB component alone does not provide obstacle detection, navigation control or a complete safety function.
Produce an evaluation decision
The outcome should state the configuration evaluated, the reference/method, the observations and the open conditions. It may support a revised mounting arrangement or another documentation request rather than a production choice.
Use UWB following and positioning integration for the project scope and component shortlist; keep this guide as the measurement-record companion.
Sources & method
The model figures are manufacturer-stated. The tables are evaluation-record templates, not measured results. FiRa is cited for general ranging concepts, not as evidence of certification or interoperability of the listed CH2 devices.