eQSL not populating comments?

[m0odh]

I cant see any options in WSJT-x to upload to eQSL. I have setup the interface so it passes QSO to Log4OM and it gets logged and passed to eQSL from there.

I've just done another test on FT8 and can reproduce the original problem. ie that QSOs logged via WSJT-x do not populate the QSLMSG field in Log4OM, see below;

Screenshot 2022-10-10 174335.png (157.52 KiB) Viewed 732 times

I assume that if WSJT-x is using an ADIF file to transfer data to Log4OM could it be overwriting the QSLMSG with a blank record? Struggling to figure out why it works from Log4OM and not from WSJT-x.

[G4POP]

No! If there is no QSLMSG provided by the FT8 program it is saved and uploaded as is.

Remember the FT8 program is saving direct to the sqlite database

Get WSJT to add a QSLMSG

[m0odh]

Ok, so if WSJT-x does not provide a QSLMSG, then Log4OM will not put in the default message either?

Remember the FT8 program is saving direct to the sqlite database

So this bypasses the QSO front end, and therefore bypasses the code that adds the default QSL text?

I'll take another look at WSJT-x, but not seeing any easy way to add more fields to the QSO, so will log another call with them as well.

[G4POP]

Ok, so if WSJT-x does not provide a QSLMSG, then Log4OM will not put in the default message either?

Remember the FT8 program is saving direct to the sqlite database

So this bypasses the QSO front end, and therefore bypasses the code that adds the default QSL text?

I'll take another look at WSJT-x, but not seeing any easy way to add more fields to the QSO, so will log another call with them as well.

You could edit the QSO's after they are received from WSJT by adding the QSLMSG then do a manual upload instead of automatic

That said with the automatic nature of an FT8 QSO is the QSLMSG relevant or even noticed by the other party who probably receives hundreds of worked stations on FT8 by his robot software.

[m0odh]

Hi Terry, You raise a good point with this;

That said with the automatic nature of an FT8 QSO is the QSLMSG relevant or even noticed by the other party who probably receives hundreds of worked stations on FT8 by his robot software.

It works fine when logging QSOs in Log4OM2, and those would naturally be SSB and more personal.

FT8 probably not a big deal, it just makes my QSL cards a little nicer.

You're right though, for FT8 this is not the end of the world.

[KI5IO]

As many OMs have noted: FTxx modes are just a "contact collecting mode".

Not really a mode for a QSO that then leads to the nice QSO Comments such as from SSB or CW.