WSJT DX Aggregator is a program that allows the stations using the WSJT-X or JTDX programs to automatically upload DX reports to DXMAPS so that they can be shown on the maps, listings, etc.
NOTICE also that WSJT DX Aggregator does not send DX-Spots to the DX-Cluster network, but only to DXMAPS.
The program takes the decode frames from the UDP stream of WSJT-X/JTDX, interpret and filter them, and upload the data to DXMAPS server.
Using WSJT DX Aggregator is extremely easy and if you already use WSJT-X/JTDX you can be uploading DX reports in minutes. Simply follow these steps:
1.- Download the program, unZIP it and place it in any folder of your computer you whish (for instance C:\radio\WsjtDXAggregator). The program does not require installation in most of the cases. Just place it in a folder and run it. If you get an error message indicating that some files are missing then download a full setup package , place it in an empty folder and run it from there (do not run it directly from internet)
2.- Enter your amateur radio callsign, your locator/grid square and the UDP port where WSJT-X is sharing the frames. Then press "Start monitoring".
If all is OK you will immediately see the frames received in the "Raw message received" box. Otherwise it means that the UDP port configured in WSJT DX Aggregator and in WSJT-X/JTDX don't match. Please notice that port 2237 used in this example can be any available UDP port in your system. Just make sure that it is the same that you have configured in WSJT-X/JTDX for sharing the data.
Leave the program running (you can minimize it if you want). As soon as it detects a CQ or QRZ message it will automatically spot it to DXMAPS.
In WSJT-X go to "File - Settings - Reporting" to configure the UDP port, as show below.
If you are running WSJT-X and WSJT DX aggregator on the same computer you must use the "localhost" IP address 127.0.0.1
If you are running WSJT DX Aggregator on a second computer you must configure the IP address of that computer. Just bear in mind that both computers must be in the same network.
VERY IMPORTANT: The frequency in which the stations will be reported is the frequency shown in WSJT-X. Make sure that this frequency is the same that set in the rig before starting the WSJT DX Aggregator.
Multicast: In order to allow messages to be shared by several programs, WSJT-X allows to send them to a multicast group, instead of to a specific IP and Port. All programs that join that multicast group will get the messages. Read the following page for multicast configuration details.
JT-Alert users: So far it is not possible to use simultaneously JT-Alert and the Aggregator because JT-Alert is blocking the use of the UDP port, not allowing other applications to get the messages from WSJT-X. If someday in the future, JT-Alert can join a multicast group then it will be possible to have both programs working at the same time.
Multiple instances of WSJT DX-Aggregator: If you are running multiple instances of WSJT-X / JTDX in different bands you must also have multiple instances of WSJT-DX Aggregator. Each WSJT-X/JTDX must be paired with an instance of the Aggregator using a common and unique UDP port. You can force each instance of the Aggregator to have a different configuration by starting it with a command line parameter, for instance run "WsjtDXAggregator.exe /C=ConfigFile1.ini" to use ConfigFile1.ini, etc.
WSJT DX Aggregator has been tested with the release versions 1.6 and 1.7 of WSJT-X. Also with JTDX 17.7, although it will eventually work with other versions.
If you are having some trouble using WSJT DX Aggregator don't hesitate to E-Mail me
You could also be interested in the APRS DX Aggregator, in the AIS DX Aggregator and in the MAP65 DX Aggregator
Changes in version 2.2:
Changes in version 2.1:
Changes in version 2.0:
Changes in version 1.9:
Changes in version 1.8:
Changes in version 1.7:
Changes in version 1.6:
Changes in version 1.5:
Changes in version 1.4:
Changes in version 1.3:
Changes in version 1.2: