Campbell Scientific LoggerNet Datalogger Support Software - Manual (Page 533)

Appendix E. Log Files
E.1 Event Logging
As LoggerNet performs its work, it will create records of various kinds of
events. The logs can be very useful for troubleshooting problems and
monitoring the operation of the datalogger network. You can monitor these
logs using LogTool launched from the Tools category of the LoggerNet
toolbar. They can also be saved to disk and opened in a text editor. Most users
will not need to understand these logs, but if you request technical assistance, a
Campbell Scientific applications engineer may ask you to send them one or
more of the logs.
E.1.1 Log Categories
The LoggerNet server logs events in four different kinds of logs as follows:
Transaction Status (TranX.log) – This log file documents the state of the
various transactions that occur between the LoggerNet server and devices in
the datalogger network. This is the most readable of the logs and contains
event messages that are meaningful to most users. Examples of these events
are:
• Datalogger clock check/set
• Datalogger program downloads
• Data collection
The format and type of records in this log are strictly defined to make it
possible for a software program to parse the log records.
Communications Status (CommsX.log) – This log file documents the quality
of communications in the datalogger network.
Object State (StateX.log) – This log file documents the state of an object.
This is primarily for troubleshooting by software developers and the messages
are relatively free in form.
Low Level I/O (IOXSerial Port_1.log) – A low level log file is associated
with each root device in the datalogger network to record incoming and
outgoing communications. While the entire network can be monitored from a
single messaging session of the transaction, communications status, or object
state logs, monitoring of the low-level log is performed on a session with the
root device for that log.
E-1