Device Name changing with nRF52840 using sd_ble_gap_device_name_set in Python

[Fabio Ballanti]

Hi,

I'm trying to make a script in Python using the nRF52840 dongle, to make some BLE advertising.

I'm using:

- Python 3.7.2 (32 bit)

- pc_ble_driver_py library

- Windows 10

- Visual Code

- nRF52840 dongle with USB CDC ACM FW

Now I would like to set a name to my device as I can see it through nRF APP on my mobile phone.

Searching through similar issues in other posts, I've found this function sd_ble_gap_device_name_set, which defined as follow:

def sd_ble_gap_device_name_set(adapter, p_write_perm, p_dev_name, len):
 return _nrf_ble_driver_sd_api_v2.sd_ble_gap_device_name_set(adapter, p_write_perm, p_dev_name, len)

To figure out how to use it, I've searched in some tutorials and found Bluetooth low energy Advertising, a beginner's tutorial which are written in C;

The function in C is declared as follow:

uint32_t sd_ble_gap_device_name_set	(	ble_gap_conn_sec_mode_t const * 	p_write_perm,
                                        uint8_t const * 	p_dev_name,
                                        uint16_t 	len 
                                    )	

In my script, the function is used as follow:

    # Device Name Change
    device_name = split_str(DEVICE_NAME)
    gap_device_name = [hex(ord(x)) for x in device_name]
    str_length = len(DEVICE_NAME.encode(encoding='utf_8'))
    driver.sd_ble_gap_device_name_set(
            peripheral.adapter.driver.rpc_adapter,
            None,
            DEVICE_NAME.encode(encoding='utf_8'),
            str_length
            )

when in Debug mode with Visual Code, I receive this message:

Can anyone help me to solve this issue?

Thanx,

Fabio

[Karl Ylvisaker]

Hello Fabio,

Fabio Ballanti said:

Ok, sounds good. I'll read it.

Great! Please do not hesitate to open a new ticket if you should encounter any issues or questions regarding how to use the Scan response.

Fabio Ballanti said:

Yes, from the output logger the following message:

Thank you for sharing the full error message. It seems this error is returned when you attempt to exceed the legal length of the advertising data.
As you have already figured out, the best way to avoid this error is staying within the allowed 31 byte limit.

Hopefully the additional 31 bytes of the scan response will allow you to meet the requirements of your application.

Best regards,
Karl