Connection priority

RE: Connection priority

Vidar Berg — Thu, 24 Oct 2019 11:34:17 GMT

It's documented in the Scheduling chapter where scheduling priorities are shown in table 1.

[quote user="ViktorS"]What if we use event length extension and multiple peripherals start transmitting more data at the same time?[/quote]

As illustrated by figure 1 in Connection timing with Connection Event Length Extension, the connection event length extension is dynamic allowing any idle time between connection events to be utilized if necessary.

RE: Connection priority

vist — Thu, 24 Oct 2019 10:23:28 GMT

Ok thank you. But what does as 'efficient as possible' mean? Is the algorithm used by the SoftDevice documented somewhere?

What if we use event length extension and multiple peripherals start transmitting more data at the same time? Does the SoftDevice try to balance it so that all the peripherals get the same event length?

RE: Connection priority

Vidar Berg — Thu, 24 Oct 2019 08:43:23 GMT

It's not possible to control connection priorities directly. The Softdevice is responsible for scheduling the links as efficient as possible and avoid collisions. But as you said, you can control the throughput by selecting appropriate connection parameters such as connection intervals, MTU length, and data length. These parameters can be configured individually for each link (can be negotiated dynamically with GATT and connection param modules). See the "Suggested intervals and windows" chapter of the Softdevice specification for general recommendations.