can peripheral start connection?

RE: can peripheral start connection?

Gil — Tue, 12 May 2020 13:02:14 GMT

ok. thank you very much

RE: can peripheral start connection?

haakonsh — Tue, 12 May 2020 11:52:20 GMT

The S140 SoftDevice supports up to 20 concurrent links in any number of central or peripheral roles. A BLE device can act both as a Central and a Peripheral, just not in the same link.

RE: can peripheral start connection?

Gil — Tue, 12 May 2020 11:11:13 GMT

Will it be possible in this case (while connection is open) for my peripheral to communicate with other centrals simultaneously?

RE: can peripheral start connection?

Gil — Tue, 12 May 2020 11:06:21 GMT

OK. Thanks.

RE: can peripheral start connection?

Ole Morten — Mon, 11 May 2020 18:46:47 GMT

If I were you, I'd consider just opening a connection and keeping it open as long as the devices are in range. In that way, the Central can write to a characteristic any time it has something to send, and the Peripheral can send a notification right away. The response time should be shorter, since no link needs to be established first, before data can be sent.

Since advertising (by default) consists of sending data and listening on 3 channels, while a connection event only sends and listens on 1 channel, a connection with 300 ms connection interval should also be almost 3 times more power-efficient than advertising every 300 ms too, so I don't think there are any downsides.

You could even play with a shorter connection interval, but add slave latency, which could give much improved response times from Peripheral to Central. You can take a look at this post to understand connection parameters better.