一款为 HAM 打造的开源业余无线电台日志管理系统简介 HamLog 是一款面向业余无线电爱好者（HAM）开发的本地电子日志管理软件，使用 Python + PyQt6 + SQLite3 构建，遵循 GPL-3.0 开源协议。无论你是刚入门的爱好者还是资深火腿，HamLog 都能帮助你高效管理 QSO 日志、追踪 QSL 卡片收发状态。功能状态 📝 QSO 日志录入支持呼号、频率、模式、功率、RST 报告等完整字段 🔍 智能搜索支持按呼号、QTH、设备、备注模糊搜索 📊 实时统计总通联数、今日通联数实时显示 🎴 QSL 卡片管理记录收发日期，追踪卡片状态 ⚙️ 本台信息配置呼号、姓名、QTH、网格定位等个性化设置 🌓 深色/浅色主题一键切换，适配不同使用环境 💾 数据本地存储所有数据保存在本地 SQLite 数据库，隐私安全 📤 数据导出 ADIF / CSV 格式导出（开发中） 🖼️ 界面预览 HamLog 主界面 [upl-image-preview uuid=24853a98-98a1-40cd-ad8b-962b60fda446 url=https://storage.hamcq.cn/2026-06-16/1781652666-460259-main-window.png alt={TEXT?}] 深色主题下的主界面，包含呼号信息栏、实时时钟、搜索工具和日志表格 🚀 快速开始环境要求操作系统：Windows 10 / 11 (x64) Python：3.7 或更高版本依赖库：PyQt6, SQLite3 安装运行 # 克隆仓库 git clone https://github.com/ARPRC-BA8AQA/HamLog.git cd HamLog # 安装依赖 pip install PyQt6 # 运行程序 python "HAMLOG GUI.py" 打包为可执行文件 pip install pyinstaller pyinstaller --onefile --windowed "HAMLOG GUI.py" 📁 项目结构 HamLog/ ├── programs #源码文件夹 ├── version #对应版本文件夹 ├── HAMLOG GUI.py # 主程序（PyQt6 GUI） ├── AutoDeal.py # 后端模块（数据库、校验、设置管理） ├── Log.db # 本地 SQLite 数据库（运行时生成） ├── screenshots/ # 界面截图 ├── LICENSE # GPL-3.0 许可证 └── README.md # 本文件 🗄️ 数据库说明 HamLog 使用 SQLite 本地数据库，默认存储路径：系统路径 Windows %APPDATA%\HamLog\Log.db macOS ~/Library/Application Support/HamLog/Log.db Linux ~/.local/share/HamLog/Log.db ⚠️ 建议定期备份 Log.db 文件，以防数据丢失！数据库字段字段说明 Callsign 对方呼号 Freq 频率 Year/Month/Day 通联日期 Time 通联时间 (HHMM) Mode 模式 (FM/SSB/CW/FT8 等) Power_self 我的功率 Power_side 对方功率 Rst_self 对方给我的报告 Rst_side 我给对方的报告 QTH 通联地点 Device 使用设备 QSL_RX 收到 QSL 日期 QSL_SEND 发出 QSL 日期 Remarks 备注 🤝 参与贡献我们欢迎所有 HAM 和开发者的贡献！如何贡献 Fork 本仓库个性化更改提交更改并推送至Dev分支打开 Pull Request 提交 Issue 发现 Bug 或有新功能建议？欢迎提交 Issue！ 📜 开源协议本项目遵循 GNU General Public License v3.0 开源协议。 HamLog - 业余无线电台日志管理系统 Copyright (C) 2026 BA8AQA, BG5JQN 及所有贡献者本程序是自由软件：你可以再发布本软件和/或修改本软件，只要你遵守 GNU 通用公共许可证（GPL）第 3 版或（按你的决定）任何以后版本。本程序是希望它能有用而发布的，但没有任何担保或特定用途适用性的隐含担保；甚至没有适销性。详情请参阅 GNU 通用公共许可证。 🙏 致谢特别感谢以下人员与组织对 HamLog 开发的支持： BA8AQA — 项目发起人与核心开发 BG5JQN — 核心开发所有提交 Issue 和 PR 的 HAM 贡献者开源社区提供的优秀工具与库 📬 联系我们平台链接 GitHub ARPRC-BA8AQA/HamLog Bilibili @C盘研究所-中国_BA8AQA 73 de BA8AQA & BG5JQN 🎙️ 愿电波永不消逝，友谊长存空中

@"BA8AQA"#p97779 HamLog的第1个版本--Alpha1，已于昨日正式发布，Github:https://github.com/ARPRC-BA8AQA/HamLog

好像还不支持使用adi文件进行日志导入？

@"BD1CAZ"#p97782 之前有，只是现在重构了，ADIF相关功能预计会在下一个大版本更新

挺好的，虽然这年头日志软件已经很多了，但有新软件总是好的hhh 不过 hamlog 的名字已经有好几个在用的了，俄国 ham 爱用的 hamlog.online、日本 ham 爱用的 Turbo Hamlog……

提几点结构上的建议: + 版本分隔建议使用 **标签** (*Tag*) 和 **分支** (*branch*), 而不是文件夹 *versions* + 仓库中的文档, 除有特殊需求, 尽量使用 **markdown** 而不是 *office doc* + 仓库结构可以是下面这样, 更清晰明了 - 展示 (README, LICENSE, screenshots/) - 源码 (src/) - 文档 (doc/) 再提几点发布上的建议: + 可以尝试使用 **Github Actions** 配置自动化工作流进行软件打包，这样 1. 不用自己手动打包了 2. 不怕把自己私人环境的东西包进去 3. 统一的, 可复现的构建环境 + 使用 **语义化版本控制规范** 可以让版本号管理更清晰再来一点开发上的建议: + 可以生成 `requirements.txt` 方便用户一键安装依赖 + 尽量不要 **在一个文件里面写全部代码** (*All in one file*), 而是分 **模块** (*module*) --- 以上为个人看法, 楼主可以参考. 祝开发顺利, 73

@"BI1GHZ"#p97802 这两个Hamlog还各自有个QSL系统叫hQSL🤣

数据库字段似乎还是比较少的，可能并不能覆盖很多场景的记录需求。一个建议是参考 ADIF 规范中的字段。可以参考一些现有的日志系统，来更好地规划未来的feature。

下面的话可能有点重，无意冒犯，如有不快，敬请谅解：下载试用了一下，第一件事就是录入一个短波FT8通联数据，再录一个卫星通联数据，于是立马出问题了😂，正如我在[过去某一篇帖子所讲](https://forum.hamcq.cn/d/8048/17)： > 观察论坛里很多台友开发的日志软件，共同点是都在针对 UV 语音通联，而且很多并非因为 “看到了差异点” 而主动选择 UV，而是他们只知道 UV 通联，设计上只考虑了 UV，几乎没考虑其他场景，等玩过短波、卫星、盒子或打比赛的人来操作，就会发现各种问题了。 > 实际上通用的日志软件或网站很多，像 WaveLog、QRZ 之类的，特定场景像比赛有专门的 N1MM，FT8 有专门的 WSJT-X 和 JTDX，他们都是沉淀多年的 “行业巨头”，有日志需求的场景，特别是需要去 LoTW 确认的场景，像短波通联、打比赛，HAM 大概率会选择这些 “巨头”，而不是台友开发的 UV 软件。 > 那么个人开发的东西如何真的发挥价值呢？一定要找到 “行业巨头” 的盲区。因此如果继续增加功能时，需要先思考几个问题： 1. 我的软件是为了什么？为了编程练习？为了自己用着顺手，顺便给台友用？专门给台友用的？ 2. 我的软件想覆盖哪个场景？各种通联模式吗？ 3. 每种通联模式有什么特点？有哪些必要和不必要的信息项？我的界面是否需要以及如何进行针对性设计？ 4. 在记日志时，有没有碰到什么麻烦事？程序能不能帮忙解决这个麻烦？现在收发快递都能根据一段文字自动提取省市区联系人和电话了，日志能不能也参考一下，哪怕是格式相对固定一些，让大家录入信息时候方便些？（现在有AI了，这种枯燥的文字解析工作可以扔给AI来干） 5. 再举个具体案例，有些台友并不是通完一次就发一下QSL卡片，那太麻烦，而是攒一批一块处理，能不能考虑批量处理场景？ 6. ADIF导入/导出、兼容性？另外扒一扒论坛里各种自制日志软件，以及我的以往评论，供楼主参考： * [非常非常非常简易的点名记录软件](https://forum.hamcq.cn/d/8048)（[个人评论](https://forum.hamcq.cn/d/8048/16)）：亮点在于找到了“主控”这个差异化场景，把“程序员思维”磨一磨立刻就成为了利器 * [目前做了个 homo_qso 想问问各路大佬意见](https://forum.hamcq.cn/d/8100)（[个人评论](https://forum.hamcq.cn/d/8100/3)）：虽然没完工，但是如果能把卫星通联这个场景做好，也可以封神 * [野外通联日志难记？我是这样解决的](https://forum.hamcq.cn/d/8071)（[个人评论](https://forum.hamcq.cn/d/8071/17)）：同上，做好卫星通联语音识别的话也可以封神 * [HamTool 公测版发布，一款用于管理通联日志和打印卡片的工具，欢迎提出宝贵意见！](https://forum.hamcq.cn/d/935)：亮点在于能够批量管理和打印QSL卡片。通联卡片多了，用起来很方便 * [集日志记录、收 / 发卡、日志上传全周期的在线表格](https://forum.hamcq.cn/d/6776)：亮点在于使用在线表格，这个点子不错 * [写的通联日志记录界面 (H5)，求锐评](https://forum.hamcq.cn/d/6252)：针对其界面设计和人机交互提出了[个人评论](https://forum.hamcq.cn/d/2295/1182) * [我的 HAM HOME 小程序史诗级大更新……](https://forum.hamcq.cn/d/8126) * [业余无线电台通联日志电子版](https://forum.hamcq.cn/d/7581) * [我自己做的业余无线电通联日志记录软件](https://forum.hamcq.cn/d/6724) * [EasyQSO iOS 通联日志 App 正式开源](https://forum.hamcq.cn/d/6569) * [国内专业的通联日志记录网站，欢迎注册使用](https://forum.hamcq.cn/d/3909)

又要翻炒出来了（ [upl-image-preview uuid=774c1016-8cc0-41f3-83f3-69a02aa62d37 url=https://storage.hamcq.cn/2026-06-18/1781783337-408596-image.png alt={TEXT?}] [upl-image-preview uuid=987abc41-c0af-40f3-bc89-e0371f38c54d url=https://storage.hamcq.cn/2026-06-18/1781783351-624214-image.png alt={TEXT?}] [upl-image-preview uuid=4bc491ba-7449-4ab4-9751-01fd2711965b url=https://storage.hamcq.cn/2026-06-18/1781783362-187824-image.png alt={TEXT?}] 然后之前重构了一版web版的还没有实际投入部署（ https://github.com/BH2VSQ/QSLCard-Manager https://github.com/BH2VSQ/QSLCard-Manager-PYV

HamLog Amateur Radio Station Log Management System

BA8AQA

An open-source amateur radio log management system designed for HAMs.
Introduction
HamLog is a software designed for amateur radio enthusiasts.（HAM）Developed a local electronic log management software, built using Python + PyQt6 + SQLite3, and adhering to the GPL-3.0 open source license.

Whether you are a beginner or an experienced ham radio operator, HamLog can help you efficiently manage your QSO logs and track the status of your QSL cards.

Function | Status
📝 QSO Log Entry Support: Supports complete fields such as call sign, frequency, mode, power, RST report, etc.
🔍 Smart Search: Supports fuzzy searches by call sign, QTH (location), device, and notes.
📊 Real-time statistics: Total connections and current daily connection count displayed in real time.
🎴 QSL card management: Record receipt and sending dates, track card status.
⚙️ Customizable information settings: call sign, name, location (QTH), grid coordinates, etc.
🌓 Dark/Light Theme: One-click switching, adapts to different usage environments.
💾 Data local storage: All data is stored locally in an SQLite database, ensuring privacy and security.
📤 Data Export: ADIF/CSV format export (in development)
🖼Interface preview
HamLog main interface

The main interface under a dark theme includes an information bar for call signs, a real-time clock, a search tool, and a log table.

🚀 Quick Start
Environmental requirements
Operating System: Windows 10 / 11 (x64)
Python: Version 3.7 or higher
Dependencies: PyQt6, SQLite3
Installation and operation

Clone repository

git clone https://github.com/ARPRC-BA8AQA/HamLog.git
cd HamLog

Install dependencies

Install PyQt6 using pip: `pip install PyQt6`

Run the program

python "HAMLOG GUI.py"
Package as an executable file
pip install pyinstaller
pyinstaller --onefile --windowed "HAMLOG GUI.py"
📁 Project Structure
HamLog/
├── programs # Source code folder
├── version # Version folder
├── HAMLOG GUI.py # Main program (PyQt6 GUI)
├── AutoDeal.py # Backend module (database, validation, settings management)
├── Log.db # Local SQLite database (generated at runtime)
├── screenshots/ # Screenshots of the interface
├── LICENSE # GPL-3.0 License
└── README.md # This file
🗄Database Description
HamLog uses an SQLite local database with a default storage path of:

System Path
Windows: %APPDATA%\HamLog\Log.db
macOS: ~/Library/Application Support/HamLog/Log.db
Linux ~/.local/share/HamLog/Log.db
⚠️ We recommend regularly backing up the Log.db file to prevent data loss!

Database field
Field | Description
Callsign Opposing callsign
Frequency
Year/Month/Day Date (according to Tonglian)
Time Communication Time (HHMM)
Mode (FM/SSB/CW/FT8, etc.)
Power_self My power
Power side Opponent's power
Rst_self The report provided by the other party
Rst_side The report I prepared for them
QTH: Location
Device Equipment used
QSL_RX Received date of QSL
QSL_SEND Date of sending QSL
Remarks Notes
🤝 Contribute
We welcome contributions from all HAMs and developers!

How to contribute
Clone this repository
Personalized customization
Submit changes and push to the Dev branch.
Open the Pull Request

Submit an issue
Found a bug or have a suggestion for new features? We welcome your contributions!

📜 Open-source license
This project adheres to the GNU General Public License v3.0 open-source license.

HamLog - Amateur Radio Station Log Management System
Copyright (C) 2026 BA8AQA, BG5JQN and all contributors

This software is free software: you are allowed to redistribute it and/or modify it.
As long as you comply with the GNU General Public License.（GPL）Version 3 or any subsequent version (as you decide).

This program is released with the hope that it will be useful, but without any warranty or guarantee.
Implied warranties of suitability for specific purposes; even without merchantability. See the GNU General Public License for details.
🙏 Acknowledgments
We would like to express our sincere gratitude to the following individuals and organizations for their support of the development of HamLog:

BA8AQA – Project initiator and core developer
BG5JQN — Core Development
All contributors to HAM who have submitted issues and pull requests.
Excellent tools and libraries provided by the open-source community.
📬 Contact us
Platform Link
GitHub ARPRC-BA8AQA/HamLog
Bilibili @C盘研究所 - China_BA8AQA
73 from BA8AQA & BG5JQN 🎙️
May the radio waves never fade away, and may friendship endure in the air.

BA8AQA

BA8AQA The first version of HamLog, Alpha1, was officially released yesterday. Github:https://github.com/ARPRC-BA8AQA/HamLog

BD1CAZ

It seems that it doesn't currently support importing logs using .adi files?

BA8AQA

BD1CAZ Previously, this functionality existed, but it has been refactored. The ADIF-related features are expected to be included in the next major version update.

BI1GHZ

It's great! Although there are many logging software options available these days, having a new one is always welcome.

However, the name "hamlog" is already in use by several other entities, such as the Russian hamlog.online and the Japanese Turbo Hamlog used by ham愛.

BD1CAZ

BI1GHZ These two Hamlogs also have their own QSL systems called hQSL.🤣

BG4QBF

Here are a few structural suggestions:

Recommended version separation method Tags (Tag) and Branch (branch), instead of a folder versions
For documents stored in the warehouse, please use them whenever possible, except when there are specific requirements. markdown Instead of office document
The warehouse structure could be like this, for better clarity.
- Demonstration (README, LICENSE, screenshots/)
- Source code (src/)
- Document (doc/)

Here are a few more suggestions regarding the release:

You can try using GitHub Actions Configure automated workflows for software packaging, so that...
1. No need to manually package it yourself.
2. Don't be afraid to include personal items in your environment.
3. A unified and reproducible build environment
Usage Semantic Version Control Guidelines It allows for clearer version management.

And here are some more suggestions regarding development:

Can be generated requirements.txt Provide users with a one-click installation of dependencies.
Please avoid doing so whenever possible. Write all the code in one file. (Single file), instead of dividing them into Module (module)

The above are my personal opinions; the original poster can refer to them. I wish you all the best in your development efforts. 73

BI1GHZ

The database fields seem to be relatively limited, and may not cover many scenarios' record requirements. A suggestion is to refer to the fields specified in the ADIF specification.

You can refer to some existing logging systems to better plan future features.

BG4IJK

The following may be a bit strong, and I apologize if it causes any offense; please accept my apologies if you are offended.

I downloaded and tried it out. The first thing I did was enter some shortwave FT8 data, followed by satellite communication data. Immediately, I ran into problems.😂As I haveWhat was discussed in a previous post?：

When observing many forum users who have developed logging software, a common characteristic is that they all target UV voice communication. Moreover, many users didn't actively choose UV because they "saw the differences," but rather because they simply knew about UV communication. Their designs primarily considered UV, with little or no consideration for other scenarios like shortwave, satellite, or contest operation. Once experienced users who have used these other modes come to operate the software, various problems are discovered.
In reality, there are many general logging software and websites available, such as WaveLog and QRZ. For specific scenarios like competitions, there are dedicated programs like N1MM for contesting and WSJT-X and JTDX for FT8. These are established "industry leaders" with years of experience, and are likely to be chosen by hams who need logging software, especially when confirming contacts on LoTW, such as for shortwave communication or contests. While UV software developed by amateur radio enthusiasts is also available, it's less common among experienced hams.
So, how can individual developers truly create value? The key is to identify the "blind spots" of industry giants.

Therefore, if we continue to add features, we need to first consider a few questions:

What is the purpose of my software? Is it for programming practice? Or primarily for my own convenience, with a secondary benefit for others? Is it specifically designed for use by others?
What scenarios does my software aim to cover? All communication modes?
What are the characteristics of each communication mode? What information items are necessary and unnecessary? Does my interface need to be designed in a specific way, and if so, how?
When logging, have you encountered any problems? Can the program help solve these issues? Currently, we can automatically extract province, city, and contact information with phone numbers from a text snippet for both sending and receiving packages. Could the logging system also be used in this way, even if the format is relatively fixed? This would make it easier for everyone to enter information. (Now that we have AI, this tedious task of text parsing can be delegated to AI.)
For example, some operators don't send QSL cards after completing a single contact; this is too cumbersome. Could we consider a batch processing scenario?
ADIF import/export, compatibility?

Additionally, I've compiled a list of various self-made logging software available on forums, along with my previous comments, for the OP to review.

An extremely simple and easy-to-use attendance recording software.（Personal review): The key advantage lies in identifying the "core control" scenario, which allows you to quickly leverage "programmer thinking."
I've just implemented a basic `homo_qso` and would like to get your feedback on it.（Personal review): Although it's not yet complete, if we can successfully implement satellite communication, it would be a resounding success.
Having trouble remembering your off-road communication logs? Here's how I solved it.（Personal review): As mentioned above, if satellite communication voice recognition works well, it can truly achieve perfection.
HamTool trial version released, a tool for managing and printing QSL cards. We welcome your valuable feedback!The highlight is the ability to manage and print QSL cards in bulk. It's very convenient when you have a lot of 通联卡片.
An online form that covers all aspects of logging, including receiving/sending cards and uploading logs throughout the entire period.: The highlight is the use of online forms; this is a good idea.
The interface for logging communications with Tonglian. (H5)Please provide a sharp critique.: Regarding its user interface design and human-computer interaction.Personal review
My HAM HOME mini-program has undergone a massive update – truly epic!
Amateur Radio Station Communication Log - Electronic Version
My own amateur radio log keeping software.
EasyQSO iOS Universal Log App officially open-sourced.
A professional domestic log management website. Welcome to register and use it.

BD4UIP

BH2VSQ

It seems like this is being rehashed again.

Then, we had previously rebuilt a version of the web application, but it hadn't yet been deployed in practice.
https://github.com/BH2VSQ/QSLCard-Manager
https://github.com/BH2VSQ/QSLCard-Manager-PYV

闽ICP备2021006864号-7

闽公网安备35020602002794号互联网举报中心

用户协议隐私政策社区规范积分规则中继规则转载须知
更新日志联系我们常见问题友情链接运营报告赞助

浩奇科技（厦门）有限公司

是无线电，把我们联系在一起