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.

Desgnate short address?

Other Parts Discussed in Thread: Z-STACK, TIMAC

Hi all,

 

I have a simple question, but i can't figure out how to do it.

I'm using Z-Stack 2.5.0 on cc2530eb,  ZigBeePro stack profile.

I want to designate short address on routers and end devices, but not randomly generated by parent device.

Can z-stack support this function? 

Can TiMac or other stack support this function?

 

Regards,

Douglas

 

 

 

 

  • Hi,

    I don't know how to do that with TI's stacks, but you could do that using Atmel's ZigBee stack (BitCloud). The main problem is that you may want to work with TI chips...

    Yoann Hilairet

  • Thanks for your reply, but I really need to use TI's stack.

    Anyone has ideas?

  • Hi,

     

    Let's take a different approach, what is the reason you want to designate short addresses

    to devices?

    Why the stochastic addressing approach implemented in (Z-stack) ZigBee-PRO doesn't

    satisfy your design/project?

  • Hi~

     

    Because I want to design a method:

    let users transmit their serial data to the designated destination.

    The destination can be configured through serial data

    but not depend on the bind operation through push button.

    If I cant designate the short address to some ZigBee devices,

    I think it's really hard to satisfy these requirement.

     

     

    Regards,

    Douglas

  • IEEE address, which is unique per ZigBee device won't do the trick?

    Here's some sort of scenario:

    1. Assume that user "knows" what is the IEEE address of serial data destination
    2. IEEE can be translated (locally, or through the nodes in the network) to short address
    3. Upon receiving the short address based on IEEE address, the serial data will be sent
      to it's destination.

    The cons of this scenario are:

    1. The assumption that the user itself must know the IEEE of serial data destination.
      This means that someone, somehow must tell to the user what is the IEEE address.
    2. Can create a massive traffic in large network by searching for short address based
      on IEEE address. 
  •  

    Ya, it works with IEEE address.

    But as you know, 8-byte IEEE address is redundant for user.

    Users need to manually construct a table to remember the IEEE address of each device.

    They search the table and enter destination's IEEE address every time they want to transmit data.

    What's even worse, users can not change IEEE address by themselves.

    This design is not intuitive.

    If we can designate short address to the device, we can simply mark device number 1,2,3... (same as their short address).

    As far as i know, many ZigBee products on th market use the term "Node Id" to represent this idea.

    I think Z-Stack really need to support this function.

     

    Regards,

    Douglas

     

     

  • Hi,

    if 8-byte IEEE address is too long for operating, you can use any x-byte ID for your nodes. In any case you have to create a table of ID( or IEEE)<->ShortAddress translations. The main drawback of using own ID instead if IEEE address is that you cannot perform node search directly, i.e. by ID.

  • Hi

     

    I have done a short address to node id mapping table which causes some defects:

    1. It needs lots of memory space to store this table in large network.

    2. Dynamically updating this table is not stable and resource-wasted.

    3. User may be confused when they sniffer the packet.

     

    Regards,

    Douglas