Campbell RF410 Bedienerhandbuch PDF herunterladen (Seite 69)

PakBus Networking Guide

If there is no beaconing in the network, LoggerNet can connect to CR10XPB_1

because it is in LoggerNet’s static routes. If CR10XPB_1 does not have

CR205_2 in its neighbor list, LoggerNet’s routing algorithm cannot route

toward CR205_2. By adding CR205_2 to CR10XPB_1’s neighbor filter

potential neighbor list, you essentially force that route to CR205_2.

If LoggerNet were beaconing, it could discover CR205_2 directly (sometimes

creating an undesirable, weak rf link).

If you had the following device map (un-represented RF400 Series are

assumed):

With LoggerNet not beaconing, you can connect to CR205_2 via a static route,

only it will not be via CR10XPB but directly to CR205_2A.

Neighbor Filter Force A Path Through Router

If a datalogger has a *D19 neighbor filter, only the devices in its potential

neighbor list are candidates for neighbor. An exception is that if the datalogger

hears a PakBus node with address ≥ 4000 (normally the LoggerNet server with

PakBus Address = 4094) it will send a hello message to it and they will become

neighbors.

For example, if a datalogger has both a neighbor filter and a P190, the neighbor

filter must list the P190 addressed remote device or else the P190 will not be

able to communicate with the remote device. This is by design so that a

datalogger with P190 can be forced (by leaving the remote device out of the

P190 datalogger’s neighbor filter but including the desired router) to take the

path through the router avoiding the undesirable long path (marginal rf link) to

a remote device (see Figure 21).

1 2 ... 64 65 66 67 68 69 70 71 72 73 74 ... 123 124

Keine Kommentare

Campbell RF410 Bedienerhandbuch Seite 69