SDK15.2.0 switch NON -CONNECTABLE Beacon into CONNECTABLE

RE: SDK15.2.0 switch NON -CONNECTABLE Beacon into CONNECTABLE

Simonr — Mon, 25 May 2020 07:18:21 GMT

Hi Manoj

I'm sorry that I couldn't provide the answer you were looking for, but I did mention where you should look to make a functional connectable peripheral. I'm happy that you found what you were looking for eventually though!

Note that if you'd like a connectable example we have multiple examples available in the SDK already using various services already.

Best regards,

Simon

RE: SDK15.2.0 switch NON -CONNECTABLE Beacon into CONNECTABLE

Manoj Hiwarkar — Fri, 22 May 2020 16:33:07 GMT

No. You are wrong you have to add gap_params_init(); and gatt_init(); which are not there in beacon example. Later I observed this. Its very sad that you people never prompted us to right direction.

RE: SDK15.2.0 switch NON -CONNECTABLE Beacon into CONNECTABLE

Simonr — Fri, 22 May 2020 09:08:18 GMT

Hi Manoj

When a device is NONSCANNABLE it means that it won't respond to scan requests from the central device, and won't yield scan reports when asked.

The reason you see the error when making the beacon connectable is that you need to tweak a few more configurations in order to make it able to connect to a central. I suggest taking a look at I.E. the ble_app_uart example to see what advertising parameters it uses in order to be able to connect to a central.

Best regards,

Simon