Do you have the JTalert DECODES window open? If so, what grid does it show there for the /MM ? That is most likely what JTalert will send for the log ... if it is EMPTY, then that might explain why

Mark ... you're doing that the HARD WAY!! I also use the QRZ logbook and LotW ... but I use JTalert to upload my QSOs as they are made DIRECTLY to QRZ.com (you do need to have the QRZ XML

In the past, when I completed an FT8 QSO with a /MM maritime mobile station in a new water grid, the grid in the WSJT-X "DX Grid" field was entered in the llog box which opened after the 73 message

Hi Laurie, 1. I've only just returned to the hobby and I am still in the process of setting things up so the only logging that I'm doing is in WSJT-X and then up loading that .ADI file to QRZ.COM. I

what window? always good idea to include a screen shot of what you are talking about so folks here don't have to guess, or ask a bunch of questions to get the details.

rx window? in wsjt? what version jtalert and wsjtx ( or jtdx) are you using Dave Garber VE3WEJ / VE3IE

I will watch to see when this problem next occurs and let you know. Roger ZF1RC

First let me say I love JT alert . That being said. I have problem in RX frequency window. I call cq all meters say I’m putting signal out. Even get response , now here is the dilemma my call

Roger, I would fix this if I could isolate the cause. Unfortunately, the error line numbers are typically grossly inaccurate. Does this occur during very busy band

I have noticed that from time to time the attached message appears on the screen. It is not repeatable to so I have to wait for it to occur. Do I just continue to click OK and continue or does it need

You're missing most of the WSJT-X diagnostic information included in the JTAlert "Help -> About". Is this loss of comms with WSJT-X a recent problem or has it always done this?

Are you running another logging program or something like GridTracker that also requires UDP support from WSJTX? Since you are not using multicast UDP, the "third program" may be preventing JTAlert

No QSOs are showing. any help welcome. SJT-X UDP ID : WSJT-X UDP Port : 2237 WSJT-X UDP Server : 127.0.0.1 WSJT-X UDP MCast on LB : False WSJT-X UDP Max Schema :

There can be a number of reasons why the QSO History is not displaying results. Not having a logger enabled in JTAlert. JTAlert is looking at the wrong or empty log file.

Thanks, Laurie. Keeping fingers crossed :D Paul, sq5nry

Sorry, clicked on the wrong 3D2 station. Here's what happens with 3D2USU.

This is correct. Although you have worked 3D2USU, you apparently have not worked 3D2TS. 73, ... Joe, W4TV

FYI, this is also how WSJTX behaves. de Laurie VK3AMA

Sorry, That's not possible. I did some searching and found this note in the 2.10.0 release notes... The above notes have been added to the JTAlert Help file,

Nothing I can do. JTAlert doesn't know which browser is the Windows default. The code executed by JTAlert is identical for all browsers... The ShellExecute is an inbuilt