← Back to the chapter · Previous detail

Technical detail · UWB Indoor Positioning Systems

Review airtime load and the position error budget

Capacity belongs in the same evidence record as geometry. If 200 tags need a 1 Hz update, the system must budget about 200 tag reports per second before retries, management frames, and rejected observations. If the workflow can accept 0.2 Hz for slow-moving assets, the load drops to 200 x 0.2 = 40 reports per second. That change may decide whether TDoA blinks are sufficient, whether TWR exchanges are practical only for a smaller tool fleet, or whether the project needs smaller zones with different update policies.

Compare two rough budgets. In a TWR design with 80 active tags, 4 anchors per position, and 1 update per second, the system asks for about 80 x 4 x 1 = 320 tag-anchor ranging exchanges per second. If a commissioning mode uses only 10 tools at 2 Hz, the request is 10 x 4 x 2 = 80 exchanges per second, which may be more manageable. Per-anchor evidence still needs its own quality checks. In a TDoA design, 80 tags at 1 Hz can be closer to 80 tag transmissions per second because synchronized anchors listen to the same blink. The tradeoff is that anchor synchronization, timestamp quality, and calibration become release-critical evidence.

The solver then turns accepted observations into position with an error budget, not a guarantee. A practical record might say: range uncertainty 0.15 m, geometry factor 2.5, expected environment bias 0.20 m, and filter lag allowance 0.10 m. A simple review estimate is 0.15 x 2.5 + 0.20 + 0.10 = 0.675 m. If the application needs only room-level asset awareness, that may be acceptable. If it needs a robot safety boundary at 0.30 m, the same evidence is not good enough.

← Back to the chapter · Previous detail