When a cellular + Wi-Fi IoT gateway fails EMC late in the programme, it rarely fails because the lab is “too strict”. It fails because the product was never exercised the way EN 301 489 expects: the right radio modes, the right port configurations, the right operating conditions, and the right performance monitoring. A solid pre-compliance test plan is how RF compliance managers turn EMC from a calendar risk into an engineering task with measurable progress.
This post sets out a practical pre-compliance approach for ETSI EN 301 489 aimed at multi-radio gateways (LTE/5G, Wi‑Fi 5/6/6E, Bluetooth, GNSS, SRD). It’s written from the perspective of teams who need confidence before they spend money on a full notified lab campaign—and who want fewer surprises when they do.
1) Start by mapping your product to the correct EN 301 489 parts
EN 301 489 is a series: Part 1 contains the common EMC requirements, and the relevant “radio part” adds technology-specific conditions and performance assessment. For a typical gateway you’ll commonly see:
- EN 301 489-1 (Common technical requirements). The currently used edition is V2.2.3 (2019-11).
- EN 301 489-17 for broadband/wideband data transmission systems (Wi‑Fi / WLAN, and related wideband technologies). ETSI has been evolving this part—recent drafts (e.g. V3.2.5, 2022-08) show where immunity testing expectations are heading, including broader radiated immunity coverage.
- EN 301 489-52 for 5G NR user equipment. The published edition V1.3.1 (2019-11) is commonly referenced for NR EMC conditions.
- EN 301 489-3 for Short Range Devices (SRD). The more recent published version is V2.3.2 (2023-01), which matters if your gateway includes sub-GHz radios, NFC, or other SRD functions in-scope.
Pre-compliance tip: don’t stop at the radio headline. List every intentional transmitter and every receiver path that affects essential performance (cellular, Wi‑Fi, GNSS, BLE, SRD). Then decide what “pass/fail” means for each during immunity (throughput, BLER/PER, disconnection, GPS fix loss, etc.).
2) Build an EN 301 489 pre-compliance matrix (phenomena × ports × modes)
Most delays come from gaps: a port that wasn’t tested, or a mode that wasn’t monitored. Create a matrix that includes:
- Ports/cables: AC mains, DC input, Ethernet (screened/un-screened), USB, UART/service ports, antenna ports (conducted where applicable), HDMI/display (if any), IO cables, and any long harnesses.
- EMC phenomena: radiated emissions, conducted emissions (mains/DC/telecom), radiated immunity, ESD, EFT/burst, surge, conducted RF immunity, magnetic field immunity where applicable, voltage dips/interruptions if powered from AC.
- Operating modes: worst-case TX, RX sensitivity mode, idle/camped mode, maximum data throughput (UL/DL), MIMO active, Wi‑Fi 80/160 MHz where supported, Wi‑Fi 6E 6 GHz mode if present, simultaneous radios (cellular + Wi‑Fi + BLE), and “customer realistic” mode.
The matrix becomes your schedule and your evidence pack. For each cell, define: test setup, monitoring method, pass criteria, and the “knobs” you will use to provoke worst case (TX duty cycle, channel, bandwidth, power, aggregation, traffic model).
Industry insight #1: radiated immunity expectations are widening
Even if your formal test plan references today’s harmonised list, it’s sensible to pre-empt where the series is moving. Recent EN 301 489-17 draft evolution points to wider frequency coverage for radiated immunity (beyond the historically common 1 GHz breakpoints), which matters for modern gateways packed with high-speed clocks and wideband radios. If you only ever pre-test up to 1 GHz, you’re leaving risk on the table.
3) Define “essential performance” like an engineer, not a lawyer
EN 301 489 compliance depends on performance during immunity. For gateways, the fastest way to arguments (and re-testing) is a vague definition of what constitutes acceptable degradation. In pre-compliance you should lock this down with the product team and, ideally, with the test house you intend to use later.
Examples that work well for cellular + Wi‑Fi gateways:
- Cellular: maintain RRC connection; no unintended detach; BLER/PER below an agreed threshold; data session sustained (e.g. UDP/TCP throughput above X); recovery within Y seconds after disturbance.
- Wi‑Fi: association maintained; throughput above X; no reboot; MLO (Wi‑Fi 7) link stability if applicable; acceptable retry rate.
- GNSS (if present): no permanent loss of fix; time-to-first-fix recovery; acceptable C/N0 drop for a defined period.
- System: no watchdog resets, no corruption of flash, no latch-up requiring power cycle.
Pre-compliance tip: instrument it. Log PHY stats, disconnect events, CPU resets, and supply rail disturbances. A pass with no data is not a pass—it’s a missed opportunity to learn.
4) Plan the actual tests: what to run in-house before you book the chamber
You don’t need a full accredited lab to de-risk EN 301 489. You do need disciplined setups that correlate. A sensible staged approach:
Stage A — Bench sanity checks (1–3 days)
- Power integrity under RF stress: run worst-case TX while probing DC rails for droop and switching noise coupling into RF front ends.
- Cable/common-mode hygiene: clamp-on current probe checks on Ethernet/USB/DC cables to spot unintended common-mode emissions early.
- ESD “first look”: targeted contact/air discharges around user-accessible points (USB shield, SIM door, RJ45 shell, buttons). You’re hunting for resets and latch conditions, not collecting a certificate.
Stage B — Pre-scan emissions (semi-anechoic or well-characterised room, 1–2 weeks)
- Radiated emissions pre-scan: identify worst orientations, frequencies, and cable layouts; check harmonics and spurs in representative radio modes.
- Conducted emissions (where applicable): LISN-based checks on mains/DC inputs; pay attention to DC-DC converter signatures and Ethernet PHY noise peaks.
Use this stage to iterate hardware quickly: shielding terminations, cable bonding strategy, PCB return paths, common-mode chokes, and enclosure gasketing. This is where cost-effective fixes live.
Stage C — Immunity rehearsal (GTEM/chamber time, 1–2 weeks)
- Radiated immunity: run with your defined performance monitors active (throughput scripts, modem logs, Wi‑Fi stats). Test single-radio and multi-radio operation—multi-radio is where the “mystery” failures hide.
- Conducted RF immunity: especially relevant for long Ethernet/DC cables acting as antennas. Gateways in industrial environments are classic victims.
- EFT/surge (as applicable): if you ship with an AC PSU or have long DC leads, transient immunity can be the real field failure driver, not radiated fields.
Industry insight #2: Wi‑Fi 6E / 7 increases the number of credible worst-case modes
With Wi‑Fi moving into 6 GHz (Wi‑Fi 6E/7), wider channels and more complex link behaviours increase the surface area for EMC upset and self-jamming. Even though EN 301 489 is “EMC”, not “spectrum access”, in practice your worst-case functional modes now include 160/320 MHz operation, MIMO, and high-duty traffic patterns. Pre-compliance should deliberately exercise those modes, not just 20 MHz legacy settings.
5) Common failure mechanisms on gateways (and how your plan should catch them)
Most EN 301 489 pain is repeatable. A good pre-compliance plan bakes in checks for:
- DC/DC noise folding into receivers: shows up as sensitivity loss under certain load states. Catch it by testing RX performance while stepping CPU load, Ethernet traffic, and radio TX states.
- Enclosure/cable resonance: Ethernet and DC cables become efficient radiators; emissions peaks move dramatically with cable routing. Your plan should fix cable configurations early and treat them as part of the design, not as lab “furniture”.
- ESD-induced latch states: devices that “recover” but with degraded RF performance until reboot. Catch it by running extended post-ESD functional tests, not just checking the unit powers up.
- Multi-radio desense during immunity: cellular and Wi‑Fi concurrently can mask marginal immunity. Always include a simultaneous-radios test case.
This is also where a partner with both RF design and test capability earns their keep: you want fixes that don’t just add ferrites everywhere, but preserve RF performance, thermal margins, and manufacturability.
6) Don’t ignore adjacent compliance: cybersecurity deadlines are about to bite product schedules
Even if your immediate project is “just EMC”, compliance planning is increasingly coupled. The EU’s Radio Equipment Directive cybersecurity Delegated Act (2022/30) applies from 1 August 2025 for in-scope radio equipment. That pulls software, update mechanisms, and security assurance into the same release train as your radio and EMC evidence.
From a programme perspective, it’s another reason to get EN 301 489 pre-compliance done early: the later you discover an EMC redesign, the more it collides with frozen firmware, security hardening, and manufacturing validation.
How Novocomms Space typically supports EN 301 489 pre-compliance
At Novocomms Space, we treat pre-compliance as part of product engineering rather than a box-ticking exercise. Typical support for gateway teams includes:
- RF architecture and layout reviews aimed at EMC robustness (return paths, isolation, antenna placement, shielding strategy).
- Pre-compliance test planning and execution with automation for repeatable throughput and link monitoring (so you can compare builds A/B, not just “feel” improvements).
- Rapid prototyping and debug loops—mechanical, embedded and RF—so the EMC fix is manufacturable, not a one-off lab hack.
- Scalable manufacturing support, because an EMC fix that can’t be built consistently will come back as a production escape.
In practice, that means turning your EN 301 489 campaign into a controlled series of engineering experiments: identify the coupling path, implement the simplest effective fix, and re-test with the same scripts and setups.
Conclusion: treat EN 301 489 as a design input, not an end-stage exam
A credible pre-compliance plan for EN 301 489 is less about running every formal test early, and more about proving you understand your worst-case modes, ports, and performance criteria—then generating evidence that design iterations are moving in the right direction. For cellular and Wi‑Fi IoT gateways, that discipline is the difference between a straightforward lab pass and a costly re-spin driven by an “unexpected” cable or corner case radio mode.
If you want to de-risk your next gateway build—whether you’re adding 5G, Wi‑Fi 6E/7, or simply trying to hit a fixed ship date—talk to Novocomms Space about an EN 301 489 pre-compliance programme tailored to your product and your market timelines. Contact us here: https://novocomms.space/contact-us/.
