Date   

Re: Windows 11 -- No problem with DXLabs

Dave AA6YQ
 

+ AA6YQ comments below

I just upgraded to windows 11 and can't get commander to connect . I get the Invalid port number (8002) error. What do you suggest?

+ "Invalid port number" means exactly that: Windows reports that the COM port you have Commander configured to use does not exist. Sadly, this is all too common after a Windows upgrade.

+ To correct this, determine the COM port to which your transceiver is connected, and then update Commander accordingly. Check out the "Ports (COM & LPT)" section of the Windows Device Manager, which is accessible via the Windows Control Panel.

73,

Dave, AA6YQ


Re: Windows 11 -- No problem with DXLabs

Gilbert Baron W0MN
 

If true (I have not seen tyis luckily) it is a horrible defect in Windows.

 

Outlook LT Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of w6de
Sent: Sunday, October 31, 2021 1:47 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Windows 11 -- No problem with DXLabs

 

Some but not all Windows major upgrades have a habit of rearranging your Ports and Sound devices.

Open windows Device Manager and go down to ports and see what and where the new installation of windows-11 put your Ports.  While you are at it open Sound and see what new arrangements Windows-11 did with your sound devices.

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of John-WA7ZXD via groups.io
Sent: Sunday, October 31, 2021 14:53
To: DXLab@groups.io
Subject: Re: [DXLab] Windows 11 -- No problem with DXLabs

 

I just upgraded to windows 11 and can't get commander to connect .  I get the Invalid port number (8002) error.  What do you suggest?
John


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: Windows 11 -- No problem with DXLabs

w6de
 

Some but not all Windows major upgrades have a habit of rearranging your Ports and Sound devices.

Open windows Device Manager and go down to ports and see what and where the new installation of windows-11 put your Ports.  While you are at it open Sound and see what new arrangements Windows-11 did with your sound devices.

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of John-WA7ZXD via groups.io
Sent: Sunday, October 31, 2021 14:53
To: DXLab@groups.io
Subject: Re: [DXLab] Windows 11 -- No problem with DXLabs

 

I just upgraded to windows 11 and can't get commander to connect .  I get the Invalid port number (8002) error.  What do you suggest?
John


Re: Logging and fox/hound

g4wjs
 

On 31/10/2021 13:06, Markku SM5FLM via groups.io wrote:
I made a fox/hound FT8 qso today (7P8RU), but I'm not sure what happened. I assume the qso was correct because I received an <my-call RR73> message. But the DXKeeper did not log the qso and no upload was done to LOTW or eqsl. I haven't worked fox/hound FT8 before, so maybe I have settings wrong.
Any tips?
Hi Markku,

WSJT-X does not use or understand messages like "K1ABC RR73; F1XYZ <P5DX> -10" in normal FT8 mode, they are not used except by Fox stations in FT8 DXpedition Mode. One of the features of Hound mode is to correctly parse and act on those type of messages.

MSHV with its "multi-stream" mode *does* use those type of messages in its half-baked implementation of FT8 DXpedition Mode so if you try and work a station using that variant you will find that QSOs ending or starting with that type of message will not progress as expected. For QSO starting it is probably OK as nothing is lost and the QSO may well continue later if they send a normal FT8 report message. For QSOs ending with that message its not so good as the Log QSO dialog will not be popped up automatically so you must remember to press the "Log QSO" button yourself.

The next version of WSJT-X will parse the above message type and act on it correctly.

73
Bill
G4WJS.



--
73

Bill

G4WJS.


Re: Logging and fox/hound

Dave AA6YQ
 

+ AA6YQ comments below
On occasion a QSO will fail to log. Unsure why it happens. A manual log of the Q would be needed.
It usually only fails once and works near flawlessly after. (at least in my experience)
The RR73  was confirming the  contact
Nice capture BTW. 

+ Are you anti-malware applications configured to consider each of your amateur radio applications to be "safe" -- including each of your DXLab applications and applications like JTAlert?

      73,

            Dave, AA6YQ


Re: Logging and fox/hound

Mick
 

On occasion a QSO will fail to log. Unsure why it happens. A manual log of the Q would be needed.
It usually only fails once and works near flawlessly after. (at least in my experience)
The RR73  was confirming the  contact
Nice capture BTW. 


Re: Spot Collector Hiccup ... ??

 

On Sun, Oct 31, 2021 at 10:40 AM, Joe Subich, W4TV wrote:
With the Continent and Origin filters "empty" (no checks) means that
you are *not allowing* spots of those continents or spots from those
regions to be displayed. Similarly with the Mode filter, no checks
means no spots of those modes.

I'd suggest you start by selecting "ALL" on those three filters and
then spend some time studying the "Filtering the Spot Database Display"
topic in the SpotCollector Help file.

73,

... Joe, W4TV
Joe,

Tnx and I've been putzing with those as well.  I'll get a combination that makes sense for me.

Reason for my approach is that I have very detailed filters set in CC User and am using discreet SSIDs for the two clusters I've always used.  

Ergo ... all the band, mode Cont, etc.. are pre-selected before being ported into Spot Collector.

Seems like I'm doing a 'double' filtering, but mainly it is about me better understanding how SC works.
 
--

73 - Nolan K.  -  ki5io


Re: Spot Collector Hiccup ... ??

Joe Subich, W4TV
 

Cntrl-Click does show each of those filters to be empty or no items selected.
With the Continent and Origin filters "empty" (no checks) means that
you are *not allowing* spots of those continents or spots from those
regions to be displayed. Similarly with the Mode filter, no checks
means no spots of those modes.

I'd suggest you start by selecting "ALL" on those three filters and
then spend some time studying the "Filtering the Spot Database Display"
topic in the SpotCollector Help file.

73,

... Joe, W4TV


On 2021-10-31 11:24 AM, Nolan - KI5IO wrote:
Joe,
At startup the 4 Filters you noted do show up ...  Filter:  Band and Mode and Cont and Origin
Cntrl-Click does show each of those filters to be empty or no items selected.
One-Click on "X" does bring or maintain those 4 Filters showing as you mentioned and I confirmed above.
If I do a Cntrl-Click on the "X" the the display changes to - Filter: None  and the two clusters start their display.
At several start-ups of Spot Collector it appears that the 4 Filters are the default.
How can I make the default start-up stay with -  Filter: None  ??
--
73 - Nolan K.  -  ki5io


Re: Spot Collector Hiccup ... ??

 

Joe,

At startup the 4 Filters you noted do show up ...  Filter:  Band and Mode and Cont and Origin

Cntrl-Click does show each of those filters to be empty or no items selected.

One-Click on "X" does bring or maintain those 4 Filters showing as you mentioned and I confirmed above.

If I do a Cntrl-Click on the "X" the the display changes to - Filter: None  and the two clusters start their display.

At several start-ups of Spot Collector it appears that the 4 Filters are the default.  

How can I make the default start-up stay with -  Filter: None  ??


--

73 - Nolan K.  -  ki5io


Re: Windows 11 -- No problem with DXLabs

John-WA7ZXD
 

I just upgraded to windows 11 and can't get commander to connect .  I get the Invalid port number (8002) error.  What do you suggest?
John


Re: Spot Collector Hiccup ... ??

Joe Subich, W4TV
 

Control-click the Band, Mode, Continent and Origin filters (each in
turn) and see if one or more of them is enabled. They should also
show above the filter text box if enabled (at startup or if you simply
click 'X").

73,

... Joe, W4TV

On 2021-10-31 9:43 AM, Nolan - KI5IO wrote:
I've quite likely set a hidden filter to cause my 'hiccup', but have not been able to find it or a solution ... "so far".
I have two Spot Sources enabled and set for Auto-Connect on Startup.
I have also enabled an Initial Cluster Command of:  "sh/mydx 10"
I do not have the Pre-Filter enabled.
Under Controls I do have Maximum Age of valid incoming spots set for '60 minutes'.
I have looked at settings and cannot see any other filters I may have in-advertently set.
What is happening:
- Starting Spot Collector ... goes through its startup routine, the two Spot Sources panels briefly appear and then 'hide'.
-  Nothing appears in the main SC display panel.
-  Once I do a 'cntrl click' on the "Filter X" all the spots from both clusters will appear.
-  Does not appear that the 'sh/mydx 10' has worked as well, but still checking on this.
I'm sure I have some toggle set that is filtering the initial display, but currently am stumped?
Suggestions?
--
73 - Nolan K.  -  ki5io


Spot Collector Hiccup ... ??

 

I've quite likely set a hidden filter to cause my 'hiccup', but have not been able to find it or a solution ... "so far".

I have two Spot Sources enabled and set for Auto-Connect on Startup.

I have also enabled an Initial Cluster Command of:  "sh/mydx 10"

I do not have the Pre-Filter enabled.

Under Controls I do have Maximum Age of valid incoming spots set for '60 minutes'.

I have looked at settings and cannot see any other filters I may have in-advertently set.

What is happening: 

- Starting Spot Collector ... goes through its startup routine, the two Spot Sources panels briefly appear and then 'hide'.

-  Nothing appears in the main SC display panel.

-  Once I do a 'cntrl click' on the "Filter X" all the spots from both clusters will appear.

-  Does not appear that the 'sh/mydx 10' has worked as well, but still checking on this.

I'm sure I have some toggle set that is filtering the initial display, but currently am stumped?

Suggestions?
--

73 - Nolan K.  -  ki5io


Re: Logging and fox/hound

Joe Subich, W4TV
 

Isn't WSJTX configured to "prompt me to log QSO"?

Normally that setting (File -> Settings -> Reporting) will cause
WSJTX to pop-up a box with the QSO information and clicking
OK will cause the QSO to be logged in DXKeeper (if DXLab
Suite is properly configured and/or JTAlert is also running).

Yes, that log prompt does pop-up on receipt of RR73; if WSJTX
is in "Hound" mode.

73,

... Joe, W4TV

On 2021-10-31 9:06 AM, Markku SM5FLM via groups.io wrote:
I made a fox/hound FT8 qso today (7P8RU), but I'm not sure what happened. I assume the qso was correct because I received an <my-call  RR73> message. But the DXKeeper did not log the qso and no upload was done to LOTW or eqsl. I haven't worked fox/hound FT8 before, so maybe I have settings wrong.
Any tips?


Logging and fox/hound

Markku SM5FLM
 

I made a fox/hound FT8 qso today (7P8RU), but I'm not sure what happened. I assume the qso was correct because I received an <my-call  RR73> message. But the DXKeeper did not log the qso and no upload was done to LOTW or eqsl. I haven't worked fox/hound FT8 before, so maybe I have settings wrong.
Any tips?


Re: Time out on Logging

Dave AA6YQ
 

+ AA6YQ comments below
Thanks! This started several months ago, but I can't remember exactly when. It happened very minimally at first but has gotten worse to the point now it's happening over 50% of the time. Your questions below prompted me to do some checking with Task Manager to see what else was running on my desktop. I did have a couple of other applications running, so I stopped them and then did some tests with only DXLabs Suite and WSJT-X running. Still have the same error message so maybe something else is consuming CPU resources or other. I'll run some more tests while looking at the CPU performance (if I can remember where to find it). BTW, I don't run any virus protection software other than what is built in to Win 10. CPU is an older i5 with 8gB of RAM and a 256gB SSD. Performance has not been a problem even tho this is an older system.

+ Slowing of the communication among DXLab applications could the result of interference from an anti-malware application. See

https://www.dxlabsuite.com/dxlabwiki/ApplicationInteference

      73,

            Dave, AA6YQ


Windows 11 -- No problem with DXLabs

Jim Miller, AB3CV
 

Seems to work fine. Also running WSJT linked to Spotcollector.

All good.

jim ab3cv


Re: Time out on Logging

Rod Greene
 

Dave,

Thanks! This started several months ago, but I can't remember exactly when. It happened very minimally at first but has gotten worse to the point now it's happening over 50% of the time. Your questions below prompted me to do some checking with Task Manager to see what else was running on my desktop. I did have a couple of other applications running, so I stopped them and then did some tests with only DXLabs Suite and WSJT-X running. Still have the same error message so maybe something else is consuming CPU resources or other. I'll run some more tests while looking at the CPU performance (if I can remember where to find it). BTW, I don't run any virus protection software other than what is built in to Win 10. CPU is an older i5 with 8gB of RAM and a 256gB SSD. Performance has not been a problem even tho this is an older system.

73, Rod/w7zrc

On Friday, October 29, 2021, 11:45:56 AM MDT, Dave AA6YQ <aa6yq@...> wrote:


+ AA6YQ comments below

Using WSJT-X via SC to DXK. I keep getting this message:

"Unable to log QSO with XXXXX on 40m in FT8: DXKeeper did not execute the Log directive within 15 seconds.


If DXKeeper is executing another function, wait for that function to complete, and then try logging the QSO again."

After this message window pops up and another few seconds transpire, the QSO is logged normally. And I don't remember this happening in the past.

I've looked in SC and DXK Config but not finding a way to give it a little more time.

Please point me in the right direction!

+ When did this error message appear for the first time?

+ What changes did you make to your hardware or software around that time?

+ The "Log this QSO" directive from SpotCollector to DXKeeper does not traverse the internet. Normally, it's conveyed within a few milliseconds, so there's no need to extend the timeout beyond 15 seconds!


          73,


                Dave, AA6YQ







Re: Time out on Logging

Dave AA6YQ
 

+ AA6YQ comments below

Using WSJT-X via SC to DXK. I keep getting this message:

"Unable to log QSO with XXXXX on 40m in FT8: DXKeeper did not execute the Log directive within 15 seconds.


If DXKeeper is executing another function, wait for that function to complete, and then try logging the QSO again."

After this message window pops up and another few seconds transpire, the QSO is logged normally. And I don't remember this happening in the past.

I've looked in SC and DXK Config but not finding a way to give it a little more time.

Please point me in the right direction!

+ When did this error message appear for the first time?

+ What changes did you make to your hardware or software around that time?

+ The "Log this QSO" directive from SpotCollector to DXKeeper does not traverse the internet. Normally, it's conveyed within a few milliseconds, so there's no need to extend the timeout beyond 15 seconds!

73,

Dave, AA6YQ


Time out on Logging

Rod Greene
 

Using WSJT-X via SC to DXK. I keep getting this message:

"Unable to log QSO with XXXXX on 40m in FT8: DXKeeper did not execute the Log directive within 15 seconds.

If DXKeeper is executing another function, wait for that function to complete, and then try logging the QSO again."

After this message window pops up and another few seconds transpire, the QSO is logged normally. And I don't remember this happening in the past.

I've looked in SC and DXK Config but not finding a way to give it a little more time.

Please point me in the right direction!

Thanks and 73, Rod/w7zrc


Re: Commander - Strange Behavior with Yaesu FT-2000

W2EQ
 

Problem still happening at 38400 baud.  I re-produced the problem with debug log enabled and sent Dave the debug log via email.  73 - Tom, W2EQ

3921 - 3940 of 208010