Log4OM

Hello,

it seems that I have a problem with v2.26.0.0
I imported my QRZ.com adi file into Log4OM because on QRZ.com I had stored excactly 9 more QSOs compared to Log4OM and I did not know which were these 9 missing QSOs.
The 9 missing contacts got imported to Log4OM after setting the duplicates threshold to 320 seconds, before setting that value I had everything double after the import..
During the import there were also some corrections of CQ and QRZ Zones, States, DXCCs and so on but I guess this is correct because QRZ.com does not check the values.
here is a short extract from the log file:

[IMPORT ADIF FORM] Begin ADIF import task
WARNING: Callsign: HA7TM Date: 13.05.2021 18:41:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM H TO
Callsign: IW0UWE Date: 14.05.2021 12:24:00 Band: 10m Mode: FT8 DXCC has changed from 248 to 225
WARNING: Callsign: IK2ZEC Date: 20.05.2021 11:27:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM I TO
WARNING: Callsign: II0BIKE Date: 23.05.2021 18:36:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM IT TO
WARNING: Callsign: HB9CQL Date: 24.05.2021 18:05:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM CH TO
WARNING: Callsign: OM0ST Date: 24.05.2021 23:25:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM SK TO
WARNING: Callsign: IZ7GIT Date: 26.05.2021 10:58:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM IT TO
Callsign: R9FDI Date: 29.05.2021 09:53:00 Band: 10m Mode: FT8 DXCC has changed from 15 to 54
Callsign: R9FDI Date: 29.05.2021 09:53:00 Band: 10m Mode: FT8 ITU ZONE has changed from 20 to 30
WARNING: Callsign: IW9HEU Date: 31.05.2021 13:11:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM IT TO
WARNING: Callsign: DL7BO Date: 01.06.2021 12:18:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM DE TO
Callsign: RA0R Date: 01.06.2021 14:37:00 Band: 10m Mode: FT8 DXCC has changed from 54 to 15
Callsign: R8KAN Date: 02.06.2021 09:22:00 Band: 10m Mode: FT8 DXCC has changed from 54 to 15
WARNING: Callsign: DM5TI Date: 06.06.2021 11:23:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM D TO
Callsign: HA5MG/MM Date: 06.06.2021 11:44:00 Band: 10m Mode: FT8 DXCC has changed from 239 to 0
Callsign: HA5MG/MM Date: 06.06.2021 11:44:00 Band: 10m Mode: FT8 CQ ZONE has changed from 15 to 0
Callsign: HA5MG/MM Date: 06.06.2021 11:44:00 Band: 10m Mode: FT8 ITU ZONE has changed from 28 to 0
WARNING: Callsign: EG7RKB Date: 06.06.2021 14:48:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM 34 TO
WARNING: Callsign: F4CVA Date: 07.06.2021 14:07:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM FR TO
WARNING: Callsign: DF1DN Date: 08.06.2021 12:45:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM DE TO
WARNING: Callsign: YT1EB Date: 09.06.2021 21:17:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM SR TO
WARNING: Callsign: EA8AOC Date: 10.06.2021 14:12:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM A TO
Callsign: R9YQ Date: 14.06.2021 07:44:00 Band: 10m Mode: FT8 DXCC has changed from 54 to 15
WARNING: Callsign: CX7CO Date: 02.07.2021 16:03:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM MV TO
Callsign: R9WJ Date: 05.07.2021 10:37:00 Band: 10m Mode: FT8 DXCC has changed from 54 to 15
Callsign: R9WJ Date: 05.07.2021 10:37:00 Band: 10m Mode: FT8 CQ ZONE has changed from 17 to 16
WARNING: Callsign: OE4AHG Date: 07.07.2021 07:50:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM A TO
WARNING: Callsign: UA2DF Date: 09.07.2021 07:17:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM 39 TO
Callsign: UA2DF Date: 09.07.2021 07:17:00 Band: 10m Mode: FT8 DXCC has changed from 54 to 126
Callsign: R8KAN Date: 09.07.2021 08:09:00 Band: 10m Mode: FT8 DXCC has changed from 54 to 15
WARNING: Callsign: YT1EB Date: 09.07.2021 16:52:00 Band: 10m Mode: FT8 QSO STATE CHANGED FROM SR TO
Callsign: KP3U Date: 11.07.2021 13:14:00 Band: 10m Mode: FT8 CQ ZONE has changed from 4 to 5
Callsign: KP3U Date: 11.07.2021 13:14:00 Band: 10m Mode: FT8 ITU ZONE has changed from 8 to 6
Callsign: UW5EJX/MM Date: 14.07.2021 14:50:00 Band: 10m Mode: FT8 DXCC has changed from 288 to 0
Callsign: UW5EJX/MM Date: 14.07.2021 14:50:00 Band: 10m Mode: FT8 CQ ZONE has changed from 16 to 0
Callsign: UW5EJX/MM Date: 14.07.2021 14:50:00 Band: 10m Mode: FT8 ITU ZONE has changed from 29 to 0

I don't know if this is okay but I guess it is correct that a /MM station has no CQ and ITU Zone? If so this seems to be an error..

Another question:
After the import several distance values are incorrect as you can see in the attached screenshot..
It seems that the comma is not set before the last 2 digits.
When I open the contact and save it again it is corrected.
Is there any way how I can correct it for the whole log without opening every single QSO?

Also is it normal that there are 3 digits after the comma for FT8 contacts?

73s de DO9KW - Stefan

DO9KW wrote: 23 Jan 2023, 11:45
I don't know if this is okay but I guess it is correct that a /MM station has no CQ and ITU Zone? If so this seems to be an error..

Yes that looks OK and when you work a boat/ship and its /MM it must be at sea, not docked to a country so there is no DXCC for the oceans/seas!

Another question:
After the import several distance values are incorrect as you can see in the attached screenshot..
It seems that the comma is not set before the last 2 digits.
When I open the contact and save it again it is corrected.
Is there any way how I can correct it for the whole log without opening every single QSO?

These values probably came from the import, not calcualted by Log4OM

Easy to fix go to

QSO manager

Select the QSO's to be edited

Bulk edit the 'Distance' field to be empty/blank by using 'Single field update' (Field to update = Distand and check 'clear field' followed by 'Update'

Finally still with the QSO's selected/highlighted use 'QSO checks' tab in QSO manager to update the distance/bearing

Dont forget to un check 'Simulation' or nothing will be changed

All of these steps/updates are in our user guide

Also is it normal that there are 3 digits after the comma for FT8 contacts?

Yes because your using audio offsets to trequencies in FT8

Not a LOG4OM error so moving topic to User Support

That works, many thanks

Could this be a partly Log4OM error?
I tried to import an ADIF Backup from Log4OM where I did not make any QRZ.com import and there I had the same issues with wrong distance values (missing comma).
I am pretty sure I did not have this behaviour in v2.25.0.0

Is the mass update also available for missing operator names in my log because older QSO have - why ever - no names saved.
When I open a contact, click on refresh data the operator name appears and then I can save the contact but it would be great if I could do this somehow for all the missing names in one step.

I found another problem:
several stations from Hawaii operate from the USA (Florida for example) but when importing the data from QRZ.com (with the correct GRIDs from the WSJT-X log) to Log4OM the GRIDs got updated, is it possible to prevent this somehow? I only want to import the missing contacts and DON'T want to edit the existing ones in the Log4OM log.
But when having nearly 10000 QSOs in Log it is hard to say which are the ones that are missing..

73s