Data ID in SoftDevice Extended Advertising

[n-snyder]

Hi,

I am using version S140 of an nRF52840 in an application that creates an extended (S=8) advertising beacon. For my application to comply with regulations, I need to set the 12-bit advertising data ID field in the extended header to 0x000 - for both the ADV_EXT_IND and AUX_EXT_IND packets. From bench testing, it appears that the advertising data ID is being randomly assigned in the firmware.

I found the structure for changing the advertising data set ID, but the data ID seems to be missing in the structure. What must I do to force data ID to 0x000? If this is not something that I can do in the API, what options are available to achieve this goal?

Thank you,

Nathan Snyder

[n-snyder]

Never mind. In parallel with this request, I reached out to the leader of the regulation working group. The assignment of 0x000 for the DATA ID is a mistake that will be corrected in the next release.

[tesc]

Hi,

I can confirm your requirement of controlling the Advertising Data ID (DID) field sounds like a mistake, yes. That field is handled automatically by the stack, in accordance with the Bluetooth Core Specification, and is outside the scope of the application.

For anyone interested in the details, see the Bluetooth Core Specification Version 5.4, Vol 6, Part B, section 2.3.4.4 AdvDataInfo field.

Regards,
Terje