Incorrect Grid Logged

[N6VH]

Using:
Log4OM 2.26.0.3
WSJT-X 2.6.1
JtAlert 2.60.4 Beta 0009
Win 11

I worked K7IOC today on FT8. He was sending grid CN88. However, Log4OM logged him as DN11. CN88 was the grid he was sending, and it was the grid sent to Log4OM by JTAlert. This shouldn't be a matter of lookups, cty files, Clublog, or anything else. The point is, the information sent to Log4OM wasn't what was logged. Where did the DN11 come from?
Incidentally, I have also worked the same station recently, under the same circumstances, using 2.26.0.0, and he was logged correctly. Has something changed in the beta?

73,
Jim N6VH

[N6VH]

This seems to be happening with other calls also. Furthermore, K7IOC uploaded to LOTW with grid CN88SE, and Log4OM didn't change the grid from DN11.

73, Jim N6VH

[es2hv]

ES2HV I have the same problem

[PD2TX]

version 2.25 don't shows this error.
version 2.26 does!

I had the same issue en downgraded the softwareversion to the 2.25 and the problem disappeared.

73'
Nico PD2TX

[Pa0ply]

I switched off external references, to get is working with WSJT-x

[DF5WW]

viewtopic.php?t=8118

[N6VH]

Thank you. Yes, I have been reading those posts, also. The problem I was having was in the beta version, 2.26.0.3, I reverted back to 2.26.0.0, and have not had that problem. Something seems to have changed in the beta version.

73,

Jim N6VH

[ve3wej]

not sure if this is related, but I just imported a log into log4om 2.26.0.0 and 99% introduced a grid square ( incorrectly). fyi, there was no grid square in the original adi file. where is log4om picking this up, and why. I can qrz all these contest grids via the qso manager after


I manually deleted each grid, so the lookup would refill it with the correct one ( or at least what is posted )