Why can't nrf52810's broadcast name be displayed completely?

RE: Why can't nrf52810's broadcast name be displayed completely?

liuyanfeng — Wed, 11 Nov 2020 08:13:42 GMT

...

RE: Why can't nrf52810's broadcast name be displayed completely?

Vidar Berg — Wed, 11 Nov 2020 07:18:26 GMT

The ble_app_uart example includes a scan response packet, which effectively double the available adv. payload from 31 to 62 bytes. For more details, please read the "scan response data" section of this tutorial: https://devzone.nordicsemi.com/nordic/short-range-guides/b/bluetooth-low-energy/posts/ble-advertising-a-beginners-tutorial

RE: Why can't nrf52810's broadcast name be displayed completely?

liuyanfeng — Wed, 11 Nov 2020 00:51:01 GMT

The same code, put in ble_ app_ UART / pc10040e / S112 is complete. And put it in ble_ app_ Template / pca10040e / S112 cannot be displayed completely. Only the

/ / init.advdata.uuids_ complete.uuid_ cnt = sizeof(m_ adv_ uuids) / sizeof(m_ adv_ uuids[0]);

/ / init.advdata.uuids_ complete.p_ uuids = m_ adv_ uuids;

If you leave out the comment, you can display it completely.

I don't know where the reason is, tell me, thank you!

RE: Why can't nrf52810's broadcast name be displayed completely?

Vidar Berg — Tue, 10 Nov 2020 13:58:24 GMT

Hello,

The name is truncated by ble_advdata_encode() if the payload is too big to fit inside the advertisment packet (31 octets), and it becomes too big as soon as you add the manufacturer field.

Best regards,

Vidar