<?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>Why advertising packet length in BLE sniffer is different with LL packet length ?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46644/why-advertising-packet-length-in-ble-sniffer-is-different-with-ll-packet-length</link><description>Dear experts.. 
 I&amp;#39;m currently developing and testing nRF52832 application with nRF52-DK. 
 This are three questions about &amp;quot;actual&amp;quot; advertising packet length on air. 
 
 First &amp;gt; I wonder about that why the advertising packet length is 54 bytes in my application</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 03 May 2019 08:13:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46644/why-advertising-packet-length-in-ble-sniffer-is-different-with-ll-packet-length" /><item><title>RE: Why advertising packet length in BLE sniffer is different with LL packet length ?</title><link>https://devzone.nordicsemi.com/thread/185077?ContentTypeID=1</link><pubDate>Fri, 03 May 2019 08:13:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a617d95f-a9f9-40c3-a64d-79d1c0f7b65c</guid><dc:creator>Daewoong Kim</dc:creator><description>&lt;p&gt;No more for this problem. Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why advertising packet length in BLE sniffer is different with LL packet length ?</title><link>https://devzone.nordicsemi.com/thread/185074?ContentTypeID=1</link><pubDate>Fri, 03 May 2019 08:10:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4b91996f-78f9-462d-94eb-25b58016621f</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;Ok great! Have you answered you question fully then or do you still need anymore help? &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why advertising packet length in BLE sniffer is different with LL packet length ?</title><link>https://devzone.nordicsemi.com/thread/184738?ContentTypeID=1</link><pubDate>Thu, 02 May 2019 00:23:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:15f2eaf3-6351-44df-8ad2-4021e82589a1</guid><dc:creator>Daewoong Kim</dc:creator><description>&lt;p&gt;It&amp;#39;s OK. I think 16 bytes of data might be BLE sniffers information (such as, measurement time, RSSI level, etc.).&lt;/p&gt;
&lt;p&gt;So, those packet length is same with expected length!.&lt;/p&gt;
&lt;p&gt;After connection, I could see the empty packet having data length of 26 bytes, which consisted of 16 bytes of BLE&lt;/p&gt;
&lt;p&gt;sniffer info- packets + 10 bytes of BLE LL packets (preamble + access address + LL header + CRC = 10).&lt;/p&gt;
&lt;p&gt;Anyway, thank you for your reply &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why advertising packet length in BLE sniffer is different with LL packet length ?</title><link>https://devzone.nordicsemi.com/thread/184665?ContentTypeID=1</link><pubDate>Wed, 01 May 2019 06:48:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c7209eb-f7fb-44b2-a40c-08bc3d1e250a</guid><dc:creator>Bj&amp;#248;rn Kvaale</dc:creator><description>&lt;p&gt;&lt;span&gt;Due to other support activity, I have been kept busy the last few days. You can expect a response latest on the 3rd of May. Sorry for any inconvenience caused!&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>