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

Section 14. Troubleshooting Guide
include the remote datalogger’s address. Whether you set up a
beacon or Neighbor Filter make sure the port so configured matches
the communications device port configuration. For example, if the
selected neighbor filter port is “17”, make sure that the RF400 Active
Interface is “CSDC 7.”
Possible reason 3: An RF400 Series radio is set to a different
Hopping Sequence, Network Address, Radio Address, or Standby
Mode.
Remedy 3: Set all network radios exactly the same in the above
parameters. Network RF400s’ Active Interfaces may vary from node
to node, however, they will typically be configured for CSDC 7 or 8
except for a ‘base’ radio which is typically AutoSense or M.E..
Dataloggers automatically detect the RF400’s port (Active Interface)
for packet communications, however, the potential neighbor hello
port or beacon port must be configured to match the RF400’s Active
Interface, or no discovery of neighbors will take place.
Possible reason 4: A CR200 Series has just received an OS
download resetting network address, radio address, hopping
sequence, and radio power mode to defaults.
Remedy 4: Configure CR205 settings to agree with network.
Possible reason 5: The two routers in the path to the CR205 have
neighbor filters and at least one of the neighbor filters doesn’t list the
other as a potential neighbor.
Remedy 5: 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: Can’t LoggerNet communicate with datalogger-router in network?
(PC-RF400~~~RF400-CR10XPB~~~CR205)
Possible reason: The datalogger-router has more than one M.E.
peripheral cabled to it.
Remedy: Connect only one M.E. device to a datalogger (or change
one M.E. peripheral to CSDC 8 port).
Problem: Changed P190 port type and it no longer communicates with remote.
Possible reason: The Active Interface of the communications device
(for example, RF400 Series) no longer matches the P190 port.
Remedy: Make the communications device Active Interface agree
with P190 Parameter 1.
Problem: Rapid spurious communications lasting a few seconds at a time
between devices in RF400 network.
Possible reason: Two network devices have the same PakBus
Address.
14-18