Campbell Scientific PakBus Networking Guide - Manual (Page 21)

Appendix A. Entering CR10X-PB
PakBus Settings with a Keyboard
Display
If using a keyboard display to enter PakBus settings, they can be configured
using *D settings anytime after downloading a PakBus operating system to the
datalogger and either before or after sending the program to the datalogger.
Pressing *0 recompiles the datalogger and saves the *D settings to FLASH
memory. Current PakBus settings will persist through a new program send as
long as the new program does not contain PakBus settings that were entered in
Edlog.
*D15 The PakBus Address and Routing Table Creation
Collect any wanted data before typing *0 to save *D15
edits to FLASH because final storage data is cleared! CAUTION
*D15 settings allocate memory similar to *A. It is a good
idea when configuring them to leave “room to grow.”
Changing *D15 settings later on could result in loss of
data.
Set the PakBus address and routing table information of the datalogger by
entering the following settings:
*D15 :nnnn The PakBus address from 1-4094. Remember that
each node on the network must have a unique PakBus
address. Avoid PakBus addresses used by support
software and be careful with PakBus addresses larger
than 3999 if using allowed neighbor lists.
01 :nnnn The maximum number of nodes in the network. Enter
0 if the datalogger is a leaf node and make sure to enter
a non-zero number if the datalogger is a router.
02 :nnnn The maximum neighbors for this node. The maximum
must be a non-zero number.
03 :nnnn The maximum routers in the network and must be non-
zero.
04 :nnnn The default router’s PakBus address. Used so that
packets can be passed efficiently through the network.
If a device is unable to find a route to a destination in its routing table, and it
has a default router address configured, it will send the packet out via the
default router.
If in doubt about how large to make max nodes, neighbors, or routers in the
datalogger configuration, guess a little high. Setting these values too low can
be catastrophic if it means required routes are missing from lack of space. The
following table shows how datalogger memory usage rises per the square of the
number of routers.
A-1