6
\$\begingroup\$

I need BLE connectivity in a product, so to save costs on FCC certification, Bluetooth SIG membership, etc. it will use a pre-certified module for this purpose.

Usually such modules work in one or multiple of the following ways:

  • Controlled through an external interface (e.g. AT commands over UART)
  • Programmable using some proprietary scripting language (e.g. Bluegiga modules)
  • Fully user programmable

The first two approaches seem logical, the manufacturer of the module has very tight control over what can be done with the hardware (especially RF parameters, etc.).

The third approach is very appealing - most BLE chips already contain powerful microcontrollers, so it make sense to do all the processing on them. However I'm not sure whether one still gets the simplified FCC certification. I was under the impression that firmware is part of FCC testing too, especially since RF parameters (usually) can be changed significantly by software. However I wasn't able to find any warnings/clarifiactions about that in the datasheets/app notes/other docs. Could anyone clarify this a bit?

I'm mainly looking at nRF52 based and Cypress EZ-BLE modules.

\$\endgroup\$
1

3 Answers 3

3
\$\begingroup\$

It has been my experience that you would have to re-certify if you are replacing the firmware in the module.

Be aware that despite the pre-certified nature of certain modules that ultimately you or your company are responsible for meeting the legal requirements for emissions and immunity of the product as a whole. So even though a module may be pre-certified you still need to test your system with the module present.

The only place I know of where a pre-certified type module may have some decided advantages are as follows:

  1. For an embedded module you at least know that the pre-certified module is much less likely to be the source of issues for your system.
  2. A module like an analogue telephone line modem that probably carries several pre-certs may excuse you from testing the analogue phone line requirements whereas the emissions and immunity part may need to still be qualified with your system as a whole.
  3. Externally applied attachments to your product such as power bricks and cords can come pre-certified and safety inspection labeled such that you do not have to deal with that over again for your product. (A very common reason so many products today have external power bricks or wall warts).
\$\endgroup\$
0
\$\begingroup\$

By using pre-certified components, all you are doing is increasing the probabilities that your system will pass certification, not that you will be able to skip it all together. Making any change to a pre-certified component, makes the demand for system certification even stronger. If your "system" consists of only this part, then re-certification would be required.

\$\endgroup\$
0
\$\begingroup\$

I am facing a similar predicament. This application note from Wurth Electronik has been the most informative source I have found so far:

CERTIFICATION OF CUSTOM MODULES - HOW TO GAIN THE CERTIFICATION OF RADIO MODULES WITH CUSTOM FIRMWARE?

I know this should be a comment instead of an answer, but I don't have enough rep on this SE site right now to post comments. I might come back and add a summary later after reading the app note a few times to fully understand it.

\$\endgroup\$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.