• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 57 subscribers
  • Views 287 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LAUNCHXL-CC26X2R1: Coordinator recycle the short address for End-Device

Lawrence Lin
Genius 4755 points
Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: Z-STACK

Hi TI team,

I have two LaunchPad of CC26652. One is End-Device(Switch example code). Another is Coordinator(Light example code).

I know my Coordinator will randomly assign a short address to my End-Device when my End-Device join with my Coordinator.

I want to know whether my Coordinator will recycle the short address that already assigned to my End-Device when I clean/reset the zigbee configuration on my End-Device?? 

Thank you very much

  • 0
    Guru 735685 points
    As I know, it won't recycle the short address that already assigned to your End-Device when you clean/reset the zigbee configuration on End-Device.
  • 0 in reply to YiKai Chen
    Genius 4755 points

    Hi YK,
    Could I know when these short address that already assigned will be recycled? Such as reset the Coordinator? or A periodic time?
    I think if coordinator will not recycle short address that already assigned, short address in coordinator will be not enough for End-Devices.
    For example, I may reset my End-Device many times. And each time I get different short address.
    Or
    my concepts are wrong?
    Thanks

  • 0 in reply to Lawrence Lin
    Guru 735685 points
    You can read Zigbee spec for details about short address assignment.
  • 0 in reply to YiKai Chen
    TI__Guru**** 218567 points

    Stochastic addressing assigns a random address that does not already appear in any entry in the parent's NIB. Therefore, short addresses which have been removed from the network are valid for re-use. Device Announces messages are further used by joining devices to ensure that there are no address conflicts, but once again re-assignment is completely random based on what is already known about the network.  You can find more information in "3.6.1.7 Stochastic Address Assignment Mechanism" section of the Zigbee Specification or "3.2.1 Stochastic Addressing" in the Z-Stack Overview section of the Z-Stack User's Guide.

    Regards,
    Ryan