Campbell RF410 Manual de instrucciones descargar pdf (Pagina 61)

PakBus Networking Guide

The advantage of Neighbor Filter over beaconing is that you avoid generating

the periodic rf activity, and the possibility of rf collisions so long as there is

some kind of communications within the interval you set, such as a scheduled

data collection. More importantly, a neighbor filter avoids selecting marginal rf

routes.

The disadvantage of having a Neighbor Filter is that if a potential neighbor

fails, the datalogger who lists the failed device as a potential neighbor will

continuously send brief hello messages to the failed device at random 1 to 15

second intervals. If this happens, you can use Edlog \ Options \ PakBus Settings

to prepare a program to delete the failed device from the datalogger’s potential

neighbor list until you repair or replace the failed device.

Neighbor Filters provide a way to force a certain route. When beaconing you

can’t control who answers and what links are established. With Neighbor

Filters you can limit what links are established and, thereby, control the routes

followed in the network.

If a datalogger has a Neighbor Filter configured, only the devices in the

potential neighbor list are candidates for neighbor, with one exception: if a

device with Neighbor Filter is addressed (or beaconed) by a node whose

address is ≥ 4000, it will treat that node as a potential neighbor. This is so that a

datalogger with Neighbor Filter can have LoggerNet, with default PakBus

Address of 4094, in its neighbor list even though LoggerNet is not in its

potential neighbor list.

If you have two in-range routers using neighbor filters, in order for them to

discover one another you must list each of them as a potential neighbor in the

other’s neighbor filter. Any device with neighbor filter will ignore hellos unless

from a device that is on its list of potential neighbors (or has address ≥ 4000).

If a datalogger has both a Neighbor Filter and a P190, the Neighbor Filter must

contain the P190 addressed remote device or the P190 will not be able to

communicate with that device. This is by design so that a datalogger with P190

can be Neighbor Filter forced (by leaving the remote device out of the

datalogger’s Neighbor Filter, but including the desired router in the Neighbor

Filter) to route through a router rather than directly connect via marginal rf link

to a remote device.

If you have previously set up a Router Table in *D15, when you configure

Neighbor Filter settings the datalogger sends potential neighbors a hello

message. If they respond, the potential neighbors become neighbors enabling

the datalogger to communicate with those devices.

A datalogger’s neighbors can be observed by viewing the datalogger’s Routing

Table. This is accomplished by keying in *D17 and pressing “A” repeatedly to

see the table entries. A route consists of 3 lines in the table. If the first two

windows of a route contain the same PakBus Address, that device is a neighbor

to the datalogger. For example, if device 0003 is a neighbor to the datalogger,

the datalogger’s routing table will look like this:

1 2 ... 56 57 58 59 60 61 62 63 64 65 66 ... 123 124

Comentarios a estos manuales

Sin comentarios

Campbell RF410 Manual de instrucciones Pagina 61

Comentarios a estos manuales

Relacionado con productos y manuales para Redes Campbell RF410