
PakBus Networking Guide
52
removed from its neighbor list. The same removal procedure will happen in the
other device.
When a network route’s neighbor list changes (either neighbor added or
neighbor removed), it then shares that information with other routers. This
behavior fundamentally drives the network routing process.
A device with a neighbor always has an associated communications verification
interval. If a device has several neighbors, each link has a separate
communications verification interval.
When one device establishes another device as a neighbor, it also learns the
port through which it communicated with that neighbor. Although not
displayed, the com port is included in the device’s neighbor list.
Neighbor List
A PakBus device actively updates its list of neighbors. Regular normal
communications between devices is sufficient to preserve their neighbor status.
If a device hears a directed packet (addressed to the device) from a neighbor
within 2.5 × the CVI, it will not need to otherwise communicate with that
neighbor. If the time expires without hearing from the neighbor, it will initiate 4
hello message exchanges before giving up and removing the device from its
neighbor list.
Whenever a router experiences a change in its neighbor list, it sends its new
neighbor list to other routers in the network enabling them to update their
routing tables.
Part of a neighbor list entry is the com port (02, 17, 18 or RS-232) through
which to communicate with a neighbor. In order to send a packet to a neighbor
you must have not only the correct PakBus Address, but also the correct port
(matching your communication peripheral’s port setting) leading to the
neighbor device.
A “neighbor” is indicated in a *D17 Routing Table by the fact that there is a
single PakBus Address present before the hop metric response time. For
example, if device 0003 is a neighbor to a datalogger, the datalogger’s routing
table will look like this:
01: 0003 PakBus Address of destination node
01: 1.0000 worst case response time in seconds
Although *D17 shows neighbors, in the case of multiple peripherals it does not
show the ports used to access the respective neighbors. The port used is a
function of the P190, neighbor filter, etc. used to discover the neighbor.
7.4 Discovery and Removal of Neighbors
Neighbor filter hello-ing, beaconing or any form of directed communication
(such as P190) can be used to discover a datalogger’s neighbor. This is
followed by a hello-exchange to pass communications verification intervals so
that any unresponsive neighbor can be deleted. The *D18 beacon is the simpler
of the two methods to configure. More setup is required for a *D19 neighbor
Comentarios a estos manuales