Campbell CR800 Spécifications Page 306

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 324
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 305
Section 14. PakBus Networking
14-22
14.5 Network Troubleshooting
Symptom Possible Causes Cures
PakBus address in Device
Map disagrees with CR800’s
PBA.
Configure the same
address.
Allow time for
previous link to time
out based on its
communication
verification interval
(this won’t work in
the case of an
infinite verification
interval; see 14.3.8).
LoggerNet doesn’t
connect to in-range
CR800 in its device
map.
After the CR800 switches to
a different port LoggerNet
still has a link in its routing
table via the original CR800
port.
Using PakBus
Graph, do a Reset
Node and a
Broadcast Reset to
reset LoggerNet’s
and the CR800’s
routing tables (resets
routing tables of
LoggerNet and all
nodes that are
neighbors to
LoggerNet).
LoggerNet doesn’t
connect to in-range
CR800 via RF4xx
link.
LoggerNet Setup’s
PakBusPort Maximum Baud
Rate is set at some baud rate
other than the RF4xx’s 9600.
Change PakBusPort
Max Baud Rate to
match RF4xx.
Some radio has wrong Hop,
Net, Radio, Standby, Retry,
Protocol (RF401), or Active
Interface setting.
Configure all
network radios to
same Hop, Net,
Radio, Standby
settings. Verify all
settings.
Router has no neighbor filter
or beacon allowing it to
become a neighbor to the
destination CR800.
Enable beaconing or
install neighbor filter
in the router listing
destination CR800 as
a neighbor allowed.
LoggerNet doesn’t
connect to CR800
through a router in
RF4xx network.
Destination CR800 has
neighbor filter disallowing
(not listing) router comms.
Remove neighbor
filter from leaf-node
CR800 or list router
in neighbors
allowed.
Vue de la page 305
1 2 ... 301 302 303 304 305 306 307 308 309 310 311 ... 323 324

Commentaires sur ces manuels

Pas de commentaire