This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Device name too short?

When trying out the ble_app_hrs_freertos example in nRF5 SDK 11.0.0-2.alpha_bc3f6a0, I seem to only get 14-character long device name announcements.

This happens when using components/softdevice/s132/hex/s132_nrf52_2.0.0-7.alpha_softdevice.hex.

I haven't had a chance yet to try it with s132_nrf52_1.0.0-3.alpha_softdevice.hex, which I had experience using from the nRF52 SDK 0.9.2.

Parents
  • Advertising data are limited to 31 bytes by specification (before BT5.0 extensions are supported) and if you support GAP layer (which is 99% of devices) you need to leave space for overhead and other elements then Device Name. Hence you have maximum of 29 bytes and in practice much less. However if you control the stack (such as on nRF5x device with Nordic Soft Device) you can organize GAP AD objects in the way that you advertise more or less just that which should give you +- 26 bytes for that. Is this your questions? If not then please open new one, give us all details about what project you run, what steps you did, what do you expect to happen and what happened instead.

Reply
  • Advertising data are limited to 31 bytes by specification (before BT5.0 extensions are supported) and if you support GAP layer (which is 99% of devices) you need to leave space for overhead and other elements then Device Name. Hence you have maximum of 29 bytes and in practice much less. However if you control the stack (such as on nRF5x device with Nordic Soft Device) you can organize GAP AD objects in the way that you advertise more or less just that which should give you +- 26 bytes for that. Is this your questions? If not then please open new one, give us all details about what project you run, what steps you did, what do you expect to happen and what happened instead.

Children
No Data
Related