Expert Opinion: Your certified radio module is evidence, not a finished compliance strategy
EKTOS – Using a pre-assessed Wi-Fi, Bluetooth or cellular module can save significant development time. But it can also create a false sense of security. The module may have been tested. The finished product has not. Once the module is integrated into a host, the operating conditions can change. The antenna may sit close to the metalwork. The power supply may introduce noise. PCB layout, cables, interfaces, and enclosure design can all influence radio and EMC behavior.
The useful question is therefore not: “Is the module already compliant?”
It is: “Does the existing module evidence still apply to the way we have integrated it?”
That distinction matters.
Start with the conditions behind the module assessment
Before planning new tests, look at the evidence you already have. Check how the module was originally assessed, including:
- antenna type and gain
- supply conditions
- operating frequencies and modes
- firmware or software configuration
- installation restrictions
- intended operating environment
Then compare those conditions with the finished product. If the host uses a different antenna, changes the RF environment, introduces additional noise sources or operates the module outside the assessed conditions; further evaluation may be needed. This is why host-product compliance should be treated as an engineering assessment, not simply as a paperwork exercise.
Integration can change performance
A radio module does not operate in isolation once it is inside a product. A nearby display interface, switching converter, processor clock, or cable can introduce unwanted emissions. Mechanical changes can affect antenna performance. Multiple radios operating together can create new coexistence or interference issues.
These are not necessarily problems with the module itself. They are the consequences of integration. The practical goal is to identify which changes can affect conformity and verify those areas rather than automatically repeating every test.
Europe, the US and Canada take different approaches
The regulatory route also depends on the target market. European RED conformity assessment and the modular approval frameworks used by the FCC in the US and ISED in Canada are not identical.
A module that provides useful test evidence for one market may not give you the same route to compliance in another. That makes module selection a regulatory decision as well as a technical one, especially for products intended for several markets.
The key question is what still needs to be verified
Using an already assessed module can reduce unnecessary testing, but only if the assumptions behind the original evidence are understood. The most useful approach is usually:
Review the module evidence, compare it with the final integration, identify the gaps, then test only where the integration introduces uncertainty.
That is where experienced test engineers can be valuable. A short technical review early in development can often clarify what evidence can be reused, what needs to be checked, and where additional testing is justified. There are also some recommendations from the authorities.
On 22 October, EKTOS’ test engineers will cover this topic in the third edition of our practical Open Lab session at our test lab in Hvidovre.
The event includes host-product considerations, selected testing, and an open Q&A. Learn more and Register
If you are unsure what your module documentation actually covers, talk to a test engineer before defining the test plan.
Asmildklostervej 11
8800 Viborg, Denmark
Tlf.: +45 7070 1499
E-mail: info@ektos.net
