The Question No Road Test Can Answer
At the Rohde & Schwarz booth at the EMC exhibition in Cologne this January, the left half of the demo station carried a title that reframes the entire automotive radar testing problem:
AUTOMOTIVE RADAR TESTING UNDER EMC CONDITIONS.
Not "automotive radar testing." Not "EMC testing of radar." The combination — radar functional testing, conducted simultaneously with electromagnetic interference conditions — is a fundamentally different measurement challenge from either discipline alone.
The setup on the bench made the problem concrete: a 77 GHz automotive radar sensor on a tripod, connected via orange fiber optic cable to a radar target simulator, with an EMC test environment layered on top. The screen above showed not a spectrum trace or a compliance limit comparison — it showed a vehicle instrument cluster, with a speedometer reading the target velocity the radar was detecting.
The question being answered was not "does this radar emit within CISPR limits?" It was: does this radar still work correctly when it is surrounded by electromagnetic interference?
The Radar Target Simulator: Creating a Controlled World for the Sensor
The white instrument unit on the right side of the bench is a Rohde & Schwarz radar target simulator. The product card on the left screen describes its key capabilities:
→ Dynamic & precise target simulation — the instrument generates synthetic radar return signals that the DUT sensor receives as if they came from real objects
→ Flexible target distances and velocities (Doppler) — simulated targets can be placed at any range and moving at any velocity, with the correct Doppler frequency shift applied
→ Various types of road users (RCS) — radar cross-section values can be configured to represent pedestrians, cyclists, cars, or trucks
→ Fully compatible with MIMO sensors — the system handles the multiple transmit/receive channel architecture of modern automotive radar
The orange fiber optic cable connecting the red radar sensor to the target simulator is the key architectural detail. The fiber carries the radar signal between the antenna and the simulator electronics — isolating the measurement from cable-conducted interference while preserving the RF signal integrity at 77 GHz frequencies. This allows the target simulator to inject precisely controlled synthetic radar returns into the sensor's receive path while the EMC test environment applies interference conditions from the outside.
The result is a controlled, repeatable test environment: the sensor under test always "sees" exactly the targets the simulator defines, regardless of the ambient RF environment. The question becomes whether the sensor's detection algorithm correctly processes those defined targets in the presence of interference — or whether the interference corrupts the detection.
The Software Display: A Speedometer as a Functional Test Result
The right screen above the bench was showing the EMC Test Automation Software interface — and the choice of visualization is deliberately accessible: a vehicle instrument cluster with a speedometer and tachometer, displaying the velocity the radar was reporting in real time.
This is not a user interface design decision. It is a measurement philosophy. The speedometer is showing the output of the radar's detection algorithm — the velocity value it calculated from the Doppler-shifted return from the simulated target. If the radar is performing correctly under interference, the speedometer reads the velocity the simulator defined. If interference degrades the sensor's performance, the reading diverges, fluctuates, or drops out.
The "Demo License, for evaluation only" label visible on the screen confirms this is a live software instance running actual measurement data — not a static mockup.
For an automotive ECU engineer or a safety validation team, this visualization is immediately meaningful: they are not reading a spectrum trace and inferring functional impact. They are watching the sensor's functional output directly, in the units that matter for the application — km/h, at a defined target distance, under defined interference conditions.
Why "Under EMC Conditions" Changes Everything
Standard automotive radar development follows a two-track process. Radar engineers validate that the sensor detects targets correctly — range accuracy, velocity accuracy, angular resolution, false alarm rate. EMC engineers validate that the sensor's emissions comply with automotive standards (CISPR 25, UNECE R10) and that it survives immunity test levels (ISO 11452, IEC 61000-4 series).
These two validation tracks traditionally run separately. The radar performance tests happen in a controlled RF environment — anechoic chamber or shielded room — specifically designed to exclude interference. The immunity tests happen with a calibrated interference field applied, but without evaluating whether the radar is actually detecting targets correctly during the test.
The gap between these two tracks is where real-world failure modes live.
A radar sensor might pass both validations independently:
→ Clean radar performance in an interference-free environment ✓
→ Survives the immunity test field levels without damage ✓
And still fail functionally in a real-world electromagnetic environment — because the immunity test verified survival, not performance. The sensor may be alive and generating outputs, but those outputs may be corrupted by the interference in ways that cause false detections, missed targets, or incorrect velocity readings.
In an ADAS system where the radar output feeds a lane-change assist or automatic emergency braking algorithm, a corrupted velocity reading is not a compliance failure. It is a safety failure.
The R&S demo was showing the measurement approach that closes this gap: test radar functional performance and EMC conditions simultaneously, in a controlled environment where both the interference scenario and the radar target scenario are precisely defined and repeatable.
The Right Side of the Banner: EMC Test Automation Software
The right half of the booth banner — EMC TEST AUTOMATION SOFTWARE — represents the operational infrastructure that makes this kind of combined testing feasible at scale.
A test that simultaneously controls a radar target simulator (target distance, velocity, RCS), an interference generator (frequency, level, modulation), a data acquisition system (radar output logging), and a pass/fail evaluation engine cannot be run manually with acceptable repeatability. The number of test combinations — interference type × interference level × frequency × target scenario — grows rapidly into the hundreds or thousands of configurations required for a complete validation matrix.
Automation software orchestrates this matrix: executing each configuration in sequence, applying the correct stimulus conditions, logging the radar's functional response, evaluating against defined acceptance criteria, and generating the test report that feeds into the vehicle program's safety documentation. The same software that controls the compliance test sequences (as seen in the Article 026 R&S + ZES Zimmer booth) is here extended to cover the combined radar-functional + EMC-immunity test domain.
For an automotive OEM or Tier 1 supplier running a complete ADAS radar validation program, the test automation layer is what compresses a months-long manual validation effort into a timeline that fits within a vehicle development program's gate structure.
The Broader Context: Why This Test Category Is Growing
Automotive radar is no longer a premium feature. It is standard equipment on new vehicles across the European market — legally mandated for new model types under UNECE regulations requiring Autonomous Emergency Braking (AEB) systems. Every new vehicle architecture must validate radar performance not just in ideal conditions, but in the electromagnetic environments it will actually encounter.
Those environments are getting more complex, not less:
→ More vehicles on the road with 77 GHz radar systems means more mutual interference between sensors
→ 5G infrastructure deployment in the 26 GHz and potentially higher bands creates new interference sources in the radar's operating environment
→ High-voltage powertrains in EVs and hybrids generate broadband emissions that the radar receiver must reject
→ V2X communication systems operating in adjacent bands add yet another interference source layer
A radar sensor validated only in a clean RF environment is validated for a world that no longer exists on public roads. Testing under realistic EMC conditions — with the target simulator providing the controlled "truth" the sensor should be detecting — is the engineering approach that produces results with actual predictive validity for real-world performance.
The R&S demo in Cologne was showing that the test infrastructure for this approach now exists as a commercial, automated, measurement-grade system. That is a meaningful development for automotive radar development workflows.
Instruments observed: Rohde & Schwarz Automotive Radar Target Simulator · 77 GHz automotive radar sensor (DUT) · fiber optic signal connection · EMC Test Automation Software with vehicle instrument cluster visualization · combined automotive radar functional + EMC immunity test system
All photos: Thomas · @SignalByThomas