<?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>Extended advertising call-back register</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/90618/extended-advertising-call-back-register</link><description>Hallo, 
 currently I try to optimise the functionality of my extended advertiser code. I found that there are also some call-backs defined for extended advertisers. The struct bt_le_ext_adv_cb contains fields for sent, connected and scanned call-back</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 04 Aug 2022 12:15:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/90618/extended-advertising-call-back-register" /><item><title>RE: Extended advertising call-back register</title><link>https://devzone.nordicsemi.com/thread/380116?ContentTypeID=1</link><pubDate>Thu, 04 Aug 2022 12:15:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:437ff1cf-1ce1-4550-8031-5df559d77b76</guid><dc:creator>axel_s</dc:creator><description>&lt;p&gt;Hi Edvin,&lt;/p&gt;
&lt;p&gt;thanks - it&amp;#39;s working now.&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Axel&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Extended advertising call-back register</title><link>https://devzone.nordicsemi.com/thread/379869?ContentTypeID=1</link><pubDate>Wed, 03 Aug 2022 10:46:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b53afe0d-9d9f-4cdb-84a7-b94d5fb2d401</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;If you have a look at the sample found in:&lt;/p&gt;
&lt;p&gt;NCS\nrf\samples\bluetooth\multiple_adv_sets, you can see that this uses an instance of bt_le_ext_adv_cb, which is registered using&amp;nbsp;bt_le_ext_adv_create() inside advertising_set_create();&lt;/p&gt;
&lt;p&gt;This is all implemented in adv.c, and relying on already existing events in hci_core, such as bt_hci_le_adv_set_terminated() and bt_hci_le_scan_req_received(). The implementation inside adv.c is not too difficult to read. It just checks whether the callback exists (not NULL), and then it triggers the appropriate callback.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>