<?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>How to config the maximum TX power in NCS for both BLE central and peripheral?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/103774/how-to-config-the-maximum-tx-power-in-ncs-for-both-ble-central-and-peripheral</link><description>Dear Support Team 
 We use two nRF52 DKs to test the BLE range, one DK runs the central uart sample and the other runs the peripheral_uart sample. We would like to extend the range of the two DKs. Could you please guide me how to config the maximum TX</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 14 Sep 2023 14:07:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/103774/how-to-config-the-maximum-tx-power-in-ncs-for-both-ble-central-and-peripheral" /><item><title>RE: How to config the maximum TX power in NCS for both BLE central and peripheral?</title><link>https://devzone.nordicsemi.com/thread/446092?ContentTypeID=1</link><pubDate>Thu, 14 Sep 2023 14:07:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:db85847e-e004-4ea1-bb11-f829bd56f27c</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Please check &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/73161/nrf-ncs---set-radio-tx-power"&gt;this ticket&lt;/a&gt;, where my colleague Einar explains how you can set the TX power how you&amp;#39;d like in NCS. There are multiple other DevZone tickets of this available as well.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>