DXLab Suite Setup Guide: DXKeeper, Commander and SpotCollector

For many DXers, DXLab Suite is the software that ties the whole station together. It is not a single program but a family of applications that each do one job well and cooperate automatically when they run side by side: one controls the radio, one keeps the log, one collects DX spots, one shows maps and propagation, and so on. That modular design is its greatest strength and also the reason new users sometimes find it confusing. Installed in the wrong order or configured piecemeal, it can feel like eight programs fighting for attention. Set up methodically, it becomes one of the most capable DXing environments available.

This guide explains what each DXLab application does, a sensible order for installing and configuring them, and how to connect logging, rig control, spot collection and confirmation services. It describes the general workflow; for menu-level details, the DXLab documentation and its wiki are thorough and kept up to date by the author and users.

What DXLab Suite Is

According to the DXLab Suite website, DXLab is a suite of eight interoperating applications that can be installed independently in any order. When several of them are running, they detect each other and work together automatically. The suite runs on Windows.

The site lists a wide range of functions: transceiver control for many radio brands, rotator control, grey line display, prefix and grid lookup, callbook lookup, real-time logging, QSL card and label generation, synchronisation with Logbook of the World, Club Log, eQSL and QRZ, award tracking for a long list of programmes, spot collection from several clusters including DX Summit and the Reverse Beacon Network, propagation prediction and digital mode operation. It also interoperates with WSJT-X, Fldigi and other popular programs.

The key idea is that you only run the parts you need. A casual operator might use only the logger and the radio controller. A serious DXer chasing awards on many bands and modes might run all eight.

The Eight Applications

Each application has a clear role. Understanding them before you install anything makes the rest of the setup much easier.

Plan Before You Install

Before you install, decide three things: which applications you need, where the data will live, and what your existing log looks like.

• Which applications: start with Launcher, Commander and DXKeeper. Add SpotCollector and DXView once logging and rig control work. Add the others when you have a reason.
• Where the data lives: DXKeeper stores the log in its own database file. Know where that file is, because it is the file you must back up.
• Your existing log: if you are migrating from another program, export a complete ADIF file first. Our guide to ADIF and moving your log between programs explains what to check in that export, especially QSL status fields and mode names.

Step 1: Install Launcher

Launcher is the control centre. It downloads and installs the other applications, keeps them up to date, and can start and stop them together. Installing it first means every later step goes through one familiar place.

Once Launcher is running, use it to install the applications you have chosen. Launcher can also start the applications in a set order when you begin a session, so you do not have to open them one by one. Configure that once you are happy with the basic setup. The DXLab getting started guide walks through this first stage in detail.

Step 2: Configure Commander for Your Radio

Commander controls the transceiver. It needs to know the radio model, the serial or USB port the radio appears on, and the communication settings such as baud rate. Those settings must match what is configured in the radio’s own menus.

1. Connect the radio’s CAT interface, usually a USB cable that appears as a virtual serial port.
2. In Commander’s configuration, select your radio family and model.
3. Choose the correct port and set the baud rate and other parameters to match the radio.
4. Enable the port and confirm that Commander displays the radio’s frequency and mode, and follows when you turn the dial.

If Commander cannot talk to the radio, the cause is almost always the port, the baud rate or another program already holding the port open. Only one program can open a serial port at a time, which is why it matters how other software, such as WSJT-X, accesses the radio. Our article on rig control and connecting radio and software explains the general principles of CAT control and port sharing.

Once Commander works, every other DXLab application can use it. DXKeeper reads frequency and mode for new log entries, SpotCollector can tune the radio to a spot with one click, and DXView can show the beam heading for the station you are about to call.

Step 3: Set Up DXKeeper

DXKeeper is the logbook and the heart of award tracking. Configuration takes a little longer because it has many options, but the essentials are straightforward.

Your station information

Enter your callsign, location and grid square. If you operate from more than one location or under more than one callsign, DXKeeper lets you define separate station profiles so that each QSO records where it was made. This matters for awards with location rules and for Logbook of the World.

Importing your existing log

Import your ADIF file and review the result. Check a sample of QSOs for correct bands, modes, dates and QSL status. DXKeeper can then recompute award progress from the imported contacts. Fixing import problems at this stage is much easier than discovering them months later.

Award tracking

Select the awards you care about. DXKeeper tracks progress per band and mode and can tell other DXLab applications what you still need. That is what makes SpotCollector’s needed-spot highlighting work. Our guide to how DXCC works explains entity, band and mode credits, which are exactly what DXKeeper tracks.

Confirmation services

DXKeeper can synchronise with Logbook of the World, Club Log, eQSL and QRZ. Set up the accounts and credentials each service requires, then use DXKeeper’s upload and download functions to send new QSOs and bring back confirmations. Regular synchronisation keeps your award status accurate without manual checking.

Step 4: Add SpotCollector

SpotCollector connects to DX clusters and other spot sources, combines what they report, and builds a database of active stations. The SpotCollector page describes support for several clusters at once, including DX Summit and the Reverse Beacon Network, with filtering and direct tuning.

The real power appears when SpotCollector runs alongside DXKeeper. Spots for stations you still need for an award, on a band and mode you still need, can be highlighted, so a busy spot window becomes a short list of contacts that actually matter to you. You can then tune the radio to a spot through Commander with a click.

A few configuration tips help:

• Connect to more than one spot source for better coverage, but filter aggressively so the display stays useful.
• Decide whether to include skimmer spots. They add a huge volume of CW and digital spots, which is useful for activity but noisy without filters.
• Use the needed-spot highlighting rather than reading every spot. Let the software do the comparison with your log.

Cluster etiquette still applies when software does the reading. Our article on DX cluster spotting etiquette and filtering covers how to filter well and how to post good spots yourself.

Step 5: DXView, PathFinder, PropView and WinWarbler

Once logging, rig control and spots work together, add the remaining applications as needed.

• DXView shows where a station is, the short and long path headings, and maps with the grey line. If you have a supported rotator, it can turn the antenna to the station you are working.
• PathFinder searches online sources for QSL routes and station information, which saves time when you need a manager or address.
• PropView produces propagation predictions for a path, helping you decide when to look for a station. It can also monitor the international beacon network.
• WinWarbler handles PSK and RTTY operation and provides CW and voice keying. For FT8 and FT4, most operators use WSJT-X, which interoperates with DXLab.

Connecting WSJT-X and Other Programs

Many DXLab users also run WSJT-X for FT8 and FT4. The two can share radio control and logging. A common arrangement is for WSJT-X to control the radio through Commander, so that only one program owns the CAT port, and for logged FT8 QSOs to flow into DXKeeper automatically. The exact configuration depends on the current versions, so follow the DXLab documentation for WSJT-X interoperation.

The same principle applies to any external program: decide which application owns the radio port, and let the others access the radio through it. Port conflicts are the most common source of trouble in multi-program stations.

Backups and Maintenance

Your log is irreplaceable. DXKeeper can create backups of its log database, and you should keep copies off the computer as well, for example on an external drive or a cloud folder. Export a full ADIF file from time to time too; ADIF is readable by any logging program and protects you if you ever change software.

Keep the applications updated through Launcher. Updates fix problems and add support for new radios, award rules and online services. After a major update, check that synchronisation with confirmation services still works and that award totals look correct.

Common Problems

• Commander shows no frequency: wrong port, wrong baud rate or another program holding the port.
• Applications do not see each other: make sure they are all running on the same computer and started normally; restart them through Launcher.
• SpotCollector shows everything as needed: DXKeeper may not have finished recomputing awards after an import, or award tracking is not configured.
• Duplicate QSOs after import: the same contacts were imported twice or from two different exports. Use DXKeeper’s tools to identify and remove duplicates carefully.
• LoTW confirmations not arriving: station location settings or certificate details do not match. Check the station profile used for upload.

If you are still deciding between logging programs, our comparison of N1MM, Log4OM and DXLab sets out where each one fits; DXLab is generally strongest for everyday DXing and award chasing, while dedicated contest loggers lead during contests.

The Bottom Line

DXLab Suite is a set of eight cooperating Windows applications for DXing: Launcher, Commander, DXKeeper, DXView, SpotCollector, PathFinder, PropView and WinWarbler. Install Launcher first, get Commander talking to your radio, set up DXKeeper with your station details, imported log and awards, and then add SpotCollector so that spots are compared with what you still need. Decide which program owns the radio port, synchronise regularly with confirmation services and back up the log. Built up step by step this way, DXLab becomes a coherent station environment rather than a pile of windows.

Frequently Asked Questions

What is DXLab Suite?

DXLab Suite is a set of eight interoperating Windows applications for amateur radio DXing. They cover rig control, logging, award tracking, spot collection, maps, QSL routes, propagation and digital modes, and they work together automatically when running.

Which DXLab application should I install first?

Install Launcher first. It installs, updates and starts the other applications. Then set up Commander for rig control and DXKeeper for logging, and add the remaining applications once those work.

Can DXKeeper import my existing log?

Yes. Export your existing log as an ADIF file from your current program and import it into DXKeeper. Review a sample of QSOs afterwards and let DXKeeper recompute award progress.

Does DXLab work with WSJT-X?

Yes. DXLab interoperates with WSJT-X. A common setup lets WSJT-X control the radio through Commander and sends logged FT8 and FT4 contacts to DXKeeper. Follow the DXLab documentation for current configuration details.

Does DXLab Suite synchronise with Logbook of the World?

Yes. DXKeeper supports synchronisation with Logbook of the World, Club Log, eQSL and QRZ, uploading new QSOs and downloading confirmations so that award progress stays current.

Is DXLab Suite good for contesting?

DXLab can log contest QSOs, but it is designed mainly for everyday DXing and award chasing. Most serious contesters use a dedicated contest logger during the contest and then import the log into DXKeeper afterwards.