The Bluetooth SIG recently updated the tools to create product declarations. This guide will help you generate a submission.
PLEASE NOTE: This is only meant to be a guide when generating Bluetooth SIG Declarations using Rigado Bluetooth Modules. Final authority of these procedures fall within the Bluetooth SIG. You may need to open a support ticket with the SIG for specific declaration questions. The SIG has several training videos which may also contain useful information for your project: https://vimeo.com/225876947/de9bf34dad
- First, sign-in to the Bluetooth.com website and open up Launch Studio.
While Rigado's module products can refer to existing tested component QDIDs, the path to follow is actually the second one where it says "Required Testing". Later in the process, the existing "test evidence" is provided by reference to these QDIDs.
- Click the "Start the Bluetooth Qualification Process with Required Testing"
- Give your project a name.
- Search for the appropriate QDIDs to match your project. There are both Bluetooth 4.2 and Bluetooth 5 QDIDs, so be sure to select the correct ones. Please refer to this page for a list of current QDIDs associated with Rigado's modules: https://rigado.zendesk.com/hc/en-us/articles/115003419908-Rigado-Module-QDIDs-for-Bluetooth-SIG-Declaration
- For this example, we'll assume that the Bluetooth 5 QDIDs will be used:
- 93865 Nordic Semiconductor S132 nRF52 5.0.0 Link Layer
- 94418 Nordic Semiconductor S132 nRF52 5.0.0 Host Layer
- 101625 Rigado BMD-3xx RF-PHY
- Enter each QDID number separately. Once all three are entered, your screen should look similar to this:
The next section of the page is where you'll indicate the product type. First select "[1/1] End Product". You'll see two more options appear for Controller Core and Host Core Configurations. Select "LE Controller" and "LE Host" as shown here:
- Click "Save All Changes", then navigate at the top to "ICS Selection and click the "Consistency Check:
- At this point you should see "No Invalids".
If you see an "invalid", click on the link to see what might need adjusted:
- Sometimes it's a simple update to the procedure that needs a different box ticked.
- Here we'll untick "2/45" and tick "2/45a"
- Run the consistency check again:
Here all of the dependencies are now met.
- Now, click on "Testing". When the page refreshes, Click the "Download Test Plan" button
- This will download a spreadsheet to your computer.
- Open the spreadsheet. Here is where all of the test evidence will be updated. Note there are nearly 600 rows.
Column I shows the "Test Evidence Information". For all rows with a Test Case ID, enter "Referenced" in Column I:
- Now move over to Column N. This is where you'll enter the appropriate QDID for each of the test case rows. Much can be copied and pasted, although be careful which test case ID is associated with which QDID:
QDID Test Case ID 94418 GAP, L2CAP, GATT, SM, ATT 92865 LL 101625 RF PHY
- Go back to the Launch Studio and click on "Test Documentation"
- Click on "Add Test Evidence" and select your edited Test Plan spreadsheet.
- Click on Product Declaration and enter the appropriate fields. Note that the listing date may be up to 90 days into the future.
- Purchase and select your Declaration ID, then click on Review and Submit.
- Review your information. When you are satisfied with the entry, e-sign and submit the project.