This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

RF Core NRF52832 vs NRF52810

Hey all,

I would like to make a flexible design with ability to assemble NRF52832 or NRF52810 , both are pin to pin compatible ,

But i just wonder how to consider regulation issues:

1. Does this 2 components are sharing same RF Core?

2. Do I need different sig registration ? 

3. Do I need different BQB report ?

4. Can I use same FCC ID ( if answer for 1 is yes i assume no issue here)?

Parents
  • 1. Does this 2 components are sharing same RF Core?

     The Radio on the nRF52832 and the NRF52810 are very similar. 

    2. Do I need different sig registration ? 

    If you use the same IC for multiple similar designs, then it is possible re-use the same listing, like this https://launchstudio.bluetooth.com/ListingDetails/89624. Here multiple models of the end product are listed in the same declaration. 

    However, I do not think you are allowed to refer to more than one End Product QDID in a single listing. I tried doing this in Bluetooth Launch Studio and I got this error message 

    When referencing more than 1 Qualified Designs, only the following are supported: 1 End Product + 1 or more Profile Subsystems; 1 Controller Subsystem + 1 Host Subsystem + 0 or more Profile Subsystems.

    So you might have to refer to the tested components used in the End Product QDID  instead 94115 (Component (Tested)) ,94418 (Component (Tested)) ,102543 (Component (Tested))

    3. Do I need different BQB report ?

    We provide End Product QDIDs for both the nRF52810 and nRF52832, so you do not need to go through the qualification process. 

    However, we recommend that customers perform a Bluetooth RF-PHY when performing CE,FCC or ISED certification of the End Product so that you can prove compliance. 

    4. Can I use same FCC ID ( if answer for 1 is yes i assume no issue here)?

     As the ICs are not identical I think you will have to perform FCC certification for each of the designs, i.e. one FCC certification for the design with the nRF52832 and one with the nRF52810. 

    I suggest that you ask the testing facility where you plan to do the FCC testing about the Question 2 and 4. 

    Best regards

    Bjørn

     

     

Reply
  • 1. Does this 2 components are sharing same RF Core?

     The Radio on the nRF52832 and the NRF52810 are very similar. 

    2. Do I need different sig registration ? 

    If you use the same IC for multiple similar designs, then it is possible re-use the same listing, like this https://launchstudio.bluetooth.com/ListingDetails/89624. Here multiple models of the end product are listed in the same declaration. 

    However, I do not think you are allowed to refer to more than one End Product QDID in a single listing. I tried doing this in Bluetooth Launch Studio and I got this error message 

    When referencing more than 1 Qualified Designs, only the following are supported: 1 End Product + 1 or more Profile Subsystems; 1 Controller Subsystem + 1 Host Subsystem + 0 or more Profile Subsystems.

    So you might have to refer to the tested components used in the End Product QDID  instead 94115 (Component (Tested)) ,94418 (Component (Tested)) ,102543 (Component (Tested))

    3. Do I need different BQB report ?

    We provide End Product QDIDs for both the nRF52810 and nRF52832, so you do not need to go through the qualification process. 

    However, we recommend that customers perform a Bluetooth RF-PHY when performing CE,FCC or ISED certification of the End Product so that you can prove compliance. 

    4. Can I use same FCC ID ( if answer for 1 is yes i assume no issue here)?

     As the ICs are not identical I think you will have to perform FCC certification for each of the designs, i.e. one FCC certification for the design with the nRF52832 and one with the nRF52810. 

    I suggest that you ask the testing facility where you plan to do the FCC testing about the Question 2 and 4. 

    Best regards

    Bjørn

     

     

Children
No Data
Related