Import

F6EXV · Post by **F6EXV** » 18 Oct 2020, 19:55

Hi all
I have messed up with my 2 callsigns, trying to configure "the whole thing".
So I need to completely erase the log under Log4OM, and reimport an adif file.
The import menu screen now looks like the attached file.
The button that started the import has disappeared !
So I cannot import my adif file
Must I go through a whole reinstall ?
Thanks + 73
Paul F6EXV

PS The button still does no show up when I have selected an adif file to import...

Post by **G4POP** » 18 Oct 2020, 20:15

Check your screen resolution I think you set it to 125% if so reset it to 100%

F6EXV · Post by **F6EXV** » 19 Oct 2020, 07:14

Hi
No, that was not the' isuue.
I had to unisntall and reinstal, but now other problems have appeared...
Thanks + 73
Paul F6EXV

Post by **G4POP** » 19 Oct 2020, 07:27

F6EXV wrote: 19 Oct 2020, 07:14 Hi
No, that was not the' isuue.
I had to unisntall and reinstal, but now other problems have appeared...
Thanks + 73
Paul F6EXV

What other problems? and did you realise the 'Import' button will only show after you have selected an ADIF to import?

F6EXV · Post by **F6EXV** » 19 Oct 2020, 15:52

Hi Terry
Thanks for answer(s).
Using (or better said, trying to use) Log4OM + JTDX + JTAlert.
When completing a QSO with JTDX, I get a JTAlert error message. See attached.
BUT the QSO is indeed logged. So JTDX works OK with Log4OM. And JTAlert gets the callsigns OK from JTDX. So what is wrong ?

Also, still talking of import...and LoTW.
The manual says that if I want to upload to LoTW (when the program is closed) I have to set Type=LoTW to Queued. Explanation : a QSO has been selected to be uploaded to the online service.
Then, on setting up LoTW in the Exrternal services menu, it says a QSO is considered to be uploaded when the sent status is Requested, and it must match the confirmation tab setup... Or should I understand that if I want all the QSOs to be uploaded to LoTW, I should set the default LoTW to Q, and Log4OM will change it to Requested once it has been uploaded to LoTW ? Is this correct ?

Thanks + 73
Paul F6EXV

Post by **G4POP** » 19 Oct 2020, 16:00

F6EXV wrote: 19 Oct 2020, 15:52 Using (or better said, trying to use) Log4OM + JTDX + JTAlert.
When completing a QSO with JTDX, I get a JTAlert error message. See attached.
BUT the QSO is indeed logged. So JTDX works OK with Log4OM. And JTAlert gets the callsigns OK from JTDX. So what is wrong ?

In JTAlert there is a setting to change the time before a not logged message is generated change it to the highest value and the message will not happen.

The reason is that sometimes if Log4OM is doing another task the confirmation (Answer back) is not as fast as JTAlert would like!

The manual says that if I want to upload to LoTW (when the program is closed) I have to set Type=LoTW to Queued. Explanation : a QSO has been selected to be uploaded to the online service.
Then, on setting up LoTW in the Exrternal services menu, it says a QSO is considered to be uploaded when the sent status is Requested, and it must match the confirmation tab setup... Or should I understand that if I want all the QSOs to be uploaded to LoTW, I should set the default LoTW to Q, and Log4OM will change it to Requested once it has been uploaded to LoTW ? Is this correct ?

I think if you watch our YouTube tutorials confirmations 1, 2 & 3 all will become clear

F6EXV · Post by **F6EXV** » 19 Oct 2020, 16:27

The mystery continues... I only closed the whole set of programs, and reopened it. Now I no longer get the error message, but the QSO is logged twice ! What should I un tick, and where ??!!!

Post by **G4POP** » 19 Oct 2020, 16:31

Do not use ADIF MONITOR and UDP

As it states in our usr guide if you use both you will cause duplicates !!

Import

Import

Re: Import

Re: Import

Re: Import

Re: Import

Re: Import

Re: Import

Re: Import