Warehouse Tracking Is the Least Interesting Thing UWB Does
Measuring where a person or object is with Bluetooth Low Energy (BLE) is like finding a bakery by its smell. You know it is close, you just can’t tell if it is 10 metres ahead or 30 metres to your left. Ultra-Wideband (UWB) gives you an edge. It measures the same distance the way a tape measure does: accurate to the centimetre. That precision is why UWB is showing up in applications where BLE cannot deliver. Every one of those applications is a firmware team solving a problem BLE never forced them to think about.
Most of the content written about UWB fixates on Real-Time Location Systems (RTLS: infrastructure-heavy tracking systems that monitor the positions of assets and people across a large space using fixed anchor hardware).
That coverage has its place. However, the five applications where firmware teams are doing the most interesting work “right now” go largely unwritten about: autonomous robot follow-me, child presence detection tied to automotive safety ratings, gesture recognition without cameras, contactless vital sign monitoring, and peer-to-peer ranging in consumer devices. Two of these are what regulation mandates. But all five are firmware-intensive in ways warehouse tracking never is.
This article covers all five. It includes: why UWB fits each problem, what the firmware actually has to do, and which silicon fits each use case. As for the alternatives, catch a more detailed read in our other post – UWB vs BLE vs Wi-Fi: A Firmware Engineer’s Decision Framework.
Why UWB Changes the Firmware Problem
A UWB pulse lasts less than one nanosecond, the time it takes light to travel roughly 30 centimetres. That timing precision is what makes UWB a ruler rather than a radio.
Here is what “wide frequency bandwidth” means in plain terms. Narrow-band radios broadcast the way someone holds a long note on a saxophone: by the time the note reaches you directly, the echo bouncing off the wall is already on top of it.
The two blur into one sound. UWB broadcasts the way a drummer plays a single sharp hit: direct sound and echo arrive as two distinct beats you can tell apart. Spreading across 500 MHz gives the receiver that sharp-beat resolution. It separates the direct signal from its wall-reflected copies cleanly.
For firmware engineers, this shifts the problem from filtering and estimating to measuring and acting.
The five applications below all exploit that shift in different ways.
1. Autonomous Robot Follow-Me
An autonomous follow-me robot is a wheeled or legged machine that follows a specific person through a shared workspace: a nurse down a hospital corridor, a warehouse picker between aisles, a logistics worker on a factory floor. The robot carries the tools, parts, or load the person would otherwise push on a cart. The design brief sounds simple. Stay a fixed distance behind the person. Close enough to be useful. Far enough to be safe. Never hit them.
The environment is where the job gets hard. For instance, in situations where: another person steps between the robot and the operator or the operator turns around and walks back to grab something from the cart. The robot has to spot the reversal, stop and hold its ground, then swing around and start following again once the operator heads off.
KUKA’s KMR iiwa, one of the most capable mobile robots on factory floors today, uses laser scanners to navigate for exactly these reasons. The same problem now shows up in humanoid robotics. Unitree’s G1 humanoid is already being paired with UWB tracking modules from vendors like Weston Robot. Once a humanoid is meant to share spaces with people, the robot must know the exact position of the person it follows, within a few centimetres, at all times.
BLE Received Signal Strength Indicator (RSSI) fails in these conditions because signal strength is a guess. The same received power could mean the operator is 2 metres directly ahead, or 8 metres away behind a steel shelf. UWB works differently. It timestamps when a radio signal is sent and when it comes back, divides by the speed of light, and returns a distance accurate to centimetres.
Think of it the way a ship uses sonar: send a pulse toward the seabed, wait for it to return, measure the round-trip time, and the depth is calculable to within metres.
TWR does the same thing between two UWB radios, at the speed of light: the tag sends a timestamped message, the anchor responds with its own timestamp, and the round-trip time reveals a distance accurate to centimetres. A UWB tag worn by the operator and an anchor node mounted on the robot exchange these ranging messages on a timed schedule.
The firmware on the robot side runs a ranging scheduler: a task that wakes the radio, collects the distance measurement, and passes it to the motion controller before putting the radio back to sleep. For heading estimation (knowing which direction to follow, in addition to how far), firmware teams typically fuse UWB readings from two or three tag positions with data from an Inertial Measurement Unit (IMU: a sensor that measures acceleration and rotation, used here to track which way the robot is turning).
Silicon that fits: the Qorvo DW3120 handles TWR with interrupt-driven firmware integration that maps cleanly onto a Real-Time Operating System (RTOS: the software layer that manages when each firmware task runs on the processor). For battery-operated operator tags where current draw is the binding constraint, Spark Microsystems documents the SR1000 at sub-mW active receive current at 0.85 Mbps in its product documentation.
For teams evaluating autonomous mobility systems: UWB follow-me removes the “clean environment” assumption from your testing checklist. The system works where your robot actually operates.
2. Child Presence Detection
By 2026, Child Presence Detection (CPD) has become a requirement for top safety ratings in major markets, led by the European New Car Assessment Programme (Euro NCAP: the body that rates vehicle safety across Europe). Euro NCAP started awarding CPD points in 2023. From January 2025, the system must also detect a child aged three to six who climbs into an unlocked car on their own and becomes trapped when it locks. The US Hot Cars Act pushes a parallel regulatory path.
Two standards bodies carve up the CPD problem between them: Euro NCAP sets the detection requirements (what the system must spot, and how reliably), while the FiRa Consortium (Fine Ranging Consortium: the industry body that governs how UWB devices from different vendors talk to each other) sets the interoperability rules for the UWB radios themselves. For automotive suppliers and Tier 1 integrators, Euro NCAP’s CPD requirement is already scoring your competitors. This is an engineering deadline with a date attached, and a 5-star rating on the line.
The challenge is physical. A sleeping infant’s chest rises and falls three to eight millimetres with each breath. A heartbeat moves the chest by 0.2 to 0.5 millimetres. Cameras need good lighting and a clear view of the child. A closed car on a hot day gives you neither.
Think of UWB in-cabin sensing the way a bat navigates a cave. A bat reads the echo of its own chirp to map everything around it: walls, gaps, moving prey, without needing to see any of it.
A UWB radar node reads the echo of its own pulse, and a breathing chest changes that echo in a pattern no inanimate object in the car produces. The firmware configures the radio in radar mode rather than ranging mode, collects pulse-return data at a high repetition rate, applies signal averaging to filter out road vibration, and extracts the respiration waveform from what remains.The FiRa Consortium sets the interoperability rules for UWB ranging. The CPD sensing requirements (what the system must detect and how reliably) are governed by Euro NCAP.
Silicon that fits: NXP’s Trimension is the company’s family of UWB chips — the same line BMW uses for its Digital Key Plus passive entry system. NXP’s published documentation for in-cabin UWB sensing covers the Trimension CPD configuration in detail. The chip built for this job in production vehicles is the NCJ29D6A. It combines UWB ranging with short-range radar on a single chip and carries AEC-Q100 qualification (Automotive Electronics Council standard 100: the industry test suite that confirms a chip survives the temperature swings, vibration, and humidity a car endures over its lifetime). For CPD specifically, that matters because the chip has to keep working in a parked car that hits 70°C on a hot afternoon.
3. Gesture Recognition
For product teams in automotive, consumer electronics, and industrial control: UWB gesture recognition works in any lighting condition, captures no image data, and runs five to seven recognised gestures at above 90% accuracy in production conditions. The privacy compliance burden disappears before it reaches your legal team.
Camera-based gesture systems face three challenges firmware teams rarely budget for up front. The first is the privacy compliance burden image capture brings with it. The second is processing demand most embedded platforms cannot spare. The third is a hard dependency on lighting conditions. UWB sidesteps all three.
Every UWB transmission channel produces a Channel Impulse Response (CIR). Think of the CIR the way a musician reads a room. Strike the same chord in an empty warehouse and in a tiled bathroom, and the note sounds different: same source, but completely different reflection profile.
When a hand moves between two UWB nodes, the CIR shifts in a pattern that matches the gesture. The firmware grabs the CIR frames at a fast update rate, hands them to a machine learning model running on the main microcontroller, and outputs the gesture in under 50 milliseconds.
How many gestures can UWB tell apart? A 2020 study hit 95% accuracy across eight hand gestures. The gestures were four swipe directions (left-right, right-left, up-down, down-up), two diagonal swipes, and two rotations (clockwise and counterclockwise). A 2021 public dataset stretched the count to twelve. In production cars, where a false positive is dangerous, vendors keep the menu tighter: five to seven gestures, accuracy above 90% once the model is trained on the actual cabin layout.
The implementation challenge is throughput. Raw CIR data coming off the radio must move to the classifier without stalling other firmware tasks. On an RTOS, that means a dedicated high-priority interrupt service routine handing data to a processing queue, with the classifier running as a lower-priority task against a timestamp-matched buffer. Teams that underestimate this pipeline are the ones who end up with gesture latency measured in seconds rather than milliseconds.
Silicon that fits: Where most ranging chips hand you a distance and nothing else, Qorvo DW3220 gives you the full raw reflection data directly. That full reflection fingerprint is what the classifier trains on and runs against. A mature driver ecosystem means the radio is up and feeding data quickly. The firmware problem left to solve is the interesting one: building the model.
4. Vital Sign Monitoring
For medical device teams and automotive OEMs: contactless vital sign monitoring removes the need for electrodes, adhesives, or patient compliance. The sensor reads breathing and heartbeat at up to five metres of clear line-of-sight. It works whether the patient cooperates or not.
UWB can detect breathing and heartbeat through air, without touching the patient. The physics is the same impulse-radar principle used in contactless monitors in neonatal intensive care units (NICUs), where it has been tested against ECG and chest-impedance sensors on more than thirty premature babies in published clinical studies. Microwave radar has been used to monitor vital signs in clinics since the mid-1970s. UWB takes the same physics and shrinks it to fit the power budget and board space embedded engineers work with.
Each UWB pulse reflects off the chest wall. As the chest moves with each breath, the return time of the reflected pulse shifts by picoseconds (trillionths of a second), corresponding to a displacement of millimetres. The firmware averages thousands of pulse returns to pull this signal out of noise, applies bandpass filters tuned to the frequencies of human respiration (12 to 20 cycles per minute) and heartbeat (60 to 100 beats per minute), and produces a clean waveform a host processor can interpret.
A useful frame for picturing this: press your wrist gently against a drumhead while someone taps the other side of the drum. You feel the vibration clearly, even though your wrist is nowhere near the source. UWB reads the equivalent of that vibration through open air, without any physical connection to the patient. Working range for reliable respiration detection is up to approximately 5 metres under clear line-of-sight conditions.
Applications include neonatal monitoring, in-vehicle occupant detection as a complement to the CPD use case above, and eldercare systems where reducing physical contact with a sensor matters. A patient who moves or removes a wired monitor in the night still has a chest wall that can be monitored.
Silicon that fits: Novelda’s X4M200 is a dedicated Impulse-Radio UWB (IR-UWB: the sub-category of UWB that uses short, repeated radar-like pulses specifically for sensing rather than communication) respiration sensor. Novelda’s own product documentation confirms its 0.4 to 5-metre sensing zone for breathing detection, and the IR-UWB approach it uses is independently validated in peer-reviewed literature.
5. Peer-to-Peer Ranging
Fixed-infrastructure positioning is expensive. RTLS forces you to mount anchors on ceilings, calibrate them, run a location engine on a server, and pay to keep all of it running. That cost shuts a lot of useful applications out of the market.
Peer-to-peer (P2P) UWB ranging removes the infrastructure entirely. Two devices with UWB radios trade timestamped messages and work out the distance between them directly. No anchors. No server.
What this unlocks: Apple’s AirTag uses P2P UWB to point you to a misplaced wallet within a few centimetres. BMW’s Digital Key Plus uses it for hands-free entry: the owner’s phone ranges against a UWB node inside the car door, and the lock opens when the phone is authenticated and inside the permitted zone.
The Car Connectivity Consortium (CCC: the industry body that sets the standard for how phones unlock cars) defines this in its Digital Key 3.0 standard, covering both the ranging protocol and the security on top of it. Industrial proximity warning, asset pairing without a network, and contactless payment confirmation are all live build areas.
What firmware has to solve: The hard problem is not ranging. It is scheduling. When dozens of P2P devices range at the same time in a tight space like a car park, a warehouse loading dock, or a busy office, the protocol has to decide who talks when. If it gets that wrong, measurement collisions stack up into delays.
Think of P2P ranging like two people standing at opposite ends of a street, each holding a stopwatch synchronised to the same clock. One calls out, the other records the time of arrival and calls back. From those two timestamps and the known speed of radio waves, both can calculate the distance between them to within centimetres.
The firmware manages two roles: initiator (the device that sends the first ranging message) and responder (the device that timestamps receipt and replies). At product scale, the hard firmware problem shifts from ranging to scheduling: when dozens of P2P devices are ranging simultaneously in a confined space, the protocol must handle contention without measurement collisions stacking up into delays.
Silicon that fits: Qorvo documents the DW3xxx series for consumer and industrial P2P ranging in its “UWB in Digital Car Key” whitepaper, which details ranging performance in CCC Digital Key 3.0-compliant deployments. For automotive-grade implementations requiring both CCC compliance and AEC-Q100 qualification, NXP’s Trimension SR150 product documentation maps the chip directly to the CCC Digital Key 3.0 specification.
The Thread Running Through All Five
None of the five applications above uses ceiling anchors. None requires a cloud location engine. Strip away the RTLS framing that dominates most UWB content, and what remains is a single consistent capability: precise distance measurement between two points, executed in firmware, at close range.
That is the thread. Between two devices. Between a radar node and a chest wall. Between a robot and the operator it follows.
The firmware architecture that serves all five looks the same at its core: a ranging or radar engine producing raw measurements, a decision layer acting on those measurements against a threshold or model, and a power manager keeping the radio asleep between sessions. Master that pattern once, and it transfers across every application in this article.
One constraint carries across all five applications: line-of-sight matters, but the meaning is more specific than zero obstacles. Commercial UWB ranging chips operate in the 6 to 9 GHz band. At those frequencies the signal passes through drywall, wood, and glass with some loss of accuracy. It degrades sharply through brick and reinforced concrete. It is effectively blocked by metal: steel shelving, car door pillars, aluminium cabinets, copper plumbing in a wall. Water absorbs UWB too, which is why a human body itself blocks the signal.
The practical rule for firmware teams: a UWB node needs a clear radio path to its target, free of metal obstructions, with at least twenty centimetres of clearance from any nearby metal that could distort the antenna. A metal cabinet between a UWB node and a patient’s chest, a car door pillar between two ranging nodes, a steel shelf between a robot and its operator tag will all wreck measurement quality. Antenna placement is an architecture decision. Finalise it before the software stack takes shape.
The volume in UWB over the next product cycle is coming from these five firmware problems, driven by regulatory mandates, consumer product adoption, and the specific gap that centimetre-level ranging fills where BLE cannot.
Where does your current product sit against that list, and what does the firmware architecture need to look like when UWB joins the stack?
Work With embedUR
embedUR’s firmware team has integrated UWB ranging across automotive, consumer, and industrial applications. If you are evaluating UWB for any of the applications covered here, a 30-minute architecture review maps your requirements to a firmware topology and flags integration risks before any code is written.
If you enjoyed this article, discover even more of UWB’s capabilities in our next blog post – UWB Beyond Ranging: What IEEE 802.15.4ab Means for Your Firmware.
