https://devzone.nordicsemi.com/f/nordic-q-a/10255/advertising-initHi everyone. I am making an application which combines two services (ANCS and Nordic UART). I compare the advertising_init() function from the two provided examples (ble_app_ancs_c and ble_app_uart) and see the difference inside advertising_init functionen-USTelligent Community 13Mon, 16 Nov 2015 06:48:21 GMThttps://devzone.nordicsemi.com/thread/38065?ContentTypeID=1Mon, 16 Nov 2015 06:48:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:704d906b-10e8-48a3-8407-e22f97c72b08shibshab<p>In some cases, other devices will require more information about a device than whats contained within the advertisement packet. This is done by sending a &quot;SCAN_REQ&quot; packet to a device which is advertising (note that this only applies for the advertising types ADV_IND and ADV_SCAN_IND/ADV_DISCOVER_IND.</p> <p>If you don&#39;t care about providing more information in the &quot;SCAN_RSP&quot; packet, or your advertisement is of a non-scannable type, you do not have to provide scan response data to the advertising initialization.</p> <p>This is valid for scannable advertisement types as well, and will result in a &quot;SCAN_RSP&quot; with no data being sent.</p> <p>(1) does not provide scan response data, whilst (2) does. If you want to provide some extra information from your advertiser without connecting, you should use (2) and place the extra data in the scan response. Otherwise you should/could use (1).</p> <p>Note that there might be some convention/desired way of doing this that I&#39;m not aware of.</p><div style="clear:both;"></div>