Not down here ... was able to log in and check most recent QSOs/QSLs as well as Awards status and the home page. The number of QSO records in the system is incrementing in fits and starts. 73,

Back up, just uploaded the 4 QSO's that I got the error on. Thanks, Gordon - N1MGO

LoTW is currently down. My erroneous claim below was the result of checking the LoTW Queue, rather than attempting to log in or submit QSOs or Sync. 73, Dave, AA6YQ

+ AA6YQ comments below + Either LoTW was down (it's running at 1958Z), your internet connection was down, or TQSL is being prevented from accessing the internet, most likely by your anti-malware.

In Commander -> Config-> Ports -> Primary CAT Serial Port Set RTS to TX If you are using the multi-rig capability of Commander in Commander -> Config -> MultiRadio -> CAT Serial Port Set the

+ AA6YQ comments below + So that I can see what's going on, please do the following: 1. on the General tab of DXKeeper's Configuration window, check the "Log debugging info" box 2. terminate

I get the following error when trying to upload to LOTW: Attempting to upload one QSO C:\HamPrograms\DXLab\DXKeeper\LotWUpload.ADI: Couldn't upload the file: CURL returned "Timeout was reached"

+ AA6YQ comments below + Not necessary, Rick. While not everyone here may be anxiously awaiting the next episode, what you're describing is certainly of interest to some members, perhaps reinforcing

+ AA6YQ comments below + Have you arranged for the COM port RTS signal to switch your IC-375 from RX to TX and back? Does this work correctly? + Have you configured the Audio tab of the WSJT-X

When I send DXKeeper an externallog entry via TCP, it uploads the QSO to LotW whether or not I have specified <UploadLoTW:1>N I went through the config screens and tried to make sure that there were

That depends on what Windows version you're running. Here's one example article : https://www.howtogeek.com/194041/how-to-open-the-command-prompt-as-administrator-in-windows-8.1/ Look for an article

I sent the message below to the WSJT-X group looking for help with control of my old IC-375A. Since I hope to run that rig via DX Commander I am sending the message to the DXLab group as

+ AA6YQ comments below + That means you submitted those QSOs with a "Station Location" that specified CN98pl instead on CN97uj. Correct your "Station Location" to specify CN97uj, and then resubmit

+ AA6YQ comments below + On the Callbook tab of DXKeeper's Configuration window, what options are selected? + In particular, - is "QRZ.com via Pathfinder" enabled? - is "Automatically use callbook

+ AA6YQ comments below + When did this behavior first appear? + In the "Radio Selection" sub-panel in the Radio panel on Commander's Configuration window's General tab, what is specified in the

Jeff - That was it! The IP in the multi-radio was wrong. Many thanks!! 73 de K1ESE John

+ AA6YQ comments below + Please reboot Windows into "Safe Mode with Networking". Then start the Launcher; how long does it take for the Launcher's Main window to appear? 73,

Hello Rick Where you say ===> "What I would try is to run a Command prompt "As Adminstrator" - press the "Windows" key, type the letters "cmd" then you should see a "Run as Administrator" option.

A friend of mine had this same issue after upgrading to the latest SDR version on his Flex. On the Commander Config Multi Radio Tab if you hit the Select Button next to the Flex radio see if the IP

I thought you might be on to it, Joe. I was not aware of starting a workspace but there is a workspace shown in Launcher. I did as you suggested, saving the correct IP to the workspace, but