Team,

Just checked this out in 2.6.1 and FIXED! That's like record time. Great job.

Are you referring to your own zone info in the program config If so what must be happening is that WSJT etc are using incorrect info for YOUR zones, of course when we receive that information as part of the incoming data we don't change or check it Use the UDP monitor to watch the incoming data fro...

There is a 4/5 page long topic on this forum about this, please refer. Resolved in next release Terry, If you are referring to the CQ Zone "0" issue, I'm well aware of that and have contributed to that discussion. This is a different problem. It seems Log4OM automatically changes my Station Informa...

I have discovered if my CQ or ITU zones are different in JTAlert than in Log4OM and I log a contact from JTAlert, Log4OM changes my station setup to the CQ and ITU zones that come in the JTAlert logging "transaction". I know these fields should never be different between the two programs but if it h...

Another WB2UBW test: Turned External Sources to "None" for Running and History. Logged from WSJTX and got 6 0. Updated with globe and got 8 5. Turned External Sources back on for both Running and History. Logged from WSJTX and got same 6 0. Updated with globe and got same 8 5. Looked in JTAlert Log...

I just did a test log of WB2UBW, from WSJT-X/JTAlert. The correct zones were logged. For real-time logging, I have my configuration set the same as yours, except I don't use lookups from external sources (QRZ, etc.). Try turning off look-ups from external sources, and then do a test log using WB2UB...

A couple nights ago I worked WB2UBW via WSJT-X / JTAlert. He should log as ITU=8, CQ=4. He logged as 6 0 instead. Here's my Info Provider Config. Config2.png I then just keyed this call into the UI. It shows Zones 8 5. UI1.png To figure out what was going on, I changed the Realtime Logging config to...

I've made 34 contacts in the last 3 days using ver 2.5 and have 6 contacts logging ITU=6 and CQ=0. If I go into edit of these contacts and hit refresh, 4 of them update to ITU=8 CQ=5 which is correct for their gridsquare. One is gridsquare EM13 which should be ITU=7 CQ=4 and it refreshes to ITU=6 CQ...

Tom, I keyed in all of the possible KH6X calls. The only ones that showed as US were KG4V & KG4W. I also typed in some KG4XXX calls that I haven't worked, and they all show Gitmo. I don't use QZX lookups (or lookups from any other source), but that shouldn't be a factor. The country (in my case) co...

Jim, Thank you for checking some more. There may be differences between looking up calls already worked vs a "new one". I have been checking "new ones" and always see US and DXCC 291 unless the call is a KG4 2x2. Could you quickly rattle through all of the 2x1 KG4 calls and note if any show other th...