Inconsistencies in Bluetooth Qualification Workspace

[Sailor]

Hi

I am setting up our project to generate a test plan in Bluetooth.com. It is a custom hardware using the nRF52832, so we need to do the RF.PHY-testing.

So in the qualification workspace I selected the nRF SDK QDIDs: 214837 and 214713 and continued to the ICS selection to check for inconsistencies.

Unforunately two inconsistencies shows up that cannot be resolved:

How can that be? Is it a bug in the new qualification tool or is it something else?

Thanks,

Henrik

[ketiljo]

Did you start with "no required testing"? RF-PHY is already tested so all it takes is a re-test to verify, not a full test.

[Sailor]

Since we are qualifying an end product incorporating a nRF52832 SoC, not a module, I am quite sure we have to do the full RFPHY test since it is a test more for the hardware implementation and performance, not for the stack. If nothing has changed recently at the SIG, I have always been required in the past to do the full test.

[Sailor]

By the way, what do you mean by a re-test, not a full test?

[ketiljo]

There are only so much that can change with the design, like output and frequency accuracy. Parameters like receiver blocking will not change as it's part of the chip design. 

A re-test consists of output power, sensitivity, frequency accuracy and modulation characteristics, like this: Anritsu BLE test report example.pdf

All other parameters are not affected by the design. 

BLE testing is done conducted so the antenna is not a part of the test. 

[Sailor]

Ok. Then I go for "no required testing" for the SIG, and our antenna measurements and RED testing (EN300328) should well cover the re-tests you mentioned.

Thanks for clearing that up!

Best regards