Connection event position in time

[Andrzej Kuros]

Dear Nordicers,

I have an application where node based on s132 sofddevice 4.0.2 has multiple connections as a peripheral and as a central. The case is about non overlapping central and peripheral connection events. I can make all my central connection events non overlapping according to initiator timing and connection timing as a central.

How about peripheral connection events? Does softdevice take into account existing peripheral connections when placing new central connection events? Can I force peripheral connection event (managed obviously by remote central) to be located in time not used by my local central links? Can central move connection event anchor point (for example by Connection Update Procedure)? Do I have any control over transmitWindowOffset/transmitWindowSize (Bluetooth Specification 4.2 Vol 6, part B, chapter 4.5.4). Can I get timing information about existing connections from softdevice? Do softdevice perform automatically any procedure to ensure peripheral and central connection events on the same node do not overlap?

[endnode]

Yes, as I said there are certain way how to "shift" connection event (transmit window) after connection interval and I don't know how much Soft Device uses it (actually if this your question then formulate it like this in separate thread and Nordic team will answer it), however it has certain granularity so you cannot shift connection interval wherever you want + for long connections there is certain drift in the time so my bet is there will be collision sooner or later to solve. Are your concerns theoretical or you've really measured this? How it harms your application? (because it doesn't harm work of lower BLE layers)