This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[MESH SDK] Provisioning slow and unstable

Hi,

I'm using the provisioner mesh example for the nrf mesh sdk but when I'm trying to provision (an other board with light switch client example also from nrf mesh sdk), 8 times out of 10 the provisioning is slow between the NRF_MESH_PROV_EVT_STATIC_REQUEST an the next steps (an average of 40s) and 5 times out of 10, the provisioning failed at this step and need to be retry.

However, I don't think that it's the provisioned nodes that cause this issue because when I provision them through the NRF MESH mobile application, the provisioning never exceeds 20 seconds in total and never crashes

The problem is the same whether there are 1, 2 or 6 nodes in the network.

So, what could be the cause of this slowdown and instability ?

Regards

Used sdk :

- nRF5_SDK_16.0.0_98a08e2

- nrf5_SDK_for_Mesh_v4.2.0_src

Board used :

- nrf52840 evaluation board

  • Hi,

    Are there other 2.4 GHz devices nearby? It could be interference from other devices. I assume that you include the 5/10 instances failing in the 8/10 count for "slow", that is, the 8/10 is "slow or failing" and only 2/10 succeed.

    Do you have the log from the devices involved, for cases that are slow and/or failing?

    Regards,
    Terje

  • Hi,

    The provisioned devices used the light_switch server example. When I log them, there nothing weird all looks fine.

    The issue never appear when I try to provision them from the nrf mesh android app but only when I try to provision them from the nrf52840 development board with the mesh sdk 5.0.0 (also test with mesh sdk 4.2.0).

    The provisioning slow down and cause a long waiting time during the NRF_MESH_PROV_EVT_STATIC_REQUEST event.

    Regards.

  • Hi Neicureruil, 

    I think a long pause you observed was when the crypto module is running and calculating the session key for provisioning. But 40s is way too long in my opinion.

    Did you do any modification to the provisioner and the light switch example  ? 
    Could you try testing with the 2 hex files I provided here. Just so we can rule out any hardware related issue. 
    In my test here it took less than 3 seconds to finish provisioning. 

    provisioner_nrf52840_xxAA_s140_7.2.0.hex

    light_switch_client_nrf52840_xxAA_s140_7.2.0.hexs140_nrf52_7.2.0_softdevice.hex

    It's compiled with SDK v5.0

Related