<?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>How can I know how many queued packets I loose on disconnection when connected to multiple peripherals?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/51508/how-can-i-know-how-many-queued-packets-i-loose-on-disconnection-when-connected-to-multiple-peripherals</link><description>Hi, 
 I&amp;#180;m using nrf52840 with softdevice S132, SDK version 15.2 as ble central. I&amp;#180;m using the write_cmt_tx_queue by setting ble_gattc_conn_cfg_t::write_cmd_tx_queue_size to larger than 1, and counting queued writes by increasing a counter when receiving</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 03 Sep 2019 12:27:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/51508/how-can-i-know-how-many-queued-packets-i-loose-on-disconnection-when-connected-to-multiple-peripherals" /><item><title>RE: How can I know how many queued packets I loose on disconnection when connected to multiple peripherals?</title><link>https://devzone.nordicsemi.com/thread/207680?ContentTypeID=1</link><pubDate>Tue, 03 Sep 2019 12:27:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dd6aa7d8-42cd-4c99-9106-19acd5cd8ba2</guid><dc:creator>mk2</dc:creator><description>&lt;p&gt;I see, thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How can I know how many queued packets I loose on disconnection when connected to multiple peripherals?</title><link>https://devzone.nordicsemi.com/thread/206638?ContentTypeID=1</link><pubDate>Wed, 28 Aug 2019 13:16:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4bd57f57-ea41-4998-a823-2ff893d85d85</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Not really no (even ideal best case there would be an inaccuracy of 1 packet since the peer might always have receive a packet that is not ack&amp;#39;ed yet on the link layer). I would instead consider using ack on the application layer, for instance send 10 packets (by regular write or notification), wait for a packet (by write or notification) in reverse direction, before transmitting the next 10 packets and so on. Upon (re-)connection you can always &lt;span&gt;inquire how many packets have been received and continue from there.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;br /&gt;Kenneth&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>