This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Trying to develop a mesh connected system using multiple Thingy52

I am new to Nordic and BLE mesh connectivity. I have the following assumptions & queries, Please clarify if I am wrong.

1. Is it possible to implement BLE Mesh using Thing52? I found a project on GITHUB, I believe its possible.

2. What are the toolchains required? Segger embedded studio. do I need any other tools?

3. I believe I can program Thing 52 using a nrf52 DK. Will that be fine

4. Whats the difference between soft device and Mesh SDK? I read Soft device is the Communication Stack, I was in a thought that Mesh SDK is also a stack. 

5. Other than the Mesh SDK and Soft device(if required), we need nrf thingy SDK as well for the firmware.

Do I need any other resources or tools or SDK to implement BLE mesh in Thingy 52? 

Parents
  • Hi,

    1. Yes, that is possible. The Thingy Mesh Demo v0.1 on Github is a good starting point.

     

    1. See this page. You can find the latest version of nRF5x Command Line Tools here( Windows, Linux, OSX)

     

    1. Yes, you can use the nRF52-DK to program the Thingy 52. The simplest way of connecting the Thingy to the nRF52 DK would be using a 10-pin 2x5 1.27 mm pitch cable, like this one.

     

    1. Yes, these are two different stacks. All Mesh packet is handled by mesh stack, directly using the radio peripheral. The SoftDevice is currently only used for it's Timeslot API. But the BLE Softdevice can also be usefully, so that the device can do BLE if needed, such as advertising, beaconing, GATT connection etc.

     

    1. Thingy 52 SDK can be found here.
Reply
  • Hi,

    1. Yes, that is possible. The Thingy Mesh Demo v0.1 on Github is a good starting point.

     

    1. See this page. You can find the latest version of nRF5x Command Line Tools here( Windows, Linux, OSX)

     

    1. Yes, you can use the nRF52-DK to program the Thingy 52. The simplest way of connecting the Thingy to the nRF52 DK would be using a 10-pin 2x5 1.27 mm pitch cable, like this one.

     

    1. Yes, these are two different stacks. All Mesh packet is handled by mesh stack, directly using the radio peripheral. The SoftDevice is currently only used for it's Timeslot API. But the BLE Softdevice can also be usefully, so that the device can do BLE if needed, such as advertising, beaconing, GATT connection etc.

     

    1. Thingy 52 SDK can be found here.
Children
Related