Turning on log warning function

RE: Turning on log warning function

Vidar Berg — Wed, 23 Mar 2022 08:55:45 GMT

Yes, the softdevice can support up to 20 concurrent connections. This is achieved by establishing one connection at a time. I.e. you re-start connectable advertising as soon as a connection is established to allow the next device to connect. This sequence can be repeated until you have reached the max. number of connections.

Below are some resources which are relevant to Bluetooth:

- https://devzone.nordicsemi.com/guides/short-range-guides/b/bluetooth-low-energy

- S140 SoftDevice Specification

- https://www.novelbits.io/

- https://www.bluetooth.com/specifications/specs/core-specification-5-3/

But don't hesitate to ask us when you have questions. We are here to help 🙂

RE: Turning on log warning function

willai — Wed, 23 Mar 2022 05:39:57 GMT

I have another question upon the issue.

I did some reading and found that s140 softdevice supports up to 20 concurrent connections. And I also read some thread talking about that max one connection with central would be supported.

As you mentioned the softdevice does not support multiple advertisement, what if i start the beacon advertisement after the connect with a central device is established? Would it be possible?

I am kind of new to BLE/Bluetooth. I am sorry if I am asking a stupid question. Please directly me to some reading or resource if possible so that I can do the reading on my own instead of having you explaining to me that much.

RE: Turning on log warning function

Vidar Berg — Mon, 21 Mar 2022 09:52:32 GMT

The initial value adv_handle value is always set to BLE_GAP_ADV_SET_HANDLE_NOT_SET. Here from ble_advertising_init():

It then gets set to '0' when the advertisement set has been configured through the sd_ble_gap_adv_set_configure() function (notice that p_adv_handle is an in,out argument):

RE: Turning on log warning function

willai — Mon, 21 Mar 2022 08:58:11 GMT

Thanks Vidar Berg! It works by changing m_adv_handle to 0.

By the way, in the initialization of connectable advertising mode, I didn't see the value of adv_handle being set (See ble_advertising_init() in ble_advertising.c). Is the value by default equals to 0?

While you mentioned the same advertising handle for both your connectable and non-connectable advertisements, could you explain it a bit so that I could understand a bit more about the situation I was in please?

RE: Turning on log warning function

Vidar Berg — Mon, 21 Mar 2022 08:17:37 GMT

Hello,

I guess the problem is that m_adv_handle is set to BLE_GAP_ADV_SET_HANDLE_NOT_SET when you call sd_ble_gap_adv_set_configure(). The Softdevice does not support multiple advertisement sets, which means you have to re-use the same advertising handle for both your connectable and non-connectable advertisements. Try to set m_adv_handle to '0' instead.

Best regards,

Vidar