Is there a "Good Practice" in Scanning a network?

When I am going in a site to scan a network for the very first time I am having problems to scan all units in network. Usually toolkit prompts an error like "Unable to scan network" when unravel is completed.
The way I found to proceed is to scan few din rail units, then I am giving address 1 in a unit, enabling burden and C-Bus clock and afterwards I scan again the network crossing my fingers to make it work.
I am wondering if this problem is occurred because I have too many new switches (all in address 255 from the factory) in the network or am I doing something wrong?

 

All units at 255 shouldn't be a problem. However no burden on a small or medium size network is a common scan killer. If you have hardware burden, it's a simple solution to this problem. In case if you don't have it you need to find through the initial scan a unit with the software burden in it, preferably other than local PCI, put it at address 1 and turn on its software burden. Network scan should be more reliable after this.

There are other issues to watch out, too. For example, not enough power on the network, too many units that have C-Bus Clock enabled or units at the same address as local PCI. Also scan can fail if you are adding/removing units while it is in progress.

George