<?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>nRF51822 Beacon Kit Advertisements Not Recieved by nRF51822 Development Board</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/36368/nrf51822-beacon-kit-advertisements-not-recieved-by-nrf51822-development-board</link><description>My current setup is this: 
 I have a nRF51822 beacon (tiny coin cell beacon) advertising with its default settings. I have another board, a nRF51822 Development Kit, that is scanning for nearby BLE devices. The development board then sends the MAC addresses</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 16 Jul 2018 16:04:24 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/36368/nrf51822-beacon-kit-advertisements-not-recieved-by-nrf51822-development-board" /><item><title>RE: nRF51822 Beacon Kit Advertisements Not Recieved by nRF51822 Development Board</title><link>https://devzone.nordicsemi.com/thread/140260?ContentTypeID=1</link><pubDate>Mon, 16 Jul 2018 16:04:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:52607220-3def-4f10-878f-3442834563ef</guid><dc:creator>Mttrinh</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;1. Yes, it should be possible for DKs to read beacon advertisement packets.&lt;/p&gt;
&lt;p&gt;2. Not sure what you mean by BCCD, I assume you mean the 16-bit UUID you put in the base UUID. The parameters for is_uuid_present is:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;static bool is_uuid_present(const ble_uuid_t *p_target_uuid,
                            const ble_gap_evt_adv_report_t *p_adv_report)&lt;/pre&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In the first parameter, you should have your 16-bit UUID and UUID type(BLE_UUID_TYPE_VENDOR_BEGIN if it your custom UUID and&amp;nbsp;BLE_UUID_TYPE_BLE if it is a UUID from Bluetooth SIG).&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>