<?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>beacon data length</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23373/beacon-data-length</link><description>Currently, I&amp;#39;m developing a beacon. We would like to employ a beacon to send a package including a IP address to other device for getting a new message from the website. 
 I&amp;#39;ve study the example of ble_app_beacon. In that one, the section &amp;quot;ble_advdata_manuf_data_t</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 10 Jul 2017 05:30:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23373/beacon-data-length" /><item><title>RE: beacon data length</title><link>https://devzone.nordicsemi.com/thread/91879?ContentTypeID=1</link><pubDate>Mon, 10 Jul 2017 05:30:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4c4260a0-f74f-4b54-8076-ba25cfdfb86d</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;You&amp;#39;ve read correctly, the maximum size of ADV packet in BT LE 4.0-4.2 is 31Bytes but in case your device is GAP&amp;amp;GATT (layers&amp;#39;) compliant you need to cut some overhead (3Bytes for &amp;quot;Flags AD&amp;quot; object and 4Bytes of &amp;quot;Manufacturer Specific Data AD&amp;quot; header). So you have 24Bytes in maximum. Note that there is a way to send &amp;quot;another&amp;quot; 31Bytes in SCAN_RSP packet but that must be actively requested by Observer and again you need to count 4Bytes of GAP overhead so maximum 27Bytes. In addition active scanning won&amp;#39;t have such frequency as ADVertising so total bandwidth will be lower... but for transporting quasi-static string in Broadcaster/Observer mode you can employ up to 24+27=51Bytes, you just need to split them (and Observer need to actively scan+reconstruct them back).&lt;/p&gt;
&lt;p&gt;Read more in any BLE Advertising/Beacon tutorial on the internet.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>