Campbell Scientific RTDAQ Software - Manual (Page 56)

Section 4. The RTDAQ Main Screen
On the left side of the LogTool window is a display of all devices set up in
RTDAQ. You can choose to show all messages or filter them to show only
certain devices or dataloggers. RTDAQ can also store these messages to log
files on the PC’s hard drive and will eventually overwrite these files to keep
them from growing forever. You can control whether these logs are used, as
well as the number and size of each log file type with the Options | Log File
Settings menu and dialog.
RTDAQ’s communications engine creates four different types of message
logs. Transaction messages are the highest level, and show every action
undertaken by RTDAQ. For example, if you’re monitoring a datalogger every
second, RTDAQ will show clock check messages each second. Many of the
messages displayed on this log are understandable and may provide some
insight to the processes going on behind the scenes when you monitor or
collect data.
The other three logs are more technical in nature, but can be very useful to
Campbell Scientific support engineers. Communications messages show when
devices are activated, the settings passed to those devices, and their responses.
This log may include status, warning, and fault messages. The Object State
messages record the state of software objects behind the scenes in RTDAQ.
The most detailed log is the Low Level Log. A separate log is stored for each
root level device (each COM port, IP port or TAPI port). These logs record
every byte sent or received through that port. Interpreting all of these logs
requires knowledge of both Campbell Scientific protocols as well as other,
lower level protocols, and requires a detailed understanding of what is
4-20