About deleting node, then configuring node failed

RE: About deleting node, then configuring node failed

JeffZ — Mon, 03 Aug 2020 08:52:21 GMT

Hi Mttrinh, thanks for advising. I created a new ticket.

RE: About deleting node, then configuring node failed

Mttrinh — Mon, 03 Aug 2020 08:46:37 GMT

Hi,

This is a really old thread, I suggest you create a new ticket for this issue and we will handle it there.

RE: About deleting node, then configuring node failed

JeffZ — Fri, 31 Jul 2020 12:57:24 GMT

Hi guys,

I have the same issue as coca1989 had 2 years ago. Did anybody found a solution?

I am using health model and simple message model. Client and Provisioner are running on one device (demoboard). I can provision and configure upto 5 server nodes (dongles). I get health events from each connected server (all 10 seconds) and I can send and receive small messages on all server nodes.

Now, I would like to remove nodes from the mesh network and reconnect them (reprovisioning and reconfiguration). This are the steps that I am doing:

config_client_server_bind() and config_client_server_set() to the server node I would like to remove from network
config_client_node_reset()
the server gets the node reset event (CONFIG_SERVER_EVT_NODE_RESET) from client and performs node_reset() with: mesh_stack_config_clear() and mesh_stack_device_reset()
the server responds to the client with CONFIG_CLIENT_EVENT_TYPE_CANCELLED and I do dsm_devkey_delete()

After removing the server node, I can reprovision and reconfigure the node successfully (getting health events and send/receive messages). But the configuration takes longer then the first time. Repeating this process (removing node and reconnecting) increases the configuration time each time.

Here is a time table:

First configuration: 2-3 seconds
Second configuration (after removing node from mesh): 10-11 seconds
Third configuration (after removing node from mesh):20-30 seconds
Fourth configuration (after removing node from mesh): 45 -50 seconds
Fifth configuration (after removing node from mesh): >80 seconds

This is reproduceable. Rebooting the client/provisioner device after removing a server node reduces the configuration time back to 2-3 seconds, but I do not get health events and no messages.

During reconfiguration (after removing the server from network) I am getting SAR mesh events on the server node. At the first configuration (fresh device) I dont have this SAR events.

I guess I have to delete more on client side? Maybe the simple message or health is still active on the last address handles?

RE: About deleting node, then configuring node failed

Sash — Mon, 29 Jul 2019 15:43:21 GMT

caca1989,can you please tell me how to re-provision the node to same address.

RE: About deleting node, then configuring node failed

Mttrinh — Thu, 15 Nov 2018 11:32:15 GMT

Can you try to debug the code, set some breakpoints and see why it fails. See if you get any error code when it fails?

Also, can you do a flash dump so we can see what is in the flash? Yuo can do this by using nrfjprog:

Use this command, nrfjprog --readcode --readuicr filename.hex

RE: About deleting node, then configuring node failed

caca1989 — Wed, 07 Nov 2018 01:38:16 GMT

Yes, each configuration time is longer than the last time until the configuration fails, you can refer to my log

RE: About deleting node, then configuring node failed

Mttrinh — Tue, 06 Nov 2018 15:42:48 GMT

[quote user=""]Repeat more than ten times, the configuration will fail[/quote]

Does it always take more than ten times before you see this issue?

RE: About deleting node, then configuring node failed

caca1989 — Wed, 31 Oct 2018 01:33:52 GMT

Hi，

Thank you for your reply!

But my problem is not solved.

Deleting a node and configuring a node is successful, but multiple such operations will fail

RE: About deleting node, then configuring node failed

Mttrinh — Tue, 30 Oct 2018 15:39:42 GMT

Hi,

Can you have a look at this post and see if this helps you?