FLdigi mode recording

Post Reply
User avatar
G4DWV
Old Man
Posts: 445
Joined: 11 Sep 2014, 16:02

FLdigi mode recording

Post by G4DWV »

I had my first Olivia QSO yesterday and I noticed that the mode was not sent to LOg4OM. I had to enter it manually. Am I doing something wrong or is this normal behaviour.
Take care and keep safe.
You've never known happiness until you're married; but by then it is too late.
User avatar
AE6DS
Advanced Class
Posts: 31
Joined: 07 May 2020, 22:00

Re: FLdigi mode recording

Post by AE6DS »

If you are using the FLDigi log button, Log4OM picks up the QSO info by following an adif file. Setup is on p 190-191 in current user manual.

In my experience, you will need to follow the temporary log file at c:\Users\<login>\fldigi.files\temp\log.adif, not the permanent logbook.adi. The latter doesn’t have ADIF compliant SUBMODE entries so some modes like OLIVIA will be logged incorrectly by Log4OM. If you are only using PSK31 either file will work.

Dale
User avatar
G4DWV
Old Man
Posts: 445
Joined: 11 Sep 2014, 16:02

Re: FLdigi mode recording

Post by G4DWV »

Hi Dale,
Thanks for your informative post.
Take care and stay safe.
You've never known happiness until you're married; but by then it is too late.
k4rva
Novice Class
Posts: 6
Joined: 14 Jan 2023, 15:21

Re: FLdigi mode recording

Post by k4rva »

I am having trouble with QSLs coming back from LOTW that do not match the mode in Log4OM, specifically OLIVIA from LOTW does not match OLIVIA8/250 as shown in Log4OM.

I have Log4OM configured via the ADIF Monitor settings to import from the temporary FLDIGI log, c:\users\steve\fldigi.files\temp\log.adif -- the log that correctly records MODE and SUBMODE.

After an Olivia QSO is imported from FLDIGI into Log4OM, it shows "OLIVIA8/250" on the Recent QSOs grid, as well as in the QSO details when I double-click the QSO in Log4OM.

I exported that one QSO from Log4OM to an ADIF file, before uploading it to LOTW, and it is showing the correct MODE and SUBMODE.

Code: Select all

<CALL:5>NW7US <BAND:3>15m <MODE:6>OLIVIA <QSO_DATE:8>20231031 <TIME_ON:6>190400 <A_INDEX:2>12 <ANT_AZ:1>0 <ANT_EL:1>0 <STATE:2>OH 
<CONT:2>NA <COUNTRY:3>USA <CQZ:1>5 <DISTANCE:6>1782.7 <DXCC:3>291 <EQSL_QSL_RCVD:1>N <EQSL_QSL_SENT:1>N <FREQ:9>21.072500 
<GRIDSQUARE:6>EM89aq <ITUZ:1>6 <LOTW_QSL_RCVD:1>N <LOTW_QSL_SENT:1>N 
<SUBMODE:12>OLIVIA 8/250 <MY_COUNTRY:24>United States Of America <MY_CQ_ZONE:1>4 <MY_DXCC:3>291 <MY_GRIDSQUARE:6>DM78pv <MY_ITU_ZONE:1>7 
I upload the QSO to LOTW from Log4OM, and the MODE shows OLIVIA (not OLIVIA8/250) on the LOTW website. After the other station uploads the QSO, I download the new confirmation from LOTW in Log4OM, and it seems that the MODE "OLIVIA" does not match the MODE stored in Log4OM, which is showing OLIVIA8/250.

Code: Select all

Parsing FULL ADIF file...
ADIF FULL document parsed: 1 qso found.
QSO NOT FOUND : NW7US|10/31/2023 7:04:00 PM|15m|OLIVIA
LOTW UPDATING STATISTICS...
LOTW END
I'm sure it's something I'm doing wrong, or something I have setup incorrectly. Any thoughts or ideas?

Cheers,
Steve K4RVA
k4rva
Novice Class
Posts: 6
Joined: 14 Jan 2023, 15:21

Re: FLdigi mode recording

Post by k4rva »

I just had this same issue with an another Olivia contact, but this time it was with with eQSL. I exported from Log4OM to eQSL, and then later imported from eQSL to Log4OM via the QSL Manager dialog in Log4OM.

Here's what the import log from eQSL to Log4OM showed:

QSO NOT FOUND: VE3FGU|11/4/2024 6:09:00 PM|10m|OLIVIA

Log4OM is showing 'MODE=OLIVIA' and 'SUBMODE=OLIVIA 8/250' (with a space before the 8/250) when I export from Log4OM to an ADIF file. But eQSL seems to only record 'OLIVIA' as the MODE, so when I import back from eQSL to Log4OM, I guess the mode is not matching?

The relevant bits of an ADIF export from Log4OM:

<CALL:6>VE3FGU <BAND:3>10m <MODE:6>OLIVIA <QSO_DATE:8>20241104 <TIME_ON:6>180800 <EQSL_QSLSDATE:8>20241104 <EQSL_QSL_RCVD:1>N <EQSL_QSL_SENT:1>Y <GRIDSQUARE:4>EN92 <LOTW_QSLSDATE:8>20241104 <LOTW_QSL_RCVD:1>N <LOTW_QSL_SENT:1>Y <SUBMODE:12>OLIVIA 8/250 <MY_GRIDSQUARE:6>DM78pv <NAME:4>Mike <STATION_CALLSIGN:5>K4RVA <PROGRAMID:7>LOG4OM2

I assume Log4OM is not accepting it because the MODE does not match? Could it be something else like grid square, etc?

Has anybody else seen this or found a way to get the MODES to match?

Cheers,
Steve K4RVA
ve3wej
Old Man
Posts: 163
Joined: 31 Aug 2017, 00:11
Location: Ontario

Re: FLdigi mode recording

Post by ve3wej »

I thought the correct mode for submode olivia was mfsk not mode olivia but I did notice YOUR entry had olivia8/250 and not olivia 8/250
as shown in the adi file could that be the difference

more confusion for eqsl I am sure
Dave ve3wej / ve3ie
ve3wej
Old Man
Posts: 163
Joined: 31 Aug 2017, 00:11
Location: Ontario

Re: FLdigi mode recording

Post by ve3wej »

sorry also, did you manually add olivia into log4om?? i dont even show it as an option in mine
Dave ve3wej / ve3ie
k4rva
Novice Class
Posts: 6
Joined: 14 Jan 2023, 15:21

Re: FLdigi mode recording

Post by k4rva »

ve3wej wrote: 07 Nov 2024, 01:49 I thought the correct mode for submode olivia was mfsk not mode olivia
I'm not sure, but Fldigi appears to be storing <MODE:6>OLIVIA <SUBMODE:12>OLIVIA 8/250 in the log.adif file located in the fldigi.files/temp folder. And an ADIF export of the same QSO from Log4OM (after Log4OM imports the QSO via the ADIF Functions feature) shows <MODE:6>OLIVIA <SUBMODE:12>OLIVIA 8/250 as well.

But eQSL and LotW appear to be recording the MODE as OLIVIA, so when I download the return QSL from either of those services, it does not match what is recorded in Log4OM, therefore they do not get marked as 'Received' for eQSL or LotW.

ve3wej wrote: did you manually add olivia into log4om??
No, they are listed in the drop Mode selection field. I'll see if I can attached a screen shot...
Screenshot 2024-11-08 104731.png
Screenshot 2024-11-08 104731.png (48.98 KiB) Viewed 623 times
Post Reply