ADIF Monitor - is it supposed to be?

General discussions V2
Post Reply
User avatar
sq9jxb
Advanced Class
Posts: 61
Joined: 14 Jan 2020, 16:00
Contact:

ADIF Monitor - is it supposed to be?

Post by sq9jxb » 19 Jan 2020, 13:20

Welcome

2 hours ago I started the program and so far it is happening:

Image

I did not import from an adif file
The original log file has 3912 QSOs and as you can see this number is increasing.

Why?

Is this the effect of enabling the Adi Monitor option?

CPU usage from 35 to 65%.

Regards

EDIT:

start of scan - 11:30
end of scan - 13:28

Log had 3912 QSO, now has 5450.
Most QSOs are duplicates.
Why?
Log4OM 2.4 , JTDX 2.1.0.x64, Windows 10 x64
Yaesu FT-897D, Icom IC-735, Musb1017/Musb2232FK , ATU-150 , LDG-AT-200Pro
SGC PowerClear, EMU0202
.........................................
73!
Jan SQ9JXB

User avatar
IW3HMH
Site Admin
Posts: 2653
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: ADIF Monitor - is it supposed to be?

Post by IW3HMH » 19 Jan 2020, 15:44

I need some more informations on that.
What your log contained before?
What is the content of the file being scanned?
If QSO are dupe, is the file being scanned containing QSO up to SECONDS? are your QSO containing QSO up to seconds?

Without an ADIF of some kind and without some more info it's pretty impossible to provide a solution to a problem.
It may be a bug, an issue on your ADIF, an issue on your previous log... everything

If you want we can check, but i need some more info
Daniele Pistollato - IW3HMH

User avatar
sq9jxb
Advanced Class
Posts: 61
Joined: 14 Jan 2020, 16:00
Contact:

Re: ADIF Monitor - is it supposed to be?

Post by sq9jxb » 19 Jan 2020, 16:20

Hello Danielle

The scanned file is wsjtx_log.adi from JTDX
  part of the saved file from Log Viewer is attached

Regards

P.S. I can't add the wsjtx_log.adi file to the attachment.

I can send it to your email if you provide it.
Attachments
log-adif-monitor.txt
(152.53 KiB) Downloaded 32 times
Last edited by sq9jxb on 19 Jan 2020, 16:40, edited 1 time in total.
Log4OM 2.4 , JTDX 2.1.0.x64, Windows 10 x64
Yaesu FT-897D, Icom IC-735, Musb1017/Musb2232FK , ATU-150 , LDG-AT-200Pro
SGC PowerClear, EMU0202
.........................................
73!
Jan SQ9JXB

User avatar
IW3HMH
Site Admin
Posts: 2653
Joined: 21 Jan 2013, 14:20
Location: Quarto d'Altino - Venezia (ITA)
Contact:

Re: ADIF Monitor - is it supposed to be?

Post by IW3HMH » 19 Jan 2020, 16:36

in the part of log you sent me i can see the ADIF was imported (fully i presume) and parsed for awards.
Once done, each qso was analyzed and data-enriched:

Performing QSO search on callsign UA0FO -> indicate that this QSO is being analyzed
[HAMQTH] Search start on UA0FO (originally UA0FO) -> Start of HAMQTH search
[HAMQTH] Search completed -> end of HAMQTH checks
QSO search on callsign UA0FO completed -> End of analisys process (that include HAMQTH, clublog, clublog exceptions, CTY file and some other internal logics)

Once done that, Log4OM tries to save the QSO:
[ADIF MONITOR] C:\Users\sq9jx\AppData\Local\JTDX\wsjtx_log.adi QSO not saved: UA0FO|01.11.2018 08:00:00|17m|FT8. Skipped

QSO not saved means routine cannot write it (usually is dupe, but in INFO mode on log you don't have further informations)

Then the software starts another QSO analisys.

During those steps the most time consuming activity is due to external HAMQTH search (with switch to QRZ.COM in your case when callsign is not found) so it's taking 0.7-2 seconds for each QSO to make a full roundtrip. about dupes can you kindly send me the ADIF of 2 QSO that are dupe?
Daniele Pistollato - IW3HMH

User avatar
sq9jxb
Advanced Class
Posts: 61
Joined: 14 Jan 2020, 16:00
Contact:

Re: ADIF Monitor - is it supposed to be?

Post by sq9jxb » 19 Jan 2020, 17:09

Hi Danielle

I understand, but why are QSO duplicates created?

I can't send them because I deleted the entire log and loaded from the beginning the log exported from Log4OM V1 in ADIF 3 format.
A few hours with the program and I had enough.
ADIF Monitor should scan wsjtx_log.adi and nothing more, not create duplicates.
This function is not supposed to work as it currently does.
The proposal to log in from JTDX to Log4OM V2 with the ADIF option enabled Monitor does not solve the problem but creates a new one.

Regards
Log4OM 2.4 , JTDX 2.1.0.x64, Windows 10 x64
Yaesu FT-897D, Icom IC-735, Musb1017/Musb2232FK , ATU-150 , LDG-AT-200Pro
SGC PowerClear, EMU0202
.........................................
73!
Jan SQ9JXB

Post Reply