Using multiple peripheral connections (HID+custom) at the same time

[Tomi]

I am using HID example with nrf52, where firmware allows connection from proprietary HID host, e.g. PC as virtual (BLE) keyboard. When connection is established, I use button press on my custom board to send chosen HID code (e.g. key "a") to PC. So I was looking for best way to customize firmware in a way that my custom board could receive another custom user's data (e.g. Nordic's blinky custom UUID data) from another device (e.g. mobile phone), despite the fact that the HoG connection is established to PC.

Therefore, I looked at newer SD releases and found that "multiple peripherals" are possible with "SD132 4.0.0-1.alpha" and laters, and now I like to know:

1. how should I initialize and use this feature correctly?

2. what will using "alpha" release (instead of "production ready" release) mean for my app's future deployment? and

3. what are potential implications, when using multiple peripherals instead of just 1 connection (e.g. timing/performance issues, etc.)?

[Petter Myhre]

If you are connected to the PC as a peripheral, you can also be connected to a smart phone as a central, or as a peripheral (as you have figured out is possible with the S140).

Multiple peripheral is a very young feature, and as far as I know there is no SDK example showcasing it yet.

1. I haven't tested myself (I can give it a try if you get into trouble), but I think you just have to configure SoftDevice so that it supports x number of links, and after the first connection is established you just start doing connectable advertising once again.

2. It means that the alpha shouldn't be used for production, only for testing and exploring new features.

3. It is a bit difficult to give a general answer to this, it depends, but as long as you don't have too many connections, too small connection intervals, or sending too many packets, it should be good. It should be more information about this when the production release it out, because it will come with a SoftDevice specification that should explain these things.

Edit 07.01.2017: Maybe this can be useful.