After Unpromising (Reset Node) the node is not able to discover for further provisioning.

[ramachandra]

Hi,

   We are using nRF52840 chipset with SDK 15.0.0  with Mesh implemetation. 

1. We are provisioning the mesh node using the nRF mesh APP.

2. Then we are resetting the node using same nRF mesh APP.

3. Sometimes above works and we are able to scan/see the node in unprovision list  of mesh APP. 

4. But sometime when we reset (unprovision) the node it is not coming back in unprovision list neither we are able to scan/see  it anymore.which is almost dead state for us because we are no longer able to see and connect it.

This has become show stopper for us because even after power cycle we are not able to discover it. 

Waiting for your immediate resolution and support.

Regards,

Ram

[Robin M Saltnes]

Hi Ram, 

Depending on the firmware you're running on the nodes it may not have been designed to put the nodes back into "provisioning mode" after a reset in the app. The easiest way to get the nodes back this state would simply be to re-upload the firmware to the nodes.

The alternative would be to rewrite the firmware code to enable a function where the nodes goes back into "provisioning mode" after being reset in the app. 

Best regards, 

Robin

[ramachandra]

Hi Robin,

  As mentioned in my previous message in point 3 we are having the supporting firmware to unprovision the node and it is working.

As mentioned in point 4 the actual problem is sometime the unprovision fails  (say out of 10 tries 2 times fail) after that the node is not visible in either provision or unprovision list.

Even when we power cycle the module it is not even visible in nRF connect APP. It means the BLE chip is DEAD and no more it is accessible from any BLE APP. 

Observation:

    During unprovison we have the function call mesh_stack_config_clear() to clear the mesh information, during the execution of this function we observe that the BLE chip is resetting because of which the unprovision might be not happening properly.

Please let us know how we can handle it.

Regards,

Ram

[Hung Bui]

Hi Ram, 

It seems that you are using pretty old SDK, most likely SDK v2.2.0. 
I suggest you to move to latest SDK.

If it's not possible you may need to test with our example and check if you get the same issue or not.  Note that when you debug you need to set optimization level to 0 and debug level to 3. 

[ramachandra]

Hi Hung,

   Sure we will try with the new Mesh SDK version 4.2 and check it out once.

   But does this SDk support for configuring both Generic On OFF Server and Generic On Off Client model in same binary image as shown in the below snippet.

  Because i remember before using the proxy sdk( which we are using currently) we use to have two separate binary images one for configuring the Generic On OFF Server and one for Generic On Off Client( We use to get only 1 option under Element)

Please suggest if anything i am missing.

Regards,

Ram

  

[ramachandra]

Hi Hung,

    We have observed the issue that the Exception is getting generated when the BLE APP which is connected to the BLE chip is is closed all of a sudden, It is generating the exception, Please find the snippet below for the call stack and the error

Regards,

Ram

[ramachandra]

Hi Hung,

  We tried the BLE Stack for resetting the Mesh Node(Unprovisioning). It looks like when we reset with the Nordic Mesh APP the node is resetting perfectly without any issue Everytime.

But when we try to reset using the node by our application which inturn calls the same code which is called by the push button (Screenshot below) he node is not resetting. 

 

Code In PUsh Button Handler to reset the node.

Node in Our Application

Please let us know is there call back function which can be used to reset the node in the similar fashion how the Mesh APP is resetting.

 Or could you please specify the sequence of function call during the Reset of Node when Done through Mesh APP

Regards,

Ram

[Hung Bui]

Hi Ram, 

When you mentioned "the node is not resetting" what exactly happened ? Did the node reset (re-booting) ? Did the node erase bonding ?
When you see an issue you would need to debug it. We can't really tell what could be wrong by just looking at your screenshots. 

What the function does is to stop proxy function (disconnect from the phone) the erase the mesh provisioning, configuration data. After the flash erasing is stopped the device is reset. 

Please try to compare the same process when  you test using the light switch server example with your application to see why it doesn't work as it should.