Campbell RF410 Manual de Instruções descarregar pdf (Página 72)

PakBus Networking Guide

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.

8.2 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 (see *D15 Set PakBus Address and Routing Table,

Section 4.1.2.1).

*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 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.

CAUTION

1 2 ... 67 68 69 70 71 72 73 74 75 76 77 ... 123 124

Sem comentários

Campbell RF410 Manual de Instruções Página 72