Log4OM

I'm having trouble with downloading QSL information from LOTW using QSL Management. The process seems to work, but reports this information:

8/23/2015 10:06:52 PM: Begin ADIF generation request
8/23/2015 10:06:52 PM: Login kt5v
8/23/2015 10:06:52 PM: qso_qslsince 2015-01-01
8/23/2015 10:06:52 PM: qso_owncall KT5V
8/23/2015 10:06:53 PM: ADIF request accepted
8/23/2015 10:06:53 PM: ADIF document downloaded
8/23/2015 10:06:53 PM: ADIF document parsed: 0 qso found.

I've played around with a range of dates - still 0 qso found. I'm not sure where this ADIF from LOTW is after its downloaded. I couldn't find it or I would have check its contents However logging in to LOTW website and downloading the lotwreport.adi gets a file with over 600 QSLs - so I know there should be something in the file.

I have no problems uploading - passwords etc. appear to be set correctly.

73 de David KT5V

Was it working and now it's not or is this the first time you have tried download?

Hi Terry. This is the first time I've tried to download.

73 de David

Check that you have your station location set correctly in the options/external logs tab for LOTW it's easy to get it wrong! It has to be as in the TQsl program

Hi Terry - External log settings seem to check out with TQSL. I should note that uploading works fine so it would seem password and location are correct. Below are some screen clips - am I missing anything?

In Tqsl open Dallas like you are going to edit it and check what the station location is in full

David, as SOTA activator I'm using more than 50 TQSL locations and it took me a while to find out how the LOTW download works.

In Settings > Options > External Logs > LOTW Settings I do not put anything in the "Station ID" field.
LOTW download then grabs all QSLs which match the callsign I put in the "My call (opt)" field, regardless of what my location was.

Example: After having activated around 30 different SOTA summits in DM/BW (each of them with its own TQSL location) as DL/HB9BRJ/P, I select the Log4OM profile called DL/HB9BRJ/P as active profile and a LOTW download will find all QSLs for QSOs I made as DL/HB9BRJ/P, no matter whether a QSO was made on DM/BW-123 or DM/BW-456.

Are you sure there are LOTW QSLs waiting for your Dallas location?
Try to remove the "Station ID" from your profile and try again.

GL/73, Markus

G4POP wrote:In Tqsl open Dallas like you are going to edit it and check what the station location is in full

Hi Terry. I think this is the screen clip you are looking for. As you can see the station location name "Dallas" is different from the listing. There might a clue here. I will experiment tonight

HB9BRJ wrote:David, as SOTA activator I'm using more than 50 TQSL locations and it took me a while to find out how the LOTW download works.

In Settings > Options > External Logs > LOTW Settings I do not put anything in the "Station ID" field.
LOTW download then grabs all QSLs which match the callsign I put in the "My call (opt)" field, regardless of what my location was.

Example: After having activated around 30 different SOTA summits in DM/BW (each of them with its own TQSL location) as DL/HB9BRJ/P, I select the Log4OM profile called DL/HB9BRJ/P as active profile and a LOTW download will find all QSLs for QSOs I made as DL/HB9BRJ/P, no matter whether a QSO was made on DM/BW-123 or DM/BW-456.

Are you sure there are LOTW QSLs waiting for your Dallas location?
Try to remove the "Station ID" from your profile and try again.

GL/73, Markus

Hi Markus, thanks for jumping in. Your method makes sense, so I tried it same results (or lack of results).

As mentioned after trying several times to download through Log4OM, I pulled a lotwreport.adi directly from LOTW with about 600 QSLs so they were there waiting. I also tried setting the date on the Log4OM download dialog well back in the past - nothing.

Going back to Terry's question, I tried some variation on station ID with no success. Note that an upload through Log4OM worked flawlessly with KT5V as station ID.

I'm at a loss. But feel as though I'm missing something obvious.

In the help menu set debug to Trace

Try another download

Go back to the help menu and send me the support request zip file by email