Date   

Re: Digital operation on old rig [TS-850S]. Signalink USB a good solution?

Joe Subich, W4TV
 

On 2021-04-14 6:53 PM, g4wjs wrote:

yes.
If you are careful and configure both Windows and WSJTX properly (I
would not touch JTDX since it departs from WSTJX in important ways).

73,

... Joe, W4TV


On 2021-04-14 6:53 PM, g4wjs wrote:
On 14/04/2021 22:44, dwfred@bellsouth.net wrote:
Anyone have experience using the Signalink USB audio interface box? It looks like an easy way, with a pre-made cable, to hook my notebook up to my TS850S for digital modes.  What I'm curious about is how it affects the notebook's sound interface.  When the USB interface is enumerated, does the Signalink appear in Windows as an additional sound card?  Does this disable the notebook's built-in sound card for regular Windows output?  For example, say I want to watch a YouTube video while doing FT8.  Can I listen to the sound from the YouTube video's audio in my regular PC speakers while still using the audio interface for the Signalink USB for JTDX?

Thanks for any info.
73,
Dean W8ZF
Hi Dean,
Yes, no, and yes.
73
Bill
G4WJS.


Re: Digital operation on old rig [TS-850S]. Signalink USB a good solution?

g4wjs
 

On 14/04/2021 22:44, dwfred@bellsouth.net wrote:
Anyone have experience using the Signalink USB audio interface box?  It looks like an easy way, with a pre-made cable, to hook my notebook up to my TS850S for digital modes.  What I'm curious about is how it affects the notebook's sound interface.  When the USB interface is enumerated, does the Signalink appear in Windows as an additional sound card?  Does this disable the notebook's built-in sound card for regular Windows output?  For example, say I want to watch a YouTube video while doing FT8.  Can I listen to the sound from the YouTube video's audio in my regular PC speakers while still using the audio interface for the Signalink USB for JTDX?

Thanks for any info.
73,
Dean W8ZF
Hi Dean,

Yes, no, and yes.

73
Bill
G4WJS.



--
73

Bill

G4WJS.


Re: Commander 15.0.9 is available

Joe Subich, W4TV
 

On 2021-04-14 6:29 PM, Jim N7US wrote:
I am using Win4K3Suite to control the radio, with the radio
connected to that program. Might that be the cause?
Yes, contact the developer of Win4K3Suite to see if it passes
the "report SWR" command.

73,

... Joe, W4TV


On 2021-04-14 6:29 PM, Jim N7US wrote:
Thanks for the update, Dave, and all that you do for us.
I'm not seeing the SWR with my K3S while transmitting. Where should I be looking?
I am using Win4K3Suite to control the radio, with the radio connected to that program. Might that be the cause?
73, Jim N7US
-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ via groups.io
Sent: Monday, April 12, 2021 00:53
To: DXLab@groups.io
Subject: [DXLab] Commander 15.0.9 is available
If you are using Window Defender Antivirus (Windows 10), update it to its latest malware definition in
https://www.microsoft.com/en-us/wdsi/definitions
before installing or upgrading to Commander 15.0.9
This release
- updates CW speed shown in Main window's Mode panel when it changes (tnx to Norm KC1BMD)
- correctly display spectrum data from an Icom transceiver if started with low-pass filtering enabled with a value of 1 (tnx to Floyd K9AC)
- when controlling an Elecraft K3, KX3, or KX2 whose firmware supports the SW command, display the SWR while transmitting (tnx to Phil F5PHW and Greg VK3VT)
- updates the TXMeter.htm documentation file
Notes
1. in this version, the Secondary CAT Port's "CAT Protocol" selector can be set to "FlexRadio PGXL", but this is not yet working correctly with a FlexRadio PGXL amplifier.
2. Update your firewall and anti-malware applications to consider this new version of Commander to be "safe"
- 0 of 56 antivirus scanners accessible via Virus Total detected malware <https://www.virustotal.com/gui/home/upload>
- 0 of 15 antivirus scanners accessible via Jotti detected malware <https://virusscan.jotti.org/>
- submitted for online analysis by Microsoft Windows Defender: no malware detected
3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking
4. After upgrading, to revert to the previous version of Commander, see http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion
Commander 15.0.9 is available via the DXLab Launcher and via
http://www.dxlabsuite.com/download.htm
73,
Dave, AA6YQ


Re: Commander 15.0.9 is available

Jim N7US
 

Thanks for the update, Dave, and all that you do for us.

I'm not seeing the SWR with my K3S while transmitting. Where should I be looking?

I am using Win4K3Suite to control the radio, with the radio connected to that program. Might that be the cause?

73, Jim N7US

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ via groups.io
Sent: Monday, April 12, 2021 00:53
To: DXLab@groups.io
Subject: [DXLab] Commander 15.0.9 is available

If you are using Window Defender Antivirus (Windows 10), update it to its latest malware definition in

https://www.microsoft.com/en-us/wdsi/definitions

before installing or upgrading to Commander 15.0.9


This release

- updates CW speed shown in Main window's Mode panel when it changes (tnx to Norm KC1BMD)

- correctly display spectrum data from an Icom transceiver if started with low-pass filtering enabled with a value of 1 (tnx to Floyd K9AC)

- when controlling an Elecraft K3, KX3, or KX2 whose firmware supports the SW command, display the SWR while transmitting (tnx to Phil F5PHW and Greg VK3VT)

- updates the TXMeter.htm documentation file


Notes

1. in this version, the Secondary CAT Port's "CAT Protocol" selector can be set to "FlexRadio PGXL", but this is not yet working correctly with a FlexRadio PGXL amplifier.


2. Update your firewall and anti-malware applications to consider this new version of Commander to be "safe"

- 0 of 56 antivirus scanners accessible via Virus Total detected malware <https://www.virustotal.com/gui/home/upload>

- 0 of 15 antivirus scanners accessible via Jotti detected malware <https://virusscan.jotti.org/>

- submitted for online analysis by Microsoft Windows Defender: no malware detected


3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking


4. After upgrading, to revert to the previous version of Commander, see http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion



Commander 15.0.9 is available via the DXLab Launcher and via

http://www.dxlabsuite.com/download.htm

73,

Dave, AA6YQ


Re: Spot Collector not showing spots

Dave AA6YQ
 

+ AA6YQ comments below

On Wed, Apr 14, 2021 at 6:33 AM Grant Kesselring <kesselg75@gmail.com> wrote:

Unfortunately, I've spoken too soon. Evidently, after 5-6 hours of spots coming in properly, this morning I find that all spots stopped at 0842Z (about 5 hours ago). The telnet windows are still there, but unresponsive. All of the Telnet status lights in Spot Collector are yellow. The WSJT source status is still green even though no spots are coming across UDP. The WSJT program is actively decoding stations, so there is activity that would generate spots. The only way to recover is to terminate Spot Collector from the task manager. It does not respond to termination using DXLab Launcher.
It sounds like something in SpotCollector is hanging (i.e. waiting for a response to some request, and blocking other work from proceeding).

Some suggestions to consider, to try to isolate the problem:

* Disable Email and Audio alarms (if you have them enabled)
* Disable TNC Serial Port (you didn't mention having a TNC, but just in case...)
* Disable the web server (if enabled)
* Disable all spot sources except one (the one you can't live without?), and see if the problem recurs, then, if not, re-enable one at a time

Did you do recomputes of your log database (in DXKeeper) and your spot database after changing your award objectives? Failure to do so shouldn't cause SpotCollector to hang, but you mentioned the award objective change as the apparent origin of the problem.

Another option might be to enable "Log debugging information", then examine the ErrorLog.txt when the problem occurs to look for clues.
You could probably email it directly to Dave for his analysis too.
Note that the log could grow quickly, especially with multiple spot sources enabled.

+ I would prefer that Grant conduct the "boot Windows into Safe Mode with Networking" test first.

73,

Dave, AA6YQ


Re: Spot Collector not showing spots

iain macdonnell - N6ML
 

On Wed, Apr 14, 2021 at 6:33 AM Grant Kesselring <kesselg75@gmail.com> wrote:

Unfortunately, I've spoken too soon. Evidently, after 5-6 hours of spots coming in properly, this morning I find that all spots stopped at 0842Z (about 5 hours ago). The telnet windows are still there, but unresponsive. All of the Telnet status lights in Spot Collector are yellow. The WSJT source status is still green even though no spots are coming across UDP. The WSJT program is actively decoding stations, so there is activity that would generate spots. The only way to recover is to terminate Spot Collector from the task manager. It does not respond to termination using DXLab Launcher.
It sounds like something in SpotCollector is hanging (i.e. waiting for
a response to some request, and blocking other work from proceeding).

Some suggestions to consider, to try to isolate the problem:

* Disable Email and Audio alarms (if you have them enabled)
* Disable TNC Serial Port (you didn't mention having a TNC, but just
in case...)
* Disable the web server (if enabled)
* Disable all spot sources except one (the one you can't live
without?), and see if the problem recurs, then, if not, re-enable one
at a time

Did you do recomputes of your log database (in DXKeeper) and your spot
database after changing your award objectives? Failure to do so
shouldn't cause SpotCollector to hang, but you mentioned the award
objective change as the apparent origin of the problem.

Another option might be to enable "Log debugging information", then
examine the ErrorLog.txt when the problem occurs to look for clues.
You could probably email it directly to Dave for his analysis too.
Note that the log could grow quickly, especially with multiple spot
sources enabled.

73,

~iain / N6ML


Re: Setting unto serve Spots to outside world?

David Reed
 

Thanks Dave! Got it all up and running just like I wanted!

73 de W5SV - David F. Reed

On Apr 14, 2021, at 12:40, Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I currently successfully have SpotCollect configured to serve a webpage of my filtered spots on my internal internet.

I have a new need developing in which as I travel and operate remote base, I want to access my current needs same as I spot them at
home.

Rather that maintaining a up to date copy of my log as I travel, I am thinking that some form of port forwarding would put this info
available to me in the outside world.

I am unsure how to do this in general, so I am hoping someone here has the requisite knowledge to share to help me get this going.

+ See " Viewing the Spot Database Display from Another Computer, Tablet, or Smart Phone" in

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

     73,

             Dave, AA6YQ





Re: Setting unto serve Spots to outside world?

Dave AA6YQ
 

+ AA6YQ comments below

I currently successfully have SpotCollect configured to serve a webpage of my filtered spots on my internal internet.

I have a new need developing in which as I travel and operate remote base, I want to access my current needs same as I spot them at
home.

Rather that maintaining a up to date copy of my log as I travel, I am thinking that some form of port forwarding would put this info
available to me in the outside world.

I am unsure how to do this in general, so I am hoping someone here has the requisite knowledge to share to help me get this going.

+ See " Viewing the Spot Database Display from Another Computer, Tablet, or Smart Phone" in

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

73,

Dave, AA6YQ


Setting unto serve Spots to outside world?

David Reed
 

I currently successfully have SpotCollect configured to serve a webpage of my filtered spots on my internal internet.

I have a new need developing in which as I travel and operate remote base, I want to access my current needs same as I spot them at home.

Rather that maintaining a up to date copy of my log as I travel, I am thinking that some form of port forwarding would put this info available to me in the outside world.

I am unsure how to do this in general, so I am hoping someone here has the requisite knowledge to share to help me get this going.

Many thanks for all the help I have received here!

73 de W5SV - David F. Reed


Re: Spot Collector not showing spots

Dave / NR1DX
 

Grant

What kind of computer are you running? Are you on a laptop and resource (memory, processor ) limited? Ran fine in the past but you loaded a bunch of stuff in the past 6months that are running in the background? etc etc

This sounds vaguely like a memory "leak" , there was a problem 10 + years ago for example where one of the actors in the Windows office suit would over time coral more and more memory until the operating system locked up. If it is a memory leak the bad actor may not be DXLab at all

On boot up open task manager , click on the top of the memory column. This will show you in descending order which programs are using memory. Take a screen shot and save it. Then in a couple hours when spot collector goes deaf open task manager and see who if at all the memory hog is

Long shot to be sure but worth a shot and educational.

Dave
NR1DX

On 4/14/2021 11:48 AM, Grant Kesselring wrote:
My spots database is currently <5MB, pruned on startup and for entries older than 1 day.

Dave, I will follow up with your original suggestion regarding anti-malware interfering with SpotCollector.  Unfortunately, in my case it seems that everything works as expected for several hours at time.  Then, all of a sudden all the spot sources get suspended, and SpotCollector does not respond to termination commands.  So, it will take some time on my end to experiment.

My current session (Spot Collector only) has been getting spots for about 2.5 hours now.  If I know precisely when the spots stop, are there any Windows Defender, ESET, etc logs I can check to see what happened around that time?
--
Dave Manuals@ArtekManuals.com www.ArtekManuals.com
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Re: Spot Collector not showing spots

Dave AA6YQ
 

+ AA6YQ comments below

My spots database is currently <5MB, pruned on startup and for entries older than 1 day.

Dave, I will follow up with your original suggestion regarding anti-malware interfering with SpotCollector. Unfortunately, in my case it seems that everything works as expected for several hours at time. Then, all of a sudden all the spot sources get suspended, and SpotCollector does not respond to termination commands. So, it will take some time on my end to experiment.

My current session (Spot Collector only) has been getting spots for about 2.5 hours now. If I know precisely when the spots stop, are there any Windows Defender, ESET, etc logs I can check to see what happened around that time?

+ SpotCollector is working correctly, so its errorlog would show nothing untoward except network connections timing out. Something external is stopping its ability to communicate with the internet and with other applications. This is the classic symptom of interference from an anti-malware application, though that interference generally occurs immediately at startup rather than after a delay.

73,

Dave, AA6YQ


Re: Spot Collector not showing spots

Grant Kesselring
 

My spots database is currently <5MB, pruned on startup and for entries older than 1 day.

Dave, I will follow up with your original suggestion regarding anti-malware interfering with SpotCollector.  Unfortunately, in my case it seems that everything works as expected for several hours at time.  Then, all of a sudden all the spot sources get suspended, and SpotCollector does not respond to termination commands.  So, it will take some time on my end to experiment. 

My current session (Spot Collector only) has been getting spots for about 2.5 hours now.  If I know precisely when the spots stop, are there any Windows Defender, ESET, etc logs I can check to see what happened around that time?


Re: Spot Collector not showing spots

Dave AA6YQ
 

+ AA6YQ comments below
One thing that I missed when I first set up SpotCollector was to limit the size of the database. I set mine to 5 days now. The old database was almost 2 GB by the time I recognised it as the cause
Of my slow starts. 

+ Configuring SpotCollector to manage the size of its Spot Database is one of several performance optimizations described here:

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

      73,

              Dave, AA6YQ

 

 


Re: Spot Collector not showing spots

Dave AA6YQ
 

+ AA6YQ comments below
Unfortunately, I've spoken too soon.  Evidently, after 5-6 hours of spots coming in properly, this morning I find that all spots stopped at 0842Z (about 5 hours ago).  The telnet windows are still there, but unresponsive.  All of the Telnet status lights in Spot Collector are yellow.  The WSJT source status is still green even though no spots are coming across UDP.  The WSJT program is actively decoding stations, so there is activity that would generate spots.  The only way to recover is to terminate Spot Collector from the task manager.  It does not respond to termination using DXLab Launcher.

I use Windows Defender and ESET for anti-virus. 

+ Please see the recommendation in my first response:

https://groups.io/g/DXLab/message/200858

     73,

           Dave, AA6YQ

 


Re: Spot Collector not showing spots

Steve Wedge
 

I, too, had some issues after the last windows update. When starting the DXLab Suite, as each application loaded, I got a message from Windows security asking me to allow the app to run. 

I answered yes to each of them and everything then ran normally except for WSJT-X, which showed signals on The waterfall but wasn’t decoding. (Yes, I know it’s a different app but figured I’d put this out for everyone’s convenience). I had to do a full shut down and restart to make everything work again. 

One thing that I missed when I first set up SpotCollector was to limit the size of the database. I set mine to 5 days now. The old database was almost 2 GB by the time I recognised it as the cause
Of my slow starts. 

TNX es 73,

Steve Wedge, W1ES/4

Time flies like an arrow.  Fruit flies like a banana.


Sent from ProtonMail for iOS

--
73,

Steve, W1ES/4


Re: Spot Collector not showing spots

Grant Kesselring
 

Unfortunately, I've spoken too soon.  Evidently, after 5-6 hours of spots coming in properly, this morning I find that all spots stopped at 0842Z (about 5 hours ago).  The telnet windows are still there, but unresponsive.  All of the Telnet status lights in Spot Collector are yellow.  The WSJT source status is still green even though no spots are coming across UDP.  The WSJT program is actively decoding stations, so there is activity that would generate spots.  The only way to recover is to terminate Spot Collector from the task manager.  It does not respond to termination using DXLab Launcher.

I use Windows Defender and ESET for anti-virus. 

Thanks for the help.


Re: Spot Collector not showing spots

Dave AA6YQ
 

+ AA6YQ comments below

Thank you for your quick response. I failed to mention one other detail in my previous post. During the same time-frame as these Spot Collector issues popped up for me, Win10 forced me to do an upgrade. Tonight as I continued to dig through the documentation for Managing Spot Sources, I checked this in my settings:
--> via the Network section of the Windows Control Panel, configure
--> Windows to never power down the wired or wireless adapter by which
--> your computer is connected to the internet
It turns out that under Power Management of my Ethernet Connection Properties, the 'Allow the computer to turn off this device to save power' was checked. I unchecked it, and it appears things are back to normal. Perhaps the Windows update mucked with those settings?

+ Windows Update should not modify Windows settings, but sadly it seemed to do so in this case.

+ A list of all potential causes of "no new Spot Database Entries" is here

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

73,

Dave, AA6YQ


Re: Spot Collector not showing spots

Grant Kesselring
 

Dave,
Thank you for your quick response.  I failed to mention one other detail in my previous post.  During the same time-frame as these Spot Collector issues popped up for me, Win10 forced me to do an upgrade.  Tonight as I continued to dig through the documentation for Managing Spot Sources, I checked this in my settings:
--> via the Network section of the Windows Control Panel, configure Windows to never power down the wired or wireless adapter by which your computer is connected to the internet
It turns out that under Power Management of my Ethernet Connection Properties, the 'Allow the computer to turn off this device to save power' was checked.  I unchecked it, and it appears things are back to normal.  Perhaps the Windows update mucked with those settings?

Spots are streaming in from all sources again.  Thanks for the help!

73, Grant K1KD


Re: Spot Collector not showing spots

Dave AA6YQ
 

+ AA6YQ comments below
I have had SpotCollector configured to source four telnet dx cluster, IRC and WSJT-X for several weeks without problems.  Spots have been appearing in the SpotCollector window from all sources as expected.
 
A few days ago, I made a change to the awards I wanted to track.  In addition to selecting award tracking for DXCC Bands & Modes, I included WAS Band & Mode as well.  After making the change, I closed DXLab Suites and then re-launched the program.  Ever since then I have had trouble with Spot Collector.  Initially, I am able to connect to each of the spot sources, and those spots appear in the Spot Collector window.  However, a few minutes later all the spots stop even though the Spot Source status lights remain green.  After perhaps 10-20 minutes, all of the lights go to yellow or red.  In the Telnet window I get an error such as this:
 
Winsock Error # 10060 - The attempt to connect timed out @ 4/14/2021 0009
 
The WSJT-X spot source using port 2237 also initially works, but then abruptly quits after a few minutes.  The DXLab SC_WSJTX indicates that SpotCollector and WSJT-X are both connected. 
 
Any idea what could be going wrong?

+ That could be your anti-malware interfering with SpotCollector. As a diagnostic step, reboot Windows into "Safe mode with Networking", and start SpotCollector. Any change in behavior?


       73,

             Dave, AA6YQ


Spot Collector not showing spots

Grant Kesselring
 

I have had SpotCollector configured to source four telnet dx cluster, IRC and WSJT-X for several weeks without problems.  Spots have been appearing in the SpotCollector window from all sources as expected.

A few days ago, I made a change to the awards I wanted to track.  In addition to selecting award tracking for DXCC Bands & Modes, I included WAS Band & Mode as well.  After making the change, I closed DXLab Suites and then re-launched the program.  Ever since then I have had trouble with Spot Collector.  Initially, I am able to connect to each of the spot sources, and those spots appear in the Spot Collector window.  However, a few minutes later all the spots stop even though the Spot Source status lights remain green.  After perhaps 10-20 minutes, all of the lights go to yellow or red.  In the Telnet window I get an error such as this:

Winsock Error # 10060 - The attempt to connect timed out @ 4/14/2021 0009

The WSJT-X spot source using port 2237 also initially works, but then abruptly quits after a few minutes.  The DXLab SC_WSJTX indicates that SpotCollector and WSJT-X are both connected. 

Any idea what could be going wrong?

73, Grant K1KD

7181 - 7200 of 207995