Rejoin into network .

[mithunGhosh13]

How could i get reconnected into the same network while my device got disconnected due to some reason?

[jwhui]

Thread devices should automatically look to reconnect to an existing network.

A Thread end device will periodically look for a parent to attach to while it is detached.

A Thread router-capable device will form its own partition and become a leader if it cannot discover any other routers around. However, a router-capable device does discover another neighboring partition, the devices should attempt to merge the partitions.

[jwhui]

otInstance points to the volatile memory used by OpenThread. otInstanceInitSingle() effectively calls the constructors on the otInstance object. You should not store the otInstance object in non-volatile memory.

I suggest taking a look at the CLI example app in examples/apps/cli/main.c.

[jwhui]

As mentioned, the device will automatically retrieve the Active Operational Dataset from its parent and store in non-volatile after successfully attaching. If you want to view the Active Operational Dataset saved to non-volatile memory, you can use the otDatasetGetActive().

[mithunGhosh13]

yes, i have tried to check the stored data using otDatasetGetActive() in my code . But execution has stuck at the point where i used otDatasetGetActive() function.

[mithunGhosh13]

First thing is i am not using the CLI example code. I am using coap_client and coap_server example code which provided by nordic .
I can able to execute the CLI command with the coap example code. i can see devices are not communicating after execute CLI command mention steps in Operational Dataset Quick Start Guide. what are the next steps needs to follow?

[jwhui]

Given that this appears to be an issue with Nordic's example code, please reach out via Nordic DevZone for support.

FWIW, I am not able to reproduce your issue using the OpenThread CLI example.