The influence of Bluetooth name and setting tx power level in nRF52832

RE: The influence of Bluetooth name and setting tx power level in nRF52832

Karl Ylvisaker — Wed, 08 Sep 2021 07:32:45 GMT

[quote user="wfagly"]so that the problem of the length of the Bluetooth name is solved. Thanks![/quote]

Great, I am happy to hear that the issue is now resolved!

[quote user="wfagly"]I put the transmit power data in the broadcast return packet,[/quote]

Yes, you may divide the data over the advertising and scan response's - both of which have a 31 byte limit.

[quote user="wfagly"]Or use Bluetooth 5.0 and all broadcast packets, so that the broadcast data can reach 255 bytes.[/quote]

Using extended advertising should indeed also resolve the data size constraint.

Please do not hesitate to open another ticket if you should encounter any issues or questions in the future.

Good luck with your development!

Best regards,
Karl

RE: The influence of Bluetooth name and setting tx power level in nRF52832

Mikey — Wed, 08 Sep 2021 01:57:48 GMT

	init.config.ble_adv_primary_phy      = BLE_GAP_PHY_1MBPS;
    init.config.ble_adv_secondary_phy    = BLE_GAP_PHY_2MBPS;
    init.config.ble_adv_extended_enabled = true;

Or use Bluetooth 5.0 and all broadcast packets, so that the broadcast data can reach 255 bytes.

RE: The influence of Bluetooth name and setting tx power level in nRF52832

Mikey — Wed, 08 Sep 2021 01:42:18 GMT

init.srdata.p_tx_power_level 	= &tx_power_level;

Hello, I put the transmit power data in the broadcast return packet, so that the problem of the length of the Bluetooth name is solved. Thanks!

RE: The influence of Bluetooth name and setting tx power level in nRF52832

Karl Ylvisaker — Tue, 07 Sep 2021 04:56:20 GMT

[quote user="wfagly"]Sorry, I tried it yesterday but it didn't work, but today I learned that the browser plug-in affected the insertion of my code.[/quote]

No worries at all, thank you for formatting the code and making it readable! :)

So, back to your issue; I still believe that it is caused by the advertising data exceeding the 31 byte advertising payload limit.
What is the total size of your advertising packet, with the above code?
Please also keep in mind that every new datafield (i.e name, uuid's, appearance, manufacturer specific, etc) requires 2 bytes of overhead. So, if you have a 8 byte manufacturing specific data payload(2 bytes company identifier, and 6 bytes arbitrary data), it will take up 10 bytes of your total 31 available bytes.

Did you add the DEBUG define to your preprocessor defines like I asked?
If so, are you getting any error messages in your logger when this behavior occurs?

Best regards,
Karl

RE: The influence of Bluetooth name and setting tx power level in nRF52832

Mikey — Tue, 07 Sep 2021 03:54:21 GMT

/**
 * @brief Function for initializing the Advertising functionality.
 */
static void advertising_init(void)
{
    uint32_t               err_code;
    ble_advertising_init_t init;
    int8_t tx_power_level = TX_POWER_LEVEL;

    memset(&init, 0, sizeof(init));

    init.advdata.name_type          = BLE_ADVDATA_FULL_NAME;
    init.advdata.include_appearance = false;
    init.advdata.flags              = BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE;
    init.advdata.p_tx_power_level 	= &tx_power_level;

    init.srdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]);
    init.srdata.uuids_complete.p_uuids  = m_adv_uuids;

    uint8_t my_adv_manuf_data[6] = {0};
    memcpy(my_adv_manuf_data, "123456", 6);
    ble_advdata_manuf_data_t manuf_specific_data;
    manuf_specific_data.company_identifier = 0x0059;
    manuf_specific_data.data.p_data = my_adv_manuf_data;
    manuf_specific_data.data.size   = sizeof(my_adv_manuf_data);
    init.advdata.p_manuf_specific_data = &manuf_specific_data;

    init.config.ble_adv_fast_enabled  = true;
    init.config.ble_adv_fast_interval = APP_ADV_INTERVAL;
    init.config.ble_adv_fast_timeout  = APP_ADV_DURATION;
    init.evt_handler = on_adv_evt;


    err_code = ble_advertising_init(&m_advertising, &init);
    APP_ERROR_CHECK(err_code);

    ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG);
}

Sorry, I tried it yesterday but it didn't work, but today I learned that the browser plug-in affected the insertion of my code. I also added a 6-digit random key to the broadcast data

RE: The influence of Bluetooth name and setting tx power level in nRF52832

Karl Ylvisaker — Mon, 06 Sep 2021 15:03:48 GMT

Hello again,

Please use the Insert -> Code option when sharing code here on DevZone. The code you have posted above is not readable without considerable effort.

[quote user="wfagly"]I tried to add ble_advdata_encode() and the software restarts indefinitely[/quote]

This sounds like a non-NRF_SUCCESS error code is passed to an APP_ERROR_CHECK somewhere. Could you make sure to have DEBUG defined in your preprocessor defines, like shown in the included image?

This will make your logger output a detailed error message whenever a non-NRF_SUCCESS error code is passed to an APP_ERROR_CHECK.

Were you not already calling ble_advdata_encode previously, before configuring the advertising data? Which example are you using as the base of your project?

Best regards,
Karl

RE: The influence of Bluetooth name and setting tx power level in nRF52832

Mikey — Mon, 06 Sep 2021 13:00:25 GMT

/** * @brief Function for initializing the Advertising functionality. */ static void advertising_init(void) { uint32_t err_code; ble_advdata_t addata; ble_advertising_init_t init; int8_t tx_power_level = TX_POWER_LEVEL; memset(&init, 0, sizeof(init)); init.advdata.name_type = BLE_ADVDATA_FULL_NAME; init.advdata.include_appearance = false; init.advdata.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE; init.advdata.p_tx_power_level = &tx_power_level; init.srdata.uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0]); init.srdata.uuids_complete.p_uuids = m_adv_uuids; uint8_t my_adv_manuf_data[6] = {0}; memcpy(my_adv_manuf_data, "123456", 6); ble_advdata_manuf_data_t manuf_specific_data; manuf_specific_data.company_identifier = 0x0059; manuf_specific_data.data.p_data = my_adv_manuf_data; manuf_specific_data.data.size = sizeof(my_adv_manuf_data); init.advdata.p_manuf_specific_data = &manuf_specific_data; init.config.ble_adv_fast_enabled = true; init.config.ble_adv_fast_interval = APP_ADV_INTERVAL; init.config.ble_adv_fast_timeout = APP_ADV_DURATION; init.evt_handler = on_adv_evt; m_advertising.adv_data.adv_data.len = 64; err_code = ble_advertising_init(&m_advertising, &init); APP_ERROR_CHECK(err_code); ble_advertising_conn_cfg_tag_set(&m_advertising, APP_BLE_CONN_CFG_TAG); }

I tried to add ble_advdata_encode() and the software restarts indefinitely

RE: The influence of Bluetooth name and setting tx power level in nRF52832

Karl Ylvisaker — Mon, 06 Sep 2021 11:55:25 GMT

Hello,

This is likely cause by the 31 advertising byte limit being exceeded when you add the TX data field.
Including the TX data increases the payload size, which might cause it to exceed the hard 31 byte limit. The ble_advdata_encode function will then truncate the advertising name - by shaving characters off of the name - in order to make it fit into the 31 byte limit. Please see the warning of the ble_advdata_encode function's API reference for more information about this.

Best regards,
Karl