Radar for Robotics: The Ultimate Guide

A camera sees color and a LiDAR sees geometry, and both go blind the moment the air fills with dust, fog, rain, or smoke, or the moment the sun sets and no one turns a light on. Radar keeps working. It sends out a radio wave in the millimeter band, listens for the echo, and reads distance, speed, and rough direction off the returned signal, and it does this through a dust cloud that would white out a laser and in a darkness that would blind a camera. That robustness, plus a trick no optical sensor can match (it measures the radial velocity of every target directly, on a single frame, with no tracking), is why radar earned a permanent seat on self-driving cars and is now spreading to drones, mobile robots, and security systems.

This guide is about millimeter-wave (mmWave) radar as a robotics sensor. We will work through how a frequency-modulated continuous-wave (FMCW) chirp encodes range as a beat frequency, how the phase change of that beat across successive chirps recovers velocity through the Doppler effect, and how an antenna array recovers angle. We will go through the radar equation that sets your detection range, the resolution limits that make radar coarse in angle, and the multipath and clutter artifacts that make a raw radar point cloud look like a hallucination until you clean it. Then we get concrete: automotive versus imaging (4D) radar, the 24/60/77 GHz bands, indoor presence and vital-signs sensing, and where radar fits against LiDAR and cameras on a real robot.

Radar is the sensor you add when the other two fail. It does not draw a pretty picture of the world, and its angular resolution is coarse enough that a bicycle and a lamppost can merge into one blob. What it gives you is a distance and a velocity you can trust in weather and darkness, cheaply, from a solid-state chip with no moving parts.

The take: radar's value is a direct, per-target radial velocity measured through weather and darkness, from a cheap solid-state sensor with no moving parts. Its weakness is angular resolution: it tells you how far and how fast far better than it tells you exactly where. Treat radar as the all-weather velocity-and-range layer that fuses with a camera for semantics and a LiDAR for fine geometry, and you get a perception stack that degrades gracefully instead of failing all at once.

Companion reading: LiDAR & depth cameras, robot sensors, sensor fusion & Kalman filtering, self-driving cars, and counter-drone (C-UAS).

Table of contents

1. Key takeaways
2. Why radar earns a seat on a robot
3. FMCW fundamentals: how a chirp measures range
4. Velocity from Doppler across chirps
5. Angle from an antenna array
6. The radar equation and detection range
7. Bands: 24, 60, and 77 GHz
8. Imaging radar and the 4D point cloud
9. Indoor presence and vital-signs sensing
10. The signal-processing chain
11. Radar vs LiDAR vs camera
12. Limitations: resolution, multipath, clutter, ghosts
13. Applications and how to select
14. Frequently asked questions

Why radar earns a seat on a robot

A robot's exteroceptive sensors each answer "what is around me" through a different physical channel, and each channel has weather and lighting it cannot survive. A camera collects ambient light and reads color and texture, so it fails in darkness, glare, and fog. A LiDAR emits its own light and times the return, so it works in the dark but its 905 nm or 1550 nm beam scatters off airborne dust, fog droplets, rain, and snow, filling the point cloud with false returns and cutting range. The LiDAR and depth cameras guide covers both in depth.

Radar operates in the millimeter-wave band, wavelengths of roughly 1 to 12 mm. Those waves are long enough to pass around and through small particles that scatter light. Fog droplets, dust grains, and rain are a large fraction of an optical wavelength, so they scatter light strongly, and a small fraction of a radar wavelength, so they barely perturb the radio wave. The result is a sensor that measures a truck through a dust storm that has blinded every optical sensor on the vehicle. Radar is also fully active and coherent: it supplies its own illumination and cares only about the echo of its own transmitted signal, so ambient light and darkness are irrelevant.

The second reason radar earns its seat is velocity. Because it is a coherent sensor, it measures the Doppler shift of every target directly, which is the target's radial velocity relative to the robot, on a single measurement frame with no frame-to-frame tracking. A camera infers speed by differencing positions across frames, which is noisy and lagged. A LiDAR does the same unless it is an expensive FMCW unit. Radar hands you velocity for free, and velocity is exactly the quantity a collision-avoidance or tracking system wants most.

Rule of thumb: reach for radar when your robot must work in weather or darkness, or when you need direct target velocity. Reach for LiDAR or a camera when you need fine spatial detail or semantics. The strong systems carry all three and fuse them.

The cost of these strengths is detail. Radar's angular resolution is coarse, its point clouds are sparse and noisy, and it carries no color or texture at all. It tells you a target is 42 m away closing at 8 m/s somewhere in a 12-degree cone, and it tells you that reliably in conditions that would blind everything else. That trade is the whole story of radar in robotics.

FMCW fundamentals: how a chirp measures range

Almost every mmWave radar in robotics is FMCW: frequency-modulated continuous wave. Instead of firing a short pulse and timing the echo (which demands the same picosecond timing electronics that make pulsed LiDAR hard), FMCW transmits a continuous signal whose frequency ramps linearly over time. That ramp is called a chirp.

The chirp and the beat frequency

A chirp sweeps from a start frequency f_c upward at a constant slope S = B/T_chirp, where B is the swept bandwidth and T_chirp is the chirp duration. The transmitted signal reflects off a target and returns after the round-trip time t = 2R/c. Because the transmitter has kept ramping during that delay, the returned echo is a copy of the chirp shifted slightly lower in frequency. Mixing the echo with the current transmit signal (a homodyne mixer) produces a low-frequency "beat" tone whose frequency is directly proportional to range:

Range beat frequency:
  f_R = S · t = S · (2R/c) = (2 · B · R) / (c · T_chirp)

  S       = chirp slope = B / T_chirp  [Hz/s]
  B       = swept bandwidth  [Hz]
  T_chirp = chirp duration   [s]
  R       = target range     [m]
  c       = speed of light ≈ 3e8 m/s

Solve for range:
  R = (c · f_R) / (2 · S) = (c · f_R · T_chirp) / (2 · B)

The elegance is that a target's range shows up as a single tone in the mixer output. Take a Fourier transform of one chirp's beat signal (the "range FFT") and each target appears as a peak at its own beat frequency. Multiple targets at different ranges produce multiple tones, and the FFT separates them in one operation. This is why FMCW radar can be built on a cheap CMOS chip: the hard part is a fast ADC and an FFT, not picosecond timing.

Range resolution depends only on bandwidth

Two targets are resolvable in range only if their beat tones are far enough apart to appear as separate FFT peaks. The FFT can separate two tones spaced by at least 1/T_chirp in frequency, which translates to a range separation:

Range resolution:
  ΔR = c / (2 · B)

  B = 1 GHz  →  ΔR = 15 cm
  B = 4 GHz  →  ΔR = 3.75 cm

Range resolution depends on the swept bandwidth alone, not on the chirp time, the carrier frequency, or the processing. Widen the sweep and you resolve finer. This is the single most important radar equation to internalize: if you need to tell two close objects apart in range, you need bandwidth, and bandwidth is exactly what the 77 GHz automotive band (4 GHz wide) provides and the old 24 GHz narrowband band (200 MHz) does not.

Maximum range and the ambiguity ceiling

The maximum unambiguous range is set by how fast you sample the beat signal. The ADC sampling rate F_s must capture the highest beat frequency, which corresponds to the farthest target:

Max range (ADC-limited):
  R_max = (F_s · c) / (2 · S)

Push the slope up to pack more chirps into a frame and you lower the maximum range for a given ADC. The real limit is usually the radar equation and signal-to-noise, covered below, but the ADC ceiling is why a datasheet's "maximum range" is a design choice traded against range resolution and frame rate, not a fixed property of the chip.

Rule of thumb: range resolution is bandwidth (ΔR = c/2B), and nothing else moves it. If a spec sheet promises fine range separation on a narrowband 24 GHz part, it is promising something the physics does not allow.

Velocity from Doppler across chirps

Range comes from one chirp. Velocity comes from comparing many chirps. A radar frame is a burst of chirps, typically 64 to 256 of them fired a few microseconds apart. This burst is called a chirp frame or, in the processing, the "slow-time" dimension.

The phase trick

A moving target changes its range slightly between one chirp and the next. That range change is tiny (a target at 10 m/s moves 0.1 mm in a 10 microsecond chirp gap), far too small to see in the range FFT, whose resolution is centimeters. But it shows up as a phase shift of the beat tone. The phase of a returned signal advances by 4π·ΔR/λ for a range change ΔR, and because the millimeter wavelength is so short, even a sub-millimeter motion produces a measurable phase rotation from chirp to chirp.

Take the range FFT of every chirp in the frame, then run a second FFT across the chirps at each range bin (the "Doppler FFT"). A target moving at radial velocity v_r produces a phase that rotates at a constant rate across the chirps, which the Doppler FFT reads as a peak at a specific Doppler frequency:

Doppler frequency:
  f_D = 2 · v_r / λ

Radial velocity:
  v_r = (λ · f_D) / 2

  λ = c / f_c  (≈ 3.9 mm at 77 GHz)

The two-dimensional result (range FFT then Doppler FFT) is the "range-Doppler map": a grid where each cell is a range-velocity pair, and each target lights up a cell. Two objects at the same distance but different speeds (a car and the road behind it) land in different Doppler bins and separate cleanly. This is the measurement that no optical sensor gives you on one frame.

Velocity resolution and ambiguity

Velocity resolution is set by how long the whole frame lasts, because a longer observation resolves finer frequency differences in the Doppler FFT:

Velocity resolution:
  Δv = λ / (2 · T_frame)

  T_frame = N_chirps · T_chirp  (total frame time)

Max unambiguous velocity:
  v_max = ± λ / (4 · T_chirp)

The tension is direct. To measure fine velocity differences you want a long frame (many chirps), and to measure high velocities without ambiguity you want a short chirp spacing. A target faster than v_max aliases: its phase rotates more than π per chirp and wraps, so a fast approaching car can read as a slow receding one. Designers pick the chirp timing to cover the velocity span the application needs, and advanced systems stagger chirp timing or use multiple pulse-repetition intervals to unwrap the ambiguity, the same Chinese-remainder logic that unwraps phase in an iToF depth camera.

War story: an outdoor AMR kept braking for oncoming forklifts that were actually parked. The radar's max unambiguous velocity was set low for a slow indoor robot, and a forklift approaching at 4 m/s aliased across the wrap into a phantom fast target that tripped the collision logic. The fix was shortening the chirp spacing to raise v_max above any speed the site produced, at the cost of coarser velocity resolution the application did not need. The sensor had reported the wrapped velocity honestly; the frame timing was wrong for the environment.

Angle from an antenna array

Range and velocity come from the waveform. Angle comes from geometry: using more than one receive antenna and reading the phase difference of the echo between them.

Phase difference across receivers

A wavefront arriving from angle θ (off boresight) reaches two antennas spaced d apart at slightly different times, so it arrives with a phase difference:

Phase difference between adjacent antennas:
  Δφ = (2π · d · sin θ) / λ

Solve for angle:
  θ = arcsin( (λ · Δφ) / (2π · d) )

With antennas spaced at half a wavelength (d = λ/2), the phase difference maps directly to the angle of arrival. Run a third FFT across the receive antennas (the "angle FFT") and each target's angle appears as a peak, giving the full three-dimensional picture: range, velocity, and angle. Two receive rows give elevation as well as azimuth, which is what makes a "4D" radar (range, velocity, azimuth, elevation).

MIMO: a large virtual array from few antennas

Angular resolution improves with the number of antennas, and physical antennas cost board space and receiver channels. MIMO (multiple-input, multiple-output) radar synthesizes a large array cheaply. With N_Tx transmit antennas emitting separable waveforms (time-multiplexed or coded) and N_Rx receive antennas, the processing reconstructs N_Tx · N_Rx distinct virtual antenna positions. A chip with 3 transmit and 4 receive antennas behaves like a 12-element receive array:

Virtual array size:
  N_virtual = N_Tx · N_Rx

Angular resolution (uniform array, boresight):
  θ_res ≈ λ / (N_virtual · d)   [radians]
        ≈ 2 / N_virtual          (for d = λ/2, small angle)

A 12-element virtual array resolves roughly 2/12 ≈ 0.17 rad ≈ 10 degrees. To reach the 1-degree resolution of imaging radar you need on the order of 100 to 200 virtual elements, which is exactly what cascaded imaging radars build by chaining several transceiver chips (for example a 4-chip cascade giving 12 transmit by 16 receive, or 192 virtual antennas). MIMO is the reason radar angular resolution is climbing without the antenna count exploding.

Why angle is the weak axis

Compare the three axes. Range resolution is centimeters (set by gigahertz of bandwidth). Velocity resolution is a fraction of a meter per second (set by a long frame). Angular resolution is degrees, and a 10-degree cone at 50 m is nearly 9 m wide. This is why radar merges nearby objects laterally: a pedestrian standing next to a pole at 40 m falls inside one angular bin and returns as a single blob. Every angular improvement (more antennas, super-resolution algorithms like MUSIC or ESPRIT) fights this, and imaging radar is the current answer.

The radar equation and detection range

How far a radar detects a target follows the radar range equation, the radio-frequency cousin of the LiDAR range equation. Because the wave spreads out on the way to the target and again on the way back, received power falls as the fourth power of range:

Radar range equation (monostatic):
  P_r = (P_t · G² · λ² · σ) / ((4π)³ · R⁴)

  P_t = transmit power
  G   = antenna gain (assumes same antenna Tx and Rx)
  λ   = wavelength
  σ   = target radar cross section (RCS)  [m²]
  R   = range

Two facts fall out. First, the 1/R⁴ falloff is punishing: doubling the range cuts the return by 16x, so radar detection range is hard-won and every decibel of transmit power, antenna gain, and processing gain matters. Second, detection depends on the target's radar cross section (RCS), a measure of how strongly it reflects radio waves back toward the sensor.

Radar cross section decouples from physical size

RCS is what makes radar counterintuitive. It depends on a target's shape, material, and orientation, with size only one factor among them. A flat metal plate facing the radar has an enormous RCS; the same plate tilted away reflects the wave elsewhere and nearly vanishes. A corner reflector (three perpendicular faces) bounces the wave straight back and has an RCS far larger than its physical size. A person is a poor reflector (roughly 0.5 to 1 m² RCS, and variable), a car is large (roughly 10 to 100 m²), and a small drone can be tiny (0.01 m² or less), which is exactly why detecting small drones at range is a genuinely hard radar problem covered in the counter-drone guide.

Approximate RCS (77 GHz, order of magnitude):
  Pedestrian      0.5 - 1 m²
  Bicycle         ~2 m²
  Car             10 - 100 m²
  Small drone     0.01 - 0.1 m²
  Corner reflector  much larger than physical size

Processing gain and honest range specs

FMCW radar wins back a great deal against the 1/R⁴ falloff through coherent processing gain. The range and Doppler FFTs coherently sum energy across the chirp bandwidth and the whole frame, so a target buried below the noise in a single sample rises above it after processing. This is why a low-power CMOS radar detects a car at 200 m: the raw echo is far below noise, and the FFTs concentrate it into a peak. When you read a maximum-range spec, ask which target RCS it assumes. A range quoted against a car (large RCS) says nothing about detecting a pedestrian (small RCS) at the same distance.

Rule of thumb: radar detection range scales as (P_t · G² · σ)^(1/4), so hardware improvements buy range slowly. The cheap way to extend usable range is processing gain (more chirps, longer integration) and a fusion partner that fills in where RCS is low.

Bands: 24, 60, and 77 GHz

Radar for robotics lives in a few licensed and license-exempt millimeter-wave bands, and the band cascades into bandwidth, antenna size, and range.

24 GHz is the legacy short-range band. The narrowband allocation offers around 200 MHz of bandwidth, which caps range resolution at roughly 75 cm, far too coarse to separate nearby objects. The wideband 24 GHz allocation that once offered more is being phased out by regulators worldwide. New designs avoid 24 GHz except for the simplest presence and motion detectors.

60 GHz (57-64 GHz, license-exempt in much of the world) is the short-range indoor band. It offers wide bandwidth (up to 7 GHz in some allocations, so sub-centimeter range resolution) and the shortest wavelength, so antennas and the whole module shrink to fit a phone or a smart-home device. The catch is atmospheric absorption: oxygen has an absorption peak near 60 GHz that attenuates the signal strongly over distance, which limits range to a few meters. That limit is a feature indoors, because it stops the radar seeing through a wall into the next room, and 60 GHz is the band for gesture sensing, presence detection, and vital-signs monitoring.

77 GHz (76-81 GHz) is the workhorse for automotive and outdoor robotics. It provides up to 4 GHz of bandwidth (about 3.75 cm range resolution), a short enough wavelength (3.9 mm) for small high-gain antennas, and it is the globally harmonized automotive radar band, so the silicon ecosystem (Texas Instruments AWR/IWR, NXP, Infineon) is mature and cheap. The 76-77 GHz sub-band allows higher transmit power for long-range forward sensing; the 77-81 GHz sub-band allows the full 4 GHz sweep for short-range high-resolution sensing. For any robot that goes outdoors or needs both range and resolution, 77 GHz is the default.

Band	Bandwidth	Range resolution	Typical range	Antenna size	Best for
24 GHz	~200 MHz	~75 cm	short-medium	larger	Legacy motion/presence
60 GHz	up to ~7 GHz	sub-cm	~1-10 m (O2 absorption)	tiny	Indoor gesture, presence, vitals
77 GHz	up to 4 GHz	~3.75 cm	up to ~250 m	small	Automotive, outdoor robots, drones

Imaging radar and the 4D point cloud

Ordinary automotive radar returns a sparse list of detections: a handful of range-velocity-azimuth points per frame, enough for adaptive cruise control and blind-spot warning but too coarse for a self-driving perception stack to reason about shape. Imaging radar, often marketed as "4D radar," pushes angular resolution and antenna count high enough to produce a dense point cloud with elevation, closing part of the gap to LiDAR.

What makes it "4D" and "imaging"

The four dimensions are range, radial velocity, azimuth, and elevation. The imaging quality comes from a large MIMO virtual array, typically built by cascading several transceiver chips so the virtual array reaches 100 to 200 elements. That array delivers around 1-degree azimuth resolution and adds enough elevation channels to place points in a vertical plane, so the output is a genuine 3D point cloud with a velocity attached to every point. Vendors in this space include Arbe, Uhnder (which uses digitally coded MIMO rather than time-multiplexed chirps), Continental, ZF, and Mobileye's radar effort, alongside the merchant chipmakers.

What it buys and what it still cannot do

A 4D imaging radar gives you a point cloud dense enough to cluster into objects and estimate their extent, in weather and darkness, with per-point velocity that a LiDAR lacks. That combination is why 4D radar is being pushed as a lower-cost, all-weather complement or partial substitute for LiDAR on advanced driver assistance and some autonomy stacks. It still trails LiDAR badly on angular resolution (1 degree versus 0.1 degree), it has no color or texture, and its point cloud is noisier and more prone to multipath ghosts. It narrows the gap; it does not close it.

Indoor presence and vital-signs sensing

The same FMCW radar that tracks cars at 200 m also detects the sub-millimeter motion of a human chest at 1 m, and this indoor sensing role is a large and growing market for the identical silicon.

Presence and motion

A 60 GHz radar in a room detects a person from the tiny motions of breathing and fidgeting even when they are otherwise still, because the phase measurement is sensitive to sub-millimeter displacement (the same phase-of-Doppler physics from the velocity section). This makes radar a strong presence sensor where a passive-infrared (PIR) motion detector fails: PIR only fires on movement across its field and goes blind on a still person, while radar holds a lock on a seated, reading, or sleeping person. Applications include occupancy for lighting and HVAC, fall detection for elder care, and automotive child-presence detection (a regulatory requirement in several markets to prevent hot-car deaths), where the radar distinguishes a breathing infant in a rear seat from an empty car seat.

Vital signs

Push the phase sensitivity further and radar reads vital signs contactlessly. Breathing moves the chest wall by several millimeters at roughly 0.2 to 0.5 Hz; the heartbeat moves it by a fraction of a millimeter at roughly 1 to 2 Hz. A radar measuring chest-wall displacement phase, then band-pass filtering into respiration and cardiac bands, recovers both rates without touching the person. The signal is delicate: body motion swamps the tiny cardiac component, and separating heartbeat from the much larger breathing harmonics is the core signal-processing challenge. Done well it enables sleep monitoring, driver-drowsiness detection, and non-contact patient monitoring, and it is the same chip family used for perception, which is a large reason mmWave radar volumes and costs have moved in the robot builder's favor.

The signal-processing chain

A radar chip hands you raw ADC samples. Everything useful happens in the processing, and the chain is standardized enough to describe end to end.

1. Range FFT (fast time). Transform each chirp's beat signal. Output: a range profile per chirp, peaks at each target's range.
2. Doppler FFT (slow time). Transform across the chirps at each range bin. Output: the range-Doppler map, with velocity separated from range.
3. CFAR detection. Constant false-alarm rate detection slides a window across the range-Doppler map and declares a detection where a cell exceeds an adaptive threshold set from its neighbors' noise level. CFAR is what keeps the false-alarm rate constant as background clutter varies, and it is the make-or-break step: too aggressive and you miss weak targets, too lax and you drown in ghosts.
4. Angle estimation (DoA). For each detected range-Doppler cell, run the angle FFT (or a super-resolution method like MUSIC) across the virtual antennas to place the detection in azimuth and elevation.
5. Clustering. Group nearby detections that belong to one physical object (DBSCAN is the common choice), since a single car returns many detections across its extent.
6. Tracking. Feed clustered detections into a tracker, usually a Kalman filter, to maintain object identity, smooth position, and use the measured velocity to predict motion. This is where radar's direct velocity pays off, and it is covered in the sensor fusion and Kalman filtering guide.

The chain runs on the radar chip's onboard DSP or hardware accelerator for the FFTs and CFAR, then on a host processor for clustering, tracking, and fusion. The compute is modest next to LiDAR point-cloud processing, which is part of radar's appeal on power-constrained robots.

Rule of thumb: the sensor gets you the range-Doppler map; the CFAR threshold and the clustering get you objects. Most "the radar is noisy" complaints are a mistuned CFAR and no clustering, not a bad chip.

Radar vs LiDAR vs camera

The three exteroceptive sensors are complementary because their failure modes do not overlap. The table is the argument for fusing all three rather than betting on one.

Property	Radar (mmWave FMCW)	LiDAR	Camera
Measures	Range, radial velocity, coarse angle	Range, fine angle (3D geometry)	Angle, color, texture (2D)
Direct velocity	Yes (Doppler, per frame)	Only FMCW LiDAR	No (infer from frames)
Range resolution	~4 cm (4 GHz band)	mm to cm	N/A (no direct range)
Angular resolution	Coarse (1-15 deg)	Fine (~0.1 deg)	Fine (pixel-limited)
Dust / fog / rain / smoke	Works	Degrades badly	Fails
Darkness	Works	Works	Fails (needs light)
Direct sunlight / glare	Works	905 nm degrades	Degrades
Semantics (what is it)	Poor	Moderate	Excellent
Cost	Low	High (falling)	Very low
Moving parts	None	Often (spinning/MEMS)	None
Typical robot range	up to ~250 m	up to ~250 m	scene-dependent

The one-line summary: radar for velocity and all-weather range, LiDAR for fine geometry, camera for semantics. A self-driving stack runs all three precisely because rain blinds the LiDAR, glare blinds the camera, and neither event touches the radar. See the self-driving cars guide for how these fuse into a full autonomy stack, and the LiDAR guide for the optical side.

Limitations: resolution, multipath, clutter, ghosts

Radar's failure modes are specific, physical, and worth knowing before you trust a radar point cloud.

Angular resolution

Covered above and worth repeating: radar's lateral resolution is degrees, so nearby objects merge and small objects at range are hard to separate from their surroundings. This is intrinsic to the antenna aperture. A robot that needs to know a pedestrian is standing beside a pole, not fused with it, needs either imaging radar or a camera or LiDAR to disambiguate.

Multipath and ghost targets

A radar wave can reach a target by more than one path: directly, and by bouncing off the ground, a wall, or a guardrail. Each path has a different length, so one physical object produces several detections at different ranges, some of them ghosts that hover where no object exists. The classic case is a car under a bridge or beside a barrier, where the metal surfaces create a mirror image of the target at a phantom range. Multipath is the radar analog of a LiDAR's flying pixels, and it is the reason a raw radar point cloud looks untrustworthy until clustering and tracking reject the inconsistent ghosts.

Clutter

Clutter is the return from everything you did not want to detect: the ground, foliage, rain, walls, and railings. Ground clutter is especially bad for a low-mounted robot radar, because the beam illuminates the floor and every bump returns energy. The primary defense is Doppler: stationary clutter sits at zero relative velocity (after compensating for the robot's own motion), so filtering out the zero-Doppler bin removes most of it, which is one more reason radar's velocity measurement is load-bearing. Weather clutter (rain, snow) is harder because the particles move.

Interference and self-interference

As radars proliferate, one radar's chirp can land in another's receiver and raise the noise floor or plant false targets, the mutual-interference problem that automotive radar standards are still wrestling with. Coded and randomized chirp schemes (as in digitally modulated MIMO radar) reduce it. Separately, a strong nearby reflector can saturate the receiver and mask weaker targets behind it, the radar version of dynamic range limits.

War story: a security robot patrolling a metal-clad warehouse reported a wall of intermittent targets that no camera confirmed. The corrugated steel walls and the concrete floor were creating multipath ghosts and strong ground clutter, and the flat metal loading doors acted as mirrors that reflected the robot's own body back as a phantom fast-approaching object. The fix was three layers: zero-Doppler clutter rejection after ego-motion compensation, a tighter CFAR, and a tracker that required a detection to persist across frames before promoting it to an object. None of it was a hardware change. The radar was reporting real echoes of a reflective room, and the naive per-frame decode had trusted every one.

Applications and how to select

Where radar goes on robots

Self-driving cars and trucks carry radar as the all-weather velocity-and-range layer, one long-range forward unit plus corner radars for surround coverage, fused with cameras and LiDAR. Radar is the sensor that keeps adaptive cruise and automatic emergency braking working in the rain and fog that blind the others. The self-driving cars guide covers the full stack.

Drones use compact radar for altitude (a downward radar altimeter that works over water and vegetation where optical fails), obstacle avoidance in dust (agricultural and inspection drones flying through their own rotor wash and crop dust), and terrain following. See the drone hardware guide.

Mobile robots (AMR/AGV) add radar for obstacle detection in dusty warehouses, foundries, and outdoor yards where LiDAR chokes on airborne particulate, and for velocity-aware collision avoidance around moving forklifts and people. The mobile robots guide covers the navigation side.

Counter-drone (C-UAS) systems lean heavily on radar to detect and track small drones at range, a hard problem precisely because a small drone's radar cross section is tiny (0.01 m² or less) and its micro-Doppler signature (the rotor blades produce a distinctive Doppler spread) is one of the few reliable ways to distinguish a drone from a bird. The counter-drone guide goes deep on this.

Indoor and consumer robots use 60 GHz radar for presence, gesture, and safety around people, and the same sensing appears in smart-home and automotive-cabin roles.

How to select

Choose in this order, each criterion narrowing the field:

1. Band. Outdoor or automotive or any need for range and resolution: 77 GHz. Short-range indoor presence, gesture, or vitals: 60 GHz. Avoid 24 GHz for new designs.
2. Range and velocity ambiguity. Fix your maximum range (which sets the radar equation and transmit budget) and your maximum unambiguous velocity (which sets chirp timing). Confirm the max velocity covers the fastest target in your environment so you do not alias, the mistake in the AMR war story above.
3. Range resolution. Need to separate close objects in depth? You need bandwidth: 4 GHz at 77 GHz gives 3.75 cm.
4. Angular resolution and point-cloud density. Coarse detection (adaptive cruise, blind spot, presence) is fine with an ordinary 3Tx x 4Rx chip. Object shape and dense mapping need imaging (4D) radar with a cascaded array, at higher cost and compute.
5. Interface and processing. The TI AWR/IWR family and NXP and Infineon parts differ in onboard DSP, how much of the chain runs on-chip versus host, and driver maturity. A part that hands you clustered tracked objects over CAN or Ethernet saves months versus one that hands you raw ADC.
6. Integration and fusion. Budget for the fusion work. Radar's value multiplies when its velocity and all-weather range fuse with a camera's semantics and a LiDAR's geometry, and that fusion (time synchronization, extrinsic calibration, association) is where the engineering time goes. See the sensor fusion guide.

Rule of thumb: fix the band and the ambiguity limits first, because they are physics you cannot tune away later. Angular resolution decides ordinary versus imaging radar and drives most of the cost. Everything else is interface and integration, which is where you actually spend your time.

Frequently asked questions

Does radar work in fog, dust, and rain when LiDAR and cameras fail? Yes, and this is its main reason for existing on a robot. Millimeter waves are long compared with fog droplets, dust grains, and most rain, so they pass through with little scattering, while those same particles scatter light strongly and blind optical sensors. Heavy rain and snow do attenuate and clutter the radar somewhat, but radar degrades gently in weather that stops a LiDAR or camera cold.

How does radar measure velocity directly when a camera cannot? Radar is a coherent sensor, so it measures the Doppler shift of the echo, which is the target's radial velocity, from the phase change of the beat signal across successive chirps in one frame. A camera has to difference positions across frames to infer speed, which is noisy and lagged. Radar hands you velocity per target on a single frame with no tracking, and that is often the most useful quantity for collision avoidance.

Why is radar so bad at angular resolution? Angular resolution is set by the antenna aperture, roughly λ/(N·d) for N antennas spaced d apart. Fitting many antennas on a small chip is hard, so ordinary radar resolves 10-15 degrees, which merges nearby objects laterally. MIMO synthesizes a larger virtual array (Tx·Rx elements) and imaging radar cascades chips to reach about 1 degree, still coarse next to a LiDAR's 0.1 degree.

What is a radar cross section and why does it matter more than size? RCS measures how strongly a target reflects radio energy back to the sensor, in square meters, and it depends on shape, material, and orientation, with physical size only one factor among them. A flat metal plate facing you has a huge RCS and the same plate edge-on nearly vanishes; a small drone has a tiny RCS despite being visible to the eye. Because detection range scales with RCS, a range spec is meaningless without stating the target it assumes.

77 GHz, 60 GHz, or 24 GHz: which band should I use? 77 GHz for almost all robotics: it offers 4 GHz of bandwidth (fine range resolution), small antennas, and a mature cheap ecosystem. 60 GHz for short-range indoor presence, gesture, and vital-signs sensing, where oxygen absorption conveniently limits range and stops the radar seeing through walls. Avoid 24 GHz for new designs; it is narrowband and being phased out.

What is 4D or imaging radar and do I need it? 4D radar measures range, velocity, azimuth, and elevation and produces a dense point cloud, using a large MIMO virtual array (often cascaded chips) to reach about 1-degree resolution. You need it when object shape and dense all-weather mapping matter, such as on an autonomy stack using radar as a LiDAR complement. For adaptive cruise, blind-spot, or presence detection, an ordinary radar chip is enough and far cheaper.

Why does my radar report targets that are not there? Ghosts come from multipath (the wave reaches a target by several bounce paths and returns detections at phantom ranges) and from clutter (ground, walls, foliage). Real mitigations are ego-motion-compensated zero-Doppler filtering to kill stationary clutter, a well-tuned CFAR threshold, clustering, and a tracker that requires persistence before promoting a detection to an object. Most "noisy radar" complaints are a missing processing chain, not a bad sensor.

Can radar really detect breathing and heartbeat? Yes. The phase measurement is sensitive to sub-millimeter chest-wall motion, so a 60 GHz radar recovers respiration (several millimeters, ~0.2-0.5 Hz) and heartbeat (a fraction of a millimeter, ~1-2 Hz) by band-pass filtering the displacement signal. It is delicate because body motion swamps the tiny cardiac component, but it is the same silicon used for perception, which is one reason mmWave radar has become cheap.

How much compute does radar processing need compared with LiDAR? Considerably less. The core chain is a couple of FFTs and a CFAR detector, often handled by the radar chip's onboard DSP or accelerator, then modest clustering and tracking on the host. That light compute footprint is part of why radar suits power- and weight-constrained robots and why the raw data rate is far below a LiDAR point cloud.

Should I replace my LiDAR with radar? Rarely. Radar and LiDAR are complementary: radar gives velocity and all-weather range with coarse angle, LiDAR gives fine geometry that radar cannot match. Imaging radar narrows the gap and can substitute for LiDAR in cost- or weather-driven designs, but the strong systems fuse both plus a camera so that each covers the others' blind spots. Choose by which failure modes you must survive.