nRF52 Bluetooth Certification & Declaration Clarification

RE: nRF52 Bluetooth Certification & Declaration Clarification

Jev — Wed, 02 Dec 2020 02:03:40 GMT

[quote userid="2125" url="~/f/nordic-q-a/68884/nrf52-bluetooth-certification-declaration-clarification/282666#282666"]For a pre-certified module, you normally don't have to do general radio testing, except for EMI/EMC. For CE, you can self certify the radio testing if that's done already. Provided you don't have other transmitters, body worn devices etc. as outlined in the qualification note for the module.[/quote]

What you meant by "body worn devices", do you mean devices that has direct contact with skin/body (e.g. chest pulse strap, smartwatch and etc).

Thanks for all your replies! That does cover all the things I wanted to clarify.

RE: nRF52 Bluetooth Certification & Declaration Clarification

ketiljo — Tue, 01 Dec 2020 12:55:18 GMT

[quote user="jkeeeng"]

Will it be required to conduct a general radio testing in order to get FCC/CE approval even if we will use a pre-certified module (with FCC/CE) from the following list:

https://www.nordicsemi.com/Software-and-tools/3rd-Party/3rd-party-modules

Can we get away with just general EMI/EMC or even self-certification? Are these pre-certified modules just gives an imminity against test?

[/quote]

For a pre-certified module, you normally don't have to do general radio testing, except for EMI/EMC. For CE, you can self certify the radio testing if that's done already. Provided you don't have other transmitters, body worn devices etc. as outlined in the qualification note for the module.

[quote user="jkeeeng"]

ketiljo said:
Listing is required for the end product to be sold. So if you don't sell the product to an end customer, you shouldn't need to list it. But your customers have to in case they take this into a end product.

Even if the product will be demoed or sold to business customer as a solution, so the business customer will be required to do certification before puttin to market? Am I correct?

[/quote]

Yes, it's the one that puts it into market to be available for the end user that has to list the product.

[quote user="jkeeeng"]I might be wrong, but I thought that the Thread is royalty free, so it is not mandatory to pay fees or list your device within Thread. Am I wrong? I do understand the importance of all these fees, that they will help to support futher development of the protocol, but as a small company or individual, just can't afford that amount of fees spent on the product. Unfortunatelly, some of proprietary protocols are poor in terms of specs, like number of nodes connected or other reduced functionality. [/quote]

I think Thread itself is free to use, but you have to be member of the Thread Group https://www.threadgroup.org/thread-group#Membershipbenefits

RE: nRF52 Bluetooth Certification & Declaration Clarification

Jev — Mon, 30 Nov 2020 14:53:45 GMT

First of all, thanks for your reply!

[quote userid="2125" url="~/f/nordic-q-a/68884/nrf52-bluetooth-certification-declaration-clarification/282470#282470"] The fee is per end product yes. https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/qualification-listing-fees/ No testing required for the Bluetooth part, other than general radio testing of course. [/quote]

Will it be required to conduct a general radio testing in order to get FCC/CE approval even if we will use a pre-certified module (with FCC/CE) from the following list:

[quote userid="2125" url="~/f/nordic-q-a/68884/nrf52-bluetooth-certification-declaration-clarification/282470#282470"]Listing is required for the end product to be sold. So if you don't sell the product to an end customer, you shouldn't need to list it. But your customers have to in case they take this into a end product. [/quote]

Even if the product will be demoed or sold to business customer as a solution, so the business customer will be required to do certification before puttin to market? Am I correct?

[quote userid="2125" url="~/f/nordic-q-a/68884/nrf52-bluetooth-certification-declaration-clarification/282470#282470"]Therad also have some kind of listing fee. As long as it's a protocol backed by a interest group, like Bluetooth, Zigbee, Thread, etc, there's very often a listing fee that covers the operation of the group. You can always go for a proprietary protocol like ESB, but you will not have the same interoperability as a standard. [/quote]

I might be wrong, but I thought that the Thread is royalty free, so it is not mandatory to pay fees or list your device within Thread. Am I wrong? I do understand the importance of all these fees, that they will help to support futher development of the protocol, but as a small company or individual, just can't afford that amount of fees spent on the product. Unfortunatelly, some of proprietary protocols are poor in terms of specs, like number of nodes connected or other reduced functionality.

Thanks again.

RE: nRF52 Bluetooth Certification & Declaration Clarification

ketiljo — Mon, 30 Nov 2020 14:10:32 GMT

[quote user=""]1. If we decide to go to the market and sell our product, what it will cost to us? Is it just Declaration fee which is $4000 (Associate) or $8000 (Adopter, in our case)? Is it applied per each product? Will it involve any other fees e.g. testing and etc.?[/quote]

The fee is per end product yes. https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/qualification-listing-fees/ No testing required for the Bluetooth part, other than general radio testing of course.

[quote user=""]2. What is the process of declaration/qualification? Is it similar to compliance testing and will involve the physical test on the end product? Incl. Hardware & Software?[/quote]

You start with this process: https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/qualification-process-with-no-required-testing/

[quote user=""]3. Do we need to declare the product if we are going the B2B route and will sell the technology, but not the product as itself. E.g. the company I am working at is focusing on some technologies not related to BLE and BLE device just works as an auxiliary device that helps us to demo our technology. Do we still need to declare our Bluetooth product if we are going to use it to demo to our business customers or even during an expo-shows? Or it should be declared only if our business customer will decide to sell it to the end customer?[/quote]

Listing is required for the end product to be sold. So if you don't sell the product to an end customer, you shouldn't need to list it. But your customers have to in case they take this into a end product.

[quote user=""]4. In case we are going to design a full system that will consist of 2-3 different Bluetooth products e.g. It will be a Bluetooth server/gateway that will be collecting data from a couple of sensors (different products, based on the same or similar HW). Should we declare and pay the fees for each product?[/quote]

It's per end product. But if you have multiple configurations of the same HW, you could list just the superset of the devices.

[quote user=""]5. What else should we be aware of, before bringing our Bluetooth based product to the market?[/quote]

Form a Bluetooth perspective, there's noting else but the product listing.

[quote user=""]6. Are there any other protocols that don't require high membership/adoption/declaration fees supported in Nordic products? Are there anything like Microchip MiWi which is are free for commercial use and comes as pre-certified modules? As for small start-up company it is essential. Would be Thread stack on the nRF52840 the correct option? Or should I stick to proprietary protocols like ESB?[/quote]

Therad also have some kind of listing fee. As long as it's a protocol backed by a interest group, like Bluetooth, Zigbee, Thread, etc, there's very often a listing fee that covers the operation of the group. You can always go for a proprietary protocol like ESB, but you will not have the same interoperability as a standard.