Campbell Scientific CR1000 Measurement and Control System - Manual (Page 356)

Section 8. Operation
356
8.5.4.2 Ping
Link integrity can be verified with the following procedure by using
PakBusGraph Ping Node. Nodes can be pinged with packets of 50, 100, 200, or
500 bytes.
Note Do not use packet sizes greater than 90 when pinging with 100 mW radio
modems and radio enabled dataloggers (see the appendix Telecommunications
Hardware
).
Pinging with ten repetitions of each packet size will characterize the link. Before
pinging, all other network traffic (scheduled data collections, clock checks, etc.)
should be temporarily disabled. Begin by pinging the first layer of links
(neighbors) from the PC / LoggerNet router, then proceed to nodes that are more
than one hop away. Table PakBus Link-Performance Gage
(p. 356)
provides a link-
performance gage.
Table 85. PakBus Link-Performance Gage
500 byte
Pings Sent Successes Link Status
10 10 excellent
10 9 good
10 7-8 adequate
10 <7 marginal
8.5.4.3 Traffic Flow
Keep beacon intervals as long as possible with higher traffic (large numbers of
nodes and / or frequent data collection). Long beacon intervals minimize
collisions with other packets and resulting retries. The minimum recommended
Beacon Interval setting is 60 seconds. If communications traffic is high, consider
setting beacon intervals of several minutes. If data throughput needs are great,
maximize data bandwidth by creating some branch routers, or by eliminating
beacons altogether and setting up neighbor filters.
8.5.5 LoggerNet Network-Map Configuration
As shown in figure Flat Map
(p. 356)
and figure Tree Map
(p. 357)
, the essential
element of a PakBus ® network device map in LoggerNet is the PakBusPort. After
adding the root port (COM, IP, etc), add a PakBusPort and the dataloggers.
Figure 109: Flat Map