Log4OM

Friends
I have noticed this behaviour and it just happened to me on 20m
I was on 14.205 and log4OMNG 2.2 recorded same but when uploaded to ClubLog and QRZ, it was changed to 14.200 thats a 5KHz difference.
Any reasons for that?
14.217 changed to 14.210

Not yet, think Lele is working on that ...

4s6ryd wrote: 29 Jan 2020, 14:52 Friends
I have noticed this behaviour and it just happened to me on 20m
I was on 14.205 and log4OMNG 2.2 recorded same but when uploaded to ClubLog and QRZ, it was changed to 14.200 thats a 5KHz difference.
Any reasons for that?
14.217 changed to 14.210

This is the problem https://forum.log4om.com/viewtopic.php? ... =10#p25282

Will there be a fix for this or do we have to change any settings ?

Please stay tuned and check out this post, Lele is a programmer but not a wizzard.
First thing is to check what the problem is with QRZ. If he find out what the problem
is it will be fixed soon i think.

First thing is to check what the problem is with QRZ

The problem is with the Log4OM generated ADIF file and needs to be fixed.

Thank you. Appreciate what you guys are doing.
As a temporary measure, disabled automatic upload to QRZ.COM, CLUBLOG ETC.
Will wait until we have a solution
73

Just for clarification QSO/QSL matching by any of the external DB's is not based on the actual frequency logged. It is based on the reported Band among other criteria like date time callsign etc..

That's why I consider this bug rather cosmetic than critical, however it needs to be fixed no question.


73
Roland

Is this issue solved with the latest release 2.3 ?

4s6ryd wrote: 05 Feb 2020, 02:29 Is this issue solved with the latest release 2.3 ?

yes