Keyboard Shortcuts
Likes
- DXLab
- Messages
Search
|
Re: Spot Collector
Try working through the items here:
toggle quoted message
Show quoted text
<> Most common - improperly configured filter: Control-Click on the X beside the filter text box to remove all filtering Highly likely - your computer clock or timezone is off: Set Windows for your local timezone and time 73, ... Joe, W4TV On 2025-05-09 11:10 AM, k0au via groups.io wrote:
Sorry to add another non-specific "Spots don't display" question. But spots stopped displaying. |
|
Spot Collector
Sorry to add another non-specific "Spots don't display" question. But spots stopped displaying.
?
Windows 11, Nvidia RTX3060i with Studio Driver 576.02, Spot Collector 9.8.3
?
Only spot source is N6WS and I see spots rolling in on the status window.? If it's a clue, when I compact the spots database I see spots flash on the spot collector window briefly and then go away.
?
? |
|
Re: Spot Collector
What do you mean "single space"? If you mean the row height in Spot
toggle quoted message
Show quoted text
Database display is too large, got to Config -> Spot Database Display and click the "Set Row Height" button in the Font panel along the left side of that screen. 73, ... Joe, W4TV On 2025-05-09 8:10 AM, Ron S. wrote:
Can't seem to get it to single space.? Don't know what I did, but no success. |
|
Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
+ AA6YQ comments below
SpotCollector will track your 6-meter grids.+ DXLab provides real-time award tracking for the DXCC, IOTA, Marathon, VUCC, WAS, WAZ, and WPX awards on the bands and modes that you've specified for each of them. Active stations with whom a QSO would advance your progress towards these awards are highlighted in SpotCollector with font color, with optional audio and email alerts. When directly interoperating with WSJT-X, stations with whom a QSO would advance your progress towards these awards are highlighted with font color in the WSJT-X Band Activity panel, as illustrated here: + Logging a QSO in WSJT-X automatically conveys that QSO to DXKeeper. Logging a QSO in DXKeeper automatically updates your award progress to reflect the impact of that QSO - whether the QSO was logged from WSJT-X, WinWarbler, MixW, MMSSTV, MultiPSK, or DXKeeper itself. ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ |
|
Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
开云体育SpotCollector will track your 6-meter grids. First set up in DXKeeper | Config | Awards tab | VUCC Bands & Modes, this will activate the search for VHF grids. Then configure your SpotCollector display to show a column for your Award needs. SpotCollector | Config | Spot Database Display | Layout panel | select “Need” to add to the list. A need column will then appear in you SpotCollector on screen display, adjust column width and order as you would do in a spread sheet.? If unfamiliar click the “Help” box in the SpotCollector Config Awards Spot-Database-Display for details. ? After set up in DXKeeper and SpotCollector, you can have SpotCollector only display your complete list of Award needs by clicking the “Need” button in the lower portion of the SpotCollector display.? Use the “Age” filter after you set the Age time limit filter for the SpotCollector’s display in SpotCollector’s configuration. ? 73, Dave, w6de ? From: [email protected]
<[email protected]> On Behalf Of Peter Dougherty via groups.io
Sent: 8 May, 2025 19:43 To: [email protected] Subject: Re: [DXLab] 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?
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 ballIf 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. ?+ 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 On Thu, May 8, 2025 at 11:12?AM Peter Dougherty via <lists=[email protected]> wrote:
--
Richard Hill |
|
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 ? ? 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. -- 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?
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 On Thu, May 8, 2025 at 11:12?AM Peter Dougherty via <lists=[email protected]> wrote:
--
Richard Hill |
|
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! ? |
Gilbert Baron W0MN