<?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>ANT RX fail while BLE connected with phone</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/124552/ant-rx-fail-while-ble-connected-with-phone</link><description>Hi, 
 
 I am currently developing a heart rate strap using SDK 17.1.0 and the S312 SoftDevice with the nRF52805. I have noticed an issue: when I connect the heart rate strap to my phone using the nRF Connect app, the ANT broadcast shows a large number</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 25 Sep 2025 14:49:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/124552/ant-rx-fail-while-ble-connected-with-phone" /><item><title>RE: ANT RX fail while BLE connected with phone</title><link>https://devzone.nordicsemi.com/thread/549828?ContentTypeID=1</link><pubDate>Thu, 25 Sep 2025 14:49:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1928b2f1-1421-48a0-a621-e54b5cfd4a63</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi John,&amp;nbsp;&lt;br /&gt;&lt;span&gt;NRF_SDH_BLE_GAP_EVENT_LENGTH&amp;nbsp; decide how long the BLE stack should stay in a connection event.&amp;nbsp;&lt;br /&gt;&lt;/span&gt;If you set it to 240 it will stay in the connection event&amp;nbsp;up to 300ms if the connection event is as long.&amp;nbsp;&lt;br /&gt;When you set it down to 6 the maximum time the BLE stack stay in the connection event will be down to 7.5ms.&lt;br /&gt;This mean you will have more time for ANT protocol.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;When you change&amp;nbsp;&lt;span&gt;&amp;nbsp;MIN_CONN_INTERVAL&amp;nbsp; and MAX_CONN_INTERVAL&amp;nbsp; down to 30 and 60ms, I think it will allow the phone to actually use these number instead of ignore it due to it &amp;#39;s too long (when you set to&amp;nbsp;400 and 650). I suspect that in that case the phone actually set it to something smaller. But we need to see the sniffer trace to be able to tell.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ANT RX fail while BLE connected with phone</title><link>https://devzone.nordicsemi.com/thread/549769?ContentTypeID=1</link><pubDate>Thu, 25 Sep 2025 08:03:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c2a54ad7-d307-41a4-a693-7920ac639a98</guid><dc:creator>JohnCC</dc:creator><description>&lt;p&gt;Hi Hung,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; I change&amp;nbsp;&lt;span&gt;NRF_SDH_BLE_GAP_EVENT_LENGTH value from 240 to 6.&amp;nbsp;The issue has been greatly improved.&lt;br /&gt;Can you help me explain why this value has an effect?&lt;br /&gt;&lt;br /&gt;On the other hand, if I change MIN_CONN_INTERVAL&amp;nbsp; and MAX_CONN_INTERVAL to 30 ms and 60 ms, it also greatly improves this problem. I don&amp;rsquo;t understand why?&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thank you.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;John.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ANT RX fail while BLE connected with phone</title><link>https://devzone.nordicsemi.com/thread/549708?ContentTypeID=1</link><pubDate>Wed, 24 Sep 2025 14:19:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:351cdbfc-0739-48f1-9cf6-9dc4277c19cf</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi John,&lt;/p&gt;
&lt;p&gt;Could you check what&amp;#39;s the actual connection interval when you connect to the phone ? It&amp;#39;s the connection interval reported in&amp;nbsp;BLE_GAP_EVT_CONNECTED event.&amp;nbsp;&lt;br /&gt;You can also use the &lt;a href="https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-6-bluetooth-le-sniffer/"&gt;sniffer trace&lt;/a&gt; to see what actually happen over the air.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I suspect that the connection interval for BLE was too short that it affects ANT communications.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please also check the configuration for&amp;nbsp;NRF_SDH_BLE_GAP_EVENT_LENGTH , could you try setting it down to 6 or lower .&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>