Log4OM

Win 10/ ver 2.6.1.0

I've a remote location where we have no internet - so no auto uploads of logs. I was there this weekend, and exported the ADIF file to take with me to upload to LoTW this week. In attempting to do so via TQSL - I'm getting the following error on all lines:

Invalid MODE (FT8,) on line xxxx <<<<just a log line number here I believe

Did I pull the WRONG type of ADIF file for this upload?

Is there a way to correct the ADIF I pulled to allow the upload?

The ADIF was too large to attach but is available if needed but here are the 1st and 2nd line of the file:

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

<ANT_AZ:1>0 <ANT_EL:1>0 <BAND:3>20m <CALL:5>VA3FF <CONT:2>NA <COUNTRY:6>Canada <CQZ:1>4 <DXCC:1>1 <EQSL_QSL_RCVD:1>R <EQSL_QSL_SENT:1>R <FREQ:9>14.075187 <GRIDSQUARE:4>FN03 <ITUZ:1>4 <LOTW_QSL_RCVD:1>R <LOTW_QSL_SENT:1>R <MODE:4>FT8, <MY_GRIDSQUARE:6>EM11IG <STATION_CALLSIGN:4>K5WV <PROGRAMID:7>LOG4OM2 <PROGRAMVERSION:7>2.6.1.0 <QSL_RCVD:1>R <QSL_RCVD_VIA:1>E <QSL_SENT:1>R <QSL_SENT_VIA:1>E <QSO_COMPLETE:1>Y <QSO_DATE:8>20200501 <QSO_DATE_OFF:8>20200501 <RST_RCVD:3>-05 <RST_SENT:3>+01 <SWL:1>N <TIME_OFF:6>022830 <TIME_ON:6>022745 <QSO_RANDOM:1>Y <SFI:1>0 <CLUBLOG_QSO_UPLOAD_DATE:8>20200515 <CLUBLOG_QSO_UPLOAD_STATUS:1>Y <EOR>

Thanks

Greg

See the other thread about this subject

Not sure the cause yet but we think it's the JT software sending spurious characters again!

Of more use would be to look at the Log4OM log file to see what the JT program has sent to Log4OM but be aware it's not every qso affected!

Hi Terry
Isn't the ADIF line above indicative of what is being saved in Log4OM? As that's is the ADIF generated by Log4OM.

For me at least I've not seen the issue of extra characters being generated by the JT software on any of the releases. I've never had upload problems (when I have connectivity). This same log file has been able to upload to Clublog (I tethered to my phone for connectivity) using the automatic upload process in Log4OM with no issues but I'm not sure if that's a fair comparison between the 2 processes of upload.

Greg

No Greg,
Just because that's what is saved it tells us nothing unless we know where it came from?

Had it been SSB, It would have been almost certain the comma was generated by Log4om during a manual logging of a QSO

With data modes the mode comes from the data program so unless you see an incoming FT8 QSO in the log file as FT8 without the comma then after it was saved it's FT8 with a comma then we would have to assume it's caused by Log4OM

However if the incoming FT8 QSO shows in the log file as FT8 with a comma, then it's originating from the JT software

Like I said the ADIF is meaningless

Still wondering that we have only 2 of this errors reported and we have meanwhile mor than 3K users here
in the forum. I´ve tried to reproduce this error but still all o.k. here at my side. Doing more than 80% of my
QSO´s in FT8 mode and always using latest JTDX and WSJT-X in companion with JTalert and latest V2 alpha.
Don´t find any "FT8," im my whole Log and i have worked with all of the V2 versions since we work on this.

Very misterious thing ...

bonjour a tous
j'ai le même problème, survenu depuis le 02/10
les envois de log vers qrz.com et eqsl.cc ce font avec une virgule
donc impossible de valider les contacts.

capture sur qrz.com

We have found out that there was something wrong with the modelist.
Please use Settings/Update Ressources/Modes to download a fresh one.

This should resolve this problem.