Re: no wsjt to dxkeeper transfer of logs all day

HamApps Support (VK3AMA)
 

On 14/06/2018 12:16 PM, Dave AA6YQ wrote:
+ You must have JTAlert running for QSOs made with WSJT to be automatically logged to DXKeeper.

+ WSJT maintains a ADIF file in which it records all QSOs logged, so you can recover the QSOs that weren't properly logged. If you decide to import this ADIF file, be sure that duplicate checking is enabled; making a backup copy of your log file before importing makes it easy to recover if the import doesn't go as planned.

The WSJT-X ADIF file will only contain QSOs that have been logged in WSJT-X, that is the user has used the OK button on the WSJT-X Log QSO window.

If the user is OKing the Log QSO window, then WSJT-X will generate a QSO logged UDP packet which JTAlert detects and forwards the data to DXKeeper.

Upon receipt of a the UDP packet, JTAlert will either display a DXKeeper logging success or failure popup. If neither popup is seen (provided the user hasn't disabled the notifications) that indicates the JTAlert never received the UDP packet. Typically this happens because the user is not logging the QSO in WSJT-X.

WSJT-X is not an out-logging QSO machine. User intervention is needed to log a QSO.

de Laurie VK3AMA

Join DXLab@groups.io to automatically receive all group messages.