QSO Mode Olivia 8/250 problem

[HB9VQQ]

I just noticed a problem with logging Mode Olivia. The logged QSO was automatically imported by ADIF monitor from FlDigi.
The Mode and Report is correctly displayed in the "Recent QSO's (F7) overview window, but when I click on "Edit QSO" the mode is empty and Report has changed.

Here is a screen of the QSO with EA1IYK

Unbenannt.JPG (57.51 KiB) Viewed 4242 times

Same QSO when I click on "Edit QSO", notice Mode is empty and Report is wrong

Unbenannt1.JPG (55.65 KiB) Viewed 4242 times

I believe this problem is because there is a space in "Olivia 8/250", this is the way FlDigi logs the QSO Mode:

<FREQ:8>7.071004<CALL:6>EA1IYK<MODE:12>OLIVIA 8/250....

Logging the same QSO manually without a space resolves the problem.

73
Roland

[IW3HMH]

Hi Roland,
in ADIF protocol, OLIVIA submode is registered with a space on it
http://www.adif.org/310/ADIF_310.htm

Even if it's shown, when editing the QSO the mode is searched into our mode list file that is the source for the drop down menu.
A space on it will prevent mode from being detected. You can create a copy of modelist.csv called modelist_user.csv and editing the mode name in the ADIF columns

I suppose other applications could have issues with modes reported with different formats

[HB9VQQ]

Okay Daniele, understood. I guess the modelist_user.csv will not be overwritten when upgrading to a future release.
I noticed there are 3 coloumns

Unbenannt.JPG (39.67 KiB) Viewed 4218 times

The 3.x SUBMODE coloumn already has the spaces in there. I guess I need to change the Modes in "//log4om Mode" coloumn right ?

Thanks
Roland

[IW3HMH]

Log4OM more is what it's shown on the dropdown menu.
2nd column is the mode Log4OM will READ from ADIF 2.x
3rd and 4th columns are the modes Log4OM will read from ADIF 3.x (mode and submode)

Obviously what is READ is also what is WRITTEN as internal mode (first column) is exported in ADIF following the same rule
That means adding a new mode OLIVIA4/125 exported (and then imported) without spaces will be shown and handled correctly, by Log4OM and his backup/restore points, but can be rejected from external services that receive the ADIF from Log4OM itself

If the application is sending mode as V2, without submode, you can have OLIVIA4/125 on V2 column (that is used for import) and OLIVIA 4/125 in the ADIF 3 columns, as Log4OM talks with external sources only in V3 (backup is V3 too)
If application is working with ADIF V3 there is no way, they should comply with ADIF standard on their side.

_user files have priority over default files and not deleted by new installs

[HB9VQQ]

OK, got it.
Changed first coloumn and added a space. Working now.

TU Lele
73