NOTE:
A list of Settings fieldnames is also available from the data logger terminal mode using
command F.
18.3.1 Baudrate
This setting governs the baud rate that the data logger will use for a given port in order to
support serial communications. For some ports (COM), this setting also controls whether the port
will be enabled for serial communications.
Some ports (RS-232) support auto-baud synchronization while the other ports support only fixed
baud. With auto-baud synchronization, the data logger will attempt to match the baud rate to
the rate used by another device based upon the receipt of serial framing errors and invalid
packets.
18.3.2 Beacon
This setting, in units of seconds, governs the rate at which the data logger will broadcast PakBus
messages on the associated port in order to discover any new PakBus neighboring nodes. If this
setting value is set to a value of 0 or 65,535, the data logger will not broadcast beacon messages
on this port.
This setting will also govern the default verification interval if the value of the Verify() setting for
the associated port is zero. If the value of this setting is non-zero, and the value of the Verify
setting is zero, the effective verify interval will be calculated as 2.5 times the value for this setting.
If both the value of this setting and the value of the Verify setting is zero, the effective verify
interval will be 300 seconds (five minutes).
18.3.3 Cell Settings
For data loggers with integrated CELL modules, see
18.3.4 CentralRouters
This setting specifies a list of PakBus addresses for routers that are able to work as Central
Routers. By specifying a non-empty list for this setting, the data logger will be configured as a
Branch Router meaning that it will not be required to keep track of neighbors of any routers
except those in its own branch. Configured in this fashion, the data logger will ignore any
neighbor lists received from addresses in the central routers setting and will forward any
messages that it receives to the nearest default router if it does not have the destination address
for those messages in its routing table.
18. Information tables and settings (advanced)
159