PZTLog came about because I wanted an easy-to-use logging application with
simple/quick entry of various QSO fields plus some form of export of data
so that I can display it on my website as text and GoogleMaps. This
project evolved from an earlier attempt at a logging program called
MiniLog which was abandoned after I lost interest in the hobby in late
2009. Fast-forward to the start of 2012... When I started operating again,
I immediately found that several of the popular logging applications
available didn't suit my needs or my operating preferences - My Mother
always told me that I was a bit "different"...!
Whether you want a simple QSO logger for the odd bit of HF DX or VHF
"square-bashing", or an everyday logger with Stats, PSK/RTTY modes, eQSL
uploading and simple Contest dupe/serial-number integration - PZTLog may
be just what you're looking for...
So - What Does It Do? It serves as a general-purpose logger (whether live or typing-up
later) for ragchews as well as helping me
keep track of contest QSOs on HF/VHF. Over the past few months, I have added additional features such as: PSK/RTTY Datamodes,
QRZ.com XML lookup, GoogleMaps KML output (eg: display QSOs in Google
export, eQSL upload, DX Spot database with
archive facility, CQ Voice Keyer, Contest "dupe-checking" and more.
The software can run over a network, such as a multiband contest with a
shared log and dupe/new-band alerts.
There are 2 "modes" that you
can run PZTLog in: Full Mode offers a single-window
with all of the
log/cluster/datamode functions whilst Simple Mode offers a "windows" feature
with a low-profile logger and optional Datamodes, DX Cluster and Log Viewer
windows which can be moved/sized accordingly.
What it doesn't do : It doesn't calculate points per QSO/State/Km...
It doesn't handle LoTW nor does it
control your rotator...
Logging without the fuss Small GUI, basic QSO-entry fields and
ideal for netbooks/laptops "in the field"
Flexi-Input of QSO Data - in almost
any order you like! Enter Callsign, RST-Sent, RST-Received, QRA Locator, IOTA/WAB,
CQ/ITU Zone and
the same textbox and PZTLog will place it in the correct field for you -
No more tabbing to find the relevant textbox! Here's the simple
process of logging a QSO using PZTLog.
In the Flexi-Input textbox, type
57S <enter> (this is the signal report you gave him)
59 <enter> (he gave you 5 and 9)
N BOB <enter>
Q LONDON <enter>
FT-450D, G5RV AT 50FT# <enter>
All of the above fields will be placed in the correct textboxes - You can
save the QSO by pressing <enter> (with no text in the box) or by pressing
the F5 key.
QRZ.com XML Lookup With a subscription to QRZ, you can look-up the Name, City, Locator
Square, IOTA and State when entering a Callsign in either the Logbook Entry or QSO Edit
Cluster via Telnet and DX Spot Archive Keep an eye on the latest DX spots, and filter via the band/s you are
interested in. A DX Spot archive is now created within the
DXSpots.mdb file - this is used to keep a list of previous DX Spots.
A new DX Spot review window allows you to easily edit a DX Spot prior to
Contest-friendly You can tell PZTLog to only commit a QSO to the Logbook once a Locator
and/or Serial Number has been entered. The current Serial Exchange
is shown in large text for easy viewing. A "dupe" alert is also
shown if configured. There is no system in place for calculating
points or exporting to Cabrillo at this time.
Datamodes : PSK and RTTY Using the MMVari engine (which is also used in
N1MM), you can operate PSK/RTTY - A waterfall display, TX/RX window plus QSO Macros are available
and make PZTLog great for casual (not to mention contest) datamode
operating. With built-in PSK/RTTY, CQ Voice-Keyer and PTT control -
you can easily switch between data+phone without having to fiddle with
cables, buttons or settings on the radio! Double-click received text
to set Callsign, Locator, RST/Serial, Name/QTH etc - great for a face-pased
RTTY contest or PSK QSOs
CAT Control via OmniRig Using the excellent OmniRig software, you can display frequency/band
data as well as set the frequency from PZTLog - You can also control the
PTT using the F12 key. Change bands, toggle your internal-ATU, set
filtering and IF Shift, change menu items (eg: TX-BW on FT-950).
needs to be downloaded and installed from this website
Networkable Multiple PZTLog workstations can be linked to use a shared logbook
Log Window Displays the QSOs in the log database for easy look-up as well as
"have we worked before" and "new locator square" etc.
When a callsign is entered in Full Mode, PZTLog will revert the Log
display to show all previous QSOs with that station - and, in the case of
Contest operating, will alert you to a "dupe". It also
shows you DXCC data so if you hear a callsign and can't remember the
Country it belongs to, just type 3 (or more) characters and PZTLog will
Distance and Bearing Calculator
When using QRA Locators, PZTLog will give you distance (in
miles+kilometres) plus bearing for the
target locator square - For QSOs that have a QRA Locator Square logged,
you can filter via band (or other search result) to find the "Best DX" -
Voice Keyer and CW Keyer Play up to 4 MP3/WAV file CQ messages with PTT keying via COM port -
this requires an opto-isolator for PTT switching, eg: a "soundcard"
interface as used with AGW/PSK31/WSPR etc. A new CW Keyer using the
CWType API can be
used to send CW - great for quick CW QSOs. Basic Macros for CW are supported.
eQSL Upload Each QSO, when saved, can be automatically uploaded to eQSL either
from PZTLog or via PZTFTP as part of the usual logbook FTP upload process.
You can also manually upload to eQSL with a single click via the Edit
Export to ADIF/eQSL, CSV,
GoogleMaps KML, Text You can export your Logbook Database to a ADIF/eQSL, CSV or simple Tabbed Text
File. You can also export to GoogleMaps KML for
plotting of worked stations on a map (uploaded to your webspace via PZTFTP). There
is also a basic ADIF import routine so you can easily upload the exported ADIF file to
JT65-HF Traffic Window You can display the CSV file from the JT65-HF software and easily add
QSOs to PZTLog but double-clicking the exchanges. The HB9HQX build
of JT65-HF is also supported but not the most recent versions as he's
changed the log-file format - I need to fix that (or keep using the old
Despite the variety of features, PZTLog is easy-to-use and great
for Club-events as an alternative to paper logging. The Flexi-Input
allows for rapid-entry of QSO details so great for single-op working or
even the non-computer-literate! You are given Logbook Entry, LogView, DX Cluster
and Datamodes in a single window. A separate Log Viewer window is
also available. This caters for most
requirements, screen resolutions as well as operating preferences.
As I operate /P a fair bit
during the warmer months and dislike using a paper logbook - I wrote
a very simple logging application for the Android OS called
tabLog. It outputs an
ADIF file so can easily import into PZTLog, Ham Radio Deluxe etc.
PZTLog Downloads This software is free to use and offered here on the basis that you may find
it useful. It was designed as a logging program purely for my own needs
and operating methods.
Please note that this is a Windows application and I work exclusively in
Microsoft Windows - If you're running Linux or a Mac, I can't help you.
The software works best when installed to C:\PZTLog
If upgrading from an existing install of PZTLog, you are advised to
keep a spare copy of your PZTLog.exe , PZTLog.ini (settings) and Log.mdb
Download PZTLog v1.22 Setup.exe
[updated 20th May 2015]
This is the full-installer for first-time users - Simply run the installer (as
Administrator) and enjoy. Existing users can just use the Update Zip (below)
and put the latest files into their program folder. You can also run this installer over the top of an existing install without
loss of any data/settings.
Download PZTLog v1.22 Update ZIP
[updated 20th May 2015]
This contains the latest EXE, Help File and DXCC Prefix Database for existing users - You MUST have an
existing installation to use these files. Simply unzip and replace your
existing files with those in this archive. Please refer to the Help
File for a detailed list of changes/fixes...