<?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>about Connection Interval</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/115029/about-connection-interval</link><description>We have tried the following changes, but couldn&amp;#39;t get expecting results. 
 Sometimes unable to pair two devices / Sometimes fails to link with one device 
 Could you answer the inquiry 1 &amp;amp; 2? 
 
 [SDK ver.] 
 2.7.0 
 [Changes] 
 
 Changed the Connection</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 11 Oct 2024 12:50:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/115029/about-connection-interval" /><item><title>RE: about Connection Interval</title><link>https://devzone.nordicsemi.com/thread/505890?ContentTypeID=1</link><pubDate>Fri, 11 Oct 2024 12:50:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5e51e61b-096f-4ca8-8c29-f0fd2170bb90</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Tomokuni,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Unfortunately the sniffer traces you captured don&amp;#39;t provide much useful information because it didn&amp;#39;t follow the connection.&amp;nbsp;&lt;br /&gt;We have a tutorial that you can follow here regarding the sniffer:&amp;nbsp;&lt;a href="https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-6-bluetooth-le-sniffer/"&gt;https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-6-bluetooth-le-sniffer/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;BLE_ACL_CONN_INTERVAL is the normal connection interval, yes.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;br /&gt;You can reduce the time from starting advertising until connection established by advertising with shorter advertising interval.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: about Connection Interval</title><link>https://devzone.nordicsemi.com/thread/505866?ContentTypeID=1</link><pubDate>Fri, 11 Oct 2024 10:46:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bedc217e-6808-43a5-9722-e0aed4304ed7</guid><dc:creator>tommy</dc:creator><description>&lt;p&gt;&amp;quot;Link time&amp;quot; means the elapsed time to establish the connection between Central and Peripheral.&lt;br /&gt;Here are the log of connection captured by the sniffer.&lt;br /&gt;We have changed the value of&amp;nbsp;&lt;span data-teams="true"&gt;&lt;span class="ui-provider a b c d e f g h i j k l m n o p q r s t u v w x y z ab ac ae af ag ah ai aj ak" dir="ltr"&gt;BLE_ACL_CONN_INTERVA, and tried 30msec and 100msec.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;(BTW,BLE_ACL_CONN_INTERVA surely define the Connection interval as circled in red?)&lt;/p&gt;
&lt;p&gt;30ms_CONNECTION_FAIL-SUCCESS.pcapng&lt;br /&gt;&amp;nbsp;-&amp;gt; once failed, but SUCCESSED afterward&lt;/p&gt;
&lt;p&gt;30ms_CONNECTION_SUCCESS.pcapng&lt;br /&gt;&amp;nbsp;-&amp;gt; connection successed&lt;/p&gt;
&lt;p&gt;100ms_CONNECTION_FAIL.pcapng&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;-&amp;gt; connection failed&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;100ms_CONNECTION_SUCCESS.pcapng&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;-&amp;gt; connection successed&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;In our environment, we have found the following result;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;30msec: the elapsed time surely reduced, however sometimes it becomes easier for the connection to be lost and recovered.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;100msec:the connection lost rarely happened.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;span&gt;Is there some way to optimize this parameter?&lt;br /&gt;or are there any optimized value for each SDK?&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/2677.log.zip"&gt;devzone.nordicsemi.com/.../2677.log.zip&lt;/a&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/ConnectionInterval.jpg" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: about Connection Interval</title><link>https://devzone.nordicsemi.com/thread/503981?ContentTypeID=1</link><pubDate>Thu, 26 Sep 2024 12:36:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:00824bb7-0c6d-4c72-a3f1-88c7061f7d42</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Tomokuni,&amp;nbsp;&lt;br /&gt;Please provide more information about the issue:&amp;nbsp; Unable to pair two devices / Sometimes fails to link with one device&lt;br /&gt;&lt;br /&gt;When you reduce the connection interval, the data exchange can be faster and result in shorter time for service discovery and pairing.&amp;nbsp;&lt;br /&gt;Please elaborate what you meant by &amp;quot;link time&amp;quot;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;My suggestion is to use&lt;a href="https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-6-bluetooth-le-sniffer/"&gt; the sniffer&lt;/a&gt; to capture the connection and pairing.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>