WaveLog Resources

Resource Area: Resource Home | Useful Links

Licensing: Get Licensed | License Testing

Repeaters, Nets, and Logging: Repeater & Nets | Net Operations | NetLogger

Digital, Radios, and Logs: Radio Guides | Pi-Star / Hotspots | WPSD | EchoLink | Wavelog

Activities: POTA | SOTA | Fox Hunt | Field Day | Special Event Resources

Emergency and Partner Groups: ARES | RACES | ERC

LDARC Wavelog Quick Reference

Server: https://wavelog.k6ldf.com/

Accounts: contact KN6RBP Rick or KO6ALP Terry.

Use this server for personal LDARC member logging and club logging, including special events, Field Day, demonstrations, and shared operating.

Before Logging

  1. Sign in.
  2. Check whether you are in your personal account or a club station.
  3. Select the correct station location.
  4. Select the correct logbook.
  5. If using WavelogGate, confirm the correct API key and station profile.

Personal Logging

Use your own account, your own station location, and your personal logbook.

Use QSO -> Live QSO for real-time operation.

Use QSO -> Post QSO for contacts entered after operating.

Club Mode

Switch into club mode before logging club, special event, or Field Day contacts.

To switch in:

  1. Sign in as yourself.
  2. Open the upper-right user/menu area.
  3. Choose the club station or special event station.
  4. Confirm the switch.
  5. Verify the club station context is active.
  6. Confirm station location and logbook.

To switch back:

  1. Save any open QSO.
  2. Use the upper-right “Switch back” option, or log out and log back in.
  3. Confirm your personal account is active again.

If you do not see the club station option, contact Rick or Terry.

Logging a QSO

  1. Open QSO -> Live QSO or QSO -> Post QSO.
  2. Enter callsign.
  3. Verify date/time, band, frequency, mode, and reports.
  4. Add grid, name, QTH, notes, or references as needed.
  5. Save.
  6. Check the recent contacts or Logbook view.

Confirming Contacts

Open Logbook, find the QSO, and use the QSO details/edit menu to update QSL, eQSL, LoTW, or other confirmation status.

Use the Logbook confirmation columns to see whether a contact has been sent, received, or confirmed.

DX Cluster

Use the DX Cluster/bandmap to find spots.

Helpful filters:

  • Band
  • Mode
  • Not Worked
  • Worked
  • Confirmed
  • Worked not Confirmed
  • LoTW users only
  • Contest only
  • My Favorites

Click a spot to open a QSO form. If CAT is configured, Ctrl/Cmd + click can tune the radio.

WavelogGate Setup

WavelogGate URL:

https://wavelog.k6ldf.com/index.php

WavelogGate needs:

  • Wavelog URL including index.php
  • API key
  • Correct station profile
  • Optional radio control through FLRig, Hamlib, or Internal Hamlib

Create API keys in the correct context:

  • Personal key for personal logging
  • Club/event key while switched into the club station for club logging

WSJT-X to WavelogGate

In WSJT-X:

  1. File -> Settings -> Reporting
  2. Enable Secondary UDP Server
  3. Server: localhost
  4. Port: 2333

Use Secondary UDP Server, not Primary UDP.

WavelogGate Common Ports

  • 2333 UDP: receives WSJT-X/FLDigi QSOs
  • 54321 HTTP: Wavelog QSY requests
  • 54322 WebSocket: radio status

Stop and Ask

Stop logging and contact Rick or Terry if:

  • You are unsure whether you are in personal or club mode.
  • Contacts are going into the wrong log.
  • You selected the wrong station profile.
  • You need access to a club station.
  • You are unsure about API keys for a club event.

Most Common Mistakes

  • Forgetting to switch into club mode.
  • Forgetting to switch back out of club mode.
  • Using the wrong station profile in WavelogGate.
  • Creating an API key in the wrong account context.
  • Leaving index.php off the WavelogGate URL.
  • Using WSJT-X Primary UDP instead of Secondary UDP.

LDARC Wavelog and WavelogGate Guide

This guide is for LDARC members using the club Wavelog server at:

https://wavelog.k6ldf.com

The LDARC Wavelog server is available to all LDARC members for both personal logging and club logging. Use it for your own station log, portable operations, special event stations, club stations, Field Day, contesting, demonstrations, and other LDARC operating activities.

To get an account set up, contact:

If you are not sure whether you should log under your own call, a club call, or a special event call, ask before logging. It is much easier to set the correct account, station location, and logbook before operating than to clean up contacts afterward.

What Wavelog Does

Wavelog is a web-based amateur radio logbook. You can use it from a normal browser without installing a full logging program. It supports multiple users, station locations, station profiles, QSL and confirmation tracking, awards, maps, statistics, DX cluster features, club station operation, and API integration with tools such as WavelogGate.

Think of Wavelog as the permanent logbook. It stores the QSO details and keeps them organized by station, location, logbook, operator, and confirmation status.

Think of WavelogGate as the bridge between your local shack computer and Wavelog. It can receive completed contacts from WSJT-X or FLDigi, forward them into Wavelog with your API key, and optionally send radio frequency and mode data between Wavelog and your radio through FLRig, Hamlib, or its internal Hamlib support.

Account Setup

  1. Go to https://wavelog.k6ldf.com/.
  2. Sign in with the account created for you.
  3. If you do not have an account yet, contact KN6RBP Rick or KO6ALP Terry.
  4. After your first login, review your account settings before logging contacts.

Recommended first-login checks:

  • Confirm your callsign is correct.
  • Confirm your name and email are correct.
  • Set your preferred display options.
  • Create or verify your personal station location.
  • Create or verify your personal logbook.
  • Generate an API key only if you plan to use WavelogGate or another integration.

Do not share your password or API keys. If a key is exposed, delete it in Wavelog and create a new one.

Personal Logging, Club Logging, and Special Events

LDARC members may use this Wavelog server in two main ways:

  • Personal logging: contacts made under your own callsign for your own station log.
  • Club logging: contacts made for an LDARC club call, special event, Field Day, demonstration, contest, or other shared operation.

Before operating, check the account context shown in the upper-right area of Wavelog. This matters because the active user or club station determines where contacts go.

For personal contacts, log while you are in your own account and using your own station location/logbook.

For club or special event contacts, switch into the correct club station or special callsign mode before logging. When finished, switch back to your own account.

Key Wavelog Concepts

Users

A user is an individual login account. Most LDARC members will have one user account tied to their own callsign.

Station Locations

A station location is a template for where and how you are operating. It can include your callsign, grid square, DXCC, QTH, state, county, IOTA/SOTA/POTA/WWFF references, and third-party service settings.

Use separate station locations when the operating facts are different. Examples:

  • Home station
  • Portable station
  • Mobile station
  • POTA activation
  • Field Day site
  • Special event station
  • Different callsign or club call

Station locations are important because Wavelog uses them throughout the system. They help keep QSOs, awards, QSL information, and service integrations clean.

Station Profiles

Station profiles contain QSOs under a profile and are tied to the station callsign, DXCC, grid square, and related station information. A new user should have at least one station profile before logging.

When using WavelogGate, the selected station profile tells Wavelog where imported QSOs should land.

Logbooks

A logbook is a way to group contacts for personal or operational use. You might have one normal personal logbook, plus separate logbooks for Field Day, special events, club events, or experiments.

For most members:

  • Use your personal logbook for your everyday QSOs.
  • Use a separate event or club logbook when instructed for LDARC activities.
  • Do not mix club-event QSOs into your personal log unless that is explicitly part of the operating plan.

Setting Up Locations and Logbooks for Personal Use

Before logging your own QSOs, set up your personal station information.

  1. Sign in to https://wavelog.k6ldf.com/.
  2. Open the station/location area from the administration or station menu available to your account.
  3. Create a station location for your normal operating position.
  4. Fill in at least:
  • Callsign
  • Grid square
  • DXCC/entity
  • State and county, if applicable
  • Station description, such as “Home”, “Portable”, or “Mobile”
  1. Save the location.
  2. Make sure it is selected before you log contacts.
  3. Create or select your personal logbook.

Good naming examples:

  • KN6ABC Home
  • KN6ABC Portable
  • KN6ABC POTA
  • KN6ABC Mobile

Avoid vague names such as Test, Station 1, or Default once you are doing real logging. Clear names prevent mistakes later.

Logging Contacts in Wavelog

Wavelog offers two common QSO entry modes:

  • Live QSO: best when operating in real time. It uses a live clock and can use radio CAT information if configured.
  • Post QSO: best when entering contacts after the fact from paper notes, another logger, or a past event.

Live QSO

Use Live QSO while actively operating.

  1. Confirm you are in the correct user or club station context.
  2. Confirm the correct station location and logbook are selected.
  3. Open QSO -> Live QSO.
  4. Enter the callsign.
  5. Let Wavelog look up available callsign details.
  6. Enter or verify:
  • Band
  • Frequency
  • Mode
  • Date and time
  • RST sent and received
  • Name, QTH, grid, state, county, or notes as needed
  1. Save the QSO.

If CAT/radio integration is active, Wavelog may pre-fill frequency and mode. Still verify the contact before saving.

Post QSO

Use Post QSO when entering contacts after operating.

  1. Open QSO -> Post QSO.
  2. Enter the contact date and time carefully.
  3. Enter callsign, band, mode, reports, and other details.
  4. Save the QSO.

Post-logging is a common place for errors. Pay special attention to UTC date/time, band, mode, and callsign spelling.

After Saving

After logging, check the recent contacts list or Logbook view. Confirm:

  • The callsign is correct.
  • The date and time are correct.
  • The band, mode, and frequency are correct.
  • The QSO appears under the intended station location/logbook.
  • Club or special event contacts show the correct operator context.

Editing, Deleting, and Correcting QSOs

To edit a contact:

  1. Open Logbook.
  2. Search for the callsign or browse to the QSO.
  3. Use the action menu or edit icon on the right side of the QSO row.
  4. Correct the needed fields.
  5. Save.

To delete a contact, open the QSO edit/details view and use the delete option if your account permissions allow it.

For club logs, do not delete another operator’s QSO unless you are authorized and certain it is wrong. If in doubt, contact KN6RBP Rick or KO6ALP Terry.

Confirming Contacts and QSL Status

Wavelog tracks confirmation and QSL status for normal QSL cards and supported online services such as LoTW, eQSL, QRZ.com, HRDLOG.net, and others depending on server and account configuration.

In the Logbook view, confirmation columns show whether a QSL action has been sent or received. Wavelog commonly uses visual indicators for sent and received status, and color changes to show completed actions.

Use confirmation tracking to answer questions such as:

  • Has this QSO been confirmed?
  • Was a QSL sent?
  • Was a QSL received?
  • Has this contact been confirmed through LoTW or eQSL?
  • Does this QSO count toward an award?

To update confirmation information:

  1. Open Logbook.
  2. Find the QSO.
  3. Open the QSO details or edit menu.
  4. Update QSL, eQSL, LoTW, or other confirmation fields as appropriate.
  5. Save the QSO.

If your personal LoTW, eQSL, QRZ, or other external service is not configured, Wavelog can still store your QSOs, but it may not be able to automatically upload or synchronize confirmations for that service.

For club or special event logs, ask before connecting personal third-party accounts. Club logs may need club-owned credentials or no third-party upload at all.

Using the DX Cluster

Wavelog includes a DX Cluster bandmap that shows live DX spots and can help you find stations to work.

The DX Cluster can show:

  • Live DX spots
  • Band and mode filters
  • DXCC and continent filters
  • Worked, not worked, confirmed, and worked-not-confirmed status
  • POTA/SOTA/IOTA/WWFF or contest indicators where available
  • A map showing station locations and paths
  • One-click opening of a QSO form
  • Click-to-tune when CAT control is configured

Basic DX Cluster Workflow

  1. Open the DX Cluster or bandmap feature.
  2. Choose the band and mode you are operating.
  3. Use filters to reduce noise.
  4. Look for needed or interesting stations.
  5. Click a spot to open a QSO form with available details pre-filled.
  6. Work the station on the air.
  7. Verify the QSO details.
  8. Save the contact.

Helpful Filters

Use these filters when the spot list is too busy:

  • Band: show only the band you are using.
  • Mode: show CW, SSB, FT8, FM, or another mode.
  • Not Worked: find new stations/entities.
  • Worked not Confirmed: find stations/entities you still need confirmed.
  • Confirmed: verify previous confirmed contacts.
  • LoTW users only: useful for award chasing.
  • Contest only: useful during contests.
  • My Favorites: quickly narrow the display to saved interests.

CAT and Click-to-Tune

If CAT control is set up, Wavelog can track your radio band and tune the radio from DX Cluster spots. In Wavelog’s DX Cluster guide, Ctrl/Cmd + click is used for tune actions.

If the bandmap keeps changing unexpectedly, turn off CAT tracking for the cluster view.

If CAT is not configured, the DX Cluster still works as a spotting and logging aid. You will tune the radio manually.

Club Mode and Club Station Logging

Club mode is one of the most important features for LDARC use. It lets an approved member switch from their own account into a club station or special event station and log QSOs there.

Use club mode for:

  • LDARC club station operation
  • Special event callsigns
  • Field Day
  • Demonstrations
  • Shared contesting
  • Any operation where contacts should belong to a club or event log instead of your personal log

Before Switching Into Club Mode

Confirm:

  • You have permission to use the club station or event call.
  • You know which callsign should be on the air.
  • You know which station location and logbook should be active.
  • You know whether WavelogGate should use a club/event API key or your personal key created while switched into the club station.
  • Other operators know who is logging and when.

Switching Into Club Mode

  1. Sign in using your own Wavelog account.
  2. Look at the upper-right user/menu area.
  3. If you have been added to a club station, you should see a switch option for the club station.
  4. Select the club station or special event station.
  5. Confirm the switch when prompted.
  6. Verify that the interface now shows the club station context.
  7. Select the correct station location and logbook for the activity.
  8. Start logging.

Do not assume you are in club mode. Always verify the active context before the first QSO.

Switching Back Out of Club Mode

When you are finished:

  1. Stop logging.
  2. Save any open QSO.
  3. Use the upper-right menu option to switch back to your own account. Wavelog may show this as a “Switch back” option.
  4. Confirm that your personal account is active again.
  5. If you are at a shared computer, log out.

You can also log out and log back in to return to your normal account context.

Club Mode Permissions

Wavelog supports different club station permission levels.

  • Club members can switch into the club station and log QSOs.
  • Club members with ADIF permission can also upload and download ADIF files for QSOs they made.
  • Club officers can manage club station membership and permissions, but they do not automatically have full Wavelog server administrator rights.

If you cannot see a club station switch option, you probably have not been added to that club station yet. Contact KN6RBP Rick or KO6ALP Terry.

WavelogGate Integration

WavelogGate is a desktop gateway application. It connects local amateur radio software and radio control tools to Wavelog.

Use WavelogGate when you want to:

  • Automatically send completed WSJT-X contacts to Wavelog.
  • Automatically send completed FLDigi contacts to Wavelog.
  • Let Wavelog know your radio frequency and mode.
  • Use Wavelog DX Cluster click-to-tune features with radio CAT control.
  • Use FLRig, Hamlib, or WavelogGate’s internal Hamlib support.

WavelogGate is especially useful for FT8/FT4 and other digital modes where contacts are generated locally in WSJT-X.

Installing WavelogGate

Download WavelogGate from the official GitHub releases page:

https://github.com/wavelog/WaveLogGate/releases

Choose the package for your operating system:

  • Windows: download the .exe.
  • macOS: download the .dmg for Apple Silicon or Intel.
  • Linux: download the .deb, .rpm, or use the available Arch packages as appropriate.

Creating a Wavelog API Key

WavelogGate needs an API key so it can send contacts to Wavelog.

  1. Sign in to https://wavelog.k6ldf.com/.
  2. Open your user/settings menu.
  3. Open the API key section.
  4. Create a new key.
  5. Use a read/write key for WavelogGate if it will upload QSOs.
  6. Copy the key into WavelogGate.
  7. Store it securely.

Use read-only keys only for tools that do not need to write QSOs. WavelogGate needs write access when it is submitting contacts.

You can delete an API key later to remove access.

API Keys in Club Mode

When you switch into a club station, Wavelog treats API keys and radios in the club station context. Each user who switches into a club station can create their own API keys and radio entries for that club station. Club members can see their own keys; club officers can see key ownership, with other users’ keys masked.

For LDARC operations, this means:

  • Personal WavelogGate logging should use your personal API key and personal station profile.
  • Club/event WavelogGate logging should be configured while switched into the correct club station, using the correct club/event station profile.
  • Do not reuse a personal API key for club logging unless Rick or Terry has specifically told you to do so.

WavelogGate Configuration

In WavelogGate, configure the Wavelog section:

  • URL: https://wavelog.k6ldf.com/index.php
  • API Key: your Wavelog API key
  • Station: choose the correct station profile from the dropdown
  • Radio name: a useful name such as Home IC-7300, Field Day Radio 1, or WLGate

The WavelogGate URL should include index.php. If the station list does not load or the test reports a wrong URL, check that the URL ends with index.php.

After entering the URL and key, reload the station list and select the correct station profile. This step is critical. If the wrong station profile is selected, contacts can be logged to the wrong location.

Testing WavelogGate

Use WavelogGate’s Test button before an event or before relying on it for real contacts. The test verifies that WavelogGate can talk to the server and that the URL/API key/station settings are usable.

If the test fails:

  • Recheck the URL.
  • Recheck the API key.
  • Recheck whether the key was created in personal mode or club mode.
  • Recheck the selected station profile.
  • Confirm you are online.

WSJT-X Setup

In WSJT-X:

  1. Open File -> Settings -> Reporting.
  2. Enable Secondary UDP Server.
  3. Set server name to localhost if WavelogGate is on the same computer.
  4. Set server port to 2333.
  5. Save settings.

Use the Secondary UDP Server for WavelogGate. WavelogGate expects that format for WSJT-X logging.

When WSJT-X completes a logged QSO, WavelogGate receives the UDP log packet and submits the QSO to Wavelog using your configured API key and station profile.

FLDigi Setup

In FLDigi:

  1. Open Configure -> User Interface -> Logging.
  2. Enable UDP log output.
  3. Set host to localhost if WavelogGate is on the same computer.
  4. Set port to 2333.
  5. Save settings.

Radio Control with FLRig, Hamlib, or Internal Hamlib

WavelogGate can operate without radio control. In that case it simply forwards log entries from WSJT-X or FLDigi into Wavelog.

For frequency/mode tracking and click-to-tune, configure a radio backend:

  • None: no radio control; log forwarding only.
  • FLRig: connect to a running FLRig instance, commonly at 127.0.0.1:12345.
  • Hamlib: connect to a running rigctld instance, commonly at 127.0.0.1:4532.
  • Internal Hamlib: let WavelogGate manage a local rigctld process if supported on your system.

If you do not need click-to-tune, start with None. Add radio control later once basic logging is working.

WavelogGate Ports

Default WavelogGate ports:

  • 2333 UDP inbound: receives QSO log packets from WSJT-X or FLDigi.
  • 54321 HTTP inbound: receives QSY requests from Wavelog.
  • 54322 WebSocket outbound: broadcasts live radio status.

If another program is using one of these ports, WavelogGate will show a status error. Close the conflicting program or change the WavelogGate settings where available.

Recommended Event Workflow

For Field Day, a special event, or a club station activity:

  1. Before the event, Rick, Terry, or an authorized club officer confirms the correct club station, logbook, station location, and permissions.
  2. Operators sign in with their own accounts.
  3. Operators switch into the correct club station.
  4. Operators verify the active station location/logbook.
  5. WavelogGate stations are configured using API keys created in the correct club station context.
  6. Each operating position runs a quick test.
  7. Operators log contacts.
  8. Operators periodically check the Logbook view for accuracy.
  9. At shift change, the outgoing operator saves any open QSO and switches/logs out.
  10. The incoming operator signs in, switches into the club station, verifies context, and continues.
  11. After the event, authorized users review, export, upload, or reconcile the log.

Common Mistakes to Avoid

  • Logging club contacts while still in your personal account.
  • Forgetting to switch back after club operation.
  • Selecting the wrong station profile in WavelogGate.
  • Creating an API key in personal mode, then using it for club logging.
  • Using the wrong WavelogGate URL by leaving off index.php.
  • Using WSJT-X Primary UDP instead of Secondary UDP.
  • Post-logging with local time instead of UTC when UTC is required.
  • Uploading a large ADIF into the wrong station location or logbook.
  • Deleting another operator’s club QSO without permission.

Troubleshooting

I cannot log in

Contact KN6RBP Rick or KO6ALP Terry.

I do not see the club station switch option

You probably have not been added to that club station, or you are not signed into the correct account. Contact Rick or Terry.

My contacts went into my personal log instead of the club log

Stop logging immediately. Do not keep adding contacts. Contact Rick or Terry so the QSOs can be reviewed and moved or corrected if possible.

WavelogGate station list is empty

Check:

  • URL is https://wavelog.k6ldf.com/index.php
  • API key is correct
  • API key has the needed permissions
  • API key was created in the correct personal or club context
  • You pressed reload for the station list

WSJT-X contacts are not appearing in Wavelog

Check:

  • WavelogGate is running.
  • WavelogGate shows no port conflict.
  • WSJT-X Secondary UDP Server is enabled.
  • WSJT-X server is localhost or the WavelogGate computer IP.
  • WSJT-X port is 2333.
  • WavelogGate has the correct URL, API key, and station profile.

DX Cluster shows no spots

Check:

  • Filters are not too narrow.
  • Band and mode selections are correct.
  • Clear filters and reload the page.
  • If using CAT tracking, confirm the radio interface is active.
  • Ask Rick or Terry if the server-side DX Cluster cache needs attention.

Sources and Further Reading

LDARC Guide to Sending and Receiving QSL Cards in Wavelog

This guide is for LDARC members using the Wavelog server at:

https://wavelog.k6ldf.com

For account setup or access help, contact:

Use this guide for personal QSL work and for LDARC club activities such as special events, Field Day, demonstrations, and club station operation. Before changing QSL settings or sending confirmations for a club log, make sure you are authorized to do so.

What QSL Means in Wavelog

A QSL is confirmation that a contact happened. In Wavelog, QSL information can cover several different confirmation paths:

  • Paper QSL cards sent or received directly or through a bureau.
  • Printed labels for physical cards.
  • Wavelog-generated QSL postcards.
  • eQSL confirmations and digital card images.
  • LoTW confirmations.
  • QRZ, HRDLOG.net, Club Log, or other third-party log confirmation services if configured.

Wavelog does not replace the need to make an accurate QSO first. A QSL confirmation should match a real contact already in your log.

Before You Send or Receive QSLs

Check these items first:

  1. Sign in to https://wavelog.k6ldf.com/.
  2. Confirm whether you are in your personal account or switched into a club station.
  3. Confirm the correct station location and logbook are selected.
  4. Confirm the QSO details are accurate before sending any confirmation.
  5. For club or event logs, confirm the club’s QSL policy with Rick, Terry, or the event lead.

Do not send personal QSLs from a club log unless that is part of the event plan. Do not configure personal LoTW, eQSL, QRZ, or other third-party credentials inside a club station unless instructed.

Finding QSL Status

  1. Open Logbook.
  2. Search for the callsign or browse to the QSO.
  3. Review the QSL-related columns.
  4. Open the QSO details or edit menu for the full confirmation fields.

The Logbook view uses confirmation columns to show whether a QSL was sent, received, or confirmed through supported services. The exact icons and colors may vary by theme, but the main idea is:

  • Sent means your side has sent or uploaded a confirmation.
  • Received means the other station’s confirmation has been received or imported.
  • Confirmed means the QSO is matched or accepted through the selected path.

Paper QSL Workflow

Use this workflow for traditional cards sent direct, through a bureau, or as part of an event batch.

Sending a Paper QSL

  1. Open Logbook.
  2. Find the QSO.
  3. Verify the QSO details:
  • Callsign
  • Date and time in UTC
  • Band
  • Mode
  • Frequency
  • Signal reports
  • Your station callsign and location
  1. Mark the QSO as requested or queued for QSL printing if you plan to print labels or postcards.
  2. Print the label or postcard.
  3. Attach the label to the card, or use the generated postcard.
  4. Mail the card direct, send through the bureau, or handle according to club/event instructions.
  5. Update the QSO’s QSL sent status after the card is prepared or mailed.

For club events, use the process defined for that event. Some special event logs may wait until after the event to print cards in one batch.

Receiving a Paper QSL

  1. Open Logbook.
  2. Search for the callsign.
  3. Confirm that the received card matches the logged QSO.
  4. If the details match, open the QSO details/edit view.
  5. Mark the paper QSL as received.
  6. Add notes if needed, such as direct, bureau, manager, or event card.
  7. Save the QSO.

If the card does not match your log, do not force it. Check for:

  • UTC date rollover.
  • Wrong band or mode.
  • Similar callsign.
  • Operator logged under the wrong club or personal account.
  • A duplicate or corrected QSO.

For club logs, ask before changing another operator’s QSO.

Printing QSL Labels

Wavelog includes label printing for physical QSL cards.

Set Up Label Printing

  1. Open the user menu.
  2. Choose Labels.
  3. If no label type exists, create a paper type first if needed.
  4. Create a label type.
  5. Save it.
  6. Choose Use For Print.

If you use a sheet of labels, configure the paper and label layout carefully. If you use a dedicated label printer, create the paper type and label type for that printer’s label size.

Add QSOs to the Print Queue

Labels print from queued QSOs. A QSO appears in the label queue when its QSL status is set to Requested or Queued.

  1. Open Logbook.
  2. Find the QSO.
  3. Set the QSL status to Requested or Queued.
  4. Save.
  5. Open Labels.
  6. Select the queued QSOs.
  7. Click the printer icon.
  8. Choose print options, including starting position on a partially used sheet if needed.
  9. Print.

After printing, update the QSO sent status according to your workflow.

Designing and Printing QSL Postcards

Wavelog also has a QSL Postcard Designer for physical postcard-style QSLs. It can create a ready-to-print PDF, normally one postcard per callsign. The standard card size is 5.5 x 3.5 inches.

Create a QSL Postcard Template

  1. Open the user menu.
  2. Choose QSL Postcard Designer.
  3. Optionally upload a background image.
  4. Add fields such as callsign, date, time, band, mode, RST, grid, and your station information.
  5. Add any fixed text, such as PSE QSL, TNX QSL, 73, club name, or special event name.
  6. Set template options such as how many QSOs can appear per card.
  7. Save the template with a clear name.
  8. Generate a test PDF and proofread it.

Good template names:

  • KN6ABC Personal Card
  • LDARC Field Day
  • K6LDF Special Event
  • Portable Activation

Print Postcards

You can print cards for all QSOs awaiting cards or for specific selected QSOs, depending on the postcard designer options available to your account.

Before printing a large batch:

  • Print a proof first.
  • Confirm callsign and address placement.
  • Confirm UTC time display.
  • Confirm the right station callsign and location.
  • Confirm the background image prints correctly.
  • Confirm card stock orientation in your printer.

Mailing addresses may depend on the configured callbook lookup service. If no usable address is found, a postcard may not be generated for that callsign.

eQSL Workflow

eQSL is a digital QSL-card service. If configured, Wavelog can synchronize with eQSL.cc so you do not have to manage every eQSL task manually.

Important: Wavelog does not download your entire eQSL log as a replacement for your Wavelog log. The QSO must already exist in Wavelog. Wavelog uses eQSL to upload confirmations and fetch confirmations for matching logged QSOs.

eQSL Setup Requirements

Before using eQSL in Wavelog:

  • Your eQSL login details must be set in your Wavelog user profile.
  • Your eQSL username is usually the callsign for that eQSL account.
  • Each station profile should have the correct eQSL QTH Nickname.
  • The QSO date must fall within the valid date range for that eQSL QTH/Nickname.

eQSL treats each QTH Nickname like its own location with its own credentials and validity range. If you change a password or location date range in eQSL, make sure Wavelog matches.

Upload QSOs to eQSL

  1. Open the eQSL area from the user menu.
  2. Choose Upload QSOs.
  3. Review the list of QSOs that have not been sent.
  4. Upload the QSOs.
  5. Confirm the QSOs are marked sent after a successful upload.

Import eQSL Confirmations

  1. Open the eQSL area from the user menu.
  2. Use the import option.
  3. Either import an exported eQSL inbox ADIF file or use the pull/download option if available.
  4. Wavelog marks matching QSOs as received.
  5. In Logbook, click the received eQSL indicator to view the digital card image if available.

eQSL Cautions

  • Avoid special characters in eQSL passwords used with API-style access.
  • Keep passwords simple enough for eQSL’s backend to accept.
  • Make sure each eQSL QTH Nickname has the correct date range.
  • If eQSL returns wrong password or user not found, Wavelog may remove stored credentials to protect the account or server.

LoTW Workflow

LoTW confirmations are excellent for awards because they are widely accepted and cryptographically tied to your callsign certificate.

LoTW Setup Requirements

LoTW setup depends on your LoTW account and certificate. If you upload a certificate into Wavelog, export it from TQSL version 2.7 or later, and do not set a password during export.

LoTW uploads and downloads use different credentials:

  • Uploads use the LoTW certificate.
  • Downloads use your LoTW username and password.

If uploads work but downloads fail, check the LoTW username/password stored in Wavelog.

Uploading to LoTW

  1. Confirm your LoTW certificate is valid for the QSO date range.
  2. Open the LoTW upload/synchronization area.
  3. Review QSOs ready for upload.
  4. Upload.
  5. Wavelog marks QSOs as uploaded when the upload itself succeeds.

LoTW processes uploaded logs asynchronously. That means LoTW may accept the uploaded file for processing before all matches are visible.

Downloading LoTW Matches

  1. Confirm your LoTW username and password are current in Wavelog.
  2. Open the LoTW synchronization area.
  3. Download or sync confirmations.
  4. Review updated QSO confirmation status in Logbook.

LoTW Cautions

  • A certificate can be valid overall but still restricted to a specific QSO start/end date range.
  • QSOs outside the certificate QSO date range will not upload successfully.
  • Renewed certificates may replace older certificates. If LoTW says the certificate was superseded, replace it in Wavelog.
  • LoTW’s last-upload activity data can lag because the source file is updated periodically, not continuously.

QSL Cards in Club Mode

Club station and special event QSLs need extra care.

Before sending, uploading, importing, or marking QSLs in club mode:

  1. Confirm you are switched into the correct club station.
  2. Confirm the correct club/event station location.
  3. Confirm the correct club/event logbook.
  4. Confirm the event’s QSL plan.
  5. Confirm whether you are allowed to update QSL statuses.

For LDARC events, the club may choose one of these workflows:

  • One person handles all outgoing QSLs after the event.
  • Operators mark requested cards, but do not print or mail them.
  • Operators print cards during the event.
  • Digital confirmations are uploaded after review.
  • No automatic third-party uploads are used for the event.

If you are unsure, stop and ask KN6RBP Rick or KO6ALP Terry.

Recommended Personal Workflow

For normal personal operating:

  1. Log the QSO accurately.
  2. Confirm the station location and logbook are correct.
  3. If the other station requests a paper card, mark the QSO Requested or Queued.
  4. Print a label or postcard.
  5. Mail the card.
  6. Mark QSL sent.
  7. When a card arrives, verify it against the log.
  8. Mark QSL received.
  9. Use eQSL or LoTW sync if you have configured those services.

Recommended LDARC Event Workflow

For special events, Field Day, and club operations:

  1. Decide the QSL policy before the event starts.
  2. Use the correct club station and event logbook.
  3. Keep station locations clean and event-specific.
  4. During the event, log accurately and avoid unnecessary QSL status changes unless assigned.
  5. After the event, review the log for errors.
  6. Export or back up the event log if needed.
  7. Print cards or upload digital confirmations only after review.
  8. Keep notes about what was sent and when.

Common Mistakes

  • Marking a QSL sent before it was actually printed, mailed, or uploaded.
  • Marking a QSL received without checking the QSO details.
  • Sending personal QSLs from a club log.
  • Uploading club QSOs to a personal eQSL or LoTW account.
  • Printing a batch from the wrong logbook.
  • Using the wrong station location on a card.
  • Forgetting that eQSL QTH Nicknames have their own date ranges and credentials.
  • Forgetting that LoTW certificates can have QSO date restrictions.
  • Printing without first checking a proof PDF.

Troubleshooting

The QSO is missing from the label queue

Make sure the QSO is marked Requested or Queued for QSL printing.

The postcard did not generate for a callsign

Check whether Wavelog has a usable mailing address for that callsign. The postcard designer may skip callsigns without address data.

eQSL upload fails

Check the eQSL username, password, QTH Nickname, and QTH date range. Also check for password characters that eQSL’s backend may reject.

eQSL confirmations are not appearing

Confirm the QSO already exists in Wavelog. Wavelog uses eQSL to confirm existing logged QSOs; it is not a full-log import replacement.

LoTW upload fails

Check whether the LoTW certificate is current, not superseded, and valid for the QSO date range.

LoTW download fails

Check the LoTW username and password in Wavelog. Upload and download credentials are not the same mechanism.

Club/event QSLs look wrong

Stop the batch. Confirm the club station, station location, logbook, template, and QSL policy before continuing.

Sources and Further Reading

Resource Area: Resource Home | Useful Links

Licensing: Get Licensed | License Testing

Repeaters, Nets, and Logging: Repeater & Nets | Net Operations | NetLogger

Digital, Radios, and Logs: Radio Guides | Pi-Star / Hotspots | WPSD | EchoLink | Wavelog

Activities: POTA | SOTA | Fox Hunt | Field Day | Special Event Resources

Emergency and Partner Groups: ARES | RACES | ERC