
Section 14. PakBus Networking
14-24
neighbor list unless the beaconing device’s address is ≥
4000 (normally LoggerNet).
Beacon Interval
User assigned interval between broadcast beacons.
Beacon Interval
SDC7
Same as BeaconSDC7. The CR800 setting of the
interval between broadcast beacons.
Branch Router
Typically an RF401 configured as a stand-alone router.
A branch router has a reduced view of the network and
strives to know only the neighbor lists of central
routers, routers between the central routers and itself,
and routers outward from itself in the network.
BMP5
Block Mode Protocol 5. The datalogger application
layer packet protocol used in PakBus communications.
High-level BMP5 communications transfer such things
as programs, data, and clock checks.
Broadcast
Sent to all PakBus devices in the network.
Buddy
The single quasi-neighbor of a CR2xx. After acquiring
a buddy, the CR2xx ignores all further broadcast
packets so long as communications verification is
current. RF traffic is thereby minimized. A CR2xx with
a buddy will continue to respond to any packets
directed to it.
Central Router
A router (for example, a CR800) that is in a network
with RF401 branch routers which have a reduced view
of the network. A branch router only strives to know
the neighbor lists of the designated central routers, the
routers between the central routers and itself, and the
routers that are outward from itself in the network.
Client
In client-server architecture, a client is typically an
application that runs on a personal computer that relies
on a server for resources to perform certain operations.
PakBus examples: Setup, ConnectScreen, and
PakBusGraph are clients to the LoggerNet server.
Comms
Short for communications.
Communications
Verification
Interval
The period of time that a PakBus device uses to
determine when it’s time to send a hello message to
confirm that a neighbor can still respond (and remain a
neighbor). Verification intervals are passed in hello-
exchanges.
Com Port
Com port is used interchangeably with “active
interface” in regards to communication peripherals and
dataloggers.
Komentarze do niniejszej Instrukcji