Log4OM

Hiya,
In this version the grid is incomplete and shows the grid in the middle of the country (default grid).
Also the beta version of 2.26.03 has this bug.
Reinstalling the 2.25 version wil give the correct grid again.
-73 Nico
PD2TX

version 2.25 not correct

es2hv wrote: 13 Feb 2023, 07:10 version 2.25 not correct

Viktor,

Did you read the reply I provided to you on your thread? In your case you don't have (as best I can determine) at least an XML Data Subscriber membership with QRZ.com that will help provide you more detailed/granular information.

Here is that thread: https://forum.log4om.com/viewtopic.php?p=42636#p42636

I have set it up according to the instructions given in the help, but the program still sometimes behaves correctly and sometimes incorrectly

es2hv wrote: 13 Feb 2023, 14:03 I have set it up according to the instructions given in the help, but the program still sometimes behaves correctly and sometimes incorrectly

Please read viewtopic.php?t=4462

I'm sorry Terry but something serious has changed since about v2.24.
Even using the very latest v2.26.0.7 Beta, the "Grid" data is wrong.
LOG4OM appears to report the centre of the country even though it used to be correct.
I do have a QRZ.com subscription that is paid up and current.
I have (temporarily) changed to HAMQTH and still the wrong data is shown.
This is with "live" QSOs and nothing to do with QSOs via an FT8 program or similar.

What on earth are we all doing wrong?
(It isn't just me having the problem who have returned to a previous version because of it.)
73, G3ZPB

Please read release notes in help/about

Think you need to replace udp connections

Hi Terry,

Yes, I have read the Help/About notes right back to v2.24 and cannot find anything relevant to me relating to this problem (for example, I do have a current QRZ subscription).
This problem occurs with "live" QSOs which surely cannot be influenced by any UDP messages????

G3ZPB wrote: 10 Mar 2023, 16:23 Hi Terry,

Yes, I have read the Help/About notes right back to v2.24 and cannot find anything relevant to me relating to this problem (for example, I do have a current QRZ subscription).
This problem occurs with "live" QSOs which surely cannot be influenced by any UDP messages????

"Live QSO's" as in:

1. You manually enter the QSO?
2. The details are auto filled by clicking cluster?
3. The QSO's are coming from an external JT program?
4. The QSO is received from a data or CW program like FLdigi or MRP40?

Hi again Terry,

I may have fixed the problem.....the "secret" is in "Config/Info Providers/Config".
This was set to CTY..Clublog..External for "Realtime logging" and this has worked perfectly for years.
With v2.26, I need to set it to External..Clublog..CTY; now it appears to work AOK.

Mni tnx for your patience and help.