<?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>Change TX power of iBeacon advertising</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128201/change-tx-power-of-ibeacon-advertising</link><description>Hi everyone, 
 We recently started to add the iBeacon broadcasting to our own BLE project that runs on an nRF5340. It is based on the code from the sample of the SDK (we currently use v2.9.0) located at &amp;quot;ncs\v2.9.0\zephyr\samples\bluetooth\ibeacon&amp;quot;. </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 21 May 2026 12:49:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128201/change-tx-power-of-ibeacon-advertising" /><item><title>RE: Change TX power of iBeacon advertising</title><link>https://devzone.nordicsemi.com/thread/566691?ContentTypeID=1</link><pubDate>Thu, 21 May 2026 12:49:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e966407e-ee9f-4c2b-bd4e-a2edabfbc36e</guid><dc:creator>Ryisen0</dc:creator><description>&lt;p&gt;Hi Einar,&lt;/p&gt;
&lt;p&gt;thank you for your quick reply. I&amp;#39;ll take a look at the sample code and merge it into our project.&lt;/p&gt;
&lt;p&gt;Many thanks,&lt;/p&gt;
&lt;p&gt;Alex&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Change TX power of iBeacon advertising</title><link>https://devzone.nordicsemi.com/thread/566689?ContentTypeID=1</link><pubDate>Thu, 21 May 2026 12:42:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:be9abfcc-728d-4500-9469-92bedb5669a0</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;Alex,&lt;/p&gt;
&lt;p&gt;You can change the Tx power of a specific advertising set (or a specific connection for that matter) by using a HCI command as&amp;nbsp;demonstrated in the &lt;a href="https://github.com/nrfconnect/sdk-zephyr/blob/fbde0eff49ab12c99e7f53e6eb1c45b426180ed8/samples/bluetooth/hci_pwr_ctrl"&gt;HCI Power Control sample&lt;/a&gt;. This approach works on the nRF5340 as well, but you need to make sure to build the network core image (ipc_radio) with support for dynamic power control.&lt;/p&gt;
&lt;p&gt;To use this sample on the nRF5340 application core you can add two small configuration files:&lt;/p&gt;
&lt;p&gt;sysbuild.conf:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;SB_CONFIG_NETCORE_IPC_RADIO=y
SB_CONFIG_NETCORE_IPC_RADIO_BT_HCI_IPC=y&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;sysbuild/ipc_radio.conf:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL=y
CONFIG_BT_CTLR_CONN_RSSI=y&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;When adding to your own application, you will need the same configurations.&lt;/p&gt;
&lt;p&gt;(You can also remove two&amp;nbsp;configurations you put in ipc_radio.conf from the prj.conf, as they are only relevant for the BT Controller on the network core, and not for the host that runs on the application core).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>