How to set the tx power in the mesh stack?

[Young]

Hi Nordic support team,

nrf sdk for mesh 5.0.0,  nrf sdk 17.0.2,  nrf52832,

When I config the tx power for the mesh msg transmission I faced a problem.  I found that there are many places where the tx power is set, such as bear init, advertiser init, scanner init, network relay config, network transfer config ( originator ).  I am really confused about this.  Why are there so many configurations for the tx power? 

I tried to search the document which explains these tx power info, but I got nothing.   Is there a document which talks about the details of the tx power of the mesh sdk?   I want to understand the tx power configuration details. And I want to set the tx power to 4dBm for the mesh msg transmission. Could anybody provide any info about these concerns? 

[AHaug]

Hi,

Unfortunately there does not exist a single document that gathers and explains the various tx power settings/function/APIs that you're mentioning, so the best place to read about them is at infocenter.nordicsemi.

For instance, as this case refers to, you may find the API https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.meshsdk.v5.0.0%2Fgroup__MESH__OPT__CORE.html&anchor=ga3ed961289f0246c32d3ee89f06eebd1a under nRF5 SDK for Mesh 5.0. 

The case I mentioned should also contain an answer to how to set the tx power for the msg transmission.

Kind regards,
Andreas

[Young]

Hi AHaug,

My understanding is that each bear has one advertiser and each advertiser has its own tx power in mesh stack. 

In addition, for provisionee GATT BLE advertisement tx power, provisionee GATT connected BLE tx power, proxy GATT BLE advertisement tx power, proxy GATT connected BLE tx power, they can be set individually?  From the thread you mentioned, it said the sd_ble_gap_tx_power_set() can be used for provision GATT BLE advertisement, for others, there are other APIs can be used to set the tx powers? 

[AHaug]

Hi, 

Apologies for the slightly delayed response time.

Young said:

My understanding is that each bear has one advertiser and each advertiser has its own tx power in mesh stack. 

There are two bearers in Mesh; the Advertising bearer and the GATT bearer. The GATT bearer uses the Proxy protocol to allow devices that does not support the Advertising bearer to communicate indirectly with nodes of a mesh network. These has their own tx power configuration options. Everything that uses the Advertising bearer uses different settings for configuration than what is used for the Softdevice (i.e what the GATT bearer uses). This (quite old) case explains this concept to some extent.

Young said:

In addition, for provisionee GATT BLE advertisement tx power, provisionee GATT connected BLE tx power, proxy GATT BLE advertisement tx power, proxy GATT connected BLE tx power, they can be set individually?  From the thread you mentioned, it said the sd_ble_gap_tx_power_set() can be used for provision GATT BLE advertisement, for others, there are other APIs can be used to set the tx powers? 

Yes, that would be the correct conclusion All of these items you mention here belongs to the GATT bearer, and can be configured using settings you configure the SoftDevice with.

Kind regards,
Andreas