
CUWB 200 Hz Ultra-Wideband (UWB) tags beacon up to 200 times per second. This explainer covers what that rate means in practice, what it costs the network, and how roles let integrators use it where it adds value.
Tags beacons, or transmissions, over ultra-wideband are heard and timestamped by anchors and used by the CUWB location engine to determine the tags location. A tag’s “beacon rate” is how often it transmits. At 10 Hz, a tag reports ten times per second, or once every 100 milliseconds. At 200 Hz, it reports every 5 milliseconds.
A higher beacon rate doesn't change how precisely each position is measured. It changes how much of the movement between positions you can see. A forklift braking hard, an autonomous mobile robot correcting its path or an athlete changing direction can happen between two updates at a standard rate. At 200 Hz, those moments show up in the data.
Watch: how beacon rate works on a live CUWB network.
Rapid beacon rates do more for integrations than just fill in the gaps. As Justin Bennett, Director of Engineering at Ciholas, explains, a richer stream of location data lets system integrators apply advanced filtering while keeping latency low. Filtering can help reach the target performance with fewer anchors, which lowers infrastructure and overall system costs.
Ultra-wideband airtime is a shared resource. Every beacon uses a slice of the network's airtime, and when two devices transmit at the same time, they collide resulting in bad data. In MultiTimeTM mode, where the CUWB engine schedules every transmission to avoid collisions, a CUWB network supports up to 3,300 location updates per second (LPS) in a single coverage area.
A 200 Hz tag uses 200 LPS, and ten 200 Hz tags use 2000. On a system with 3300 LPS available, that leaves enough capacity for another 130 tags operating at 10Hz. That's a good trade when those ten tags are the ones that matter, and a poor one when they aren't. For fast rates, generally above 50 Hz per tag, MultiTime™ mode is the recommended setup.
Beacon rates aren’t fixed. In the CUWB Manager, each role has its own beacon rate, and tags are assigned a role. A tag can move between roles on a live network. As a result, its rate can change with what it's doing.
Robotics: an AMR operates at 200 Hz while it's moving and drops to a low rate when it's parked or charging.
Sports: players on the field are tracked at 200 Hz, while players on the bench are tracked at a lower rate until they're subbed in.
Live production: performers on stage run at 200 Hz, and everyone backstage runs at 10 Hz, switching as people walk on and off.
System capacity is used where it is needed, leaving room for the rest of the system to keep running as normal.
Battery life: a tag beaconing at 200 Hz uses noticeably more power than one at 10 Hz. Roles help here too. You can move a tag to a lower-rate role when it doesn’t need 200 Hz, saving battery.
Network capacity: every high-rate tag draws on the shared airtime budget. Plan how many tags need 200 Hz at the same time in the same area.
Network mode: high beacon rates are best supported in MultiTime™ mode, where transmissions are fully scheduled.
The 200 Hz tags are built for applications where milliseconds matter:
The 200 Hz tags are available now. Learn more at cuwb.io/tags, or contact us to talk through the beacon rates and roles your application needs.