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 Many-To-One affect OAD?

Other Parts Discussed in Thread: CC2530

I'm running ZStack 2.5.0 on a CC2530 platform. I have a server (PC), coordinator/gateway and 65+ routers. In my application, the routers do not communicate with one another, except during OAD. I was looking at adding Many-To-One in the ZStack Developers Guide and was wondering if this feature would affect OAD, since I have parents (and uncles per se) upgrading children.

I would guess that as long as a node was a neighbor to the child, OAD would work fine. Is this correct?

From ZStack Developers Guide:

Many-to-one routing is a special routing scheme that handles the scenario where centralized traffic is involved. It is part of the ZigBee PRO feature set to help minimize traffic particularly when all the devices in the network are sending packets to a gateway or data concentrator. Many-to-one route discovery is described in details in Section 5.4.

  • I don't think many-to-one works in your case if you want peer to peer router msg exchange via unicast, AODV type of regular routing is more useful.

    However, based on your application, it seems a broadcast scenario is better.

    Rui

  • Rui,

    This would occur only during a firmware update using over the air download.  Under normal conditions the router is only communicating with the gateway/coordinator.  If the client OAD is being update by a neighbor (OAD server) such as the parent, then the destination address should be located in the neighbor table. I would think that many to one would not interfere with this.

    From the ZStack Developer's Guide

    When a router receives a unicast packet, from its application or from another device, the NWK layer forwards it according to the following procedure. If the destination is one of the neighbors of the router (including its child devices) the packet will be transmitted directly to the destination device. Otherwise, the router will check its routing table for an entry corresponding to the routing destination of the packet. If there is an active routing table entry for the destination address, the packet will be relayed to the next hop address stored in the routing entry. If a single transmission attempt fails, the NWK layer will repeat the process of transmitting the packet and waiting for the acknowledgement, up to a maximum of NWK_MAX_DATA_RETRIES times. The maximum data retries in the NWK layer can be configured in "f8wconfig.cfg". If an active entry can not be found in the routing table or using an entry failed after the maximum number of retries, a route discovery is initiated and the packet is buffered until that process is completed.