<?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>nRF52840 not appearing when scanning in the NRFConnect application (Using the Long-Range example 1MPBS)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/33363/nrf52840-not-appearing-when-scanning-in-the-nrfconnect-application-using-the-long-range-example-1mpbs</link><description>Hi, 
 I was trying out the long range example provided on the NordicPlayground GitHub repo, and worked great when communicating between two nRF52840 dev kits. I however noticed that it wasn&amp;#39;t possible to scan for the peripheral device when using the application</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 13 Apr 2018 16:13:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/33363/nrf52840-not-appearing-when-scanning-in-the-nrfconnect-application-using-the-long-range-example-1mpbs" /><item><title>RE: nRF52840 not appearing when scanning in the NRFConnect application (Using the Long-Range example 1MPBS)</title><link>https://devzone.nordicsemi.com/thread/128288?ContentTypeID=1</link><pubDate>Fri, 13 Apr 2018 16:13:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:70209e9c-c524-41b5-85d7-31d9382c53d4</guid><dc:creator>Hadi Deknache</dc:creator><description>&lt;p&gt;Hello, first of all thanks for helping out.&lt;/p&gt;
&lt;p&gt;I have as shown in the included code above set the primary/secondary phy to 1MBPS, am I missing something? Also I noticed that the scannable isn&amp;#39;t possible to be set since the application would return invalid params&amp;nbsp;when running&amp;nbsp;the&amp;nbsp;sd_ble_gap_adv_start() function. Could maybe this be the cause of the device not appearing when scanning through the mobile phone?&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;&lt;strong&gt;EDIT 16/4-18:&lt;/strong&gt;&lt;/span&gt; I Successfully managed to scan for the device today after setting the legacy_pdu = 1 and scannable = 1, but don&amp;#39;t understand the functionality of the legacy pdu?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52840 not appearing when scanning in the NRFConnect application (Using the Long-Range example 1MPBS)</title><link>https://devzone.nordicsemi.com/thread/128262?ContentTypeID=1</link><pubDate>Fri, 13 Apr 2018 13:32:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e754d546-99ad-43a3-a975-324fcee16740</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;In the example on github the peripheral advertises, as you say, on coded phy&amp;nbsp;(aka long range) and the central is also &lt;em&gt;scanning &lt;/em&gt;on coded phy. Devices must advertise and scan on the same phy to be able to discover each other. I&amp;#39;m not aware of any phones&amp;nbsp;compatible with coded phy.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>