Peripheral in a connected mode and broadcaster

RE: Peripheral in a connected mode and broadcaster

Mike Voytovich — Sat, 07 Nov 2015 00:25:25 GMT

Thanks for the answer Petter, I tried this on S132 and it worked fine. Note that I did have to call sd_ble_gap-adv_stop() on the BLE_GAP_EVT_DISCONNECTED event first, before calling sd_ble_gap_adv_start() again with type BLE_GAP_ADV_TYPE_ADV_IND to re-advertise as connectable.

RE: Peripheral in a connected mode and broadcaster

Yaroslav — Thu, 23 Oct 2014 21:00:34 GMT

So, have you tried to restart advertising after connection and it works?

RE: Peripheral in a connected mode and broadcaster

Yaroslav — Thu, 23 Oct 2014 17:02:25 GMT

I have tried starting new advertising while connected on S110. I set type to BLE_GAP_ADV_TYPE_ADV_NONCONN_IND and 150 ms interval. But device just reboots.

RE: Peripheral in a connected mode and broadcaster

Petter Myhre — Thu, 16 Oct 2014 07:39:44 GMT

If you find my answer sufficient please accept it by clicking the grey circle with a check mark in it. If you have more questions I would appreciate if you could add them separately, so they can be helpful to others, not hidden in the comments. That said, have you examined SoftDevice S130?

RE: Peripheral in a connected mode and broadcaster

tadas — Wed, 15 Oct 2014 17:43:12 GMT

Thanks Petter. I was able to test this on S110. Is it possible to do something similar on S310? I'm basically trying to decide on my stack, so I could implement mesh networking. It seems that you cannot be a scanner and broadcaster at the same time on S110. I was looking at examples on your github page at github.com/.../. It looks like you're not using standard softdevice ble calls but accessing radio directly. I was thinking about implementing mesh with ant but i'd also like to be able to broadcast data on S310 while in connected mode, in case we decide to move mesh to bluetooth completely. Thanks.

RE: Peripheral in a connected mode and broadcaster

Locky — Mon, 13 Oct 2014 20:43:54 GMT

Does a BLE_GAP_EVT_CONNECTED event automatically cause Advertising to cease? I notice that most example project have a Start function but no Stop function for Advertising. It would be my assumption then that the Stack must automatically stop Advertising and thus it is up to the application to restart Advertising (unconnectable). Is this accurate?

RE: Peripheral in a connected mode and broadcaster

Petter Myhre — Mon, 13 Oct 2014 12:27:22 GMT

Locky is correct, you can trigger the advertising on the BLE_GAP_EVT_CONNECTED event. The advertising type must be set to BLE_GAP_ADV_TYPE_ADV_NONCONN_IND and the advertising interval must be over 100 ms.

Just declare a new ble_gap_adv_params_t struct, a separate advertising_init() function and start the advertising with sd_ble_gap_adv_start().

Locky: The SoftDevice automatically stops the advertising. The BLE_GAP_EVT_CONNECTED is sent to the application after a connection is established.

RE: Peripheral in a connected mode and broadcaster

Locky — Sat, 11 Oct 2014 04:09:32 GMT

We were told by Nordic that this was going to be in the current release of S110. So I do believe this is possible, however I cannot provide any help with a code example (not there yet in f/w development). Have you tried simply starting advertising while connected? I assume you have to change to un-connectable advertising first.