BQB Certification information NRF52833

[picatostas]

Hi,

We are currently filling out the forms for BQB certification and I have some questions. We are using S132 v7.2.0 and NRF52833 for which I have already seen at infocenter that Nordic Semi doesn't provide a QDID for. Could I use the QDID that is provided for S140 v7.2.0 + NRF52833 or shall I migrate the application to use S140 v7.2.0 instead?

The BQB form requests the following information:

- Power class level, select from: Class 1 ( P >= 0dBm), Class 2 (-6dBm < P < 4dBm) and Class 3 (P < 0 dBm)

- Peak Antenna Gain: ?

- Cable Loss: ?

- Core Specification Version, select from: 4.2, 5.0, 5.1, 5.2, 5.3

- Core Configuration, select from: BR, EDR, LE, HS:

- LE Blueetooth 5 features, select from: LE 2M PHY, LE Coded Phy, Stable modulation Index TX and RX.

- LE Packet length (TX/RX):

- Direction Finding Features(5.1 BT or later):

For the Core Specification Version, I cat get it from the softdevice by running the following snippet:

uint32_t sys_get_softdevice_version(void) {
    ble_version_t v;
    uint32_t err = sd_ble_version_get(&v);
    return err == NRF_SUCCESS ? v.version_number : 0xffffffff;
}

Which gives back 0x0000000a so the Bluetooth version is 5.1, right ?

I have connected our application to nrf connect and I can see the following information:

So from what I understand:

- We are using legacy mode for advertising.

- EDR and BR are not supported.

- We use LE general discoverable Mode.

I am trying to figure out if we are using any of the AoA direction finding and LE  features introduced in Bluetooth 5, but I'll guess we don't as we use legacy mode.

How can I find out about the rest of the required information by the BQB form ?

It is the first time I go through this process so I need some guidance.

Thanks in advance,

Pablo

[Hung Bui]

Hi Pablo, 

Could you let me know what exactly you are trying to get the certification for ? 
I'm not so sure what you meant by "BQB" are you trying to get a Declaration ID ? 

Have you checked if your design require testing or doesn't require testing ? 

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

Usually for those which require testing, a RF PHY retest is needed and you would need to talk to a test house to perform the test. 

Regarding your question, you would need to use S140 v7.2.0 to use the QDID, so you may need to migrate to S140 v7.2.0 for that. 

S140 v7.2.0 support Bluetooth v5.1 

If you don't do any AoA it means no AoA feature used. 

[picatostas]

Hi Hung Bui,

We have submitted our device for certification and If I understand correctly we want to certify for FCC ID, FCC SdoC, IC ID, IC-VOC and CE. Since have a Bluetooth device we also need to get approval from BTSIG, If I got it right, BQB is Bluetooth certification.

Our design requires testing. We had the previous version of the product registed in BTSIG however we changed both the MCU ( from NRF52832 to NRF52833) and the Softdevice and the product has been redesign from ground up.

What is RF PHY testing? I don't recall that term from the conversation we had with the cert house so far.

I will start migrating the app to S140 v7.2.0 then.

What about the following points ?

- Power class level, select from: Class 1 ( P >= 0dBm), Class 2 (-6dBm < P < 4dBm) and Class 3 (P < 0 dBm)

- LE Packet length (TX/RX):

Where can I find the information about them ?

Regards,

[Hung Bui]

Hi Pablo, 

BQB could be a term introduced by the test house, not by Bluetooth SIG. For Bluetooth SIG certification it should be DID or QDID. Have you taken a look at the link I pointed to ? 

I'm not the best to answer about RF questions but the power class you are pointing to also sounds a bit strange. Usually the power class refer to: 

Class	Maximum Tx power	Operating range
class 1	20 dBm	~100 meters
class 2	4 dBm	~10 meters
class 3	0 dBm	~1 meter

RF-PHY testing is the test of the PHY level, you can find the information in the list here. This re-test is optional. If you follow our reference design you shouldn't have a problem to pass this re-test. 

Regarding the packet length, the actual packet length is varied but I think you can provide the maximum packet length you support in your application, usually it's defined in sdk_config.h: NRF_SDH_BLE_GAP_DATA_LENGTH