• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 1537 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

How can root/coordinator know if a enddivice leave the network?

winson wu
Prodigy 80 points
Other Parts Discussed in Thread: Z-STACK

hi all,

I was working on a locating project about ZStack-CC2530-2.3.0-1.4.0.   Now a problem come, we need know all the point in the network(both RT(root) and ED(enddivce)),

so i should catch a new ED come or remove, i found the array of "AssociatedDevList" which can show whether a new piont come(father node do ), but i can not found a effect  measure to catch the information  when a ED or RT is left(father node)?

 

And  i aslo want to know Can root use api of ZStack-CC2530-2.3.0-1.4.0 manage this by its self?

 

 

I have much of misunderstanding on this topic so If anyone knows, or can

help  in some better way, 

please advise.

If you need more information, please let me know.



Thanks in advance.

 

winson_wu

  • 0
    Guru 31280 points

    Hi Winson,

     

    I have a couple of questions to you in order to clarify what kind of solution

    you are seeking:

    1. Is the leaving device notified by external source (lets say, button press)
      that it should leave the network now, or is it allowed to leave without any
      external notification? 
    2. Have you read the "Z-stack API.pdf" document? (to be more specific:
      sections 3.4.1.11 and 3.4.1.12 )?
    3. Is the ED configured to be a a sleeping device (where the RT is certainly 
      a non sleeping device)?

    Br,

    Igor

  • 0 in reply to Igor Sherer
    Prodigy 80 points

    thanks Ti

    I see your word

    1 the enddevice leave without set, it means may be work worry or other worry.

    2 now  i see the ZDP_ActiveEPIFReq i will use it tomorrow .

    i want know can coordinator catch zhe lost enddevice/root by a function?

    3 sleeping device is not related by now ...

    by

    winson wu

  • 0 in reply to winson wu
    TI__Mastermind 19350 points

    Back to the original question and proposed solution: do not use NWK/MAC layer data structures to solve and Application layer problem. The data structures mentioned are used by the ZStack NWK library to maintain neighbors, routing, etc. - i.e. to solve the mesh networking problem. Your problem is anywhere in a huge, deep, complex mesh network, how to know when a ZED appears or disappears. This is completely an Application layer problem to solve. As we know from the Two Generals conundrum in computer science, it is not solvable. But you can devise protocol at the Application layer to predict with high certainty that a ZED is active or not in the network. Start with just sending it message with APS ACK request option. The longer and longer that ZED sleep, the harder the problem becomes.

  • 0 in reply to Dirty Harry
    Prodigy 80 points

    Hi Ti

    Thanks for your help.

    i see it's a longer work , and if a ZED sleeps may be will be harder.

    Now if i do work with application layer problem to solve my problem, should i do some work with route table(rtgTable) and route discovery table(rtDiscTable),

    or only work with  AssociatedDevList?

    my idea is making some prorocol to  judge if a ZED appears or disappears, and shoud i care AssociatedDevList(add or delete ) by myself to protect the network?

    if all this is not right ,should anyone tell me the effective way ?

     

    thanks

    by

    winson