From 8ff1412fcfb6fcdfc5e9a96fbdafb6eaafd033be Mon Sep 17 00:00:00 2001 From: Michael Clemens Date: Sat, 14 Nov 2020 22:40:22 +0100 Subject: [PATCH] updated documentation to include QSL ADIF export, qrz.com integration and changes to the rig control mechanism. --- doc/index.html | 56 +++++++++++++++++++++++++++++++++++--------------- 1 file changed, 40 insertions(+), 16 deletions(-) diff --git a/doc/index.html b/doc/index.html index fb23ccf..f0ca43b 100644 --- a/doc/index.html +++ b/doc/index.html @@ -278,14 +278,23 @@ they are not important.

previous QSOs when entering a new callsign in the main logging mode. -
  • rigmodel - Rig model for Hamlib.pm cat support.
    • +
  • hamlibaddr - IP address of the system on which the + hamlib rigctld daemon is running (default 127.0.0.1).
    • -
  • rigpath - Path to the device used by Hamlib, e.g. - /dev/ttyS0
    • +
  • hamlibport - Port number of the hamlib rigctld daemon + to which yfklog should connect (default: 4532)
  • autoqueryrig - When 1, the frequency and mode is automatically queried from the radio.
    • +
  • qrzuser - Your QRZ.com user name. This is needed + for querying qrz.com data in the logging screen. A subscription might + be needed for this.
    • + +
  • qrzpass - Your QRZ.com password. This is needed + for querying qrz.com data in the logging screen. A subscription might + be needed for this.
    • +
  • lotwdetails - Whether or not to use QSO details from LoTW to update the log.
    • @@ -383,6 +392,8 @@ following sections; some are self explanatory. A quick overview:

    database can be changed or deleted in this menu point.
  • Import/Export LoTW - Support for working with ARRL's LoTW. See chapter LoTW for details.
    • +
  • Export QSL ADIF - Generate an ADIF file of + all QSOs from the QSL queue.
  • Setup YFKlog - Most settings mentioned in Setup can be changed here.
  • DX cluster - Send commands to the DX cluster.
    • @@ -441,13 +452,11 @@ respectively.

  • This window shows information about the callsign entered, derived - from the country file cty.dat. The last line also shows - - if available - - known club memberships, if the DXCC was worked before, - and if so on which bands, and if the callsign appears in any other log, - as specified by checklogs in the config file. This is an example where all these - information are shown.
    • + from the country file cty.dat and - if configured - from qrz.com. + The last line also shows - if available - known club memberships, + if the DXCC was worked before, and if so on which bands, and if the callsign + appears in any other log, as specified by checklogs in the config file. + This is an example where all these information are shown.
  • The last few QSOs in the log are shown in Window 3. You can jump here by pressing F9 and select any QSO to edit it. The @@ -555,6 +564,16 @@ sent), and you can continue with the next card.

    save all changed QSL-flags, F3 cancels all changes and returns to the main menu.

    +

    6.2.3 Export ADIF files for external labeling/printing

    + +

    To export an ADIF file for using other software or services for printing labels +or QSL cards, YFKlog offers the submenu "Export QSL ADIF". For details on ADIF +exports and how to specify date ranges, please see the next chapter "7. ADIF +import and export".

    + +

    After exporting a QSL ADIF, the QSL status of all affected QSOs will be +changed from "Q" (queued) to "Y" (yes, sent). +

    7. ADIF import and export

    @@ -758,13 +777,18 @@ Perl bindings.

    13.1 Hamlib setup

    -

    The config file contains two parameters for hamlib: rigmodel -and rigpath. The first is the number of the transceiver to be -used, as shown in rigctl --list. The second is the path to the -device to which the transceiver is connected, e.g. /dev/ttyS0. +

    The config file contains two parameters for hamlib: hamlibaddr +and hamlibport. The first is the IP address of the rigctld that +should be polled, the second parameter the TCP port number. The defaults are:

    + +

    hamlibaddr=127.0.0.1
    +hamlibport=4532

    + +

    You need to have a rigctld instance running somewhere - either on the same +system or somewhere network accessible. The following is an example of +rigctld in combination with a Yaesu FT-450D:

    -
    $ ./rigctl --list 2> /dev/null | grep K2
-221     Elecraft        K2                      0.5     Beta
     +

    rigctld -m 127 -r /dev/ttyUSB0

    13.2 Usage