Getting Started with K1JT modes using Direct Interoperation Between DXLab and WSJT-X

WSJT-X uses a soundcard connected to your transceiver to implement communication protocols or "modes" called FST4, FT4, FT8, JT4, JT9, JT65, JT9, MSK144, Q65, QRA64, and WSPR, as well as one called Echo for detecting and measuring your own radio signals reflected from the Moon. These modes were all designed for making reliable, confirmed QSOs under extreme weak-signal conditions.

SpotCollector can connect to up to 16 instances of WSJT-X, orchestrating the realtime interoperation between those instances of WSJT-X and your DXLab applications by creating and updating Spot Database Entries, directing DXKeeper, DXView, and Pathfinder to perform lookup operations, and routing logged QSOs to DXKeeper. The instance of WSJT-X running on the same computer as SpotCollector and Commander is referred to as the local WSJT-X instance.

When connected to one or more instances of WSJT-X as a spot source, SpotCollector will create a new Spot Database Entry for station X when, assuming all other Spot Database Entry creation criteria are met, when

The new Spot Database Entry's Network field will be set to WSJTX.

When WSJT-X decoding station X results in the creation of a new Spot Database Entry, the new Entry's Source field will be set to your callsign. When WSJT-X decoding station Y calling station X results in the creation of a new Spot Database Entry, the new Entry's Source field will be set to Y.

Three Spot Database Fields are used to record the most recent, lowest, and highest SNR computed and reported by WSJT-X for each station:

SpotCollector will update existing Spot Database Entries with new SNR and grid square information reported by WSJT-X; Network and Source fields will also be updated. Note that the "WSJT-X decodes station Y calling station X with an SNR" scenario does not update the Spot Database Entry for station X with an SNR, as the reported SNR is computed and reported by station Y, not by your instance of WSJT-X.

When a Spot Database Entry is created with no SNR is available - either the station is operating in a K1JT mode but hasn't yet been decoded by your instance of WSJT-X, or because the station isn't operating in a K1JT mode - ActualSNR, ActualSNRMin, and ActualSNRMax fields are set to -9999, which are shown as blank in the Spot Database Display; this is illustrated by the fourth row of the Spot Database Display in the screenshot below, where WSJT-X decoded a report of HK3UA by CT7AIU, but has not decoded CT7AIU.

http://www.dxlabsuite.com/Wiki/Graphics/SpotCollector/WSJTXSpotDatabaseEntries.jpg

Filtering the Spot Database Display

With SpotCollector connected to the local WSJT-X instance, you can filter the Spot Database Display to show only active stations operating in the mode currently selected in that local WSJT-X instance by using the SQL expression

MODE='<WSJTXMODE>'

By default, the Spot Database Display will include all active stations reported by instances of WSJT-X: those it directly decodes, and those reported with an SNR by stations it decodes.

(MODE='<WSJTXMODE>') and (ACTUALSNR<>-9999)

<STANDARDFILTER> and ((MODE<>'<WSJTXMODE>') or  ((MODE='<WSJTXMODE>') and (ACTUALSNR<>-9999)))

<NEEDFILTER> and ((MODE<>'<WSJTXMODE>') or  ((MODE='<WSJTXMODE>') and (ACTUALSNR<>-9999)))

Color-coding Callsigns in the WSJT-X Band Activity Panel

With the same font colors and background colors used in the Spot Database Display, SpotCollector colors the text and backgrounds of callsigns that appear in the WSJT-X Main window's Band Activity panel based to indicate award need (DXCC, IOTA, Leaderboard, Marathon, VUCC, WAS, WAZ, WPX) and eQSL/LoTW participation. You can optionally specify the colors used to display CQs and your callsign in the WSJT-X Main window's Band Activity panel by checking the CQ color and MyCall color boxes respectively in the WSJT-X panel on the Spot Sources tab of SpotCollector's Configuration window; to modify either color, click in the colored rectangle to the right of the checkbox.

http://www.dxlabsuite.com/Wiki/Graphics/SpotCollector/WSJTX.jpg

Directing DXKeeper, DXView, and Pathfinder to Perform Lookup Operations

When a new DX Call is selected or specified in an instance of WSJT-X,

All three of the above functions are enabled by checking the Lookup box in the WSJT-X panel on the Configuration window's Spot Sources tab.

Selecting a Spot Database Entry

With SpotCollector connected to an instance of WSJT-X, double-clicking a Spot Database Entry will, if the Entry's Mode field is a K1JT mode (FST4, FT4, FT8, JT4, JT9, JT65, JT9, MSK144, Q65, QRA64, and WSPR), do the following:

Logging QSOs to DXKeeper

With SpotCollector connected to one or more instances of WSJT-X, when you direct an instance of WSJT-X to log a QSO, the information captured in that instance's Log QSO window is routed to DXKeeper, which augments it with

and then directs DXKeeper to log the QSO, with the option to upload the logged QSO to ClubLog, eQSL, and/or LoTW.

Note: after unsuccessfully pursuing a QSO, strike the ESC or F4 key to ensure that the WSJT-X Log QSOs window proposes an accurate start time for the next QSO.

Installation and Configuration

Computer Clock Synchronization

Operation in the FT4 and FT8 requires your computer clock to be accurate.

See the WSJT-X User Guide for recommended applications that will automatically keep your computer's clock accurate.

Installing and Configuring WSJT-X as the Local WSJT-X Instance

The instance of WSJT-X running on the same computer as SpotCollector and Commander is referred to as the local WSJT-X instance.

  1. The latest WSJT-X installation file is available in http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

  2. Open the Settings window by selecting the File menu's Settings... tab

  3. On the Settings window's General tab

    1. In the Station Details panel,

      1. Set My Call to your callsign

      2. Set My Grid to your six-character grid square

      3. Select your IARU Region

    2. In the Display panel,

      1. Check the Blank line between decoding periods box

      2. Check the Tx messages to Rx frequency window box

  4. On the Settings window's Radio tab

    1. In the Rig dropdown menu, select DXLab Suite Commander

      • This enables WSJT-X to control your radio via Commander, rather than via a serial port, or a virtual serial port created by a USB connection.

      • If you've configured Commander to use other than TCP port 52002, then specify the port TCP Commander is using in the CAT Control panel's Network Server box

    2. Set the Poll Interval to 1 second

    3. Set the PTT Method panel to CAT (in this context, PTT refers to switching the radio between reception and transmission)

      • Alternatively, if you have a separate COM port connected to a device with PTT capability triggered by the assertion of the port's DTR or RTS modem control signal, you can configure WSJT-X to use it, as doing so will provide more accurate PTT timing. If you choose this approach, however, don't configure Commander to use the same COM port for PTT, as WSJT-X would then be denied access to the COM port.

      • If Commander cannot switch your radio between reception and transmission, then consider an alternate selection for PTT method, e.g. VOX.

    4. In the Mode panel, select the transceiver mode that is appropriate for your radio:

      • If your radio provides a DATA mode, choose Data/Pkt

      • If your radio doesn't provide a DATA mode, choose USB

    5. In the Split Operation panel, select Rig. If this setting doesn't work with your radio, selectFake it.

    6. Test WSJT-X's interaction with Commander (which must be running)

      1. Click the Test CAT button; it should turn green after a few seconds to indicate that WSJT-X is correctly interacting with Commander

      2. Click the Test PTT button and confirm that your radio switches from receiving to transmitting; click the Test PTT button again and confirm that your radio switches back to receiving

  5. On the Settings window's Audio tab

    1. In the Soundcard panel, select the appropriate soundcard Input and Output sections

      • You may need to adjust levels in Windows audio settings for best operation. The WSJT-X documentation describes how to do this. The best settings may not be optimal for !Winwarbler operation so you may have to find a compromise that works for both.

    2. In the Remember power settings by band panel, check the Transmit and Tune boxes

  6. On the Settings window's Reporting tab

    1. In the Logging panel, check the Prompt me to Log QSO box

    2. In the UDP Server panel

      1. If SpotCollector is hosted on the same computer as WSJT-X, set the UDP Server box to 127.0.0.1; otherwise, set the UDP Server box to the IP address of the computer that is hosting SpotCollector, and configure the firewall on that computer to accept incoming UDP messages on port 2237

      2. Set the UDP Server port number to 2237

      3. Check the Accept UDP requests box

  7. On the Settings window's Frequencies tab,

    1. Set the Frequency Calibration panel's Slope and Intercept to 0

    2. Set the Offset to 0 in any entries in the Station Information panel

  8. In the Settings window's Colors tab's Decode Highlighting panel,

    1. Check the My Call in message box (at the top)

    2. Check the Transmitted message box (at the bottom)

    3. Uncheck all other boxes

  9. If you're using Windows 10, configure Windows to enable Let apps use my microphone in its Settings window's Microphone section. If this option is disabled, applications will be prevented from using any audio device.

Installing and Configuring Additional WSJT-X Instances

Only one instance of Commander is permitted to run on a computer. Thus you can

  1. install additional WSJX-X instances on the computer on which SpotCollector and Commander are running, but these instances must directly control their associated transceivers; they cannot use Commander to do so.

  2. install Commander and one an additional WSJX-X instance on a computer that is network-connected to the computer on which SpotCollector and Commander are running that uses Commander for transceiver control

  3. install additional WSJX-X instances on a computer that is network-connected to the computer on which SpotCollector and Commander are running, but these instances must directly control their associated transceivers; they cannot use Commander to do so.

An additional instance of WSJT-X must be started from a CMD window using the rig-name command line argument, as described in the WSJT-X User Manual.

Each additional WSJT-X instance should be configured as described in Installing and Configuring WSJT-X as the Local WSJT-X Instance above, except that

Configuring Commander

  1. On the Configuration window's General tab, click the Net Server button on the right edge of the tab to display Commmander's Network Service window.

  2. In Commmander's Network Service window, set the TCP Network Service panel's Base Port to 52000

Configuring SpotCollector

  1. On the Configuration window's General tab,

    1. set the to Transceiver mode for WSJT-X panel to match your choice of mode in step 4.d of the Configuring WSJT-X section above

    2. select a Sub-band Definition file that defines sub-bands for the K1JT modes you'll be using; the file BandModes 2019-05-02.txt in your SpotCollector folder defines sub-bands for many K1JT modes.

  2. On the Configuration window's Spot Database tab, set the Combination Criteria panel's Maximum separation in frequency (kHz) to 3

  3. In the Layout panel on the Configuration window's Spot Database Display tab

    1. If you are pursuing awards based on primary administrative subdivisions (e.g. US States, Canadian Provinces, Russian Oblasts), add a column to the Spot Database Display for the Primary field

    2. To see the SNR most recently decoded by WSJT-X, add a column to the Spot Database Display for the ActualSNR field

    3. To see the smallest and largest SNRs decoded by WSJT-X, add columns to the Spot Database Display for the ActualSNRMin and ActualSNRMax fields, respectively

  4. In the WSJT-X panel on the Configuration window's Spot Sources tab

    1. Check the CQ color box. By default, CQs in the WSJT-X window's Band Activity panel will be colored emerald green; to change the color, click in the emerald green box.

    2. Check the MyCall color box. By default, your callsign in the WSJT-X window's Band Activity panel will be colored purple; to change the color, click in the purple box.

    3. Set the Port to 2237

    4. Check the Callbook box if you want DXKeeper to augment the information logged with a QSO to include the results of a Callbook lookup

    5. Check the Lookup box if you want DXKeeper, DXView, and Pathfinder to be directed to perform lookup operations when a new DX Call is selected or specified on the WSJT-X Main window

    6. Check the eQSL, LoTW, and/or ClubLog boxes to enable automatic uploading of logged QSOs

    7. Check the Enable box; if WSJT-X is running, the right-most LED-like display in the Spot source status panel at the top of SpotCollector's Main window should change from red to yellow (meaning connecting to WSJT-X) and then to green (meaning connected to WSJT-X)

http://www.dxlabsuite.com/Wiki/Graphics/SpotCollector/WSJTXSpotSourceConfig.jpg

Configuring DXKeeper Before an Operating Session

  1. On the Defaults tab of DXKeeper's Configuration window,

    1. Specify a default Operator callsign to be logged with the QSOs you are about to make

    2. Specify a default Propagation mode that you expect will be used in most of the QSOs you are about to make

    3. Clear the Satellite name and Satellite mode boxes unless you will be making QSOs via a satellite

    4. Clear the Meteor shower box unless you will be making QSOs via meteor scatter during a specific meteor shower

    5. If desired, specify a Default QSL Message

  2. In the Log Settings panel on the Log tab of DXKeeper's Configuration window, specify the Default myQTH ID to be logged with the QSOs you are about to make

Starting an Instance of WSJT-X

SpotCollector will accept connections from up to 16 instances of WSJT-X. If more than one instance of WSJT-X is running on the same computer, each instance on that computer must have distinct IDs; this can be accomplished by specifying a unique rig name in a command line used to start WSJT-X, for example:

wsjtx --rig-name=IC7800

The specified ID will appear in the WSJT-X window's caption:

http://www.dxlabsuite.com/Wiki/Graphics/SpotCollector/WSJT-X ID.jpg

Limitations

  1. JT-Alert and SpotCollector cannot be simultaneously connected to the same instance of WSJT-X via the same UDP address and port; if you wish to use JT-Alert,

    1. uncheck the Enable box in the WSJT-X panel on SpotCollector's Configuration window's Spot Sources tab

    2. start JT-Alert.

  2. SpotCollector will accept connections from up to 16 instances of WSJT-X

  3. WSJT-X logs a single frequency for each QSO; it does not record both TX and RX frequencies.
  4. The contest exchange information logged by WSJT-X is not yet documented; DXKeeper is unlikely to generate correct Cabrillo from QSOs logged by WSJT-X.

  5. With SpotCollector connected to WSJT-X,

    1. double-clicking a Spot Database Entry whose Mode field specifies FT8, JT65, JT65A, JT65B, JT65B2, JT65C, or JT65C will not change the mode in WSJT-X, or set the DX Callsign in WSJT-X.

    2. double-clicking a Spot Database Entry for which no sub-band is defined for the Entry's Mode within the Entry's band will result in no change of transceiver frequency or mode.

Additional Topics

Post a question or suggestion on the DXLab Discussion Group

Interoperation with Other Amateur Radio Applications

Getting Started with DXLab

GettingStartedwithK1JTModesDirect (last edited 2021-06-17 23:52:06 by AA6YQ)