Coap-Server Coap-Client Example / OpenThread Border Router

[ENC]

Hi,

I am developing Coap-Client and Coap-Server devices using nRf52840 dev kit. I am using ncs 1.7.1 sdk. I have a few questions.

1- I can successfully send a data received from Coap-Client to the Border Router, but after a while, the Coap-Server, the Router, declares itself as the Leader and disconnects from the network (connects back as a child device) and does not become a router again. What is the reason for this?

2- The Coap-Server device creates a different ip address each time and I have to change the address to which the coap-client will send the data. Is there a shorter way to send data to the router it connects to every time without changing the ip address in unicast without multicasting?

3- Coap client must first send data to coap-server and then coap-server must send the data it receives to Border Router, for this I made some changes in coap-server, it is working now, but a data received from Border Router is Cannot send to Coap-Client (route same order (BR-Server-Client)) , what should I do about it?

Thank you for your help!

[Sigurd Hellesvik]

Hi

Good that you managed to fix it.

From what I read onThread IPv6 addressing, I can not see any way to assign static IP Addresses.
To be sure, I have asked our developers, and will return as soon as they respond with what I learn.
If this is not possible, I find and  advise you to an alternative method in place for static addresses.
You will hear from be at latest by the end of tomorrow, at best sometime today.

Regards,
Sigurd Hellesvik

[Sigurd Hellesvik]

Hi

Unfortunately I have not heard back from my colleagues yet.
But I have pinged them, so I hope to get you an answer soon.

Regards,
Sigurd Hellesvik

[Sigurd Hellesvik]

Hi

I am not able to find any way to set static IP fot Thread devices.
However, I have not found any definitive information that it is not allowed either.
This would be in the Thread Specification somewhere.

However, since it is not a part of our Thread Configuration documentation, I assume it is not possible to set static IP addresses for Thread FTD or MTD.

To share addresses, I recommend to do partitioning, the same way our CoAP Server and Client samples.
In short, they use multicast to find their fellow nodes, then save unicast addresses for later use.

Thread network informatin can be saved in flash using the Settings API.
These settings will be removed when you erase the program on the chip (nrfjprog --erase-all).
However, for use in a product, the unicast addresses could be retained between resets and power-offs.

Regards,
Sigurd Hellesvik