<?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>Reading Beacon UUID 128 bit</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/77111/reading-beacon-uuid-128-bit</link><description>Dear Ladies and Gentlement, 
 I would like to read the 128bit UUID transmitted an iBeacon received on a S140 ble_central - just similarly as it is done with nordic App nRF Connect. 
 So when activating the iBeacon device, while scanning for it on the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 06 Jul 2021 12:00:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/77111/reading-beacon-uuid-128-bit" /><item><title>RE: Reading Beacon UUID 128 bit</title><link>https://devzone.nordicsemi.com/thread/318777?ContentTypeID=1</link><pubDate>Tue, 06 Jul 2021 12:00:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1bae8607-a820-443e-94fd-2c8d2573038d</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi Richard,&lt;/p&gt;
&lt;p&gt;You get the full advertising payload from the SoftDevice, so you can parse the packet to get all the information you want. As the iBeacon format is fully defined by Apple it makes sense to parse that yourself. You can refer to the &lt;a href="https://en.wikipedia.org/wiki/IBeacon#BLE_Advertisement_Packet_Structure_Byte_Map"&gt;packet format here&lt;/a&gt; (or get&amp;nbsp;Proximity Beacon Specification R1.pdf &lt;a href="https://developer.apple.com/ibeacon/"&gt;from Apple&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;To actually get the data so that you can parse them, you need to handle the&amp;nbsp;BLE_GAP_EVT_ADV_REPORT event when scanning. There you get a pointer to a &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.0.1/structble__gap__evt__adv__report__t.html"&gt;ble_gap_evt_adv_report_t &lt;/a&gt;instance, which has the address, RSSI as well as the full payload.&lt;/p&gt;
&lt;p&gt;Einar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>