It should have been obvious to me why the 160M FST4W band is 200 Hz higher in WSJT-x ;=( HF band FST4W experiments I have been running with Stu WB6YRW strongly suggest that FST4W signals should not be

At the suggestion of Holger OE9GHV, I have moved the location of WD's temporary files from /tmp/wpsrdaemon to /dev/shm/wsprdaemon. The /dev/shm file system is created automatically and its size scaled

Do overload events show up in the error logs when using wdle? Steve KD2OM

I recently repaired a dipole antenna used at my KX4AZ/T locationin Michigan, and the restored spotting performance motivated me to purchase a second KiwiSDR, in order to get full WSPR band coverage. L

Hi Tom, I am cc'ing this to the group since it seems of general importance to WD users. Thanks for looking so closely at that difference which I think can be explained by the difference in how WD is r

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

I forget. How can I display my noise charts on my local wsprdaemon machine? Where can I learn to use wspr.rocks ? john

I am now watching for FST4W-120 on 80 meters Type-1 Matenhead (4CHR) only. 73 TI4JWC

Hi Rob, I have been running WSPRdaemon on a RPI3 for a few days now and I have many problems looking as overload of the RPI. Looking at the processor from the RPI I see a CPU usage which never exceeds

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 ju

Hey Rob-- Corner case: The sun is always up or down. From watchdog_daemon.log: Thu 02 Jun 2022 05:05:01 UTC: watchdog_daemon() Starting in /home/wsprdaemon/wsprdaemon as pid 21929 Thu 02 Jun 2022 05:0

Rob mentions: in your case the much bigger problem is a memory leak in the Bash 5.1.4 included in bullseye. Gwyn G3ZIL identified that problem which leads the Pi to run out of memory in 1-5 days. I no

There were scheduling problems in 3.0.2.5 which are corrected in 3.0.2.6

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 at

A Raspberry Pi runs from SD-Card. so It might be a good idea when /tmp/wsprdaemon is not on the same SD-Card. Is there an easy way to convince wsprdaemon to use an external USB-Stick or disk to store

Hi Rob, I'm wondering if you are working towards running wsprdaemon with SDR Play devices on a headless Raspberry Pi 4 Regards, John VK4CT

I have started tracking which spots get rejected on wsprnet uploads. The wsprdaemon.sh -le command in v3.02 is useful for doing this. I have found 2 categories so far bad decodes or otherwise misforme

I almost always execute 'wd -a' to start WD and 'wd -z' to stop it. However if you want to have WD start automatically after power-up or reboot, then execute 'wd -A'. It configures Linux to run WD at

The new Wsprdaemon version 3.0 software running on 20 sites from Maui to Europe is configured to simultaneously decode and report to wsprnet.org WSPR-2 and all of the FST4W-xxx modes on 630M and 160M.

I have just checked in a revision of that file which (I hope) fixes a few errors and adds a much more detailed explanation of the settings in your wsprdaemon.conf For those of you already running 3.0.