Log4OM

NS8K

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 ...

NS8K

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 ...

NS8K

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 ...

NS8K

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 ...

NS8K

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 ...

NS8K

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 ...

NS8K

To get back to the original topic, I just tested some kG4XXX calls using actual calls. Almost all of them show as Guantanamo Bay, even though they are located in the US. The one exception is KG4W, which displays correctly as US. I updated the country file and restarted Log4OM, and still getting ...

NS8K

Terry,

That's perfect, Thank You. V2 is great!

NS8K

Try bandplan_user_dxcc291.xml

Terry,
I thought you might have it but that doesn't work either. bandplan_dxcc291_user.xml does work but only when bandplan_dxcc291.xml is either gone or renamed.

I also discovered an error in my original solution. I am running "split" in WSJT-X so the dial ...

NS8K

In my case about 1/2 the US calls I search show up correctly on user the right map but center of country on left map.

Rich,

I assume you are talking about calls other than KG4 2x1 and 2x3 calls. I haven't noticed this but will pay more attention. Maybe this is a bigger issue than just ...

Search found 61 matches

Re: CQ Zone "0"

Re: CQ Zone "0"

Re: CQ Zone "0"

Re: CQ Zone "0"

Re: Country file- KG4x and KG4XXX not Gitmo

Re: Country file- KG4x and KG4XXX not Gitmo

Re: Country file- KG4x and KG4XXX not Gitmo

Re: 60 meter band not logging properly

Re: 60 meter band not logging properly

Re: Country file- KG4x and KG4XXX not Gitmo