[BitCloud] Coordinator/Router rejoin questions

Go To Last Post
3 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

hello,
I've read some threads about how to handle connection lost for routers now. So the app has to handle this similar to WSNDemo with a error threshold and leaving/rejoin the network if its too large.

But how to handle this for coordinator? I got a C -> R -> E network. Now after just turn off the R, C seems to be in a helpless state too? (all zdp responses on C have status e9, d0 and so on). The network it self seems to be up, since other devices could connect.

What would be the right way to proceed? Full leave and rejoin for coordinator like routers in WSNDemo do or is there a 'soft way' without breaking connection to devices still connected?

Last Edited: Fri. Oct 16, 2015 - 02:31 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

manuelp wrote:
But how to handle this for coordinator? I got a C -> R -> E network. Now after just turn off the R, C seems to be in a helpless state too? (all zdp responses on C have status e9, d0 and so on).
Responses on what request? As soon as ED will reconnect ZDP requests to the ED will return correct codes. If ED does not reconnect then it is out of the network.

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The request was IEEE_addr_req and Mgmt_Lqi_req. But it seems the problem is just temporary (or not a problem at all :)). After a while the network works again without resetting the coordinator. I guess it just takes some time until the neighbor tables get rid of gone nodes.