<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multi-link central lost connection with a peer when I changed the connection interval</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/95993/multi-link-central-lost-connection-with-a-peer-when-i-changed-the-connection-interval</link><description>I am using the SDK 17.0.2 and the S140 on an nrf52840 
 I have built a network with up to 3 devices. And I want to switch the connection interval between 100ms to 500ms to improve the power consumption of the peripherals when the device is idle. And return</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 24 Jan 2023 12:56:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/95993/multi-link-central-lost-connection-with-a-peer-when-i-changed-the-connection-interval" /><item><title>RE: Multi-link central lost connection with a peer when I changed the connection interval</title><link>https://devzone.nordicsemi.com/thread/406246?ContentTypeID=1</link><pubDate>Tue, 24 Jan 2023 12:56:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5d8cba87-cb90-4ffd-9509-2fed3c50f778</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;It&amp;#39;s not very common to change the connection interval run-time on the fly, typically you enable slave latency to achieve the same effect (e.g. slave latency =5). Using slave latency the peripheral can send data every connection interval (e.g. 100ms), but will skip up to slave latency intervals (e.g. 500ms) if there is no data to send.&lt;/p&gt;
&lt;p&gt;In terms of what may be the problem here I am not entirely sure, maybe it could be related to clock drift of the 32kHz in some way, what tolerance (in ppm) have you specified for the LFCLK on the central and peripheral devices here? You typically specify this when enable the softdevice.&lt;/p&gt;
&lt;p&gt;Btw, it should not directly affect what you see, but I suggest to set scan window/interval to significantly smaller than the connection interval, so if the connection interval is 100ms, then set for instance scan window = 5ms and interval = 10ms. This will schedule scanning between connection events.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>