<?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>packets per connection interval from nRf sniffer log</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24364/packets-per-connection-interval-from-nrf-sniffer-log</link><description>Hi! 
 Thanks for this post blog and question on sniffer logs . However, I am not clear on how to calculate the number of packets sent every connection interval? Please clarify. 
 In my case, the connection interval is 10ms and I transmit the following</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 15 Aug 2017 16:39:50 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24364/packets-per-connection-interval-from-nrf-sniffer-log" /><item><title>RE: packets per connection interval from nRf sniffer log</title><link>https://devzone.nordicsemi.com/thread/95928?ContentTypeID=1</link><pubDate>Tue, 15 Aug 2017 16:39:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a123e388-e701-4f09-ad45-816f25e77654</guid><dc:creator>endnode</dc:creator><description>&lt;ol&gt;
&lt;li&gt;Connection interval is extended by More Data (MD) bit in LL PDU header. &lt;a href="https://github.com/Szarp/WolfsHeart/blob/master/Documents/Low%20Energy%20Training.pdf"&gt;See slides 115, 122 and 123 here&lt;/a&gt;. So by looking at MD bits and time-stamps you need to count it yourself. Yes, time-stamps on Nordic sniffer with Wireshark aren&amp;#39;t very accurate, that&amp;#39;s what you get for $40, anything better costs you $1k-$30k (depending on brand and other capabilities).&lt;/li&gt;
&lt;li&gt;Only you know what data are going over your link so it&amp;#39;s only you to tell which data are which. If you use different GATT Services/Characteristics to transport these then it is easy but even with single GATT &amp;quot;tube&amp;quot; it should be trivial to define some reasonable protocol how to decode data transported over.&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>