This page explains two possible methods which should be employed when JT-Alert is working with WSJT-X.
These are not required when using WSJT stand-alone, thus can pass log QSO data directly to Winlog32

Method 1: WSJT generates and passes QSO data to JTAlert, JT-Alert then passes logging data formatted as ADIF to Winlog32 via UDP.
See also ADIF UDP for this method.

Method 2: WSJT generates and passes logging data to JT-Alert, JT-Alert generates a single QSO ADIF file, and Winlog32 automatically processes the file, and logs the QSO.

One of these methods must be used when running JT-Alert together with WSJT-X.

METHOD 1: UDP direct data communication method.

This Winlog32 interface receives an ADIF data stream from JTAlert via UDP.
This option is necessary when using JTAlert-X with WSJT-X as JT-Alert occupies the UDP port to get its log data from WSJT-X.
A QSO log file is created by WSJT-X and passed to JTAlert-X for processing, JT-Alert passed same to Winlog32 via UDP, this function requires the WSJT-X option 'Add To Log' and also some parameters setting in both JTAlert and Winlog32.

menu/Option/Logging Interface/UDP N1MM, ADIF, JTAlert> Options.

Menu/Options/Logging interface/N1MM+ADIF> Enable 'ADIF'

A green indicator will show when a logging interface is enabled.

JTAlert configuration:
JTAlert should first be configured to work with WSJT-X.
Settings/Manage Settings/Logging/Last QSO API: enable option 'Enable transmission of last QSO'.
Ensure that UDP port is set to the same number as in Winlog32.
The setting 'Include ADIF header' can be disabled as Winlog32 does not use this data.

Method 2: Single file transfer from JTAlert.

Menu/Options/Logging interface/FLDIGI-JT-ALERT > Enable JT-Alert

This interface imports a single QSO from JTAlert-X when WSJT-X is used in conjunction with JTAlert-X.
This option is necessary when using JTAlert-X with WSJT-X as JT-Alert occupies the UDP port to get its log data from WSJT-X.
A QSO file is automatically created by JTAlert-X ('lastqso.adi') for this function when 'Add To Log' is used in WSJT-X.
This file is automatically imported then discarded by Winlog32, only a single QSO can be imported by this method.

If this method is used and a QSO has already been stored in this file, you will be prompted to import this QSO when the Winlog32 <> JTAlert-X option is enabled.

This can be a useful fail-safe if the logging option was not enabled or Winlog32 was not started and a QSO had already been logged in WSJT-X. Please note that only the LAST QSO logged by WSJT-X is stored in this file.

N.B.
The JT-Alert option (Method 2) requires the 'User Callsign' in Winlog32 to be the same as that used in WSJT-X / JT-Alert for a correct file path direction to that created by JT-Alert.
In cases where this is not possible, use JTAlert UDP Method 1.

N.B.
If the JT-Alert option is enabled the WSJT-X UDP is disabled, if the WSJT-X UDP is enabled the JT-Alert option is disabled, you can not use both togther as this may create duplicate QSO entries in Winlog32.

N.B.
When using third party logging interfaces, the Real-Time Upload to Online Logs' can still be used however it is better to disable the Auto-Upload 'PROMPT' option. menu/options/Settings TAB Realtime Upload
Be aware that some external kogging software may have similar options to upload QSO, it is obviously essential that only one upload takes place for each QSO by enabling/disabling the appropriate options in either software.

It may be necessary to verify that a QSO has been logged correctly by Winlog32 when using any of these methods as there is no prompt or notification from Winlog32 when adding a QSO to the Log.
A slight delay of one or more seconds may occur when logging a QSO with the JTAlert file interface, this is normal (Method 3).
There is minimal delays using UDP interfaces.

These are general settings and similar options apply to all logging interfaces, however depending on application, some options may be ignored.

'Add Band Only'
Transfer Frequency BAND only, the default is to transfer the full frequency from WSJT-X.

'Add Info to User' and 'Add Info to Remarks'.
These two options select which field the WSJT-X / JTAlert Name and Comments are added in Winlog32.

Not all log fields produced by external logging will be imported into Winlog32.

The 'Auto-add' functions in Winlog32 are disabled when using the above logging methods.