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

DFU over BLE messing up Mesh provisioning

Hello all,

We are trying to implement coexistence between BLE and Bluetooth mesh.

After following the Nordic coexistence tutorials, our program builds fine using both SDKs and it seems to run fine; no runtime errors. The issue seems to be performance-related; however, it is entirely blocking us from setting up the mesh network. 

To simplify things so that we can test our mesh network, we have stripped out all BLE functionality to avoid the inherited problems we've been seeing; however, we still need to be able to perform DFUs and want to avoid using DFU over mesh because (1) we need coexistence working anyway and (2) we don't want to flood the network with DFU packets.

When we have the DFU enabled alongside all of the mesh features, the DFU seems to work perfectly fine; however, this has an observable performance knock-on effect in the provisioning of mesh nodes. 

We are using the nRF Mesh app for mobile to provision. And what we are seeing exactly is it recognising the unprovisioned nodes, but none of the features work. A connection leads to an immediate disconnection most of the time, then if it does manage to provision, it always returns an error message saying "Initial Configuration Failed". When we disable our DFU functionality, mesh appears to work fine which leads me to believe our issues pertain to mesh-BLE coexistence.

Any advice or support will be greatly appreciated.

All the best!

Parents
  • Hi Char, 

    Please clarify the following. You mentioned that you avoid using DFU over mesh but you still have DFU supported, which DFU method is that  ? 

    You also mentioned that you use Mesh app for mobile provision, so you still have PB-GATT (provision via a phone connection ) supported ? 

    How about your own BLE profile, do you also have that running ? What's the functionality of that ? 

    Please be aware that having DFU over mesh supported doesn't affect mesh performance when DFU process is not in place. Even with DFU process in place, mesh should still work at at least 90% of the performance as there is no change in the scanning (still do normal Mesh scanning) and the sending of DFU packets are at very low rate.. 

Reply
  • Hi Char, 

    Please clarify the following. You mentioned that you avoid using DFU over mesh but you still have DFU supported, which DFU method is that  ? 

    You also mentioned that you use Mesh app for mobile provision, so you still have PB-GATT (provision via a phone connection ) supported ? 

    How about your own BLE profile, do you also have that running ? What's the functionality of that ? 

    Please be aware that having DFU over mesh supported doesn't affect mesh performance when DFU process is not in place. Even with DFU process in place, mesh should still work at at least 90% of the performance as there is no change in the scanning (still do normal Mesh scanning) and the sending of DFU packets are at very low rate.. 

Children
No Data
Related