Log4OM

Hi folks
When working stations on zone 18, 19, 3 and 4 QSOs aregistered always as Russian Asiatic 17 and USA as zone 5.
Most of the times shows on the entrance windown the right zone but goes to the log 17 for Asiatic Russia and 5 for USA.
Can that be fixed?
Oms PY5EG

As always when you see this type of issue provide specific call signs so that we can check!

Thanks Terry for usual prompt ansewr.
I will do that but I can say that Russians from zone 18, or 19 shows always as zone 17. Some times on the log in window shows 18 or 19, but when you insert on the log becomes zone 17
Thanks
Oms PY5EG

bonjour
the problem has been present with me since version 2.09
post open in the section: Language / French


https://forum.log4om.com/viewtopic.php?f=38&t=5908

73

Hello
I confirm the problem with K0PT :

Log4om indicates ITU = 7 and CQ = 4
while KOPT is in ITU = 8 and CQ = 5 as indicated on its QRZ.com page ....
73

Hi Daniel,

Bad news:
For many calls it's not possible to determine the correct CQZ and/or ITUZ. Either a callsign block (e.g. K0) is in more than one zone, or the owner moved, etc. This is the case for most of the US and UA callsigns.

Good news:
You easily can fix this in Log4OM if you're using e.g. QRZ.com (but not all zones are correct there as well).
Go to Configuration -> Info providers -> Configuration and change the sequence under "REALTIME LOGGING". Most probably in your configuration you will have CTY set as priority 1.

In my configuration, I put Clublog on top, followed by ExternalSource (which is QRZ.com in my case) and last is CTY. Don't forget to save and apply any changes. If you check again with K0PT, you will see now CQZ 5 and ITUZ 8.

73,
Claus

Hello Claus
Thank you very much , indeed by adjusting as you show there is no more error ...
Thank you so much
73

bonjour a tous
je viens de mettre la meme configuration, mais cela ne fonctionne toujours pas chez moi

Laurent,

Your recent post reflects your QSO input from an FTxx APP and you noted above that you have observed this since V 2.9.0.0 ...

I have observed and experience the same thing with some anomaly with the data input from an FTxx APP to Log4OM V2.

ITU and CQ zones appear FB in Main UI, but once the QSO is 'saved' the resulting ITU & CQ zone gets changed.

What Dan and Claus seemed to be addressing were manually input callsigns or callsigns input from a cluster or band-map click.

Data coming from the FTxx APPs is somehow or another doing something different.

Hello
Yes Nolan
I confirm that the tests carried out here were done by manually typing the call, I did not test by validating this same callsign from an FTxx digital mode interface, but if necessary I can give it a try…
73