Multi-Link Peripheral - what is really needed?

[awneil]

Most of the SDK Peripheral examples support only a single connection.

Is there a guide somewhere which explains and illustrates  what, exactly, needs to be changed to update a single-connection example to support multiple connections ?

The SDK  v15.3.0 "BLE Multiperipheral" example does not provide any explanation - it is purely presented as a done & dusted fait accompli.

it also obfuscates the issue by using the Queued Writes module - which, by Nordic's own admission, is not a widely-used feature!

In particular, I want to know: Apart from counting connections & re-starting advertising, is it necessary to do anything more at all in a Peripheral which has only Read & Write characteristics - no Notifications?

I ask because that is exactly what I am doing at the moment:

I have a  Peripheral which has only Read & Write characteristics - no Notifications

I have got as far as adding the counting of connections & re-starting advertising - and it seems that the Reading & Writing of the characteristics works fine with multiple connections without making any further changes!

But is this safe?

[Dmitry]

Hi,

I can just confirm that it works - without any further changes - at least if you can live with sudden disconnects after a few hours with "timeout" or "instant passed" HCI status. Also I didn't investigate how peer manager handles corner cases like simultaneous pairing from two masters (we're using our own peer manager).