Import and export
ADIF is the common format of amateur radio logs - it is how you exchange QSOs with other programs and services (POTA, WWFF, QRZ…). This page also covers Cabrillo export, Log4OM and the QSO list for your website.
ADIF import
Menu → Import data from ADIF files (Ctrl+I):
- 1. File - choose the
.adi/.adiffile and the ADIF template. If the file stores the frequency in unusual units, choose them (Hz, kHz, MHz, GHz). Add default template data (Park, Summit etc.) if the original data is empty fills in your program fields. Program references are read from thePOTA_REF,WWFF_REF,SOTA_REF,IOTAfields (andMY_...); older files have onlySIG_INFO- then the program tells which program the reference belongs to bySIG, by the shape of the reference, and finally by the chosen template. - 2. LogBook - the date range (all, today, one day, a range) and the target: Add QSOs to current LogBook or Create new LogBook (the name is generated, you can change it; standard or contest type). Tick Ignore duplicates - QSOs with the same station within 2 minutes and 2 kHz are not added a second time.
- Click Start. The program reports how many QSOs it added and how many it skipped.
You can also open an ADIF file with a double-click in Explorer - after enabling the file association on the Misc configuration page (Associate .adi and .adif files with this program.). The program starts with the import window.
ADIF export
The Export ADIF button in the LogBook window, Menu → Export data to ADIF files or Ctrl+E. The window has three tabs:
| Tab | What to set |
|---|---|
| 1. Range | All dates, Last log date (e.g. the last activation), Today, Single log date, Log date range, Visible rows in my LogBook, e.g. filtered, Selected rows in my LogBook. |
| 2. File | ADIF template (or Use all templates),
Folder, the file name: Constant file name or Dynamic file name with the macros
[#CallSign], [#TemplateName], [#MyProgram] (e.g. your park number), [#Date].
Show example of generated file name shows the result. You can override the date in the file name, and the callsign and
program data in the exported records (the log itself does not change). |
| 3. Options | Removing prefixes and suffixes from callsigns, Remove duplicates, Skip QSO if my program field is empty, Remove USB/LSB from mode - some services require it. |
The files go to a subfolder named after the template in the chosen folder. Show folder in Explorer shows them.
POTA: the POTA template with the dynamic name [#callSign]@[#MyProgram]-[#Date] gives files like
SP4THK@SP-0123-20261024.adi. With several of your parks (comma separated) each park gets its own file.
Export templates
An ADIF template says which fields go into the file. Ready templates: STANDARD, POTA, SOTA, WWFF, LLOTA, IOTA, Field Day, CONTEST and QRZ - they are read-only, but you can duplicate one and change the copy. Manage templates (in the export window or Configure export templates on the Misc page) opens Manage export templates:
- the template list, Add new, Duplicate as new, Delete current, Save current template, Default templates;
- Log type, the frequency unit, Read only;
- the Basic / Advanced switch next to ADIF template.
Removing prefixes and suffixes from callsigns (SP4THK/P → SP4THK) is set in the export window, tab 3. Options.
Basic mode
On the left Available fields in groups (QSO, Contacted station, My station, Contacted station programs, My programs, QSL and uploads, Contest, Satellite and split), on the right Fields in ADIF file. The → arrow (or a double click) adds a field, ← (or a double click on the right) removes it; a selected group and → adds the whole group. The contacted callsign is always in the file. The order of ADIF fields does not matter.
Programs have their own ADIF 3.1.8 fields in the file: POTA_REF, WWFF_REF, SOTA_REF, IOTA
(yours: MY_...). For older programs and pota.app the reference of the program matching the Log type also goes
as SIG / SIG_INFO (STANDARD template - POTA). LLOTA has no ADIF field of its own and uses SIG - if the
log type program already uses it, the window warns that the LLOTA lake will not go into the file.
Advanced mode
The template as text with macros - for fields the basic mode does not have (e.g. own programs Custom 1-5 or a field a particular service requires). Macros are listed in Available macros, a double click inserts one at the cursor.
You can switch between the modes both ways until you change the text by hand. After the first change Basic is disabled (Template changed by hand - advanced mode only) and once saved the template stays advanced. Templates written by hand open in the advanced mode only (Own template - advanced mode only).
Cabrillo
The contest entry format. Cabrillo export is in the End Contest window - see Contests.
Log4OM
On the Misc configuration page:
- Export all logs and LogBooks directly to the Log4OM database - choose the Log4OM database file and the logs to move. QSOs that are already in the database are skipped.
- Import all logs directly from the Log4OM database - into the current or a new LogBook; an option to convert times to UTC (check the dates afterwards) and to skip duplicates.
Back up the Log4OM database and close Log4OM before the operation. The Log4OM functions are not available on computers with an ARM processor.
QSO list for a web page
Menu → Additional Windows → QSO list for web page... creates a table of your QSOs with a callsign search box - to show on your own website.
- 1. Range - as in the export, plus Last QSOs (the last N).
- 2. Columns and templates - which columns and in what order, sorting, Grid locator: first 4 characters only, Anonymize personal data (name, e-mail, QTH) - recommended when you publish the list.
- 3. Export to web page - the mode:
- Separate page (
index.html+style.css+qso.json) - a ready subpage; for later updates it is enough to send the data only (Send data only); - Block to embed - the HTML table only, styled by your own style sheet;
- Standalone HTML to paste - to paste e.g. into the WordPress editor.
- Separate page (
You change the look of the page in mode 1 by editing the templates (Show templates folder, the WWW\TEMPLATES folder).
Files are saved by default in WWW\OUTPUT.
FTP servers
The program can send files to your server: the QSO list for a web page, a zipped copy of LogBooks, the program backup and LogBook synchronization. Each of these functions has its own server - configuration, FTP servers page: select a row, Configure..., and when everything goes to the same server - Copy to others....
- Protocol: Automatic (recommended), FTP, FTPS (explicit or implicit) or SFTP (SSH, port 22).
- Server, Port, Username, Password (or an SSH key),
Folder on the server, e.g.
/public_html/qso. - Test connection... checks the login, write permissions and national characters in file names.
On the first connection the program remembers the server's "fingerprint". If it changes later, the program warns you and will not connect without your consent - this protects against someone impersonating the server. Not sure about the settings? Check your hosting panel.