Amateur Radio Log Book Exporter

WHAT IT DOES

This script scans amateur radio log book pages—QRZ, Logbook of the World, HamRadioDeluxe, and others—for QSO entries including callsign, date, time, frequency, mode, signal report, and notes. It displays a floating panel showing a summary of the log with total contacts, unique callsigns, bands used, and modes. A one-click export function saves the log as ADIF (Amateur Data Interchange Format), CSV, or plain text. The script captures all QSO fields and includes them in the export. Users can filter contacts by date range, band, or mode before exporting. Export preferences are stored per domain for reuse across visits.

WHERE IT RUNS

Works on any amateur radio log book page—QRZ, Logbook of the World, HamRadioDeluxe, Club Log, or any page displaying QSO entries. The script detects log entries using common patterns like callsigns (AA1AA format), dates, times, frequencies, modes, and signal reports, making it compatible with most logging platforms.

HOW TO USE

The panel appears automatically when you visit a log book page. It detects QSO entries and shows a summary with total contacts, unique callsigns, bands used, and modes. Choose your export format: ADIF (.adi), CSV (.csv), or Plain Text (.txt). Click "Export Log" to download the file. Click "Copy to Clipboard" to copy the formatted content directly. ADIF format is the standard for amateur radio logging software and includes all QSO fields with proper ADIF tags. CSV format is useful for spreadsheets and data analysis. Plain text format provides a human-readable summary. Use "Save Current Settings" to remember your format preference for future visits. The script automatically detects callsigns, dates, times, frequencies, modes, RST reports, names, QTH, and notes.

TECHNICAL MECHANISM: QSO ENTRY DETECTION WITH FIELD PARSING AND MULTI-FORMAT EXPORT

The script uses a multi-pass detection strategy to find QSO entries. It searches for common log entry containers (.log-entry, .qso-entry, .contact, .entry) and falls back to scanning table rows, divs, and list items that contain callsigns. For each entry, it extracts callsigns using a regex pattern that matches amateur radio callsign format (1-2 letters, 1-3 digits, 1-4 letters). Dates are extracted using a date parser that supports MM/DD/YYYY format. Times are extracted from HH:MM patterns. Frequencies are extracted from patterns like "14.250 MHz" or "14.250". Modes are detected from a list of common modes (SSB, CW, FM, AM, FT8, FT4, PSK31, RTTY, etc.). Signal reports (RST) are extracted from 599 or 5NN patterns. Name and QTH are extracted using patterns like "Name: [Name]" and "QTH: [Location]". The ADIF export generates standard ADIF tags for each field: CALL, QSO_DATE, TIME_ON, FREQ, MODE, RST_SENT, RST_RCVD, NAME, QTH, COMMENT. The CSV export generates a header row with all fields. The text export generates a structured human-readable format. Unique callsigns, modes, and bands are calculated from the detected QSOs.

THE PANEL

The log exporter appears in a draggable, resizable panel that remembers its position per site. The panel shows the log summary, format selector, and export buttons. Drag by the header to reposition, collapse to a compact icon with a click, and resize using the bottom-right corner. The panel snaps to screen edges for tidy placement and closes with the Escape key. All settings—format preference and panel position—persist per website using GM_setValue, so your view returns exactly as you left it.

PLEASE NOTE

This script requires the free BotGentz extension to run. The script relies on common log book page structures—if a platform uses a non-standard layout, QSO detection may be incomplete. The date parser currently supports MM/DD/YYYY format; other date formats may not be detected correctly. The mode detection uses a static list of common modes; custom or less common modes may be missed. The ADIF export includes the fields detected; some fields may be empty if not present in the source page. The script does not access your log book account credentials or modify your log data—all data is read from the visible page and exported locally. The script is designed for exporting logs, not for importing or modifying logs on the server.