[nRF Connect SDK] How to change BT name

RE: [nRF Connect SDK] How to change BT name

Tim Hwang — Wed, 27 Apr 2022 08:18:13 GMT

awesome! it works. I though it is too difficult. 🙂 Thank you.

RE: [nRF Connect SDK] How to change BT name

Vidar Berg — Wed, 27 Apr 2022 07:57:27 GMT

OK Thanks. You need to remove the "static const" from the "sd2" definition to get rid of the "initializer is not constant" error.

RE: [nRF Connect SDK] How to change BT name

Tim Hwang — Tue, 26 Apr 2022 23:49:09 GMT

Here is my source code & build error.

RE: [nRF Connect SDK] How to change BT name

Vidar Berg — Tue, 26 Apr 2022 08:33:30 GMT

Can you post the compile error(s) here? Thanks.

RE: [nRF Connect SDK] How to change BT name

Tim Hwang — Tue, 26 Apr 2022 08:23:12 GMT

Hello.

extended scan is not my problem.

BT_DATA(BT_DATA_NAME_COMPLETE, new_name, 32),

new_name can be "ABCD0001"(8) or "ABCDEF0001"(10) under 32Bytes in our product.

BT_DATA(BT_DATA_NAME_COMPLETE, new_name, strlen(new_name)),

-> I cannot have this usage due to compile error. so I open this case.

I have no choice but to use fixed length(32) whatever new_name is.

If I have new name as "RFR901", we can see NULL(\0\0\0...) in sniffer.

RE: [nRF Connect SDK] How to change BT name

Vidar Berg — Tue, 26 Apr 2022 08:16:40 GMT

A regular advertisement packet can only hold 31 bytes of payload, which explains why your device name won't fit. For larger advertisement packets you could use the extended advertising feature introduced in Bluetooth 5: https://blog.nordicsemi.com/getconnected/bluetooth-5-advertising-extensions. But the drawback then is that the device will only be seen be scanners that supports extended scanning.

RE: [nRF Connect SDK] How to change BT name

Tim Hwang — Thu, 21 Apr 2022 02:25:05 GMT

static const struct bt_data ad[] = {
BT_DATA_BYTES(BT_DATA_FLAGS, (BT_LE_AD_GENERAL | BT_LE_AD_NO_BREDR)),
BT_DATA(BT_DATA_NAME_COMPLETE, DEVICE_NAME, DEVICE_NAME_LEN),
};

static const struct bt_data ad[] = {
BT_DATA_BYTES(BT_DATA_FLAGS, (BT_LE_AD_GENERAL | BT_LE_AD_NO_BREDR)),
BT_DATA(BT_DATA_NAME_COMPLETE, new_name, 32),
};

char new_name[32+1];

memset(new_name, 0x0, sizeof(new_name));

strcpy(new_name, "NewName");

I could change DEVICE_NAME to new_name. It worked. But DEVICE_NAME_LEN should have 32.

(I cannot use actual length)

I'm afraid that wrong length made system halt.

In addition, I don't have to use bt_set_name()

RE: [nRF Connect SDK] How to change BT name

Vidar Berg — Wed, 20 Apr 2022 09:22:21 GMT

Hi,

Did you manage to update the adv. name dynamically as well, or is it something you are still struggling with?

RE: [nRF Connect SDK] How to change BT name

Tim Hwang — Tue, 19 Apr 2022 01:00:11 GMT

I found bt_set_name("NEW_NAME") worked. After connection, peer device had "NEW_NAME".

Now I have to advertise name as "NEW_NAME".

My customer will have several my BLE devices, so I have to tell them what device is working.

Thanks.

RE: [nRF Connect SDK] How to change BT name

Tim Hwang — Mon, 18 Apr 2022 08:06:38 GMT

I want to use NEW name but not DEVICE_NAME.
I'll receive new name via UART before bt_enable(). and I have to display new name

RE: [nRF Connect SDK] How to change BT name

qwertynoon — Mon, 18 Apr 2022 07:26:31 GMT

DEVICE_NAME is determined at compile time.

void main()
{
    String DEVICE_NAME = "Uart name"; // this is for example only.
                                        You can determine this variable anywhere
    uint8_t DEVICE_NAME_LEN = (sizeof(DEVICE_NAME) - 1);
    
    static const struct bt_data ad[] = {
    	BT_DATA_BYTES(BT_DATA_FLAGS, (BT_LE_AD_GENERAL | BT_LE_AD_NO_BREDR)),
    	BT_DATA(BT_DATA_NAME_COMPLETE, DEVICE_NAME, DEVICE_NAME_LEN),
    };
    
    static const struct bt_data sd[] = {
    	BT_DATA_BYTES(BT_DATA_UUID128_ALL, BT_UUID_NUS_VAL),
    };
    
    #define BT_LE_ADV_CONN_TEST BT_LE_ADV_PARAM(BT_LE_ADV_OPT_CONNECTABLE, \
                                                   adv_param_interval_min, \
                                                   adv_param_interval_max, NULL)
    
    err = bt_le_adv_start(BT_LE_ADV_CONN_TEST, ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd));
    if (err) {
    	LOG_ERR("Advertising failed to start (err %d)", err);
    	return;
    }
}

RE: [nRF Connect SDK] How to change BT name

Tim Hwang — Sun, 17 Apr 2022 23:41:29 GMT

Thanks for updating.

DEVICE_NAME is determined at compile time. What I'm asking you is how I can change ad[] variable in runtime.

In my test, bt_set_name() did not work.

I believe you have good solution.

RE: [nRF Connect SDK] How to change BT name

qwertynoon — Fri, 15 Apr 2022 08:55:39 GMT

String DEVICE_NAME = "Uart name";
uint8_t DEVICE_NAME_LEN = (sizeof(DEVICE_NAME) - 1);

static const struct bt_data ad[] = {
	BT_DATA_BYTES(BT_DATA_FLAGS, (BT_LE_AD_GENERAL | BT_LE_AD_NO_BREDR)),
	BT_DATA(BT_DATA_NAME_COMPLETE, DEVICE_NAME, DEVICE_NAME_LEN),
};

static const struct bt_data sd[] = {
	BT_DATA_BYTES(BT_DATA_UUID128_ALL, BT_UUID_NUS_VAL),
};

#define BT_LE_ADV_CONN_TEST BT_LE_ADV_PARAM(BT_LE_ADV_OPT_CONNECTABLE, \
                                               adv_param_interval_min, \
                                               adv_param_interval_max, NULL)

err = bt_le_adv_start(BT_LE_ADV_CONN_TEST, ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd));
if (err) {
	LOG_ERR("Advertising failed to start (err %d)", err);
	return;
}