Which settings are crucial for mesh implementation and what interferences might there be?

[Juliusc]

Hello all,

Ive been working on mesh a lot in the last weeks and had problems implementing the Mesh SDK into an existing ble application of mine already. Many problems occurred but Im still here to keep it up since I really want to achieve a coexisting version of my existing app. 

the current situation is that Ive included all necessary examples, followed all the guidelines on integrating mesh into an existing application -- nothing crashed but my (static) provisioner can't find the mesh node. So my question is on how to even approach this? BLE works well as before, the init and mesh_stack_start() don't show any errors.. where to continue? I know that often the suggestion will be to just take a working example and integrate my own functionality in it but I actually want to understand what's going on and why? Which timers are relevant (I have 3 timers enabled, do they interfere with the sd/mesh observer?), which configurations could break the program and how can I assure that everything fine here? 

hope that anyone has some input for me

br

[Hung Bui]

Hi Julius, 

I wouldn't suggest to create a duplicate case about the same issue. 

It's hard for us to give you any advice without enough debug information. 

If you want to debug the application you can for example add a breakpoint or print out a log inside send_unprov_beacon() in prov_bearer_adv.c file to see if the device actually sending unprovisioning beacon. 

You can also use a power profiler tool (for example oscilloscope ) to check if there is any activity on the radio. 

You mentioned that you use 3 timer, are they the hardware TIMER or it's the app_timer you used ? The Mesh stack uses timeslot requested from the softdevice, so it might not be related.