• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 57 subscribers
  • Views 3848 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.

ZigBee 16 bit short address

Kevin Lin
Expert 1445 points
Other Parts Discussed in Thread: CC2430

Hi,

  I am currently using CC2430 to develop a monitoring system based on SampleApp.  However, I am confused with the 16 bit short address.  Since I am using ZigBee 2006 protocol, addresses are assigned according to the CSKIP algorithm and each one in the network is unique.  I know that  0x796f will be assigned to first end device linked to the coordinator, and 0x7970 to second end device and so on.  However, if the link is re-established, are end devices going to get the same 16 bit short addresses as bofore?  Because I need to know exactly where the information is from, I need to assign each end device a static short address.  Can I assign end devices a short address manually?  Thank you 

  • 0
    Intellectual 330 points

    Kevin said:
    Because I need to know exactly where the information is from, I need to assign each end device a static short address.  Can I assign end devices a short address manually?  Thank you 

     

    Hi Kevin,

    EndDevices are no Mesh-Nodes. They are child nodes of their parent router. If an (f.e.: mobile node) EndDevice changes its parent router, it will get a new Network-Address from the new parent.

    For routers, You may implement your own way to assign network address. C-Skip is just needed for Tree-Routing. If you use Table-Routing only, you may implement an other way of assigning Network Addresses.

     

  • 0 in reply to OZ2550
    Expert 1445 points

    Hi OZ,

    Thank you for your answer.  I am still confused.  So I can assign every end device a short address through their parent router?  I have read somewhere on the forums that assigning the short address is implemented in the ZigBee protocol, so changing the protocol won't make my network not ZigBee compliant?  If it doesn't, where in SampleApp is C-Skip implemented?  Thank you

     

    regards

  • 0 in reply to Kevin Lin
    Mastermind 9792 points

    Why not just use the long address to determine which device to send/receive from? I've done that on a few sensor systems and it is pretty easy to do. Sometimes I have the sensor include its long address in the message that it sends to be sure I know where it's coming from.

     

    --Derek

  • 0 in reply to Derek
    Expert 1445 points

    Hi Derek,

        Thank you so much for your tips.  However, I am still confused about the short/long address.  Isn't the long address for the entire ZigBee network, which means every ZigBee device has the same long(MAC/Extended) address?  Please help me clarify this.  Thank you 

  • 0 in reply to Kevin Lin
    TI__Expert 5255 points

    PanID - the same for all devices in a network, assigned by the network coordinator

    Short Address (NWK) - unique for each device in a network, assigned when it joins the network

    Long Address (IEEE) - unique for each device, usually assigned by a manufacturer at the factory, never changes

  • 0 in reply to Derek
    Expert 1925 points

    Hi, Derek,

    I wonder how you did that, i am trying to use the long address in zcl_SendRead, but seems it can't work(I set a breakpoint at where to get a SendRead message, but it never reach there)

    Derek said:

    Why not just use the long address to determine which device to send/receive from? I've done that on a few sensor systems and it is pretty easy to do. Sometimes I have the sensor include its long address in the message that it sends to be sure I know where it's coming from.

     

    --Derek

     

  • 0 in reply to zhu
    Mastermind 9792 points

    I don't know, I've never used any of the ZCL.

     

    --Derek