Peripheral Role and Bluetooth mesh simultaneously in nRF52832

RE: Peripheral Role and Bluetooth mesh simultaneously in nRF52832

Hung Bui — Tue, 10 Jul 2018 12:27:05 GMT

Hi Brent,

I'm sorry the link was missing.
Please follow this link:

https://devzone.nordicsemi.com/f/nordic-q-a/29108/how-to-add-mesh-into-nrf5-sdk-v14-1-ble-and-sdk-v15-application

RE: Peripheral Role and Bluetooth mesh simultaneously in nRF52832

brent_dong — Tue, 10 Jul 2018 01:17:02 GMT

Hi,Hung

I want the BLE and Mesh runing sample, I cannot download from thie web page , could you send to

brent_dong@szce.com,

or give a effective link for download?

Thanks

Brent

RE: Peripheral Role and Bluetooth mesh simultaneously in nRF52832

Hung Bui — Mon, 02 Jul 2018 08:59:34 GMT

If you are talking about implementing mesh stack on a central role , we current have any example on that.

For your application to have the least modification and work, i would suggest to just adding a proprietary GATT service on the proxy node and then use the central to connect to it. This way you don't have to implement mesh stack on the central.

RE: Peripheral Role and Bluetooth mesh simultaneously in nRF52832

Arepa — Fri, 29 Jun 2018 14:27:10 GMT

Thats great news for me

So I dont have to do a huge modication to my current setup(Well I hope so)

Is there any similar example doing something similar?

RE: Peripheral Role and Bluetooth mesh simultaneously in nRF52832

Hung Bui — Fri, 29 Jun 2018 11:31:41 GMT

Hi Arepa,

The relay role and proxy role are not the same. Relay role is for ADV bearer when proxy role is for GATT bearer.

The GATT proxy and proxy node are the same.

It doesn't matter if a proxy node is a central that scan and connect or a peripheral that advertise and wait to be connected. It can be any of those. The more important is that GATT server has to be implemented on the proxy node, when on the other side ( on the phone or your node) it should have the Mesh GATT client. This is what missing in your central node.

In our implementation the proxy nodes acts as peripheral and advertise. The phone can connect to it, and on the phone when you run the Mesh app, a GATT client is created and can talk to the proxy node.

So, in your case your sensor can still be central, but you need to implement the minimum mesh stack on it.

RE: Peripheral Role and Bluetooth mesh simultaneously in nRF52832

Arepa — Thu, 28 Jun 2018 18:53:46 GMT

Hey Hung thanks for the quick reply.

I believe I am misunderstanding the mesh proxy node, is it the same that GATT proxy right? Since there is no concept of connections in a mesh network If I implement mesh stack on my central node it means, this node will advertise instead of scanning and connecting to an advertising device

I would like to use mesh between all my devices: gateway <--> repeaters(relays/proxy node/GATT proxy?) and keep my sensor using the central role I don't want they advertising or someone can see that they are there

New terms make it a little confusing because I am not sure if the three I mentioned above are the same thing 🙂

RE: Peripheral Role and Bluetooth mesh simultaneously in nRF52832

Hung Bui — Thu, 28 Jun 2018 12:59:32 GMT

Hi Arepa,

Yes, you can have BLE and Mesh running at the same time. We made an example that you can download here (scroll down for latest SDK implementation).

Another option is to use your device as a mesh proxy node. However, that requires you to implement mesh stack on your central node as well.