Just wanted to say thanks to Dick for the kill switch in Aggregator. It has made a real difference here. Usually it takes a few days for the issue with CWSL__SSBWave to show up, so nightly restarts are a nice interim fix. And thanks to Alex for writing it in the first place! I wish I had the C++ chops and time to dig in and work on it, but sadly I do not.

Dave KM3T

On Thu, Jul 11, 2019 at 3:26 PM Bob Wilson, N6TV <n6tv@arrl.net> wrote:
It would also be nice if CWSL_SSBWave could be enhanced to support the new
shared memory naming convention defined by CWSL_Tee.dll, CWSL_Tee2.dll,
etc., which I've mentioned previously (privately).

Frankly if you have an old RP and a new RP, you can do all the WSJT-X FT8
decoding on the old RP standalone, for up to 8 HF FT8 frequencies at once,
with all the decoding running right on the RP, using the built-in
sdr_transceiver_ft8 app plus SM7IUN's scripts.  No Windows software needed
beyond Aggregator (which is optional too).  It just keeps running and
running, even when you reboot Windows.

Everything you need to know is posted here:

https://sm7iun.ekelund.nu/red-pitaya/ft8-skimmer

It automatically reports to PSKReporter.info too.  You can also use it to
feed the Aggregator and the RBN

73,
Bob, N6TV


On Thu, Jul 11, 2019 at 10:54 AM Alexander Ranaldi <alexranaldi@gmail.com>
wrote:

> If there are any software developers knowledgeable in C++ that would like
> to assist in resolving the stability issue with CWSL_SSBWave, please feel
> free to investigate. I'm the author and have been unable to find the
> issue.  The code is here:
>
> https://github.com/alexranaldi/CWSL/tree/master/CWSL_SSBWave
>
> Thanks
> Alex
> w2axr
>
> On Thu, Jul 11, 2019 at 1:42 PM W3OA <w3oa@roadrunner.com> wrote:
>
> > Hi Andy -
> >
> > Have you tried this:
> >
> > 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] FT8Start and CWSL_SSBWAVE.exe stability issue.eml
> >
> > Subject:
> > [Skimmertalk] FT8Start and CWSL_SSBWAVE.exe stability issue
> > From:
> > Andy KU7T <ku7t@ku7t.org>
> > Date:
> > 7/11/2019, 10:46 AM
> >
> > To:
> > 'SkimmerTalk Reflector' <skimmertalk@contesting.com>
> >
> >
> > Good morning,
> >
> > I am using the new RP 16 bit for both CW and FT8 Skimming. I noticed that
> > my FT8 spots had stopped at some time in the last few days. CW skimming
> has
> > been stable for at least a week.
> >
> > Got on the box and stopped all "FT8 rigs". I noticed that the CPU
> > utilization was still very high. The reason is that I have about 50
> > processes of CWSL_SSBWave.exe running. I guess a reboot will fix. Can the
> > "Kill FT8 rigs" function kill all CWSL processes?
> >
> > Thanks,
> > Andy
> > KU7T
> >
> >
> > info/skimmertalk
> >
> > _______________________________________________
> > Skimmertalk mailing list
> > Skimmertalk@contesting.com
> > http://lists.contesting.com/mailman/listinfo/skimmertalk
> >
> _______________________________________________
> Skimmertalk mailing list
> Skimmertalk@contesting.com
> http://lists.contesting.com/mailman/listinfo/skimmertalk
>
_______________________________________________
Skimmertalk mailing list
Skimmertalk@contesting.com
http://lists.contesting.com/mailman/listinfo/skimmertalk