2 communications, 1 rs-232, 2 communicating with multiple pc programs – Campbell Scientific CR200/CR200X-series Dataloggers User Manual
Page 166: Table 25. math expressions and crbasic results

Section 18. Troubleshooting
Table 25. Math Expressions and CRBASIC Results
Expression
CRBASIC Expression
Result
0 / 0
0 / 0
NAN
∞ - ∞
(1 / 0) - (1 / 0)
NAN
(-1)
∞
-1 ^ (1 / 0)
NAN
0 * -∞
0 * (-1 * (1 / 0))
NAN
±∞ / ±∞
(1 / 0) / (1 / 0)
NAN
1
∞
1 ^ (1 / 0)
NAN
0 * ∞
0 * (1 / 0)
NAN
x / 0
1 / 0
NAN
x / -0
1 / -0
NAN
-x / 0
-1 / 0
NAN
-x / -0
-1 / -0
NAN
∞
0
(1 / 0) ^ 0
1
0
∞
0 ^ (1 / 0)
0
0
0
0 ^ 0
1
18.2 Communications
18.2.1 RS-232
Baud rate mis-match between the CR200(X) and datalogger support software is
often the root of communication problems through the RS-232 port. Software
settings should be set to a baud rate of 9600.
18.2.2 Communicating with Multiple PC Programs
A common practice is to monitor the performance of a CR200(X) using
Devconfig or LoggerNet while the CR200(X) has an open connection to another
copy of LoggerNet. For example, the main connection can be via RF while the
performance monitoring is done via RS-232 port. This is a useful feature of the
CR200(X). A problem often arises, however, in that the CR200(X) gets
confused when attempting this via two different ports, from two different
instances of the same PakBus® address, i.e. if LoggerNet and Devconfig have
the same address.
Note LoggerNet defaults to PakBus® address 4094. Devconfig is fixed at
PakBus® address 4094.
The solution is to change the PakBus® address in LoggerNet | Setup | Options |
LoggerNet Pakbus Settings). If feasible, use PC200W or PC400 instead of
Devconfig as each has a different default PakBus® address from LoggerNet.
154