<?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>Third peripheral sending Empty PDUs, dropping packets</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/28648/third-peripheral-sending-empty-pdus-dropping-packets</link><description>I&amp;#39;m experiencing the same issues as a previous poster that went unresolved: devzone.nordicsemi.com/.../ 
 With 1 or 2 peripherals (sensors), the connection works fine. With 3, almost always at least one sensor drops a large number of packets (40%+) while</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 Dec 2017 12:59:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/28648/third-peripheral-sending-empty-pdus-dropping-packets" /><item><title>RE: Third peripheral sending Empty PDUs, dropping packets</title><link>https://devzone.nordicsemi.com/thread/113574?ContentTypeID=1</link><pubDate>Wed, 20 Dec 2017 12:59:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:057819c8-0afb-4c21-a03c-e9dccedcf43f</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;BLE is a reliable protocol, meaning there will be no packet missing on link layer. A packet will be resend until it&amp;#39;s acked. It could be the central application code cause the packet notification packet not processed, but we don&amp;#39;t have control over it.&lt;/p&gt;
&lt;p&gt;As you can see in the Test 3 E5 trace, there was no notification packet, I don&amp;#39;t know how you can receive data (if not from read request).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Third peripheral sending Empty PDUs, dropping packets</title><link>https://devzone.nordicsemi.com/thread/113573?ContentTypeID=1</link><pubDate>Tue, 19 Dec 2017 18:46:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2315ccd5-598b-4d6e-a459-2dd28ce6c2ce</guid><dc:creator>mwmccabe</dc:creator><description>&lt;p&gt;In our protocol, a &amp;quot;data frame&amp;quot; is composed of five notifications. This data frame has a frame counter which is used to determine whether or not frames are dropped. By losing I just meant dropped/never received by our software (so presumably the central as well.)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Third peripheral sending Empty PDUs, dropping packets</title><link>https://devzone.nordicsemi.com/thread/113572?ContentTypeID=1</link><pubDate>Tue, 19 Dec 2017 17:10:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:03009f20-8485-4535-a599-a883c53a9d06</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;How do you send data from E5 to central ? How do you check if it&amp;#39;s &amp;quot;losing&amp;quot; ? what exactly is losing ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Third peripheral sending Empty PDUs, dropping packets</title><link>https://devzone.nordicsemi.com/thread/113571?ContentTypeID=1</link><pubDate>Tue, 19 Dec 2017 14:04:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0800605c-a5c2-4c96-8333-a4b353e3a574</guid><dc:creator>mwmccabe</dc:creator><description>&lt;p&gt;My central is still receiving data from sensor E5 in Test 3, but losing roughly 50% of it. How can this be if there was no write request?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Third peripheral sending Empty PDUs, dropping packets</title><link>https://devzone.nordicsemi.com/thread/113570?ContentTypeID=1</link><pubDate>Tue, 19 Dec 2017 11:45:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad6c0c3d-510d-4c12-8812-54563c3fc335</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi mwmccabe,&lt;/p&gt;
&lt;p&gt;I see no problem with Test3 Sensor E5, the connection was terminated properly. Empty PDU just mean the central didn&amp;#39;t do anything and then disconnect. I don&amp;#39;t see the central does any write request to enable notification.&lt;/p&gt;
&lt;p&gt;Test 2 Sensor E5, I don&amp;#39;t see any connection, can say nothing here.&lt;/p&gt;
&lt;p&gt;Test 1 Sensor D0, in this trace actually we can see something not normal. The central stopped sending empty PDU or at least the sniffer couldn&amp;#39;t capture any packet from central.&lt;/p&gt;
&lt;p&gt;LL_CHANNEL_MAP_REQ shouldn&amp;#39;t be an issue here, the connection is fine until very long after the new channel map took effect.&lt;/p&gt;
&lt;p&gt;From those data you provided, I don&amp;#39;t see any issue from our side. Would suggest you to test with other centrals, suggest to test with central from other brand.&lt;/p&gt;
&lt;p&gt;I assume you created an app that can handle multiple peripherals.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>