Question about how the adif import works

[N5INP]

Using the JT65 software I've been running (JT65-HF HB9HQX Edition), it can either export only the last logged QSOs or the entire log for a backup. I do both, except I only use the the last logged QSO adif file to import into Log4OM every few days. Yesterday I made a mistake and imported the entire backup adif file from the JT65 program. I thought I made a big mistake because I was worried that it would overwrite all the logged JT65 QSOs I had imported into Log4OM before and all the additional info that I added to each JT65 QSO after importing into Log4OM would be lost (such as QSO sent status, LoTW status and so on). However - that did not happen. The only thing that happened was that the last new QSO was added, just as I wanted. It did not do anything to the other entries already there.

So it seems I did not really understand what the adif import logic really was. Is it true that it only "adds" new information, and does not "overwrite" information already existing? I just want to understand how it works better. I may have a follow-up question also.

Thanks.

[G4POP]

In Log4om we don't allow duplicate QSO's to be imported

So if during the import a QSO is found with the same date, time, call sign, band and mode we reject it and don't import it.

A list of duplicates found will be seen in the import window and the list can be saved as a text file.

If you used WSJT-X and JTAlert the QSO would automatically be forwarded to Log4om and then you would not need to do the ADIF import

[N5INP]

In Log4om we don't allow duplicate QSO's to be imported

So if during the import a QSO is found with the same date, time, call sign, band and mode we reject it and don't import it.

Oh good, that's what I wanted to know.

If you used WSJT-X and JTAlert the QSO would automatically be forwarded to Log4om and then you would not need to do the ADIF import

Yes, I know, but WSJT-X has other usability issues that are not as good as JT65-HF HB9HQX Edition. However, I am using WSJT-X for JT9 as the other program cannot do that mode.

[NN7D]

Mike,

There is also a version of JTAlert which will work with JT65-HF, and as Terry points out will automatically log qso's into Log4OM. It interfaces very will.

I believe that when you install JTAlert, all versions are installed, so you may have it now. Go to All Programs and expand the JTAlert folder and you should see versions for HB9HQX, WSJT-X and JT65-HF.

A bit off topic, but what do you find lacking in WSJT-X? I have found that WSJT-X decodes about 15% more signals than any of the other versions of JT65 software.

Hope this helps,

Doug
W7DRM

[N5INP]

Mike,

There is also a version of JTAlert which will work with JT65-HF, and as Terry points out will automatically log qso's into Log4OM. It interfaces very will.

I believe that when you install JTAlert, all versions are installed, so you may have it now. Go to All Programs and expand the JTAlert folder and you should see versions for HB9HQX, WSJT-X and JT65-HF.

OK I'll check it out.

A bit off topic, but what do you find lacking in WSJT-X? I have found that WSJT-X decodes about 15% more signals than any of the other versions of JT65 software.

The HB9HQX edition allows more configuration such as custom colors for stations already worked and other conditions, and it has it's own built-in log editor which is very convenient to have available on the spot.

How did you objectively determine that it decodes (about) 15% more signals? That seems like a very hard comparison to make given all the fluctuations involved in receiving HF signals. Just curious.

[NN7D]

Hi Mike. I just ran both software programs simultaneously, so they were decoding the same signal. I did several 10 minute runs at different times of the day, different bands. Just counted the number of decodes for each minute with each software. Then added them up. WSJT-X just decodes weaker signals and signals which are adjacent to other stronger signals, which the other programs missed. You might give it a try. Your results might vary, but I consistently got around 15% more decodes with WSJT-X. And with JT-65, its no fun getting half way through a QSO and losing it to a no-decode.

Doug

[N5INP]

Hi Mike. I just ran both software programs simultaneously, so they were decoding the same signal. I did several 10 minute runs at different times of the day, different bands. Just counted the number of decodes for each minute with each software. Then added them up. WSJT-X just decodes weaker signals and signals which are adjacent to other stronger signals, which the other programs missed. You might give it a try. Your results might vary, but I consistently got around 15% more decodes with WSJT-X. And with JT-65, its no fun getting half way through a QSO and losing it to a no-decode.

Doug

OK thanks, I've already got WSJT-X for JT9 so I'll try it for JT65. I also want to run JT65 on two different bands at the same time anyway, as I have two HF radios and I'm putting up another ant. for 17 & 15 m for the other radio.