Peripheral devices / drivers support for Mesh SDK

Question

Hello guys, 
 I have got some evaluation project based on Mesh. 
 I have got Mesh SDK (nrf52832 DK Based) and Thingy52 Mesh examples working. Even we created sample Android app to control LEDs (and trying to get working receiving the data from devices, like temperature, but it does not work now) of Thingy52 devices in Mesh network (similar shown at Thingy52 Mesh SDK page). 
 Now I need to add additional sensors and actuators to that Demos. 
 Also, I see that T52 Mesh SDK is a little bit different from Mesh SDK. 
 So, my questions are: 
 - Please let me know what Mesh SDK (T52 or DK based) is better to use for case I described ( need to add additional sensors and actuators ); 
 - Please let me know how to add UART / SPI / I2C / ADC and the rest of MCU peripheral devices to T52 / DK Mesh SDKs? Do some proper way or docs / procedure exist? 
 - Could T52 Mesh SDK to be used for customer HW or even for DK? Just to start porting T52 Mesh Demo to custom HW due to this Demo has more functionality for now. 
 Thanks and Regards, 
 Alexander A.

leonwj · Answer

ok, not a Nordic employee... but, the simple task of reading will go a long way to helping you progress things along! 
 In the github repository that you linked to, it clearly states the following in the Running the demo section... 
 2. Download Nordic nRF5 SDK for Mesh v1.0.1 and extract it under Thingy:52 SDK, rename the directory from "nrf5_SDK_for_Mesh_v1.0.1_src" to "mesh_sdk". 
 
 So from this you should clearly be aware that there's a single Nordic Mesh SDK located here , which the Thingy-52 mesh demo brings into its build path to obtain mesh functionality. 
 
 In terms of UART etc. functionality merged with Mesh, I did a quick search of the forum and the following link which should be relevant to your needs is clearly available. 
 If you are looking to specifically to bring sensors/actuators into a compliant Mesh solution, then you really should be looking at the Bluetooth SIGs Mesh Model Specification v1.0 . This will ensure that any end solution you build is interoperable with other mesh stacks. (Since you are looking at other Mesh stacks, it appears that this might be important to you). ( caveat : Since these (Model profiles) are optional features within the Mesh spec, I do not believe that they have currently been implemented in the Nordic stack, but should be on their roadmap - my recommendation is for you to reach out to your Nordic reps for additional insight into things ) 
 
 Finally, as you are aware, Bluetooth Mesh is an infant technology so i'm sure that even within the Nordic Mesh there will be some changes in how the underlying Mesh stack is implemented. My suggestion would be to try to adhere to the SIG profiles as best as you can in order to insulate your solution from any stack changes. This will be important regardless of which mesh stack you choose to implement. 
 Regards,

aafanasj · Answer

Thank you.

Peripheral devices / drivers support for Mesh SDK

Top Replies

core_v2_widget.Hide()