nRF-Connect Windows Advertising issues

[Michael Portmann]

I am trying to set up a custom Advertisement in nRF-Connect for Windows, using an nRF52 DK (PCA10040)

In Advertising Setup, I remove the existing "Complete local lame" entry in the Advertising data and then add my own Custom AD type. I enter type 0x21 with 26 bytes of data and when I try to Apply the change, I get the error "Length of packet is 28 bytes, which is larger than the maximum of 20 bytes."

I tried using nRF-Connect Windows as cloning the Advertisement data from nRF-Connect for Android doesn't support the 128 byte UUID service data.

Also, with regards to the above - when I add the 01 / 06 custom AD type and then add a UUID service data that is short enough to not complain about the 20 byte limit, e.g. 21 / 8D69DE3D57374FBD5441E873649BFE94FFFF. When viewed in nRF-Connect Android, the nRF52 DK only advertises the type 21 and not the type 01.

How do you use the Advertising feature in nRF-Connect ?

[Sigurd]

Hi,

Thank you for reporting this. There seem to be 2 different bugs here.

• It's only possible to add one Custom AD type to the advertising data. When adding a second Custom AD type the first one will be overwritten. Only the one added last will be included.
• The 20 bytes limit. This should have been 31 bytes.

Both bugs have been reported internally, and will hopefully be fixed in the next release.

[Michael Portmann]

Hi,

I think the bug is actually the 20 byte limit. The advertising packet can contain upto 31 characters. (BLE_GAP_ADV_MAX_SIZE)

[Sigurd]

Hi,

That is correct. I have updated my answer.