RUMlogNG Version 1.2.5

RUMlog, the Next Generation. Completely rewritten.
User avatar
DL2RUM
Administrator
Posts: 2932
Joined: Mon 27. Aug 2007, 13:36
Location: JO40DF

Re: RUMlogNG Version 1.2.5

Unread post by DL2RUM »

Well, I have you log. :-) You have a very huge log! I was happy to see a lot of my used dx callsigns are in your log!

I was able to download data for eQSL and LoTW. First problem was the "Last QSL in" date setting. It was set to 1.2.918. It seems this confused eQSL
The Time out for LoTW occurred here as well when trying to download the full log. It is my error, I have had a wrong understanding of one parameter. :oops:

After changing it, it downloaded and processed 43.196 QSLs for LoTW. It took ca. 30 minutes. Never had the possibility to test this big number of QSOs.

I have to upload a corrected version asap. As work around, you can set the "Last QSL in" dates to a date where you have got already QSLs with your old logger. This should prevent the time out error.
2.tiff
2.tiff (137.68 KiB) Viewed 3564 times
2.tiff
2.tiff (137.68 KiB) Viewed 3564 times
73 and best dx de Tom, DL2RUM
User avatar
DL2RUM
Administrator
Posts: 2932
Joined: Mon 27. Aug 2007, 13:36
Location: JO40DF

Re: RUMlogNG Version 1.2.5

Unread post by DL2RUM »

Please test version 1.2.6: http://dl2rum.de/RUMlogNG/RUMlogNG.zip
I hope this works for you now. Please note, Maps are disabled in this version.
73 and best dx de Tom, DL2RUM
K8AJS
Posts: 52
Joined: Mon 26. Oct 2009, 03:08
Location: Ohio, USA

Re: RUMlogNG Version 1.2.5

Unread post by K8AJS »

DL2RUM wrote:Well, I have you log. :-) You have a very huge log! I was happy to see a lot of my used dx callsigns are in your log!

I was able to download data for eQSL and LoTW. First problem was the "Last QSL in" date setting. It was set to 1.2.918. It seems this confused eQSL
The Time out for LoTW occurred here as well when trying to download the full log. It is my error, I have had a wrong understanding of one parameter. :oops:

After changing it, it downloaded and processed 43.196 QSLs for LoTW. It took ca. 30 minutes. Never had the possibility to test this big number of QSOs.

I have to upload a corrected version asap. As work around, you can set the "Last QSL in" dates to a date where you have got already QSLs with your old logger. This should prevent the time out error.
Thanks for the corrected version. It seems to work fine; I downloaded 43208 QSLs rcvd, 536 QSOs not in log, 3 QSOs corrected.

FYI, this is not my entire log. In the original log, I have approximately 50,000 more QSOs under my old callsign, WB8KKI (the 536 "not in log" QSOs in the LotW download are from that time period). My logs are joined in LotW, I have yet to explore the possibility of adding those 50K QSOs under my old callsign into this same log file. I've hesitated to do that, because there doesn't seem to be any way to show a different station callsign in this log.

Next step is to do the same thing in eQSL and make sure it's working OK also.

Thanks, Tom, for your efforts!

73,

John K8AJS
bastinj@gmail.com
John Bastin K8AJS
bastinj@gmail.com
VE7GM
Posts: 3
Joined: Fri 3. Oct 2014, 01:52

Re: RUMlogNG Version 1.2.5

Unread post by VE7GM »

I am using RumlogNG 1.2.5 (56) with OS X Version 10.10.5.

I seem to have screwed up my LotW upload capability. I aborted during an upload a few days ago when I cancelled during the tqsl step (for reasons I don’t recall at the moment).

Since then, I can’t do a LotW upload any more. I keep getting the error message “tqsl Error, Cancelled by user”.

Any suggestions as to how I might fix this so I can start uploading again?

Thanks very much. RumlogNG is my core logging program.

73

Brett VE7GM
Post Reply