hamradio/cqrlog
1
0
Fork 0
mirror of https://github.com/ok2cqr/cqrlog.git synced 2024-09-21 02:17:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

help updated

Browse Source
This commit is contained in:
Petr Hlozek 2016-04-18 18:52:11 +02:00
parent ce04fdc601
commit a405bde887
21 changed files with 2856 additions and 2264 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

113
help/cwd.html
View File

@ -1,34 +1,44 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en-us"><head>
<title>CQRLOG - cwdaemon setup</title></head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td align="justify" bgcolor="ffffcc" valign="top"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<html lang="en-us">
<head>
<title>CQRLOG - cwdaemon setup</title></head>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td align="justify" bgcolor="ffffcc" valign="top"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h26.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h26.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align="center"><img src="img/line.png"></p>
<strong>cwdaemon setup</strong><br><br>
<div align="justify">cwdaemon is a very good software trick which does a good job if
you build your own kernel and you also don't need to fire it up separately with root
privileges if you have an addition in your start-up scripts.<br><br>
you build your own kernel and you also don't need to fire it up separately with root
privileges if you have an addition in your start-up scripts.<br><br>
<strong>Poor sounding CW </strong><br><br>
Sloppy CW from the cwdaemon it depends on kernel settings. I tested it thoroughly because I love CW at higher speeds. Latency of 1000 Hz helped a bit, I was able to run at usual contest speeds up to 36 wpm. Since kernel 2.6.23 the problem seems cured with tickless kernel. Here is an excerpt from my config:</div>
<strong>Poor sounding CW </strong><br><br>
Sloppy CW from the cwdaemon it depends on kernel settings. I tested it thoroughly because I love CW at higher
speeds. Latency of 1000 Hz helped a bit, I was able to run at usual contest speeds up to 36 wpm. Since kernel 2.6.23
the problem seems cured with tickless kernel. Here is an excerpt from my config:
</div>
<pre>
# # Processor type and features #
CONFIG_TICK_ONESHOT=y
@ -39,33 +49,33 @@ CONFIG_X86_PC=y
....</pre>
<div align="justify">Now I can go up to 60 WPM and the resulting CW is excellent,
however I'm using cwdaemon 0.9.4beta1. Versions below 0.8 are actually useless,
the worst CW I ever heard was produced by cwdaemon 0.5 and an unmodified kernel.<br><br>
however I'm using cwdaemon 0.9.4beta1. Versions below 0.8 are actually useless,
the worst CW I ever heard was produced by cwdaemon 0.5 and an unmodified kernel.<br><br>
The newest cwdaemon 0.9.4 depends on unixcw version 2.3 (or above) which won't
compile on my Slackware system (and I was not patient enough to track all the dependencies),
therefore not tested. I believe that the new dependency was a bad step back...
I hope that new versions of cwdaemon will continue the way set by the 0.9.4beta1 version
(source download here). Anyway, with this version of cwdaemon and custom made kernel 2.6.23
(and higher) I am fully satisfied. I am convinced that any development of CW related
software should be thoroughly tested by high speed freaks, it is rather bad if a developer
or tester means he did well if he is limited by 25 WPM... <br><br></div>
The newest cwdaemon 0.9.4 depends on unixcw version 2.3 (or above) which won't
compile on my Slackware system (and I was not patient enough to track all the dependencies),
therefore not tested. I believe that the new dependency was a bad step back...
I hope that new versions of cwdaemon will continue the way set by the 0.9.4beta1 version
(source download here). Anyway, with this version of cwdaemon and custom made kernel 2.6.23
(and higher) I am fully satisfied. I am convinced that any development of CW related
software should be thoroughly tested by high speed freaks, it is rather bad if a developer
or tester means he did well if he is limited by 25 WPM... <br><br></div>
<strong>Start-up without root privileges </strong><br><br>
<div align="justify">There is no need to start cwdaemon separately with root privileges.
Put a little addition in your start-up script and cwdaemon will start without any keystroke.
It is a good solution for a ham radio machine, however you may have some problems if you want
to use your parallel port for printing or other purposes. <br><br>
Put a little addition in your start-up script and cwdaemon will start without any keystroke.
It is a good solution for a ham radio machine, however you may have some problems if you want
to use your parallel port for printing or other purposes. <br><br>
I added two simple blocks to the <font face=Courier,Courier New>/etc/rc.d/rc.local</font>
which applies to Slackware GNU/Linux, however your preferred distribution may use another
name and location.<br><br>
I added two simple blocks to the <font face=Courier,Courier New>/etc/rc.d/rc.local</font>
which applies to Slackware GNU/Linux, however your preferred distribution may use another
name and location.<br><br>
The first block is used to load parport and parport_pc modules which are essential to
cwdaemon. The second block actually loads cwdaemon. First, it stops the module which
can block your parallel port - here it was cups. cwdaemon also won't work if the lp module
is loaded, so unload it if necessary. Next, a device node is created and cwdaemon is loaded.
The first block is used to load parport and parport_pc modules which are essential to
cwdaemon. The second block actually loads cwdaemon. First, it stops the module which
can block your parallel port - here it was cups. cwdaemon also won't work if the lp module
is loaded, so unload it if necessary. Next, a device node is created and cwdaemon is loaded.
</div>
<pre>#load parport, parport_pc
@ -83,17 +93,18 @@ mknod -m 0660 parport0 c 99 0
Remember the cwdaemon options:<br><br>
<img src="img/cwdaem.png"><br><br>
I find it useful to start cwdaemon without any sidetone, it seems much better to use
the sidetone of your radio rather than the PC speaker.
the sidetone of your radio rather than the PC speaker.
<p align="center"><img src="img/line.png"></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h26.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h26.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>
</body>
</html>

749
help/h1.html
View File

@ -1,207 +1,225 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Preferences</title>
<html>
<head>
<title>CQRLOG - Preferences</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=#ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=#ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="index.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h20.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="index.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h20.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>Preferences</strong></h2>
<div align=justify>The first step you need is to set up your log preferences. From the
logging window, choose the 'File' menu item and 'Preferences' (or Ctrl-P).<br><br>
<img src=img/h2.png border=0>
<br><br>
A multitab window appears, allowing setup of the following parameters:<br>
<ul style="margin-left: 40px;">
<li><a href="h1.html#ah2">Program</a></li>
<li><a href="h1.html#ah3">Station</a></li>
<li><a href="h1.html#ah4">New QSO</a></li>
<li><a href="h1.html#ah5">Visible columns</a></li>
<li><a href="h1.html#ah6">Bands</a></li>
<li><a href="h1.html#ah7">TRX Control</a></li>
<li><a href="h1.html#ah8">Modes</a></li>
<li><a href="h1.html#ah9">QTH Profiles</a></li>
<li><a href="h1.html#ah10">Export</a></li>
<li><a href="h1.html#ah11">DX Cluster</a></li>
<li><a href="h1.html#ah12">Fonts</a></li>
<li><a href="h1.html#ah13">WAZ, ITU Zones</a></li>
<li><a href="h1.html#ah14">IOTA</a></li>
<li><a href="h1.html#ah15">Membership</a></li>
<li><a href="h1.html#bh1">Bandmap</a></li>
<li><a href="h1.html#bh2">xplanet support</a></li>
<li><a href="h1.html#bh3">Zip code tracking</a></li>
<li><a href="h1.html#bh4">LoTW support</a></li>
<li><a href="h1.html#ch1">CW interface</a></li>
<li><a href="h1.html#ch2">fldigi interface</a></li>
<li><a href="h1.html#ch3">Auto backup</a></li>
<li><a href="h1.html#ch4">External viewers</a></li>
<li><a href="h1.html#ch5">Callbook support</a></li>
<li><a href="h1.html#ch6">RBN support</a></li>
<li><a href="h1.html#ch7">Online log upload support</a></li>
</ul>
<h2><strong>Preferences</strong></h2>
The first tab of the 'Preferences' dialog is labelled 'Program'. Here you can setup the
main program behaviour.<br><br>
<a name=ah2><h2><strong>Program</strong></h2></a>
<img src=img/h5.png border=0>
<br><br>
The <strong>Internet connection</strong> is important to those who are behind a proxy.
The data required does not need further explanation, hopefully. CQRLOG attempts to connect
if you try to connect to the DX Cluster (either via web or telnet) and/or if you hit F6
to access the HamQTH.com/QRZ.COM callbook data.
<br><br>
Other settings are:<br><br>
<strong>get UTC time from computer time</strong> - CQRLOG will read UTC from the system time.
If you uncheck the option, you can set the difference between UTC and your local time manually
both for sunrise/sunset and qso time.
<br><br>
<strong>Grayline offset</strong> - sometimes the gray line position is not accurate.
You can set your own correction.
<br><br>
<strong>Check for newer version of DXCC tables after program startup</strong></a> - if checked,
CQRLOG will check if any update of the country files is available. If a new version is found,
an update will be performed, however you are asked first if you want this update.<br><br>
<strong>Check for newer version of qsl managers database after program startup</strong> - if
checked, CQRLOG will check if any update of the QSL Managers database is available. If a new
version is found, an update will be performed, however you are asked first if you want
this update.<br><br>
<img src=img/h67.png border=0><br><br>
<strong>Show deleted countries in statistics</strong></a> - adds formerly valid countries
to statistics and overall DXCC counts.<br><br>
<strong>Show sunrise/sunset in UTC</strong> - if checked, sunrise and sunset times are shown
in UTC, otherwise in local time. Set up the proper time difference for both grayline
and sun rise/set.<br><br>
<strong>Show statistics in</strong> metres (m) or Megahertz (MHz). Selecting one of the radio
buttons affects the statistics appearing at the bottom of logging screen:<br><br>
<img src=img/h27.png border=0><br><br>
and also the headers of the main statistics (DXCC, WAZ and ITU).
<br><br>
<strong>Configuration storage settings</strong> - if you have one common database and several
computers with CQRLOG installed, you can choose which configuration items will be stored
only on the local computer and which will be stored in the database. Configuration stored
in the database will be common for all computers but local configuration will affect CQRLOG
on the local computer only. E.g. if you have two computers in hamshack, both are connected to
the common database. Now you can choose that TRX control, CW keying interface and position
of opened windows will be stored only to local computer.
You'll be able to have different TRX control configuration, windows postions, number of
opened windows etc. on each computer.
logging window, choose the 'File' menu item and 'Preferences' (or Ctrl-P).<br><br>
<img src=img/h2.png border=0>
<br><br>
A multitab window appears, allowing setup of the following parameters:<br>
<ul style="margin-left: 40px;">
<li><a href="h1.html#ah2">Program</a></li>
<li><a href="h1.html#ah3">Station</a></li>
<li><a href="h1.html#ah4">New QSO</a></li>
<li><a href="h1.html#ah5">Visible columns</a></li>
<li><a href="h1.html#ah6">Bands</a></li>
<li><a href="h1.html#ah7">TRX Control</a></li>
<li><a href="h1.html#ah8">Modes</a></li>
<li><a href="h1.html#ah9">QTH Profiles</a></li>
<li><a href="h1.html#ah10">Export</a></li>
<li><a href="h1.html#ah11">DX Cluster</a></li>
<li><a href="h1.html#ah12">Fonts</a></li>
<li><a href="h1.html#ah13">WAZ, ITU Zones</a></li>
<li><a href="h1.html#ah14">IOTA</a></li>
<li><a href="h1.html#ah15">Membership</a></li>
<li><a href="h1.html#bh1">Bandmap</a></li>
<li><a href="h1.html#bh2">xplanet support</a></li>
<li><a href="h1.html#bh3">Zip code tracking</a></li>
<li><a href="h1.html#bh4">LoTW support</a></li>
<li><a href="h1.html#ch1">CW interface</a></li>
<li><a href="h1.html#ch2">fldigi interface</a></li>
<li><a href="h1.html#ch3">Auto backup</a></li>
<li><a href="h1.html#ch4">External viewers</a></li>
<li><a href="h1.html#ch5">Callbook support</a></li>
<li><a href="h1.html#ch6">RBN support</a></li>
<li><a href="h1.html#ch7">Online log upload support</a></li>
</ul>
<h2><strong>Preferences</strong></h2>
The first tab of the 'Preferences' dialog is labelled 'Program'. Here you can setup the
main program behaviour.<br><br>
<a name=ah2><h2><strong>Program</strong></h2></a>
<img src=img/h5.png border=0>
<br><br>
The <strong>Internet connection</strong> is important to those who are behind a proxy.
The data required does not need further explanation, hopefully. CQRLOG attempts to connect
if you try to connect to the DX Cluster (either via web or telnet) and/or if you hit F6
to access the HamQTH.com/QRZ.COM callbook data.
<br><br>
Other settings are:<br><br>
<strong>get UTC time from computer time</strong> - CQRLOG will read UTC from the system time.
If you uncheck the option, you can set the difference between UTC and your local time manually
both for sunrise/sunset and qso time.
<br><br>
<strong>Grayline offset</strong> - sometimes the gray line position is not accurate.
You can set your own correction.
<br><br>
<strong>Check for newer version of DXCC tables after program startup</strong></a> - if checked,
CQRLOG will check if any update of the country files is available. If a new version is found,
an update will be performed, however you are asked first if you want this update.<br><br>
<strong>Check for newer version of qsl managers database after program startup</strong> - if
checked, CQRLOG will check if any update of the QSL Managers database is available. If a new
version is found, an update will be performed, however you are asked first if you want
this update.<br><br>
<img src=img/h67.png border=0><br><br>
<strong>Show deleted countries in statistics</strong></a> - adds formerly valid countries
to statistics and overall DXCC counts.<br><br>
<strong>Show sunrise/sunset in UTC</strong> - if checked, sunrise and sunset times are shown
in UTC, otherwise in local time. Set up the proper time difference for both grayline
and sun rise/set.<br><br>
<strong>Show statistics in</strong> metres (m) or Megahertz (MHz). Selecting one of the radio
buttons affects the statistics appearing at the bottom of logging screen:<br><br>
<img src=img/h27.png border=0><br><br>
and also the headers of the main statistics (DXCC, WAZ and ITU).
<br><br>
<strong>Configuration storage settings</strong> - if you have one common database and several
computers with CQRLOG installed, you can choose which configuration items will be stored
only on the local computer and which will be stored in the database. Configuration stored
in the database will be common for all computers but local configuration will affect CQRLOG
on the local computer only. E.g. if you have two computers in hamshack, both are connected to
the common database. Now you can choose that TRX control, CW keying interface and position
of opened windows will be stored only to local computer.
You'll be able to have different TRX control configuration, windows postions, number of
opened windows etc. on each computer.
</div>
<p align=center><img src=img/line.png></p>
<a name=ah3><h2><strong>Station</strong></h2></a>
<img src=img/h6.png border=0><br><br>
<div align=justify>
Enter your call, name, QTH and QRA Locator here. Remember, that the entered call is also used
as the login for the DX Cluster and is displayed on all stats exported to html. The QRA locator
is of high importance because it determines your accurate position (ie. you don't need to enter
your exact coordinates). The QRA Locator is used in beam heading and distance computation as
well as the start point of the simplified path to the other station which appears on the
grayline map.
Enter your call, name, QTH and QRA Locator here. Remember, that the entered call is also used
as the login for the DX Cluster and is displayed on all stats exported to html. The QRA locator
is of high importance because it determines your accurate position (ie. you don't need to enter
your exact coordinates). The QRA Locator is used in beam heading and distance computation as
well as the start point of the simplified path to the other station which appears on the
grayline map.
</div>
<p align=center><img src=img/line.png></p>
<a name=ah4><h2><strong>New QSO</strong></h2></a>
<img src=img/h7.png border=0><br><br>
<div align=justify>
Here are the default values for a new QSO. Remember, that if the radio interface control is
active, the default frequency does not appear on the logging screen. The preset RST values
will apppear in their corresponding boxes.
<br><br>
The <em>Change default values</em> button allows you to change the frequencies available in
the drop down menu in the NewQSO window. Very useful if you have favourite frequencies
and don't have the radio connected to the computer.<br>
The <em>'Use spacebar to move between fields'</em> is very interesting and probably the
most natural way but it works only if you are moving forwards. To move between fields,
there are two other generic possibilities (TAB key and up/down arrow keys) which
remain unaffected even if you check the spacebar option. The <em>'Refresh data after
save QSO'</em> affects the data displayed in the QSO List (Ctrl-O). If checked, each
QSO appears in this list immediately after logging, however the refresh procedure is
quite slow. To save time, keep this box unchecked. The <em>'Skip over mode and frequency
when radio is connected'</em> is very important if the radio control is active.
The <em>'Show detail window'</em> option enables an extra window to appear at program start.
The <em>'Enable auto search on HamQTH.com/QRZ.COM'</em> switches on the automated search
for HamQTH/QRZ callbook data for any worked station. This option does the same as F6 on the
logging screen, however it can be rather slow depending on the HamQTH.com/QRZ.COM server
availability. The <em>'Show recent QSO records for last ** days'</em> limits the QSO records
listed in the logging screen. Do not set the number of days too high, a high number can
cause program speed issues! The default value of 5 days is appropriate for most cases.
The <em>In previous QSO list show also QSO with call/p</em> etc. means you can see
previous QSO with a station even if he was active from another country with his
call/prefix. E.g. if you enter OK2CQR, you'll also see previous QSOs with him when he
was OM/OK2CQR, SP/OK2CQR etc.</div><br>
Here are the default values for a new QSO. Remember, that if the radio interface control is
active, the default frequency does not appear on the logging screen. The preset RST values
will apppear in their corresponding boxes.
<br><br>
The <em>Change default values</em> button allows you to change the frequencies available in
the drop down menu in the NewQSO window. Very useful if you have favourite frequencies
and don't have the radio connected to the computer.<br>
The <em>'Use spacebar to move between fields'</em> is very interesting and probably the
most natural way but it works only if you are moving forwards. To move between fields,
there are two other generic possibilities (TAB key and up/down arrow keys) which
remain unaffected even if you check the spacebar option. The <em>'Refresh data after
save QSO'</em> affects the data displayed in the QSO List (Ctrl-O). If checked, each
QSO appears in this list immediately after logging, however the refresh procedure is
quite slow. To save time, keep this box unchecked. The <em>'Skip over mode and frequency
when radio is connected'</em> is very important if the radio control is active.
The <em>'Show detail window'</em> option enables an extra window to appear at program start.
The <em>'Enable auto search on HamQTH.com/QRZ.COM'</em> switches on the automated search
for HamQTH/QRZ callbook data for any worked station. This option does the same as F6 on the
logging screen, however it can be rather slow depending on the HamQTH.com/QRZ.COM server
availability. The <em>'Show recent QSO records for last ** days'</em> limits the QSO records
listed in the logging screen. Do not set the number of days too high, a high number can
cause program speed issues! The default value of 5 days is appropriate for most cases.
The <em>In previous QSO list show also QSO with call/p</em> etc. means you can see
previous QSO with a station even if he was active from another country with his
call/prefix. E.g. if you enter OK2CQR, you'll also see previous QSOs with him when he
was OM/OK2CQR, SP/OK2CQR etc.
</div>
<br>
<img src=img/h25.png border=0><br><br>
<div align=justify>
This window dispays details about new/confirmed zones, IOTA details etc.</div>
This window dispays details about new/confirmed zones, IOTA details etc.
</div>
<p align=center><img src=img/line.png></p>
<a name=ah5><h2><strong>Visible columns</strong></h2></a>
<img src=img/h8.png border=0><br><br>
<div align=justify>
Checked columns are visible in the previous QSO list appearing at the top of the
logging screen.</div>
Checked columns are visible in the previous QSO list appearing at the top of the
logging screen.
</div>
<p align=center><img src=img/line.png></p>
<a name=ah6><h2><strong>Bands</strong></h2></a>
<img src=img/h9.png border=0><br><br>
<div align=justify>
Checked bands are visible in both statistics appearing at the bottom of logging screen
(bands/modes of the actual logged station) and main DXCC, WAZ and ITU zones statistics.
It also affects the Challenge points at the bottom of the DXCC statistics.</div>
Checked bands are visible in both statistics appearing at the bottom of logging screen
(bands/modes of the actual logged station) and main DXCC, WAZ and ITU zones statistics.
It also affects the Challenge points at the bottom of the DXCC statistics.
</div>
<p align=center><img src=img/line.png></p>
<a name=ah7><h2><strong>TRX Control</strong></h2></a>
<img src=img/h10.png border=0><br><br>
<div align=justify>
The TRX Control displays actual frequency. You can change band and mode. The radio will
change the freq/mode after you double click on a spot from dx cluster or on an item
in bandmap.<br> CQRLOG uses the rigctld utilty from HamLib. It controls the radio and
programs communicate with it through UDP. CQRLOG supports operating with two TRX but
only one can be active at a time.<br><br>
<strong>Radio one, desc:</strong> is a description you'll see in TRX control window. It is only
descriptive text, you can write whatever you want.<br><br>
<strong>Host:</strong> computer where rigctld is running, localhost is fine for most cases. <br><br>
<strong>RIG model:</strong> choose your radio model from the list<br><br>
<strong>Device:</strong> device which the radio is connected to. /dev/ttyS0 is COM1, /dev/ttyS1
is COM2 etc. If you use USB to serial interface, the device will usually be /dev/ttyUSB0
for COM1 etc. If you are using Ubuntu or Debian, you have to be member of the dialout users
group to have rights to the serial ports.<br><br>
<strong>Poll rate:</strong> specifies how often CQRLOG should read data from rigctld. 500 miliseconds
is fine.<br><br>
<strong>Port number</strong> is the number of the port used to communicate with rigctld.
Default value is 4532. The second radio, has to have a different port e.g. 4533.<br><br>
<strong>Extra command line arguments</strong> usefull when you have to specify more parameters to
rigctld. E.g. CIV address (--civaddr=ID, where ID is the CIV address).<br><br>
<strong>Serial port parameters</strong> from the manual of your rig, please choose the correct options.
Very often it is much better to specify only serial speed and leave other options as default.
Default value means that the settings from HamLib will be used.<br>
The TRX Control displays actual frequency. You can change band and mode. The radio will
change the freq/mode after you double click on a spot from dx cluster or on an item
in bandmap.<br> CQRLOG uses the rigctld utilty from HamLib. It controls the radio and
programs communicate with it through UDP. CQRLOG supports operating with two TRX but
only one can be active at a time.<br><br>
<strong>Radio one, desc:</strong> is a description you'll see in TRX control window. It is only
descriptive text, you can write whatever you want.<br><br>
<strong>Host:</strong> computer where rigctld is running, localhost is fine for most cases. <br><br>
<strong>RIG model:</strong> choose your radio model from the list<br><br>
<strong>Device:</strong> device which the radio is connected to. /dev/ttyS0 is COM1, /dev/ttyS1
is COM2 etc. If you use USB to serial interface, the device will usually be /dev/ttyUSB0
for COM1 etc. If you are using Ubuntu or Debian, <strong>you have to be member of the dialout users
group</strong> to have rights to the serial ports.<br><br>
<strong>Poll rate:</strong> specifies how often CQRLOG should read data from rigctld. 500 miliseconds
is fine.<br><br>
<strong>Port number</strong> is the number of the port used to communicate with rigctld.
Default value is 4532. The second radio, has to have a different port e.g. 4533.<br><br>
<strong>Extra command line arguments</strong> usefull when you have to specify more parameters to
rigctld. E.g. CIV address (--civaddr=ID, where ID is the CIV address).<br><br>
<strong>Serial port parameters</strong> from the manual of your rig, please choose the correct options.
Very often it is much better to specify only serial speed and leave other options as default.
Default value means that the settings from HamLib will be used.<br>
<br>
<strong>Switch only between mode related memories</strong> if this option is cheched, only memories related to
current
operating mode will be used. E.g. you are on CW right now, CQRLOG will switch only between memories with CW mode.
When you switch to
USB or LSB, CQRLOG will use memories both with USB and LSB mode.<br><br>
<strong>Show communication with TRX in console</strong> sometimes TRX control doesn't work. Check this option, run
CQRLOG from console and
you'll see the communication between TRX and Hamlib. This could help to find out what is wrong.<br><br>
<strong>Change default frequencies</strong><br>
The default frequencies which the radio tunes if you click a band button in the 'TRX control'
panel can be changed to your preferences. The mode is switched in accordance to the band plan,
there is actually a separate set of default frequencies for each CW, SSB, RTTY, AM and FM modes.
Click the 'Change default frequencies' button and set up frequencies of your choice.
</div>
<br>
<strong>Switch only between mode related memories</strong> if this option is cheched, only memories related to current
operating mode will be used. E.g. you are on CW right now, CQRLOG will switch only between memories with CW mode. When you switch to
USB or LSB, CQRLOG will use memories both with USB and LSB mode.<br><br>
<strong>Show communication with TRX in console</strong> sometimes TRX control doesn't work. Check this option, run CQRLOG from console and
you'll see the communication between TRX and Hamlib. This could help to find out what is wrong.<br><br>
<strong>Change default frequencies</strong><br>
The default frequencies which the radio tunes if you click a band button in the 'TRX control'
panel can be changed to your preferences. The mode is switched in accordance to the band plan,
there is actually a separate set of default frequencies for each CW, SSB, RTTY, AM and FM modes.
Click the 'Change default frequencies' button and set up frequencies of your choice.</div><br>
<img src=img/h100.png border=0><br>
<p align=center><img src=img/line.png></p>
<br>
<a name="mem"><strong>Add/Modify memory</strong></a><br><br>
You can define your own favourite frequencis and swich between them directly in New QSO window using ALT+V (Mem down) and
You can define your own favourite frequencis and swich between them directly in New QSO window using ALT+V (Mem down)
and
ALT+B (Mem up). These keys are used in N6TR clones to switch between bands.
<br><br>
<img src="img/radio_memory.png"><br><br>
@ -230,11 +248,19 @@ for each operation.
<p align=center><img src=img/line.png></p>
<a name=ah10><h2><strong>Export</strong></h2></a>
<img src=img/h13.png border=0><br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top">
<img src="img/bulb.png"></td><td bgcolor="#ccffff" valign="top"><strong><font color="blue">
Our tip:</font></strong> Check all fields if you backup your whole log. Nothing will be lost
and the amount of data is not large, compared to a very reduced export.
</td></tr></tbody></table><br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2">
<tbody>
<tr>
<td valign="top">
<img src="img/bulb.png"></td>
<td bgcolor="#ccffff" valign="top"><strong><font color="blue">
Our tip:</font></strong> Check all fields if you backup your whole log. Nothing will be lost
and the amount of data is not large, compared to a very reduced export.
</td>
</tr>
</tbody>
</table>
<br><br>
This option allows an easy setup of the log fields to be exported into ADIF or HTML format.
Only checked fields are exported. The 'Width' option denotes the column size in the HTML
export.<br><br>
@ -271,11 +297,19 @@ club' box. A long list of Clubs appears.<br><br><img src=img/h37.png border=0><b
<strong>2. Click the 'Load' button.</strong> The membership data is loaded from the text
database in the 'members' subfolder of your CQRLOG directory. A box with the number of
converted records appears.<br><br><img src=img/h38.png border=0><br><br>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top">
<img src="img/note.png"></td><td bgcolor=#eaeaea valign="top" align="justify"><strong>
<font color="blue">Note:</font></strong> All files in the <em>'membership'</em> subfolder
are displayed. If you create your own database, put it into this subfolder!
</td></tr></tbody></table><br><br>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top">
<img src="img/note.png"></td>
<td bgcolor=#eaeaea valign="top" align="justify"><strong>
<font color="blue">Note:</font></strong> All files in the <em>'membership'</em> subfolder
are displayed. If you create your own database, put it into this subfolder!
</td>
</tr>
</tbody>
</table>
<br><br>
<strong>3. Click the 'Settings' button.</strong> A new dialog appears:<br><br>
<img src=img/h32.png border=0><br><br>
The color coding scheme for new members, new band, new mode, need of a QSL card and an
@ -288,16 +322,25 @@ are:<br>
New band %s member! (%c #%n)
New mode %s member! (%c #%n)
QSL needed for %s member! (%c #%n)
Already confirmed %s member! (%c #%n)</pre><br>
Already confirmed %s member! (%c #%n)</pre>
<br>
Note also the regular expressions used in the messages. The complete list is here:<br>
<pre>%l - long club name
%s - short club name
%n - club number
%c - callsign</pre><br>
%c - callsign</pre>
<br>
The right half of this screen contains the join rules.
<table border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top">
<img src="img/h35.png"></td><td valign="top"><img src="img/h36.png">
</td></tr></tbody></table>
<table border="0" cellpadding="5" cellspacing="2">
<tbody>
<tr>
<td valign="top">
<img src="img/h35.png"></td>
<td valign="top"><img src="img/h36.png">
</td>
</tr>
</tbody>
</table>
Here you can set up which fields from the QSO entry should be bound with the appropriate
column in the membership database. Because the most relevant is the call sign in the QSO
and the membership database contains also mostly the call sign, use the defaults
@ -331,13 +374,13 @@ to dark grey and light grey) and your own entries, <strong>made with Ctrl-A</str
or the <strong>Big Plus key</strong> on the numerical keyboard, are shown in blue.
Also, another set of <em>Watched</em> and <em>Ignored</em> entries can be defined.<br><br>
The content of the Band map can be stored if leaving the log. Check the <em>'Save band
map after close'</em> option.<br><br>The <em>'Show only active mode'</em> and <em>'Show
only active band'</em> options providing an additional level of cluster spot filtering.
map after close'</em> option.<br><br>The <em>'Show only active mode'</em> and <em>'Show
only active band'</em> options providing an additional level of cluster spot filtering.
When checked, the Band Map will show only spots for the mode or band which the radio is on.
The spots are sorted by frequency, so you will see what is on the band - at a glance.
No doubt you will prefer this over the DX Cluster window which contains a mess of rolling
spots, often hard to 'catch'. Finally, if the <em>'Delete station from band map after
QSO'</em> option is checked, the entry with a worked station disappers from the Band Map.
QSO'</em> option is checked, the entry with a worked station disappers from the Band Map.
If such a station is spotted again, it will appear again in the Band Map.
<a name=bh2><h2><strong>xplanet support</strong></h2></a>
<img src=img/h66.png border=0><br><br>
@ -347,179 +390,191 @@ install xplanet. Many distributions have this program either on the installation
(CD, DVD) or xplanet exists in the form of a corresponding package
(rpm, deb, tgz, ebuild etc.). If not, download source codes from:<br>
<a href="http://xplanet.sourceforge.net/download.php">
<strong>http://xplanet.sourceforge.net/download.php</strong></a><br><br>
<strong>http://xplanet.sourceforge.net/download.php</strong></a><br><br>
Follow the usual installation instructions:<br>
<pre>./configure
make
make install</pre>
There are no known dependencies issues.<br><br>
<div align=justify>
The first thing to be set up is the path to the xplanet binary. The default
<pre>/usr/local/bin/xplanet</pre> is OK in most cases for installation from sources,
the usual path for installation from precompiled packages is <pre>/usr/bin/xplanet</pre>
Adjust the <strong>window size</strong> (remember to set up a square, ie. 400x400,
300x300 etc. to avoid strange effects). Also, the <strong>window position</strong>
must be set up to create a nice looking screen. Use the <strong>Test it!</strong>
button to see how your settings affect the resulting screen.<br><br>
Xplanet can refresh its display at a preset interval. This is very useful because it
can read the spot (entry) list and update the displayed data. To avoid a 'flooded',
unreadable window, the number of displayed spots/entries must be limited. It seems
that 20 is the maximum to keep the display garbage away. Actually, the number of
spots (entries) is not limited by the program but by the readability. If you change
the number of spots to be displayed or if the spots should (should not) be sent to
xplanet, restart the program. Remember that a program restart will be needed to
make the changes take effect!<br><br>
Set up the source (DX Cluster, Band map) by checking the appropriate radio button
in the '<strong>Show stations from</strong>' section. The '<strong>Projection</strong>'
has 3 options:<br>
<ul><li><strong>3D</strong> - shows the globe as viewed from space. This rendering
type without any projection is very nice, however the very distant points will not be
visible, also spots or band map entries of distant DX locations will disappear.
Angles should be true because the globe is 'centered' on your location. Distances
are <em>not true</em> because of the lack of projection. This eye candy is
therefore good for those who do not work DX stations.</li>
<li><strong>Azimuthal</strong> - is the usual directional map which you will find
useful for any rotator indication. Both angles and distances are true, however the
continent patterns may look a bit strange to those who are not very accustomed
to this projection. The azimuthal projection is the best for a DXer.</li>
<li><strong>Azimuthal without background</strong> - is the same as above but the
background which contains the angle (polar) scale is not rendered. It is an
'emergency' solution which is useful if you have not enough space to set up
the main xplanet window as a square.</li></ul>
The xplanet window currently has no other function than to display spots or band
map entries in the azimuthal projection or 3D-like picture.
<br><br>
<a name=bh3><h2><strong>Zip code tracking</strong></h2></a>
<img src=img/h69.png border=0><br><br>
Zip code tracking allows you to determine states, counties, provinces and other
geographical details if the postal zip code structure allows such operations. The zip
code itself is retrieved from the callbook address. The database is located in
the /zipcodes folder. If set up properly, the F6 key is used to determine US state,
US county and Italian province.<br><br>
<strong>Setup: </strong>The database must be loaded before use and the target (field)
must be specified. Also, the position of the zip code (line begin or end) must be set
up.<br><br>
<a name=bh4><h2><strong>LoTW/eQSL support</strong></h2></a>
<img src="img/h76.png"><br><br>
Provide your user name for eQSL/LoTW and the password (this is <strong>not</strong>
the password sent to US amateurs via postcard!). Choose if you want to include LoTW
confirmation in the statistics and <em>New country</em> and <em>New band country</em>
info messages.<br><br>
<a name=ch1><h2><strong>CW interface</strong></h2></a>
<img src="img/h95.png"><br><br>
Choose your preferred CW interface. There are 4 options: None, WinKeyer USB,
cwdaemon and K3NG keyer. We strongly recommend Winkey USB by Steve Elliot, K1EL,
which provides 'all in one' keying, including one of most advanced paddle keyers available.
cwdaemon should be seen as a backup option with many limitations, which may need
a custom linux kernel to avoid sloppy CW at speeds above 25 WPM. If cwdaemon is used,
only keyboard keying is possible.<br><br>
Detailed setup of the CW devices is here:<ul>
<li><a href=cwd.html><strong>cwdaemon</strong></a>
<li><a href=wkusb.html><strong>Winkey USB</strong></a></li>
<li><a href="http://blog.radioartisan.com/arduino-cw-keyer/" target="_blank">
<strong>K3NG</strong></a></li></ul>
For further steps (CW messages edit, keyboard keyer operation) - click
<a href=h26.html><strong>here</strong></a>.
<br><br>
<a name=ch2><h2><strong>fldigi interface</strong></h2></a>
First, <em>fldigi</em> must be installed and functional.
Preferences must be set up to operate with fldigi. Set up the path to fldigi, and if you wish
to start it when CQRLOG switches to remote mode. Other parameters including the way that
the CQRLOG - fldigi combo should handle the frequency, mode and RST. CQRLOG also loads
the fldigi contents to keep the data, so the 'polling' period should be set up.
The 2 seconds interval is a very acceptable default.<br><br>
<img src="img/h101.png"><br><br>
The way the CQRLOG - fldigi combo handles the frequency, mode and RST is rather important.
Keep in mind that CQRLOG operates in remote mode which means that the logger is offline
and therefore does not display the actual frequency and mode on the logging screen. If
you properly set up the <em>fldigi</em> mode and frequency control, both are correctly
displayed in the <em>fldigi</em> window. <strong>Choose the fldigi</strong> option in
<em>Frequency from</em>, <em>Mode from</em> and <em>RST from</em> boxes and you don't
need to watch the logger, except the QSO list in the upper portion of the logging screen.
When logging/saving a contact, frequency, mode and RST should appear correctly in this QSO list.
If you choose the CQRLOG option, you must set the mode in CQRLOG which seems less sensible.
<a name=ch3><h2><strong>Auto backup</strong></h2></a>
To increase the safety of your log data, CQRLOG is equipped with an <em>Auto backup</em>
option which allows you to export (ADIF) and store the log data in a safe location.
The ADIF format was choosen because of its text format. The output file can be compressed
in tar.gz format.<br><br>
<img src="img/h102.png"><br><br>
Of course, the export and compression takes some time, depending on the log size (QSO count).
If you are not in a hurry, allow the program 2-3 minutes to perform this safety measure.
We reccomend you backup your log to your hard drive from there it should be copied to
other media (your server, USB flash, a memory card etc.).
<a name=ch4><h2><strong>External viewers</strong></h2></a>
Set up the viewers used for browsing the notes related to a particular callsign.<br><br>
<img src="img/h111.png"><br><br>
The notes in the call_data subfolder can contain text, html, pdf and image files.
To enable reading of all file types, corresponding viewers must be set up properly,
ie. must be in the system path.<br>
<a name=ch5><h2><strong>Callbook support</strong></h2></a>
CQRLOG supports <a href="http://HamQTH.com">HamQTH</a> and <a href="http://qrz.com">QRZ.com</a>
callbooks but only access through the XML interace is supported. HamQTH has a free interface,
for QRZ.com you have to pay an annual fee.<br><br>
<img src="img/h1112.png"><br><br>
The first thing to be set up is the path to the xplanet binary. The default
<pre>/usr/local/bin/xplanet</pre>
is OK in most cases for installation from sources,
the usual path for installation from precompiled packages is
<pre>/usr/bin/xplanet</pre>
Adjust the <strong>window size</strong> (remember to set up a square, ie. 400x400,
300x300 etc. to avoid strange effects). Also, the <strong>window position</strong>
must be set up to create a nice looking screen. Use the <strong>Test it!</strong>
button to see how your settings affect the resulting screen.<br><br>
Xplanet can refresh its display at a preset interval. This is very useful because it
can read the spot (entry) list and update the displayed data. To avoid a 'flooded',
unreadable window, the number of displayed spots/entries must be limited. It seems
that 20 is the maximum to keep the display garbage away. Actually, the number of
spots (entries) is not limited by the program but by the readability. If you change
the number of spots to be displayed or if the spots should (should not) be sent to
xplanet, restart the program. Remember that a program restart will be needed to
make the changes take effect!<br><br>
Set up the source (DX Cluster, Band map) by checking the appropriate radio button
in the '<strong>Show stations from</strong>' section. The '<strong>Projection</strong>'
has 3 options:<br>
<ul>
<li><strong>3D</strong> - shows the globe as viewed from space. This rendering
type without any projection is very nice, however the very distant points will not be
visible, also spots or band map entries of distant DX locations will disappear.
Angles should be true because the globe is 'centered' on your location. Distances
are <em>not true</em> because of the lack of projection. This eye candy is
therefore good for those who do not work DX stations.
</li>
<li><strong>Azimuthal</strong> - is the usual directional map which you will find
useful for any rotator indication. Both angles and distances are true, however the
continent patterns may look a bit strange to those who are not very accustomed
to this projection. The azimuthal projection is the best for a DXer.
</li>
<li><strong>Azimuthal without background</strong> - is the same as above but the
background which contains the angle (polar) scale is not rendered. It is an
'emergency' solution which is useful if you have not enough space to set up
the main xplanet window as a square.
</li>
</ul>
The xplanet window currently has no other function than to display spots or band
map entries in the azimuthal projection or 3D-like picture.
<br><br>
<a name=bh3><h2><strong>Zip code tracking</strong></h2></a>
<img src=img/h69.png border=0><br><br>
Zip code tracking allows you to determine states, counties, provinces and other
geographical details if the postal zip code structure allows such operations. The zip
code itself is retrieved from the callbook address. The database is located in
the /zipcodes folder. If set up properly, the F6 key is used to determine US state,
US county and Italian province.<br><br>
<strong>Setup: </strong>The database must be loaded before use and the target (field)
must be specified. Also, the position of the zip code (line begin or end) must be set
up.<br><br>
<a name=bh4><h2><strong>LoTW/eQSL support</strong></h2></a>
<img src="img/h76.png"><br><br>
Provide your user name for eQSL/LoTW and the password (this is <strong>not</strong>
the password sent to US amateurs via postcard!). Choose if you want to include LoTW
confirmation in the statistics and <em>New country</em> and <em>New band country</em>
info messages.<br><br>
<a name=ch1><h2><strong>CW interface</strong></h2></a>
<img src="img/h95.png"><br><br>
Choose your preferred CW interface. There are 4 options: None, WinKeyer USB,
cwdaemon and K3NG keyer. We strongly recommend Winkey USB by Steve Elliot, K1EL,
which provides 'all in one' keying, including one of most advanced paddle keyers available.
cwdaemon should be seen as a backup option with many limitations, which may need
a custom linux kernel to avoid sloppy CW at speeds above 25 WPM. If cwdaemon is used,
only keyboard keying is possible.<br><br>
Detailed setup of the CW devices is here:
<ul>
<li><a href=cwd.html><strong>cwdaemon</strong></a>
<li><a href=wkusb.html><strong>Winkey USB</strong></a></li>
<li><a href="http://blog.radioartisan.com/arduino-cw-keyer/" target="_blank">
<strong>K3NG</strong></a></li>
</ul>
For further steps (CW messages edit, keyboard keyer operation) - click
<a href=h26.html><strong>here</strong></a>.
<br><br>
<a name=ch2><h2><strong>fldigi interface</strong></h2></a>
First, <em>fldigi</em> must be installed and functional.
Preferences must be set up to operate with fldigi. Set up the path to fldigi, and if you wish
to start it when CQRLOG switches to remote mode. Other parameters including the way that
the CQRLOG - fldigi combo should handle the frequency, mode and RST. CQRLOG also loads
the fldigi contents to keep the data, so the 'polling' period should be set up.
The 2 seconds interval is a very acceptable default.<br><br>
<img src="img/h101.png"><br><br>
The way the CQRLOG - fldigi combo handles the frequency, mode and RST is rather important.
Keep in mind that CQRLOG operates in remote mode which means that the logger is offline
and therefore does not display the actual frequency and mode on the logging screen. If
you properly set up the <em>fldigi</em> mode and frequency control, both are correctly
displayed in the <em>fldigi</em> window. <strong>Choose the fldigi</strong> option in
<em>Frequency from</em>, <em>Mode from</em> and <em>RST from</em> boxes and you don't
need to watch the logger, except the QSO list in the upper portion of the logging screen.
When logging/saving a contact, frequency, mode and RST should appear correctly in this QSO list.
If you choose the CQRLOG option, you must set the mode in CQRLOG which seems less sensible.
<a name=ch3><h2><strong>Auto backup</strong></h2></a>
To increase the safety of your log data, CQRLOG is equipped with an <em>Auto backup</em>
option which allows you to export (ADIF) and store the log data in a safe location.
The ADIF format was choosen because of its text format. The output file can be compressed
in tar.gz format.<br><br>
<img src="img/h102.png"><br><br>
Of course, the export and compression takes some time, depending on the log size (QSO count).
If you are not in a hurry, allow the program 2-3 minutes to perform this safety measure.
We reccomend you backup your log to your hard drive from there it should be copied to
other media (your server, USB flash, a memory card etc.).
<a name=ch4><h2><strong>External viewers</strong></h2></a>
Set up the viewers used for browsing the notes related to a particular callsign.<br><br>
<img src="img/h111.png"><br><br>
The notes in the call_data subfolder can contain text, html, pdf and image files.
To enable reading of all file types, corresponding viewers must be set up properly,
ie. must be in the system path.<br>
<a name=ch5><h2><strong>Callbook support</strong></h2></a>
CQRLOG supports <a href="http://HamQTH.com">HamQTH</a> and <a href="http://qrz.com">QRZ.com</a>
callbooks but only access through the XML interace is supported. HamQTH has a free interface,
for QRZ.com you have to pay an annual fee.<br><br>
<img src="img/h1112.png"><br><br>
<a name=ch6><h2><strong>RBN support</strong></h2></a>
CQRLOG can receive spots from RBN and show them on the Gray line map. It's very nice to
see where your signal has been decoded especially when you are calling CQ on an empty band.<br><br>
<img src="img/h1114.png"><br><br>
<em>Login:</em> - your user name to log in to RBN. It's usually your own callsign.<br>
<em>Watch for:</em> the callsign you are watching for, also usually your own callsign.
If you leave this field empty, every spot will be shown on the grayline map.<br>
<em>Auto connect after open the log</em> - check this option if you want to autoconnect
to RBN when the program starts, you won't have to worry about it and CQRLOG will do
it for you automatically.
<em>Signal strength</em> How strong you are will be clear very quickly when you look
at the map with the dots in different colours. Which colour will be used can be set here.<br>
<em>Delete old information after XX seconds</em> The dots won't stay on the map forever.
180 seconds (3 minutes) is a good default value. Please note, it also depends on the band,
if you change band, dots will always be deleted. All data is band related.<br>
<a name=ch7><h2><strong>Online log upload support</strong></h2></a>
CQRLOG supports online log upload to <a href="http://HamQTH.com">HamQTH</a>,
<a href="https://secure.clublog.org/loginform.php">ClubLog.org</a> and
<a href="http://hrdlog.net/">HRDLOG.net</a><br>
<img src="img/h1116.png"><br><br>
Both ClubLog and HamQTH need a username and password, Clublog also needs the email address
used when you registered. HRDLog.net needs only user name and the code you got by e-mail.
You can set different color for each service. This color will be used for status messages
which will inform you about upload progress.
<em>Upload QSO data immediately after save, update or delete</em> means that every
insert/update or delete will be uploaded automatically. But if you change something in
QSO list window with hot keys e.g. CTRL+S, CTRL+W etc. and/or download data
from eQSL/LoTW, changes won't be uploaded. All will be uploaded after you save/delete QSO
or if you choose Online log and Upload to all online logs menu.<br>
<a name=ch6><h2><strong>RBN support</strong></h2></a>
CQRLOG can receive spots from RBN and show them on the Gray line map. It's very nice to
see where your signal has been decoded especially when you are calling CQ on an empty band.<br><br>
<img src="img/h1114.png"><br><br>
<em>Login:</em> - your user name to log in to RBN. It's usually your own callsign.<br>
<em>Watch for:</em> the callsign you are watching for, also usually your own callsign.
If you leave this field empty, every spot will be shown on the grayline map.<br>
<em>Auto connect after open the log</em> - check this option if you want to autoconnect
to RBN when the program starts, you won't have to worry about it and CQRLOG will do
it for you automatically.
<em>Signal strength</em> How strong you are will be clear very quickly when you look
at the map with the dots in different colours. Which colour will be used can be set here.<br>
<em>Delete old information after XX seconds</em> The dots won't stay on the map forever.
180 seconds (3 minutes) is a good default value. Please note, it also depends on the band,
if you change band, dots will always be deleted. All data is band related.<br>
<a name=ch7><h2><strong>Online log upload support</strong></h2></a>
CQRLOG supports online log upload to <a href="http://HamQTH.com">HamQTH</a>,
<a href="https://secure.clublog.org/loginform.php">ClubLog.org</a> and
<a href="http://hrdlog.net/">HRDLOG.net</a><br>
<img src="img/h1116.png"><br><br>
Both ClubLog and HamQTH need a username and password, Clublog also needs the email address
used when you registered. HRDLog.net needs only user name and the code you got by e-mail.
You can set different color for each service. This color will be used for status messages
which will inform you about upload progress.
<em>Upload QSO data immediately after save, update or delete</em> means that every
insert/update or delete will be uploaded automatically. But if you change something in
QSO list window with hot keys e.g. CTRL+S, CTRL+W etc. and/or download data
from eQSL/LoTW, changes won't be uploaded. All will be uploaded after you save/delete QSO
or if you choose Online log and Upload to all online logs menu.<br>
<a name=ch8><h3>How to get it to work?</h3></a>
<ul>
<li>check if you have set correct username, password (email, Code)</li>
<li>export all data from the log to ADIF file</li>
<li>import this adif file to the website of online log you are going to use
(if you are using HamQTH, please wait untill the email about a successful import arrives)</li>
<li>open QSO list window, click to <em>Online log</em> menu and choose
<em>Mark QSO as uploaded to all logs</em>, CQRLOG marks all QSO as uploaded</li>
</ul>
That's all, Now if you insert/edit or delete a QSO, it will also be uploaded to the online log.
<br><br>
<strong>Close the "Status of log upload" window after successful upload</strong>
if you don't want to have Log upload status window visible, check this option and
windows will be closed after upload to online log is finished.
<br><br>
<strong>Ignore changes caused by LoTW/eQSL upload or download</strong> - every change of
a qso will cause a new upload to the online log database. Sometimes it can be useful to
have the opportunity to disable it when upload/download data to LoTW/eQSL. These changes
won't be logged and QSO won't be uploaded to any online log.
<a name=ch8><h3>How to get it to work?</h3></a>
<ul>
<li>check if you have set correct username, password (email, Code)</li>
<li>export all data from the log to ADIF file</li>
<li>import this adif file to the website of online log you are going to use
(if you are using HamQTH, please wait untill the email about a successful import arrives)
</li>
<li>open QSO list window, click to <em>Online log</em> menu and choose
<em>Mark QSO as uploaded to all logs</em>, CQRLOG marks all QSO as uploaded
</li>
</ul>
That's all, Now if you insert/edit or delete a QSO, it will also be uploaded to the online log.
<br><br>
<strong>Close the "Status of log upload" window after successful upload</strong>
if you don't want to have Log upload status window visible, check this option and
windows will be closed after upload to online log is finished.
<br><br>
<strong>Ignore changes caused by LoTW/eQSL upload or download</strong> - every change of
a qso will cause a new upload to the online log database. Sometimes it can be useful to
have the opportunity to disable it when upload/download data to LoTW/eQSL. These changes
won't be logged and QSO won't be uploaded to any online log.
</div>
<p align=center><img src=img/line.png></p>
<br>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="index.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h20.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="index.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h20.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>
</body>
</html>

552
help/h20.html
View File

@ -1,25 +1,31 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Keys and Shortcuts</title>
<html>
<head>
<title>CQRLOG - Keys and Shortcuts</title>
</head>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h1.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h21.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h1.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h21.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div align="left"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
@ -27,248 +33,277 @@ in Preferences. This autobackup function creates an ADIF file with a backup of y
<a name="ah16"><h2><strong>Keys and shortcuts</strong></h2></a>
<strong>Logging screen</strong><br><br>
<table width="99%" border="0" cellpadding="4" cellspacing="0">
<tbody>
<tr>
<td width="35%">2x ESC</td>
<td width="65%">Empty all fields and prepare program for a new QSO</td>
</tr>
<tr>
<td width="35%">PgUp</td>
<td width="65%">CW Speed +2 WPM (QRQ)</td>
</tr>
<tr>
<td width="35%">PgDn</td>
<td width="65%">CW Speed -2 WPM (QRS)</td>
</tr>
<tr>
<td width="35%">` (back single quote) or CTRL-W</td>
<td width="65%">Send a spot to the DX Cluster</td>
</tr>
<tr>
<td width="35%">F11</td>
<td width="65%">QRZ/HamQTH Callbook (call in the field)</td>
</tr>
<tr>
<td width="35%">Ctrl-A</td>
<td width="65%">Add the logged call sign and the actual frequency to the bandmap</td>
</tr>
<tr>
<td width="35%">Ctrl-D </td>
<td width="65%">DXCC statistics - Confirmed only</td>
</tr>
<tr>
<td width="35%">Ctrl-I </td>
<td width="65%">Detailed info</td>
</tr>
<tr>
<td width="35%">Ctrl-L </td>
<td width="65%">Change your QRA locator</td>
</tr>
<tr>
<td width="35%">Ctrl-M</td>
<td width="65%">Remote mode for fldigi</td>
</tr>
<tr>
<td width="35%">Ctrl-N </td>
<td width="65%">Show/edit long note</td>
</tr>
<tr>
<td width="35%">Ctrl-O </td>
<td width="65%"><strong><font color="red">QSO list</font></strong> (see below)</td>
</tr>
<tr>
<td width="35%">Ctrl-P </td>
<td width="65%">Preferences</td>
</tr>
<tr>
<td width="35%">Ctrl-Q </td>
<td width="65%">Quit (Close)</td>
</tr>
<tr>
<td width="35%">Ctrl-R </td>
<td width="65%">Change ref. call</td>
</tr>
<tr>
<td width="35%">ALT-B</td>
<td width="65%"><a href="h1.html#ah7">Memory down</a></td>
</tr>
<tr>
<td width="35%">ALT-V</td>
<td width="65%"><a href="h1.html#ah7">Memory up<a></td>
</tr>
</tbody>
<tbody>
<tr>
<td width="35%">2x ESC</td>
<td width="65%">Empty all fields and prepare program for a new QSO</td>
</tr>
<tr>
<td width="35%">PgUp</td>
<td width="65%">CW Speed +2 WPM (QRQ)</td>
</tr>
<tr>
<td width="35%">PgDn</td>
<td width="65%">CW Speed -2 WPM (QRS)</td>
</tr>
<tr>
<td width="35%">` (back single quote) or CTRL-W</td>
<td width="65%">Send a spot to the DX Cluster</td>
</tr>
<tr>
<td width="35%">F11</td>
<td width="65%">QRZ/HamQTH Callbook (call in the field)</td>
</tr>
<tr>
<td width="35%">Ctrl-A</td>
<td width="65%">Add the logged call sign and the actual frequency to the bandmap</td>
</tr>
<tr>
<td width="35%">Ctrl-D</td>
<td width="65%">DXCC statistics - Confirmed only</td>
</tr>
<tr>
<td width="35%">Ctrl-I</td>
<td width="65%">Detailed info</td>
</tr>
<tr>
<td width="35%">Ctrl-L</td>
<td width="65%">Change your QRA locator</td>
</tr>
<tr>
<td width="35%">Ctrl-M</td>
<td width="65%">Remote mode for fldigi</td>
</tr>
<tr>
<td width="35%">Ctrl-N</td>
<td width="65%">Show/edit long note</td>
</tr>
<tr>
<td width="35%">Ctrl-O</td>
<td width="65%"><strong><font color="red">QSO list</font></strong> (see below)</td>
</tr>
<tr>
<td width="35%">Ctrl-P</td>
<td width="65%">Preferences</td>
</tr>
<tr>
<td width="35%">Ctrl-Q</td>
<td width="65%">Quit (Close)</td>
</tr>
<tr>
<td width="35%">Ctrl-R</td>
<td width="65%">Change ref. call</td>
</tr>
<tr>
<td width="35%">ALT-B</td>
<td width="65%"><a href="h1.html#ah7">Memory down</a></td>
</tr>
<tr>
<td width="35%">ALT-V</td>
<td width="65%"><a href="h1.html#ah7">Memory up<a></td>
</tr>
</tbody>
</table>
<br>
<p align=center><img src=img/line.png></p>
<strong>QSO list</strong><br><br>
<table><tr><td valign="top"><img src="img/bulb.png"></td><td bgcolor=ccffff width="100%">
<strong><font color="blue">The QSO list is the main screen for maintenance!</font></strong>
</td></tr></table>
<table>
<tr>
<td valign="top"><img src="img/bulb.png"></td>
<td bgcolor=ccffff width="100%">
<strong><font color="blue">The QSO list is the main screen for maintenance!</font></strong>
</td>
</tr>
</table>
<br><br>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="35%">F1</td>
<td width="65%">Help (this file)</td>
</tr>
<tr>
<td width="35%">F2</td>
<td width="65%">New QSO</td>
</tr>
<tr>
<td width="35%">F3</td>
<td width="65%">View QSO</td>
</tr>
<tr>
<td width="35%">F4</td>
<td width="65%">Edit QSO <font color="red"><strong>*</strong></font></td>
</tr>
<tr>
<td width="35%">F6</td>
<td width="65%">QRZ/HamQTH Callbook search</td>
</tr>
<tr>
<td width="35%">F7</td>
<td width="65%">Sort (setup sort order)</td>
</tr>
<tr>
<td width="35%">F8</td>
<td width="65%">Delete QSO <font color="red"><strong>*</strong></font></td>
</tr>
<tr>
<td width="35%">F10</td>
<td width="65%">Go to menu</td>
</tr>
<tr>
<td width="35%">F12</td>
<td width="65%">Create filter</td>
</tr>
<tr>
<td width="35%">Ctrl-D </td>
<td width="65%">DXCC statistics <font color="blue"><strong>**</strong></font></td>
</tr>
<tr>
<td width="35%">Ctrl-F</td>
<td width="65%">Search</td>
</tr>
<tr>
<td width="35%">Ctrl-P </td>
<td width="65%">Preferences</td>
</tr>
<tr>
<td width="35%">Ctrl-Q </td>
<td width="65%">Close the QSO list window</td>
</tr>
<tr>
<td width="35%">Ctrl-R</td>
<td width="65%">QSL received</td>
</tr>
</tbody>
</table><br>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr>
<td valign="top"><img src="img/exc.png"></td><td bgcolor=ffffcc valign="top">
<strong><font color="red">WARNING!</font></strong> Use the <strong>Edit (F4)</strong>
and <strong>Delete (F8)</strong> (marked with a red star) options only if you are sure,
what you are doing! There is NO UNDO, so the operation cannot be undone!
</td></tr></tbody></table><br>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top">
<img src="img/bulb.png"></td><td bgcolor=ccffff valign="top" width="100%"><strong>
<font color="blue">Your DXCC statistics can only be rebuilt from the QSO list!</font></strong>
</td></tr></tbody></table>
<tbody>
<tr>
<td width="35%">F1</td>
<td width="65%">Help (this file)</td>
</tr>
<tr>
<td width="35%">F2</td>
<td width="65%">New QSO</td>
</tr>
<tr>
<td width="35%">F3</td>
<td width="65%">View QSO</td>
</tr>
<tr>
<td width="35%">F4</td>
<td width="65%">Edit QSO <font color="red"><strong>*</strong></font></td>
</tr>
<tr>
<td width="35%">F6</td>
<td width="65%">QRZ/HamQTH Callbook search</td>
</tr>
<tr>
<td width="35%">F7</td>
<td width="65%">Sort (setup sort order)</td>
</tr>
<tr>
<td width="35%">F8</td>
<td width="65%">Delete QSO <font color="red"><strong>*</strong></font></td>
</tr>
<tr>
<td width="35%">F10</td>
<td width="65%">Go to menu</td>
</tr>
<tr>
<td width="35%">F12</td>
<td width="65%">Create filter</td>
</tr>
<tr>
<td width="35%">Ctrl-D</td>
<td width="65%">DXCC statistics <font color="blue"><strong>**</strong></font></td>
</tr>
<tr>
<td width="35%">Ctrl-F</td>
<td width="65%">Search</td>
</tr>
<tr>
<td width="35%">Ctrl-P</td>
<td width="65%">Preferences</td>
</tr>
<tr>
<td width="35%">Ctrl-Q</td>
<td width="65%">Close the QSO list window</td>
</tr>
<tr>
<td width="35%">Ctrl-R</td>
<td width="65%">QSL received</td>
</tr>
</tbody>
</table>
<br>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top">
<strong><font color="red">WARNING!</font></strong> Use the <strong>Edit (F4)</strong>
and <strong>Delete (F8)</strong> (marked with a red star) options only if you are sure,
what you are doing! There is NO UNDO, so the operation cannot be undone!
</td>
</tr>
</tbody>
</table>
<br>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top">
<img src="img/bulb.png"></td>
<td bgcolor=ccffff valign="top" width="100%"><strong>
<font color="blue">Your DXCC statistics can only be rebuilt from the QSO list!</font></strong>
</td>
</tr>
</tbody>
</table>
<p align=center><img src=img/line.png></p>
<a name="ah17"><h2><strong>New QSO (online logging)</strong></h2></a>
<div align="justify">
While logging online (during your QSO), date, start and end time are
set automatically. Type the call into the dedicated box and move from
this field with <strong>Arrow-Down</strong> key or <strong>spacebar</strong>
(only if you enable it in the <a href="h1.html#ah4"><strong>Preferences</strong></a>).
The 'Frequency' and 'Mode' fields are skipped if you have properly set up the
<a href="h1.html#ah7"><strong>TRX Control</strong></a>.
If you omit settting up the TRX Control option or if your radio does not
allow Computer Aided Control (CAT), the Frequency and Mode fields
are not skipped and must be filled manually, however you can use the
pull-down menu to choose a corresponding default frequency in any band
and the mode. <br><br>
When the cursor leaves the 'Call' field, you will see your previous
contacts with the logged station (if any). The number above 'Call' box marked 'QSO nr.'
denotes the number of contacts you already have with the worked station (here,
130 QSO worked already with G3LIK, the 131st just being logged). The previously confirmed
contacts are highlighted in red. If the station has a QSL
manager, his call appears in the 'QSL VIA' field and an indication
'QSL manager found' is displayed. If the station wants QSL direct only,
the 'QSL VIA' field remains empty but the red 'QSL manager found'
warning is still displayed. Click the button at the right of the
'QSL VIA' field and a separate window with QSL managers appears, the
correct address is highlighted.<br><br>
<img src="img/h29.png" border="0"><br><br>
Note, that if you move the cursor from the 'Call' field to the 'RST
sent' field, the S in the RST is highlighted, making it possible to simply
overwrite the corresponding number (S). The same applies to the 'RST rcvd'
field.<br><br>
This trick can speed up the QSO entering procedure. You can also move
between fields with the TAB key but then the whole RST field is highlighted, so
reports where more than a single character need to be overwritten (ie.
449) can be entered more easily. The default report
is predefined in <a href="h1.html#ah4"><strong>Preferences</strong></a>).
Note, the RST field changes to its correct form (RS or RST) with mode.<br><br>
The 'Start time' begins to run if you move the cursor to the 'RST rcvd'
field. This means that you can set your RST without any hurry. Also,
the QSO duration counter starts to run. It is just behind the time
fields on the logging screen.<br><br>
If the cursor leaves the 'Call' field, a lot of another details are
displayed. If the location is exactly on an island with IOTA reference
number, it is displayed in the IOTA field. If the call represents more
IOTA refs., the IOTA designator above its field became red. Click the
button on the right side and a pull-down menu with all possible IOTA
references is displayed.<br><br>
<img src="img/h26.png" border="0"><br><br>
CQRLOG also displays the usual data like exact QTH description
(including province, regions, call districts etc.), WAZ and ITU zones,
continent, DXCC reference, geographical coordinates (in decimal form),
distance, azimuth (direction), date and local time of the target point
and the salutation corresponding to the local time (GM, GE etc.). <br><br>
You can add a general long note to your log with the Ctrl-N key (from
the logging screen or from the 'File' menu option).<br><br>
<img src="img/h2.png" border="0"><br><br>
Ctrl-N opens a new dialog window where you can add or edit your note.
This note is <b>not</b> related to any record, it is just a notepad allowing
operations with your notes which are stored in your log database.<br><br>
<img src="img/h68.png" border="0"><br><br>
If a call sign is entered, the grayline map displays a line from your QTH to
the target point.<br><br>
</div><img src="img/h24.png" border="0"><br><br>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr>
<td valign="top"><img src="img/note.png"></td><td bgcolor="#eaeaea"><strong>
<font color="blue">Note: </font></strong>
The yellow line on the grayline map has nothing to do with actual beam
heading nor the actual path! The purpose of this line is to indicate if
the path goes from/to day or night areas.</td></tr></tbody></table><br>
While logging online (during your QSO), date, start and end time are
set automatically. Type the call into the dedicated box and move from
this field with <strong>Arrow-Down</strong> key or <strong>spacebar</strong>
(only if you enable it in the <a href="h1.html#ah4"><strong>Preferences</strong></a>).
The 'Frequency' and 'Mode' fields are skipped if you have properly set up the
<a href="h1.html#ah7"><strong>TRX Control</strong></a>.
If you omit settting up the TRX Control option or if your radio does not
allow Computer Aided Control (CAT), the Frequency and Mode fields
are not skipped and must be filled manually, however you can use the
pull-down menu to choose a corresponding default frequency in any band
and the mode. <br><br>
When the cursor leaves the 'Call' field, you will see your previous
contacts with the logged station (if any). The number above 'Call' box marked 'QSO nr.'
denotes the number of contacts you already have with the worked station (here,
130 QSO worked already with G3LIK, the 131st just being logged). The previously confirmed
contacts are highlighted in red. If the station has a QSL
manager, his call appears in the 'QSL VIA' field and an indication
'QSL manager found' is displayed. If the station wants QSL direct only,
the 'QSL VIA' field remains empty but the red 'QSL manager found'
warning is still displayed. Click the button at the right of the
'QSL VIA' field and a separate window with QSL managers appears, the
correct address is highlighted.<br><br>
<img src="img/h29.png" border="0"><br><br>
Note, that if you move the cursor from the 'Call' field to the 'RST
sent' field, the S in the RST is highlighted, making it possible to simply
overwrite the corresponding number (S). The same applies to the 'RST rcvd'
field.<br><br>
This trick can speed up the QSO entering procedure. You can also move
between fields with the TAB key but then the whole RST field is highlighted, so
reports where more than a single character need to be overwritten (ie.
449) can be entered more easily. The default report
is predefined in <a href="h1.html#ah4"><strong>Preferences</strong></a>).
Note, the RST field changes to its correct form (RS or RST) with mode.<br><br>
The 'Start time' begins to run if you move the cursor to the 'RST rcvd'
field. This means that you can set your RST without any hurry. Also,
the QSO duration counter starts to run. It is just behind the time
fields on the logging screen.<br><br>
If the cursor leaves the 'Call' field, a lot of another details are
displayed. If the location is exactly on an island with IOTA reference
number, it is displayed in the IOTA field. If the call represents more
IOTA refs., the IOTA designator above its field became red. Click the
button on the right side and a pull-down menu with all possible IOTA
references is displayed.<br><br>
<img src="img/h26.png" border="0"><br><br>
CQRLOG also displays the usual data like exact QTH description
(including province, regions, call districts etc.), WAZ and ITU zones,
continent, DXCC reference, geographical coordinates (in decimal form),
distance, azimuth (direction), date and local time of the target point
and the salutation corresponding to the local time (GM, GE etc.). <br><br>
You can add a general long note to your log with the Ctrl-N key (from
the logging screen or from the 'File' menu option).<br><br>
<img src="img/h2.png" border="0"><br><br>
Ctrl-N opens a new dialog window where you can add or edit your note.
This note is <b>not</b> related to any record, it is just a notepad allowing
operations with your notes which are stored in your log database.<br><br>
<img src="img/h68.png" border="0"><br><br>
If a call sign is entered, the grayline map displays a line from your QTH to
the target point.<br><br>
</div>
<img src="img/h24.png" border="0"><br><br>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/note.png"></td>
<td bgcolor="#eaeaea"><strong>
<font color="blue">Note: </font></strong>
The yellow line on the grayline map has nothing to do with actual beam
heading nor the actual path! The purpose of this line is to indicate if
the path goes from/to day or night areas.
</td>
</tr>
</tbody>
</table>
<br>
<div align="justify"><strong><h3>Status line</h3></strong>
<img src="img/h44.png" border="0"><br><br>
Here your own QRA locator is displayed which can be changed using Ctrl-L (important
mostly for VHF freaks who forget to change the QRA locator in the QTH profile).
In the next column is the reference call sign (the core of a slashed call, ie.
KH6/OK2CQR). You can change it using Ctrl-R. The purpose is to provide the possibility
of changeing the reference call if a correction of membership needed.
The number in the right corner denotes the CQRLOG version.
<p align=center><img src=img/line.png></p>
<a name="ah17"><h2><strong>New QSO (offline logging, ie. from paper log etc.)</strong></h2></a>
To switch to the offline mode, check the 'Offline' box above the date.
To indicate that you are offline, the box with the 'Offline'
description became red framed.<br><br>
<img src="img/h30.png" border="0"><br><br>
Basically, offline logging is the same as online logging, however
there are some differences. The 'Frequency' and 'Mode' fields are not
skipped. You can enter the exact frequency or choose a default (for
each band) from the pull-down menu. The same applies to the mode.<br><br>
You also need to enter the 'Date' and at least the 'Start time'. The
date format is YYYYMMDD and you can enter it without dashes, ex. 26.
May 1994 can be entered as just 19940526. The dashes are added
automatically. The same applies to the time which can be entered
without the colon.<br><br>
The CAT (radio computer control) is turned off. Other fields and log
actions are the same. If you uncheck the 'Offline' box, CQRLOG returns
to the online mode.<br><br></div>
<img src="img/h44.png" border="0"><br><br>
Here your own QRA locator is displayed which can be changed using Ctrl-L (important
mostly for VHF freaks who forget to change the QRA locator in the QTH profile).
In the next column is the reference call sign (the core of a slashed call, ie.
KH6/OK2CQR). You can change it using Ctrl-R. The purpose is to provide the possibility
of changeing the reference call if a correction of membership needed.
The number in the right corner denotes the CQRLOG version.
<p align=center><img src=img/line.png></p>
<a name="ah17"><h2><strong>New QSO (offline logging, ie. from paper log etc.)</strong></h2></a>
To switch to the offline mode, check the 'Offline' box above the date.
To indicate that you are offline, the box with the 'Offline'
description became red framed.<br><br>
<img src="img/h30.png" border="0"><br><br>
Basically, offline logging is the same as online logging, however
there are some differences. The 'Frequency' and 'Mode' fields are not
skipped. You can enter the exact frequency or choose a default (for
each band) from the pull-down menu. The same applies to the mode.<br><br>
You also need to enter the 'Date' and at least the 'Start time'. The
date format is YYYYMMDD and you can enter it without dashes, ex. 26.
May 1994 can be entered as just 19940526. The dashes are added
automatically. The same applies to the time which can be entered
without the colon.<br><br>
The CAT (radio computer control) is turned off. Other fields and log
actions are the same. If you uncheck the 'Offline' box, CQRLOG returns
to the online mode.<br><br></div>
<a name="ah33"><h2><strong>Digital modes (including RTTY)</strong></h2></a>
CQRLOG employs <em>fldigi</em> by Dave Freese, W1HKJ. We believe that this is the
best digimode software available. To use <em>fldigi</em>, CQRLOG must be switched
@ -282,16 +317,17 @@ Now, use <em>fldigi</em> in its normal way and your contacts will go directly to
The most important thing is a <a href="h1.html#ch2">proper setup</a> of the remote mode
(frequency and mode). See fldigi help and the Beginners Guide on the W1HKJ site
<a href=http://www.w1hkj.com/beginners.html>
strong>http://www.w1hkj.com/beginners.html</strong></a>.
strong>http://www.w1hkj.com/beginners.html</strong></a>.
<p align=center><img src=img/line.png></p>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h1.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h21.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h1.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h21.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>
</div></body>
</html>

342
help/h21.html
View File

@ -1,24 +1,31 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - DX Cluster Operation</title>
<html>
<head>
<title>CQRLOG - DX Cluster Operation</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h20.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h22.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h20.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h22.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
@ -38,131 +45,178 @@ cluster node by simply clicking the 'Connect' button. You should see the cluster
messages indicating progress. You can enter any command into the 'Command' field
(ie. SH/DX to display last spots, SH/U to see the users connected to the node etc.).
<br><br>
<table border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top">
<img src="img/bulb.png"></td><td bgcolor="#ccffff" width="100%">
<strong><font color="blue">Our tip:</font></strong> For a nice looking cluster window,
choose a fixed-width font. We prefer Monospace Regular or Onuava but also Courier works
nicely. Apple's Monaco font is also very nice and has a slashed zero.</td></tr></tbody></table>
<br>
<table border="0" cellpadding="5" cellspacing="2" width="99%"><tbody>
<tr><td valign="top"><div align="justify">CQRLOG
has some predefined cluster nodes, however you will probably need to
set up a node of your preference. Click the 'Select' button and a list
of cluster node appears (see below). Click the 'New' option. Another dialog
appears (right). <br><br><img border="0" src="img/h18.png"></div></td>
<td valign="top"><img src="img/h19.png" border="0" align="top"><br>
<div style="text-align: justify;">Enter
the description (mostly the callsign). The 'Address' can be either an IP
or the name (see examples in the list). The 'Port' is given by a number.
Both address and port number can be obtained from the lists of DX cluster
nodes which are widely available on the internet.
<br><br><font color="red"><strong>Remember</strong></font> to put your callsign
into the 'User name' field. This will enable <strong>autologin</strong>.
The 'Password' column should remain empty in most cases because only few nodes
are password protected.
<br><br>A detailed list of DX Cluster nodes can be found
<a href="http://www.dxcluster.info/telnet/index.php"><strong>here</strong></a>
(page created by Jim, AD1C).
</div></td></tr></tbody></table><br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%"><tbody>
<tr><td valign="top">
<a name="bh19"><h2><strong>Bandmap Operation</strong></h2></a>
<img src="img/h64.png" border="0"></td><td valign="top"><div align="justify"><br><br>
The main purpose of a bandmap is to combine the most interesting info from two sources - the DX
Cluster and your personal notes. The bandmap combines a DX Cluster window with scratch
pad memories available on many radios, however a band map is more comfortable by far - you
don't need to manipulate subtle buttons on the radio panel, also the transceiver does
not indicate what is in the scratch pad memory. The band map is operated from the keyboard
and shows all at a glance.
<br><br>A valuable addition is the 'entries aging' option. If the bandmap entry is 'too' old,
it changes color and after another period it disappears. This is different from the usual
DX Cluster windows which display details of stations you have already worked, that are QRT
or are not very interesting to you from another reason. A band map provides frequency-sorted
and highly filtered details which don't scroll away (like the DX Cluster window does).
There are two levels of filtering:</div>
<ul>
<li>Spot filtering set up for the DX Cluster window</li>
<li>Additional band map filtering capable of filtering out spots from momentarily unwanted
modes, contries, zones or continents. CQRLOG has another filter allowing you to watch spots
of special interest, ie. you are waiting for an expedition etc. You can set up another
filter showing spots only on the active band (the band which the radio is on) and the
actual mode (the mode the radio is on).</li>
</ul>
<div align="justify">You can add your own information by writing the call into the logging
screen in the usual way (like logging). Then press <strong>Ctrl-A</strong> and the entry
will be added to the band map. Your own entries are marked with an asterisk (here MD0CCE).
You can return to the frequency anytime, the call will jump into its box in the same way
as if clicked from the DX Cluster window. Click on any entry, you are on, prepared for
QSO logging.<br><br>
If the entry becomes older than the set time, it is displayed in a lighter color. Very old
entries will disappear, also if you log the station, the corresponding entry disappears
from the band map. The entries are always sorted by frequency.
</div>
</td></tr>
</tbody>
</table><br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%"><tbody>
<tr><td valign="top">
<a name="ch19"><h2><strong>Xplanet support</strong></h2></a>
<img src="img/h65.png" border="0"></td><td valign="top">
<div align="justify"><br><br>There is currently no other function than DX Cluster spot
displaying in true azimuthal projection with correct angles (azimuth) and distances.
Alternatively, a map without projection, ie. the globe as seen from space can be selected.</div>
</td></tr>
</tbody>
</table><br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%"><tbody>
<tr><td valign="top">
<a name="ch20"><h2><strong>Propagation indicator</strong></h2></a>
<img src="img/h110.png" border="0"></td><td valign="top"><div align="justify"><br><br>
There is a simple window providing propagation indices as provided by the NOAA Space
Weather Center. CQRLOG does not include a propagation forecast module but keen users
can estimate many parameters just from the supplied data.</div>
</td></tr>
</tbody>
</table><br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%"><tbody>
<td><td valign="top">
<a name="ch21"><h2><strong>Additional notes to a callsign</strong></h2></a>
<img src="img/h112.png" border="0"><div align="justify"><br><br>
CQRLOG provides virtually unlimited support for additional notes which can be attached
to a particular callsign (ie. an electronic QSL, a map showing the position, text files
with antenna details etc). Assuming that external viewers for the text, PDF, image
(jpg, png, gif) and HTML files are <a href="h1.html#ch4">set up properly</a>, all these
files can be displayed.<br><br>
The main program tree contains the <strong>call_data</strong> subfolder where any callsign
can have its own subfolder containing the files related to the call sign. The subfolder
for a call sign must be created manually. If this subfolder exists, a special icon "Call
has an attachment" appears at the bottom right corner of the <em>Comment to callsign</em>
field in the main logging screen. Click this icon and another window
<strong>Call attachment</strong> appears, showing the contents of the call sign subfolder.
Highlight the file you want to view and either double click or use the View button to display
the file. The number of call sign related subfolders in <strong>call_data</strong> is
unlimited, also the call sign related subfolder may contain any number of files.</div>
</td><td valign="middle"><img src="img/h113.png" border="0"><br><br>
<div align="justify">If the folder contains a file named "qsl_call_front.png" or
"qsl_call_front.jpg" (must be .png or .jpg), another icon "Call has a QSL image"
(ie. the ok2cqr subfolder contains qsl_ok2cqr_front.jpg). Click this icon and a QSL browser
appears showing the front of the QSL card. The "qsl_call_front.png" or "qsl_call_front.jpg"
<strong>is mandatory</strong> but there can also be a reverse side of QSL card with the
name "qsl_call_back.png" or "qsl_call_back.jpg". If this file is available, you can use
the "Front" and "Back" tabs to display both sides of the QSL card.<br><br>
<img src="img/h116.png" border="0"></div></td></tr>
</tbody>
</table><br><br>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h20.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h22.html">Next </a>&gt;</td>
</tr>
</tbody>
<table border="0" cellpadding="5" cellspacing="2">
<tbody>
<tr>
<td valign="top">
<img src="img/bulb.png"></td>
<td bgcolor="#ccffff" width="100%">
<strong><font color="blue">Our tip:</font></strong> For a nice looking cluster window,
choose a fixed-width font. We prefer Monospace Regular or Onuava but also Courier works
nicely. Apple's Monaco font is also very nice and has a slashed zero.
</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>
<table border="0" cellpadding="5" cellspacing="2" width="99%">
<tbody>
<tr>
<td valign="top">
<div align="justify">CQRLOG
has some predefined cluster nodes, however you will probably need to
set up a node of your preference. Click the 'Select' button and a list
of cluster node appears (see below). Click the 'New' option. Another dialog
appears (right). <br><br><img border="0" src="img/h18.png"></div>
</td>
<td valign="top"><img src="img/h19.png" border="0" align="top"><br>
<div style="text-align: justify;">Enter
the description (mostly the callsign). The 'Address' can be either an IP
or the name (see examples in the list). The 'Port' is given by a number.
Both address and port number can be obtained from the lists of DX cluster
nodes which are widely available on the internet.
<br><br><font color="red"><strong>Remember</strong></font> to put your callsign
into the 'User name' field. This will enable <strong>autologin</strong>.
The 'Password' column should remain empty in most cases because only few nodes
are password protected.
<br><br>A detailed list of DX Cluster nodes can be found
<a href="http://www.dxcluster.info/telnet/index.php"><strong>here</strong></a>
(page created by Jim, AD1C).
</div>
</td>
</tr>
</tbody>
</table>
<br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%">
<tbody>
<tr>
<td valign="top">
<a name="bh19"><h2><strong>Bandmap Operation</strong></h2></a>
<img src="img/h64.png" border="0"></td>
<td valign="top">
<div align="justify"><br><br>
The main purpose of a bandmap is to combine the most interesting info from two sources - the DX
Cluster and your personal notes. The bandmap combines a DX Cluster window with scratch
pad memories available on many radios, however a band map is more comfortable by far - you
don't need to manipulate subtle buttons on the radio panel, also the transceiver does
not indicate what is in the scratch pad memory. The band map is operated from the keyboard
and shows all at a glance.
<br><br>A valuable addition is the 'entries aging' option. If the bandmap entry is 'too' old,
it changes color and after another period it disappears. This is different from the usual
DX Cluster windows which display details of stations you have already worked, that are QRT
or are not very interesting to you from another reason. A band map provides frequency-sorted
and highly filtered details which don't scroll away (like the DX Cluster window does).
There are two levels of filtering:
</div>
<ul>
<li>Spot filtering set up for the DX Cluster window</li>
<li>Additional band map filtering capable of filtering out spots from momentarily unwanted
modes, contries, zones or continents. CQRLOG has another filter allowing you to watch spots
of special interest, ie. you are waiting for an expedition etc. You can set up another
filter showing spots only on the active band (the band which the radio is on) and the
actual mode (the mode the radio is on).
</li>
</ul>
<div align="justify">You can add your own information by writing the call into the logging
screen in the usual way (like logging). Then press <strong>Ctrl-A</strong> and the entry
will be added to the band map. Your own entries are marked with an asterisk (here MD0CCE).
You can return to the frequency anytime, the call will jump into its box in the same way
as if clicked from the DX Cluster window. Click on any entry, you are on, prepared for
QSO logging.<br><br>
If the entry becomes older than the set time, it is displayed in a lighter color. Very old
entries will disappear, also if you log the station, the corresponding entry disappears
from the band map. The entries are always sorted by frequency.
</div>
</td>
</tr>
</tbody>
</table>
<br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%">
<tbody>
<tr>
<td valign="top">
<a name="ch19"><h2><strong>Xplanet support</strong></h2></a>
<img src="img/h65.png" border="0"></td>
<td valign="top">
<div align="justify"><br><br>There is currently no other function than DX Cluster spot
displaying in true azimuthal projection with correct angles (azimuth) and distances.
Alternatively, a map without projection, ie. the globe as seen from space can be selected.
</div>
</td>
</tr>
</tbody>
</table>
<br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%">
<tbody>
<tr>
<td valign="top">
<a name="ch20"><h2><strong>Propagation indicator</strong></h2></a>
<img src="img/h110.png" border="0"></td>
<td valign="top">
<div align="justify"><br><br>
There is a simple window providing propagation indices as provided by the NOAA Space
Weather Center. CQRLOG does not include a propagation forecast module but keen users
can estimate many parameters just from the supplied data.
</div>
</td>
</tr>
</tbody>
</table>
<br><br>
<p align=center><img src=img/line.png></p>
<table border="0" cellpadding="5" cellspacing="2" width="99%">
<tbody>
<td>
<td valign="top">
<a name="ch21"><h2><strong>Additional notes to a callsign</strong></h2></a>
<img src="img/h112.png" border="0">
<div align="justify"><br><br>
CQRLOG provides virtually unlimited support for additional notes which can be attached
to a particular callsign (ie. an electronic QSL, a map showing the position, text files
with antenna details etc). Assuming that external viewers for the text, PDF, image
(jpg, png, gif) and HTML files are <a href="h1.html#ch4">set up properly</a>, all these
files can be displayed.<br><br>
The main program tree contains the <strong>call_data</strong> subfolder where any callsign
can have its own subfolder containing the files related to the call sign. The subfolder
for a call sign must be created manually. If this subfolder exists, a special icon "Call
has an attachment" appears at the bottom right corner of the <em>Comment to callsign</em>
field in the main logging screen. Click this icon and another window
<strong>Call attachment</strong> appears, showing the contents of the call sign subfolder.
Highlight the file you want to view and either double click or use the View button to display
the file. The number of call sign related subfolders in <strong>call_data</strong> is
unlimited, also the call sign related subfolder may contain any number of files.
</div>
</td>
<td valign="middle"><img src="img/h113.png" border="0"><br><br>
<div align="justify">If the folder contains a file named "qsl_call_front.png" or
"qsl_call_front.jpg" (must be .png or .jpg), another icon "Call has a QSL image"
(ie. the ok2cqr subfolder contains qsl_ok2cqr_front.jpg). Click this icon and a QSL browser
appears showing the front of the QSL card. The "qsl_call_front.png" or "qsl_call_front.jpg"
<strong>is mandatory</strong> but there can also be a reverse side of QSL card with the
name "qsl_call_back.png" or "qsl_call_back.jpg". If this file is available, you can use
the "Front" and "Back" tabs to display both sides of the QSL card.<br><br>
<img src="img/h116.png" border="0"></div>
</td>
</tr>
</tbody>
</table>
<br><br>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h20.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h22.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body>
</html>

192
help/h22.html
View File

@ -1,24 +1,31 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - QSL Records</title>
<html>
<head>
<title>CQRLOG - QSL Records</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h21.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h23.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h21.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h23.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
@ -27,18 +34,19 @@ in Preferences. This autobackup function creates an ADIF file with a backup of y
All QSL operations must be done from the QSO list (Ctrl-O from the logging screen).
The QSO list has a dedicated QSL menu item in the upper menu bar.
<ul>
<li><strong>Send QSL</strong> - the sent QSL menu has following options:<br><br>
<img src="img/h71.png" border="0"><br><br>
<ul>
<li>Buro (B) (a 'B' appears in the log, column 'QSL sent')</li>
<li>Direct (D)</li>
<li>eQSL(E)</li>
<li>Manager (M)</li>
<li>Do not send (N)</li>
<li>Manager direct (MD)</li>
<li>Manager buro (MB)</li>
<li>Confirmad by email (CE)</li>
</ul></ul>
<li><strong>Send QSL</strong> - the sent QSL menu has following options:<br><br>
<img src="img/h71.png" border="0"><br><br>
<ul>
<li>Buro (B) (a 'B' appears in the log, column 'QSL sent')</li>
<li>Direct (D)</li>
<li>eQSL(E)</li>
<li>Manager (M)</li>
<li>Do not send (N)</li>
<li>Manager direct (MD)</li>
<li>Manager buro (MB)</li>
<li>Confirmad by email (CE)</li>
</ul>
</ul>
If you want to send a QSL card, it is better to mark the QSO record with a similar mark
which begins with <strong>'S'</strong> (Send). This can be done with the Ctrl-W shortcut.
The QSO record will be marked with the default option <strong>'SB'</strong>
@ -46,8 +54,10 @@ The QSO record will be marked with the default option <strong>'SB'</strong>
choose an appropriate option. Once a QSL is complete (ready to go), press Ctrl-S.
The 'S' letter disappears making it clearly visible that the QSL is complete and sent.
<ul>
<li><strong>Receive QSL</strong> - navigate to the record for the QSL card received.
Press Ctrl-R and in the 'QSL_R' (QSL Received) field an 'X' will appear.</li></ul>
<li><strong>Receive QSL</strong> - navigate to the record for the QSL card received.
Press Ctrl-R and in the 'QSL_R' (QSL Received) field an 'X' will appear.
</li>
</ul>
<strong>QSL manager search</strong><br><br>
<img src="img/h53.png" border="0"><br><br>
When you choose this option A QSL manager window appears, in the lower left corner is
@ -57,96 +67,84 @@ For LoTW operations see <a href=h7.html><strong>here</strong></a>.
<a name="bh4"><h2><strong>QSL labels printing</strong></h2></a>
<div align="justify">QSL label printing is accomplished with the gLabels software
which is very powerful and allows you to print QSL labels of any size,
any number, also a whole QSL card can be designed and printed in professional quality
(printer depending). The gLabels software can be downloaded from
http://glabels.sourceforge.net/. It contains numerous predefined templates of label sheets
from many manufacturers. Most Linux distributions have gLabels in their repositories,
the Slackware package can be downloaded from the OK1RR personal repository at
<a href=http://www.ok1rr.com/download.php?list.10>
<strong>www.ok1rr.com</strong></a>.</div><br>
<strong>gLabels installation</strong><br><br>
gLabels is designed for Gnome and can be installed directly into distributions using
Gnome desktop manager. For KDE and other desktop managers, you need to install:
<pre>GTK+-2.10.x
LIBGNOME[UI]-2.16.x
LIBXML-2.6.x
LIBGLADE-2.6.x</pre>
To be more specific, gLabels needs the following Gnome components which should be
installed into KDE:<br>
<pre>avahi-0.6.23-i486-1as.tgz
gail-1.20.2-i486-1_rlw.tgz
gconf-2.20.1-i686-7as.tgz
gnome-keyring-2.20.3-i686-1dl.tgz
gnome-vfs-2.20.1-i686-1dl.tgz
libbonoboui-2.20.0-i686-1dl.tgz
libbonobo-2.20.3-i686-1dl.tgz
libgnomecanvas-2.20.1.1-i686-1dl.tgz
libgnomeui-2.20.1.1-i686-1dl.tgz
libgnome-2.20.1.1-i686-2dl.tgz
orbit2-2.14.12-i686-1dl.tgz</pre>
which is very powerful and allows you to print QSL labels of any size,
any number, also a whole QSL card can be designed and printed in professional quality
(printer depending). The gLabels software can be downloaded from
http://glabels.sourceforge.net/. It contains numerous predefined templates of label sheets
from many manufacturers. Most Linux distributions have gLabels in their repositories.
</div>
<br>
<div align="justify">The main task of CQRLOG is data preparation in a format (CSV) which
can be processed by gLabels. Several QSOs on a single label are possible and
gLabels provides all that we need. </div><br>
can be processed by gLabels. Several QSOs on a single label are possible and
gLabels provides all that we need.
</div>
<br>
<strong>QSL label template</strong><br>
<IMG src="img/h72.png"><br><br>
<div align="justify">A template with data to be printed, its order, typeface, position etc.
is needed to print your QSL labels. gLabels uses its own format for label design.
The result is a binary file. The syntax can be derived from the label designer picture,
you own label design can be derived from the example qsl.glabels included in the CQRLOG
installation.</div><br>
is needed to print your QSL labels. gLabels uses its own format for label design.
The result is a binary file. The syntax can be derived from the label designer picture,
you own label design can be derived from the example qsl.glabels included in the CQRLOG
installation.
</div>
<br>
<strong>Printing of individual QSL labels (default)</strong><br><br>
<IMG src="img/h71.png"><br><br>
<div align="justify">The QSO records should be properly marked. Records previously marked
SB (Send Bureau), SM (Send Manager), SMB (Send Manager - Bureau), SD (Send Direct) or SMD
(Send Manager- Direct) in any combination are exported.</div><br>
SB (Send Bureau), SM (Send Manager), SMB (Send Manager - Bureau), SD (Send Direct) or SMD
(Send Manager- Direct) in any combination are exported.
</div>
<br>
<IMG src="img/h70.png"><br><br>
<strong>Batch QSL label printing</strong>
<div align="justify">This method can be used if no QSO records are marked.
A filter can be set up, labels are printed for the filtered output and all such records
are marked as 'QSL sent'. To make this option effective, check the box 'Export all QSOs'
and 'Mark QSLs sent after export'. If you forget to check the 'Export all QSOs' box,
no output will be generated unless there are previously marked QSO records (see above).
If the 'Mark QSLs sent after export' remains unchecked, no QSO records will be marked as
'QSL sent'.</div><br>
A filter can be set up, labels are printed for the filtered output and all such records
are marked as 'QSL sent'. To make this option effective, check the box 'Export all QSOs'
and 'Mark QSLs sent after export'. If you forget to check the 'Export all QSOs' box,
no output will be generated unless there are previously marked QSO records (see above).
If the 'Mark QSLs sent after export' remains unchecked, no QSO records will be marked as
'QSL sent'.
</div>
<br>
<div align="justify">For both methods, the filtering potential can be utilized.
For example, you can filter out all QSOs with DJ3 stations and print QSL labels for them.
You will get such output:</div><br>
For example, you can filter out all QSOs with DJ3 stations and print QSL labels for them.
You will get such output:
</div>
<br>
<IMG src="img/h73.png"><br>
<div align="justify">There is no need to print QSL labels online on your printer. A very
good and proven trick is to print the labels to a PDF file, check that for correctness and
proper alignment against a real label sheet and then print it.</div>
good and proven trick is to print the labels to a PDF file, check that for correctness and
proper alignment against a real label sheet and then print it.
</div>
<br>
<p align=center><img src=img/line.png></p>
<a name="bh5"><h2><strong>Auto mark QSL</strong></h2></a>
<IMG src="img/h74.png"><br><br>
<div align="justify">This option allows you to set the QSL field for the first QSO with a
particular station on a band, mode, band/mode or for the first band, mode, band/mode
contact with a particular DXCC country regardless of the station.<br><br>
<IMG src="img/h75.png"><br><br>
It works in cooperation with the filters, however the test for the 'first QSO' is taken
from the whole log. You can limit your selection to 2008 but if you worked this station
in 1998 for first time, it will NOT be marked. This prevents you from sending multiple QSLs
for an already confirmed contact on that band, mode or band+mode.</div>
particular station on a band, mode, band/mode or for the first band, mode, band/mode
contact with a particular DXCC country regardless of the station.<br><br>
<IMG src="img/h75.png"><br><br>
It works in cooperation with the filters, however the test for the 'first QSO' is taken
from the whole log. You can limit your selection to 2008 but if you worked this station
in 1998 for first time, it will NOT be marked. This prevents you from sending multiple QSLs
for an already confirmed contact on that band, mode or band+mode.
</div>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h21.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h23.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h21.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h23.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>
</div></body>
</html>

60
help/h23.html
View File

@ -1,24 +1,31 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Filtering</title>
<html>
<head>
<title>CQRLOG - Filtering</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h22.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h24.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h22.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h24.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
@ -43,13 +50,14 @@ Choose 'ADIF' or 'HTML'. The usual File Save dialog appears (depending on the de
used). Choose a location and file name.<br><br>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h22.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h24.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h22.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h24.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>
</div></body>
</html>

87
help/h24.html
View File

@ -1,44 +1,60 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Statistics</title>
<html>
<head>
<title>CQRLOG - Statistics</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h23.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h27.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h23.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h27.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<a name="ah23"><h2><strong>Statistics</strong></h2></a>
There are 4 basic types of online statistics:<ul>
<li>DXCC</li>
<li>WAZ zones</li>
<li>ITU zones</li>
<li>IOTA</li></ul>
There are 4 basic types of online statistics:
<ul>
<li>DXCC</li>
<li>WAZ zones</li>
<li>ITU zones</li>
<li>IOTA</li>
</ul>
<p align=center><img src=img/line.png></p>
<strong>DXCC</strong><br><br>
The statistics can be viewed from both the login screen and the QSO list, however the menu
is slightly different. While the logging screen only allows viewing the statistics,
the QSO list can trigger a DXCC statistics rebuild.
<table cellspacing="2" border="0" cellpadding="5">
<tbody>
<tr><td><strong>Logging screen</strong></td><td><strong>QSO List</strong></td></tr>
<tr><td valign="top"><img src="img/h20.png" border="0"><td valign="top">
<img src="img/h46.png"></td></td></tr></tbody>
<tbody>
<tr>
<td><strong>Logging screen</strong></td>
<td><strong>QSO List</strong></td>
</tr>
<tr>
<td valign="top"><img src="img/h20.png" border="0">
<td valign="top">
<img src="img/h46.png"></td>
</td></tr>
</tbody>
</table>
The main difference is that the 'Details' window can ionly be activated (if not activated
at program startup, <a href="h1.html#ah4"><strong>see 'Preferences'</strong></a>)
@ -86,13 +102,14 @@ The small check box in the left lower corner toggles the worked/confirmed scores
The 'Save' button exports the statistics to an ASCII text file.
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h23.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h27.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h23.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h27.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>
</div></body>
</html>

152
help/h25.html
View File

@ -1,90 +1,106 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - QSO Record edit</title>
<html>
<head>
<title>CQRLOG - QSO Record edit</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>QSO record edit</strong></h2>
<div align="justify">Most editing operations can be done from the QSO list window
which appears by pressing Ctrl-O or clicking the corresponding menu item from the
logging screen.<br></div>
which appears by pressing Ctrl-O or clicking the corresponding menu item from the
logging screen.<br></div>
<p><img src=img/h2.png></p>
<div align="justify">The QSO list displays either all QSO records or a limited
number (QSO since ... year), depending on the
<a href="h1.html#ah2">Preferences -> Program</a> settings.<br></div>
number (QSO since ... year), depending on the
<a href="h1.html#ah2">Preferences -> Program</a> settings.<br></div>
<p><img src=img/h89.png></p>
<div align="justify">This window has a quite complex icon system which is explained here:<br></div>
<p><img src=img/h77.png></p>
<div align="justify">A single record can be edited (viewed, deleted) if you highlight
it using mouse or up/down keys and click the corresponding button (it will be EA8FC
in the example above). You will be returned to the QSO logging window which is now
changed to an Edit window. This status is clearly marked with the red message
<font color=#ff0000>(edit mode)</font> just behind the <em>Call</em> header which
is also displayed in red. All fields can be edited. When you finish editing, you should
save the chages using the ENTER key or by clicking the <em>Save QSO [enter]</em> button,
in the same way that you do when you log a new contact.<br></div>
it using mouse or up/down keys and click the corresponding button (it will be EA8FC
in the example above). You will be returned to the QSO logging window which is now
changed to an Edit window. This status is clearly marked with the red message
<font color=#ff0000>(edit mode)</font> just behind the <em>Call</em> header which
is also displayed in red. All fields can be edited. When you finish editing, you should
save the chages using the ENTER key or by clicking the <em>Save QSO [enter]</em> button,
in the same way that you do when you log a new contact.<br></div>
<p><img src=img/h93.png></p>
<div align="justify">A QSO record can now be edited directly from the logging screen.
The QSOs made in last few days <a href="h1.html#ah4">(see Preferences -> New QSO)</a>
are displayed in the logging screen. Right click on the required record which appears
in the logging screen, and select edit QSO, exactly as described above
(here 5R8IC will be edited).<br></div>
The QSOs made in last few days <a href="h1.html#ah4">(see Preferences -> New QSO)</a>
are displayed in the logging screen. Right click on the required record which appears
in the logging screen, and select edit QSO, exactly as described above
(here 5R8IC will be edited).<br></div>
<p><img src=img/h94.png></p>
<div align="justify">You can also view the record and search in the QRZ database or
look for the QSL manager in the IK3QAR QSL manager database.
<p align=center><img src=img/line.png></p>
look for the QSL manager in the IK3QAR QSL manager database.
<p align=center><img src=img/line.png></p>
<a name="grp"><h2><strong>Group edit</strong></h2></a>
<div align="justify">A record can be tagged by clicking the corresponding icon or
with the mouse - hold the Ctrl key on the keyboard and left click on the QSO record
to be tagged.<br></div>
<p><img src=img/h90.png></p>
<div align="justify">Click the <em>Edit QSO</em> button and the group edit menu
appears:<br></div>
<p><img src=img/h91.png></p>
<div align="justify">Choose the field to be edited from the pulldown menu:<br></div>
<p><img src=img/h92.png></p>
<div align="justify">The field name changes. Enter the value (word, string) which
will appear in <strong>ALL</strong> tagged QSO records. Click the <em>Apply</em>
button and the value in all tagged records will be changed to the value entered
into <em>Value:</em> box. All values entered within a session are temporarily stored
so you can list it with the "down arrow" button in the group edit menu.</div>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font>
There is no UNDO option!</strong> If you click the <em>Apply</em> button,
there is no way to return to previous values! Make a backup before any group edit
operation!</td></tr></tbody></table>
<a name="grp"><h2><strong>Group edit</strong></h2></a>
<div align="justify">A record can be tagged by clicking the corresponding icon or
with the mouse - hold the Ctrl key on the keyboard and left click on the QSO record
to be tagged.<br></div>
<p><img src=img/h90.png></p>
<div align="justify">Click the <em>Edit QSO</em> button and the group edit menu
appears:<br></div>
<p><img src=img/h91.png></p>
<div align="justify">Choose the field to be edited from the pulldown menu:<br></div>
<p><img src=img/h92.png></p>
<div align="justify">The field name changes. Enter the value (word, string) which
will appear in <strong>ALL</strong> tagged QSO records. Click the <em>Apply</em>
button and the value in all tagged records will be changed to the value entered
into <em>Value:</em> box. All values entered within a session are temporarily stored
so you can list it with the "down arrow" button in the group edit menu.
</div>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font>
There is no UNDO option!</strong> If you click the <em>Apply</em> button,
there is no way to return to previous values! Make a backup before any group edit
operation!
</td>
</tr>
</tbody>
</table>
<p align=center><img src=img/line.png></p>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div></body></html>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</div>
</body>
</html>

157
help/h26.html
View File

@ -1,80 +1,97 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - CW Interface</title>
<html>
<head>
<title>CQRLOG - CW Interface</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=#ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=#ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h25.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h25.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>CW interface</strong></h2>
<li align=justify>Assuming that your CW interface is properly set up and working,
you can add and/or edit your CW messages.<br><br>
First, set up your CW messages. In the upper menu bar on the logging screen,
click on the 'CW' item.<br><br>
<img src=img/h96.png><br><br>
Choose the 'Messages' option. In the resulting window, edit your CW messages which
will be played if you press the corresponding F key (in the logging screen).
You can set up to 10 predefined messages:<br><br>
<img src=img/h97.png><br><br>
There are some predefined macros which you can use in your messages:<br><br>
<table border="0" cellpadding="5" cellspacing="2" width="50%"><tbody>
<tr><td bgcolor=#ffffcc valign="top">
%mc - my callsign<br>
%mn - my name<br>
%mq - my qth<br>
%r - rst to be sent<br>
%n - his name<br>
%c - his callsign<br>
| - half space<br>
%h - greetings (GM/GA/GE) calculated from local time of worked station<br>
%rs - rst to be sent, 9 replaced with N<br>
you can add and/or edit your CW messages.<br><br>
First, set up your CW messages. In the upper menu bar on the logging screen,
click on the 'CW' item.<br><br>
<img src=img/h96.png><br><br>
Choose the 'Messages' option. In the resulting window, edit your CW messages which
will be played if you press the corresponding F key (in the logging screen).
You can set up to 10 predefined messages:<br><br>
<img src=img/h97.png><br><br>
There are some predefined macros which you can use in your messages:<br><br>
<table border="0" cellpadding="5" cellspacing="2" width="50%">
<tbody>
<tr>
<td bgcolor=#ffffcc valign="top">
%mc - my callsign<br>
%mn - my name<br>
%mq - my qth<br>
%r - rst to be sent<br>
%n - his name<br>
%c - his callsign<br>
| - half space<br>
%h - greetings (GM/GA/GE) calculated from local time of worked station<br>
%rs - rst to be sent, 9 replaced with N<br>
</td></tr></tbody></table><br>
Another option 'CW type' is a powerful keyboard keyer with 3 operation modes:<br><br>
<img src=img/h98.png><br><br><ul>
<li><strong>letter mode</strong> - the character of the corresponding keyboard key is
sent immediately on pressing the key
<li><strong>word mode</strong> - a whole word is typed, sending starts after pressing
of the spacebar
<li><strong>word mode, first word in letter mode</strong> - a combination of above.
The keyer begins in letter mode to avoid unneccessary delays, if you type fast enough
it switches to word mode</li></ul>
These modes are common on professional keyboard keyers.<br><br>
The <strong>keying speed</strong> can be changed with PgUp (QRQ) and PgDn (QRS) keys
in 2 WPM steps. In the 'CW type' window, it can also be changed with the small arrow
buttons to the right of the speed display. The actual speed is always displayed in
the status line of the logging screen.<br><br>
<img src=img/h99.png><br><br>
Setup howtos for both <a href=cwd.html><strong>cwdaemon</strong></a> and
<a href=wkusb.html><strong>Winkey USB</strong></a> are available.<br><br>
</div>
<p align=center><img src=img/line.png></p>
<br>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h25.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>
</td>
</tr>
</tbody>
</table>
<br>
Another option 'CW type' is a powerful keyboard keyer with 3 operation modes:<br><br>
<img src=img/h98.png><br><br>
<ul>
<li><strong>letter mode</strong> - the character of the corresponding keyboard key is
sent immediately on pressing the key
<li><strong>word mode</strong> - a whole word is typed, sending starts after pressing
of the spacebar
<li><strong>word mode, first word in letter mode</strong> - a combination of above.
The keyer begins in letter mode to avoid unneccessary delays, if you type fast enough
it switches to word mode
</li>
</ul>
These modes are common on professional keyboard keyers.<br><br>
The <strong>keying speed</strong> can be changed with PgUp (QRQ) and PgDn (QRS) keys
in 2 WPM steps. In the 'CW type' window, it can also be changed with the small arrow
buttons to the right of the speed display. The actual speed is always displayed in
the status line of the logging screen.<br><br>
<img src=img/h99.png><br><br>
Setup howtos for both <a href=cwd.html><strong>cwdaemon</strong></a> and
<a href=wkusb.html><strong>Winkey USB</strong></a> are available.<br><br>
</div>
<p align=center><img src=img/line.png></p>
<br>
<table width="100%" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h25.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>

234
help/h27.html
View File

@ -1,155 +1,173 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - SQL console</title>
<html>
<head>
<title>CQRLOG - SQL console</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html#ah23"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h3.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html#ah23"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h3.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>SQL Console</strong></h2>
<div style="text-align: justify;">To enter the SQL Console, go to QSO list (Ctrl+O)
and in the upper menu bar go to <em>Filter -> SQL console.</em>
and in the upper menu bar go to <em>Filter -> SQL console.</em>
<div align="left">
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="50%" align="left"><img src=img/h114.png border="0"></td></tr>
<tr><td width="50%" align="left"><img src=img/h115.png border="0"></td>
</tr>
</tbody>
</table><br>
The icons in the upper menu allow the following actions:<br><br>
<strong>1st icon</strong>
&nbsp; &nbsp;&nbsp;Execute SQL statement<br>
<strong>2nd icon</strong>
&nbsp;&nbsp;&nbsp;Previous SQL command<br>
<strong>3rd icon</strong>
&nbsp;&nbsp;&nbsp;Next SQL command<br>
<strong>4th icon</strong>
&nbsp;&nbsp;&nbsp;Load SQL command from a file<br>
<strong>5th icon</strong>
&nbsp;&nbsp;&nbsp;Save SQL command to a file<br>
<strong>6th icon</strong>
&nbsp;&nbsp;&nbsp;Export data to a csv or html file<br>
<strong>7th icon</strong>
&nbsp;&nbsp;&nbsp;Get SQL command currently used in the main database. For example,
if a filter is set, clicking this icon allows you to edit the SQL command created
by the filter.<br><br>
<div align="left">
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="50%" align="left"><img src=img/h114.png border="0"></td>
</tr>
<tr>
<td width="50%" align="left"><img src=img/h115.png border="0"></td>
</tr>
</tbody>
</table>
<br>
The icons in the upper menu allow the following actions:<br><br>
<strong>1st icon</strong>
&nbsp; &nbsp;&nbsp;Execute SQL statement<br>
<strong>2nd icon</strong>
&nbsp;&nbsp;&nbsp;Previous SQL command<br>
<strong>3rd icon</strong>
&nbsp;&nbsp;&nbsp;Next SQL command<br>
<strong>4th icon</strong>
&nbsp;&nbsp;&nbsp;Load SQL command from a file<br>
<strong>5th icon</strong>
&nbsp;&nbsp;&nbsp;Save SQL command to a file<br>
<strong>6th icon</strong>
&nbsp;&nbsp;&nbsp;Export data to a csv or html file<br>
<strong>7th icon</strong>
&nbsp;&nbsp;&nbsp;Get SQL command currently used in the main database. For example,
if a filter is set, clicking this icon allows you to edit the SQL command created
by the filter.<br><br>
<h3><strong>Tables in cqrlogXXX:</strong></h3><br>
<h3><strong>Tables in cqrlogXXX:</strong></h3><br>
where XXX is numer of the log e.g. cqrlog001 for the first log.<br><br>
<strong>cqrlog_main</strong><br>
&nbsp;&nbsp;&nbsp;the main table with all QSO records<br><br>
where XXX is numer of the log e.g. cqrlog001 for the first log.<br><br>
<strong>cqrlog_main</strong><br>
&nbsp;&nbsp;&nbsp;the main table with all QSO records<br><br>
<strong>notes</strong><br>
&nbsp;&nbsp;&nbsp;table containing the call sign related notes<br><br>
<strong>notes</strong><br>
&nbsp;&nbsp;&nbsp;table containing the call sign related notes<br><br>
<strong>profiles</strong><br>
&nbsp;&nbsp;&nbsp;list of QTH profiles<br><br>
<strong>profiles</strong><br>
&nbsp;&nbsp;&nbsp;list of QTH profiles<br><br>
<strong>db_version</strong><br>
&nbsp;&nbsp;&nbsp;database version<br><br>
<strong>db_version</strong><br>
&nbsp;&nbsp;&nbsp;database version<br><br>
<strong>award1 ... award5</strong><br>
&nbsp;&nbsp;&nbsp;external tables used for memberships<br><br>
<strong>award1 ... award5</strong><br>
&nbsp;&nbsp;&nbsp;external tables used for memberships<br><br>
<strong>zipcode1 ... zipcode3</strong><br>
&nbsp;&nbsp;&nbsp;external tables used for zip codes<br><br>
<strong>zipcode1 ... zipcode3</strong><br>
&nbsp;&nbsp;&nbsp;external tables used for zip codes<br><br>
<strong>long_note</strong><br>
&nbsp;&nbsp;&nbsp;a long note valid for the whole log<br><br>
<strong>long_note</strong><br>
&nbsp;&nbsp;&nbsp;a long note valid for the whole log<br><br>
<strong>cqrlog_config</strong><br>
&nbsp;&nbsp;&nbsp;configuration file<br><br>
<strong>cqrlog_config</strong><br>
&nbsp;&nbsp;&nbsp;configuration file<br><br>
<strong>dxcc_id</strong><br>
&nbsp;&nbsp;&nbsp;a list of DXCC countries<br><br>
<strong>dxcc_id</strong><br>
&nbsp;&nbsp;&nbsp;a list of DXCC countries<br><br>
<strong>log_changes</strong><br>
&nbsp;&nbsp;&nbsp;a list of changes made to cqrlog_main database filled by
triggers (only when log upload function is enabled)<br><br>
<strong>log_changes</strong><br>
&nbsp;&nbsp;&nbsp;a list of changes made to cqrlog_main database filled by
triggers (only when log upload function is enabled)<br><br>
<strong>upload_status</strong><br>
&nbsp;&nbsp;&nbsp;last IDs of uploaded QSO to online logs<br><br>
<strong>upload_status</strong><br>
&nbsp;&nbsp;&nbsp;last IDs of uploaded QSO to online logs<br><br>
<strong>view_cqrlog_main_by_callsign</strong><br>
&nbsp;&nbsp;&nbsp;a view to show QSO sorted by callsign<br><br>
<strong>call_alert</strong>
&nbsp;&nbsp;&nbsp;list of callsigns with mode and band for dxcluster alert function<br><br>
<strong>view_cqrlog_main_by_qsodate</strong><br>
&nbsp;&nbsp;&nbsp;a view to show QSO sorted by qsodate<br><br>
<strong>freqmem</strong>
&nbsp;&nbsp;&nbsp;list of memories for fast frequency switching<br><br>
<strong>view_cqrlog_main_by_callsign</strong><br>
&nbsp;&nbsp;&nbsp;a view to show QSO sorted by callsign<br><br>
<strong>view_cqrlog_main_by_qsodate</strong><br>
&nbsp;&nbsp;&nbsp;a view to show QSO sorted by qsodate<br><br>
<h3><strong>Tables in cqrlog_common:</strong></h3><br>
<h3><strong>Tables in cqrlog_common:</strong></h3><br>
The common database used by all logs. <br>
The common database used by all logs. <br>
<strong>bands</strong><br>
&nbsp;&nbsp;&nbsp;band limits (lower/upper end)<br><br>
<strong>bands</strong><br>
&nbsp;&nbsp;&nbsp;band limits (lower/upper end)<br><br>
<strong>db_version</strong><br>
&nbsp;&nbsp;&nbsp;database version<br><br>
<strong>db_version</strong><br>
&nbsp;&nbsp;&nbsp;database version<br><br>
<strong>bandcn</strong><br>
&nbsp;&nbsp;&nbsp;info if the country is worked and confirmed by a paper QSL or via LoTW<br><br>
<strong>bandcn</strong><br>
&nbsp;&nbsp;&nbsp;info if the country is worked and confirmed by a paper QSL or via LoTW<br><br>
<strong>dxcc_ref</strong><br>
&nbsp;&nbsp;&nbsp;the current DXCC reference table<br><br>
<strong>dxcc_ref</strong><br>
&nbsp;&nbsp;&nbsp;the current DXCC reference table<br><br>
<strong>dxclusters</strong><br>
&nbsp;&nbsp;&nbsp;list of DX cluster nodes<br><br>
<strong>dxclusters</strong><br>
&nbsp;&nbsp;&nbsp;list of DX cluster nodes<br><br>
<strong>iota_list</strong><br>
&nbsp;&nbsp;&nbsp;IOTA reference list<br><br>
<strong>iota_list</strong><br>
&nbsp;&nbsp;&nbsp;IOTA reference list<br><br>
<strong>log_list</strong><br>
&nbsp;&nbsp;&nbsp;list of logs created in cqrlog<br><br>
<strong>log_list</strong><br>
&nbsp;&nbsp;&nbsp;list of logs created in cqrlog<br><br>
<strong>qslmngr</strong><br>
&nbsp;&nbsp;&nbsp;list of QSL managers<br><br>
<strong>qslmngr</strong><br>
&nbsp;&nbsp;&nbsp;list of QSL managers<br><br>
</div>
<strong>Example:</strong><br><br>
</div>
<strong>Example:</strong><br><br>
<div align="justify">Select from the database date, call sign, frequency and mode,
where the QSO date is from timespan between Jan. 1. 2009 and Dec. 31. 2009 and the WAZ
zone is 15.<br><br>
<div align="justify">Select from the database date, call sign, frequency and mode,
where the QSO date is from timespan between Jan. 1. 2009 and Dec. 31. 2009 and the WAZ
zone is 15.<br><br>
<strong>SQL command:</strong><br>
<strong>SQL command:</strong><br>
<pre>
SELECT qsodate, callsign, freq, mode FROM view_cqrlog_main_by_qsodate WHERE
qsodate >= '2009-01-01' and qsodate <= '2009-31-12' and waz = 15
</pre><br>
The databases structures are listed <a href=sql_console.html><strong>here</strong>.</a></div>
</pre>
<br>
The databases structures are listed <a href=sql_console.html><strong>here</strong>.</a></div>
</div>
<p align=center><img src=img/line.png></p><br>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html#ah23"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h3.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html#ah23"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h3.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>
</body>
</html>

545
help/h3.html
View File

@ -1,289 +1,296 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Maintenance</title>
<html>
<head>
<title>CQRLOG - Maintenance</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h4.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h4.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>Maintenance</strong></h2>
<div style="text-align: justify;">
<a name=ah24><strong>ADIF import</strong></a><br><br>
The main purpose is to add QSO records from other logging and/or contesting programs.
You may need it if you migrate from another logger or if you are adding contacts made
in a contest (any modern contesting program has the ADIF export facility, some older
programs may need a third party conversion utility).
<br><br>
Go to QSO list (Ctrl+O on the main logging screen or File -> Show QSO list from the menu).
<br><br>
<img src="img/h39.png" border="0"><br><br>
From the menu <strong>here</strong> choose File -> Import -> ADIF.<br><br>
Click on 'ADIF' and an 'Open file' dialog appears.<br><br>
<img src="img/h40.png" border="0"><br><br>Navigate to the file you want to import and
click 'Open'. You will see a new dialog, click the 'Import' button here. You can also
add a QTH profile and a note ('Remarks:') which will appear on any imported QSO record.
Using this option, a portable, mobile or QRP operation can be clearly marked.<br><br>
<img src="img/h41.png" border="0"><br><br>
If you import a huge file, you will see a progress bar, however import of a small file
is so fast that you never notice the progress indicator.<br><br>
<img src="img/h42.png" border="0"><br><br>
The previous window now shows the import completion, the number of imported records and
the number of errors. If the ADIF file contains incorrect entries, they will be stored
separately in the file <strong>errors.adi</strong> located in the 'log_data' subfolder.
You can fix the errors manually and import again. <br><br>
<img src="img/h43.png" border="0"><br><br>
Duplicate entries (contacts already in the log) are indicated with a separate dialog
allowing you to exclude or include these records.
<p align=center><img src=img/line.png></p>
<a name=ah25><strong>ADIF export</strong></a><br><br>
Go to QSO list using Ctrl-O or choose the QSO list from the upper menu - item 'File'.<br><br>
<img src=img/h39.png><br><br>
From the QSO list, choose 'Export' in the menu - item 'File'.<br><br>
<img src=img/h45.png><br><br>
Choose 'ADIF'. An usual a dialog appears (depending on the desktop used). Choose a
location and file name.<br><br>
<p align=center><img src=img/line.png></p>
<a name=ah26><strong>HTML export</strong></a><br><br>
The same as above, only difference is to choose the 'HTML' option.<br><br>
<p align=center><img src=img/line.png></p>
<a name=ah27><strong>Program version update</strong></a><br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr>
<td valign="top"><img src="img/exc.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);">
<strong><font color="red">WARNING!</font></strong> Making a BACKUP of your log file
before program update <strong><font color="red">is a MUST!</font></strong>
</td></tr></tbody></table>
Download the new version from the <a href=http://www.cqrlog.com><strong>CQRLOG web site</strong>
</a> (other mirrors may appear later). Unpack the tarball into a temporary location and run the
installer <pre>cqrlog_install.sh</pre>
<img src="img/h48.png"><br><br>
and choose 'Upgrade from previous version'.
Run the program and perform the DXCC Statistics Rebuild. That's all.<br><br>
The upgrade process will <strong>NOT overwrite</strong> your log file or your
configuration.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top">
<img src="img/exc.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);">
<strong><font color="red">WARNING!</font></strong> If you choose 'Complete new install',
your log and configuration <strong><font color="red">will be overwritten!</font>
</strong></td></tr></tbody></table>
<p align=center><img src=img/line.png></p>
<a name=ah28><strong>Country files update</strong></a><br><br>
CQRLOG checks the country file version at startup and the update can be
<strong>automated</strong> if you choose this option in <a href="h1.html#ch3">Preferences.</a>
The automated update needs only a click 'Yes' in the update dialog to confirm it.
<br><br><img src=img/h67.png><br><br>
<strong>Manual update</strong><br><br>
The country file set for CQRLOG is distributed as a tar.gz archive with a unique name,
ie. cqrlog-cty080227.tar.gz. The number (here 080227) denotes the version number which
is the same as the release date.<br><br>
Contents of the country file set (8 files):
<ul>
<li>AreaOK1RR.tbl</li>
<li>CallResolution.tbl</li>
<li>Country.tab</li>
<li>CountryDel.tab</li>
<li>iota.tbl</li>
<li>Exceptions.tbl</li>
<li>Ambiguous.tbl</li>
<li>README</li></ul>
<strong>How to update Country files:</strong><br>
<ol>
<li>Unpack and copy all the files into the /ctyfiles folder in your CQRLOG main folder.
The purpose of this folder is to store these files only, it is not bound to CQRLOG and
does not affect its function.</li>
<li>Start CQRLOG and select the 'Show QSO list' from the 'File' item in the main menu.
You can also get there using shortcut Ctrl-O.</li>
<li>If you are already in the QSO list, go to menu. Click the 'File' item, then the 'Import'
option. Choose the DXCC data option, located at lowest position. A dialog appears,
navigate to your /ctyfiles folder. Click the 'Open' button. All files are read and if
the import completes, a small window with the message 'Import complete. Please restart
program' appears. Click the OK button and quit CQRLOG.</li>
<li>Restart CQRLOG. The update is finished.</li></ol>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr>
<td valign="top"><img src="img/note.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(204, 255, 255);">
<strong><font color="blue">Note:</font></strong> While opening your new country files
[see 3.], you dont need to open a particular file. The 'Open' button starts a procedure
which reads ALL files in the /ctyfiles folder.</td></tr></tbody></table>
<br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr>
<td valign="top"><img src="img/exc.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);">
<strong><font color="red">WARNING!</font></strong> Don't attempt to create your own
country files. This can result in the program crashing or incorrect statistics. If you
find an incorrectly resolved station (no matter if current log or an old record), send
a note directly to me: martin@ok1rr.com. <strong><font color="red">ALWAYS</font></strong>
replace all files in the /ctyfiles folder! If you leave an old file or update only a single
file from the new version, the resulting tables will become out-of-sync which leads to
incorrect statistics. Also, the logger may not work properly.</td></tr></tbody></table>
<br>
NEW LOG FILE - you can create a new log file (crqlog.fdb) where you can import ADIF format
QSO data. A new log file is created by CQRLOG automatically if the program does not find
a cqrlog.fdb file in the /log_data folder. If you create a new log file, import the most
recent country files set BEFORE any ADIF QSO data import! The best way is to erase all
files in the /ctyfiles folder and copy the 8 files from your new archive.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr>
<td valign="top"><img src="img/exc.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);">
<strong><font color="red">WARNING!</font></strong> If you update your country files or
upgrade the CQRLOG version, <strong>always</strong> perform the 'Rebuild DXCC statistics'
which is accessible from the QSO list screen.</td></tr></tbody></table><br>
Some users have reported that their DXCC statistics became 'out of sync' and the
actual DXCC scoring does not match the results reported by CQRLOG.<br><br>
Remember that a regular rebuild of your DXCC statistics is a matter of importance.
Rebuild if you upgrade country files, rebuild also if you upgrade the program version!
<p align=center><img src=img/line.png></p>
<a name=ah29><strong>QSL Manager Database update</strong></a><br><br>
Since version 0.8.0 CQRLOG uses its own QSL Manager database in a very simple, plain
text format (CSV, semicolon separated). The update is very simple. The automated update
checks the availability of a new version, downloads and unpacks the tar.gz file if
available. The new version must be imported - go to QSO list (Ctrl+O or from menu
<em>File -> Show QSO list</em>) and choose the <em>File -> Import -> Import
qsl managers database</em>.<br><br>
A manual update is also possible if you download a recent version from the CQRLOG site
<a href=http://www.cqrlog.com><strong>http://www.cqrlog.com</strong></a>.<br><br>
<img src=img/h107.png><br><br>
The QSL Manager database format is as follows:<br>
<a name=ah24><strong>ADIF import</strong></a><br><br>
The main purpose is to add QSO records from other logging and/or contesting programs.
You may need it if you migrate from another logger or if you are adding contacts made
in a contest (any modern contesting program has the ADIF export facility, some older
programs may need a third party conversion utility).
<br><br>
Go to QSO list (Ctrl+O on the main logging screen or File -> Show QSO list from the menu).
<br><br>
<img src="img/h39.png" border="0"><br><br>
From the menu <strong>here</strong> choose File -> Import -> ADIF.<br><br>
Click on 'ADIF' and an 'Open file' dialog appears.<br><br>
<img src="img/h40.png" border="0"><br><br>Navigate to the file you want to import and
click 'Open'. You will see a new dialog, click the 'Import' button here. You can also
add a QTH profile and a note ('Remarks:') which will appear on any imported QSO record.
Using this option, a portable, mobile or QRP operation can be clearly marked.<br><br>
<img src="img/h41.png" border="0"><br><br>
If you import a huge file, you will see a progress bar, however import of a small file
is so fast that you never notice the progress indicator.<br><br>
<img src="img/h42.png" border="0"><br><br>
The previous window now shows the import completion, the number of imported records and
the number of errors. If the ADIF file contains incorrect entries, they will be stored
separately in the file <strong>errors.adi</strong> located in the 'log_data' subfolder.
You can fix the errors manually and import again. <br><br>
<img src="img/h43.png" border="0"><br><br>
Duplicate entries (contacts already in the log) are indicated with a separate dialog
allowing you to exclude or include these records.
<p align=center><img src=img/line.png></p>
<a name=ah25><strong>ADIF export</strong></a><br><br>
Go to QSO list using Ctrl-O or choose the QSO list from the upper menu - item 'File'.<br><br>
<img src=img/h39.png><br><br>
From the QSO list, choose 'Export' in the menu - item 'File'.<br><br>
<img src=img/h45.png><br><br>
Choose 'ADIF'. An usual a dialog appears (depending on the desktop used). Choose a
location and file name.<br><br>
<p align=center><img src=img/line.png></p>
<a name=ah26><strong>HTML export</strong></a><br><br>
The same as above, only difference is to choose the 'HTML' option.<br><br>
<p align=center><img src=img/line.png></p>
<strong>How to update Country files:</strong><br>
<ol>
<li>Unpack and copy all the files into the /ctyfiles folder in your CQRLOG main folder.
The purpose of this folder is to store these files only, it is not bound to CQRLOG and
does not affect its function.
</li>
<li>Start CQRLOG and select the 'Show QSO list' from the 'File' item in the main menu.
You can also get there using shortcut Ctrl-O.
</li>
<li>If you are already in the QSO list, go to menu. Click the 'File' item, then the 'Import'
option. Choose the DXCC data option, located at lowest position. A dialog appears,
navigate to your /ctyfiles folder. Click the 'Open' button. All files are read and if
the import completes, a small window with the message 'Import complete. Please restart
program' appears. Click the OK button and quit CQRLOG.
</li>
<li>Restart CQRLOG. The update is finished.</li>
</ol>
<table width="100%" border="0" cellpadding="5" cellspacing="2">
<tbody>
<tr>
<td valign="top"><img src="img/note.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(204, 255, 255);">
<strong><font color="blue">Note:</font></strong> While opening your new country files
[see 3.], you dont need to open a particular file. The 'Open' button starts a procedure
which reads ALL files in the /ctyfiles folder.
</td>
</tr>
</tbody>
</table>
<br>
<table width="100%" border="0" cellpadding="5" cellspacing="2">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);">
<strong><font color="red">WARNING!</font></strong> Don't attempt to create your own
country files. This can result in the program crashing or incorrect statistics. If you
find an incorrectly resolved station (no matter if current log or an old record), send
a note directly to me: martin@ok1rr.com. <strong><font color="red">ALWAYS</font></strong>
replace all files in the /ctyfiles folder! If you leave an old file or update only a single
file from the new version, the resulting tables will become out-of-sync which leads to
incorrect statistics. Also, the logger may not work properly.
</td>
</tr>
</tbody>
</table>
<br>
<table width="100%" border="0" cellpadding="5" cellspacing="2">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);">
<strong><font color="red">WARNING!</font></strong> If you update your country files or
upgrade the CQRLOG version, <strong>always</strong> perform the 'Rebuild DXCC statistics'
which is accessible from the QSO list screen.
</td>
</tr>
</tbody>
</table>
<br>
Some users have reported that their DXCC statistics became 'out of sync' and the
actual DXCC scoring does not match the results reported by CQRLOG.<br><br>
Remember that a regular rebuild of your DXCC statistics is a matter of importance.
Rebuild if you upgrade country files, rebuild also if you upgrade the program version!
<p align=center><img src=img/line.png></p>
<a name=ah29><strong>QSL Manager Database update</strong></a><br><br>
Since version 0.8.0 CQRLOG uses its own QSL Manager database in a very simple, plain
text format (CSV, semicolon separated). The update is very simple. The automated update
checks the availability of a new version, downloads and unpacks the tar.gz file if
available. The new version must be imported - go to QSO list (Ctrl+O or from menu
<em>File -> Show QSO list</em>) and choose the <em>File -> Import -> Import
qsl managers database</em>.<br><br>
A manual update is also possible if you download a recent version from the CQRLOG site
<a href=http://www.cqrlog.com><strong>http://www.cqrlog.com</strong></a>.<br><br>
<img src=img/h107.png><br><br>
The QSL Manager database format is as follows:<br>
<pre>
call;qsl_manager;publishing_date
Example:
3D2BV;JA1PBV;2008-01
</pre>
You can maintain your own records but we carefully maintain this database with verified
records from reliable sources (DX Bulletins). The database is updated monthly and the
covered timespan of QSL Managers is limited to 10 years after publishing date. After
this time, the expired records will be removed and stored in another file (archive)
which will be available on the CQRLOG site
<a href=http://www.cqrlog.com><strong>http://www.cqrlog.com</strong></a>.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr><td valign="top">
<img src="img/note.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(204, 255, 255);">
<strong><font color="blue">Note:</font></strong> Because the QRZ.COM entries very often
contain details useful for direct lookup but not suitable to print on QSL labels,
choose the option <em>'Ignore QRZ.COM qsl info'</em> in the <em>Preferences ->
New QSO</em> dialog. </td></tr></tbody></table>
<br>
If a station has more than one QSL Manager, click the small button to the left of the
QSL VIA field.<br><br>
<img src=img/h106.png><br><br>
A popup window of selections appears:<br><br>
<img src=img/h105.png><br><br>
Navigate to the appropriate QSL manager, use the publishing date column or verify the
QSL manager from another source. This ensures that the QSL label will contain the
proper QSL manager.
<p align=center><img src=img/line.png></p>
<a name=ah30><strong>Statistics rebuilding</strong></a><br><br>
<img src=img/h46.png><br><br>
The only way to rebuild your statistics is <strong>from the QSO list</strong>.
The 'Statistics' menu item has the 'Rebuild DXCC statistics' option (the similar option
on the logging screen does NOT have a 'Rebuild' option).<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr>
<td valign="top"><img src="img/exc.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);">
<strong><font color="red">WARNING!</font></strong> The statistics rebuilding takes a long
time if your log contains tens of thousands records!</td></tr></tbody></table><br>
<img src=img/h46.png><br><br>
A warning appears before the rebuilding process. If you answer 'Yes', be prepared for a
long wait.<br><br>
<img src=img/h47.png>
<p align=center><img src=img/line.png></p>
<a name=ah31><strong>Membership databases</strong></a><br><br>
CQRLOG supports online tracking of up to 5 memberships simultaneously. The membership
databases can also be used for filter creation, along with a date span (from-to).
The tracking and filtering feature is not limited to membership, you can create your
own databases using lists of your particular interests (short-term awards, local
groups etc.). The databases have a pure text format with data columns separated by
a semicolon ';'.<br><br>
The default installation contains data of some 57 clubs: AFM, AGCW, ARKTIKA, A1-CLUB,
A1-OP, CAV, CCT, CFO, CFT, CONVENIAT, CTC, CWJF, CWSP, DIG, DTC, EHSC, EPC, FFR, FIRAC,
FISTS, FMC, FOC, GACW, GQRPC, HACWG, HHC, HH, HSC, HTC, JAIG, MARCONISTA, MCL, MFCA,
MF, OKDXC, OKDXF, OTC-SARA, PRC, PRL, QCWA, RAFARS, RIA, RNARS, RRDXA, RTC, SHSC, SKCC,
SPAR, SPDXC, TEN-TEN, TFC, UDXC, UFT, VHSC, VRK, WAP, 070-CLUB, 9ACWG.
<br>You can go to<br>
<pre>/home/~/cqrlog/members</pre>
(the tilde ~ represents the name of your personal subdirectory within the 'home' folder).
<br><br>
Any membership file also contains a header consisting of two lines:
You can maintain your own records but we carefully maintain this database with verified
records from reliable sources (DX Bulletins). The database is updated monthly and the
covered timespan of QSL Managers is limited to 10 years after publishing date. After
this time, the expired records will be removed and stored in another file (archive)
which will be available on the CQRLOG site
<a href=http://www.cqrlog.com><strong>http://www.cqrlog.com</strong></a>.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2">
<tbody>
<tr>
<td valign="top">
<img src="img/note.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(204, 255, 255);">
<strong><font color="blue">Note:</font></strong> Because the HamQTH.com/QRZ.COM entries very often
contain details useful for direct lookup but not suitable to print on QSL labels,
choose the option <em>'Ignore HamQTH.com/QRZ.COM qsl info'</em> in the <em>Preferences ->
New QSO</em> dialog.
</td>
</tr>
</tbody>
</table>
<br>
If a station has more than one QSL Manager, click the small button to the left of the
QSL VIA field.<br><br>
<img src=img/h106.png><br><br>
A popup window of selections appears:<br><br>
<img src=img/h105.png><br><br>
Navigate to the appropriate QSL manager, use the publishing date column or verify the
QSL manager from another source. This ensures that the QSL label will contain the
proper QSL manager.
<p align=center><img src=img/line.png></p>
<a name=ah30><strong>Statistics rebuilding</strong></a><br><br>
<img src=img/h46.png><br><br>
The only way to rebuild your statistics is <strong>from the QSO list</strong>.
The 'Statistics' menu item has the 'Rebuild DXCC statistics' option (the similar option
on the logging screen does NOT have a 'Rebuild' option).<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);">
<strong><font color="red">WARNING!</font></strong> The statistics rebuilding takes a long
time if your log contains tens of thousands records!
</td>
</tr>
</tbody>
</table>
<br>
<img src=img/h46.png><br><br>
A warning appears before the rebuilding process. If you answer 'Yes', be prepared for a
long wait.<br><br>
<img src=img/h47.png>
<p align=center><img src=img/line.png></p>
<a name=ah31><strong>Membership databases</strong></a><br><br>
CQRLOG supports online tracking of up to 5 memberships simultaneously. The membership
databases can also be used for filter creation, along with a date span (from-to).
The tracking and filtering feature is not limited to membership, you can create your
own databases using lists of your particular interests (short-term awards, local
groups etc.). The databases have a pure text format with data columns separated by
a semicolon ';'.<br><br>
The default installation contains data of some 57 clubs: AFM, AGCW, ARKTIKA, A1-CLUB,
A1-OP, CAV, CCT, CFO, CFT, CONVENIAT, CTC, CWJF, CWSP, DIG, DTC, EHSC, EPC, FFR, FIRAC,
FISTS, FMC, FOC, GACW, GQRPC, HACWG, HHC, HH, HSC, HTC, JAIG, MARCONISTA, MCL, MFCA,
MF, OKDXC, OKDXF, OTC-SARA, PRC, PRL, QCWA, RAFARS, RIA, RNARS, RRDXA, RTC, SHSC, SKCC,
SPAR, SPDXC, TEN-TEN, TFC, UDXC, UFT, VHSC, VRK, WAP, 070-CLUB, 9ACWG.
<br>You can go to<br>
<pre>/home/~/.config/cqrlog/members</pre>
(the tilde ~ represents the name of your personal subdirectory within the 'home' folder).
<br><br>
Any membership file also contains a header consisting of two lines:
<pre>HSC
High Speed Club</pre>
where the first line represents the <strong>short</strong> name of the club and the second
line is the long <strong>club</strong> name. Both names must be in the header on separate
lines. The first line must be the same as the filename without suffix, ie. the HSC
membership list <strong>must</strong> be <pre>hsc.txt</pre> The mandatory suffix is
<strong>.txt</strong> and the filename must be in <strong>lowercase</strong>.<br><br>
You can examine the syntax which is more descriptive than this short example,
however there are basically 3 types of membership list files:<br><br>
<strong>1. Simple list of call signs.</strong> It does not contain any membership
number or date limits. Syntax:<br><br>
&nbsp;&nbsp;W5LGY<br>
&nbsp;&nbsp;W5LJT<br>
&nbsp;&nbsp;W5LKL<br>
&nbsp;&nbsp;W5LP<br><br>
ie. a <strong>single</strong> call per line.<br><br>
<strong>2. List of call signs with membership numbers.</strong> Syntax:<br><br>
&nbsp;&nbsp;DL5JAN;4603<br>
&nbsp;&nbsp;DL5JBM;4746<br>
&nbsp;&nbsp;DL5JBN;4642<br>
&nbsp;&nbsp;DL5JBW;5740<br><br>
ie. a <strong>single</strong> call and membership number per line. The call and the
membership number are separated by a semicolon ';'.<br><br>
<strong>3. List of call signs with membership numbers and date limits.</strong>Used
for short term awards or time span limited memberships. Syntax:<br><br>
&nbsp;&nbsp;6O2NG;533;1957-04;2005-03<br>
&nbsp;&nbsp;6Y5SR;868;1966-03;1982-07<br>
&nbsp;&nbsp;6Y5XG;331;1951-05;-<br>
&nbsp;&nbsp;7J1AEF;1297;1976-06;-<br><br>
ie. a <strong>single</strong> call, membership number and datelimits from-to, separated by
a semicolon ';', per line. See above the two optins: 6O2NG with membership number 533 was
a member of the club from April, 1957 to March, 2005. 6Y5XG with number 331 started his
membership May, 1951 and is still a member. The dash instead of a date (separated from
the begin date by a semicolon) denotes that the membership is still active. A dash can
be used <strong>only</strong> in the field for 'to'.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr>
<td valign="top"><img src="img/exc.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);">
<strong><font color="red">WARNING!</font></strong> You must keep lists of your particular
interests updated yourself! It is impossible for the authors to keep all these tables up-to-date,
however if you update a list and would like to share it with others, you are welcome!
</td></tr></tbody></table><br>
<p align=center><img src=img/line.png></p>
<a name=ah32><strong>Log backup</strong></a><br><br>
Your log is in the file<br>
<pre>/home/~/cqrlog/log_data/cqrlog.fdb</pre>
(the tilde ~ represents the name of your personal subdirectory within the 'home' folder).
<br><br>
Backup this file, however it is big. If you want to save space, export your log into
an ADIF file which is about half the size of the .fdb file. ADIF is also version
independent. Zipped or tared ADIF files also have a reasonable size if your log
contains several 100 000 records.
<p align=center><img src=img/line.png></p>
where the first line represents the <strong>short</strong> name of the club and the second
line is the long <strong>club</strong> name. Both names must be in the header on separate
lines. The first line must be the same as the filename without suffix, ie. the HSC
membership list <strong>must</strong> be
<pre>hsc.txt</pre>
The mandatory suffix is
<strong>.txt</strong> and the filename must be in <strong>lowercase</strong>.<br><br>
You can examine the syntax which is more descriptive than this short example,
however there are basically 3 types of membership list files:<br><br>
<strong>1. Simple list of call signs.</strong> It does not contain any membership
number or date limits. Syntax:<br><br>
&nbsp;&nbsp;W5LGY<br>
&nbsp;&nbsp;W5LJT<br>
&nbsp;&nbsp;W5LKL<br>
&nbsp;&nbsp;W5LP<br><br>
ie. a <strong>single</strong> call per line.<br><br>
<strong>2. List of call signs with membership numbers.</strong> Syntax:<br><br>
&nbsp;&nbsp;DL5JAN;4603<br>
&nbsp;&nbsp;DL5JBM;4746<br>
&nbsp;&nbsp;DL5JBN;4642<br>
&nbsp;&nbsp;DL5JBW;5740<br><br>
ie. a <strong>single</strong> call and membership number per line. The call and the
membership number are separated by a semicolon ';'.<br><br>
<strong>3. List of call signs with membership numbers and date limits.</strong>Used
for short term awards or time span limited memberships. Syntax:<br><br>
&nbsp;&nbsp;6O2NG;533;1957-04;2005-03<br>
&nbsp;&nbsp;6Y5SR;868;1966-03;1982-07<br>
&nbsp;&nbsp;6Y5XG;331;1951-05;-<br>
&nbsp;&nbsp;7J1AEF;1297;1976-06;-<br><br>
ie. a <strong>single</strong> call, membership number and datelimits from-to, separated by
a semicolon ';', per line. See above the two optins: 6O2NG with membership number 533 was
a member of the club from April, 1957 to March, 2005. 6Y5XG with number 331 started his
membership May, 1951 and is still a member. The dash instead of a date (separated from
the begin date by a semicolon) denotes that the membership is still active. A dash can
be used <strong>only</strong> in the field for 'to'.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(255, 255, 204);">
<strong><font color="red">WARNING!</font></strong> You must keep lists of your particular
interests updated yourself! It is impossible for the authors to keep all these tables up-to-date,
however if you update a list and would like to share it with others, you are welcome!
</td>
</tr>
</tbody>
</table>
<br>
<p align=center><img src=img/line.png></p>
<a name=ah32><strong>Log backup</strong></a><br><br>
Your log is in the <br>
<pre>/home/~/.config/cqrlog/</pre>
(the tilde ~ represents the name of your personal subdirectory within the 'home' folder).
<br><br>
Backup this directory, however it is big. If you want to save space, export your log into
an ADIF file which is about half the size of the database directory. ADIF is also version
independent. Zipped or tared ADIF files also have a reasonable size if your log
contains several 100 000 records.
<p align=center><img src=img/line.png></p>
</div>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h4.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h24.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h4.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>
</body>
</html>

107
help/h4.html
View File

@ -1,63 +1,72 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - I want to...</title>
<html>
<head>
<title>CQRLOG - I want to...</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h3.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h5.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h3.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h5.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>I want to...</strong></h2>
<div style="text-align: justify;"><ul>
<a name="ah33"><li><strong>Prepare LoTW or eQSL log/update</strong></li>
<strong>eQSL.cc</strong> - Create a filter for the time span you want to QSL or choose
another criteria and export to ADIF which can be directly uploaded to the eQSL.cc
server.<br><br>
<strong>LoTW</strong> must be signed and converted to the .tq8 format required by
the ARRL. Full description is <a href=h7.html><strong>here</strong></a>.
<strong>Trusted QSL</strong> is needed for LoTW operations. You need the latest version,
download <a href="http://www.ok2cqr.com/?q=lotw-and-linux"><strong>here</strong></a>
(sources, SuSE and Fedora packages). Ubuntu and Debian have this package in their
repositories. Slackware packages download <a href="http://www.ok1rr.com/request.php?196">
<strong>here</strong></a>.
<br><br>
<li><strong>Suggest a new feature</strong></li>
Probably the best way is to make a suggestion on the
<a href=http://www.cqrlog.com/?q=forum/4><strong>CQRLOG web site</strong></a>.<br><br>
Other lists and forums:<ul>
<div align="left"><li><a href="http://tech.groups.yahoo.com/group/cqrlog/">
<strong>Yahoo Groups</strong> (http://tech.groups.yahoo.com/group/cqrlog/)</a>
(you must be a member of Yahoo Groups)</li>
<li><a href="http://nagano.cz/cgi-bin/mailman/listinfo/cqrlog"><strong>Mailing list
at Nagano Server</strong> (http://nagano.cz/cgi-bin/mailman/listinfo/cqrlog)</a></ul><br>
You can get also in touch with the authors, for emails see the title page.</li></ul></div>
<div style="text-align: justify;">
<ul>
<a name="ah33">
<li><strong>Prepare LoTW or eQSL log/update</strong></li>
<strong>eQSL.cc</strong> you have to be registered on eQSL website.<br><br>
<strong>LoTW</strong> must be signed and converted to the .tq8 format required by
the ARRL. Full description is <a href=h7.html><strong>here</strong></a>.
<strong>Trusted QSL</strong> is needed for LoTW operations. Ubuntu and Debian have this package in their
repositories.
<br><br>
<li><strong>Suggest a new feature</strong></li>
Probably the best way is to make a suggestion on the
<a href=http://www.cqrlog.com/?q=forum/4><strong>CQRLOG web site</strong></a>.<br><br>
Other lists and forums:
<ul>
<div align="left">
<li><a href="http://tech.groups.yahoo.com/group/cqrlog/">
<strong>Yahoo Groups</strong> (http://tech.groups.yahoo.com/group/cqrlog/)</a>
(you must be a member of Yahoo Groups)
</li>
</ul>
<br>
You can get also in touch with the authors, for emails see the title page.</li></ul>
</div>
</div>
<p align=center><img src=img/line.png></p><br>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h3.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h5.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h3.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h5.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>
</body>
</html>

189
help/h5.html
View File

@ -1,111 +1,112 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Troubleshooting</title>
<html>
<head>
<title>CQRLOG - Troubleshooting</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h4.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h6.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h4.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h6.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<h2><strong>Troubleshooting</strong></h2>
<div style="text-align: justify;">
<a name="ah37"><em><strong>My radio control (CAT) does not work</strong></em><ul>
<li><strong>Check your ports.</strong> You must be a member of the user group,
which has permission to use ttyS* or ttyUSB* devices.</li>
<li><strong>Check that your radio is properly set up </strong>
<a href="h1.html#ah7"><em>(see here)</em></a>. Check that the radio type is properly
set up <a href="h6.html"><em>(see here)</em></a>. Click the 'Settings' button and
check the port settings - ttyS* or ttyUSB* number and <strong>all</strong>
communication parameters.</li>
<li><strong>Is the poll rate set too fast?</strong> Try a lower setting (higher number).</li>
</ul><br>
<p align=center><img src=img/line.png></p>
<em><strong>When I click on a spot in the DX cluster window it populates the log
but it does not move the rig to the new operating frequency.</strong> I am using
an Icom 756 (original nonPro model).</strong></em><ul>
<li>Set IF filters bandwidth to 0 (Preferences -> Modes tab).</li>
</ul><br>
<p align=center><img src=img/line.png></p>
<a name="ah38"><em><strong>I'm unable to autologin to the Cluster</strong></em><ul>
Open the DX cluster window and click the 'Select' button. In the
<a href="h21.html#ah19"><strong>DX Cluster List</strong></a> choose the 'Edit' option.
A dialog appears:<br><br>
<img src="img/h55.png" border="0"></ul>
<br>
The 'User name:' field must be filled with your call sign.<br>
<p align=center><img src=img/line.png></p>
<a name="ah39"><em><strong>I get this error message when trying to load:</strong></em><ul>
<pre>"Can't load library: /home/ham/cqrlog/libfbembed.so.2.1.1
Press OK to ignore and risk data corruption.
Press Cancel to kill the program. </pre></ul>
<p>The library <pre>libstdc++5</pre> is not installed.</p>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr>
<td valign="top"><img src="img/note.png"></td>
<td bgcolor=#eaeaea valign="top" align="justify"><strong><font color="blue">Note:</font>
Since version 0.8.5 the libstdc++5</strong> does not need to be installed, it
<strong>is already part of the installation</strong> and can be found in the /lib folder
(file name libstdc++.so.5.0.7., size 737 192 B). If you get the above mentioned
error message, check the /lib folder for presence of libstdc++.so.5.0.7.
</td></tr></tbody></table>
<a name="ah37"><em><strong>My radio control (CAT) does not work</strong></em>
<ul>
<li><strong>Check your ports.</strong> You must be a member of the user group,
which has permission to use ttyS* or ttyUSB* devices.
</li>
<li><strong>Check that your radio is properly set up </strong>
<a href="h1.html#ah7"><em>(see here)</em></a>. Click the 'Settings' button and
check the port settings - ttyS* or ttyUSB* number and <strong>all</strong>
communication parameters.
</li>
<li><strong>Is the poll rate set too fast?</strong> Try a lower setting (higher number).</li>
</ul>
<br>
<p align=center><img src=img/line.png></p>
<em><strong>When I click on a spot in the DX cluster window it populates the log
but it does not move the rig to the new operating frequency.</strong> I am using
an Icom 756 (original nonPro model).</strong></em>
<ul>
<li>Set IF filters bandwidth to 0 (Preferences -> Modes tab).</li>
</ul>
<br>
<p align=center><img src=img/line.png></p>
<a name="ah38"><em><strong>I'm unable to autologin to the Cluster</strong></em>
<ul>
Open the DX cluster window and click the 'Select' button. In the
<a href="h21.html#ah19"><strong>DX Cluster List</strong></a> choose the 'Edit' option.
A dialog appears:<br><br>
<img src="img/h55.png" border="0"></ul>
<br>
The 'User name:' field must be filled with your call sign.<br>
<p align=center><img src=img/line.png></p>
</div>
<p align=center><img src=img/line.png></p>
<a name="ah40"><em><strong>I have trouble with LoTW login getting the following error
message:</strong></em><ul>
message:</strong></em>
<ul>
<pre>PROGRESS shows:
NOT logged
Error: 0
Error: ssl_none</pre>
<p>Solution: libssl-dev must be installed</p></ul>
<p align=center><img src=img/line.png></p>
<a name="ah41"><em><strong>CQRLOG is very slow or does not run at all</strong></em><ul>
<p align="justify">The accompanying problem is an abonormally high CPU load. The problem
is instant polling of a non-existent (not responding) radio. Your radio setup is
probably incorrect. Try to downoad a default cqrlog.cfg from the CQRLOG web site
(www.cqrlog.com) and copy it into your /cqrlog/log_data folder. Backup your old
cqrlog.cfg before if you want. The default cqrlog.cfg redirects all polling to the
hamlib dummy radio (model=1] and the high CPU load should return to its
normal values.<br><br>Then you should set up your radio again.
Don't use too low a poll rate, a value of 300 is sufficient.</p></ul></div>
<p align=center><img src=img/line.png></p>
<a name="ah42"><em><strong>64 bit - CQRLOG won't install (won't run)</strong></em><ul>
<p align="justify">32 bit libraries must be installed! If not, please install
bug-buddy.i386 and all the libstdc.i386 packages. Also hamlib 32bit version
has to be installed.</p></ul></div>
<p align=center><img src=img/line.png></p>
<a name="ah43"><em><strong>Disappearing fonts in the Radio Control Window</strong></em><ul>
<p>If your Radio Control Window looks like this</p>
<p><img src=img/h108.png></p>
<p>go to Preferences -> Fonts and uncheck the 'Use default settings' option</p>
<p><img src=img/h109.png></p>
<div align="justify"><p>and set fonts manually. Choose any font of your preference
which is present on your system (you will see it in the font choice pulldown dialog
'Select font'). This fixes this problem.</p></ul></div>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h4.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h6.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<p>Solution: libssl-dev must be installed</p></ul>
<p align=center><img src=img/line.png></p>
<a name="ah41"><em><strong>CQRLOG is very slow or does not run at all</strong></em>
<ul>
<p align="justify">The accompanying problem is an abonormally high CPU load. The problem
is instant polling of a non-existent (not responding) radio. Your radio setup is
probably incorrect. Try to downoad a default cqrlog.cfg from the CQRLOG web site
(www.cqrlog.com) and copy it into your /cqrlog/log_data folder. Backup your old
cqrlog.cfg before if you want. The default cqrlog.cfg redirects all polling to the
hamlib dummy radio (model=1] and the high CPU load should return to its
normal values.<br><br>Then you should set up your radio again.
Don't use too low a poll rate, a value of 300 is sufficient.</p></ul>
</div>
<p align=center><img src=img/line.png></p>
<a name="ah43"><em><strong>Disappearing fonts in the Radio Control Window</strong></em>
<ul>
<p>If your Radio Control Window looks like this</p>
<p><img src=img/h108.png></p>
<p>go to Preferences -> Fonts and uncheck the 'Use default settings' option</p>
<p><img src=img/h109.png></p>
<div align="justify"><p>and set fonts manually. Choose any font of your preference
which is present on your system (you will see it in the font choice pulldown dialog
'Select font'). This fixes this problem.</p>
</ul>
</div>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h4.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h6.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>
</body>
</html>

468
help/h6.html
View File

@ -1,24 +1,31 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - Supported Radio Types</title>
<html>
<head>
<title>CQRLOG - Supported Radio Types</title>
</head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
/td></tr></tbody></table>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
/td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h5.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h7.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h5.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h7.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
@ -26,204 +33,249 @@ in Preferences. This autobackup function creates an ADIF file with a backup of y
<strong><h2>Supported radio types</h2></strong>
<br>
<div style="text-align: justify;">
The actual list of supported radios depends on the hamlib version.
You can obtain the actual list using the command:
The actual list of supported radios depends on the hamlib version.
You can obtain the actual list using the command:
<pre>
rigctl --list > riglist.txt
</pre>
Remember, the <i>rigctl</i> executable must be on your path.<br>
The snapshot version 1.2.7. supports the following radio types:
Remember, the <i>rigctl</i> executable must be on your path.<br>
The snapshot version 1.2.7. supports the following radio types:
<pre>
Rig# Mfg Model Vers. Status
===================================================================
1701 Alinco DX-77 0.7 Beta
2506 AmQRP DDS-60 0.1 Alpha
508 AOR AR2700 0.5 Untested
506 AOR AR3000A 0.5 Beta
505 AOR AR3030 0.4 Untested
504 AOR AR5000 0.5 Beta
514 AOR AR5000A 0.5 Alpha
503 AOR AR7030 0.4 Beta
502 AOR AR8000 0.5 Untested
501 AOR AR8200 0.5 Alpha
513 AOR AR8600 0.5 Beta
2503 Coding Technologies Digital World Travel0.1 Untested
902 Drake R-8A 0.5 Beta
903 Drake R-8B 0.5 Untested
2303 DTTS Microwave SocieDttSP 0.1 Alpha
221 Elecraft K2 0.6 Beta
229 Elecraft K3 0.6 Beta
2501 Elektor Elektor 3/04 0.4 Stable
2507 Elektor Elektor SDR-USB 0.1 Beta
2301 Flex-radio SDR-1000 0.2 Untested
1 Hamlib Dummy 0.4 Beta
2 Hamlib NET rigctl 0.2 Beta
1901 Hamlib RPC rig 0.3 Beta
354 Icom IC ID-1 0.4 Untested
303 Icom IC-271 0.4 Untested
304 Icom IC-275 0.4.1 Beta
306 Icom IC-471 0.4 Untested
307 Icom IC-475 0.4.1 Beta
360 Icom IC-7000 0.4 Untested
355 Icom IC-703 0.4 Untested
309 Icom IC-706 0.4 Untested
310 Icom IC-706MkII 0.4 Untested
311 Icom IC-706MkIIG 0.4 Stable
312 Icom IC-707 0.4 Untested
313 Icom IC-718 0.4 Alpha
314 Icom IC-725 0.4.1 Beta
315 Icom IC-726 0.4 Stable
316 Icom IC-728 0.4 Untested
319 Icom IC-735 0.4.1 Beta
320 Icom IC-736 0.4 Untested
321 Icom IC-737 0.4 Untested
323 Icom IC-746 0.4 Untested
346 Icom IC-746PRO 0.4 Untested
324 Icom IC-751 0.4.1 Beta
326 Icom IC-756 0.4 Alpha
327 Icom IC-756PRO 0.4 Untested
347 Icom IC-756PROII 0.4 Alpha
357 Icom IC-756PROIII 0.4 Untested
328 Icom IC-761 0.4.1 Stable
329 Icom IC-765 0.4 Stable
330 Icom IC-775 0.4.1 Untested
345 Icom IC-78 0.4 Untested
356 Icom IC-7800 0.4 Untested
331 Icom IC-781 0.4.1 Untested
332 Icom IC-820H 0.4 Alpha
334 Icom IC-821H 0.4 Alpha
344 Icom IC-910 0.4 Beta
335 Icom IC-970 0.4 Untested
402 Icom IC-PCR100 0.5 Beta
401 Icom IC-PCR1000 0.5 Alpha
336 Icom IC-R10 0.4 Untested
358 Icom IC-R20 0.4 Untested
340 Icom IC-R7000 0.4.0 Alpha
337 Icom IC-R71 0.4 Untested
341 Icom IC-R7100 0.4.0 Untested
338 Icom IC-R72 0.4 Untested
339 Icom IC-R75 0.4 Beta
343 Icom IC-R9000 0.4 Untested
342 Icom ICR-8500 0.4.1 Beta
605 JRC NRD-525 0.1 Alpha
606 JRC NRD-535D 0.6 Stable
607 JRC NRD-545 DSP 0.6 Beta
1801 Kachina 505DSP 0.3 Alpha
215 Kenwood R-5000 0.6 Alpha
217 Kenwood TH-D7A 0.3 Alpha
220 Kenwood TH-F7E 0.3 Beta
223 Kenwood TH-G71 0.3 Beta
226 Kenwood TM-D700 0.3 Untested
227 Kenwood TM-V7 0.3 Beta
230 Kenwood TRC-80 0.6 Alpha
225 Kenwood TS-140S 0.6.1 Beta
214 Kenwood TS-2000 0.6.3 Beta
202 Kenwood TS-440 0.6.0.6 Alpha
203 Kenwood TS-450S 0.6 Beta
228 Kenwood TS-480 0.6.1 Untested
201 Kenwood TS-50S 0.6 Untested
204 Kenwood TS-570D 0.6.1 Stable
216 Kenwood TS-570S 0.6.1 Stable
224 Kenwood TS-680S 0.6.1 Beta
205 Kenwood TS-690S 0.6 Alpha
206 Kenwood TS-711 0.6.0.6 Untested
207 Kenwood TS-790 0.6.1 Alpha
208 Kenwood TS-811 0.6.0.6 Untested
209 Kenwood TS-850 0.6.0 Beta
210 Kenwood TS-870S 0.6.0 Beta
222 Kenwood TS-930 0.6 Untested
211 Kenwood TS-940S 0.6.0.6 Alpha
213 Kenwood TS-950SDX 0.6 Beta
1004 Lowe HF-235 0.3 Alpha
2508 mRS miniVNA 0.1 Alpha
353 Optoelectronics OptoScan456 0.3 Beta
352 Optoelectronics OptoScan535 0.3 Beta
1103 Racal RA6790/GM 0.1 Untested
804 Radio Shack PRO-2052 0.3 Untested
2401 RFT EKD-500 0.4 Alpha
2502 SAT-Schneider DRT1 0.2 Beta
1402 Skanti TRP8000 0.2 Untested
2201 TAPR DSP-10 0.2 Alpha
351 Ten-Tec Omni VI Plus 0.2 Beta
1603 Ten-Tec RX-320 0.5 Beta
1604 Ten-Tec RX-340 0.1 Untested
1605 Ten-Tec RX-350 0.1 Untested
1607 Ten-Tec TT-516 Argonaut V 0.2 Stable
1602 Ten-Tec TT-538 Jupiter 0.3 Alpha
1601 Ten-Tec TT-550 0.2 Beta
1608 Ten-Tec TT-565 Orion 0.4 Beta
1611 Ten-Tec TT-588 Omni VII 0.3 Alpha
802 Uniden BC245xlt 0.3 Untested
806 Uniden BC250D 0.3 Untested
801 Uniden BC780xlt 0.3 Untested
803 Uniden BC895xlt 0.3 Untested
810 Uniden BCD-396T 0.3 Alpha
811 Uniden BCD-996T 0.3 Alpha
2601 Video4Linux SW/FM radio 0.1 Untested
1204 Watkins-Johnson WJ-8888 0.2 Untested
1501 Winradio WR-1000 0.6 Untested
1502 Winradio WR-1500 0.6 Untested
1503 Winradio WR-1550 0.6 Untested
1504 Winradio WR-3100 0.6 Untested
1505 Winradio WR-3150 0.6 Untested
1506 Winradio WR-3500 0.6 Untested
1507 Winradio WR-3700 0.6 Untested
117 Yaesu FRG-100 0.4 Beta
119 Yaesu FRG-8800 0.2 Untested
118 Yaesu FRG-9600 0.2 Untested
121 Yaesu FT-100 0.4 Beta
103 Yaesu FT-1000D 0.0.6 Alpha
124 Yaesu FT-1000MP 0.1 Alpha
129 Yaesu FT-2000 0.21 Untested
127 Yaesu FT-450 0.21.1 Beta
110 Yaesu FT-736R 0.2 Untested
105 Yaesu FT-747GX 0.3 Alpha
106 Yaesu FT-757GX 0.4 Beta
107 Yaesu FT-757GXII 0.4 Stable
109 Yaesu FT-767GX 0.1 Alpha
120 Yaesu FT-817 0.5 Beta
111 Yaesu FT-840 0.1 Untested
101 Yaesu FT-847 0.4 Beta
122 Yaesu FT-857 0.3 Beta
115 Yaesu FT-890 0.1 Stable
123 Yaesu FT-897 0.3.2 Beta
113 Yaesu FT-900 0.1 Untested
114 Yaesu FT-920 0.3.4 Stable
128 Yaesu FT-950 0.21.1 Alpha
116 Yaesu FT-990 0.1 Alpha
130 Yaesu FTDX-9000 0.21 Untested
125 Yaesu MARK-V Field FT-10000.0.5 Alpha
104 Yaesu MARK-V FT-1000MP 0.0.5 Alpha
126 Yaesu VR-5000 0.2 Alpha
------------------------------------------------------------------
Rig# Mfg Model Vers. Status
=============================================================================
1 Hamlib Dummy 0.5 Beta
2 Hamlib NET rigctl 0.3 Beta
101 Yaesu FT-847 0.5 Beta
103 Yaesu FT-1000D 0.0.6 Alpha
104 Yaesu MARK-V FT-1000MP 0.0.5 Alpha
105 Yaesu FT-747GX 0.4.1 Beta
106 Yaesu FT-757GX 0.4.1 Beta
107 Yaesu FT-757GXII 0.4 Stable
109 Yaesu FT-767GX 1.0 Stable
110 Yaesu FT-736R 0.3 Stable
111 Yaesu FT-840 0.1 Untested
113 Yaesu FT-900 0.1 Untested
114 Yaesu FT-920 2010-08-23 Stable
115 Yaesu FT-890 0.1 Stable
116 Yaesu FT-990 0.2.1 Alpha
117 Yaesu FRG-100 0.4 Beta
118 Yaesu FRG-9600 0.2 Untested
119 Yaesu FRG-8800 0.2 Untested
120 Yaesu FT-817 0.5.1 Beta
121 Yaesu FT-100 0.4.1 Beta
122 Yaesu FT-857 0.4 Beta
123 Yaesu FT-897 0.3.3 Beta
124 Yaesu FT-1000MP 0.1.1 Beta
125 Yaesu MARK-V Field FT-1000MP 0.0.5 Alpha
126 Yaesu VR-5000 0.2 Alpha
127 Yaesu FT-450 0.22.1 Beta
128 Yaesu FT-950 0.22.2 Stable
129 Yaesu FT-2000 0.22.1 Stable
130 Yaesu FTDX-9000 0.22.1 Untested
131 Yaesu FT-980 0.1 Alpha
132 Yaesu FT-DX5000 0.22 Alpha
133 Vertex Standard VX-1700 1.1 Alpha
201 Kenwood TS-50S 0.8 Untested
202 Kenwood TS-440 0.8.0.6.1 Alpha
203 Kenwood TS-450S 0.8.1 Beta
204 Kenwood TS-570D 0.8.2 Stable
205 Kenwood TS-690S 0.8.1 Beta
206 Kenwood TS-711 0.8.0.6.1 Untested
207 Kenwood TS-790 0.8.2 Alpha
208 Kenwood TS-811 0.8.0.6.1 Untested
209 Kenwood TS-850 0.8.1 Beta
210 Kenwood TS-870S 0.8.0 Beta
211 Kenwood TS-940S 0.8.0.6.1 Alpha
213 Kenwood TS-950SDX 0.8 Beta
214 Kenwood TS-2000 0.8.4 Beta
215 Kenwood R-5000 0.6.1 Alpha
216 Kenwood TS-570S 0.8.1 Stable
217 Kenwood TH-D7A 0.5 Alpha
219 Kenwood TH-F6A 0.5 Beta
220 Kenwood TH-F7E 0.5.1 Beta
221 Elecraft K2 20120615 Beta
222 Kenwood TS-930 0.8 Untested
223 Kenwood TH-G71 0.5 Beta
224 Kenwood TS-680S 0.8.1 Beta
225 Kenwood TS-140S 0.8.1 Beta
226 Kenwood TM-D700 0.5 Beta
227 Kenwood TM-V7 0.5 Beta
228 Kenwood TS-480 0.8.5 Untested
229 Elecraft K3/KX3 20120615 Beta
230 Kenwood TRC-80 0.8 Alpha
231 Kenwood TS-590S 0.8.1 Beta
232 SigFox Transfox 20111223 Alpha
233 Kenwood TH-D72A 0.5.1 Alpha
234 Kenwood TM-D710 0.5 Untested
302 Icom IC-1275 0.7 Beta
303 Icom IC-271 0.7 Untested
304 Icom IC-275 0.7.1 Beta
306 Icom IC-471 0.7 Untested
307 Icom IC-475 0.7.1 Beta
309 Icom IC-706 0.7.1 Untested
310 Icom IC-706MkII 0.7.1 Untested
311 Icom IC-706MkIIG 0.7.2 Stable
312 Icom IC-707 0.7 Untested
313 Icom IC-718 0.7.1 Beta
314 Icom IC-725 0.7.1 Stable
315 Icom IC-726 0.7 Stable
316 Icom IC-728 0.7 Untested
319 Icom IC-735 0.7.1 Beta
320 Icom IC-736 0.7 Untested
321 Icom IC-737 0.7 Untested
322 Icom IC-738 0.7 Untested
323 Icom IC-746 0.7.1 Beta
324 Icom IC-751 0.7.1 Beta
326 Icom IC-756 0.7.1 Alpha
327 Icom IC-756PRO 0.7 Untested
328 Icom IC-761 0.7.1 Stable
329 Icom IC-765 0.7 Stable
330 Icom IC-775 0.7.1 Untested
331 Icom IC-781 0.7.1 Untested
332 Icom IC-820H 0.7 Alpha
334 Icom IC-821H 0.7 Alpha
335 Icom IC-970 0.7 Untested
336 Icom IC-R10 0.7 Untested
337 Icom IC-R71 0.7 Untested
338 Icom IC-R72 0.7 Untested
339 Icom IC-R75 0.7 Beta
340 Icom IC-R7000 0.7.0 Alpha
341 Icom IC-R7100 0.7.0 Untested
342 Icom ICR-8500 0.7.1 Beta
343 Icom IC-R9000 0.7.1 Alpha
344 Icom IC-910 0.7.1 Beta
345 Icom IC-78 0.7 Untested
346 Icom IC-746PRO 0.7 Stable
347 Icom IC-756PROII 0.7 Alpha
351 Ten-Tec Omni VI Plus 0.2 Beta
352 Optoelectronics OptoScan535 0.3 Beta
353 Optoelectronics OptoScan456 0.3 Beta
354 Icom IC ID-1 0.7 Untested
355 Icom IC-703 0.7 Untested
356 Icom IC-7800 0.7.2 Untested
357 Icom IC-756PROIII 0.7.1 Beta
358 Icom IC-R20 0.7 Untested
360 Icom IC-7000 0.7.2 Beta
361 Icom IC-7200 0.7 Beta
362 Icom IC-7700 0.7.1 Stable
363 Icom IC-7600 0.7 Beta
364 Ten-Tec Delta II 0.1 Untested
365 Icom IC-92D 0.7 Untested
366 Icom IC-R9500 0.7.1 Untested
367 Icom IC-7410 0.7 Untested
368 Icom IC-9100 0.7 Untested
369 Icom IC-RX7 0.7 Untested
401 Icom IC-PCR1000 0.8 Beta
402 Icom IC-PCR100 0.8 Beta
403 Icom IC-PCR1500 0.8 Beta
404 Icom IC-PCR2500 0.8 Beta
501 AOR AR8200 0.6.1 Alpha
502 AOR AR8000 0.6.1 Beta
503 AOR AR7030 0.4.1 Beta
504 AOR AR5000 0.6.1 Beta
505 AOR AR3030 0.4 Untested
506 AOR AR3000A 0.5 Beta
508 AOR AR2700 0.6 Untested
513 AOR AR8600 0.6.1 Beta
514 AOR AR5000A 0.6 Alpha
515 AOR AR7030 Plus 0.1 Beta
516 AOR SR2200 0.1 Beta
605 JRC NRD-525 0.1 Alpha
606 JRC NRD-535D 0.6 Stable
607 JRC NRD-545 DSP 0.6 Beta
801 Uniden BC780xlt 0.3 Untested
802 Uniden BC245xlt 0.3 Untested
803 Uniden BC895xlt 0.3 Untested
804 Radio Shack PRO-2052 0.3 Untested
806 Uniden BC250D 0.3 Untested
810 Uniden BCD-396T 0.3 Alpha
811 Uniden BCD-996T 0.3 Alpha
812 Uniden BC898T 0.3 Untested
902 Drake R-8A 0.5.1 Beta
903 Drake R-8B 0.5 Untested
1004 Lowe HF-235 0.3 Alpha
1103 Racal RA6790/GM 0.1 Untested
1105 Racal RA3702 0.1 Alpha
1204 Watkins-Johnson WJ-8888 0.2 Untested
1402 Skanti TRP8000 0.2 Untested
1404 Skanti TRP 8255 S R 0.1 Untested
1501 Winradio WR-1000 0.6 Untested
1502 Winradio WR-1500 0.6 Untested
1503 Winradio WR-1550 0.6 Untested
1504 Winradio WR-3100 0.6 Untested
1505 Winradio WR-3150 0.6 Untested
1506 Winradio WR-3500 0.6 Untested
1507 Winradio WR-3700 0.6 Untested
1601 Ten-Tec TT-550 0.2 Beta
1602 Ten-Tec TT-538 Jupiter 0.6 Beta
1603 Ten-Tec RX-320 0.6 Stable
1604 Ten-Tec RX-340 0.3 Untested
1605 Ten-Tec RX-350 0.1 Untested
1607 Ten-Tec TT-516 Argonaut V 0.2 Stable
1608 Ten-Tec TT-565 Orion 0.5 Beta
1609 Ten-Tec TT-585 Paragon 0.3 Beta
1611 Ten-Tec TT-588 Omni VII 0.3 Alpha
1612 Ten-Tec RX-331 0.1 Beta
1613 Ten-Tec TT-599 Eagle 0.4 Untested
1701 Alinco DX-77 0.7 Beta
1801 Kachina 505DSP 0.3 Alpha
1901 Hamlib RPC rig 0.3 Beta
2201 TAPR DSP-10 0.2 Alpha
2301 Flex-radio SDR-1000 0.2 Untested
2303 DTTS Microwave Society DttSP IPC 0.2 Alpha
2304 DTTS Microwave Society DttSP UDP 0.2 Alpha
2401 RFT EKD-500 0.4 Alpha
2501 Elektor Elektor 3/04 0.4 Stable
2502 SAT-Schneider DRT1 0.2 Beta
2503 Coding Technologies Digital World Traveller 0.1 Untested
2506 AmQRP DDS-60 0.1 Alpha
2507 Elektor Elektor SDR-USB 0.3.1 Stable
2508 mRS miniVNA 0.1 Alpha
2509 SoftRock Si570 AVR-USB 0.2 Beta
2511 KTH-SDR kit Si570 PIC-USB 0.2 Beta
2512 FiFi FiFi-SDR 0.5 Beta
2513 AMSAT-UK FUNcube Dongle 0.2 Beta
2514 N2ADR HiQSDR 0.2 Untested
2601 Video4Linux SW/FM radio 0.2.1 Beta
2602 Video4Linux2 SW/FM radio 0.2.1 Alpha
2701 Rohde&Schwarz ESMC 0.1 Alpha
2702 Rohde&Schwarz EB200 0.1 Untested
2801 Philips/Simoco PRM8060 0.1 Alpha
2901 ADAT www.adat.ch ADT-200A 1.36 Beta
------------------------------------------------------------------
</pre>
There's no standardized protocol to remotely control one's rig, be it a Ham radio
transceiver, a SWL receiver, any kind of scanner or other mobile.
Many manufacturers have designed their own proprietary protocol, implemented in
some of their product family. Therefore, each rig family will require a Hamlib
backend to set the VFO frequency, change mode and passband width, get current
signal strength, etc.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2"><tbody><tr>
<td valign="top"><img src="img/note.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(234, 234, 234);">
<strong><font color="blue">Note:</font></strong> If your radio is not on the list,
it does not mean that it is not supported at all. The Elecraft K3 radio works as K2
(Rig# 221), you could also try one of the Kenwood radios. The Ten-Tec Omni-VI uses the
Icom IC-735 backend.</td></tr></tbody></table><br>
New backends for Yaesu FTDX-9000, FT-2000, FT-950 and FT-450 are expected very soon.
You can try the Kenwood radio instead or FT-1000MP.
<br>
There's no standardized protocol to remotely control one's rig, be it a Ham radio
transceiver, a SWL receiver, any kind of scanner or other mobile.
Many manufacturers have designed their own proprietary protocol, implemented in
some of their product family. Therefore, each rig family will require a Hamlib
backend to set the VFO frequency, change mode and passband width, get current
signal strength, etc.<br><br>
<table width="100%" border="0" cellpadding="5" cellspacing="2">
<tbody>
<tr>
<td valign="top"><img src="img/note.png"></td>
<td style="width: 100%; text-align: justify; background-color: rgb(234, 234, 234);">
<strong><font color="blue">Note:</font></strong> If your radio is not on the list,
it does not mean that it is not supported at all. The Elecraft K3 radio works as K2
(Rig# 221), you could also try one of the Kenwood radios. The Ten-Tec Omni-VI uses the
Icom IC-735 backend.
</td>
</tr>
</tbody>
</table>
<br>
</div>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h5.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h7.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h5.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="h7.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>
</body>
</html>

214
help/h7.html
View File

@ -1,118 +1,144 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en-us"><head>
<title>CQRLOG - LoTW support</title></head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td align="justify" bgcolor="#ffffcc" valign="top"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
/td></tr></tbody></table>
<html lang="en-us">
<head>
<title>CQRLOG - LoTW support</title></head>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td align="justify" bgcolor="#ffffcc" valign="top"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
/td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h6.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h8.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h6.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h8.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div align=left><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align="center"><img src="img/line.png"></p><a name="bh4"></a><br><b><h2>LoTW support</h2></b>
<p><strong>Preparation</strong></p>
<div align=justify>We assume that you have a working LoTW Account. If you are new to LoTW,
carefully read the instructions provided by the ARRL and set up your account.<br><br>
Most important is the certificate. ARRL issues certificates (.tq8) which are bound to
a particular machine and cannot be transferred to another place. If you receive a
.tq8 certificate, it is <b>absolutely essential to convert it to more usual .p12</b>
format which <strong>can</strong> be transferred. Do this immediately!<br><br>
Download and install the latest LoTW utilities (<em>tqsl</em> and <em>tqslcert</em>).
<p><strong>Setup</strong></p>
<img src="img/h76.png"><br><br>
<div align=justify>If you didn't do it already in the 'Preferences' setup procedure,
provide your user name for LoTW and the password (this is <strong>not</strong> the
password sent to US amateurs via postcard!).<br><br>
Now you need to select a certificate corresponding to the QTH you used while making
the QSOs you want to confirm. Check the certificates available by opening tqslcert
which displays all certificates.</div><br>
<img src="img/h78.png"><br><br>
<div align=justify>Now select the proper certificate <strong><em>in tqsl</em></strong>.
If you only have a single certificate, you don't need to make any selection, however note
the name of the QTH which must be entered into CQRLOG.</div><br>
<img src="img/h79.png"><br><br>
<img src="img/h80.png"><br><br>
<div align=justify>The QTH profile name here is 'Praha'. The callsign is added by default
however only the name (here 'Praha') should be entered into <em>tqsl command line
arguments:</em> column of the <em>QSL->LoTW->Export->Upload to LoTW</em> window.</div><br>
<img src="img/h81.png"><br><br>
<div align=justify>Once entered, the QTH name stays in the predefined command line.</div>
<p><strong>LoTW file export and upload</strong></p>
<div align=justify><strong>1. Select the QSO records</strong> you want to confirm.
carefully read the instructions provided by the ARRL and set up your account.<br><br>
Most important is the certificate. ARRL issues certificates (.tq8) which are bound to
a particular machine and cannot be transferred to another place. If you receive a
.tq8 certificate, it is <b>absolutely essential to convert it to more usual .p12</b>
format which <strong>can</strong> be transferred. Do this immediately!<br><br>
Download and install the latest LoTW utilities (<em>tqsl</em> and <em>tqslcert</em>).
<p><strong>Setup</strong></p>
<img src="img/h76.png"><br><br>
<div align=justify>If you didn't do it already in the 'Preferences' setup procedure,
provide your user name for LoTW and the password (this is <strong>not</strong> the
password sent to US amateurs via postcard!).<br><br>
Now you need to select a certificate corresponding to the QTH you used while making
the QSOs you want to confirm. Check the certificates available by opening tqslcert
which displays all certificates.
</div>
<br>
<img src="img/h78.png"><br><br>
<div align=justify>Now select the proper certificate <strong><em>in tqsl</em></strong>.
If you only have a single certificate, you don't need to make any selection, however note
the name of the QTH which must be entered into CQRLOG.
</div>
<br>
<img src="img/h79.png"><br><br>
<img src="img/h80.png"><br><br>
<div align=justify>The QTH profile name here is 'Praha'. The callsign is added by default
however only the name (here 'Praha') should be entered into <em>tqsl command line
arguments:</em> column of the <em>QSL->LoTW->Export->Upload to LoTW</em> window.
</div>
<br>
<img src="img/h81.png"><br><br>
<div align=justify>Once entered, the QTH name stays in the predefined command line.</div>
<p><strong>LoTW file export and upload</strong></p>
<div align=justify><strong>1. Select the QSO records</strong> you want to confirm.
A suitable choice is a filter for date, QSL received etc.<br><br>
Now, there are two possibilities:
<blockquote>
<strong>I. Export the selected records</strong> to a local ADIF file. This is useful
if you don't want (or it is impossible) to upload your log to LoTW.
Go to <em>QSL->LoTW->Export->Export QSOs to LoTW adif file</em><br><br>
<img src="img/h82.png"><br><br>
<div align=justify>Provide a file name in the <em>Export to:</em> field.</div><br>
<img src="img/h83.png"><br><br>
<div align=justify>If you want to mark the exported QSO records, do it now. Click
the <em>Export</em> button and go to <em>Upload to LoTW menu</em> item. The ADIF file
can be signed and uploaded later.<br><br>The other option is export, signing and upload
your log to LoTW in a single step.<br><br>
<strong>II. export, signing and upload your log to LoTW from CQRLOG</strong><br><br>
Go to Upload to LoTW dialog and choose the QSO records which should be exported:</div><br>
<img src="img/h84.png"><br><br>
<div align=justify>Click the <em>Export & sign</em> button. You should see:<br>
A suitable choice is a filter for date, QSL received etc.<br><br>
Now, there are two possibilities:
<blockquote>
<strong>I. Export the selected records</strong> to a local ADIF file. This is useful
if you don't want (or it is impossible) to upload your log to LoTW.
Go to <em>QSL->LoTW->Export->Export QSOs to LoTW adif file</em><br><br>
<img src="img/h82.png"><br><br>
<div align=justify>Provide a file name in the <em>Export to:</em> field.</div>
<br>
<img src="img/h83.png"><br><br>
<div align=justify>If you want to mark the exported QSO records, do it now. Click
the <em>Export</em> button and go to <em>Upload to LoTW menu</em> item. The ADIF file
can be signed and uploaded later.<br><br>The other option is export, signing and upload
your log to LoTW in a single step.<br><br>
<strong>II. export, signing and upload your log to LoTW from CQRLOG</strong><br><br>
Go to Upload to LoTW dialog and choose the QSO records which should be exported:
</div>
<br>
<img src="img/h84.png"><br><br>
<div align=justify>Click the <em>Export & sign</em> button. You should see:<br>
<pre>Signing adif file ...
Signed ...
If you did not see any errors, you can send signed file to LoTW
website by pressing the Upload button</pre><br>
Now click the <em>Upload</em> button. A message<br>
website by pressing the Upload button</pre>
<br>
Now click the <em>Upload</em> button. A message<br>
<pre>Uploading file ...
Size: xxxxx
Uploading was succesful<br></pre>
</blockquote>
This procedure can be checked in the following way: in the /cqrlog/lotw folder there should
appear two new files - an ADIF file named date_time.adi (where date and time corresponding
to the date and time of creation) and the signed file with the same file name but .tq8
extension which is then uploaded to the LoTW site. Finally, you can check the
<a href=https://p1k.arrl.org/lotwuser/default><strong>LoTW site</strong></a>.
Log in and go to <em>Your Account -> Your Activity</em> and you should see your last
upload with the date, time and file name.
<br><br></div>
<p><strong>LoTW files download and processing</strong></p>
<div align=justify>The main purpose of the LoTW file processing (also download) is to
mark existing QSO records as confirmed via LoTW. Files can be downloaded directly
into CQRLOG or an already downloaded ADIF files can be processed.</div><br>
<img src="img/h85.png"><br><br>
<div align=justify>Both options are shown here. If the <em>Import local LoTW ADIF
file</em> (already downloaded from the LoTW site) is processed, a simple progress
indicator is shown.</div><br>
<img src="img/h86.png"><br><br>
If you choose <em>Download and process data from LoTW website</em> a progress
indicator is displayed.</div><br><br>
</blockquote>
This procedure can be checked in the following way: in the /cqrlog/lotw folder there should
appear two new files - an ADIF file named date_time.adi (where date and time corresponding
to the date and time of creation) and the signed file with the same file name but .tq8
extension which is then uploaded to the LoTW site. Finally, you can check the
<a href=https://p1k.arrl.org/lotwuser/default><strong>LoTW site</strong></a>.
Log in and go to <em>Your Account -> Your Activity</em> and you should see your last
upload with the date, time and file name.
<br><br></div>
<p><strong>LoTW files download and processing</strong></p>
<div align=justify>The main purpose of the LoTW file processing (also download) is to
mark existing QSO records as confirmed via LoTW. Files can be downloaded directly
into CQRLOG or an already downloaded ADIF files can be processed.
</div>
<br>
<img src="img/h85.png"><br><br>
<div align=justify>Both options are shown here. If the <em>Import local LoTW ADIF
file</em> (already downloaded from the LoTW site) is processed, a simple progress
indicator is shown.
</div>
<br>
<img src="img/h86.png"><br><br>
If you choose <em>Download and process data from LoTW website</em> a progress
indicator is displayed.
</div>
<br><br>
<img src="img/h87.png"><br><br>
<div align=justify>The Size changes while downloading, if finished it indicates the
total file size. When the download finishes, a summary appears and the import begins,
showing the same progress indicator as above.</div><br>
total file size. When the download finishes, a summary appears and the import begins,
showing the same progress indicator as above.
</div>
<br>
<img src="img/h88.png"><br><br>
If the file is not accessible (due to server overload etc.), an error message is shown.
Also if the file contains a record which is not in your log, a warning message appears.
<p align="center"><img src="img/line.png"></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h6.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h8.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h6.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h8.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>
</body>
</html>

330
help/h8.html
View File

@ -1,83 +1,213 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head>
<title>CQRLOG - GNU GENERAL PUBLIC LICENSE</title>
<html>
<head>
<title>CQRLOG - GNU GENERAL PUBLIC LICENSE</title>
</head>
<body>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h7.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h7.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align=center><img src=img/line.png></p>
<div style="text-align: justify;">
<h3>GNU GENERAL PUBLIC LICENSE</h3>
<p> Version 2, June 1991 </p>
<pre>Copyright (C) 1989, 1991 Free Software Foundation, Inc. <br>51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA<br><br>Everyone is permitted to copy and distribute verbatim copies<br>of this license document, but changing it is not allowed.<br></pre>
<h3>Preamble</h3>
<p> The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. </p>
<p> When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. </p>
<p> To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. </p>
<p> For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. </p>
<p> We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. </p>
<p> Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. </p>
<p> Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. </p>
<p> The precise terms and conditions for copying, distribution and modification follow. </p>
<h3>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</h3>
<p> <strong>0.</strong> This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". </p>
<p> Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. </p>
<p> <strong>1.</strong> You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. </p>
<p> You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. </p>
<p> <strong>2.</strong> You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: </p>
<dl>
<dt></dt>
<dd> <strong>a)</strong> You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. </dd>
<dt></dt>
<dd> <strong>b)</strong> You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. </dd>
<dt></dt>
<dd> <strong>c)</strong> If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) </dd>
</dl>
<p> These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. </p>
<p> Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. </p>
<p> In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. </p>
<p> <strong>3.</strong> You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: </p>
<h3>GNU GENERAL PUBLIC LICENSE</h3>
<p> Version 2, June 1991 </p>
<pre>Copyright (C) 1989, 1991 Free Software Foundation, Inc. <br>51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA<br><br>Everyone is permitted to copy and distribute verbatim copies<br>of this license document, but changing it is not allowed.<br></pre>
<h3>Preamble</h3>
<p> The licenses for most software are designed to take away your freedom to share and change it. By contrast, the
GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure
the software is free for all its users. This General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to using it. (Some other Free Software
Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your
programs, too. </p>
<p> When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed
to make sure that you have the freedom to distribute copies of free software (and charge for this service if you
wish), that you receive source code or can get it if you want it, that you can change the software or use pieces
of it in new free programs; and that you know you can do these things. </p>
<p> To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you
to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute
copies of the software, or if you modify it. </p>
<p> For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the
recipients all the rights that you have. You must make sure that they, too, receive or can get the source code.
And you must show them these terms so they know their rights. </p>
<p> We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives
you legal permission to copy, distribute and/or modify the software. </p>
<p> Also, for each author's protection and ours, we want to make certain that everyone understands that there is no
warranty for this free software. If the software is modified by someone else and passed on, we want its
recipients to know that what they have is not the original, so that any problems introduced by others will not
reflect on the original authors' reputations. </p>
<p> Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that
redistributors of a free program will individually obtain patent licenses, in effect making the program
proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or
not licensed at all. </p>
<p> The precise terms and conditions for copying, distribution and modification follow. </p>
<h3>TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</h3>
<p><strong>0.</strong> This License applies to any program or other work which contains a notice placed by the
copyright holder saying it may be distributed under the terms of this General Public License. The "Program",
below, refers to any such program or work, and a "work based on the Program" means either the Program or any
derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either
verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included
without limitation in the term "modification".) Each licensee is addressed as "you". </p>
<p> Activities other than copying, distribution and modification are not covered by this License; they are outside
its scope. The act of running the Program is not restricted, and the output from the Program is covered only if
its contents constitute a work based on the Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does. </p>
<p><strong>1.</strong> You may copy and distribute verbatim copies of the Program's source code as you receive it,
in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright
notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of
any warranty; and give any other recipients of the Program a copy of this License along with the Program. </p>
<p> You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty
protection in exchange for a fee. </p>
<p><strong>2.</strong> You may modify your copy or copies of the Program or any portion of it, thus forming a work
based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above,
provided that you also meet all of these conditions: </p>
<dl>
<dt></dt>
<dd><strong>a)</strong> You must cause the modified files to carry prominent notices stating that you changed
the files and the date of any change.
</dd>
<dt></dt>
<dd><strong>b)</strong> You must cause any work that you distribute or publish, that in whole or in part
contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all
third parties under the terms of this License.
</dd>
<dt></dt>
<dd><strong>c)</strong> If the modified program normally reads commands interactively when run, you must cause
it, when started running for such interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a notice that there is no warranty (or else,
saying that you provide a warranty) and that users may redistribute the program under these conditions, and
telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on the Program is not required to print an
announcement.)
</dd>
</dl>
<p> These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived
from the Program, and can be reasonably considered independent and separate works in themselves, then this
License, and its terms, do not apply to those sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based on the Program, the distribution of the
whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole,
and thus to each and every part regardless of who wrote it. </p>
<p> Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by
you; rather, the intent is to exercise the right to control the distribution of derivative or collective works
based on the Program. </p>
<p> In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on
the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of
this License. </p>
<p><strong>3.</strong> You may copy and distribute the Program (or a work based on it, under Section 2) in object
code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the
following: </p>
<dl>
<dt></dt>
<dd> <strong>a)</strong> Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, </dd>
<dt></dt>
<dd> <strong>b)</strong> Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, </dd>
<dt></dt>
<dd> <strong>c)</strong> Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) </dd>
</dl>
<p> The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. </p>
<p> If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. </p>
<p> <strong>4.</strong> You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. </p>
<p> <strong>5.</strong> You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. </p>
<p> <strong>6.</strong> Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. </p>
<p> <strong>7.</strong> If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. </p>
<p> If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. </p>
<p> It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. </p>
<p> This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. </p>
<p> <strong>8.</strong> If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. </p>
<p> <strong>9.</strong> The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. </p>
<p> Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. </p>
<p> <strong>10.</strong> If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. </p>
<p><strong>NO WARRANTY</strong></p>
<p> <strong>11.</strong> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. </p>
<p> <strong>12.</strong> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. </p>
<dl>
<dt></dt>
<dd><strong>a)</strong> Accompany it with the complete corresponding machine-readable source code, which must be
distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange;
or,
</dd>
<dt></dt>
<dd><strong>b)</strong> Accompany it with a written offer, valid for at least three years, to give any third
party, for a charge no more than your cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and
2 above on a medium customarily used for software interchange; or,
</dd>
<dt></dt>
<dd><strong>c)</strong> Accompany it with the information you received as to the offer to distribute
corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such an offer, in accord with Subsection b
above.)
</dd>
</dl>
<p> The source code for a work means the preferred form of the work for making modifications to it. For an
executable work, complete source code means all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation and installation of the executable.
However, as a special exception, the source code distributed need not include anything that is normally
distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component itself accompanies the executable. </p>
<p> If distribution of executable or object code is made by offering access to copy from a designated place, then
offering equivalent access to copy the source code from the same place counts as distribution of the source
code, even though third parties are not compelled to copy the source along with the object code. </p>
<p><strong>4.</strong> You may not copy, modify, sublicense, or distribute the Program except as expressly provided
under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and
will automatically terminate your rights under this License. However, parties who have received copies, or
rights, from you under this License will not have their licenses terminated so long as such parties remain in
full compliance. </p>
<p><strong>5.</strong> You are not required to accept this License, since you have not signed it. However, nothing
else grants you permission to modify or distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any
work based on the Program), you indicate your acceptance of this License to do so, and all its terms and
conditions for copying, distributing or modifying the Program or works based on it. </p>
<p><strong>6.</strong> Each time you redistribute the Program (or any work based on the Program), the recipient
automatically receives a license from the original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the
rights granted herein. You are not responsible for enforcing compliance by third parties to this License. </p>
<p><strong>7.</strong> If, as a consequence of a court judgment or allegation of patent infringement or for any
other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this
License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any
other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a
patent license would not permit royalty-free redistribution of the Program by all those who receive copies
directly or indirectly through you, then the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program. </p>
<p> If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance
of the section is intended to apply and the section as a whole is intended to apply in other circumstances. </p>
<p> It is not the purpose of this section to induce you to infringe any patents or other property right claims or to
contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free
software distribution system, which is implemented by public license practices. Many people have made generous
contributions to the wide range of software distributed through that system in reliance on consistent
application of that system; it is up to the author/donor to decide if he or she is willing to distribute
software through any other system and a licensee cannot impose that choice. </p>
<p> This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this
License. </p>
<p><strong>8.</strong> If the distribution and/or use of the Program is restricted in certain countries either by
patents or by copyrighted interfaces, the original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding those countries, so that distribution is
permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation
as if written in the body of this License. </p>
<p><strong>9.</strong> The Free Software Foundation may publish revised and/or new versions of the General Public
License from time to time. Such new versions will be similar in spirit to the present version, but may differ in
detail to address new problems or concerns. </p>
<p> Each version is given a distinguishing version number. If the Program specifies a version number of this License
which applies to it and "any later version", you have the option of following the terms and conditions either of
that version or of any later version published by the Free Software Foundation. If the Program does not specify
a version number of this License, you may choose any version ever published by the Free Software
Foundation. </p>
<p><strong>10.</strong> If you wish to incorporate parts of the Program into other free programs whose distribution
conditions are different, write to the author to ask for permission. For software which is copyrighted by the
Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status of all derivatives of our free software
and of promoting the sharing and reuse of software generally. </p>
<p><strong>NO WARRANTY</strong></p>
<p><strong>11.</strong> BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE
EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER
PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK
AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE
COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. </p>
<p><strong>12.</strong> IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT
HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN
IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. </p>
<h3>END OF TERMS AND CONDITIONS</h3>
<h3>END OF TERMS AND CONDITIONS</h3>
<h3>How to Apply These Terms to Your New Programs</h3>
<p> If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. </p>
<p> To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. </p>
<table><tbody><tr><td style="background-color: rgb(238, 238, 238);">
<h3>How to Apply These Terms to Your New Programs</h3>
<p> If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to
achieve this is to make it free software which everyone can redistribute and change under these terms. </p>
<p> To do so, attach the following notices to the program. It is safest to attach them to the start of each source
file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright"
line and a pointer to where the full notice is found. </p>
<table>
<tbody>
<tr>
<td style="background-color: rgb(238, 238, 238);">
<pre><var>one line to give the program's name and an idea of what it does.</var>
Copyright (C) <var>yyyy</var> <var>name of author</var>
@ -94,32 +224,60 @@ GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
</pre></td></tr></tbody></table>
<p>Also add information on how to contact you by electronic and paper mail.</p>
<p>If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:</p>
<table><tbody><tr><td style="background-color: rgb(238, 238, 238);">
</pre>
</td>
</tr>
</tbody>
</table>
<p>Also add information on how to contact you by electronic and paper mail.</p>
<p>If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:</p>
<table>
<tbody>
<tr>
<td style="background-color: rgb(238, 238, 238);">
<pre>Gnomovision version 69, Copyright (C) <var>year</var> <var>name of author</var>
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
type `show w'. This is free software, and you are welcome
to redistribute it under certain conditions; type `show c'
for details.</pre></td></tr></tbody></table>
<p> The hypothetical commands <samp>`show w'</samp> and <samp>`show c'</samp> should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than <samp>`show w'</samp> and <samp>`show c'</samp>; they could even be mouse-clicks or menu items--whatever suits your program. </p>
<p> You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: </p>
<table><tbody><tr><td style="background-color: rgb(238, 238, 238);"> <pre>Yoyodyne, Inc., hereby disclaims all copyright<br>interest in the program `Gnomovision'<br>(which makes passes at compilers) written <br>by James Hacker.<br><br><var>signature of Ty Coon</var>, 1 April 1989<br>Ty Coon, President of Vice<br></pre> </td></tr></tbody></table>
<p> This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the </strong>GNU Lesser General Public License</strong> instead of this License. </p>
for details.</pre>
</td>
</tr>
</tbody>
</table>
<p> The hypothetical commands <samp>`show w'</samp> and <samp>`show c'</samp> should show the appropriate parts of
the General Public License. Of course, the commands you use may be called something other than <samp>`show
w'</samp> and <samp>`show c'</samp>; they could even be mouse-clicks or menu items--whatever suits your
program. </p>
<p> You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright
disclaimer" for the program, if necessary. Here is a sample; alter the names: </p>
<table>
<tbody>
<tr>
<td style="background-color: rgb(238, 238, 238);">
<pre>Yoyodyne, Inc., hereby disclaims all copyright<br>interest in the program `Gnomovision'<br>(which makes passes at compilers) written <br>by James Hacker.<br><br><var>signature
of Ty Coon</var>, 1 April 1989<br>Ty Coon, President of Vice<br></pre>
</td>
</tr>
</tbody>
</table>
<p> This General Public License does not permit incorporating your program into proprietary programs. If your
program is a subroutine library, you may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the </strong>GNU Lesser General Public License</strong> instead
of this License. </p>
</div>
<br>
<p align=center><img src=img/line.png></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h7.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td width="33%" align="left">&nbsp;&lt;<a href="h7.html"> Prev</a></td>
<td width="33%" align="center">[<a href="index.html#aa">Menu</a>]</td>
<td width="33%" align="right"><a href="index.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body></html>
</body>
</html>

BIN
help/img/h10.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 26 KiB

After

Width:  |  Height:  |  Size: 40 KiB

BIN
help/img/h49.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 13 KiB

After

Width:  |  Height:  |  Size: 26 KiB

359
help/index.html
View File

@ -1,205 +1,226 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en-us"><head>
<title>CQRLOG - Help Index</title></head>
<html lang="en-us">
<head>
<title>CQRLOG - Help Index</title></head>
<body>
<strong><h1>CQRLOG for LINUX (version 1.9.1)</h1></strong>
<strong><h1>CQRLOG for LINUX (version 2.0.0)</h1></strong>
by<br><br>
<i>Petr Hlozek, OK2CQR
[http://www.ok2cqr.com]</i>
[<a href="http://www.ok2cqr.com">http://www.ok2cqr.com</a>]</i>
<br>
and
<br>
<i>Martin Kratoska, OK1RR
[http://www.ok1rr.com]</i>
[<a href="http://www.ok1rr.com">http://www.ok1rr.com</a>]</i>
<br><br>
<strong><h3>Description:</h3></strong>
<div align="justify"><div>CQRLOG is an advanced ham radio logging application based
on a MySQL database. It provides radio interfacing utilizing the hamlib libraries
(currently support for 140+ radio types and models), DX cluster
connection, band map, QRZ.com/HamQTH.com callbook (XML access),
ClubLog and Logbook of the World support, IOTA support, a
grayliner, propagation indicator, xplanet support (maps in azimuthal projection centered in
your QTH), OK1RR free QSL manager database etc.
<br> <br>CQRLOG is intended mainly for seriously HF DX minded operators
but can be used for any ham logging purpose, also by casual operators.
It is equipped with probably most accurate DXCC country database
available, providing not only the country resolution but also state,
province, region, district etc. It resolves also antarctic bases,
special event stations, contest callsigns and much more.<br><br>
CQRLOG has its own web site at
<a href=http://www.cqrlog.com><strong>http://www.cqrlog.com</strong></a>.
Find news, changes, latest additional files and howtos there.
If you have a problem, browse the web site first, then ask for help.</div>
<br><br> <strong><h3>License and disclaimer:</h3></strong>CQRLOG is
published under the GNU GENERAL PUBLIC LICENSE Version 2 (GPL v. 2), June
1991. This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version. Full version of GPL v.
2 is <a href="h8.html"><strong>here</strong></a>.
<br><br>The authors are not responsible for any damages, losses or safety risks to the user; the software is published AS IS.
<br><br><strong><h3>Supported transceivers:</h3>
<div align="justify">
<div>CQRLOG is an advanced ham radio logging application based
on a MySQL database. It provides radio interfacing utilizing the hamlib libraries
(currently support for 140+ radio types and models), DX cluster
connection, band map, QRZ.com/HamQTH.com callbook (XML access),
ClubLog and Logbook of the World support, IOTA support, a
grayliner, propagation indicator, xplanet support (maps in azimuthal projection centered in
your QTH), OK1RR free QSL manager database etc.
<br> <br>CQRLOG is intended mainly for seriously HF DX minded operators
but can be used for any ham logging purpose, also by casual operators.
It is equipped with probably most accurate DXCC country database
available, providing not only the country resolution but also state,
province, region, district etc. It resolves also antarctic bases,
special event stations, contest callsigns and much more.<br><br>
CQRLOG has its own web site at
<a href=http://www.cqrlog.com><strong>http://www.cqrlog.com</strong></a>.
Find news, changes, latest additional files and howtos there.
If you have a problem, browse the web site first, then ask for help.
</div>
<br><br> <strong><h3>License and disclaimer:</h3></strong>CQRLOG is
published under the GNU GENERAL PUBLIC LICENSE Version 2 (GPL v. 2), June
1991. This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version. Full version of GPL v.
2 is <a href="h8.html"><strong>here</strong></a>.
<br><br>The authors are not responsible for any damages, losses or safety risks to the user; the software is
published AS IS.
<br><br><strong><h3>Supported transceivers:</h3>
</strong> The Radio Control interface is provided using <i>hamlib</i>,
a set of libraries, which is a development effort to provide a
consistent interface for programmers wanting to incorporate radio
control in their programs. <i>hamlib</i> is not a complete user
application, rather, it is a software layer intended to make
controlling various radios and other shack hardware much easier.
<br><br> Most recent amateur radio transceivers allow external control
of their functions through a serial interface. Unfortunately, control
commands are not always consistent across a manufacturer's product line
and each manufacturer's product line differs greatly from its
competitors.
<br><br> There's no standardized protocol to remotely control one's
rig, be it a Ham radio transceiver, a SWL receiver, any kind of scanner
or other mobiles. However, many manufacturer have designed their
own proprietary protocol, implemented in some of their product family.
Therefore, each rig family will require a <i>hamlib</i> backend to set
the VFO frequency, change mode and passband width, get current signal
strength, etc. The actual list of supported radios can be found <a href="h6.html"><strong>here</strong></a>.
<br><br> <strong><h3>Installation:</h3></strong>
Ubuntu users can use a repository on Launchpad. To add the repo, open a terminal and copy&amp;paste<br><br>
<code>
sudo add-apt-repository ppa:ok2cqr/ppa<br>
sudo apt-get update<br>
sudo apt-get install cqrlog <br>
</code><br>
Only Ubuntu 14.04 LTS is officially supported but there are also builds for newer
versions of Ubuntu.
<br><br>
Debian users can simply install using the package manager<br><br>
<code>
sudo apt-get install cqrlog <br>
</code><br><br>
For other distributions, you can use binaries located at
<a href="http://cqrlog.com/download">http://cqrlog.com/download</a>.
Some of them, like Fedora and Arch, have their own repositories for CQRLOG - Fedora: <a href="https://admin.fedoraproject.org/pkgdb/acls/name/cqrlog">https://admin.fedoraproject.org/pkgdb/acls/name/cqrlog</a> ArchLinux <a href="https://aur.archlinux.org/packages/cqrlog/">https://aur.archlinux.org/packages/cqrlog/</a><br>
If upgrading, no important file will be overwritten. Anyway, <strong>backup your log</strong> before you begin any upgrade!
<br><br><strong><h3>Dependencies:</h3></strong>
<ul>
<li><strong>HamLib</strong> - must be installed even if you don't want radio control. The sources are available at <a href="http://hamlib.sourceforge.net/"><strong>http://hamlib.sourceforge.net/</strong></a>, however precompiled packages are available for almost all major Linux distributions.</li>
<li><strong>MySQL server and client</strong> - The MySQL client must be installed,
without this the program will not work at all. A MySQL server must be reachable,
either on the local machine or via a network.</li>
<li><strong>libssl-devel</strong> needed if you want to use LoTW and/or online log upload
</ul>
a set of libraries, which is a development effort to provide a
consistent interface for programmers wanting to incorporate radio
control in their programs. <i>hamlib</i> is not a complete user
application, rather, it is a software layer intended to make
controlling various radios and other shack hardware much easier.
<br><br> Most recent amateur radio transceivers allow external control
of their functions through a serial interface. Unfortunately, control
commands are not always consistent across a manufacturer's product line
and each manufacturer's product line differs greatly from its
competitors.
<br><br> There's no standardized protocol to remotely control one's
rig, be it a Ham radio transceiver, a SWL receiver, any kind of scanner
or other mobiles. However, many manufacturer have designed their
own proprietary protocol, implemented in some of their product family.
Therefore, each rig family will require a <i>hamlib</i> backend to set
the VFO frequency, change mode and passband width, get current signal
strength, etc. The actual list of supported radios can be found <a href="https://sourceforge.net/p/hamlib/wiki/Supported%20Radios/"><strong>on Hamlib website</strong></a>.
<br><br> <strong><h3>Installation:</h3></strong>
Ubuntu users can use a repository on <a href="https://launchpad.net/~ok2cqr/+archive/ubuntu/ppa">Launchpad</a>. To add the repo, open a terminal and copy&amp;paste<br><br>
<code>
sudo add-apt-repository ppa:ok2cqr/ppa<br>
sudo apt-get update<br>
sudo apt-get install cqrlog <br>
</code><br>
Only Ubuntu 14.04 and Ubuntu 16.04 are officially supported but there are also builds for other
versions of Ubuntu on <a href="https://launchpad.net/~ok2cqr/+archive/ubuntu/ppa">Launchpad</a>.
<br><br>
Debian users can simply install using the package manager<br><br>
<code>
sudo apt-get install cqrlog <br>
</code><br><br>
For other distributions, you can use binaries located at
<a href="http://cqrlog.com/download">http://cqrlog.com/download</a>.
Some of them, like Fedora and Arch, have their own repositories for CQRLOG - Fedora: <a
href="https://apps.fedoraproject.org/packages/cqrlog">https://apps.fedoraproject.org/packages/cqrlog</a>
ArchLinux <a href="https://aur.archlinux.org/packages/cqrlog/">https://aur.archlinux.org/packages/cqrlog/</a><br>
If upgrading, no important file will be overwritten. Anyway, <strong>backup your log</strong> before you begin any
upgrade!
<br><br><strong><h3>Dependencies:</h3></strong>
<ul>
<li><strong>HamLib</strong> - must be installed even if you don't want radio control. The sources are available
at <a href="http://hamlib.sourceforge.net/"><strong>http://hamlib.sourceforge.net/</strong></a>, however
precompiled packages are available for almost all major Linux distributions.
</li>
<li><strong>MySQL server and client</strong> - The MySQL client must be installed,
without this the program will not work at all. A MySQL server must be reachable,
either on the local machine or via a network.
</li>
<li><strong>libssl-devel</strong> needed if you want to use LoTW and/or online log upload
</ul>
</div>
<a name="aa"><strong></strong></a><h2><a name="aa"><strong>Contents:</strong></a></h2><h3><strong>Quick start</strong></h3>
<a name="aa"><strong></strong></a>
<h2><a name="aa"><strong>Contents:</strong></a></h2>
<h3><strong>Quick start</strong></h3>
<ul style="margin-left: 40px;">
<li><a href="h1.html">Preferences</a></li>
<ul>
<li><a href="h1.html#ah2">Program</a></li>
<li><a href="h1.html#ah3">Station</a></li>
<li><a href="h1.html#ah4">New QSO</a></li>
<li><a href="h1.html#ah5">Visible columns</a></li>
<li><a href="h1.html#ah6">Bands</a></li>
<li><a href="h1.html#ah7">TRX Control</a></li>
<li><a href="h1.html#ah8">Modes</a></li>
<li><a href="h1.html#ah9">QTH Profiles</a></li>
<li><a href="h1.html#ah10">Export</a></li>
<li><a href="h1.html#ah11">DX Cluster</a></li>
<li><a href="h1.html#ah12">Fonts</a></li>
<li><a href="h1.html#ah13">WAZ, ITU Zones</a></li>
<li><a href="h1.html#ah14">IOTA</a></li>
<li><a href="h1.html#ah15">Membership</a></li>
<li><a href="h1.html#bh1">Bandmap</a></li>
<li><a href="h1.html#bh2">xplanet support</a></li>
<li><a href="h1.html#bh3">Zip code tracking</a></li>
<li><a href="h1.html#bh4">LoTW support</a></li>
<li><a href="h1.html#ch1">CW interface</a></li>
<li><a href="h1.html#ch2">fldigi interface</a></li>
<li><a href="h1.html#ch3">Auto backup</a></li>
<li><a href="h1.html#ch4">External viewers</a></li>
<li><a href="h1.html#ch5">Callbook support</a></li>
<li><a href="h1.html#ch6">RBN support</a></li>
<li><a href="h1.html#ch7">Online log upload support</a></li>
</ul>
<li><a href="h1.html">Preferences</a></li>
<ul>
<li><a href="h1.html#ah2">Program</a></li>
<li><a href="h1.html#ah3">Station</a></li>
<li><a href="h1.html#ah4">New QSO</a></li>
<li><a href="h1.html#ah5">Visible columns</a></li>
<li><a href="h1.html#ah6">Bands</a></li>
<li><a href="h1.html#ah7">TRX Control</a></li>
<li><a href="h1.html#ah8">Modes</a></li>
<li><a href="h1.html#ah9">QTH Profiles</a></li>
<li><a href="h1.html#ah10">Export</a></li>
<li><a href="h1.html#ah11">DX Cluster</a></li>
<li><a href="h1.html#ah12">Fonts</a></li>
<li><a href="h1.html#ah13">WAZ, ITU Zones</a></li>
<li><a href="h1.html#ah14">IOTA</a></li>
<li><a href="h1.html#ah15">Membership</a></li>
<li><a href="h1.html#bh1">Bandmap</a></li>
<li><a href="h1.html#bh2">xplanet support</a></li>
<li><a href="h1.html#bh3">Zip code tracking</a></li>
<li><a href="h1.html#bh4">LoTW support</a></li>
<li><a href="h1.html#ch1">CW interface</a></li>
<li><a href="h1.html#ch2">fldigi interface</a></li>
<li><a href="h1.html#ch3">Auto backup</a></li>
<li><a href="h1.html#ch4">External viewers</a></li>
<li><a href="h1.html#ch5">Callbook support</a></li>
<li><a href="h1.html#ch6">RBN support</a></li>
<li><a href="h1.html#ch7">Online log upload support</a></li>
</ul>
</ul>
<strong><h3>Operation</h3></strong>
<ul>
<li><a href="h20.html#ah16">Keys and Shortcuts</a></li>
<li><a href="h20.html#ah17">New QSO</a> (online logging)</li>
<li><a href="h20.html#ah18">New QSO</a> (offline logging, ie. from paper log etc.)</li>
<li><a href="h20.html#ah33">Digital modes</a> (<em>fldigi</em> interface)</li>
<li><a href="h25.html">QSO record edit</a></li>
<li><a href="h25.html#grp">Group edit</a></li>
<li><a href="h21.html#ah19">DX Cluster Operation</a></li>
<li><a href="h21.html#bh19">Bandmap Operation</a></li>
<li><a href="h26.html#">CW Operation</a></li>
<li><a href="h21.html#ch19">xplanet support</a></li>
<li><a href="h21.html#ch20">Propagation indicator</a></li>
<li><a href="h23.html#ah22">Filtering</a></li>
<li><a href="h22.html#ah21">QSL records</a></li>
<li><a href="h22.html#bh4">QSL labels printing</a></li>
<li><a href="h22.html#bh5">Auto mark QSL</a></li>
<li><a href="h7.html">LoTW</a></li>
<li><a href="h21.html#ch21">Additional notes to a callsign</a></li>
<li><a href="h24.html#ah23">Statistics</a></li>
<li><a href="h20.html#ah16">Keys and Shortcuts</a></li>
<li><a href="h20.html#ah17">New QSO</a> (online logging)</li>
<li><a href="h20.html#ah18">New QSO</a> (offline logging, ie. from paper log etc.)</li>
<li><a href="h20.html#ah33">Digital modes</a> (<em>fldigi</em> interface)</li>
<li><a href="h25.html">QSO record edit</a></li>
<li><a href="h25.html#grp">Group edit</a></li>
<li><a href="h21.html#ah19">DX Cluster Operation</a></li>
<li><a href="h21.html#bh19">Bandmap Operation</a></li>
<li><a href="h26.html#">CW Operation</a></li>
<li><a href="h21.html#ch19">xplanet support</a></li>
<li><a href="h21.html#ch20">Propagation indicator</a></li>
<li><a href="h23.html#ah22">Filtering</a></li>
<li><a href="h22.html#ah21">QSL records</a></li>
<li><a href="h22.html#bh4">QSL labels printing</a></li>
<li><a href="h22.html#bh5">Auto mark QSL</a></li>
<li><a href="h7.html">LoTW</a></li>
<li><a href="h21.html#ch21">Additional notes to a callsign</a></li>
<li><a href="h24.html#ah23">Statistics</a></li>
</ul>
<strong><h3>Advanced operations</h3></strong>
<ul>
<li><a href="h27.html">SQL console</a></li>
<li><a href="h27.html">SQL console</a></li>
</ul>
<strong><h3>Maintenance</h3></strong>
<ul>
<li><a href="h3.html#ah24">ADIF import</a></li>
<li><a href="h3.html#ah25">ADIF export</a></li>
<li><a href="h3.html#ah26">HTML export</a></li>
<li><a href="h3.html#ah27">Program version update</a></li>
<li><a href="h3.html#ah28">Country files update</a></li>
<li><a href="h3.html#ah29">QSL Manager Database update</a></li>
<li><a href="h3.html#ah30">Statistics Rebuilding</a></li>
<li><a href="h7.html#cfm">LoTW confirmation report update</a></li>
<li><a href="h3.html#ah31">Membership databases</a></li>
<li><a href="h3.html#ah32">Log backup</a></li>
<li><a href="h3.html#ah24">ADIF import</a></li>
<li><a href="h3.html#ah25">ADIF export</a></li>
<li><a href="h3.html#ah26">HTML export</a></li>
<li><a href="h3.html#ah27">Program version update</a></li>
<li><a href="h3.html#ah28">Country files update</a></li>
<li><a href="h3.html#ah29">QSL Manager Database update</a></li>
<li><a href="h3.html#ah30">Statistics Rebuilding</a></li>
<li><a href="h7.html#cfm">LoTW confirmation report update</a></li>
<li><a href="h3.html#ah31">Membership databases</a></li>
<li><a href="h3.html#ah32">Log backup</a></li>
</ul>
<strong><h3>Miscellaneous</h3></strong>
<ul>
<li><a href="h6.html">Supported radio types</a></li>
<li><a href="h6.html#param">Comm parameters of some popular radios</a></li>
<li><a href="h8.html">GNU GENERAL PUBLIC LICENSE</a></li>
<li><a href="h6.html">Supported radio types</a></li>
<li><a href="h6.html#param">Comm parameters of some popular radios</a></li>
<li><a href="h8.html">GNU GENERAL PUBLIC LICENSE</a></li>
</ul>
<strong><h3>Third Party Programs</h3></strong>
<ul><li><strong>Hamlib</strong> - <strong><font color="#FF0000">NEEDED</font></strong>,
without this CQRLOG will not work!</li>
<li><strong>Trusted QSL</strong> - for LoTW operations. You need the updated version, download
<a href="http://www.ok2cqr.com/?q=lotw-and-linux"><strong>here</strong></a>
(sources, SuSE and Fedora packages).
Ubuntu and Debian have this package in their repositories.
Slackware packages download <a href="http://www.ok1rr.com/request.php?196"><strong>here</strong></a>.</li>
<li><strong>xplanet</strong> - for DX Cluster spot visualization on the azimuthal map.</li>
<li><strong>cwdaemon</strong> - for CW operation, only if you choose parallel or serial port keying without Winkey.</li>
<table border="0" cellpadding="5" cellspacing="2" width="100%"><tbody><tr><td valign="top">
<img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong>
cwdaemon use may result in <strong>sloppy CW at speeds above 30 WPM</strong>.
Use Winkey (by K1EL) if possible or your <strong>kernel must be modified to minimalize the
latency</strong>. Tickless, high resolution timer and 1000 Hz sampling rate must be used.
Recommended for very experienced linux users only!</td></tr></tbody></table>
<li><strong>fldigi</strong> for RTTY and Digital Modes. Instal the package from your
distribution or download from the W1HKJ site <a href=http://www.w1hkj.com/Fldigi.html><strong>http://www.w1hkj.com/Fldigi.html</strong></a></li>
<ul>
<li><strong>Hamlib</strong> - <strong><font color="#FF0000">NEEDED</font></strong>,
without this CQRLOG will not work!
</li>
<li><strong>Trusted QSL</strong> - for LoTW operations. Ubuntu and Debian have this package in their repositories.</li>
<li><strong>xplanet</strong> - for DX Cluster spot visualization on the azimuthal map.</li>
<li><strong>cwdaemon</strong> - for CW operation, only if you choose parallel or serial port keying without Winkey.
</li>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top">
<img src="img/exc.png"></td>
<td bgcolor=ffffcc valign="top" align="justify"><strong><font color="red">WARNING!</font></strong>
cwdaemon use may result in <strong>sloppy CW at speeds above 30 WPM</strong>.
Use Winkey (by K1EL) if possible or your <strong>kernel must be modified to minimalize the
latency</strong>. Tickless, high resolution timer and 1000 Hz sampling rate must be used.
Recommended for very experienced linux users only!
</td>
</tr>
</tbody>
</table>
<li><strong>fldigi</strong> for RTTY and Digital Modes. Install the package from your
distribution or download from the W1HKJ site <a href=http://www.w1hkj.com/Fldigi.html><strong>http://www.w1hkj.com/Fldigi.html</strong></a>
</li>
</ul>
<strong><h3>I want to...</h3></strong>
<ul>
<li><a href="h22.html#bh4">print QSL labels</a></li>
<li><a href="h4.html#ah33">prepare LoTW log/update</a></li>
<li><a href="h4.html#ah34">prepare eQSL log/update</a></li>
<li><a href="h4.html#ah35">suggest a new feature</a></li>
<li><a href="h22.html#bh4">print QSL labels</a></li>
<li><a href="h4.html#ah33">prepare LoTW log/update</a></li>
<li><a href="h4.html#ah34">prepare eQSL log/update</a></li>
<li><a href="h4.html#ah35">suggest a new feature</a></li>
</ul>
<strong><h3>Troubleshooting</h3></strong>
<ul>
<li><a href="h5.html#ah37">my radio control (CAT) does not work</a></li>
<li><a href="h5.html#ah38">I'm unable to autologin to the Cluster</a></li>
<li><a href="h5.html#ah39">error message when trying to load "Can't load library:..."</a></li>
</ul><br>
<li><a href="h5.html#ah37">my radio control (CAT) does not work</a></li>
<li><a href="h5.html#ah38">I'm unable to autologin to the Cluster</a></li>
</ul>
<br>
<p align="center"><img src="img/line.png"></p>
<table border="0" cellpadding="2" cellspacing="2" width="100%">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;</td>
<td align="center" width="33%">[<a href="#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h1.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left" width="33%">&nbsp;</td>
<td align="center" width="33%">[<a href="#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h1.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
</body></html>
</body>
</html>

BIN
help/sql_console.html
View File

Binary file not shown.

270
help/wkusb.html
View File

@ -1,103 +1,191 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en-us"><head>
<title>CQRLOG - WinKey setup</title></head>
<body><table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody><tr><td valign="top"><img src="img/exc.png"></td>
<td align="justify" bgcolor="ffffcc" valign="top"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td></tr></tbody></table>
<html lang="en-us">
<head>
<title>CQRLOG - WinKey setup</title></head>
<body>
<table border="0" cellpadding="5" cellspacing="2" width="100%">
<tbody>
<tr>
<td valign="top"><img src="img/exc.png"></td>
<td align="justify" bgcolor="ffffcc" valign="top"><strong>
<font color="red">WARNING!</font></strong>
Backup your data often! BACKUP your log directory at the end of EVERY session!
All that you need to backup and store in a safe place is the log database directory
located in the ~/.config/cqrlog/database folder, or you can enable the autobackup function
in Preferences. This autobackup function creates an ADIF file with a backup of your log.
</td>
</tr>
</tbody>
</table>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h26.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h26.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
<div style="text-align: left;"><strong>CQRLOG for LINUX by OK2CQR &amp; OK1RR</strong></div>
<p align="center"><img src="img/line.png"></p>
<strong>WinKey setup</strong><br><br>
<div align="justify">Before any attempt to set up your WinKey, carefully read
the manual supplied on the accompanying CD (can also be downloaded from the K1EL's site
<a href="http://k1el.tripod.com/files/WKUSB_CD.zip"><strong>http://www.k1el.com</strong></a>
<br><br>
WinKey has three modes - a <em>host mode</em> (the keyer is connected and fully controlled
by the computer), a <em>standalone mode</em> (operated without any computer connection,
the speed pot and message buttons are fully functional) and a <em>command mode</em>
(a setup mode, commands can be entered via the paddle or dedicated
program on the computer). Because a full featured setup in CQRLOG would
probably be overkill, a very basic setup should be performed via
paddle using the command mode.<br><br>
<div align="center"><img src="img/c03.jpg"></div><br>
Press the red message button and hold it for approx. 2 seconds. The
keyer will play an 'R' (in Morse) if everything is OK or 6 dits if the
previous communication was not successful. In this case, press the red
button again until you hear the 'R'. Now you can enter your commands.
the manual supplied on the accompanying CD (can also be downloaded from the K1EL's site
<a href="http://k1el.tripod.com/files/WKUSB_CD.zip"><strong>http://www.k1el.com</strong></a>
<br><br>
WinKey has three modes - a <em>host mode</em> (the keyer is connected and fully controlled
by the computer), a <em>standalone mode</em> (operated without any computer connection,
the speed pot and message buttons are fully functional) and a <em>command mode</em>
(a setup mode, commands can be entered via the paddle or dedicated
program on the computer). Because a full featured setup in CQRLOG would
probably be overkill, a very basic setup should be performed via
paddle using the command mode.<br><br>
<div align="center"><img src="img/c03.jpg"></div>
<br>
Press the red message button and hold it for approx. 2 seconds. The
keyer will play an 'R' (in Morse) if everything is OK or 6 dits if the
previous communication was not successful. In this case, press the red
button again until you hear the 'R'. Now you can enter your commands.
</div>
<p><b>WK2 Standalone Command List</b></p>
<p></p><table border="0" cellpadding="2" cellspacing="2"><tbody><tr><td style="background-color: rgb(255, 255, 204);"><b>A</b>
- Select sidetone on or off</td><td style="background-color: rgb(255, 255, 204);"><b>O</b>
- Select output key port</td></tr><tr><td style="background-color: rgb(255, 255, 204);"><b>B</b> - Set Paddle
Break mode</td><td style="background-color: rgb(255, 255, 204);"><b>P</b>
- Save the settings in standalone mode</td></tr><tr><td style="background-color: rgb(255, 255, 204);"><b>C</b> - Set command
speed in WPM</td><td style="background-color: rgb(255, 255, 204);"><b>Q</b> - Query current settings</td></tr><tr><td style="background-color: rgb(255, 255, 204);"><b>D</b> - Decrement
serial number</td><td style="background-color: rgb(255, 255, 204);"><b>R</b> - Review message without transmitting</td></tr><tr><td style="background-color: rgb(255, 255, 204);"><b>F</b> - Set Farnsworth
Speed</td><td style="background-color: rgb(255, 255, 204);"><b>S</b> - Set bottom of speed pot range in WPM</td></tr><tr><td style="background-color: rgb(255, 255, 204);"><b>G</b> - Select serial
number 0/9 format</td><td style="background-color: rgb(255, 255, 204);"><b>T</b> - Key transmitter for tuning</td></tr><tr><td style="background-color: rgb(255, 255, 204);"><b>H</b> - Set Fast/Slow
AFK tail delay</td><td style="background-color: rgb(255, 255, 204);"><b>U</b> - Select Autospacing on/off</td></tr><tr><td style="background-color: rgb(255, 255, 204);"><b>J</b> - Set Paddle
sensitivity</td><td style="background-color: rgb(255, 255, 204);"><b>V</b> - Set Keying compensation in mSec</td></tr><tr><td style="background-color: rgb(255, 255, 204);"><b>K</b> - Select keyer
mode</td><td style="background-color: rgb(255, 255, 204);"><b>W</b> - Set Key Weight</td></tr><tr><td style="background-color: rgb(255, 255, 204);"><b>L</b> - Load message
memory slot</td><td style="background-color: rgb(255, 255, 204);"><b>X</b> - Exchange Paddles</td></tr><tr><td style="background-color: rgb(255, 255, 204);"><b>M</b> - Mute Transmit
(CPO mode)</td><td style="background-color: rgb(255, 255, 204);"><b>Y</b> - Set Dit/Dah Ratio</td></tr><tr><td style="background-color: rgb(255, 255, 204);"><b>N</b> - Load 4 digit
serial number</td><td style="background-color: rgb(255, 255, 204);"><b>Z</b> - Select sidetone frequency</td></tr></tbody></table><br>
<div align="justify">The '<b>P</b>' command is not listed in the user
manual, however it is a very important command. I recommend you save your
setup in standalone mode using the '<strong>P</strong>' command, also put a set of batteries
into the keyer (don't rely on the USB port).<br><br>
If you don't feel very comfortable with the timing, try the '<strong>J</strong>'
command to set up the 'paddle sensitivity'.<br><br>
<strong>The setup</strong> you will need is mostly the following:<br><ul>
<li>Select the output port (1 or 2) using the command '<strong>O</strong>'. Your Winkey confirms the port number with E (a single dot = port 1) or I (two dots = port 2). This setting is relevant to both paddle and keyboard operation.
</li><li>Choose the keyer mode (Curtis A or B, Ultimatic, Bug) with the command
'<strong>K</strong>'. Relevant only to paddle operation.
</li><li>Set up the weighting with the command '<strong>W</strong>'. The default
value is 50 which means that the pause has the same length as the dot. If you prefer
speeds above 30 WPM, try 'lighter' settings with pauses longer than dots (weighting
lower than 50). At slow speeds (below 20 WPM) a heavier settings may be an advantage
(above 50). The IARU operating manual by ON4UN and ON4WW is incorrect here, it lists
the weighting preferences backwards! Remember, that a pause carries a lot of information!
The proper setting is also affected by the keying properties of your radio. This setting
is relevant to both paddle and keyboard operation.
</li><li>Set up the keyer compensation (command '<strong>V</strong>') - this setting is
dictated by your keying system. It is relevant only if you are using a PTT line controlled
by the Winkey. It should prevent the hot switching of any relay in the T/R system.
Be careful, improper settings may cause serious damage of your equipment.
This setting is relevant to both paddle and keyboard operation.
<li>Set up the Paddle Break mode (command '<strong>B</strong>') - it should always be on.
OFF means that you will be unable to break continuous sending with the paddle.
</li></ul>
In host mode (when connected to the computer), the speed pot is inactive. <strong>You
can only change the speed with the PgUp/PgDn keys!</strong>
</div>
<table><tr><td valign="top"><img src="img/bulb.png"></td><td bgcolor=ccffff width="100%">
<strong><font color="blue">Remember to save your setup with the 'P' command!</font>
</strong> </td></tr></table>
<p align="center"><img src="img/line.png"></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h26.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
<p></p>
<table border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>A</b>
- Select sidetone on or off
</td>
<td style="background-color: rgb(255, 255, 204);"><b>O</b>
- Select output key port
</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>B</b> - Set Paddle
Break mode
</td>
<td style="background-color: rgb(255, 255, 204);"><b>P</b>
- Save the settings in standalone mode
</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>C</b> - Set command
speed in WPM
</td>
<td style="background-color: rgb(255, 255, 204);"><b>Q</b> - Query current settings</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>D</b> - Decrement
serial number
</td>
<td style="background-color: rgb(255, 255, 204);"><b>R</b> - Review message without transmitting</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>F</b> - Set Farnsworth
Speed
</td>
<td style="background-color: rgb(255, 255, 204);"><b>S</b> - Set bottom of speed pot range in WPM</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>G</b> - Select serial
number 0/9 format
</td>
<td style="background-color: rgb(255, 255, 204);"><b>T</b> - Key transmitter for tuning</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>H</b> - Set Fast/Slow
AFK tail delay
</td>
<td style="background-color: rgb(255, 255, 204);"><b>U</b> - Select Autospacing on/off</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>J</b> - Set Paddle
sensitivity
</td>
<td style="background-color: rgb(255, 255, 204);"><b>V</b> - Set Keying compensation in mSec</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>K</b> - Select keyer
mode
</td>
<td style="background-color: rgb(255, 255, 204);"><b>W</b> - Set Key Weight</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>L</b> - Load message
memory slot
</td>
<td style="background-color: rgb(255, 255, 204);"><b>X</b> - Exchange Paddles</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>M</b> - Mute Transmit
(CPO mode)
</td>
<td style="background-color: rgb(255, 255, 204);"><b>Y</b> - Set Dit/Dah Ratio</td>
</tr>
<tr>
<td style="background-color: rgb(255, 255, 204);"><b>N</b> - Load 4 digit
serial number
</td>
<td style="background-color: rgb(255, 255, 204);"><b>Z</b> - Select sidetone frequency</td>
</tr>
</tbody>
</table>
<br>
</body></html>
<div align="justify">The '<b>P</b>' command is not listed in the user
manual, however it is a very important command. I recommend you save your
setup in standalone mode using the '<strong>P</strong>' command, also put a set of batteries
into the keyer (don't rely on the USB port).<br><br>
If you don't feel very comfortable with the timing, try the '<strong>J</strong>'
command to set up the 'paddle sensitivity'.<br><br>
<strong>The setup</strong> you will need is mostly the following:<br>
<ul>
<li>Select the output port (1 or 2) using the command '<strong>O</strong>'. Your Winkey confirms the port number
with E (a single dot = port 1) or I (two dots = port 2). This setting is relevant to both paddle and
keyboard operation.
</li>
<li>Choose the keyer mode (Curtis A or B, Ultimatic, Bug) with the command
'<strong>K</strong>'. Relevant only to paddle operation.
</li>
<li>Set up the weighting with the command '<strong>W</strong>'. The default
value is 50 which means that the pause has the same length as the dot. If you prefer
speeds above 30 WPM, try 'lighter' settings with pauses longer than dots (weighting
lower than 50). At slow speeds (below 20 WPM) a heavier settings may be an advantage
(above 50). The IARU operating manual by ON4UN and ON4WW is incorrect here, it lists
the weighting preferences backwards! Remember, that a pause carries a lot of information!
The proper setting is also affected by the keying properties of your radio. This setting
is relevant to both paddle and keyboard operation.
</li>
<li>Set up the keyer compensation (command '<strong>V</strong>') - this setting is
dictated by your keying system. It is relevant only if you are using a PTT line controlled
by the Winkey. It should prevent the hot switching of any relay in the T/R system.
Be careful, improper settings may cause serious damage of your equipment.
This setting is relevant to both paddle and keyboard operation.
<li>Set up the Paddle Break mode (command '<strong>B</strong>') - it should always be on.
OFF means that you will be unable to break continuous sending with the paddle.
</li>
</ul>
In host mode (when connected to the computer), the speed pot is inactive. <strong>You
can only change the speed with the PgUp/PgDn keys!</strong>
</div>
<table>
<tr>
<td valign="top"><img src="img/bulb.png"></td>
<td bgcolor=ccffff width="100%">
<strong><font color="blue">Remember to save your setup with the 'P' command!</font>
</strong></td>
</tr>
</table>
<p align="center"><img src="img/line.png"></p>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="left" width="33%">&nbsp;&lt;<a href="h26.html"> Prev</a></td>
<td align="center" width="33%">[<a href="index.html#aa">Menu</a>]</td>
<td align="right" width="33%"><a href="h26.html">Next </a>&gt;</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>