Hi Jacques, Please note that wsjt-x can only populate those fields that it knows. See what is presented in the QSO logging window. For sure e.g. QSL info is not one of those, unless you have typed tha

#adiFiles

Hello I went to look at the wsjtx log and noted that after a date no more data was registered just call etc did I do something inadvertently ? Cheers F1VEV Jacques

#adiFiles

does wsjtx_log.adi populate. is ther more than one wsjt folder? Dave Garber VE3WEJ / VE3IE

#adiFiles

Do a search for the following in File Explorer - *.adi* This will list every adi file found on the computer. Click on view details and it will show you folder locations and time/date. Sort on date mod

#adiFiles

Hi Reino Then that confirms that it all come from when I rebuild the wjstx log after a computer crash and then now the lesser populated fields are original. Thank you

#adiFiles

Hello thank you for your input I wish I could upload a screen shot but apparently I cannot Dave : yes does wsjtx_log.adi populate ? yes it does but only Band and Call, QRG Grid Mode My square RST r an

#adiFiles

well that was it I merged a call from logbook into wsjtx log and all fields were populated compared to the auto entry made by wsjtx mistery solved then ? I would still like to hear what is populated i

#adiFiles

Hi Dennis, WSJT-X logs gridsquares as they are available. E.g. in EU VHF contest messages do contain six character gridsquares. It seems that more than six is not supported. So just use the ACLOG adif

#adiFiles

WSJT-X only logs 4 digit gridsquares. I am rebuilding my log from ACLOG adif file. Simple enough. But there are a lot of entries that have 6 digit gridsquares. Do I need to trim those to 4 in order fo

#adiFiles

Hi Dennis & Reino When WSJT-X reads "wsjtx_log.adi" at startup, it only takes 4 first characters of gridsquare. This is the relevat code line from "WorkedBefore.cpp" ... worked.emplace (call.toUpper (

#adiFiles

Laurie..... Thanks. You are the man!!! 73, Jim

#adiFiles #Alinco #logging

I have to stations with identical setups --- K3, WSJT-X, JTAlert, and DXKeeper. On one station, W2SM, the contacts automatically upload to LoTW once I hit the "log: button. On the other, ZF2LC, they o

#adiFiles #Alinco #logging

Hi Jim, The difference I see is that for one you are in W2 the other bin ZF2. Maybe it’s your communications ability at each location. Phil GM3ZZA Sent from Mail for Windows Sent: 08 March 2022 20:13

#adiFiles #Alinco #logging

If you are using JTAlert to log QSOs to DXKeeper than visit the JTAlert Settings window, "Logging -> DXLab DXKeeper" section and enable the "Instruct DXKeeper to upload each new QSO to LoTW" checkbox.

#adiFiles #Alinco #logging

I wish everyone would use your software, I can't do without it ! Thank you, thank you, thank you !

#adiFiles #Alinco #logging

Phil, No, that is not the case. My W2SM location action was the same as the ZF location until I had to reload from scratch all my software at W2 because of a lightening strike that took out the comput

#Alinco #adiFiles

This box pops up every time I boot up the program : Error Scanning ADIF log Invalid ADIF header In settings when I try to Rescan ADIF log, same message. Any suggestions ? Thank Hank K2HJB

#adiFiles

You have a very old version that has a bug. You need to keep up with the latest version. 73 -Jim NU0C K2HJB@... wrote:

#adiFiles

Simply upgrading to the latest version won't correct the error in the wsjtx_log.adi file's header unless the file is deleted so that the software creates a new file with the correct header. If you wan

#adiFiles

I’m running the latest version of WSJT Where do I find that file ( eh-eoh) to change ? I’m not a computer guru so If it’s complicated, I’ll live with it. Thanks Hank

#adiFiles