We’ve recently begun experimenting with a WSJT-X derivative for FT8 and other JT Modes. Its called JTDX. The JTDX software is created by Igor Chernikov, UA3DJY, and Arvo Järve ES1JA. The stated purpose for JTDX from the is:
JTDX supports JT9, JT65, T10 and FT8 © digital modes for HF amateur radio communication, focused on DXing and being shaped by the community of DXers.
The latest release candidate of JTDX supports some interesting additional features beyond WSJT-X including:
- Additional FT8 and JT65 decoder options which can provide improved sensitivity
- Advanced automatic sequencing and QSO selection features
- Decoded messaging filtering features
We’ve been testing JTDX V2.0 release candidates here for about a month now. the JTDX feature additions definitely provide some useful enhancements. The JTDX software is derived from WSJT-X and we’ve been using it here for DX’ing and for weak signal work on 6 meters. It appears to have most of the features of the current version of WSJT-X with the notable exception of support for specific contest exchanges.
JTDX adds a number of FT8 decoding options that are useful on crowded bands and in situations when signals are very weak. These features can be selectively enabled to match band and signal conditions as well as the user’s available CPU horsepower. With all features enabled, JTDX seems to decode more signals on a crowded band than WSJT-X.
There is also a QSO partner decoding “filter” option which concentrates the FT8 decoder on a narrow bandwidth around a specific weak signal that you are trying to receive and decode. This feature seems to help to decode very weak signals in a crowded band when they are surrounded by other, stronger callers.
You may have experienced the crowded conditions in the FT8 sub-band on popular bands like 20m.
If you call CQ with Auto Sequence and Call First turned on in WSJT-X, you may find that you don’t have much control over what stations are selected to answer your CQ. It’s also common for the Auto Sequencing in WSJT-X to “get stuck” on a caller that how fails to complete a QSO for whatever reason.
JTDX provides some useful features to prioritize the selection of callers in these situations.
You can see these options on the menu above. Options include choosing a station to answer based upon distance or best Signal To Noise Ratio (SNR), including or excluding stations that you’ve worked before, or including or excluding other stations calling CQ. These features allow JTDX to do a better job selecting a QSO to Auto Respond to when you are calling CQ.
What about the problem of “stuck” QSOs? JTDX has some useful features that limit the number of tries that the Auto Sequencing algorithm uses before returning to calling CQ or working the next available caller. These features prevent the Auto Sequence algorithm from getting stuck during a contact when your QSO partner fails to respond or decided to work someone else.
JTDX also has the ability to enforce “directed CQ’ing”. Directed CQ’ing is when you call, for example, “CQ DX” and get responses from callers in your country. JTDX Auto Sequencing can be configured to ignore such callers and only work DX stations that answer your CQ. Directed CQs can also be applied to specific regions of the world (CQ AS for example) as well.
Finally, you may have experienced a flood of decoded messages on a busy band. It is almost impossible to read and process all of the information a large number of decoded messages in the 15 seconds available. JTDX has some good filtering options to selectively hide decoded messages to enable the operator to focus on messages from stations that they are looking for. The image above shows a very simple application of this capability to limit the decoded message display to only CQ messages. More complex rules are possible via configuration in the Filters tab.
There is a learning curve with JTDX and it takes a little time to learn to use all of the new features. There is a basic getting started guide that helps to get JTDX set up and configured at your station and some useful FAQ documents to help you learn about some of the JTDX features. The best source of information on the more advanced features is the JTDX groups.io group.
I don’t think that JTDX is a replacement for WSJT-X. We run both here and they both work well. JTDX has some important advantages in crowded band situations and is my tool of choice for working DX with FT8. I also like the more sensitive decoder in JTDX for weak signal FT8 work on the 6m band. WSJT-X is a better tool for contests as it contains support for specific contest exchanges via FT8 – a feature that JTDX does not yet support. WSJT-X also supports important modes like MSK144 for Meteor Scatter QSOs.
If you are new to FT8, I’d suggest you begin with WSJT-X and use it to learn the basics of the FT8 protocol and how to operate using FT8. You can find a Video Introduction to WSJT-X and FT8 here on our blog to help you get started and get on the air with FT8 using WSJT-X.