Log4OM

Hello!

Log4OM shows shows the wrong grid during a QSO quite often when I use WSJT-X with it.
After the QSO is done and I save it in the log, the locator is correct again.
The field "new grid" in Log4OM is useless in such cases and also the map section does not show the correct position.

Here is an example: On the left you see the QSO windows from WSJT-X with the transmitted grid IN94.
Log4OM shows JN16 as the grid and later, when saving the QSO, the grid is set back to IN94 again (see red marks in screenshot).

Other applications like GridTracker show the correct grid.
I have attached my QRZ.com account to Log4OM. I am not a paying user there.
The grid value is showing the correct content there.

Is Log4OM not gettingt the grid together with other data from WSJT-X?
Where does it get this strange grids from?

Thanks for your help. Have a good time!
vy73 de DL4DE

Makes me wonder how you have your Program Config/Info Providers - 'Configuration' tab set up?

Hello Terry,
what exactly do you mean?
The "Info Providers"? I played with the settings a bit, but was not able to solve my problem.
Honestly, I never hearf of CTY DB at all, so I am unsure what to set here.
I got QRZ.com as the only configured external source.

My question was if Log4OM also receives the grid from WSJT-X. If not, I wonder from where it gets the grid and how this can be different from the true content that is visible in WSJT-X, QRZ.com etc.

Minutes ago I had again the case that a station from around New York had a grid from somewhere around Cuba.

73s DL4DE

DL4DE wrote: 25 Jan 2023, 14:49
Which extern sources of what application?

Log4OM - the order of this menu dictates the accuracy of the information displayed - See OUR user guide for full information

My question was if Log4OM also receives the grid from WSJT-X.

Yes the recorded (Logged) data comes from mthe FT8 software

If not, I wonder from where it gets the grid and how this can be different from the true content that is visible in WSJT-X, QRZ.com etc.

1. What is received from WSJT etc is what is logged - This may or not be correct but we wont change existing data

2. The lookup in the Log4OM window when using FT8 software is not what we log we log the information received from the FT8 software

3. The lookup in Log4OM window when using FT8 software is a visual display only and only for your information!

4. All incoming data whether from an external program or by Log4OM lookup is relient on the accuracy of the data received from the source (Info provider)

DL4DE wrote: 25 Jan 2023, 14:49 Hello Terry,
what exactly do you mean?
The "Info Providers"?
2023-01-25 16_13_53-Configuration.png

That is wrong

order for left column should be

External source
Clublog
CTY

For right column shoud be

Clublog
External source
CTY

The graphic at the botton should illustrate the origins and order of the data and if all else fails our user guide explains everything

One final point is that the information supplied from QRZ via its API for software download does not always match the information that they display on the web site lookup - Been like that for ten years

Sorry, but I still don't understand.
Your wrote that you log everything that is received from WSJT-X.
Yes, that is true. THe entry in the log is correct.
But during the QSO, before the log entry was made, the grid is different in nearly all cases.
W3XOX 's grid is FN00. But somehow from somewhere Log4OM shows EM10. Who is telling the application this wrong data?

I changed the settings like you suggested, but with no difference. The screenshot was made after I changed it.
I still can't understand this behaviour of the software.

DL4DE wrote: 25 Jan 2023, 15:44
But during the QSO, before the log entry was made, the grid is different in nearly all cases.

1. Probably because either:
a. You have not selected the correct settings in the Log4om config as described earlier
b. The FT8 information is wrong
c. The info from QRZ is incorrect
d. The info via the QRZ API for external software is not the same as displayed on their web site - As I said earlier that has been happening for the last 10 years

Most likely is a.above! but what the heck, that grid locator is not being saved to your log its the data from WSJT thats saved!

I changed the settings like you suggested, but with no difference. The screenshot was made after I changed it.
I still can't understand this behaviour of the software.

Contradictory statement - I did not describe the search order as you have it displayed

The settings from above fixed the wrong GRID lookup on my side, thanks for that
What is still wrong is the retrieved GRID when the logged station is not registered on QRZ.com
I send the GRID that I have received in WSJT-X and stored in the log to Log4OM but there another GRID is shown and saved.
After saving I have to edit the GRID manually but only for contacts that I cannot look up.
So what would be the correct settings for those stations?
My goal would be that all GRIDs were saved from WSJT-X because the GRIDs that are send out are more up to date then from QRZ.com and Co.

73s

How are the qao's transfered to log4om by ADIF monitor or UDP

Hi Terry,

please see attached screenshots.
I set the ADIF monitor so that missing QSOs are imported when opening Log4OM.
That is working very well because sometimes I forgot to open Log4OM

In the second screenshot you can see my UDP settings, there is also a connection to GridTracker which is also working very good.
If there are any glitches in the settings please let me know.

wish you all a nice weekend.

73s