BLE data transfer latencty between peripherals in a multi-connection-system

RE: BLE data transfer latencty between peripherals in a multi-connection-system

Susheel Nuguru — Fri, 07 Mar 2025 08:12:26 GMT

[quote user="Avadacadabara"] then the central would turn to the next peripheral connection. In this way, all peripherals have already been served in one connection interval, no? [/quote]

That is very simplistic way of multiplexing, but the underlying scheduler that reserves timeslots for each event with each peripheral tries to get a free timeslot, and there might be times where one of those request might be rejected due to something else already reserved a timeslot at the requested time. Apart from that, yes your understanding is right, You should also know some other variables like priorities for this scheduler to know that sometimes it is not just a round robin selection between peripherals.

[quote user="Avadacadabara"] What will be different if I set gap_event_length to 20ms and connection interval to 20ms?[/quote]

If you set the connection interval to 20ms in central, then the four peripheral Event Length slows might not fit within the 20ms and Peripheral 1 gets served in the first 20ms interval. Peripheral 2 gets served in the next 20ms interval. Peripheral 3 in the next, and so on. With 30ms connection interval and 7.5ms even length, all four peripherals get a turn within one connection interval (30ms).

With 20ms connection interval and 20ms event length, only one peripheral gets served per interval, so each peripheral gets a chance to communicate only once every 80ms, increasing latency.

RE: BLE data transfer latencty between peripherals in a multi-connection-system

Avadacadabara — Thu, 27 Feb 2025 03:48:59 GMT

Just wanna double check my understanding: current setup(7.5ms gap_event_length & 30ms connection interval) allows BLE central to connect 1 peripheral at a time, connection would be hold for 7.5ms then the central would turn to the next peripheral connection. In this way, all peripherals have already been served in one connection interval, no? What will be different if I set gap_event_length to 20ms and connection interval to 20ms?

[quote userid="6207" url="~/f/nordic-q-a/119246/ble-data-transfer-latencty-between-peripherals-in-a-multi-connection-system/524341"]so that all peripherals can be served in one connection interval[/quote]

Additionally, can I set peripheral PHY or ble parameters by central device?(without modifying peripheral firmware)

[quote userid="6207" url="~/f/nordic-q-a/119246/ble-data-transfer-latencty-between-peripherals-in-a-multi-connection-system/524341"]Also try using 2M phy instead of 1M[/quote]

Thanks

RE: BLE data transfer latencty between peripherals in a multi-connection-system

Susheel Nuguru — Mon, 24 Feb 2025 12:59:24 GMT

Your observations are correct—the delay between the responses from peripherals is mainly influenced by the GAP event length and the connection scheduling of the BLE controller.

Try increasing GAP event length to 15ms or more, so that all peripherals can be served in one connection interval. Try setting connection interval to 15ms or 10ms while ensuring enough GAP event length. Also try using 2M phy instead of 1M

RE: BLE data transfer latencty between peripherals in a multi-connection-system

Avadacadabara — Mon, 24 Feb 2025 08:06:37 GMT

Sorry I just found somthinig wrong with my experiment setup.

After modification, I'm monitoring the ble response timing in central ble_nus_data call back, and the delay between each response is about 7~8ms, match the connection parameters:

connection interval: 30ms
scanning interval: 30ms
scan window: 7.5ms
gap_event_length: 7.5ms

Seems like the minimum delay between slaves is the gap_event_length value. Since connection will turn unstable if I further decrease the gap_event_length. I guess this is the optimize BLE setup?

THX, AVA