nRF52 DK and nRF52840 dongle mesh

[Karthiknk]

Hi,

I want to create a mesh between my nRF53 DK and dongle. For my project, I created my own service to send accelerometer value to the client (mobile application). Now I want to create a mesh that pushes the sensor data from two nRF devices to the mobile application. I don't know where I should start. I don't have nRF thingy52. Please suggest to me some materials and procedures to do this.

[Mttrinh]

Hi,

Not sure if you meant nRF52-DK or nRF53-DK. In the title it says 52 and ticket says 53. Can you clarify this?

For the nRF5340, the following mesh examples are supported in the nRF Connect SDK:

Mesh Light Switch example

Mesh Light example

Also recommend you to read through this, Working with nRF53 Series. 

As for the nRF52 dongle and nRF52-DK, you can use our nRF5 SDK for Mesh. Support for the dongle got added in our latest release, v5.0.0, so I recommend you use that one.

You can find the different mesh examples here. The Light switch example is the simplest example, I recommend you use that as a starting point.

Additional documentation regarding Mesh in general:

Bluetooth Mesh concept

Bluetooth Mesh stack architecture

[Karthiknk]

Thank you for your support. The Mesh example works. Also, I'm working on an augmented reality project where I want to transmit accelerometer-gyro values from two separated devices to a mobile application. Kind of wireless earbuds, where data is streamed to two wireless devices. In my case, I want to collect data streaming from two devices. I need a suggestion from experts. Which technology should I use? Should I use BLE mesh or one to many BLE topologies? I read BLE mesh communicate in messages, it changes or read the state of the element. Will mesh network be adequate to stream live data partially from two devices? Please help me to choose one. Thank you.

[Mttrinh]

Hi,

Bluetooth mesh primarily targets simple control and monitoring applications, like light control or sensor data gathering. The packet format is optimized for small control packets, issuing single commands or reports, and is not intended for data streaming or other high-bandwidth applications. One to many BLE topologies is better suited for your kind of application. 

If you have further question regarding this, I suggest you create a new ticket :)

[new]

Hi,

I am using BLE Mesh sensor_server and sensor_client example, trying to send sensor data having 3 axis. I followed the guide and changed the sensor type to "bt_mesh_sensor_magnetic_flux_density_3d". But the client side only the first value being decoded. Any suggestion on sending custom values other than predefiend sensor types?

Thank you