Tonight I discovered another way this issue can affect log entry. Here's a screenshot of callsign K0AF. K0AF.png Note the gridsquare. Now if I fail to work him and hear N7ZZ, I might select the original call like this: K0AF2.png And key in the new call. N7ZZ.png The result is an incorrect gridsquare...

Juergen / Roy, I've read the adif spec and Juergen is correct, the format for County is State,County. In my log however, all of my county entries are just the county name in mixed case. Only when the QSO is confirmed via LoTW does the county change to the format that Roy shows. For example if I work...

Pls check to see if the most current version of Log4OM V2 has resolved this issue for you. Nolan / Terry / Daniele I am now running ver 2.8 and the issue remains the same. Daniele's explanation shows he understands exactly what is happening. Once something ends up in the gridsquare field, you canno...

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