<?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>Setting Non-Connectable and Scannable Extended Advertising in NCS v2.5.0 (nRF52840)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/120842/setting-non-connectable-and-scannable-extended-advertising-in-ncs-v2-5-0-nrf52840</link><description>Hi， 
 When I use NCS V2.5.0 （board：nRF 52840），I want to set the Non-Connectable and Scannable Extended Advertising.My code as follows.I use the APP nRF Connect for moblie，but it can‘t scan the adv.I also use the Ellisys BTR （Picture shows &amp;#39;Test Packet</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 22 Apr 2025 19:33:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/120842/setting-non-connectable-and-scannable-extended-advertising-in-ncs-v2-5-0-nrf52840" /><item><title>RE: Setting Non-Connectable and Scannable Extended Advertising in NCS v2.5.0 (nRF52840)</title><link>https://devzone.nordicsemi.com/thread/532436?ContentTypeID=1</link><pubDate>Tue, 22 Apr 2025 19:33:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:92963c25-4847-4b66-b027-4ca83a372ebf</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Hello&amp;nbsp;qianjunwang,&lt;/p&gt;
&lt;p&gt;With Scannable Undirected Extended Advertising, you cannot have Advertising Data. The idea with Extended Advertising is that data can be offloaded entirely to the Scan Response.&lt;/p&gt;
&lt;p&gt;You will need to remove the Advertising Data.&lt;/p&gt;
&lt;p&gt;By the way, I see that a lot of error returns are not properly handled in your application.&amp;nbsp;That&amp;nbsp;hinders debugging.&amp;nbsp;I recommend fixing that, and you will also be able to get a lot of clues from the log.&lt;/p&gt;
&lt;p&gt;Ref: &lt;a href="https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/Core-60/out/en/low-energy-controller/link-layer-specification.html#UUID-e722f638-576a-dacd-b93f-82c664fafe55"&gt;Bluetooth Core Specification v6.0, Vol 6, Part B,&amp;nbsp;Section 2.3.1.5&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Hieu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>