Campbell CR800 Series - Serial Talk through and Comms Watch; Troubleshooting - Using Logs; Troubleshooting - Data Recovery; Log Locations

Section 10. Troubleshooting
486
10.10.1 Serial Talk Through and Comms Watch
The options do not have a timeout when connected in terminal mode via PakBus.
Otherwise P: Serial Talk and W: Comms Watch ("sniff") modes, the timeout
can be changed from the default of 40 seconds to any value ranging from 1 to
86400 seconds (86400 seconds = 1 day).
When using options P or W in a terminal session, consider the following:
• Concurrent terminal sessions are not allowed by the CR800.
• Opening a new terminal session will close the current terminal session.
• The CR800 will attempt to enter a terminal session when it receives non-
PakBus characters on the nine-pin RS-232 port or CS I/O port, unless
the port is first opened with the SerialOpen() command.
If the CR800 attempts to enter a terminal session on the nine-pin RS-232 port or
CS I/O port because of an incoming non-PakBus character, and that port was not
opened using the SerialOpen() command, any currently running terminal
function, including the comms watch, will immediately stop. So, in programs
that frequently open and close a serial port, the probability is higher that a non-
PakBus character will arrive at the closed serial port, thus closing an existing talk-
through or comms watch session. If this occurs, the FileManager() setting to
send comms watch or sniffer to a file is immune to this problem.
10.11 Troubleshooting — Using Logs
Logs are meta data, usually about datalogger or software function. Logs, when
enabled, are available at the locations listed in the following table.
Log Locations
Software Package Usual Location of Logs
LoggerNet C:\Campbellsci\LoggerNet\Logs
PC400 C:\Campbellsci\PC400\Logs
DevConfig C:\Campbellsci\DevConfig\sys\cora\
Logs
10.12 Troubleshooting — Data Recovery
In rare circumstances, exceptional efforts may be required to recover data that are
otherwise lost to conventional data-collection methods. Circumstances may
include the following:
• Program control error
o A CRBasic program was sent to the CR800 without specifying that
it run on power-up. This is most likely to occur only while using