Westermo MR Series - Manual (Page 40)

40 6622-3201
Web Interface and Command Line Reference Guide www.westermo.com
Secondary log fi les
A second analyser trace can be written to a USB flash drive plugged into the router or internal SD
card. This is useful if the analyser is needed to be captured over an extended period of time and the
normal ana.txt file would erase old events before having chance to view them. The secondary log file
can be limited in size if required or allowed to fill the drive. Once the log file is full, old events will
be pruned off the end of the file to allow for new entries at the top.
There are 2 options for this feature:
1. Take a snapshot of the analyser trace on a specific event and append this to the file on the s: or u:
drive.
2. Continuous writing of the analyser trace to both files, i.e. the regular ana.txt and the file on the s:
or u: drive.
Snapshot to log drive
A secondary log file will be created on the USB or drive and the analyser trace will be appended to
this log file on a triggered event. As this is event triggered, there is an option in the logcodes editor
(Con figure > Event Logcodes) Analyser snapshot to log drive which will need to be set to ON for
the event on which the unit will send a copy of the analyser trace to selected drive.
There are no web page options.
The CLI commands are:
To specify the drive to log to:
ana 0 logdrive [s:|u:]
event 0 logdrive [s:|u:]
To specify the log file:
ana 0 logfile
Where is the name of the file on the log drive: For example, to log a trace to the file
u:mylog.txt or s:mylog.txt
ana 0 logfile mylog.txt
To limit the maximum size of the log file:
ana 0 logsizek
Where is the maximum allowed size of the file in Kb, if 0 is used or this value is not set, the
file size is unlimited. For example, to limit the log file to 1Gb
ana 0 logsizek 1048576