
PakBus Networking Guide
54
Once nodes establish themselves as neighbors, if a node does not hear from the
other (either by beacon or by addressed communication) within the
communications verification interval established in the hello exchange × 2.5,
then that node will issue a hello message (up to 4 times if unsuccessful) and
delete that node from its neighbor list if the hello message is not answered.
A node will ignore a certain neighbor device’s beacons and only listen to
addressed communications from that device if the node’s own beacon interval
is more than 3 times the neighbor device’s beacon interval.
A node always responds to a directed packet, even though it may not come
from a neighbor.
If the beaconing device is a potential neighbor of a certain device with neighbor
filter, that device will respond.
A non-beaconing node can initiate a hello message to a beaconing node unless
the non-beaconing node has a Neighbor Filter (and the beaconing device has
the normal PakBus Address < 4000). This is so that a beaconing node can be
sure to discover a non-beaconing node.
Beacon Interval
You configure LoggerNet’s beacon interval by clicking on “PakBusPort” in the
Setup device map. To set a datalogger’s beacon interval you use *D18 with the
keyboard/display or Edlog’s Options, PakBus Settings. If the datalogger is
already programmed for beaconing you will see a non-zero value in *D18
window 01, 02, 03, or 04. The window to which you input the beacon interval
selects either a CSDC 7, CSDC 8, Modem Enabled, or RS-232 port for the
beacon. You program an NL100’s beacon interval in NL100 Edit mode using
Telnet (see NL100 manual for details).
When doing scheduled collections, the rule-of-thumb is to make the beacon
interval less than the scheduled collection interval. However, to minimize
beacon caused delays in the middle of large data transfers, the LoggerNet
beacon interval should be greater than the time it takes LoggerNet to collect
each scheduled collection. For example, 5 minute scheduled data collection and
1 minute beaconing should work if data collection takes less than 1 minute.
7.4.2 Neighbor Filter
A way to discover neighbors without beaconing is to set up Neighbor Filter
potential neighbors. Knowing who a datalogger’s neighbors are going to be,
you can list them. You can include these settings in the datalogger’s program
using Edlog’s PakBus Settings, or directly using *D19. When you set up a
neighbor filter the datalogger will send a hello message to each potential
neighbor. If the potential neighbor responds it will be put in the datalogger’s
neighbor list.
Comentários a estes Manuais