
Section 14. PakBus Networking
14-10
For program initiated communications such as datalogger-to-datalogger
transfers, the program instruction can (1) have its Com port parameter set to 0
to auto-discover the attached communication peripheral’s active interface
(port), or (2) be configured to match the peripheral’s port. For example, if you
have an RF401 with CSDC 7 active interface, you can configure the program
instruction either:
• SendVariables (Res, 0, 0, 1, 0, 0, ”Pub”, ”FN”, Var, Sw)
or
• SendVariables (Res, ComSDC7, 0, 1, 0, 0, ”Pub”, ”FN”, Var, Sw)
It is convenient to make Com port parameter 2 equal to zero, so that whatever
port your communication peripheral is set for will work.
14.2.5.2 Baud Rates
By default the CR800’s BaudrateME and BaudrateRS232 settings are 115200
Auto (−115200). The Auto or minus sign instructs the port to auto-baud to
incoming communications. After a CR800 with negative (Auto) RS-232 or
M.E. baud rate has communicated, the number with the minus symbol (Auto)
changes to the most recently used baud rate.
Positive (non-Auto) baud rate settings fix the CR800’s baud rate at the
specified setting until a user edits it or a program instruction changes it. For
example, the SetStatus instruction can modify the CR800’s M.E. baud rate
setting as follows:
SetStatus (BaudrateME, −115200)
CSDC and COM310 ports have no associated baud rate per se. For these ports
the (synchronous) data is clocked at a rate that varies automatically according
to current traffic. They are not user configurable and LoggerNet’s Status
Table shows them as 115200.
14.2.6 LoggerNet Device Map Configuration
After adding the root PC COM (or other) port through which you wish to
communicate, add any communication devices needed, a PakBusPort, and the
dataloggers. Figures 14.2-1A and14.2-1B can be RF4xx PakBus networks.
Note that RF4xx devices need not be represented in the map.
FIGURE 14.2-1A. Flat Map
Komentáře k této Příručce