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

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

dk_07 — Tue, 09 Jun 2020 12:36:54 GMT

Thanks a lot.

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

Hung Bui — Tue, 09 Jun 2020 12:33:30 GMT

No, softdevice only allow one connectable advertising packet at a time. Note that doesn't matter which advertising name it is, it's the same GATT server that you will find when you connect. So it's the GATT server that combine both UART service and GATT Proxy/PB GATT service.

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

dk_07 — Tue, 09 Jun 2020 11:50:26 GMT

The program provided in the link works. Now Nordic UART advertise as MESH. Cann´t I simultaneously advertise Nordic UART as MESH and BLE using SDK15.2 and MESH 3.1?

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

dk_07 — Tue, 09 Jun 2020 09:29:17 GMT

Sorry. It is GATT Proxy role

Thanks for the link

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

Hung Bui — Tue, 09 Jun 2020 09:23:27 GMT

Again, please answer the question, what do you plan to do with mesh advertising ? Is it for GATT Proxy role or it's for PB-GATT ?

Anyway I provided an example here: devzone.nordicsemi.com/.../235538

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

dk_07 — Tue, 09 Jun 2020 09:19:24 GMT

Yes, your right. Now, 'I can see only Nordic_UART being advertised. So, ble_app_uart_coexist example advertises only UART not the Mesh one? If I want to advertise both simultaneously, is it possible?

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

Hung Bui — Tue, 09 Jun 2020 08:16:16 GMT

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.

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

dk_07 — Mon, 08 Jun 2020 15:54:11 GMT

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?

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

Hung Bui — Mon, 08 Jun 2020 13:51:55 GMT

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"

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

dk_07 — Mon, 08 Jun 2020 13:24:24 GMT

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?

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

Hung Bui — Mon, 08 Jun 2020 13:08:27 GMT

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 ?