开云体育

To be clear I had everything set up per the wiki and other pages and had been working perfectly for the last few years. Every parameter from

+ AA6YQ comments below + Step-by-step instructions are here: https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect + If you prefer JTAlert, install the latest version as Laurie VK3AMA

Peter, here is an additional guidance that I need to digest: https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect It seems to offer insight into various uses of "WSJTX to DXLab" when

You do not need JT Alert to log into DXKeeper. Check the documentation . You can have each QSO log directly to DXKeeper without JTALERT. There are 2 ways to operate with DXLABS. Outlook LT Gil W0MN

Here is the link: http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect Bruce McLain bruce.mclain@...

Hi Peter. I"m one of the novices here, grin. I have WSJTX reporting directly to the DXLab suite from the directions here: https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes I'm not using

DXLab will directly interact with WSJT-X. Unfortunately, I can’t get to the DXLab Wiki page to reference how to do that. Bruce McLain - K%WBM bruce.mclain@...

Such old JTAlert versions are not compatible with modern Wsjtx versions. As such they are no longer available for download. If your unhappy with JTAlert, don't use it. DXLab will work with Wsjtx for

Last November I had a catastrophic system crash that required me to do a full rebuild with new hardware. I cloned the old drive and got the OS running, no data was lost, and DX Lab Suite reinstalled

I’ll offer some of my findings with mysterious USB actions. --USB cables have length limitations. I believe that there is a normal expectation of one meter length. To exceed that length, I bought a

Hi Gil - I checked and I've been running the latest firmware, and did update the driver today. Still no joy, but at least it's usable. The problem is recent, so I'm really suspicious that it's related

The Kenwood manual emphasizes that you must use the Kenwood driver and be sure you have the latest Kenwood firmware. Download from Kenwood and get the Kenwood Radio Programming Software working as a

Well, the behavior of ARCP is similar to Commander, but with one difference. If I reboot with the rig USB plugged in, neither program can open the COM port. The difference is that a simple

Am 07.05.2025 um 18:43 schrieb Tim Sweeney via groups.io: Yes, that works. I changed the two port numbers both in device manager and DXLab and no conflict will appear. This setting survived a win11

+ AA6YQ comments below + Consider downloading and running Kenwood's ARCP-590 application (with Commander terminated): https://www.kenwood.com/i/products/info/amateur/ts_590/arcp590_e.html + If it

+ AA6YQ comments below + Unfortunately, the error message "Error in loading DLL" doesn't specify which of the several possible DLLs is generating the error. Before I suggest that you track down each

There are very limited options with this driver, just buffer sizes and COM port number. I did get an updated driver from Kenwood, but the behavior persists.

+ AA6YQ comments below + There are several reasons why a logged QSO would be not be considered valid for the DX Marathon competition: https://www.dxlabsuite.com/dxlabwiki/MarathonQSOIgnores + If the

Spot Collector is claiming that a zone is needed for DX Marathon, but I have already worked/confirmed that zone. I noticed this on 6m today when I worked a few stations in zone 4 and SC was still

I pretty much do an 80/20 split with POTA and DX (POTA is 80%). If I am running FTx? I use the organic log in WSJT-X for logging and then email the .adi file to myself and then upload it into