Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
On 09/05/2025 5:43 am, Peter Dougherty via groups.io wrote: I have tried more recent versions but they exhibit the same issues; I would love to keep using JT Alert but whatever is wrong, whether it's something within DX Labs or JT Alert, it just won't play ball If multiple versions of JTAlert are exhibiting problems the cause will very likely be caused by something other than JTAlert. The most likely culprit is your protection software is interfering with JTAlert, perhaps going online with every JTAlert action to validate JTAlert activity. Cloud based virus protection can be very problematic if not configured correctly. de Laurie VK3AMA (JTAlert author)
|
Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
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 was set back then and is still set the same way today, customized for my specific needs.?
?
I have tried more recent versions but they exhibit the same issues; I just wasn't a fan of the new user interface and the extra screen real estate it takes up. I would love to keep using JT Alert but whatever is wrong, whether it's something within DX Labs or JT Alert, it just won't play ball.? I never realized I could log directly from WSJT into DXK (since I never needed to in the past) and I'll try that. But I would love to have the alerting capabilities back for grid hunting on 6m, which is about all I ever really needed JT Alert for anyway, as well as the chat feature.
?
Once I get back home tonight I'll try to configure DXK and WSJT to talk to each other and see where it goes.
|
Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
+ AA6YQ comments below
DXLab will directly interact with WSJT-X. ?
?
Unfortunately, I can¡¯t get to the DXLab Wiki page to reference how to do that.
+ Step-by-step instructions are here: + If you prefer JTAlert, install the latest version as Laurie VK3AMA suggested.
? ? 73,
? ? ? ? ?Dave, AA6YQ
|
Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
Peter, here is an additional guidance that I need to digest:?
It seems to offer insight into various uses of "WSJTX to DXLab" when connected directly.
Rich, NU6T
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?
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 Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Peter Dougherty via groups.io
Sent: Thursday, May 8, 2025 1:13 PM
To: [email protected]
Subject: [DXLab] 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. -- W0MN EN34rb 44.08226 N 92.51265 W
Hierro candente, batir de repente
HP Laptop
|
Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
Here is the link:
Bruce McLain bruce.mclain@...
toggle quoted message
Show quoted text
On May 8, 2025, at 1:28?PM, Bruce - K5WBM via groups.io <bruce.mclain@...> wrote: 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?
Hi Peter.? I"m one of the novices here, grin.? I have WSJTX?reporting directly to the DXLab suite from the directions here:
I'm not using JTAlert yet.
Rich, NU6T
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?
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@...
toggle quoted message
Show quoted text
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
?
?
toggle quoted message
Show quoted text
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
Version ? ?23H2
Installed on ? ??11/?19/?2022
OS build ? ?22631.5189
Experience ? ?Windows Feature Experience Pack 1000.22700.1077.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 ? ?
toggle quoted message
Show quoted text
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.? 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 -- 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:
+ 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.
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.
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
_._,_._,_ 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
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.
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
|
Gilbert Baron W0MN