[Skimmertalk] FT8StartUp Beta Version 2.2b1

Fri Jul 26 14:47:43 EDT 2019

FT8StartUp Beta Version 2.2b1 had a delay of 10 seconds between the 2:00 
am "Kill All Rigs" and "Start All Rigs in Use" functions.  I've 
increased that to 60 seconds in Version 2.2b3. Please see if that helps 
or cures the problem.

Version 2.2b3 is available at 
https://www.dropbox.com/s/114bzc28cvfh1ig/FT8StartUp.exe?dl=0

73 - Dick, W3OA

To:
Ted Gisske <gisske at offex.com>, 'W3OA' <w3oa at roadrunner.com>, 
"skimmertalk at contesting.com" <skimmertalk at contesting.com>

Or the auto-kill/kill-all could check whether instances are killed after 
some time, and try again if not... Another option I see right now is to 
reboot the server once per day and use a scheduled task to launch all of 
this (I have it already scripted). The one thing I would have to figure 
out is how to click the StartAll, but I think there may be a command 
line option... But rebooting the server is a little brute-force...

Thanks
Andy
KU7T

------------------------------------------------------------------------
*From:* Ted Gisske <gisske at offex.com>
*Sent:* Friday, July 26, 2019 9:53 AM
*To:* 'Andy KU7T' <ku7t at ku7t.org>; 'W3OA' <w3oa at roadrunner.com>; 
skimmertalk at contesting.com <skimmertalk at contesting.com>
*Subject:* RE: [Skimmertalk] FT8StartUp Beta Version 2.2b1

Andy,

I’ve noticed the same thing. Some instances of WSJT-X  and 
CWSL_SSBWave.exe seemed slow to close on a kill rigs command. The, if I 
hit the start-all button before all instanced died, there were a lot of 
warnings about duplicate instances already running.

As a suggestion…Perhaps 15-20 seconds of dawdle time before 
auto-starting the rigs after an auto-kill would improve the issue.

73,

Ted

K9IMM

*From:*Skimmertalk [mailto:skimmertalk-bounces at contesting.com] *On 
Behalf Of *Andy KU7T
*Sent:* Friday, July 26, 2019 11:42 AM
*To:* W3OA; skimmertalk at contesting.com
*Subject:* Re: [Skimmertalk] FT8StartUp Beta Version 2.2b1

After running with the kill switch for a week, I noticed that my spot 
count went way down (1100 for the last 24 hours). I hit the kill all 
switch and found this:

  * all UI instances of WSJT-X were gone - good
  * 24 CWSL_SSBWave.exe instances were still running - not good
  * 2 wsjt-x.exe instance were running - not good

I killed the 26 orphan processes and hit the start all switch. Things 
are now moving again.

2 Questions:

  * Can the kill all switch be a little more aggressive and do full kill
    of these processes?
  * Do you think that a high CPU situation can cause fewer spots?  I am
    wondering whether 80 -90 CPU utilization may throttle already the
    spot count. I wonder if running on fewer bands would be better.
    Anyone know or have tried this?

Thanks

Andy

KU7T

------------------------------------------------------------------------

*From:*Andy KU7T
*Sent:* Sunday, July 14, 2019 8:30 AM
*To:* W3OA <w3oa at roadrunner.com>; skimmertalk at contesting.com 
<skimmertalk at contesting.com>
*Subject:* RE: [Skimmertalk] FT8StartUp Beta Version 2.2b1

Dick,

I ran for a few days with the “automatic kill switch”. I am running the 
new RP on 8 FT8 bands. It seems to work for the WSJT-X and jt9 
processes. However, I can see currently 16 processes with names 
CWSL_SSBWave.exe. Anything you can do here? I know I could use a script 
also to do that easily, but it would interfere with the FT8Startup 
functionality, so it would be better if it would do it….

Thanks

Andy

KU7T

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for 
Windows 10

------------------------------------------------------------------------

*From:*Skimmertalk <skimmertalk-bounces at contesting.com> on behalf of 
W3OA <w3oa at roadrunner.com>
*Sent:* Thursday, June 27, 2019 5:11:42 PM
*To:* skimmertalk at contesting.com
*Subject:* [Skimmertalk] FT8StartUp Beta Version 2.2b1

FT8StartUp Beta Version 2.2b1 is available for testing at
https://www.dropbox.com/s/f3rjjuzra51364v/FT8StartUp.exe?dl=0

This adds the option to "Kill All Rigs" and then "Start All Rigs in Use"
at 2:00 am every day,   This is a work around for the problem that
causes over driving the audio input to WSJT-X after long periods of
operation with CWSL_SSBWave.exe.

73 - Dick, W3OA
_______________________________________________
Skimmertalk mailing list
Skimmertalk at contesting.com
http://lists.contesting.com/mailman/listinfo/skimmertalk

Re: [Skimmertalk] FT8StartUp Beta Version 2.2b1.eml

Subject:
Re: [Skimmertalk] FT8StartUp Beta Version 2.2b1
From:
Lee Sawkins <ve7cc at shaw.ca>
Date:
7/26/2019, 1:57 PM

To:
Andy KU7T <ku7t at ku7t.org>
CC:
SkimmerTalk Reflector <skimmertalk at contesting.com>

Hi Andy

I don't know if it's related but I have seen RBN spots from you for Europeans on 6 meters that appear completely wrong.

Latest one:
SK2AU	50157.7	CW DX	0 dB	7 wpm	0010z 26 Jul

You are the only one in the world to spot this station.

These types of spots of yours end up on the 6 meter prop maps.

Lee VE7CC

----- Original Message -----
From: Andy KU7T<ku7t at ku7t.org>
To: Ted Gisske<gisske at offex.com>, 'W3OA'<w3oa at roadrunner.com>,skimmertalk at contesting.com
Sent: Fri, 26 Jul 2019 10:57:31 -0600 (MDT)
Subject: Re: [Skimmertalk] FT8StartUp Beta Version 2.2b1

Or the auto-kill/kill-all could check whether instances are killed after some time, and try again if not... Another option I see right now is to reboot the server once per day and use a scheduled task to launch all of this (I have it already scripted). The one thing I would have to figure out is how to click the StartAll, but I think there may be a command line option... But rebooting the server is a little brute-force...

Thanks
Andy
KU7T

________________________________
From: Ted Gisske<gisske at offex.com>
Sent: Friday, July 26, 2019 9:53 AM
To: 'Andy KU7T'<ku7t at ku7t.org>; 'W3OA'<w3oa at roadrunner.com>;skimmertalk at contesting.com  <skimmertalk at contesting.com>
Subject: RE: [Skimmertalk] FT8StartUp Beta Version 2.2b1

Andy,

I’ve noticed the same thing. Some instances of WSJT-X  and CWSL_SSBWave.exe seemed slow to close on a kill rigs command. The, if I hit the start-all button before all instanced died, there were a lot of warnings about duplicate instances already running.

As a suggestion…Perhaps 15-20 seconds of dawdle time before auto-starting the rigs after an auto-kill would improve the issue.

73,

Ted

K9IMM

From: Skimmertalk [mailto:skimmertalk-bounces at contesting.com] On Behalf Of Andy KU7T
Sent: Friday, July 26, 2019 11:42 AM
To: W3OA;skimmertalk at contesting.com
Subject: Re: [Skimmertalk] FT8StartUp Beta Version 2.2b1

After running with the kill switch for a week, I noticed that my spot count went way down (1100 for the last 24 hours). I hit the kill all switch and found this:

   *   all UI instances of WSJT-X were gone - good
   *   24 CWSL_SSBWave.exe instances were still running - not good
   *   2 wsjt-x.exe instance were running - not good

I killed the 26 orphan processes and hit the start all switch. Things are now moving again.

2 Questions:

   *   Can the kill all switch be a little more aggressive and do full kill of these processes?
   *   Do you think that a high CPU situation can cause fewer spots?  I am wondering whether 80 -90 CPU utilization may throttle already the spot count. I wonder if running on fewer bands would be better. Anyone know or have tried this?

Thanks

Andy

KU7T

________________________________

From: Andy KU7T
Sent: Sunday, July 14, 2019 8:30 AM
To: W3OA<w3oa at roadrunner.com>;skimmertalk at contesting.com  <skimmertalk at contesting.com>
Subject: RE: [Skimmertalk] FT8StartUp Beta Version 2.2b1

Dick,

I ran for a few days with the “automatic kill switch”. I am running the new RP on 8 FT8 bands. It seems to work for the WSJT-X and jt9 processes. However, I can see currently 16 processes with names CWSL_SSBWave.exe. Anything you can do here? I know I could use a script also to do that easily, but it would interfere with the FT8Startup functionality, so it would be better if it would do it….

Thanks

Andy

KU7T

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986>  for Windows 10

________________________________

From: Skimmertalk<skimmertalk-bounces at contesting.com>  on behalf of W3OA<w3oa at roadrunner.com>
Sent: Thursday, June 27, 2019 5:11:42 PM
To:skimmertalk at contesting.com
Subject: [Skimmertalk] FT8StartUp Beta Version 2.2b1

FT8StartUp Beta Version 2.2b1 is available for testing at
https://www.dropbox.com/s/f3rjjuzra51364v/FT8StartUp.exe?dl=0

This adds the option to "Kill All Rigs" and then "Start All Rigs in Use"
at 2:00 am every day,   This is a work around for the problem that
causes over driving the audio input to WSJT-X after long periods of
operation with CWSL_SSBWave.exe.

73 - Dick, W3OA
_______________________________________________
Skimmertalk mailing list
Skimmertalk at contesting.com
http://lists.contesting.com/mailman/listinfo/skimmertalk

Re: [Skimmertalk] FT8StartUp Beta Version 2.2b1.eml

Subject:
Re: [Skimmertalk] FT8StartUp Beta Version 2.2b1
From:
dd5xx at web.de
Date:
7/26/2019, 2:14 PM

To:
"Reflector Skimmertalk" <skimmertalk at contesting.com>

Hi all,

not related exactly to what Lee mentioned, but something similar I experienced:

Very often I see spots on RBN like JO40PA which appear as DXCC "Japan". I know for sure that this happens because the identified stations are beacons which send also its maidenhead locator, I have checked and identified this issue. In this example the locator JO40PA was logged as a callsign and thus appears on RBN. This occurs on skimmers who are skimming also for beacons. I see this often happen on bands 10m or 6m. Currently I am developing a WebCluster interface and because I wanted to get rid of those false spots I have integrated a regex filter for them. It could be implemented easily on RBN network too I guess, just a suggestion for anyone who care about. It's a simple regex one line in Javascript.

73
Saki, DD5XX

Gesendet: Freitag, 26. Juli 2019 um 20:57 Uhr
Von: "Lee Sawkins"<ve7cc at shaw.ca>
An: "Andy KU7T"<ku7t at ku7t.org>
Cc: "SkimmerTalk Reflector"<skimmertalk at contesting.com>
Betreff: Re: [Skimmertalk] FT8StartUp Beta Version 2.2b1
Hi Andy

I don't know if it's related but I have seen RBN spots from you for Europeans on 6 meters that appear completely wrong.

Latest one:
SK2AU 50157.7 CW DX 0 dB 7 wpm 0010z 26 Jul

You are the only one in the world to spot this station.

These types of spots of yours end up on the 6 meter prop maps.

Lee VE7CC

----- Original Message -----
From: Andy KU7T<ku7t at ku7t.org>
To: Ted Gisske<gisske at offex.com>, 'W3OA'<w3oa at roadrunner.com>,skimmertalk at contesting.com
Sent: Fri, 26 Jul 2019 10:57:31 -0600 (MDT)
Subject: Re: [Skimmertalk] FT8StartUp Beta Version 2.2b1

Or the auto-kill/kill-all could check whether instances are killed after some time, and try again if not... Another option I see right now is to reboot the server once per day and use a scheduled task to launch all of this (I have it already scripted). The one thing I would have to figure out is how to click the StartAll, but I think there may be a command line option... But rebooting the server is a little brute-force...

Thanks
Andy
KU7T

________________________________
From: Ted Gisske<gisske at offex.com>
Sent: Friday, July 26, 2019 9:53 AM
To: 'Andy KU7T'<ku7t at ku7t.org>; 'W3OA'<w3oa at roadrunner.com>;skimmertalk at contesting.com  <skimmertalk at contesting.com>
Subject: RE: [Skimmertalk] FT8StartUp Beta Version 2.2b1

Andy,

I’ve noticed the same thing. Some instances of WSJT-X and CWSL_SSBWave.exe seemed slow to close on a kill rigs command. The, if I hit the start-all button before all instanced died, there were a lot of warnings about duplicate instances already running.

As a suggestion…Perhaps 15-20 seconds of dawdle time before auto-starting the rigs after an auto-kill would improve the issue.

73,

Ted

K9IMM

From: Skimmertalk [mailto:skimmertalk-bounces at contesting.com] On Behalf Of Andy KU7T
Sent: Friday, July 26, 2019 11:42 AM
To: W3OA;skimmertalk at contesting.com
Subject: Re: [Skimmertalk] FT8StartUp Beta Version 2.2b1

After running with the kill switch for a week, I noticed that my spot count went way down (1100 for the last 24 hours). I hit the kill all switch and found this:

* all UI instances of WSJT-X were gone - good
* 24 CWSL_SSBWave.exe instances were still running - not good
* 2 wsjt-x.exe instance were running - not good

I killed the 26 orphan processes and hit the start all switch. Things are now moving again.

2 Questions:

* Can the kill all switch be a little more aggressive and do full kill of these processes?
* Do you think that a high CPU situation can cause fewer spots? I am wondering whether 80 -90 CPU utilization may throttle already the spot count. I wonder if running on fewer bands would be better. Anyone know or have tried this?

Thanks

Andy

KU7T

________________________________

From: Andy KU7T
Sent: Sunday, July 14, 2019 8:30 AM
To: W3OA<w3oa at roadrunner.com>;skimmertalk at contesting.com  <skimmertalk at contesting.com>
Subject: RE: [Skimmertalk] FT8StartUp Beta Version 2.2b1

Dick,

I ran for a few days with the “automatic kill switch”. I am running the new RP on 8 FT8 bands. It seems to work for the WSJT-X and jt9 processes. However, I can see currently 16 processes with names CWSL_SSBWave.exe. Anything you can do here? I know I could use a script also to do that easily, but it would interfere with the FT8Startup functionality, so it would be better if it would do it….

Thanks

Andy

KU7T

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986>  for Windows 10

________________________________

From: Skimmertalk<skimmertalk-bounces at contesting.com>  on behalf of W3OA<w3oa at roadrunner.com>
Sent: Thursday, June 27, 2019 5:11:42 PM
To:skimmertalk at contesting.com
Subject: [Skimmertalk] FT8StartUp Beta Version 2.2b1

FT8StartUp Beta Version 2.2b1 is available for testing at
https://www.dropbox.com/s/f3rjjuzra51364v/FT8StartUp.exe?dl=0[https://www.dropbox.com/s/f3rjjuzra51364v/FT8StartUp.exe?dl=0]

This adds the option to "Kill All Rigs" and then "Start All Rigs in Use"
at 2:00 am every day, This is a work around for the problem that
causes over driving the audio input to WSJT-X after long periods of
operation with CWSL_SSBWave.exe.

73 - Dick, W3OA

Subject:
Re: [Skimmertalk] FT8StartUp Beta Version 2.2b1
From:
Andy KU7T <ku7t at ku7t.org>
Date:
7/26/2019, 12:57 PM

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.contesting.com/pipermail/skimmertalk/attachments/20190726/387b4b9f/attachment-0001.html>