Figure 103. Flat Map
Figure 104. Tree Map
The difference between the two configurations is that the flat map configures the
router with static routes that report that all of the dataloggers are neighbours to the
server. The tree map configures static routes wherein "CR1000" is configured as
a neighbour and "CR1000_2", "CR1000_3", and "CR1000_4" are configured to
use "CR1000" as the router. Deeper nesting, while allowed, is meaningless in
terms of PakBus because PakBus does not allow dictation of the entire
communication path. You can specify the router address for only the first hop.
Within the server, dynamically discovered routes take precedence over static
routes, so once the network is learned, communications will work smoothly.
However, having the correct static route to begin is often crucial because an
attempt to ring a false neighbor can time out before routing can be discovered
from the real neighbor.
Stated another way, use the tree configuration when communication requires
routers. The shape of the map serves to disallow a direct LoggerNet connection to
CR1000_2 and CR1000_3, and it implies constrained routes that will probably be
established by user-installed neighbor filters in the routers. This assumes that
LoggerNet beacons are turned off. Otherwise, with a default address of 4094,
LoggerNet beacons will penetrate the neighbor filter of any in-range node.
399
To Next Page
Loading...
Need help?
General
