<?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>Too much scan response data to fit - strategy?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/58257/too-much-scan-response-data-to-fit---strategy</link><description>OK, so I have figured out that I can put some of my advertising content into the scan response if there is no room in the advertising packet, but what do I do if there is too much data even for that? 
 I have one (for now) standard BLE SIG service, and</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 25 Feb 2020 16:37:18 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/58257/too-much-scan-response-data-to-fit---strategy" /><item><title>RE: Too much scan response data to fit - strategy?</title><link>https://devzone.nordicsemi.com/thread/236346?ContentTypeID=1</link><pubDate>Tue, 25 Feb 2020 16:37:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d6676f81-0b86-4c78-b321-70e924536c98</guid><dc:creator>BenBurch</dc:creator><description>&lt;p&gt;OK, that appears to be what I needed, as I get past the size error. &amp;nbsp;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Too much scan response data to fit - strategy?</title><link>https://devzone.nordicsemi.com/thread/236140?ContentTypeID=1</link><pubDate>Tue, 25 Feb 2020 07:55:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:65775e41-2be3-4621-8e2c-5b1d074dd0d5</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You have at least two options:&lt;/p&gt;
&lt;p&gt;1. Remove some data from the advertising and scan response packets. Do you really need to put all the data there?&lt;/p&gt;
&lt;p&gt;2. Use advertising extensions which allows you larger advertising packets (up to BLE_GAP_ADV_SET_DATA_SIZE_EXTENDED_MAX_SUPPORTED = 255). There is also support for chaining advertisement packets. However, advertising extensions with long and/or chained advertising packets is not supported by all Bluetooth devices, so it may not be a good idea to rely on it. You can refer to the &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/ble_sdk_app_rsc.html"&gt;Running Speed and Cadence Application&lt;/a&gt; for an example of extended advertising, though this does not use large advertisement packets.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>