cqrlog/help/h7.html
OH1KH 5f47da75a9 Changes to LoTW/eQSL download error files
Preface
	Sometimes you find some "QSO not found" errors in LoTW or eQSL download. There are some reasons for that.
		QSO did not complete and you did not log that, but the opponent station thinks it is completed.
		People type in their old paper logs to computer and upload them to LoTW/eQSL. QSO is ok but it is somewhere in your earlier paper logs.
		QSO may be an SWL report waiting to confirm via eQSL

	To make handling of those qsos a bit easier format of error files is changed.

	- Added adif header to lotw/eqsl download error files.
	- Added adif record for every lotw/eqsl error 'not in log' qso record
	  with lotw/eqsl sent+date and contest_id 'Qso_was_not_found_in_log!'
	- Renamed lotw/eqsl error files to ".adi".
	  Changed error file format by adif standard

	- Fixed frmMain speed button 'select all records' to be
	  'select all records now in buffer (max 500)' that is actually true.
	  This resolves issue #380 by easy way

	- help file fixes and additions

Squashed commit of the following:

commit efcd6114d249bab1181c0f89ac6759f08b4e9597
Author: OH1KH <oh1kh@sral.fi>
Date:   Wed Feb 16 10:06:17 2022 +0200

    help file fixes and additions

commit fcd9d9fe521006bcc20a267684a9f811364bacf0
Author: OH1KH <oh1kh@sral.fi>
Date:   Tue Feb 15 19:28:00 2022 +0200

    Removed *.txt from adif import selection list. Renamed lotw/eqsl error files to .adi. Changed error file format by adif standard

commit b81dcb04c49c20c26e14a13f891b40a253592114
Author: OH1KH <oh1kh@sral.fi>
Date:   Tue Feb 15 11:47:10 2022 +0200

     Added adif header to loww/eqsl error files.Added adif record for every lotw/eqsl error 'not in log' record with lotw/eqsl sent+date and command 'not in log'. Fixed frmMain 'select all records' to be 'select all records now in buffer (max 500)' that is actually true. Added *.txt files to show in adif import file selector so that lotw/eqsl eroro files can be found for import
2022-02-16 10:25:25 +02:00

151 lines
8.1 KiB
HTML

<!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>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2" cellspacing="2">
<tbody>
<tr>
<td align="center" width="33%">[<a href="index.html" target="_top">Menu</a>]</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><h3>Preparation</h3></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><h3>Setup</h3></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><h3>LoTW file export and upload</h3></p>
You find LoTW up- and download from <b>QSO list/QSL</b> menu.
<br> For daily usage it is easier to select<b>Export only QSQs that have never been uploaded</b> using the <b>Upload to LoTW TAB </b>of Export window.
<br> Below are instructions for making file to export and exporting it.
<br><br>
<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. But be aware that QSO with propagtion mode "RPT - repeater" are filtered, due to the LoTW rule that repeater QSO doesn't count.<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>
<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><h3>LoTW files download and processing</h3></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 press <b>Download and process data from LoTW website</b> a progress
indicator is displayed in <b>Progress</b> window.
<br>You can select to <b>show new confirmed qsos</b> in Progress window after import finish.
<br>You can also select to <b>import station information from LoTW </b>data if it is not filled during qso logging (default checked).
This does not overwrite logged data, just fills empty columns of WAZ, ITU, IOTA, GRID, STATE and COUNTY
</div>
<br><br>
<img src="img/h87.png"><br><br>
<div align=justify>The Size changes while downloading, When finished it indicates the
total file size downloaded. When the download finishes, a summary appears and the import begins,
showing the same progress indicator as above.
<br>In case there are files that are not in your log the queston to show the error file appears.
You can read more about import error file handling from <a href="qslimperr.html">LoTW/eQSL import errors</a>
</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.
<br>All downloaded files from LoTW are saved in ~/.config/cqrlog/lotw folder for possible later needs.
<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="center" width="33%">[<a href="index.html" target="_top">Menu</a>]</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>