<?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>Mesh Scanner Init Power</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/51032/mesh-scanner-init-power</link><description>In the Mesh SDK the scanner.c file has a power set to 0dBm: 
 void scanner_init(bearer_event_flag_callback_t packet_process_cb) { memset(&amp;amp;m_scanner, 0, sizeof(m_scanner)); 
 packet_buffer_init(&amp;amp;m_scanner.packet_buffer, m_scanner.packet_buffer_data, SCANNER_BUFFER_SIZE</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 19 Aug 2019 08:45:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/51032/mesh-scanner-init-power" /><item><title>RE: Mesh Scanner Init Power</title><link>https://devzone.nordicsemi.com/thread/204670?ContentTypeID=1</link><pubDate>Mon, 19 Aug 2019 08:45:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d81d44bc-c943-49c5-9839-36bed13f8e69</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You can disregard my previous answer.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Turns out that both the scanner and the advertisers use the same radio_config () API for setting the radio parameters. So technically, scanner API does not have to set the TX power, it could be leftover from legacy code.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&amp;nbsp;&lt;br /&gt;Joakim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Mesh Scanner Init Power</title><link>https://devzone.nordicsemi.com/thread/204498?ContentTypeID=1</link><pubDate>Fri, 16 Aug 2019 12:07:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ce57d630-f52c-451c-866e-4564d13f08b6</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Not 100% sure why we set tx power in scaner_init().&amp;nbsp;&lt;/p&gt;
&lt;p&gt;But I assume that it is related to what is explained in this case:&amp;nbsp;&lt;br /&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/37928/just-set-tx-power/" rel="noopener noreferrer" target="_blank"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/37928/just-set-tx-power&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;quot;As a peripheral, any connection inherits the TX power that was set for the advertising role (&lt;/span&gt;&lt;code&gt;BLE_GAP_TX_POWER_ROLE_ADV&lt;/code&gt;&lt;span&gt;), so you only need to set it once before the first connection is made to get the same behavior as before. For the central it is the same, you only need to set it once with the scanner/initiator role (&lt;/span&gt;&lt;code&gt;BLE_GAP_TX_POWER_ROLE_SCAN_INIT&lt;/code&gt;&lt;span&gt;)&amp;quot;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I&amp;#39;ll double check with our Mesh developers, and get back to you.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&amp;nbsp;&lt;br /&gt;Joakim&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>