Logging QSOs shouldn’t feel like work — especially when you’re running portable. Whether you’re activating a POTA park, chasing summits for SOTA, joining Field Day, or just working HF from a hilltop, you need a logging app that’s fast, offline-ready, and built for real operators.

HAMRS is exactly that.

It’s built from the ground up for modern ham radio ops — simple UI, solid performance, and zero learning curve. Whether you run 100 watts or QRP, HAMRS gives you a clean, fast way to log contacts in the field, then export them for LoTW, QRZ, or your main shack log.

Why HAMRS Matters for Portable Ham Radio

• Offline logging with fast entry — no internet needed
• Templates for POTA, SOTA, Field Day, etc.
• Auto-fill grid squares, park info, and more
• ADIF import/export — seamless integration with Logbook of The World, QRZ, etc.
• FLRig support — auto-fill frequency/mode from your rig (Pro)
• Dark mode for visibility in all lighting conditions
• Built for speed — logs pileups without freezing or lagging

If you’re logging by hand or using bloated shack software on your laptop, HAMRS will feel like a breath of fresh air.

Install HAMRS on Arch Linux (and Derivatives)

On Arch, Manjaro, CachyOS, or any Arch-based distro, install it from the AUR with:

yay -S hamrs-appimage

This installs the latest AppImage version and sets up a launcher in your menu. Launch it, select your logging template, and you’re ready to go.

Perfect for:

• QRP operators
• HF/VHF/UHF field deployments
• Satellite logging (custom templates supported)
• EMCOMM / field exercises
• Club stations
• Quick home station logging without extra config

Exporting and Uploading Logs

Once you’re done operating, you can:

• Export logs in ADIF format
• Upload directly to QRZ (built-in feature)
• Import into TQSL for Logbook of The World
• Share logs with your club or contest team

HAMRS speaks the language of ham radio. No conversions, no weird formats.

Support the Developer

HAMRS is built by a fellow ham with optional Pro features like rig control and cloud sync.

Support the project via:

• Patreon
• Merch
• Direct donation

Final Key Point

You already care about radios, antennas, propagation, and signal reports — don’t let your logging app be the weakest part of your setup.

HAMRS was made for you — the operator in the field, in the car, in the club tent. If you value efficiency and simplicity while still hitting all the right ham features, this is your logger.

Every Day Is Field Day
https://www.hamrs.app

The post A Better Logger for Hams: HAMRS appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Enter the NAS — Network Attached Storage — a powerful and often overlooked tool for modern amateur radio operators. Whether you’re a casual hobbyist or a serious station manager, a NAS can simplify and secure your digital life in the shack.

Let’s explore how NAS systems can benefit amateur radio operators, practical use cases, and some guidance to help you set one up.

What is a NAS?

A NAS is a dedicated device or server connected to your local network that stores data and provides services like file sharing, media streaming, backups, and more. Think of it as your personal cloud, available on your LAN (and remotely if you allow it).

Open-source NAS systems like TrueNAS, OpenMediaVault, Rockstor, and XigmaNAS make it easy and affordable for hams to build one using spare hardware or a Raspberry Pi.

Why Hams Should Consider a NAS

Here are several ways a NAS can become a central part of your shack:

1. Logbook and Data Backup

Store all your digital logbooks (e.g., N1MM, CQRLOG, Ham Radio Deluxe, Fldigi) in one place and access them from multiple devices.

• Automatically back up logs from your Raspberry Pi or Windows machine.
• Share your logbook with your contesting team on the same LAN.
• Keep a version history in case of accidental deletion.

2. SDR Recordings & Waterfalls Archive

Running SDR receivers like SDRplay, HackRF, or RTL-SDR? Those I/Q recordings and spectrogram images can take up a lot of space. A NAS lets you:

• Store massive SDR data files securely.
• Host them for playback or offline analysis.
• Use ZFS/Btrfs snapshots to prevent data corruption.

3. Web Server for Shack Tools

Host useful ham tools like:

• Local callsign lookup database
• DX cluster web interface
• OpenWebRX or KiwiSDR server
• Static wiki/documentation for station SOPs

A NAS with Docker support can run these tools as services—without tying up your main shack PC.

4. Shared Resources and Scripts

Many hams use scripting (Bash, Python, Node-RED) for automating things like antenna switching, remote rig control, or APRS messaging. Store all your scripts and station configs in one place.

Bonus:

• Sync with Git for version control.
• Share with your team during field day or emergency comms ops.

5. APRS and Meshtastic Gateway Backups

Running APRS I-Gates, Meshtastic bridges, or Direwolf/KISS TNC setups? Store:

• Config files (JSON, ini, conf)
• Logs of packet traffic
• Diagnostic captures (tcpdump, AX.25 monitoring)

Keep everything ready for instant restore if your SBC or microSD card fails.

6. SSTV and Digital Mode Archiving

Store and organize:

• SSTV images
• JS8Call messages
• FT8/FT4 decoded logs
• Signal reports and waterfall screenshots

Add tags or naming conventions for contests, satellite passes, or unusual propagation events.

7. Emergency Communications (EmComm)

Prepare for EmComm deployments by:

• Preloading maps, ICS forms, and software installers.
• Hosting offline resources (e.g., Wikipedia snapshot, repeater directory).
• Synchronizing field logs to your home NAS when the network comes online.

Choosing the Right NAS Setup

Pro tip: Use a UPS (Uninterruptible Power Supply) with your NAS to avoid data corruption during power outages—especially during storms or field deployments.

Real-World Ham Use: Example Scenario

Imagine this:

• You’re operating remote HF from your home, using a Raspberry Pi to control a rig via Hamlib.
• The Pi is running WSJT-X for FT8.
• Logs are automatically pushed to your NAS.
• You’ve configured your NAS to back up these logs to a cloud provider weekly.
• You also run Node-RED dashboards on the NAS to monitor temperature, power, and SWR sensors remotely.

This setup gives you flexibility, reliability, and peace of mind—all using open-source tools and amateur radio creativity.

Getting Started

1. Reuse an old PC or get a Raspberry Pi 4 with a USB drive.
2. Choose your NAS OS (TrueNAS, OpenMediaVault, etc.).
3. Connect it to your local network via Ethernet.
4. Enable services like SMB/NFS, Docker, and snapshots.
5. Start saving, sharing, and serving your ham shack data like a pro.

Final Thoughts

In 2025, the amateur radio shack is no longer just radios and antennas—it’s also data, software, and services. By adding a NAS to your setup, you gain control, resilience, and smarter station management.

Whether you’re a contester, experimenter, satellite operator, or EmComm volunteer, a NAS is an investment that pays off in convenience, security, and scalability.

Stay curious, stay connected, and happy experimenting!

The post How Amateur Radio Operators Can Use a NAS in the Shack: A Practical Guide appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Wavelog is a self-hosted PHP application designed for amateur radio operators to log their contacts efficiently. It is an enhanced fork of Cloudlog by 2M0SQL and provides a web-based interface that allows logging QSOs from anywhere with an internet connection. Wavelog supports integrations with various online services such as ClubLog, QRZ, eQSL, HRDLog, and LotW. It is built using CodeIgniter 3 and Bootstrap 5, making it a lightweight yet powerful solution for ham radio enthusiasts.

One of Wavelog’s key features is its compatibility with a Docker-based deployment, which simplifies installation and management. By running Wavelog in a Docker container, users can ensure a consistent and portable environment without worrying about dependency conflicts.

This guide will walk you through the steps to install Wavelog using Docker on a Linux-based system.

Prerequisites

Before proceeding, ensure that you have the following installed on your system:

• A Linux-based operating system (Debian, Ubuntu, CentOS, etc.)
• Docker and Docker Compose installed
• A stable internet connection

Step 1: Install Docker and Docker Compose

If Docker is not already installed, you can install it using the following commands:

sudo apt update
sudo apt install docker.io docker-compose-plugin -y

Enable and start the Docker service:

sudo systemctl enable --now docker

Verify the installation:

docker --version
docker compose version

Step 2: Create a Docker Compose File

Create a directory for Wavelog and navigate into it:

mkdir ~/wavelog && cd ~/wavelog

Create a new docker-compose.yml file:

nano docker-compose.yml

Copy and paste the following content into the file:

services:
  wavelog-db:
    image: mariadb:11.3
    container_name: wavelog-db
    environment:
      MARIADB_RANDOM_ROOT_PASSWORD: yes
      MARIADB_DATABASE: wavelog
      MARIADB_USER: wavelog
      MARIADB_PASSWORD: wavelog # <- Insert a strong password here
    volumes:
      - wavelog-dbdata:/var/lib/mysql
    restart: unless-stopped

  wavelog-main:
    container_name: wavelog-main
    image: ghcr.io/wavelog/wavelog:latest
    depends_on:
      - wavelog-db
    environment:
      CI_ENV: docker
    volumes:
      - wavelog-config:/var/www/html/application/config/docker
      - wavelog-uploads:/var/www/html/uploads
      - wavelog-userdata:/var/www/html/userdata
    ports:
      - "8086:80"
    restart: unless-stopped

volumes:
  wavelog-dbdata:
  wavelog-uploads:
  wavelog-userdata:
  wavelog-config:

Save and exit (CTRL+X, then Y, then ENTER).

Step 3: Start Wavelog

Run the following command to start Wavelog:

docker compose up -d

This will pull the required images and start the Wavelog instance. To verify that the containers are running, use:

docker ps

Step 4: Access Wavelog

Once the setup is complete, open your web browser and navigate to:

http://localhost:8086

If you are running this on a remote server, replace localhost with the server’s IP address.

Follow the on-screen setup instructions and use the database credentials specified in docker-compose.yml:

• Database Host: wavelog-db
• Database Name: wavelog
• Username: wavelog
• Password: (use the value set in MARIADB_PASSWORD)

Step 5: Configure Reverse Proxy (Optional)

If you are hosting Wavelog on a server and want to access it using a domain name, configure an Nginx reverse proxy. Below is an example Nginx configuration:

server {
    listen 80;
    server_name wavelog.example.com;
    location / {
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_pass http://localhost:8086;
    }
}

Restart Nginx after applying the configuration:

sudo systemctl restart nginx

Step 6: Updating Wavelog

To update Wavelog, follow these steps:

docker compose down
docker pull ghcr.io/wavelog/wavelog:latest
docker compose up -d

This will pull the latest version and restart Wavelog with the new image.

Troubleshooting

Check logs for any issues:

docker logs --follow wavelog-main

If you need to increase logging details, edit config.php inside the Wavelog configuration volume.

Conclusion

By following these steps, you have successfully set up Wavelog using Docker for logging amateur radio contacts. This setup ensures a stable and scalable environment while simplifying updates and maintenance. Enjoy using Wavelog for your QSO logging needs!

For more information, visit https://github.com/wavelog/wavelog.

The post How to Install Wavelog Using Docker for Amateur Radio Logging appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

As a ham radio operator, keeping track of your contacts is essential not just for record-keeping but also for award tracking, QSL card management, and participation in the broader amateur radio community. While many logging options exist, YFKlog stands out as a feature-rich solution specifically designed for Linux and Unix systems.

What is YFKlog?

YFKlog is an open-source ham radio logbook program that runs in a terminal interface. Created by Fabian Kurz (DJ5CW, formerly DJ1YFK), this program combines powerful database capabilities with an efficient interface that works well even over SSH connections. While it may not have the flashy graphics of some Windows alternatives, it offers robust functionality that serious operators appreciate.

Key Features

Flexible Database Options

YFKlog supports both SQLite (perfect for individual operators) and MySQL (ideal for club stations or those who already run MySQL). SQLite is particularly convenient as it stores your entire log in a single file, making backups trivial.

Comprehensive QSO Management

• Quick logging: Efficiently enter QSOs with smart tab ordering and field defaults
• Powerful search: Find contacts by any combination of criteria
• Previous QSO display: Instantly see your history with a station as you log them

QSL Card Handling

One of YFKlog’s standout features is its QSL management:

• QSL queuing: Mark cards for sending later
• Batch processing: Print QSL labels in various formats (via LaTeX/PDF)
• Easy receiving: Quickly mark received QSL cards and optionally queue return cards

Awards Tracking

YFKlog automatically calculates your progress toward popular awards:

• DXCC (with band breakdowns)
• WPX (Worked All Prefixes)
• WAZ (CQ Zones)
• IOTA (Islands On The Air)
• WAS (Worked All States)
• VUCC (VHF/UHF Century Club)
• Custom awards using a flexible tagging system

Additional Capabilities

• ADIF import/export: Exchange data with other logging programs
• LoTW integration: Upload and download from ARRL’s Logbook of The World
• Rig control: Interface with your transceiver via hamlib
• DX cluster/bandmap: Monitor DX spots while logging
• Club membership tracking: See if a station belongs to clubs like HSC, FOC, etc.
• Remote logging: Receive QSO data from digital mode programs like fldigi

Getting Started

Installation

On Debian/Ubuntu systems, installation is straightforward:

# Install dependencies
sudo apt-get install perl libdbd-sqlite3-perl libclass-dbi-sqlite-perl make libsqlite3-0 libcurses-perl libwww-perl libnet-telnet-perl libio-socket-timeout-perl

# For LoTW integration
sudo apt-get install trustedqsl xvfb

# Install YFKlog
git clone https://git.fkurz.net/dj1yfk/yfklog.git
cd yfklog
sudo make install

After installation, simply run yfk to launch the program. On first run, it creates a configuration directory (~/.yfklog/) and walks you through initial setup.

Configuration

The most important settings to configure include:

• Your callsign
• Database preferences (SQLite recommended for most users)
• Default band, mode, and power settings
• QSL handling preferences
• Your station coordinates for distance/bearing calculations

Most settings can be changed either through the setup menu or by editing ~/.yfklog/config directly.

Daily Use Workflow

Here’s how a typical logging session might look:

1. Start YFKlog by typing yfk in your terminal
2. Enter the logging mode from the main menu
3. Type a callsign – YFKlog will show:
   • DXCC information
   • Previous QSOs with this station
   • Beam heading and distance
   • Any club memberships
4. Fill in signal reports and other details (many fields auto-populate)
5. Press F2 to save the QSO
6. Continue logging

Advanced Tips

Managing Multiple Logs

YFKlog lets you maintain separate logs for different callsigns. This is perfect for operators with multiple calls or club stations that share a computer.

QSL Card Production

When it’s time to send QSL cards, YFKlog can generate professional-looking labels formatted for common label sheets. The system tracks which QSOs need cards, avoiding duplicates and ensuring you never miss confirming a contact.

Backup Strategy

Regular backups are essential! For SQLite users, it’s as simple as:

sqlite3 ~/.yfklog/YFKlog '.dump' | gzip -c > logbook_backup.sql.gz

This creates a compressed SQL file that can fully restore your database if needed.

Conclusion

YFKlog may not be as flashy as some Windows logging programs, but its efficient interface, powerful features, and Linux compatibility make it an excellent choice for many ham operators. Its text-based interface works perfectly over SSH connections, allowing remote operation from any device.

Whether you’re a contester who needs rapid logging, a DXer tracking DXCC status across multiple bands, or just a casual operator wanting to keep good records, YFKlog delivers the functionality you need without unnecessary complexity.

The program continues to be actively maintained, with new features like the bandmap added in recent versions. For Linux-using ham radio operators, it’s definitely worth a look!

Visit https://fkurz.net/ham/yfklog/doc/

The post YFKlog: A Powerful Ham Radio Logging Tool for Linux appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

As amateur radio enthusiasts, we’re always on the lookout for software that can enhance our operating experience. Today, I want to introduce you to QLog, a powerful open-source logging application that’s been gaining popularity in the ham radio community.

What is QLog?

QLog is a feature-rich amateur radio logging application available for Linux and Windows platforms (with experimental MacOS support for developers). Built on the Qt framework with an SQLite database backend, QLog strikes an impressive balance between simplicity and functionality.

The philosophy behind QLog is straightforward: be as simple as possible while providing all the essential features operators need. While it’s not primarily focused on contests, it does offer basic contest support among its many capabilities.

Key Features That Stand Out

QLog comes packed with features that make it a compelling choice for radio operators:

Station Integration

• Rig Control: Supports multiple interfaces including Hamlib, Omnirig v1 & v2 (Windows only), and TCI
• Rotator Control: Works with Hamlib and PSTRotator
• CW Keyer Support: Compatible with CWDaemon, FLDigi (all modes), Morse Over CAT, and WinKey V2 hardware

Online Services

• Callbook Integration: Connects with HamQTH and QRZ.com
• DX Cluster Integration: Stay updated on DX stations
• QSL Services: Integrates with LoTW, eQSL (including QSL pictures download), QRZ.com, Clublog, HRDLog.net, and ON4KST Chat
• Secure Password Storage: For all services with password or security token protection

Operating Features

• Customizable GUI: Adapt the interface to your preferences
• Online and Offline Maps: Visualize your contacts
• Club Member Lookup: Quickly identify fellow club members
• Bandmap and CW Console: Enhanced operating tools
• WSJT-X Integration: Seamless operation with digital modes
• Station Location Profiles: Support for multiple operating locations
• Various Statistics: Track your operating achievements
• Basic Awards Support: Keep tabs on your award progress

One of the most refreshing aspects of QLog is its commitment to user privacy and freedom. There are NO ads, NO user tracking, and NO hidden telemetry—it’s simply free and open-source.

Platform Support

QLog runs well on:

• Linux (with packages available for Ubuntu, Fedora, and as a Flatpak)
• Windows 10 (64-bit)
• MacOS (experimental support for developers)

The application supports a wide range of radio equipment through its compatibility with Hamlib, Omnirig, and TCI interfaces, making it versatile enough for most ham shacks.

Getting Started with QLog

For Linux Users

Ubuntu users can install QLog through the dedicated PPA:

sudo add-apt-repository ppa:foldyna/qlog
sudo apt update
sudo apt install qlog

Fedora users can download RPM packages from GitHub Releases, and a Flatpak package (which includes built-in TrustedQSL) is available via Flathub.

For Windows Users

Windows users need to install:

• Trusted QSL (optional)
• Omnirig v1 (optional)
• Omnirig v2 (optional)

The installation package is available through GitHub Releases.

My Experience with QLog

What I particularly appreciate about QLog is its clean, uncluttered interface combined with powerful features. The SQLite backend ensures your logging data is stored efficiently and can be backed up easily.

The integration with online services like LoTW and eQSL has streamlined my QSLing process, while the rig control features mean I spend less time manually entering frequency and mode information.

Final Thoughts

Whether you’re new to amateur radio logging or looking to switch from another application, QLog deserves your consideration. Its combination of simplicity, features, and open-source philosophy makes it a valuable tool for any ham radio operator.

QLog is actively maintained, with regular updates and a responsive community. If you encounter issues or have suggestions, you can report them through QLog Issues or join the QLog mailing list.

Give QLog a try—I think you’ll be impressed by what this free, open-source logging application has to offer to the amateur radio community.

Visit https://github.com/foldynl/QLog

QLog is licensed under the GNU General Public License v3.0. The project was started by Thomas Gatzweiler in 2020 and is currently maintained by Ladislav Foldyna (2021-2025).

The post QLog: A Comprehensive Amateur Radio Logging Application for the Modern Ham appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.