Frequency is usually the first parameter a buyer quotes, and the least suitable one to order against. Two 24 GHz units with different antennas and signal chains can behave very differently; equally, treating 60 GHz as automatically "more advanced" is a common and expensive mistake. This note is about the order in which engineering decisions should be made.
What the band actually constrains
Wavelength shortens as frequency rises: roughly 12.5 mm at 24 GHz, 5 mm at 60 GHz and 3.9 mm at 77/79 GHz. Two consequences follow.
- Higher frequencies allow narrower beams and better angular resolution within the same physical aperture, and the antenna can be smaller.
- Wider contiguous bandwidth is generally available at higher bands. Since range resolution is inversely proportional to bandwidth, closely spaced targets are easier to separate at short range.
The trade-offs are equally concrete: attenuation from rain, fog, dust and vegetation increases with frequency, as do RF front-end and substrate costs. Regulations also differ by region. Export platforms must be checked against the target market's band allocations and power limits at design stage, not after the prototype is built.
Obstacle avoidance and altitude hold are different missions
This is the most frequent source of confusion in enquiries.
Obstacle avoidance depends on field of view, angular resolution, multi-target tracking and update rate. The hard part is separating several reflectors and deciding which one is a threat. Altitude hold depends on vertical range stability, ground-clutter rejection and continuity at low height — where a strong return is always present.
One radar can serve both, but the acceptance criteria must be written separately: miss rate and false-alarm rate for avoidance; range jitter near ground and reacquisition time after dropout for altitude hold. A single "maximum range" figure validates neither.
A checklist ready to paste into an RFQ
- Target characteristics: material, approximate radar cross section, typical relative velocity.
- Range and field of view: minimum and maximum operating distance, horizontal and vertical FOV, need for zoned alerts.
- Dynamic performance: update rate, track count, data latency, interface and protocol to the flight controller.
- Environmental limits: temperature range, vibration and shock, rain/fog/dust, nearby obstructions and metal reflections at the mounting position.
- Coexistence: mutual interference when several units operate in the same area, and the vendor's mitigation approach.
- Power and mechanical: supply voltage and ripple tolerance, connector type, mounting pattern, thermal path.
- Compliance: band allocation, emission limits and certification in the destination market.
- Acceptance method: test site, target objects, pass/fail criteria and thresholds, plus measured test records.
On vague claims such as "anti-interference"
A single line in a datasheet carries no engineering meaning. What matters is: under what interference power, at what distance, on which frequencies, and by what criterion the unit is still considered usable. Ask for the test conditions, not the adjective.
Likewise, no single module can guarantee lock retention under broadband suppression. A realistic design goal is to raise the threshold at which degradation begins and to make that degradation observable, so the flight controller can execute a defined fallback instead of silently consuming a wrong position.
Conclusion
Define the mission and acceptance criteria first, then field of view, range and update rate, and only then the band and the part number. Frequency is an outcome of those constraints, not a starting point. For export programmes, regulatory verification belongs in the concept phase.