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
·
|
Re: COM port oddity with Commander.
Sounds like a USB initialization error. Are you doing a power down reboot or simply a "Restart"? Is the TS-590S powered on before starting/rebooting Windows or is the TS-590S off when Windows is
By
Joe Subich, W4TV
·
#229131
·
|
Re: POTA and small rigs
Dave, thanks very much for this information! DXLab continues to amaze me, and your willingness to help is always impressive and appreciated. Looks like I have more reading to do in preparation of my
By
wb4ydy2
·
#229130
·
|
Re: COM port oddity with Commander.
Sorry for the missing details. That's what I get for posting just before going to bed! The rig generating the port is a TS-590S. The device it generates is listed as "Silicon Labs CP210x USB to UART
By
Tim Sweeney
·
#229129
·
|
Re: Recent Error in DX Keeper Creating DX Marathon Progress Report
Thanks, Dave. I followed the process you recommended precisely, and still no joy. Here is the state of the current error report. Any ideas for me about what I should do next? As far as I can tell, the
By
David Simms (N4IW)
·
#229128
·
|
Re: COM port oddity with Commander.
+ AA6YQ comments below I've recently started encountering the infamous "Invalid Port Number (8002), thePort = primary CAT port, port number = 4, settings = 115200,N,8,1" message box when trying to
By
Dave AA6YQ
·
#229127
·
|
COM port oddity with Commander.
I've recently started encountering the infamous "Invalid Port Number (8002), thePort = primary CAT port, port number = 4, settings = 115200,N,8,1" message box when trying to start Commander. Device
By
Tim Sweeney
·
#229126
·
|
Re: POTA and small rigs
+ AA6YQ comments below + 3077 "My QTHs"? No problem. DXKeeper supports 1000 more to spare. 73, Dave, AA6YQ
By
Dave AA6YQ
·
#229125
·
|
Re: POTA and small rigs
Yes, Several county hunters have operated from all counties, current count of counties and equivalent areas - 3077 No need to worry about dxlab supporting that number though. 73 Bob, KA9JAC -- This
By
KA9JAC
·
#229124
·
|
Re: POTA and small rigs
A first cut at "Logging QSOs as a POTA Activator" is available here: https://www.dxlabsuite.com/dxlabwiki/LoggingAsPotaActivator Corrections and suggested additions are welcome. 73, Dave, AA6YQ
By
Dave AA6YQ
·
#229123
·
|