• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 510 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.

Does new short address mean an new entry in association table?

Andrew Bakin
Expert 1635 points
Other Parts Discussed in Thread: CC2530, Z-STACK

(Z-stack Home 1.2.1 CC2530)

Hi,

Question 1) If an End Device is issued a new short address, does it get a completely new entry in the Association Table?

Question 2) If the answer to Question 1 is yes, then how to a force a Child (ZED or ZR) to generate/be issued, a new short address?

I am trying to force a new entry in the Coordinator Association Table when an End Device re-parents to a Router. I know Child Aging does this but I need to make it happen as soon as a device re-parents, and not wait for KEEPALIVE timeout value of Child Aging. Setting Child Aging to 0 causes way too many Leave Requests.

Also, I don't use the Short Address in my application, I use the IEEE instead, so it can change with no impact.

(Alternatively, is it possible for the Child Aging timeout value to be dynamically changed? I have tried this but to no avail)

Thanks,

Andy

  • 0
    TI__Genius 9180 points

    The only safe way I know of making a Device get a new short address is to send it a LeaveReq, this is because the Short address is assigned during Association to the network.

    Another case where a device will change its short address it if there is a address conflict, addresses are assigned randomly, so there is a chance a device can be assigned an address already used. Maybe sending a "fake" Device Announce with the child's short addr will force addr conflict resolution, but that sounds like a hack and there could be other dangerous side effects.

    Regards, TC.

  • 0 in reply to TopCat
    Expert 1635 points

    Hi TC,

    Thanks for the response. I have tried in vain to get my Z-Stack working the way I need it to and have thus far failed at the final hurdle.

    Can I please make a request to TI that there be an option whereby a Child's entry in the ZC Association Table be removed if the ZC receives a message from that Child but through a Router? I am using Many-To-One Routing, and I don't see why this functionality wouldn't be part of that use case.

    This would solve all my problems and I can't imagine the code to be hard to implement. This way I don't have to fudge Child Ageing to accomplish this, and it can be left to do it's job properly. In any case, I need the process to be quicker than 2 1/2 minutes which is the fastest I can get Child Ageing to age out a node without having lots of Leave Requests.

    Regards,

    Andy