I am running an experiment with WB6YRW who has been sending FST4W-1800 on 160M. Decoding of FST4W is much more efficient than WSPR, so Unless you are running WD On a Pi, I think you can try

This is great. Thank you Rob. So what are opinions on what a reasonable selection of FST4W decoding to use at this point? I have started with: 2200 - W2:F2:F5:F15:F30 630 - W2:F2:F5:F15 160 -

I will soon be installing 3.0.3 on a headless Ubuntu 20.0.4 and will look for the problem you encountered. -- Rob Robinett AI6VN rob@... mobile: +1 650 218 8896

Hey Rob-- OK, I updated to 3.0.3. No worries about the "no kiwi connection" problem, it eventually sorts itself out. One thing to note, I'm now running both of my sites on a fresh Ubuntu 20.04

Hi Bryan, I have just published WD 3.0.3 and your site is one of the few beta sites I couldn't update. While there are no major changes in the code since the 3.0.2.6 version you are running, there

This morning I changed the version number of WD 3.0.2.6 to WD 3.0.3 and checked it in as the 'master' version. WD 3.0.2.6 had been running on 32 beta sites, and now the 21 sites to which I have remote

Although I have run wsprdaemon from the early days, before the merge feature was added., I think I only briefly used any RPi variant. At the time, I was running Odroid XU4 for other SBC projects so

Br yan Appreciate the update - glad to read you got round the astral problem. It's excellent that you have your Kiwi at a location above the Arctic Circle. But that spectrum is truly 'pretty bad',

Hey Rob and Gwyn-- Thanks for your help on this. I ended up just modifying suntimes_astral2-2.py to just return "18:00 06:00", so got around that problem. I'm not changing frequencies based on

Thanks Rob! 73 de Andy G0FTD

Yes, that should build the newer Bash. Gwynn G3ZIL performed that upgrade to his 64 bit Pi4 running bullseye and it has run fine for weeks. I chose to install 64 bit Ubuntu on my Pi4.

On Fri, May 27, 2022 at 03:39 PM, Rob Robinett wrote: Gwyn has compiled Bash 5.1.16 on his bullseye Pi 3b and that fixes the problem.Does this mean that you can use this source and compile in Bullseye

Thanks! The zombies appear to have been successfully driven out of my system with the new update 😁 Cheers, Chris On 2022-06-04 08:11, Rob

This morning I made further refinements to WD 3.0.2.6 to address some 'zombie kiwirecorder' issues. That newest 3.0.2.6 has been running cleanly on about 20 servers for 2-6 hours So I would strongly

Yep. At least I have: in /etc/sudoers. I assume that's what you mean? I can login as wsprdaemon and do stuff like "sudo reboot" without getting

Is your account set up for your user to 'auto-sudo'? -- Rob Robinett AI6VN rob@... mobile: +1 650 218 8896

Hi Rob I'm already on 3.0.2.6 It looks like only the WSPR decoding process is getting killed: but there is still a kiwirecorder.py running

There were scheduling problems in 3.0.2.5 which are corrected in 3.0.2.6

Hi Chris, Run 'git pull' to get the latest version of 3.0 after which 'wd -V' should print 3.0.2.6. In beta testing I found that on busy servers the kiwirecord.py process which records the wav files

Hi I run a sliding schedule of bands that connect to my KiwiSDRs. The connections to the Kiwis are not going away at the end of a scheduled timeframe any more. New connections start all right, but