An EMC pre-compliance bench should be scoped as a repeatable engineering workflow, not as a single instrument purchase. The purpose is to find problems early, compare design revisions, document margin, and reduce surprises before a formal compliance lab booking. A good bench defines the LISN, spectrum analyzer, RF cabling, grounding practice, limit lines, measurement procedure, and reporting format before the first DUT is connected.
Start with the measurement type
For conducted-emissions screening, the first decision is the power interface. Document the DUT input voltage, current, phase configuration, line frequency, connector type, protective earth arrangement, and whether the product is AC powered, DC powered, or powered through an adapter. That information determines the LISN rating and the practical safety setup around it.
The LISN should be selected for the expected current and voltage, but the quote should also define how the unused port is terminated, how the RF output is protected, how the DUT is grounded, and where the measurement plane sits. If the bench will be used by several teams, include a simple wiring diagram and a checklist for setup reset. Repeatability often depends on these details more than on the analyzer model.
Match the analyzer to the workflow
The spectrum analyzer should be chosen around frequency coverage, noise floor, detector support, resolution bandwidth control, sweep speed, marker workflow, preamp/attenuation behavior, and export capability. A bench used only for quick engineering scans can be manual. A bench used to compare revisions across a design program usually needs saved settings, repeatable sweeps, screenshots, CSV export, and a report template.
For XGY Tek users, a common pairing is the EM5040 LISN series for conducted-emissions workflows and YSA spectrum analyzers for RF measurement and pre-compliance review. When scoping the bench, state whether the target is a manual spot-check station, an automated sweep station, or a broader validation rack that also includes power supplies, electronic loads, switching, and environmental sensors.
Control cables, grounding, and repeatability
Pre-compliance results can move if the setup moves. The RF cable, LISN placement, DUT cable routing, ground bonding, table surface, and nearby equipment should be treated as part of the test condition. If engineers are comparing hardware revisions, define how the DUT is placed, how cables are bundled or separated, which accessories are connected, and whether the product operates in idle, transmit, charge, load, or worst-case mode.
It is also worth documenting the analyzer settings used for each screen: start and stop frequency, RBW, VBW, detector mode, sweep time, attenuation, preamp state, trace mode, and limit line. Those settings should appear in the report. Without them, a later team may not be able to reproduce a result that looked convincing during the first debug session.
Reporting and acceptance
Pre-compliance should not be presented as a certified pass/fail result unless the test was performed by an appropriate accredited process. Its value is engineering evidence: where the emission peaks are, how much margin appears under a chosen limit line, what changed after a layout or filter update, and which mode creates the worst case. A practical report should include the DUT identifier, revision, setup diagram, analyzer settings, LISN model, cable notes, ambient conditions if relevant, screenshots, raw exported traces, and engineering comments.
For teams preparing a quotation, define whether the bench must create PDF reports, CSV files, screenshots, database rows, or a repeatable operator workflow. If the bench is part of a production or quality process, include calibration-document expectations and how instrument serial numbers should be captured.
Pre-compliance acceptance matrix
The bench should be accepted only when a second engineer can rebuild the setup and obtain comparable data. That means acceptance is not a clean screenshot; it is a documented measurement condition.
| Acceptance item | Evidence to capture | Reject or rework if |
|---|---|---|
| LISN and DUT power path | DUT voltage/current/phase, LISN rating, unused-port termination, protective earth arrangement, and RF-output protection | The LISN is selected only by current rating, or termination and protection are not documented |
| Physical setup repeatability | DUT placement, cable routing, table or ground plane note, bond points, accessory state, and operating mode | A design revision is compared after the cable layout or DUT mode changed without record |
| Analyzer configuration | Start/stop frequency, RBW, VBW, detector, sweep time, attenuation, preamp, trace mode, limit line, and correction factors | The report contains only a screenshot or peak marker without measurement settings |
| Ambient and baseline review | Ambient scan, power-off baseline when useful, known local transmitters or switching equipment, and background peaks | A suspicious peak is assigned to the DUT without baseline evidence or repeat capture |
| Report traceability | DUT ID, revision, operator, date/time, instrument IDs, calibration status, screenshots, CSV trace, and engineering comment | The data cannot identify the instrument, setup, raw trace, or design revision tested |
Standards and instrument traceability
CISPR 16 context matters because conducted-emissions screening is highly setup-dependent. LISN selection, receiver protection, termination, detector choice, RBW/VBW settings, and cable routing can change the result enough to mislead an engineering team. XGY’s EM5040 family is a V-type LISN series for conducted disturbance voltage measurement, including receiver-protection and CM/DM workflow options; that should be matched to DUT power, current, and measurement purpose before the analyzer is selected.
Record the LISN model boundary numerically. EM5040E/A/B cover 9 kHz to 30 MHz conducted-emissions workflows with 0 to 264 VAC, 0 to 375 VDC, 16 A current rating, and 50 ohm BNC output; EM5040A adds a 10 dB limiter with a 130 dBuV threshold and optional 9 kHz / 150 kHz high-pass filtering. EM5040C shifts the boundary to 100 kHz to 200 MHz, 0 to 250 VAC, 0 to 600 VDC, 100 A rated current, 500 A short-time current, and 50 ohm N output. Those limits should be visible in the quote request because they decide whether the bench protects the analyzer and represents the DUT power path correctly.
The analyzer side should be treated the same way. If a YSA real-time spectrum analyzer is used for pre-compliance debug, the report should show the analyzer settings that produced the trace, not just the screenshot. For a quality-facing workflow, ISO/IEC 17025 and calibration references are the reminder that a trace without instrument identity, calibration status, and setup conditions is weak evidence even if the peak marker looks precise.
Reject a pre-compliance result when the report cannot separate DUT emissions from setup artifacts. Common failure modes include missing ambient scans, undocumented LISN termination, changed cable routing between design revisions, unrecorded detector or RBW settings, and no exported trace data. Those gaps do not make the instrument wrong; they make the evidence too weak to support a design decision.
Engineering FAQ
Can a pre-compliance bench replace a certified EMC lab?
No. A pre-compliance bench is an engineering debug and design-comparison tool, not a substitute for formal compliance testing. Its value is repeatable evidence: which mode produced the emission, which design change reduced it, what margin was observed under the chosen limit line, and what setup produced the trace.
What does the LISN contribute to a conducted-emissions setup?
The LISN provides a defined impedance and measurement point between the DUT power input and the analyzer path. For a useful setup, the buyer still has to define voltage, current, phase, grounding, unused-port termination, RF-output protection, and the physical cable layout around the DUT.
Which analyzer settings must be recorded in the report?
Record start and stop frequency, RBW, VBW, detector mode, sweep time, attenuation, preamp state, trace mode, limit line, antenna or LISN path, cable notes, and any correction factors. A screenshot without these settings is weak evidence because another engineer cannot reproduce the measurement.
When should a pre-compliance setup become automated?
Automation is justified when multiple revisions, operators, operating modes, or product variants must be compared under the same conditions. If the team only needs occasional debug scans, a manual setup with a disciplined checklist may be sufficient; if the data supports release gates, automated settings recall and report generation are usually worth scoping.
EMC bench quote package
Send the DUT power requirements, target measurement type, current and voltage range, target standards or internal limits, frequency range, analyzer settings if already known, report format, and whether the bench should remain manual or become automated. If the product has several operating modes, include the modes that should be screened and the load or communication conditions required to reproduce them.
A credible EMC pre-compliance setup gives engineers a stable way to find and compare problems. It is not a replacement for formal compliance testing, but it can make that testing less dramatic by turning unknown emissions into measured, documented engineering work.