<?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>nrf beacon not detectcing</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24963/nrf-beacon-not-detectcing</link><description>image description (/attachment/a49b3ec690a646f7bead02928ff0a381)(/attachment/a22b78f8886f98aac724a2b9785f9c25)(/attachment/00e9df542ed79773e83dde5fb38e46cc)Hi all, 
 I have designed the nrf51822 based coin size custom board for beacon application.
i</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 07 Sep 2017 10:52:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24963/nrf-beacon-not-detectcing" /><item><title>RE: nrf beacon not detectcing</title><link>https://devzone.nordicsemi.com/thread/98300?ContentTypeID=1</link><pubDate>Thu, 07 Sep 2017 10:52:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3d6fe8ae-af3a-48cc-9864-f3ea1a28936f</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;I cannot argue about how you mix HW and FW versions during your tests but the advertising data are different so you have definitely more then one FW/configuration. Once you are OK with some of them then stick with it and test the other HW. Also note that some mobiles might cache adv. data so restarting BT/whole device might help as well. But that applies to cases where nRF Connect app displays data which you don§t expect. I§m afraid you are not there yet;)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf beacon not detectcing</title><link>https://devzone.nordicsemi.com/thread/98299?ContentTypeID=1</link><pubDate>Thu, 07 Sep 2017 10:40:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7f6d2235-bad6-418c-aae6-58e454b39412</guid><dc:creator>pavan</dc:creator><description>&lt;p&gt;Hello ,&lt;/p&gt;
&lt;p&gt;As per your suggestion i run one firmware only on my custom board but still no change its not detecting in nRF beacon app could you please help us solve this issue . i will be running the firmware only on my custom board.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf beacon not detectcing</title><link>https://devzone.nordicsemi.com/thread/98298?ContentTypeID=1</link><pubDate>Thu, 07 Sep 2017 10:22:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:79c422b7-4ad2-4a5e-ada2-d856a96642bc</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;If you look and compare the data you can see straight away that they are different! Then no surprise that applications are working differently! Mainly manufacturer ID at the beginning of last LTV object data (0x5900 vs. 0xFEAA) can make any beacon scanner failing because it usually don&amp;#39;t look for two IDs but just one (but Manufacturer ID isn&amp;#39;t typically the only filter on scanner&amp;#39;s side!) So you obviously don&amp;#39;t run the same FW on both beacons. Why such misleading description in the question? Why you imply that some app has bug when you test with almost &amp;quot;random&amp;quot; devices? I don&amp;#39;t get it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf beacon not detectcing</title><link>https://devzone.nordicsemi.com/thread/98307?ContentTypeID=1</link><pubDate>Thu, 07 Sep 2017 09:50:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8fa48856-2ad8-42ee-aaf9-2415527e3cfc</guid><dc:creator>pavan</dc:creator><description>&lt;p&gt;Hi below are my steps,&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;I take softdevice from this path (C:\Nordic Semiconductor\nRF51822 Beacon v1.1.1\SoftDevice) and programmed successfully using nrfgo Studio on nrf51DK.&lt;/li&gt;
&lt;li&gt;then i took application program from this path (C:\Nordic Semiconductor\nRF51822 Beacon v1.1.1\Precompiled hex) and programmed successfully using nrfgo Studio on nrf51DK.
3)Then I see no LED blinking I turn on nRF Connect app, I see the device broadcasting  now i opened  nRF Beacon  i can see detect device in App with monalisa picture.No LEDs blinking.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Now i repeated the same steps with my custom board i can see device detecting nRF Connect app but not in nRF Beacon it keeps scanning. Attached the raw data and images of both DK and custom board for your refeance.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf beacon not detectcing</title><link>https://devzone.nordicsemi.com/thread/98306?ContentTypeID=1</link><pubDate>Thu, 07 Sep 2017 07:31:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:33b96329-54fb-4741-add7-58f41f55b66b</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;I mean like:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;I take pre-compiled HEX file named &lt;code&gt;xyz&lt;/code&gt; from this path in this nRF5 SDk version and flash it by this program with this SoftDevice HEX file to this HW.&lt;/li&gt;
&lt;li&gt;Then I see this LED blinking (or not), I turn on nRF Connect app, I see the device broadcasting (what are &amp;quot;RAW&amp;quot; advertising and scan response data??? Paste it here!) and I can connect to the device (what happens in nRF Connect then? Any change on the board e.g. LEDs blink/light differently?)&lt;/li&gt;
&lt;li&gt;Then I open nRF Beacon app and do this and that, see this and that.&lt;/li&gt;
&lt;li&gt;Then I take same HEX files and flash the same way another HW (any description of that HW???) and see this and that.&lt;/li&gt;
&lt;li&gt;Then I open nRF Connect app again and see this and that
etc. ......................&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf beacon not detectcing</title><link>https://devzone.nordicsemi.com/thread/98305?ContentTypeID=1</link><pubDate>Thu, 07 Sep 2017 07:25:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f24d0590-0063-41d3-bd4f-1195054a93ac</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;I mean HW change should not change broadcasted information or reaction to received Connection Request. So if given FW works on some HW completely as you expect then it should either work the same or other HW or doesn&amp;#39;t work at all.&lt;/p&gt;
&lt;p&gt;When it comes to your nRF Connect vs. nRF Beacon app behavior I&amp;#39;m still missing the point. Can you update your original question  with step by step summary 1/2/3/... of what you do and what you see? Then I might be able to understand what exactly is happening and what do you expect vs. what is happening.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf beacon not detectcing</title><link>https://devzone.nordicsemi.com/thread/98303?ContentTypeID=1</link><pubDate>Thu, 07 Sep 2017 07:12:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ce220ed4-2a31-47c9-be99-56fc31c632fd</guid><dc:creator>pavan</dc:creator><description>&lt;p&gt;well then you mean to say if my custom board broadcasting with some firmware in nRF connect then it should also broadcast in nrf Beacon application. rie?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf beacon not detectcing</title><link>https://devzone.nordicsemi.com/thread/98304?ContentTypeID=1</link><pubDate>Thu, 07 Sep 2017 06:43:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:13ae21b5-03fe-44c0-a386-3379ced63276</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Get radio trace from BLE sniffer or at least past RAW advertising data as captured by nRF Connect app for Android (or other OS). If the same BLE FW works on one HW (= meaning nRF Beacon app from your oriinal question can detect it and connect if necessary) and not on other then it&amp;#39;s most likely not broadcasting at all. If you claim that certain FW on some HW (whatever custom or Nordic dev kit) works with certain application but not with other then it must be alive (= advertising and capable of connection) so it would mean that the same FW or other HW should either work the same or not work at all (because it fails during boot) but nothing in between.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf beacon not detectcing</title><link>https://devzone.nordicsemi.com/thread/98302?ContentTypeID=1</link><pubDate>Thu, 07 Sep 2017 04:09:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0511bbb2-75d1-481c-8527-da373d45f428</guid><dc:creator>pavan</dc:creator><description>&lt;p&gt;Hi ,&lt;/p&gt;
&lt;p&gt;But i have programmed the same program which is programmed in nRF518222 Bluetooth smart kit of nordic. its working fine  in that kit but not in my  custom board.&lt;/p&gt;
&lt;p&gt;Adding to above do i need to upadate any  manufacturer ID.?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf beacon not detectcing</title><link>https://devzone.nordicsemi.com/thread/98301?ContentTypeID=1</link><pubDate>Wed, 06 Sep 2017 21:16:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c00c28d3-4630-4ce3-86a1-6910995a876b</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Have you read description about exactly what &amp;quot;beacons&amp;quot; is nRF Beacon app looking for? I guess your device simply isn&amp;#39;t sending proper UUID in advertising data or not using correct Manufacturer ID in Vendor Specific AD object of Advertising Data etc. nRF Connect shows all GAP Peripheral/Broadcaster devices so that&amp;#39;s why it doesn&amp;#39;t care and works OK.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>