Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
Here is the link: http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect Bruce McLain bruce.mclain@...
By
Bruce - K5WBM
·
#229151
·
|
Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
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
By
Richard Hill
·
#229150
·
|
Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
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@...
By
Bruce - K5WBM
·
#229149
·
|
Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
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
By
JTAlert Support (VK3AMA)
·
#229148
·
|
JTAlert failure after system crash - is there a workaround to log to DXKeeper?
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
By
Peter Dougherty
·
#229147
·
|
Re: COM port oddity with Commander.
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
By
Dave w6de
·
#229146
·
|
Re: COM port oddity with Commander.
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
By
Tim Sweeney
·
#229145
·
|
Re: COM port oddity with Commander.
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
By
Gilbert Baron W0MN
·
#229144
·
|
Re: COM port oddity with Commander.
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
By
Tim Sweeney
·
#229143
·
|
Re: COM port oddity with Commander.
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
By
Matthias Zwoch
·
#229142
·
|
Re: COM port oddity with Commander.
+ 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
By
Dave AA6YQ
·
#229141
·
|
Re: Recent Error in DX Keeper Creating DX Marathon Progress Report
+ 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
By
Dave AA6YQ
·
#229140
·
|
Re: COM port oddity with Commander.
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.
By
Tim Sweeney
·
#229139
·
|
Re: Spot Collector saying zone needed for DX Marathon incorrectly
+ 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
By
Dave AA6YQ
·
#229138
·
|
Spot Collector saying zone needed for DX Marathon incorrectly
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
By
Chuck, KM3V
·
#229137
·
|
Re: POTA and small rigs
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
By
WB0WAO Dennis
·
#229136
·
|
Re: COM port oddity with Commander.
Try Device Manager -> Ports (COM & LPT) ... open the serial port for your TS-590 -> Advanced Settings and check the Miscellaneous Settings. I would start with "Serial Enumerator" checked and all the
By
Joe Subich, W4TV
·
#229135
·
|
Re: COM port oddity with Commander.
HI Matthias - What happens if you plug in one device, say the rig, and then go into Device Manager and change the COM port number in the Advanced Settings for that port? It should retain that change
By
Tim Sweeney
·
#229134
·
|
Re: COM port oddity with Commander.
Am 07.05.2025 um 05:52 schrieb Tim Sweeney via groups.io: I had and have similar problems with Win11 24H2. When I start Arduino Developm
By
Matthias Zwoch
·
#229133
·
|
Re: COM port oddity with Commander.
Hi Joe, you're on to something, I think. But to answer the questions, fastboot and hibernation are disabled (always), sleep is enabled but only manually triggered,? and I had tried both cold boot and
By
Tim Sweeney
·
#229132
·
|