https://devzone.nordicsemi.com/f/nordic-q-a/114542/data-id-in-softdevice-extended-advertisingHi, 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 bothen-USTelligent Community 13Tue, 10 Sep 2024 18:44:06 GMThttps://devzone.nordicsemi.com/thread/501996?ContentTypeID=1Tue, 10 Sep 2024 18:44:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d8ccd9d0-3a3c-4001-85c3-aed1b371dbadtesc<p>Hi,</p> <p>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.</p> <p>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.</p> <p>Regards,<br />Terje</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/501711?ContentTypeID=1Mon, 09 Sep 2024 11:49:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f98c3dff-855d-4be7-85e1-d237b5f9f7b3n-snyder<p>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.</p><div style="clear:both;"></div>