• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 56 subscribers
  • Views 340 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.

Is it possible to freely assign short address for a router in z-stack 1.4.3-1.2.1?

"Henry"
Intellectual 675 points
Other Parts Discussed in Thread: Z-STACK, CC2430

Dear all,

I found current short address assignment method in z-stack 1.4.3-1.2.1 is not suite for the production environment which has big amount nodes.

Is it possible to write short address and related data table into CC2430 chip NV memory space, then next reboot it will "recover" the net status from NV. In addition, disable all router's and coordinator's ability for FFD child address assignment. so, we get full customized short address control.

Please advise, thanks for any comments.

Happy new year!

Henry

  • 0
    TI__Expert 4155 points

    Henry, no it is not possible to assign fixed short addresses. This isn't how cskip address assignment works in Zigbee 06. Why do you say that this address scheme is not suitable for a large network?
    Sure, there is the depth limitation, but the cskip settings can be tweaked to maximize depth. So far, in the deployments that we have, we haven't run into any depth issues. What size network are you talking about? I think a network of 100-200 nodes, cskip is fine. The depth issue comes into play if you're covering a REALLY large physical area.

  • 0 in reply to "Double 0"
    Intellectual 675 points

    Mr. Zed,

    As you said, we cannot control short address assignment in Zigbee 2006. In a large network, when the up-level nodes goes failed, we must replace it, we cannot use the short address again to avoid duplicated address. it causes the next level address space waste.

    My suggestion is do NOT use NV_RESTORE in large network, because we always can use reboot method to solve many network issue. With NV_RESTORE we can do nothing.

    Henry

  • 0 in reply to "Henry"
    Intellectual 295 points

    Hi,

    I have a questions about the difference between the BasicRf and the z-stack!!

    1/ I want to send a message for an unique node in my network with the BasicRF by specifing the unique address may be the IEEE address (can I send message with the 64 bits address???

    2/- can I send in the broadcast mode basicRfSendPacket(LIGHT_ADDR, pTxData, APP_PAYLOAD_LENGTH); with the modification of the LIGHT_ADDR by 0XFFFF??!!

    3/- for the z-stack I can't see the process events from the RX:TX interrupt!! can you give me a short description about the process of the Radio fonctionality

    4/ can I just use the basicRf with a messaging to a specific node so with the 64 bits addressing

    Tks

  • 0 in reply to "Henry"
    TI__Expert 4155 points

    Henry,

    It's really NOT recommended to NOT use NV_RESTORE because you cannot guarantee if a router node in the network will never be power cycled. When it gets power cycled, it loses all knowledge of which short addresses it previously assigned and you run a huge risk of getting duplicate short addresses being handed out. If you need to bypass NV_RESTORE, you should look at implementing an application level algorithm to use zgWriteStartupOptions() to set the device back to a default network state. However, you have to do this for every router in the network. Prior to doing that, the end devices need to be told to be in a "hold" state, so that they don't rejoin a router in the process of forgetting it's NV.

  • 0 in reply to moon9903
    TI__Expert 4155 points

    moon,

    I think you should start a new thread with your questions. Thanks. Btw the whole idea behind a protocol like Zigbee is to abstract the user with having to know all the low level radio details.