Why pre-compliance scans can differ from final testing

A prototype can look comfortably below an emissions limit on the development bench, then fail final testing without any change to the electronics. The missing variable is often the measurement process itself.

Understanding pre-compliance vs compliance testing means understanding what each result can legitimately tell you. Early scans are valuable engineering tools, but they are not automatically equivalent to measurements made using the prescribed site, instrumentation, detectors, configuration and test procedure.

Pre-compliance and final testing answer different questions

A pre-compliance scan is usually designed to find problems while they are still economical to fix. It may identify dominant frequencies, cable-related resonances, noisy operating states, inadequate shielding or filters with insufficient attenuation. The setup is often deliberately accessible so that engineers can change components, reroute cables and repeat measurements quickly.

Final compliance testing asks a narrower and more formal question: does the product, in the defined configuration and operating mode, satisfy the applicable requirements when assessed using the required method? That method may be set by a product or product-family standard which, in turn, references CISPR emissions requirements or IEC basic immunity test methods.

The two activities support each other, but they are not interchangeable. A useful pre-compliance result reduces technical uncertainty. It does not by itself demonstrate conformity unless the applied route, method, evidence and documentation are suitable for that purpose.

Setup difference changes the measured coupling path

EMC measurements are highly sensitive to geometry. Cable length, cable height, equipment spacing, grounding, support material and the position of auxiliary equipment can alter common-mode current distribution and antenna efficiency. A setup difference that appears mechanically insignificant may shift a resonance or change the measured amplitude by several decibels.

Cable routing is part of the EUT

At radiated-emissions frequencies, an attached cable can become a more effective radiator than the enclosure. Coiling excess cable during a bench scan may suppress radiation by reducing its effective length, while spreading the same cable according to the prescribed final configuration can expose a strong common-mode emission. The reverse can also happen if an informal cable arrangement happens to sit at a resonant length.

Conducted emissions are equally configuration-dependent. A line impedance stabilisation network, or LISN, provides a defined RF impedance and measurement port for relevant power-port disturbance-voltage measurements. Connecting the equipment directly to an arbitrary mains extension and probing the lead does not reproduce that impedance. The resulting trace may help with diagnosis, but it cannot be compared confidently with a LISN-based result.

Ground planes and bonding affect current return paths

Conductive reference planes, equipment bonding and insulation distances must follow the applicable method. An unnecessarily long grounding strap adds inductance. At higher frequencies, that can redirect return current through signal cables or test instrumentation, making the measurement unrepresentative.

Products intended to be bonded in service should not automatically be tested floating, nor should isolated equipment be bonded merely to stabilise a noisy development setup. Either choice can produce an attractive but misleading result. The intended installation, product standard and test plan must determine the configuration.

The environment is part of the measurement system

A normal engineering workshop contains broadcast signals, mobile communications, switch-mode power supplies, network equipment, LED lighting and nearby machinery. These ambient signals can mask EUT emissions or be mistaken for them. Switching the EUT off while retaining the same receiver and antenna settings is a simple diagnostic step, but ambient subtraction is not a universal cure because both the ambient environment and the EUT emission may vary with time.

Formal radiated-emissions measurements use a site and procedure appropriate to the applicable requirement. Site characteristics, antenna distance, antenna height where required, polarisation, turntable position and measurement geometry are controlled. A close-proximity antenna scan over a PCB is useful for locating a source, but field strength measured in that near-field region cannot be treated as equivalent to a prescribed far-field or defined-distance result in dBµV/m.

Reflections matter too. A bench scan performed beside metal racking can produce constructive or destructive interference. Moving the antenna by a small distance may then change the indicated level dramatically. That instability is a warning that the environment, rather than the EUT alone, is controlling the result.

Receiver settings and detector choice can change the verdict

A spectrum analyser in peak mode is widely used for fast pre-scans. It provides rapid frequency coverage and is conservative in many situations, but only when its resolution bandwidth, video processing, sweep behaviour, attenuation and preamplification are suitable. A fast sweep can miss intermittent disturbances or under-measure signals when the analyser does not provide enough dwell or settling time.

Final emissions measurements may require CISPR receiver characteristics and specified detectors such as peak, quasi-peak or average, depending on the standard, port and frequency range. Quasi-peak detection weights disturbance repetition behaviour. Average detection applies different processing. Neither can be recreated reliably by simply reading a peak trace and subtracting an assumed margin.

Resolution bandwidth must also match the applicable measurement requirement. For example, 9 kHz is commonly associated with CISPR conducted-emissions measurements over relevant portions of the 150 kHz to 30 MHz range, while 120 kHz is commonly used for specified radiated-emissions measurements above 30 MHz. These are not universal settings. The current product standard, frequency range and referenced test method must be checked before configuring the receiver.

Uncertainty and traceability set the confidence level

Every EMC measurement contains uncertainty. Antenna factors, cable loss, LISN impedance, receiver response, site imperfections, positioning tolerances and repeatability all contribute. A pre-compliance scan may use calibrated equipment while still carrying greater overall uncertainty because the site and setup are less tightly controlled.

A margin of 1 or 2 dB on an informal scan should not be treated as evidence that a product will pass final testing. Even a larger margin requires judgement if the setup differs materially, ambient noise is high or the emission is intermittent. Margin decisions should consider the complete measurement chain rather than a single displayed trace.

EMC Hire uses test equipment with calibration traceable through an appropriate ISO/IEC 17025 accredited calibration provider. The accreditation applies to the relevant calibration laboratory or activity, not to the physical instrument. Suitable traceable calibration supports repeatability, confidence in recorded data and better comparison between development measurements and later formal testing. UKAS provides further information on the UK accreditation framework.

Immunity pre-compliance has similar limitations

The same distinction applies to immunity testing. A quick ESD investigation can expose a weak user interface or reset path, but results depend on discharge tip, return cable placement, coupling planes, discharge points, polarity and environmental conditions. Testing random enclosure points with an ESD simulator is not equivalent to applying IEC 61000-4-2 through the product standard that defines the required level and performance criteria.

Conducted RF immunity under IEC 61000-4-6 generally uses coupling and decoupling arrangements appropriate to the port, such as CDNs where specified. A BCI probe belongs to applicable bulk current injection methods used in certain automotive, military, aerospace or product-specific procedures. Substituting one method for another changes the injected quantity and coupling mechanism, so the results cannot be assumed equivalent.

Likewise, a local RF source waved near a product may reveal susceptibility, but it does not establish a calibrated radiated electric field in V/m. It is a debugging technique, not a substitute for a defined radiated-immunity setup.

Typical scenario

Consider an illustrative industrial controller with an external DC supply, Ethernet connection and two long sensor cables. The development team performs a radiated pre-scan using a spectrum analyser and antenna in a workshop. One narrowband emission sits 5 dB below the anticipated limit, so the design is released for final testing.

At the test facility, the prescribed cable layout increases common-mode radiation from a sensor cable. The antenna is positioned at the defined test distance, both polarisations are investigated, the EUT is rotated, and the highest emission is measured using the required detector. The earlier 5 dB margin disappears.

The problem was not necessarily a faulty pre-scan. It was an overconfident interpretation. A better investigation would have varied cable position and termination, exercised the highest-activity operating mode, checked antenna polarisation and preserved enough margin for setup and site differences. Current-probe measurements on the sensor cable could also have identified the dominant coupling path before final testing.

EMC Hire can support this work through EMC pre-compliance testing, suitable equipment hire, accessible test facilities and on-site investigation. The aim is to obtain calibrated engineering data early enough to debug the product, then move into formal compliance testing with a controlled configuration and a clearer evidence trail.

Turning a pre-scan into useful engineering evidence

Repeatability is more valuable than a visually clean trace. Record the EUT hardware and firmware revision, operating mode, peripheral equipment, cable type, cable position, power source, grounding arrangement, antenna details, distance and instrument settings. Photographs should show the full setup rather than only the instrument screen.

Stress the design deliberately. Test modes should exercise clocks, processors, displays, motors, radios and communication ports in combinations that represent foreseeable worst-case operation. An idle product may pass easily while its highest data-rate or maximum-load condition fails.

Use investigation methods for diagnosis, then return to a representative configuration for the decision scan. Near-field probes, current probes and temporary ferrites can isolate mechanisms, but a ferrite added only to identify a cable path is not a production mitigation. If the final design depends on it, its material, geometry, placement and assembly control must be specified.

Teams preparing for CE or UKCA activities should also distinguish testing from the wider conformity process. The manufacturer or responsible economic operator remains responsible for identifying applicable legislation, standards, conformity assessment routes and documentation. EMC evidence may support the technical file, EMC risk assessment, mitigation records and Declaration of Conformity, but testing alone does not complete every obligation. EMC Hire provides practical support for CE marking assessment and commercial CE marking and EMC testing where appropriate.

When to Hire EMC Equipment

Hiring is often technically and financially sensible when a project needs a specific LISN, receiver, antenna, current probe, CDN, ESD simulator or other test item for a defined investigation window. It avoids committing capital to equipment that may not suit the next product family or frequency range.

Short-term access also covers project peaks without creating long-term maintenance, storage, servicing and calibration obligations. This is particularly useful when several prototypes reach verification at once or when an intermittent fault requires equipment to remain on site for repeated testing.

Selection must begin with the applicable method, port, frequency range and required accessories. Receiver dynamic range, transducer factors, power handling and connector compatibility can determine whether a proposed setup is usable. EMC Hire can help identify an appropriate configuration through its EMC equipment selection guides and direct engineering support, reducing the risk of hiring or buying an instrument that cannot produce meaningful data.

Common EMC Testing Mistakes to Avoid

Comparing traces from different configurations

If cable routing, bonding or operating mode changes between scans, the traces do not represent a controlled before-and-after comparison. The team may credit a filter change for an improvement actually caused by a moved cable.

Using the wrong detector or bandwidth

Peak, quasi-peak and average results are not interchangeable. Incorrect receiver bandwidth or an excessively fast sweep can under-measure narrow, intermittent or pulse-like disturbances, creating false confidence.

Ignoring ambient signals

A workshop signal mistaken for an EUT emission wastes debugging time. An ambient that masks an EUT emission is more dangerous because the product may appear quiet until it reaches a controlled site.

Treating near-field probing as a limit measurement

Near-field probes locate sources and coupling paths. Their output is strongly affected by probe orientation, spacing and field type, so it should not be compared directly with a radiated limit in dBµV/m.

Leaving the test mode undocumented

A result without firmware revision, operating state and accessory configuration cannot be reproduced reliably. That weakens root-cause analysis and produces an unsuitable compliance evidence trail.

Assuming a generic method defines product requirements

IEC 61000-4-x documents are basic immunity test methods. Product and product-family standards commonly define applicability, levels, performance criteria and configuration. Applying a method without those product requirements can produce a technically neat but irrelevant test.

Frequently Asked Questions (FAQs)

How much margin should a pre-compliance scan show?

There is no universal safe margin. The answer depends on site quality, setup fidelity, instrumentation, ambient conditions, product variability and measurement uncertainty. A poorly controlled scan may require substantially more engineering margin than a representative facility measurement.

Can a spectrum analyser replace an EMI receiver?

It can be effective for development scans if its frequency coverage, dynamic range, bandwidths and detector functions suit the task. Final measurements must use equipment and functions meeting the applicable method. Instrument specifications and detector implementation need to be checked rather than inferred from the display labels.

Why does moving one cable alter radiated emissions?

The movement changes current distribution, coupling to the reference plane and the cable's effectiveness as an antenna. It can also alter phase relationships between radiation from the enclosure and attached leads.

Can calibrated equipment make a workshop scan compliant?

No. Calibration addresses specified characteristics of the measurement equipment. It does not correct an unsuitable site, uncontrolled geometry, wrong detector, incorrect configuration or non-representative operating mode.

Can pre-compliance data support self-certification?

Calibrated, well-documented engineering data may support a technical file and self-certification process where that route is legally and technically appropriate. The manufacturer must confirm the applicable legislation, current standards, limits, test levels, configuration and documentation requirements. Pre-compliance data does not automatically prove compliance.

When should formal testing be booked?

Book once the representative hardware, firmware, cables, power supplies and operating modes are sufficiently stable. Earlier facility work can still be worthwhile as a debugging exercise, but it should be identified as pre-compliance rather than treated as final evidence.

Plan the comparison before making the measurement

Useful pre-compliance work is not defined by how closely the setup resembles a finished laboratory photograph. It is defined by whether the team understands each deviation, controls the variables and interprets the resulting uncertainty honestly.

For help selecting hire equipment, arranging on-site testing, planning pre-compliance work or discussing formal compliance testing, contact the EMC Hire engineering team on +44 (0)1462 817111 or email sales@emchire.co.uk. The team can also discuss booking space at the EMC Hire test facility and building a test approach around the applicable product requirements.