Multiple BLE central links with peripheral (upto 15 central links)

RE: Multiple BLE central links with peripheral (upto 15 central links)

Vidar Berg — Fri, 08 Jul 2022 11:03:55 GMT

Hello,

The peripheral can request a connection parameter change through the Connection Parameters Negotiation module, but in the end it is the Central that will decide what connection parameters to use. In general, the most important parameter for scheduling is the connection interval you use.

The longer the interval, the easier it will be for the stack to schedule all the events. The timing of when the connection interval starts is automatically controlled by the central to avoid overlapping events when possible.

RE: Multiple BLE central links with peripheral (upto 15 central links)

fxpastor — Fri, 08 Jul 2022 06:39:44 GMT

Hello Vidar,

I'm a Vivek's colleague and after reading the Scheduling documentation I have some doubts about which macros are defined in the SDK to tune the spacinf between connection events, i.e, which macros should I tune in both peripheral and central?

I saw in the SDK code some macros related to connection interval but I don't see where the timing-event, described in the documentation, is defined. And if I understood well, I need a combination of both connection interval and timing-event to avoid collisions.

I'm looking forward to hearing from you.

Best regards,

RE: Multiple BLE central links with peripheral (upto 15 central links)

Vidar Berg — Fri, 24 Jun 2022 11:13:58 GMT

Hello Vivek,

It would be good to know where the "fatal error" occurs. Could you please select the "DEBUG" build configuration to get the error handler to print out more error information?

Also, what connection paramaters do you use? The stack supports up to 20 concurrent links as you say, but that requires there to be enough spacing between connection events to leave enough room room for all connections. You can read more about this in the Scheduling chapter of the Softdevice specification.

Best regards,

Vidar