<?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>Maximum extended advertising data length supported</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/38702/maximum-extended-advertising-data-length-supported</link><description>Hello, 
 I have PCA10040 development board with nRF52832, Softdevice S132 v6.1.0 &amp;amp; SDK 15.1.0). I wanted to use the extended advertisement feature to advertise more than 255 bytes of data. 
 Looking: 
 - In the release note (s132_nrf52_6.1.0_release-notes</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 18 Dec 2019 15:31:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/38702/maximum-extended-advertising-data-length-supported" /><item><title>RE: Maximum extended advertising data length supported</title><link>https://devzone.nordicsemi.com/thread/226205?ContentTypeID=1</link><pubDate>Wed, 18 Dec 2019 15:31:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d1a35e36-73ed-454a-8abe-da26af6f8684</guid><dc:creator>manumonti</dc:creator><description>&lt;p&gt;Hi Kenneth.&lt;/p&gt;
&lt;p&gt;So, are there any way for chaining &amp;quot;manually&amp;quot; more packets?&lt;/p&gt;
&lt;p&gt;I&amp;#39;m interested on advertise more than 255 bytes.&lt;/p&gt;
&lt;p&gt;Manuel Montenegro&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Maximum extended advertising data length supported</title><link>https://devzone.nordicsemi.com/thread/149743?ContentTypeID=1</link><pubDate>Fri, 21 Sep 2018 06:55:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de2ed0b0-45ac-44ea-9adf-819f888079a8</guid><dc:creator>Olivier Balitch</dc:creator><description>&lt;p&gt;Hi Kenneth,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Ok, that&amp;#39;s very clear.&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Olivier&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Maximum extended advertising data length supported</title><link>https://devzone.nordicsemi.com/thread/149693?ContentTypeID=1</link><pubDate>Thu, 20 Sep 2018 17:44:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:affc704a-7219-4384-87eb-350bddf03a3e</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;BLE_GAP_ADV_SET_DATA_SIZE_EXTENDED_MAX_SUPPORTED is the total number of bytes supported, in this case 255 bytes, this means that the total number of &amp;quot;chained&amp;quot; advertisement packets are up to 2 (or 1 depending on whether you call the first packet &amp;quot;chained&amp;quot;). Two packets are required since 255 bytes will not fit into one advertisement packet due to headers. I agree it is slightly&amp;nbsp;odd calling it &amp;quot;chained&amp;quot; advertisement packets, since the second packet is only a few bytes long in most cases.&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><item><title>RE: Maximum extended advertising data length supported</title><link>https://devzone.nordicsemi.com/thread/149681?ContentTypeID=1</link><pubDate>Thu, 20 Sep 2018 15:42:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b980ac0-22cb-46e1-8c78-85df58ce4143</guid><dc:creator>Olivier Balitch</dc:creator><description>&lt;p&gt;Hi Kenneth,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks for your quick feedback. If I understand you correctly, you are saying that chained advertisement is supported and that the on air packet can contain up to 255 bytes.&lt;/p&gt;
&lt;p&gt;The BLE_GAP_ADV_SET_DATA_SIZE_EXTENDED_MAX_SUPPORTED&amp;nbsp;is the define being used&amp;nbsp;to limit the number of bytes per packet. &lt;strong&gt;Is that correct?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What is the maximum number of chained packet supported or the maximum supported length&amp;nbsp;for extended advertising data with s132 softdevice&amp;nbsp;&amp;amp; nRF52832?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;How do you ensure user does not provide more than 1650 bytes (length given in the BLE Core specification)?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Olivier&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Maximum extended advertising data length supported</title><link>https://devzone.nordicsemi.com/thread/149621?ContentTypeID=1</link><pubDate>Thu, 20 Sep 2018 11:34:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a7c9b4c1-f7e9-460d-a135-56c428f322f2</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The hardware limit the maximum on-air packet to 255 bytes, in this case the 255 bytes must be split between adv mode, extended headers and advertisement data. The softdevice api have limited the max advertisement data also to 255 bytes (likely due to some internal implementation trade-offs).&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-49f742ebd2ed4d73963c7b4c6b82bebe/30C123AB.PNG" /&gt;&lt;/p&gt;
&lt;p&gt;Then depending on the length of the total advertisement packet (mode+headers+data), it may be split into 2 on-air packets, hence the advertisement packets are chained.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>