Log4OM

Version 2.6.1.0
Windows 10 Pro

Suddenly the program is building a faulty ADIF. The "mode" field has a comma (",") at the end, and LoTW rejects it. Example it will send <Mode:4>FT8, instead of <Mode:3>FT8 or <Mode:3>CW, instead of <Mode:2>CW

LOTW rejects the upload:

Picture removed due to sensitive information

Here is a sample of an ADIF with this error.

#++++++++++++++++++++++++++++++++++++
# Log4OM 2 by IW3HMH version 2.6.1.0
# http://www.log4om.com
# created: Tuesday, October 6, 2020
#++++++++++++++++++++++++++++++++++++

<ADIF_VERS:5>3.1.0 <PROGRAMID:7>Log4OM2 <PROGRAMVERSION:7>2.6.1.0 <eoh>

Edited due to sensitive information

<ADDRESS:64>3<PROGRAMID:7>LOG4OM2 <PROGRAMVERSION:7>2.6.1.0 <QSL_RCVD:1>N <QSL_RCVD_VIA:1>E <QSL_SENT:1>N <QSL_SENT_VIA:1>E <QSO_COMPLETE:1>Y <QSO_DATE:8>20201006 <QSO_DATE_OFF:8>20201006 <RST_RCVD:3>+04 <RST_SENT:3>-06 <SWL:1>N <TIME_OFF:6>052230 <TIME_ON:6>052000 <TX_PWR:3>100 <K_INDEX:1>3 < <QSO_RANDOM:1>Y <SFI:2>72 <CLUBLOG_QSO_UPLOAD_DATE:8>20201006 <CLUBLOG_QSO_UPLOAD_STATUS:1>Y <HRDLOG_QSO_UPLOAD_DATE:8>20201006 <HRDLOG_QSO_UPLOAD_STATUS:1>Y <QRZCOM_QSO_UPLOAD_DATE:8>20201006 <QRZCOM_QSO_UPLOAD_STATUS:1>Y <EOR>

Neglected to mention.....

This first occurred several days ago. I reinstalled V2.6.1.0 and the problem vanished.

It happened again this evening. I reinstalled V2.6.1.0 and the problem vanished again.

(I am running 2.6.1.0 because my computer has the "locked GUI" issue with versions 2.7 and higher.)

Someone else had this and we think its a recurrence of the JT program occasionally sending bogus characters, try reinstalling the JY software.

BTW we have warned users how dangerous it is to publish un edited log files and images on the forum so I will edit your post

I also got it running N1MM+ in CW.

In that instance (in this weekends California QSO party) the ADIF mode entry is "<MODE:3>CW,"

K0HB wrote: 07 Oct 2020, 02:55 I also got it running N1MM+ in CW.

In that instance (in this weekends California QSO party) the ADIF mode entry is "<MODE:3>CW,"

Something local with your keyboard set up?

Hi Terry, have downloaded a portable 2.6.1.0 and setted it up for DL0AK (our club call). Logged FT8 QSO and it looks
fine in F7 Tab but when exporting i have the comma also here. But not in later versions of V2. Looks like this failure
is on V2.6.1.0 only.

that seems really strange an issue in 2.6.1.0 only...
that part is widely consolidated...
weird...
investigating

IW3HMH wrote: 07 Oct 2020, 10:52 that seems really strange an issue in 2.6.1.0 only...
that part is widely consolidated...
weird...
investigating

No no no! the problem is in latest release also

Looks like yo´re right. Have exported ADIF from latest A and also the comma is in.


Now i have to check all contacts with FT8 which was not uploaded to LotW. Needs a while.

Have checked the LotW from the 2 tested contacts. My setup in 2.6.1.0 and latest A was to set all sent status
to NO but after closing tey where set to Requested. Maybe a corrupt upload to the LotW with the damned comma.

Found this only in my QSO´s from today and not in the older ones where i worked with JTDX instead of WSJT-X
today. I have also worked with installed Version for DF5WW and portable one for DL0AK and have this error only
in the portable versions. In the installed one all looks fine for the LotW send status "YES" ....

Another thing ist that i worked all 2m contacts with WSJT-X via JTalert but in the installed version no comma
in FT8 in the Mode field. It´s a mystery ....