central still receives adv when connected

RE: central still receives adv when connected

Martin Lesund — Fri, 13 Apr 2018 13:29:39 GMT

Hi Jurgen,

No problem, I am glad that you solved the issue.

RE: central still receives adv when connected

JB21 — Thu, 12 Apr 2018 23:00:42 GMT

Hi Martin,

I finally found the reason. My code started scanning via a timer even when it was connected. So all blame is on me. Please excuse me for wasting your time. Thank you very much for your help !

RE: central still receives adv when connected

JB21 — Tue, 10 Apr 2018 09:12:08 GMT

Hi Martin,

No, it is not unmodified.

I stripped most of the code since only one connection is needed.
BLE_GAP_EVT_ADV_REPORT event flashes a LED briefly.

When connected the LED still flashes as long as a 2nd peripheral advertises.

Also the power consumption indicates it is still scanning.

RE: central still receives adv when connected

Martin Lesund — Tue, 10 Apr 2018 07:36:35 GMT

Hi Jurgen,

So you are using the unmodified BLE Blinky Client Application example on the central side and the BLE Blinky Application on the peripheral side.

How do you measure that the Central is still scanning for peripherals after the connection?
I do not see the same behaviour that you are describing, could you please describe more about your setup.

RE: central still receives adv when connected

JB21 — Thu, 05 Apr 2018 13:32:03 GMT

Hello Martin,

It is based on BLE LED Button Service central and client application.

I don't want to publish main.c here in the open.

Shouldn't sd_ble_gap_connect() stop scanning in this case?

For a test I call sd_ble_gap_scan_stop() before sd_ble_gap_connect() and that works of course.

I wonder if that is really needed?

RE: central still receives adv when connected

Martin Lesund — Thu, 05 Apr 2018 09:11:50 GMT

Hello Jurgen,

What example are you basing your application on?

I would love to take a look at your code, if you could provide the main.c file?