BLE app uart coexist example: How to change "Mesh Client" advertising name in mesh part?

[dk_07]

Hi all,

In BLE app uart coexist example, When programmed successfully, using nrf_connect app, one can see Nordic_UART and Mesh Client  being advertisied. The BLE part advertisng name can be set using sd_ble_gap_device_name_set while initialising GAP parameters. My doubt is, how to set it for mesh part?? For example: I want to Advertise Mesh Client as Mesh Server.

Thanking you in advance

Deepa

[Hung Bui]

Hi Deepa, 
Could you let me know if you have made any modification to the ble_app_uart_coexist application ? 
As far as I know the default co-exist application doesn't has any GATT support. What do you have when you connect to the Mesh Client ? Can do provision it ? 

[dk_07]

Hi Hung Bai,

Thanks for your reply.

I have not done any modification to the example and the example works without any problem. I just want to know how is GAP Name set for mesh in coexist example without GATT support?

[Hung Bui]

Please clarify what exactly you mean by "GAP name set for mesh" ? Is it GATT Proxy role you are talking about or it's the PB-GATT (provisioning via phone) ?
If the device doesn't support GATT or PB-GATT there is no point of setting "GAP name"

[dk_07]

In ble_app_uart coexist example,  I uanble to understand, Why am I able to see Mesh Client  in nrf_connect app? Is it because of default setting while initialising mesh or something else?

[Hung Bui]

Most likely it was cached because of the last firmware you flashed on the board, the phone cached the advertising packet for it. Turn on and off Bluetooth on the phone can clear this. If not please check a screenshot of what you see on the phone, and show us the advertising data you see on the phone.