Campbell Scientific LoggerNet Datalogger Support Software - Manual (Page 479)

Section 14. Troubleshooting Guide
14.8 Troubleshooting PakBus Communications
For additional information on PakBus communication, refer to our PakBus
Networking Guide (under separate cover).
Problem: LoggerNet can’t communicate with in-range PakBus datalogger
(PC-RF400~~~RF400-CR510PB~~~ RF400-CR510PB~~~CR205)
Possible reason 1: LoggerNet’s PakBus Address for datalogger
doesn’t match datalogger’s PakBus Address.
Remedy 1: Make them match.
Possible reason 2: An RF400 Series radio is set to a different
Hopping Sequence, Network Address, Radio Address, or Standby
Mode.
Remedy 2: Set both radios exactly the same in the above parameters.
(‘base’ radio’s Active Interface is typically Auto Sense, remote radio
is typically CSDC 7)
Possible reason 3: No PakBusPort in device map between root and
datalogger.
Remedy 3: Add PakBusPort.
Possible reason 4: No PakBus OS in datalogger
Remedy 4: 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.
Problem: LoggerNet can’t communicate via datalogger-router to a certain
remote datalogger.
(PC-RF400~~~RF400-CR10XPB~~~RF400-CR510~~~CR205)
Possible reason 1: A datalogger router has insufficient *D15 max
nodes, max neighbors, or max routers configured.
Remedy 1: Increase the *D15 numbers.
*D15 settings of 000x, 6, 6, 6, 0 are reasonable for a router in a
network of under a half dozen nodes
*D15 settings allocate memory similar to *A. It is a good idea, when
configuring *D15 settings, to leave ‘room to grow.’ Changing *D15
settings later on could result in loss of data as *0 is entered to compile
new settings.
Possible reason 2: Last datalogger router has no means configured of
discovering the remote datalogger.
Remedy 2: Configure the datalogger router with either a neighbor
filter or a beacon. Make sure Neighbor Filter potential neighbors
14-17