Page 1 of 1

EME qso errors on LOTW confirmation via Log4OM

Posted: 17 Oct 2018, 20:53
by ta2nc
While importing LOTW confirmations from Log4OM
I noticed i was getting some errors as "not found" on my EME qsos.
I think, the mod that is kept on LOTW is JT65 instead of JT65B so, while downloading Log4OM can not find the qso information correct.

Maybe there should be something like JT65 = JT65B while downloading it from LOTW.

And second problem, on EME qsos the reports are not dB. Only "O" letter.
I can see it correct on my imported logs as "O" but on detail examination of the logs it seem like "+30"
I added the screenshot for it.


Re: EME qso errors on LOTW confirmation via Log4OM

Posted: 25 Oct 2018, 09:20
Sorry for delay
About "O" you can edit the configuration file adding that value to the list.

More details in my post here:

About mode you can use the same way on file "modelist.csv" (copy, rename, etc) as before...
but: actual modes in modelist.csv says:


That means you can correctly receive a JT65 mode and Log4OM will use/mark it as JT65 correctly (in ADIF too)
so it's strange you cannot get the correct mode from LOTW download (provided you have saved mode as JT65 in your log) as Log4OM, matching LOTW, is strictly use mode and doesn't allow "guessing" or defaults as modes are not fully interchangeable (and grouping them in block with default mapping from LOTW is out of scope)

Re: EME qso errors on LOTW confirmation via Log4OM

Posted: 30 Oct 2018, 17:02
by ta2nc
Hello Daniele,
I googled some and found that..
lotw uploading automatically converts all JT65x qso's to JT65 even they are JT65B on original adif file.
So while downloading it sends JT65 confirmation, not JT65B as it is on Log4OM. And thats why Log4OM does not allow to confirm this qso.

So is it possible to pass this problem with modifying modelist.csv?
If so how?

Re: EME qso errors on LOTW confirmation via Log4OM

Posted: 14 Nov 2018, 08:55
by ta2nc
I wrote to LOTW developers about this..
This is the answer i got from W4TV

he software may display them as different modes but in fact they are
different *SUB MODES*. If ADIF were fully consistent there would be
a very limited number of "MODES" - CW, AM, (SSB,) FSK, PSK, MFSK and
NPSK. All other "modes" are really submodes that are distinguished
by the data encoding and error correction.

Mode is defined by modulation:
CW - on/off keyed telegraphy
AM - amplitude modulated voice with or without a carrier,
single, double, independent or vestigial sideband
FSK - frequency shift keying (1 of 2 tones)
PSK - phase shift keying
MFSK - multiple tone frequency shift keying (1 of n tones)
nPSK - multiple PSK carriers (e.g. COFDM)

Some "sub modes" have "mode" status for historical reasons *but*
ADIF have made several effort to "clean up" the number of spurious
modes in the past and needs to do so again.

Logging software if free to display Mode/Submode or just Submode
to the user but should always export the data in Mode/Submode format
for interchange purposes.

From this.. I understand that somehow, log4om does not accept mode overwrites submode on confirmation download from LOTW:

Re: EME qso errors on LOTW confirmation via Log4OM

Posted: 18 Dec 2018, 14:36
We moved to MODE/SUBMODE in V 1.35 as LoTW was not correctly receiving ADIF 3 some time ago.
This should fix issue for new QSO, while i'm still trying to find the right way for old QSO, as they were sent as ADIF 2.x format and LoTW should be able to read them correctly (without flattening informations to standard modes)

Re: EME qso errors on LOTW confirmation via Log4OM

Posted: 20 Dec 2018, 19:45
by ta2nc
We had an emai traffic but for info i am adding the same comment also here.
I am uploading the qsos via tqsl application. Not Log4Om.
LOTW is getting them correct. But changing the JT65B information to JT65 on the fly because they assume both are same.
The problem is while downloading confirmation from LOTW to Log4OM.

Log4OM does not accept confirmation of JT65 tagged qsos, because it assumes it is different than jt65b.. Which is a submode and should be accepted by Log4OM.