Bluetooth SIG with nRF52832

RE: Bluetooth SIG with nRF52832

Aakash MALVIYA — Thu, 05 Dec 2019 04:04:34 GMT

Thank you very much for the Info. 🙏

RE: Bluetooth SIG with nRF52832

bjorn-spockeli — Wed, 04 Dec 2019 05:57:44 GMT

Yes, you do not need to qualify custom services if they use a 128-bit UUID. So in that case you can go with Path 1: Qualification Process with No Required Testing.

RE: Bluetooth SIG with nRF52832

Aakash MALVIYA — Wed, 04 Dec 2019 02:36:09 GMT

Thanks for the answer.

One more small question just confirming. it is very important for me. Please answer this
Q: I have a custom Bluetooth service but I haven't modified any of the Bluetooth SIG services ( 16bit UUID ) so then can I still choose path 1?

RE: Bluetooth SIG with nRF52832

bjorn-spockeli — Wed, 04 Dec 2019 00:56:37 GMT

From a Bluetooth perspective you only need to choose path 2 if you are modifying the PHY , Host or Controller parts of the Bluetooth protocol stack or modifying one of the Bluetooth SIG services( 16bit UUID). So if you are S132 v6.1.1 SoftDevice on a nRF52832 and use the Bluetooth SIG services in our SDK unmodified, then you can choose path 1.

The layout of the PCB and the RF frontend will have to be tested according to FCC/ETSI or any other applicable teleregulatory requirements.

RE: Bluetooth SIG with nRF52832

Aakash MALVIYA — Tue, 03 Dec 2019 03:36:13 GMT

Hello Sir, I have a similar question please answer my question

Q: We are using

IC: nRF52832
Soft Device: s132_nrf52_6.1.1_softdevice.hex
Modified PCB Antenna (very different from the reference design in the datasheet)
other ICs circuitry on PCB (not related with Bluetooth)

for Bluetooth SIG Qualification two paths mentioned on this official page

https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/

-----------------------------------------------------------------------------------------------------

Path 1: Qualification Process with No Required Testing

If you are:

Using another member organization’s qualified Bluetooth End-Product or Subsystem in your product without changes or additions to the Bluetooth capabilities
Purchasing a product manufactured by a third party and distributing it with your company’s name or logo
Creating combinations involving only qualified Bluetooth Subsystem Products and/or qualified Bluetooth End Products provided no design changes were made during the combination

Path 2: Qualification Process with Required Testing

If you are:

Creating any product or combination other than those involving only qualified Bluetooth Subsystem Products and/or qualified Bluetooth End-Products

-----------------------------------------------------------------------------------------------------

which path I should choose path 1 or path 2 since we have modified the antenna and also you mentioned

[quote userid="7571" url="~/f/nordic-q-a/25329/bluetooth-sig-with-nrf52832/99814"]Q1: In order if you're using our nRF52832 SoC and the S132 v5.0.0, then they are already pre-qualified and you will only need to declare your product with the Bluetooth SIG, as explained here.[/quote]

so I am confused. Please tell me path 1 or path 2.

After reading the answer on https://devzone.nordicsemi.com/f/nordic-q-a/34028/bluetooth-sig-qualification---timelines-ics . I guess we need to choose path 2.

RE: Bluetooth SIG with nRF52832

bjorn-spockeli — Thu, 08 Aug 2019 13:54:23 GMT

Bselekar: Create a private question and request a schematic/layout review. Private questions are only visible and accessible by the poster and Nordic Tech Support. We treat all files and information shared in private cases as confidential information.

Best regards

Bjørn

RE: Bluetooth SIG with nRF52832

Bselekar — Thu, 08 Aug 2019 13:33:45 GMT

Hi,

We are in the process of designing a new BLE device. The schematics and hardware layout is finished.

We saw in this post that you are offering a free-of-charge review of schematics and hardware layout. How can we apply for such a review?

We are under NDA so we can't publish it here.

Thank you for replay,

Blaz

RE: Bluetooth SIG with nRF52832

m.hendelja — Fri, 22 Sep 2017 11:20:08 GMT

Thank you for your answer :)

RE: Bluetooth SIG with nRF52832

bjorn-spockeli — Fri, 22 Sep 2017 09:18:06 GMT

Q1: In order if you're using our nRF52832 SoC and the S132 v5.0.0, then they are already pre-qualified and you will only need to declare your product with the Bluetooth SIG, as explained here.

Q2: No, Bluetooth is a licensed technology, so in order to obtain the license you will have to become a member of the Bluetooth SIG. As a member of the Bluetooth SIG you are obligated to pay all membership, declaration, enforcement and other fees set by Bluetooth SIG. This is clearly stated in the Bluetooth license agreements, found here.

Q3: No, if you're developing products for a 3rd party, that intend to sell/market these devices as Bluetooth devices, then its the 3rd party that should declare/qualify the products with the Bluetooth SIG. This is of course something that you may do on behalf of the 3rd party.

Q4: Again, Bluetooth is a licensed technology, so you're paying the Bluetooth Listing fee to use the technology as well as the use of the Bluetooth trademark and logo.

Q5: Yes, we will review your shematics and hardware layout as well as perform tuning of the RF circuitry once we are satisfied with your layout. We offer this service free-of-chare to our customers through our Mypage Support portal.