<?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+BLE multi-protocol communication problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/75319/ant-ble-multi-protocol-communication-problem</link><description>Dear friend， 
 Based on SDK15.3, using S332 protocol stack, running on nRF52832-QFAA. Connect the device with a mobile phone via Bluetooth. The connection parameter Min connecion interval is 30ms, Max connecion interval is 60ms The number of devices sends</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 19 May 2021 13:04:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/75319/ant-ble-multi-protocol-communication-problem" /><item><title>RE: ANT+BLE multi-protocol communication problem</title><link>https://devzone.nordicsemi.com/thread/310466?ContentTypeID=1</link><pubDate>Wed, 19 May 2021 13:04:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9463b499-bd4d-481e-abd3-67a2c51361f2</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;If there is no error message from &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.2.0/group___b_l_e___g_a_t_t_s___f_u_n_c_t_i_o_n_s.html?cp=4_7_3_1_2_4_2_4#ga313fe43c2e93267da668572e885945db"&gt;sd_ble_gatts_hvx()&lt;/a&gt; then this sounds like an issue on the phone side, maybe you need to add some application handshake to not overflow the phone (e.g. every 100notifications wait for a write command from the phone before next 100notifications etc.).&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It would be interesting if you can make an on-air sniffer log, so we can see exactly what is happening on-air, and possible which packets are lost. Possible compare the working with the failing.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>