Softdevice S140 Scheduling / Timing after Reconnecthttps://devzone.nordicsemi.com/f/nordic-q-a/40980/softdevice-s140-scheduling-timing-after-reconnectHello, First, my setup: nRF52840 Dongle Softdevice S140 6.1 SDK 15.2 I built my own adapted application code based on the multilink central example and managed to create a Nordic UART Service (NUS) client to talk mith multiple peripheralsen-USTelligent Community 13Thu, 29 Nov 2018 12:21:01 GMTRE: Softdevice S140 Scheduling / Timing after Reconnecthttps://devzone.nordicsemi.com/thread/159545?ContentTypeID=1Thu, 29 Nov 2018 12:21:01 GMT137ad170-7792-4731-bb38-c0d22fbe4515:db736c31-77c0-4f7f-986b-b64bec5462e1Dominik Weber<p>Thanks, this answered my questions.</p><div style="clear:both;"></div>RE: Softdevice S140 Scheduling / Timing after Reconnecthttps://devzone.nordicsemi.com/thread/159539?ContentTypeID=1Thu, 29 Nov 2018 12:10:38 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fa292daf-009c-4cf8-b775-50984a2799a2Kenneth<p>Hi,&nbsp;</p> <p>1 and 2: There is no reliable way to get a mapping of connection handles and ordering of the connections in time. When a device reconnects, the link may be fitted somewhere else. <br /> 3: The gaps between C1 and C2 may be a result from other links disconnecting. To move the connection events closer together the application may issue a connection parameter update.</p> <p>Best regards,<br />Kenneth</p><div style="clear:both;"></div>