Sophie

Sophie

distrib > Fedora > 14 > x86_64 > by-pkgid > d56e2615a43e036877e0b6cfab8e0892 > files > 292

fldigi-doc-3.20-3.fc14.noarch.rpm

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html><head><meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>WorkingLogs</title></head>
<body style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 204);" alink="#000099" link="#000099" vlink="#990099"><h1 style="text-align: center;">Working Logs</h1>Fldigi
maintains a number of working log files that are found in its default
folder. &nbsp;The default folder is easy to find, simply select the
menu item "File/Show config" and your OS default files explorer will be
opened to that location.<br><h3>Rx/Tx Capture File</h3>Everytime you start or stop fldigi that event is recorded in a daily log file. &nbsp;The daily log is name as:<br><br>flidigYYYYMMDD.log<br><br>where
YYYYMMDD is the current GMT date. &nbsp;This log will also contain your
entire session of Rx and Tx data annotated as to activity and
timestamped. &nbsp;Here is a small example of the daily log:<br><br><table style="text-align: left; width: 622px; height: 221px;" border="0" cellpadding="2" cellspacing="2"><tbody><tr><td style="background-color: rgb(204, 255, 255);">--- Logging started at Tue Dec 30 11:37:21 2008 UTC ---<br><br>RX (2008-12-30 11:37Z): o ur property. No pwr even for a day is rough.<br>TX (2008-12-30 11:39Z): <br>TX (2008-12-30 11:39Z): CQ CQ CQ de W1HKJ W1HKJ W1HKJ<br>TX (2008-12-30 11:40Z): CQ CQ CQ de W1HKJ W1HKJ W1HKJ pse k<br><br>RX (2008-12-30 11:40Z): mG sk<br><br>--- Logging stopped at Tue Dec 30 11:48:11 2008 UTC ---<br></td></tr></tbody></table><br>This log is appended to with each start and stop. &nbsp;That means that no data is ever overwritten.<br><h3>Status log</h3>A
log of errors, warnings and status reports is written for each session.
&nbsp;This file is overwritten each time the program is opened and
subsequently closed. &nbsp;Its format is also ASCII text and will
contain data such as:<br><br><table style="text-align: left; width: 683px; height: 69px;" border="0" cellpadding="2" cellspacing="2"><tbody><tr><td style="background-color: rgb(204, 255, 255);">Q: main: fldigi 3.04BV log started on Tue Dec 30 05:47:10 2008<br><br>W: dxcc_open: Could not read contest country file "/home/dave/.fldigi/cty.dat"</td></tr></tbody></table><br>This
data is identical to that which can be viewed with the event log dialog
which is opened using the menu item "Help/Event log"<br><br><img style="width: 522px; height: 189px;" alt="" src="images/event-log.png"> <img style="width: 522px; height: 189px;" alt="" src="images/event-log-menu.png"><br><br>There are five levels of event logging with increasing depth of reports:<br><br><img style="width: 171px; height: 29px;" alt="" src="images/event-log-quiet.png"> <img style="width: 170px; height: 25px;" alt="" src="images/event-log-error.png">&nbsp;<img style="width: 186px; height: 24px;" alt="" src="images/event-log-warning.png">&nbsp;<img style="width: 162px; height: 24px;" alt="" src="images/event-log-info.png">&nbsp;<img style="width: 177px; height: 25px;" alt="" src="images/event-log-debug.png"><br><br>The default level for logging events is "warning."<br><br>At
the Debug level you will probably see more events than you need.
&nbsp;You can select which events to suppress using the "Log sources"
menu button. &nbsp;It defaults to all enabled.<br><br><div style="text-align: center;"><a href="index.html">Contents</a><br><br></div></body></html>