Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DXLab
- Messages
Search
|
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@... On May 8, 2025, at 1:12?PM, Peter Dougherty via groups.io <lists@...> wrote: 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 painlessly. But somehow, something corrupted JT Alert. I've tried purging every last vestige of it from my system, reinstalling about a dozen different versions but no matter what I do, it will not operate in any kind of stable fashion. It will delay QSO logging by 45-90 seconds, not allow me to interact with it during that time and in general make logging or even operating the WSJT software itself impossible. I had been using JT Alert 2.16.6 for a few years and until the crash it had been perfect, and quite frankly I preferred it to the newer versions, but I'll take anything at this point.
?
As a result I had no choice but to delete it and I'm no longer able to log directly into DX Keeper, having to regularly import an ADIF from WSJT's log file. This is getting very old very fast. Are there any alternatives to JTAlert that will allow me to run the JT modes and log directly into DXKeeper? Honestly, if I could just get JT Alert 2.16.4 or 2.16.6 working again I'd be happy but that ship has apparently sailed.
Please and thank you. |
|
Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
开云体育On 09/05/2025 4:12 am, Peter Dougherty
via groups.io wrote:
JT Alert 2.16.4 or 2.16.6 working again 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 DXKeeper logging without JTAlert. de Laurie VK3AMA (JTAlert author) |
|
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 painlessly. But somehow, something corrupted JT Alert. I've tried purging every last vestige of it from my system, reinstalling about a dozen different versions but no matter what I do, it will not operate in any kind of stable fashion. It will delay QSO logging by 45-90 seconds, not allow me to interact with it during that time and in general make logging or even operating the WSJT software itself impossible. I had been using JT Alert 2.16.6 for a few years and until the crash it had been perfect, and quite frankly I preferred it to the newer versions, but I'll take anything at this point.
?
As a result I had no choice but to delete it and I'm no longer able to log directly into DX Keeper, having to regularly import an ADIF from WSJT's log file. This is getting very old very fast. Are there any alternatives to JTAlert that will allow me to run the JT modes and log directly into DXKeeper? Honestly, if I could just get JT Alert 2.16.4 or 2.16.6 working again I'd be happy but that ship has apparently sailed. Please and thank you. |
|
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 powered USB two port hub and placed it between the radio and computer. --Throw away your cheap flimsy USB cables.? Buy clear shield USB cables where you can see the woven shield through the semi-clear cover.? These will be thicker and less flexible than the cheaper cables but I have found them to be more reliable and work with longer than 3 Meter cables. --Modern Radios using USB to computer communications usually have power switches that do not completely power down the radio.? They continue a keep alive power to some their internal circuitry.? Including the USB connections.? Use the power button on your radio to shut down but do not turn off your 12 Volt power supply in order to maintain your USB connections. --Computers also have keep alive power to their communications ports, USB, ethernet and sometimes WIFI ports.? Check your computer to see if it has an on/off switch on the back near the power cable connector. If it has a power switch then it most likely will have keep alive power to maintain all your communications alive after shut-down.? Shut-down is not power down!? Do not also turn off the computer power switch. Most but not all Laptop computers do not maintain their external communications after shut down.? --If you still have USB connection loss on shut-down, try to use a powered USB hub between your radio and computer. --Do not turn off your power bar that you have all your station equipment connected to at the end of an operating session. --If you have any USB to serial port conversion cables, always use a converter cable with an FTDI chip in it.? Converter cables can be 10 feet long.? I buy mine at Amazon and select Dtech cables.
? 73, Dave, w6de ? ? From: [email protected]
<[email protected]> On Behalf Of Tim Sweeney via groups.io
Sent: 7 May, 2025 03:53 To: [email protected] Subject: [DXLab] 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 manager shows COM4 to be up and working. Unplugging / re-plugging the USB cable and disabling / reenabling the COM port doesn't resolve it. The only solution seems to be to uninstall the device, reboot and let Windows reinstall it. Then the port will open fine until the machine is rebooted again. Then we're back to invalid port and the need to reinstall. ? Edition ? ?Windows 11 Pro ? Commander ver 16.1.0 ? Anyone had this variation of the error crop up? Thanks! ? |
|
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 to a Win 11 update in some way, just because everything else on the system has been static.?
If I get ambitious I might try a factory reset of the rig itself, just for completeness sake.
?
Thanks and 73, Tim K1BR
? |
|
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 test and you should have no problem after that. They provide a link to do that. I had to do? it many years ago on mine and have never had a USB problem with my Kenwood TS590SG since. I have used it for many many years. Be careful to follow all instructions about installing the driver. ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ? From: [email protected] <[email protected]> On Behalf Of Dave AA6YQ via groups.io
Sent: Wednesday, May 7, 2025 2:59 PM To: [email protected] Subject: Re: [DXLab] COM port oddity with Commander. ? + AA6YQ comments below
+ Consider downloading and running Kenwood's ARCP-590 application (with Commander terminated): -- W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop |
|
Re: COM port oddity with Commander.
On Wed, May 7, 2025 at 12:58 PM, Dave AA6YQ wrote:
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 unplug->plug-in of the USB cable in the current session allows ARCP to connect, while Commander still can't. Commander needs the full unplug->reboot->plug-in cycle to get access to the port again. ?
I've rearranged the cable so I can access it from a front USB port, and as long as I remember to yank the cable before I boot up I'm in business. Once it's working, it seems to stay working until the next reboot, even through sleep/wake events.
?
73, Tim K1BR
|
|
Re: COM port oddity with Commander.
Am 07.05.2025 um 18:43 schrieb Tim Sweeney via groups.io:
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 across assignments, I think.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 restart - fine. But if I plug off and on the cable for the FT-DX10 the ports are back on the old number :-( 73 Matthias DD7NT |
|
Re: COM port oddity with Commander.
+ AA6YQ comments below
The rig generating the port is a TS-590S. The device it generates is listed as "Silicon Labs CP210x USB to UART Bridge". + Consider downloading and running Kenwood's ARCP-590 application (with Commander terminated): + If it reports the same error as Commander, then engage with Kenwood technical support. ? ? ? ?73, ? ? ? ? ? ? Dave, AA6YQ |
|
Re: Recent Error in DX Keeper Creating DX Marathon Progress Report
+ AA6YQ comments below
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? + 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 such DLL, un-register it, and then re-register it - which may or may not be successful - I suggest that you contact Microsoft support. Explain that you are encountering the "Error in loading DLL" in an application you're running that employs the Jet database engine, and that Microsoft's repair instructions (you have the URL) were not effective. Perhaps they have a next set of repair steps.
? ? ? ?73, ? ? ? ? ? ? ?Dave, AA6YQ |
|
Re: COM port oddity with Commander.
On Wed, May 7, 2025 at 10:10 AM, Joe Subich, W4TV wrote:
Try Device Manager -> Ports (COM & LPT) ... open the serial port 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. |
|
Re: Spot Collector saying zone needed for DX Marathon incorrectly
+ AA6YQ comments below
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 flagging stations on that zone as needed. And it was still highlighting the stations just worked. At least a couple of the stations I worked uploaded to LOTW and I confirmed them, so the CQ zone info was valid. Rebooted PC, restarted DXLab and did a recompute in the award progress tab. Checked the award tracking for some of the highlighted spots and it still says they are "unworked, needed" for DX Marathon. Suggestions?+ There are several reasons why a logged QSO would be not be considered valid for the DX Marathon competition: + If the above article doesn't explain what you're seeing, please let me know. ? ? ? 73, ? ? ? ? ? ? ? ?Dave, AA6YQ |
|
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 flagging stations on that zone as needed. And it was still highlighting the stations just worked. At least a couple of the stations I worked uploaded to LOTW and I confirmed them, so the CQ zone info was valid. Rebooted PC, restarted DXLab and did a recompute in the award progress tab. Checked the award tracking for some of the highlighted spots and it still says they are "unworked, needed" for DX Marathon. Suggestions?
Chuck KM3V |
|
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 DXKeeper.? I then upload the same .adi file to the POTA site so those who contact me get credit for the park.? If I am running SSB (which is not that common), I will use HAMRS on my tablet and email that .adi to myself and do the same thing as I do with the WSJT-X .adi file.??I then also do the MYQTHID thing when I upload the .adi into DXKeeper.? I wasn't aware of the upper limit of the MYQTHID's available - definitely won't run out of them!
?
For Information Only -
When hunting from the home QTH, I am using FTx 95% of the time.? I use WSJT-X, GridTracker, and Chrome with the POTAPlus Extension.? Since the park number isn't a part of the exchange there, I am not at all interested in adding it to the log, and
s it really doesn't matter as what I have worked and confirmed is taken care of in the POTA app.? GridTracker as it integrates with the POTA app spotting page and I also use the POTAPlus Extension with Chrome to alert me of ATNO's.? Between the two, I know what to go after first.? And then GridTracker then passes the QSO info from WSJT-X to DXKeeper when I log it.
?
For SSB hunting, I am using Commander, Spot Collector, DXKeeper, and Chrome with POTAPlus.? I do have USER_DEFINED_0 set to POTA to transfer any POTA info from Spot Collerctor to DXKeeper - but that isn't really necessary as, again, the POTA app tracks what I have worked according to the activator's logs.
?
73
Dennis - WB0WAO
? |
|
Re: COM port oddity with Commander.
On 2025-05-07 11:13 AM, Tim Sweeney via groups.io wrote:
There's something about the combination of the device being fully detached (or uninstalled) and a reboot that resets things in a wayTry 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 other options *not* checked. This is a new problem, as I've been running this same stuff for years now with no issue. The only things that have changed are newerLikely an update changed some default. However, I would check with Kenwood for an updated driver in addition to the port settings in Device Manager. 73, ... Joe, W4TV On 2025-05-07 11:13 AM, Tim Sweeney via groups.io wrote: Hi Joe, you're on to something, I think. |
|
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 across assignments, I think.?
?
In my case it's not a port conflict or changing assignments that's at issue. Just a consistently assigned port that is inconsistent in its functioning!?
?
73, K1BR
? |
|
Re: COM port oddity with Commander.
Am 07.05.2025 um 05:52 schrieb Tim Sweeney via groups.io:
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 manager shows COM4 to be up and working. Unplugging / re-plugging the USB cable and disabling / reenabling the COM port doesn't resolve it. The only solution seems to be to uninstall the device, reboot and let Windows reinstall it. Then the port will open fine until the machine is rebooted again. Then we're back to invalid port and the need to reinstall.I had and have similar problems with Win11 24H2. When I start Arduino Development Tool it gets port 4 for the communication with the ESP32 processor to program. But port 4 is already assigned to my second trx FT-DX10 and DXLab. So I have to unplug the FT-DX10 when I want to flash a prcessor and vice versa I cannot run Arduino when the FT-DX10 is in use. There are many free port numbers which could be used. But until yet I found no way to change that odd behaviour in the Win11 port assignment. 73 Matthias, DD7NT |
|
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 restart with the same result, as well as both radio on and radio off when booting.
?
But I overlooked the fact that even when the radio is "off", it's still really "on" internally, and the USB port is powered up as long as there is 12V to the rig. So I found unplugging the USB, rebooting, and re-plugging it clears the problem in the same way as uninstalling, rebooting and allowing the system to reinstall the device clears it. There's something about the combination of the device being fully detached (or uninstalled) and a reboot that resets things in a way that physical detachment or reboot separately do not.
?
This is a new problem, as I've been running this same stuff for years now with no issue. The only things that have changed are newer versions of Win 11 and DXLab. Since DXLab doesn't have a say in the matter, perhaps it was a Win 11 update that changed the game. The USB driver involved is from 2019, so I doubt that changed.?
?
Just to fill in as many data points as possible: putting the machine to sleep doesn't change the state of things once it's awakened. If it was talking to the rig when put to sleep, it will still talk to it when awakened.?
?
Thanks! |
|
Re: COM port oddity with Commander.
Sounds like a USB initialization error.
The error is generated when attempting to start Commander (throughAre 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 rebooted? Are sleep/hibernation enabled in Windows? Is "Fast Boot" enabled? (Hint: disable sleep, hibernate and fast boot). 73, ... Joe, W4TV On 2025-05-07 6:09 AM, Tim Sweeney via groups.io wrote: Sorry for the missing details. That's what I get for posting just before going to bed! |
|
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 first POTA activation. I think this is one of those things that will be much better to get it correct before I start rather than trying to make it "right" on the back end. I will keep a close eye on this topic and the "Logging QSOs as a POTA Activator" page. This page already has loads of good info I wasn't aware of.
?
Thanks again, and 73!
Pete WB4YDY |
Gilbert Baron W0MN
to navigate to use esc to dismiss