Since I have a number of eQSL accounts to support my habit of operating from more than one QTH, RUMlog won't automatically download from eQSL. I used eQSL's "export as ADIF" option to get a download of my confirmed QSOs which came out as a web page. I copied the data into a file in BBEdit and saved it to disk. When I try "eQSL In->Read File From Disk" I get the error message, "No eQSL ADIF file". I get the same message when I drag the file from a finder window onto the "Drop an ADIF File" window.
I have tried saving the file with Macintosh, Unix and Windows line endings. Although I'm not an expert on ADIF format, the lines in the file looks similar to the one produced by RUMlog for upload to eQSL.
What am I doing wrong?
ADIF files from eQSL
Re: ADIF files from eQSL
I should add that I am using RUMlog version 5.1.3
Re: ADIF files from eQSL
RUMlog can handle multiple attached accounts. Just enter all station locations into the preferences separated by a comma.
Copy and paste the adif file will not work here to. You have to download the file direct to your disk. Right Click on the "Download" link to select the correct option.
Copy and paste the adif file will not work here to. You have to download the file direct to your disk. Right Click on the "Download" link to select the correct option.
73 and best dx de Tom, DL2RUM
Re: ADIF files from eQSL
What about sending eQSL ? I can imagine it will work for receiving eQSLs but if I'll try to send one, which account will be used ?RUMlog can handle multiple attached accounts. Just enter all station locations into the preferences separated by a comma.
de SQ2KLU
de SQ2KLU
Daniel
Daniel
Re: ADIF files from eQSL
RUMlog dosen't use the station location tag for upload. eQSL uses the QSO date to determine the account.
73 and best dx de Tom, DL2RUM
Re: ADIF files from eQSL
Thanks for the help and a really good program!
Entering a single QTH in the eQSL "QTH nick name" section of each of my two logs (one for Peterborough and one for Los Gatos) did the trick. If I entered both separated by a comma, I got a popup which allowed me to choose which QTH I was using, which may be useful for people who keep everything in one log.
I still couldn't get the download of the file to work, but don't need it now.
FWIW - The file I down loaded was the same as the one I created by cut/paste, but it had extra newlines between each of the detail lines. Here is a short sample:
ADIF 2 Export from eQSL.cc
For AE6JV
Generated on Tuesday, April 9, 2013 at 22:35:39 PM UTC
<PROGRAMID:20>eQSL.cc DownloadADIF
<ADIF_Ver:1>2
<EOH>
<CALL:5>K4SBZ<QSO_DATE:8:D>20130108<TIME_ON:4>2357<BAND:3>20M<MODE:5>PSK31<RST_SENT:3>589<QSL_SENT:1>Y<QSL_SENT_VIA:1>E<EOR>
<CALL:5>W7GBB<QSO_DATE:8:D>20130115<TIME_ON:4>2304<BAND:3>20M<MODE:5>PSK31<RST_SENT:3>599<QSL_SENT:1>Y<QSL_SENT_VIA:1>E<EOR>
<CALL:5>N0QWV<QSO_DATE:8:D>20130116<TIME_ON:4>0013<BAND:3>20M<MODE:5>PSK31<RST_SENT:3>589<QSL_SENT:1>Y<QSL_SENT_VIA:1>E<EOR>
Entering a single QTH in the eQSL "QTH nick name" section of each of my two logs (one for Peterborough and one for Los Gatos) did the trick. If I entered both separated by a comma, I got a popup which allowed me to choose which QTH I was using, which may be useful for people who keep everything in one log.
I still couldn't get the download of the file to work, but don't need it now.
FWIW - The file I down loaded was the same as the one I created by cut/paste, but it had extra newlines between each of the detail lines. Here is a short sample:
ADIF 2 Export from eQSL.cc
For AE6JV
Generated on Tuesday, April 9, 2013 at 22:35:39 PM UTC
<PROGRAMID:20>eQSL.cc DownloadADIF
<ADIF_Ver:1>2
<EOH>
<CALL:5>K4SBZ<QSO_DATE:8:D>20130108<TIME_ON:4>2357<BAND:3>20M<MODE:5>PSK31<RST_SENT:3>589<QSL_SENT:1>Y<QSL_SENT_VIA:1>E<EOR>
<CALL:5>W7GBB<QSO_DATE:8:D>20130115<TIME_ON:4>2304<BAND:3>20M<MODE:5>PSK31<RST_SENT:3>599<QSL_SENT:1>Y<QSL_SENT_VIA:1>E<EOR>
<CALL:5>N0QWV<QSO_DATE:8:D>20130116<TIME_ON:4>0013<BAND:3>20M<MODE:5>PSK31<RST_SENT:3>589<QSL_SENT:1>Y<QSL_SENT_VIA:1>E<EOR>
Re: ADIF files from eQSL
The <EOR> tag is missing in your 4 QSO lines and your header looks different. RUMlog looks for the <PROGRAMID:21>eQSL.cc DownloadInBox tag.
ADIF 2 Export from eQSL.cc
Received eQSLs for DL2RUM
for QSOs between 01-Nov-1992 and 31-Dec-2020
Generated on Tuesday, April 9, 2013 at 05:12:40 AM UTC
<PROGRAMID:21>eQSL.cc DownloadInBox
<ADIF_Ver:1>2
<EOH>
<CALL:5>DL5JF<QSO_DATE:8:D>19921106<TIME_ON:4>1350<BAND:2>2M<MODE:3>SSB<RST_SENT:2>59<RST_RCVD:0 <QSL_SENT:1>Y<QSL_SENT_VIA:1>E<EOR>
<CALL:4>PX0Z<QSO_DATE:8:D>19930328<TIME_ON:4>1555<BAND:3>10M<MODE:3>SSB<RST_SENT:2>59<RST_RCVD:0><QSL_SENT:1>Y<QSL_SENT_VIA:1>E<QSLMSG:25>Tnx QSO. 73, Lima, PY1NEZ<EOR>
<CALL:6>KA7MCX<QSO_DATE:8:D>19930502<TIME_ON:4>1808<BAND:3>15M<MODE:3>SSB<RST_SENT:2>59<RST_RCVD:0><QSL_SENT:1>Y<QSL_SENT_VIA:1>E<EOR>
73 and best dx de Tom, DL2RUM
Re: ADIF files from eQSL
Thanks again for your attention Tom. I think we have it solved.
When I changed the file to say:
<PROGRAMID:21>eQSL.cc DownloadInBox
it loaded with no problems. Should RUMlog also accept:
<PROGRAMID:20>eQSL.cc DownloadADIF
?
Note that the web software for this forum does not display the right hand side of the lines I uploaded. I got the <eor> tags to display by moving the left side of the window about 15cm off the left side of the my MacBook Pro screen and then expanding the right margin.
When I changed the file to say:
<PROGRAMID:21>eQSL.cc DownloadInBox
it loaded with no problems. Should RUMlog also accept:
<PROGRAMID:20>eQSL.cc DownloadADIF
?
Note that the web software for this forum does not display the right hand side of the lines I uploaded. I got the <eor> tags to display by moving the left side of the window about 15cm off the left side of the my MacBook Pro screen and then expanding the right margin.
Re: ADIF files from eQSL
Ok, so that's perfect for someone who uses the same account in eQSL only with different location.DL2RUM wrote:RUMlog dosen't use the station location tag for upload. eQSL uses the QSO date to determine the account.
I have 2 accounts, sq2klu and sq2klu/2 depending on the location I work from. In that case I can't simply put 2 locations in as one will not be valid for the account entered. Any way to walk around that ?
I was thinking maybe a way to put in all eQSL accounts and option to choose which account you're sending with during eQSL direct export, just like with locations.
Actually the perfect situation would be if there was a way to keep QSO's for different callsigns in one Log. Let's say there's a field where you choose the callsign you work under at the moment and each QSO is marked with that call. Maybe that's too much but would be cool in my opinion

de SQ2KLU
Daniel
Daniel