Date   
Re: DXKeeper, Pathfinder, WSJT and JTALert

ND9G Mike
 

JTAlert has some settings for XML QTH and Name data on the Logging section of the settings.

I do not use those settings. I let DX Keeper do it as the QSOs are logged, using the settings on DX Keeper's config (Callbook tab).

73,
Mike ND9G

On Tue, Oct 17, 2017 at 10:08 AM, wb4mnk@... [dxlab] <dxlab@...> wrote:
 

Using Windows 10.


When I click on log qso in WSJT DXKeeper does not get OP Name or QTH plus Address is not filled in. Seems like all other info is sent to DXKeeper correctly.


Are the some settings I need to change to correct this ?


73,

Art WB4MNK


DXKeeper, Pathfinder, WSJT and JTALert

Arthur Petteway
 

Using Windows 10.


When I click on log qso in WSJT DXKeeper does not get OP Name or QTH plus Address is not filled in. Seems like all other info is sent to DXKeeper correctly.


Are the some settings I need to change to correct this ?


73,

Art WB4MNK

Re: DXKeeper - LOTW interaction

Robie
 

Dave,

Thanks for the quick response!


I understood the issue created by the new certificate.

No, the "already uploaded QSOs" option was not checked!  

Thanks again for the great support!

Robie - AJ4F



On Tue, Oct 17, 2017 at 2:19 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
 

>>>AA6YQ comments below

From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, October 17, 2017 9:34 AM
To: dxlab@...
Subject: [dxlab] DXKeeper - LOTW interaction

Dave,

I experienced the following:

1. I requested a new TQSL certificate since mine was about to expire. I received the corresponding e-mail however I did not realize the new certificate had arrived.

2. I uploaded 2 QSOs to LOTW using my old certificate and they did not appear in LOTW

>>>On processing your request for a new Callsign Certificate, LoTW invalidated your previous Callsign Certificate.

3. I then realized that my new certificate had arrived, loaded it into TQSL and attempted to upload the QSOs again. I received the following error message:

TQSL Version 2.3.1 [v2.3.1]
Signing using Callsign AJ4F, DXCC Entity UNITED STATES OF AMERICA

All QSOs are duplicates; aborted
No records to upload
Final Status: No QSOs written (8)

4. I did not see the TQSL window open that allowed me to make a selection to upload duplicate QSOs. Is this behavior correct?

>>>Yes. On the LoTW tab of DXKeeper’s “QSL Configuration” window, there is a box you can check that will direct TQSL to accept already-uploaded QSOs when you next click “Upload to TQSL”. Had you checked this box, your re-submitted QSOs would have been accepted.

73,

Dave, AA6YQ


Re: DXKeeper - LOTW interaction

Dave AA6YQ
 

AA6YQ comments below
From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, October 17, 2017 9:34 AM
To: dxlab@...
Subject: [dxlab] DXKeeper - LOTW interaction


Dave,

I experienced the following:

1. I requested a new TQSL certificate since mine was about to expire. I received the corresponding e-mail however I did not realize the new certificate had arrived.

2. I uploaded 2 QSOs to LOTW using my old certificate and they did not appear in LOTW

On processing your request for a new Callsign Certificate, LoTW invalidated your previous Callsign Certificate.
3. I then realized that my new certificate had arrived, loaded it into TQSL and attempted to upload the QSOs again. I received the following error message:

TQSL Version 2.3.1 [v2.3.1]
Signing using Callsign AJ4F, DXCC Entity UNITED STATES OF AMERICA

All QSOs are duplicates; aborted
No records to upload
Final Status: No QSOs written (8)


4. I did not see the TQSL window open that allowed me to make a selection to upload duplicate QSOs. Is this behavior correct?

Yes. On the LoTW tab of DXKeeper’s “QSL Configuration” window, there is a box you can check that will direct TQSL to accept already-uploaded QSOs when you next click “Upload to TQSL”. Had you checked this box, your re-submitted QSOs would have been accepted.
73,

Dave, AA6YQ

DXKeeper - LOTW interaction

Robie
 

Dave,

I experienced the following:

1. I requested a new TQSL certificate since mine was about to expire.  I received the corresponding e-mail however I did not realize the new certificate had arrived. 

2. I uploaded 2 QSOs to LOTW using my old certificate and they did not appear in LOTW

3. I then realized that my new certificate had arrived, loaded it into TQSL and attempted to upload the QSOs again.  I received the following error message:

TQSL Version 2.3.1 [v2.3.1]
Signing using Callsign AJ4F, DXCC Entity UNITED STATES OF AMERICA

All QSOs are duplicates; aborted
No records to upload
Final Status: No QSOs written (8)


4. I did not see the TQSL window open that allowed me to make a selection to upload duplicate QSOs.  Is this behavior correct?

5. I exported the QSOs to an adi file and successfully uploaded them with TQSL.  I received the message regarding submission of duplicates, answered YES and they were processed.

Robie - AJ4F

Re: DXLab and Linux Wine

Stan Gammons <s_gammons@...>
 

That will be good. I don't know of anything that's quite like DXLabs though. CQRLog does some of the same stuff, but it's not quite the same.


73

Stan
KM4HQE


On October 17, 2017 4:24:49 AM CDT, "neilz@... [dxlab]" wrote:
 

The good news is that whenever Laurie gets time to finish it, he has said that the next version of JT-Alert will be cross-platform.

Neil, KN3ILZ

Re: DXLab and Linux Wine

neil_zampella
 

The good news is that whenever Laurie gets time to finish it, he has said that the next version of JT-Alert will be cross-platform.

Neil, KN3ILZ

Re: Resending many QSOs to LOTW

Dave AA6YQ
 

The best way to keep abreast of LoTW status is to join the LoTW Yahoo Group:

https://groups.yahoo.com/neo/groups/ARRL-LOTW

 

     73,

 

             Dave, AA6YQ

 

From: dxlab@... [mailto:dxlab@...]
Sent: Tuesday, October 17, 2017 12:02 AM
To: dxlab@...
Subject: Re: [dxlab] Resending many QSOs to LOTW

Great!

I seem to remember you talking about it before and you probably posted info about the upgrade back then.  I just don't remember.  This summer has been a bit hectic too.

Thanks for the info.

73

Stan
KM4HQE

On 10/16/2017 10:10 PM, 'Dave AA6YQ' aa6yq@... [dxlab] wrote:

 

>>>AA6YQ comments below

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, October 16, 2017 10:14 PM
To: dxlab@...
Subject: Re: [dxlab] Resending many QSOs to LOTW

Does that mean they have upgraded/added more servers to better handle the load?   I'm getting old and forgetful, but I seem to recall such an effort being in the works.

>>>The component of LoTW that processes uploaded QSOs, referred to as the “LoTW Server”, was significantly updated; part of this effort included replacing a database engine interface implemented with a proprietary C++ API with one implemented in ODBC – an industry standard. This first stage has roughly doubled the rate at which uploaded QSOs can be processed. It was deployed to production back in early August. Performance will increase further when the database engine is upgraded, an action previously prevented by the dependency on the C++ API.

     73,

              Dave, AA6YQ


 





Re: Resending many QSOs to LOTW

Stan Gammons <s_gammons@...>
 

Great!

I seem to remember you talking about it before and you probably posted info about the upgrade back then.  I just don't remember.  This summer has been a bit hectic too.

Thanks for the info.


73

Stan
KM4HQE


On 10/16/2017 10:10 PM, 'Dave AA6YQ' aa6yq@... [dxlab] wrote:
 

>>>AA6YQ comments below

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, October 16, 2017 10:14 PM
To: dxlab@...
Subject: Re: [dxlab] Resending many QSOs to LOTW

Does that mean they have upgraded/added more servers to better handle the load?   I'm getting old and forgetful, but I seem to recall such an effort being in the works.

>>>The component of LoTW that processes uploaded QSOs, referred to as the “LoTW Server”, was significantly updated; part of this effort included replacing a database engine interface implemented with a proprietary C++ API with one implemented in ODBC – an industry standard. This first stage has roughly doubled the rate at which uploaded QSOs can be processed. It was deployed to production back in early August. Performance will increase further when the database engine is upgraded, an action previously prevented by the dependency on the C++ API.

     73,

              Dave, AA6YQ




Re: DXLab and Linux Wine

Stan Gammons <s_gammons@...>
 

The DXLab suite will not work with WINE.  If you want to run it on Linux, the only option is to run it in a windows VM. I think most everyone runs it in a WinXP, or Win7 VirtualBox VM.  I run it on Kubuntu in a win7 VM.  It works fine that way.  Just be aware that if you want to run things like fldigi and WSJT-X on Linux and DXLabs in the windows VM, you may not be able to use something like JTAlert.  I've tinkered with it a little, but so far I've been unable to make it work.

As I've said before, it would be really nice if more of the folks that wrote ham radio software for windows would make it cross platform so it would run on windows, Linux and OS-X.  But, that's not going to happen.  At least we have fldigi and WSJT-X for Linux and OS-X.

Good luck.


73

Stan
KM4HQE

On 10/16/2017 10:11 PM, kg6tt@... [dxlab] wrote:
 

This has probably been covered before, but then again WINE is evolving too.


Does anyone have successful experience running DXLab applications in Linux using WINE?


Jerry, KG6TT




Re: Slow Response with Win10

Dave AA6YQ
 

My pleasure, Scott. Welcome back!

 

     73,

 

               Dave, AA6YQ

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, October 16, 2017 11:16 PM
To: dxlab@...
Subject: RE: [dxlab] Slow Response with Win10

 



Dave,

 

It's pretty quick now and the whole program is a lot more responsive. I've been trying to chase 3C0L on 1821 since I was at the site and now remote (I guess 2 hours). In the meantime I'm modifying Commander, WinWarbler and Spot Collector the way I used to like it. I found some User defined controls for the 590s that I had in a backup drive from my Win7 computer. I thought I had one that was a slider to adjust the power of the rig but I can't find it now. Found some other goodies though like Tune, Rig on/off NB and NR controls. 

 

Thanks for working with me on this.

 

Scott




Re: DXLab and Linux Wine

Dave AA6YQ
 

AA6YQ comments below
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, October 16, 2017 11:11 PM
To: dxlab@...
Subject: [dxlab] DXLab and Linux Wine

This has probably been covered before, but then again WINE is evolving too
Does anyone have successful experience running DXLab applications in Linux using WINE?

No one has ever reported success here running DXLab on Linux using WINE. The recommended techniques for running DXLab on Linux are here:
<http://www.dxlabsuite.com/dxlabwiki/DXLabLinux>

73,

Dave, AA6YQ

Re: Slow Response with Win10

Scott
 

Dave,

It's pretty quick now and the whole program is a lot more responsive. I've been trying to chase 3C0L on 1821 since I was at the site and now remote (I guess 2 hours). In the meantime I'm modifying Commander, WinWarbler and Spot Collector the way I used to like it. I found some User defined controls for the 590s that I had in a backup drive from my Win7 computer. I thought I had one that was a slider to adjust the power of the rig but I can't find it now. Found some other goodies though like Tune, Rig on/off NB and NR controls. 

Thanks for working with me on this.

Scott

DXLab and Linux Wine

Jerald Volpe
 

This has probably been covered before, but then again WINE is evolving too.


Does anyone have successful experience running DXLab applications in Linux using WINE?


Jerry, KG6TT

Re: Resending many QSOs to LOTW

Dave AA6YQ
 

>>>AA6YQ comments below

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, October 16, 2017 10:14 PM
To: dxlab@...
Subject: Re: [dxlab] Resending many QSOs to LOTW

Does that mean they have upgraded/added more servers to better handle the load?   I'm getting old and forgetful, but I seem to recall such an effort being in the works.

>>>The component of LoTW that processes uploaded QSOs, referred to as the “LoTW Server”, was significantly updated; part of this effort included replacing a database engine interface implemented with a proprietary C++ API with one implemented in ODBC – an industry standard. This first stage has roughly doubled the rate at which uploaded QSOs can be processed. It was deployed to production back in early August. Performance will increase further when the database engine is upgraded, an action previously prevented by the dependency on the C++ API.

     73,

              Dave, AA6YQ

Re: Resending many QSOs to LOTW

Stan Gammons <s_gammons@...>
 

Does that mean they have upgraded/added more servers to better handle the load?   I'm getting old and forgetful, but I seem to recall such an effort being in the works.


73

Stan
KM4HQE


On 10/16/2017 09:05 PM, 'Dave AA6YQ' aa6yq@... [dxlab] wrote:
 

At 2Z, the LoTW processing queue was only a few minutes long:

http://www.arrl.org/logbook-queue-status

 

     73,

 

          Dave, AA6YQ

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, October 16, 2017 10:01 PM
To: dxlab@...
Subject: RE: [dxlab] Resending many QSOs to LOTW

 



Well, got the QSOs sent to LOTW - turns out there were 2,971 in all.  I've been waiting over an hour and they still don't show up in the database.  If there was an error, there's no indication at all.  I was able to send some singles up and that worked OK.  Maybe large updates are queued for processing much later?



Re: Resending many QSOs to LOTW

Dave AA6YQ
 

At 2Z, the LoTW processing queue was only a few minutes long:

http://www.arrl.org/logbook-queue-status

 

     73,

 

          Dave, AA6YQ

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, October 16, 2017 10:01 PM
To: dxlab@...
Subject: RE: [dxlab] Resending many QSOs to LOTW

 



Well, got the QSOs sent to LOTW - turns out there were 2,971 in all.  I've been waiting over an hour and they still don't show up in the database.  If there was an error, there's no indication at all.  I was able to send some singles up and that worked OK.  Maybe large updates are queued for processing much later?


Re: Resending many QSOs to LOTW

Floyd Sense
 

Well, got the QSOs sent to LOTW - turns out there were 2,971 in all.  I've been waiting over an hour and they still don't show up in the database.  If there was an error, there's no indication at all.  I was able to send some singles up and that worked OK.  Maybe large updates are queued for processing much later?

Re: Slow Response with Win10

Dave AA6YQ
 

So you now know that firewall and anti-malware configuration was not the issue.

 

Now that you’ve eliminated the memory hogs, how long is it taking for Commander’s Main window to appear on-screen after you start it?

 

        73,

 

              Dave, AA6YQ

 

From: dxlab@... [mailto:dxlab@...]
Sent: Monday, October 16, 2017 9:08 PM
To: dxlab@...
Subject: Re: [dxlab] Slow Response with Win10

 



That is how my settings in WinWarbler are set too. 

 

I went up to the site where I have the remote computer/radio because when I did Ctrl-Alt-Delete, it was activating my computer at the house. I went into safe mode and brought up DXLabs, and it wasn't recognizing the COM Port, but the apps seemed to load about the same. I went into Task Manager and there were a couple of programs in there that I did some research on and determined they were nothing but memory hogs. Once disabled, I rebooted and the apps are now running much faster. So, maybe the issue is fixed. 

 

Next step in setting up DXLabs the way I liked when I used it a couple of years ago was to load different macros that help control my radio. That's going to be very useful now that the rig is remote. I need to be able to adjust the power easily for one thing. 

 

Thanks Dave as always for your help, and the other replies and hints too.

 

73 Scott

KN3A




Re: Slow Response with Win10

Scott
 

That is how my settings in WinWarbler are set too. 

I went up to the site where I have the remote computer/radio because when I did Ctrl-Alt-Delete, it was activating my computer at the house. I went into safe mode and brought up DXLabs, and it wasn't recognizing the COM Port, but the apps seemed to load about the same. I went into Task Manager and there were a couple of programs in there that I did some research on and determined they were nothing but memory hogs. Once disabled, I rebooted and the apps are now running much faster. So, maybe the issue is fixed. 

Next step in setting up DXLabs the way I liked when I used it a couple of years ago was to load different macros that help control my radio. That's going to be very useful now that the rig is remote. I need to be able to adjust the power easily for one thing. 

Thanks Dave as always for your help, and the other replies and hints too.

73 Scott
KN3A