I have searched and not found the answer. Does EQSL accept ARRL LOTW QSLsto count towards EQSL awards? QRZ is accepting ARRL qsl confirmations.

---

AB4KJ Mike Irizarry

The only way for that to work is to get the confirmed credits from LoTW. With QRZ I think you are supplying them with your LoTW login information, the QRZ code then logs into your LoTW account and pulls down the confirmed credits.

We can't just do that without permission from ARRL. At this point they are even blocking our attempts to do AG verifications using their LoTW server, so no way they would allow us to pull down a users confirmed contacts to use for our awards program.

QRZ has worked out a deal with ARRL to allow that to happen.

---

73, Dave - VA3KAB

Why won't eqsl accept an adif down load of qsos and qsl that the arrl account holder provides to eqsl from arrl lotw for eqsl to honor for credit? That doesn't require anything from arrl lotw. Also arrl acount users could provide eqsl their lotw passwoRd and eqsl could download the adif directly?

---

AB4KJ Mike Irizarry

Because an ADIF file is not authenticated, someone could easily manipulate the ADIF file before uploading here.

Yes, that's what I was getting at in my first post. In order for it to work you would need to provide your LoTW username/password and the server here would connect and download that file. That's how QRZ does it. But! we can't just do that without permission from ARRL, and as I said, at the moment they are not even allowing us to connect to their server to authenticate our users via LoTW.

---

73, Dave - VA3KAB

Greetings. Im new here so maybe this is old but Im quite frustrated. I can download the ADI file from eQSL, but when I try and "sign" it and upload to LoTW I get the message "QSOs zero" and "Database error, invalid argument".

What am I doing wrong or arent eQSL files acceptable to LoTW?

Thanks!!
Howard
K2EQ

---

K2EQ Howard Schler

Howard,
ADI / ADIF files have many components or fields in them. The fields that you are given by a download from eQSL are not the fields that are needed to upload into LoTW.

At a minimum LoTW needs CALL, QSO_DATE, TIME_ON, BAND or FREQ or both, MODE, RST_RCVD, RST_SENT and EOR. Additional fields are ok.

Here's how the files are read:
HEADER
There are fields here for programs to know what your sending or what your getting.
I find that I usually dont mess with headers, or I strip out everything except the <EOH>.

The last field in the header is known as "End of Header" and it is abbreviated as "EOH". There is no colon or digit inside. This ends the header and everything after it is data or QSOs.

QSOs
Each field name has a left and right arrow. These contain the name of the field, a colon and digits.
Note that there is always a space before each "<". If there two spaces or no spaces, it will cause an error.
Note that the digit(s) inside the arrows and it is placed after the colon and before the ">". This digit means it is always the number of characters that will follow the ">". This tells the program how many characters of the field to load in or read. If this number is wrong it will cause an error.

The last field in each QSO line is known as "End of Record" and it is abbreviated as "EOR". There is no colon or digit inside. Think of this as the period at the end of a sentence.

Notice that the number of characters to the right of each ">" adds up to the digit(s) that is shown before ">".

<CALL:6>JH1AQN
<QSO_DATE:8>20131004
<TIME_ON:6>153826
<BAND:3>15M
<FREQ:8>21.02100
<MODE:2>CW
<RST_RCVD:3>599
<RST_SENT:3>599
<EOR>

Here's an example of an .ADI file:

~~ The header info ~~
<EOH>
<CALL:6>JH1AQN <QSO_DATE:8>20131004 <TIME_ON:6>153826 <BAND:3>15M <FREQ:8>21.02100 <MODE:2>CW <RST_RCVD:3>599 <RST_SENT:3>599 <EOR>

Note that there is a space before each "<".
Note that the digit(s) before the ">" are the number of characters that will follow the ">". This tells the program how many characters of the field to load. If this number is wrong it will cause an error.

What you get from an eQSL OUTBOX ADI download is:

~~ The header info ~~
<EOH>
<CALL:8>VI2ANZAC <QSO_DATE:8:D>20150515 <TIME_ON:4>1119 <BAND:3>30M <MODE:2>CW <RST_SENT:3>599 <QSL_SENT:1>Y <QSL_SENT_VIA:1>E <EOR>

As you can see the <RST_RCVD:3> for CW or <RST_RCVD:2> for SSB is missing.
If you are handy with text files and the "SEARCH & REPLACE" feature, then you could use S&R this way to add
this field to each QSO line. (You will have to edit each rcvd RST after this, so the RST that you do add should be the highest occurring RST report and mode you are getting. You should also choose the mode that you use most.)

Find: " <EOH>"
Replace: " <RST_RCVD:3>599 <EOH>"

Do this only once to all occurances of " <EOH>" and then go back and edit the digit after the colon as either a 2 or 3 for the mode and edit the RSTs values. You could also try to upload it with 599's. I know I'm ALWAYS 599.

So in my example it would look like this:

~~ The header info ~~
<EOH>
<CALL:8>VI2ANZAC <QSO_DATE:8:D>20150515 <TIME_ON:4>1119 <BAND:3>30M <MODE:2>CW <RST_SENT:3>599 <QSL_SENT:1>Y <QSL_SENT_VIA:1>E <RST_RCVD:3>599 <EOR>

<CALL:8>VI2ANZAC <QSO_DATE:8:D>20150515 <TIME_ON:4>1122 <BAND:3>20M <MODE:2>CW <RST_SENT:3>599 <QSL_SENT:1>Y <QSL_SENT_VIA:1>E <RST_RCVD:3>599 <EOR>

<CALL:5>EY7AD <QSO_DATE:8:D>20150517 <TIME_ON:4>0111 <BAND:3>17M <MODE:3>SSB <RST_SENT:2>57 <QSL_SENT:1>Y <QSL_SENT_VIA:1>E <RST_RCVD:3>599 <EOR>


If you're following along then you'll see that the first two QSOs are CW and 3 number RSTs would be correct. The third QSO is on SSB with EY7AD this is not going to work because it's got a 3 digit RST for an SSB QSO. For this you have to change the number 3 in RST_RCVD to a 2 and shorten the RST value to two digits, 59 for example. I'm always 5 and 9.

<CALL:5>EY7AD <QSO_DATE:8:D>20150517 <TIME_ON:4>0111 <BAND:3>17M <MODE:3>SSB <RST_SENT:2>57 <QSL_SENT:1>Y <QSL_SENT_VIA:1>E <RST_RCVD:2>59 <EOR>

The last important point is that when saving these text files in a WINDOWS environment there are two fields at the bottom of the dialog box for saving a new file or a SAVE AS.
Filename:
File Type or Save as Type:

First, the Type must be set to *.* in order to have the .ADI extension on the filename. The bad choice here is " Text Document *.txt " and that will cause erros when uploading the finished ADIF.

Second, do not enter a filename until you've selected the TYPE. Once you've select the *.* for the TYPE then type in the filename you want to use and .ADI. If you don't use the .ADI here it will not be an ADI file.

Good luck and try to find a computer geek or local DXer or contester to help you further.
73
-Charlie N1RR

---

N1RR Charlie Morrison

QRZ has worked out a deal with ARRL to allow that to happen.

any news for that?

---

SV1PIZ John Baibakis