nRF5 bluetooth name length limit shorter with SDK12 than with SDK8?

[Jarmo]

In our earlier projects with nRF51 and SDK 8 we used to have bluetooth device names of length 13 or 14 characters. However, when using nRF52 and SDK 12 I noticed that the code taken from SDK examples now limits the Bluetooth name to a maximum of 12 characters. What is the reason for that, and can I somehow set a longer name?

[Wojtek]

I don't know about examples, but SDK has nothing to device name. It would be softdevice that could matter, but it does not anyway. There is limit of whole advertising packet, there is no limit for device name field specifically. You got probably some more of other data in advertising packet, so You cannot set the name as long as it was before. You just need to tailor Your advertising packet properly...

[Jarmo]

Yeah, I know how it works, but the code provided with SDK isn't very readable (those ~900 main.c lines that are included with all those BLE examples). So it would help if somebody who wrote that mess could find the reason and probably hint how to get more room for the BLE name. Sorry, I am again frustrated :(

[Wojtek]

Yes, examples are now really overcomplicated. ble_advertising library is completely useless and makes all the advertising data preparation really hard to understand. At least for me.

[Sigurd]

An advertising packet contains 28 bytes of usable data (31 with flags). If you extend this limit the device name will be shorten. If you need to have the whole device name, you will need to reduce some of the other data you have in the advertising packet. You will need to take a look at the advertising_init() function. Maybe you can put some of the other data into the scan response packet?

[Jarmo]

Yep, I really agree the code is overcomplicated. To understand what is going on there, I have used this web site: www.argenox.com/.../. ..The API to set BLE things should not be that complicated. I have understood the corresponding MBED API is much more easy.