I have reviewed several threads that discuss what happens when no grid square is provided (from WSJT-x/JTAlert) and no external lookup... the center of the country grid square is logged.
However, I'm not seeing consistency regarding the use of external lookup sources. I am using QRZ.COM (paid XML) and HAMQTH - in that order. I have recently noticed that when no grid is provided by WSJT-X/JTAlert, that I see what seems like random results for what grid is logged. I'm sure there is a pattern, but I can't figure it out. Sometimes, its the grid displayed by the callsign lookup, sometimes its the center of the country (even when the correct grid is shown in the lookup).
Example today... YD3DCZ logged as OI62 (center of country), but lookup shown was OI51nt. What is strange is that I can't replicate this issue, but I have seen it happen many times.
WSJT-X v2.5.4, JTAlert v2.60.3, Log4OM v2.25.00. Note that I have seen this issue with earlier versions of both JTAlert and Log4OM.
73 Bill WT0DX
Wrong Grid Square Logged
Re: Wrong Grid Square Logged
I was able to catch an example of the issue. No grid was entered in WSJT-X/JTAlert. The lookup was correct, but not used in logging the contact.
73 Bill WT0DX
73 Bill WT0DX
Re: Wrong Grid Square Logged
I would appreciate if anyone else can confirm this issue. Moderators... any comments?
73 Bill WT0DX
73 Bill WT0DX
- G4POP
- Log4OM Alpha Team
- Posts: 11592
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Wrong Grid Square Logged
Because we dont update incoming qso's from JT programs, what is saved is what is received, not what we find on lookup.
Suggest you set your JT software to do the lookup while data is saved in JT program
Suggest you set your JT software to do the lookup while data is saved in JT program
73 Terry G4POP