Section 12. csilogmonitor control, 1 purpose of the csilogmonitor control – Campbell Scientific LoggerNet-SDK Software Development Kit User Manual

Page 59

Advertising
background image

Section 12. CsiLogMonitor Control

12.1 Purpose of the CsiLogMonitor Control

The CsiLogMonitor Control provides access to log message from the
LoggerNet server. The log messages stream to this control as a text string.
Use this control to display log messages or to monitor events as they occur on
the server and call other operations or programs based on these LoggerNet
server events.

The types of log files that can be retrieved from the LoggerNet server with the
CsiLogMonitor control include the transaction log and the communication log.
The transaction log messages use the following basic format:

“StationName”, “MessageNumber”, “Message”

The developer can create a program using the CsiLogMonitor control to filter
each message by station name and watch for message numbers and messages
that indicate a specific event. By parsing the transaction log text string and
looking for the triggering messages listed below, the declared station event can
be monitored.

Some station events require a preceding message. In these cases, look for the
preceding message and then for the triggering message to appear later in the
log messages. The preceding message will not necessarily appear in the logs
immediately prior to the triggering log message.

Station Event

Triggering Log Message
“MessageNumber”, “Message”

Preceding Log Message
“MessageNumber”, “Message”

On Call-Back

“114”, “Call-back Started”

N/A

After Call-Back

“116”, “Call-back Stopped”

N/A

The communication log messages use the following basic format:

“StationName”, “MessageType”, “Message”

The message types in the communication log are “S” for a status message, “W”
for a warning message, and “F” for a failure message. Status messages are
general communication messages, warning messages declare a possible
problem and communication retries, and failure messages appear when all
retries have been exhausted and communication will no longer be attempted by
the LoggerNet server for a specific transaction.

12-1

Advertising