Page 1 of 1

LOTW synchronization

Posted: 19 Aug 2013, 21:38
by K0HB
When I try to download new QSLs from LoTW I have no success.

The program (Log4OM POST OFFICE) gives the following results:

Begin ADIF generation request
ADIF request accepted
ADIF document downloaded
ADIF document parsed: 0 qso found

Then a message box, "Operation Completed"

In other words, the process returns no new QSL from LoTW, even though I know that there are some at the LoTW site that have not been downloaded.

Re: LOTW synchronization

Posted: 19 Aug 2013, 22:27
by K7PT
What is the starting date you want to download from, how many days.

If you had a new LOTW match 3 days ago and set the staring date of 2 days ago, it will return zero (0) matches because you have no new matches in the past two days.

You can set the starting date back as far a you want and it will download them not harming a thing. :roll:

Re: LOTW synchronization

Posted: 20 Aug 2013, 03:17
by K0HB
Well, I poked around and poked around and poked around with no positive result.

So decided to re-enter all the parameters, one at a time.

When I re-entered the password, suddenly the process worked, so seems I had a bad password.

Might want to look at the code, because that should have spawned "bad password" error. Instead it just reported "Process Completed".

Re: LOTW synchronization

Posted: 20 Aug 2013, 10:11
by IW3HMH
I will check that but I will give all informations that tqsl gives to me.
What version of tqsl are you using?

Re: LOTW synchronization

Posted: 20 Aug 2013, 17:27
by K0HB
Last version released.... 1.14.xx

Re: LOTW synchronization

Posted: 01 Sep 2013, 02:36
by K0HB
I am now using tQSL v 2.0 Beta RC2.

When UPLOADING to LoTW, everything works as expected.

When DOWNLOAD from LoTW, you must enter your password (even though it looks like one is saved in default). If you do not enter a password, the function seems to execute, but does not, and no error is raised.

Re: LOTW synchronization

Posted: 02 Sep 2013, 07:32
by IW3HMH
I need to make some tests on that... it's possible your saved password is not correct in Log4OM settings?