ADAS Sensors: Radar, Camera, Lidar and What They Cost to Build

ADAS is a collection of features - not one system - built on shared perception hardware. Cameras classify what an object is. Radar measures how fast it is closing, in rain and darkness where cameras struggle. Ultrasonic sensors handle the last five meters for parking. Lidar produces a dense 3D map for systems that need centimeter geometry. A domain controller fuses those inputs into a single model of the world and hands decisions to braking, steering and throttle actuators over the vehicle bus.

SAE J3016 defines six levels. Level 0 gives warnings only. Level 1 controls either speed or steering - adaptive cruise or lane centering, not both. Level 2 combines them but the driver remains fully responsible and must monitor continuously; almost everything marketed today as a driver-assist package is Level 2. Level 3 lets the driver disengage attention within a defined operational design domain, such as a mapped highway under a speed threshold, with a handover request. Levels 4 and 5 remove the driver inside, or beyond, that domain. Marketing language routinely blurs 2 and 3; the legal difference is who is liable when the system errs.

Functional safety - ISO 26262 ASIL-B to ASIL-D work products, hazard analysis, redundant sensing and fail-operational power.. SOTIF - ISO 21448 covers the hazards that occur even when nothing has failed, such as a misclassified object.. Validation mileage - millions of simulated kilometers plus targeted track scenarios with soft-target vehicles and pedestrian mannequins.. Calibration - every camera and radar must be aimed and calibrated at end of line, and again after a windshield replacement.. Environmental qualification - sensors must survive thermal shock, vibration, salt spray, stone impact and EMC testing.. Cybersecurity - ISO/SAE 21434 process obligations for anything on the vehicle bus.

Most companies entering this space are not building the domain controller - they are building brackets, sensor housings, wiring, calibration fixtures, aftermarket accessories or fleet-retrofit hardware that must not interfere with existing systems. That work still lives inside automotive discipline: IATF 16949 quality, PPAP submissions, capable tooling, and design records that survive an OEM audit. The practical entry path is a validated prototype, a documented DFMEA, and a manufacturing partner who has passed a customer-specific requirements audit before.

Three trends are reshaping the stack: 4D imaging radar that resolves elevation and starts to replace low-end lidar, centralized compute that collapses a dozen ECUs into one high-performance domain controller, and over-the-air updates that let behavior improve after the car is sold. For product teams, the practical consequence is that mechanical and electrical hardware must be specified for a software feature set that will keep changing - so thermal headroom, connector count and compute margin are design requirements, not afterthoughts.