Viconics VT7682S Application Guide - Manual (Page 10)

9
1.11. Orphan Nodes.
As such it is important to understand that HOW the network is first initially started up “may” create orphan unassigned
devices / nodes / controllers that will seem to NOT want to join the Zigbee network. Let’s first understand how an
orphan node is created. A typical example is when jobs are started on a technician desk before sending the devices /
nodes / controllers in the field for installation. Often the integration technician will power the Wireless Central Manager
– coordinator & connect it to the Workbench tool first creating & adding the WirelessTstatNetwork driver layer.
Once the WirelessTstatNetwork driver layer is up and running, they open & will start up the wireless devices / nodes /
controllers one by one on their desk and add them to their Niagara database.

They will power the first unit, add it to the database & then power it down.

They will power the second unit, add it to the database & then power it down.

And so forth up to 6 devices maximum
This will work fine for 6 devices maximum, simply because the Wireless Central Manager
– coordinator has filled its
maximum 6 give away addresses. So when the technician powers up the 7
th
device / node / controller, it will NOT be
able to join the Zigbee network…….unless one of the previous device / node / controller is powered back on also.
In order to add another 6 devices, one of the previously added devices needs to be left on. And so forth as the number
of added devices / nodes / controllers grows. If 42 devices are to be added to the network, 8 of them should be
ALWAYS powered & within connectivity range of all the others.
So how would orphan nodes appear I the field & how would you allow them to join the Zigbee network?
Please note again that this ONLY applies to the initial network start-up & that once all the devices are online to the
Niagara database, everything will operate seamlessly even on power up / down & network re-starts.
How Orphan nodes are created in the field.
Ex.: 2 small buildings are within a few feet of each other. Both have 6+ devices / nodes / controller each.
A possible case for Building B orphan nodes is as follow: Building A is first stated & sets the Wireless Central Manager
– coordinator configuration parameters for the PAN ID & Channel.
Premises:

Building A is first stated.

Yellow device / node / controller have given out its 6 addresses to other devices in building A.

Building B devices / nodes / controllers can only be connected through blue device / nodes / controller due to
maximum distance coverage.
Result:

Orange devices / nodes / controllers cannot join the Zigbee network.
Workaround to get orphan devices on the network:

Disconnect & bring one of building B device / node / controller & power it up in building A until it joins the
Zigbee network ( confirmed either at the Wireless Central Manager
– coordinator or using the status LED on
the wireless communication card of the device / node / controller.
 When the device / node / controller has joined the network in building A and is added to the Niagara database,
bring it back into building B so it can propagate Zigbee addresses to the other devices in building B.