mesh PROXY sdk2.1.1 TX power of nrf52832

[PopradiArpad]

Hi,

I want to set the TX power in a mesh proxy configuration.
I have read mesh sdk2.1.1 TX power of nrf52832,
which works good for not proxy situation (e.g for light_switch_client) but has no effect
on light_switch_proxy_client.

I measure the advertising signal strength simple using nRF Connect
and use SDK for mesh 2.1.1 and SDK 15.0.0.

How can I set the TX power in case of mesh proxy?

Regards,

Árpád

[Joakim Jakobsen]

Hi.

The suggestion in the thread you linked to is probably working. It is setting the TX power of the ADV bearer to whatever value you are using (as long as the value is supported).

But from what I understand, you want to change the TX power of the proxy bearer.
The proxy bearer uses the softdevice advertisement. To change the TX power of that advertisment packet, you have to use the softdevice API to change the TX power (sd_ble_gap_tx_power_set())

If you have any further questions, please let me know.
Best regards,
Joakim.

[PopradiArpad]

Hi Joakim,

thank you for your answer!

You are right, the tx_power settings in set_default_broadcast_configuration and
in scanner_init functions sets only for PB-ADV.

For PB-GATT these settings work:

void mesh_adv_start(void)
{
#if NRF_SD_BLE_API_VERSION == 6
    //TEST-START
    APP_ERROR_CHECK(sd_ble_gap_tx_power_set(BLE_GAP_TX_POWER_ROLE_ADV, m_adv_handle, -40));
    __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "mesh_adv_start: changed TX power\n");
    //TEST-END

    APP_ERROR_CHECK(sd_ble_gap_adv_start(m_adv_handle,  MESH_SOFTDEVICE_CONN_CFG_TAG));
#else
    APP_ERROR_CHECK(sd_ble_gap_adv_start(&m_adv_params,  MESH_SOFTDEVICE_CONN_CFG_TAG));
#endif
    /* We restart the mesh timeslot to yield time for the softdevice advertiser to start. */
    timeslot_restart();
}

static void mesh_gatt_event_handler(const mesh_gatt_evt_t * p_evt, void * p_context)
{
..
        case MESH_GATT_EVT_TYPE_CONNECTED:
            evt.conn_index = p_evt->conn_index;
            fsm_event_post(&p_bearer_gatt->fsm, E_CONNECTED, &evt);
            //TEST-START
            NRF_MESH_ASSERT(sd_ble_gap_tx_power_set(BLE_GAP_TX_POWER_ROLE_CONN, evt.conn_index, -40) == NRF_SUCCESS);
            __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "mesh_gatt_event_handler: changed TX power\n");
            //TEST-END
..
}

It would be very nice if it was not needed to hack SDK functions to set tx_power :(
scanner_init, set_default_broadcast_configuration and mesh_gatt_event_handler are SDK functions
mesh_adv_start in mesh_adv.c is only a sample implementation and mesh_adv.c is encouraged to be application specific.

Best regards,
Árpád

[PopradiArpad]

Sorry it's not PB-ADV but advertising bearer, and not PB-GATT but GATT bearer.