rrobinet

I have attached WD V2.5a to this post. It includes a large number of installation and run time fixes, most importantly a 'monitor for and kill zombie recording sessions on the Kiwi(s)'.

There is also major new feature: It can be configured to generate graphs of background noise level measurements at the same time as WSPR decodes which can be viewed by the Apache web service running on the WD server.
Those graphs can give you great insights into the quality of your receive system and site. However calculating the noise levels triples the CPU requirements on the server, so a Raspberry Pi which can support 20 no-noise bands can only support 8 bands with the noise feature enabled. So if you have more than one Kiwi and want noise graphs, you should wun WD on an Odroid, Atomic Pi, or x86 server running Ubuntu 18.04.

This code should be completely compatible with existing 2.3 installations, so save your WD2.3, stop your current WD with '-z', copy this code over the existing WD.sh and start it with '-a'
As before, '-s' will print the status of your system.

Because of all the fixes, I recommend that all sites upgrade to this code. Please report your experience and if you have problems you can easily revert to your WD 2.3 code.

I have attached WD V2.5a to this post. It includes a large number of installation and run time fixes, most importantly a 'monitor for and kill zombie recording sessions on the Kiwi(s)'.

There is also major new feature: It can be configured to generate graphs of background noise level measurements at the same time as WSPR decodes which can be viewed by the Apache web service running on the WD server.
Those graphs can give you great insights into the quality of your receive system and site. However calculating the noise levels triples the CPU requirements on the server, so a Raspberry Pi which can support 20 no-noise bands can only support 8 bands with the noise feature enabled. So if you have more than one Kiwi and want noise graphs, you should wun WD on an Odroid, Atomic Pi, or x86 server running Ubuntu 18.04.

This code should be completely compatible with existing 2.3 installations, so save your WD2.3, stop your current WD with '-z', copy this code over the existing WD.sh and start it with '-a'
As before, '-s' will print the status of your system.

Because of all the fixes, I recommend that all sites upgrade to this code. Please report your experience and if you have problems you can easily revert to your WD 2.3 code.

This is a major upgrade in functionality, reliability and installability from previous versions of wsprdaemon and its predecessor kiwiwspr.sh
Configured to connect to two Kiwis configured in 8 channel mode, it easily simultaneously decodes all 14 WSPR LF/MF/HF WSPR bands during every two minute cycle and reliably uploads spots to wsprnet.org

To install it:

1) login to the Pi as user 'pi' (or other non-root user) and create the directory '~/wsprdaemon'.
2) copy the attached file to that directory, rename it to 'wsprdaemon.sh', and make it executable with 'chmod +x '
3) cd to that directory and execute it: './wsprdaemon.sh'. It should walk you through the installation of all of the utility programs it needs and create a prototype 'wsprdaemon.conf' file
4) edit the wsprdaemon.conf file following the directions in it
5) to start the daemon: './wsprdaemon.sh -a'
6) to see the daemon status: './wsprdaemon.sh -s'
7) to stop the daemon: './wsprdaemon.sh -z'
8) for help about the daemon: './wsprdaemon.sh -h'

During installation it creates a tmpfs files system '/tmp/wspr-captures/...' where all of the recordings and logs are kept, so 24/7 recording of 14 bands => 3 Mbps of wav files doesn't wear out your microSD in a few months
It also modifies the systemclt files so the daemon will autostart during a powerup or reboot.

I have tested installation and operation on a clean 'Stretch' OS. The script can run in other Debian servers, but installation may require some custom tweaks.

The SW id can only be loaded into wsprnet.org by executing the 'one-spot-per-http' curl POST upload method. Many kiwiwspr and wsprdaemon sites upload 10 to 30 spots at the end of each 2 minute cycle, and using POST to upload them increases the transmission and computation burden on the clients and more importantly on the wsprnet.org server(s). The frequent 60-90 second hangs (and occasional timeouts) during http uploads compounds the inefficiencies and errors introduced by POST uploads as used by WSJT-x. In contrast WD uploads all spots from all bands gathered during a 2 minute cycle in one MEPT http transaction and the resulting efficiency allows for retries of the occasional http transfer failure.
I am not aware of any other wsprnet.org client which uploads using MEPT, so I think you can count any spots with *no* swversion field as coming from WD and I would be interested in getting the CALL of those reporters.

This is a major upgrade in functionality, reliability and installability from previous versions of wsprdaemon and its predecessor kiwiwspr.sh
Configured to connect to two Kiwis configured in 8 channel mode, it easily simultaneously decodes all 14 WSPR LF/MF/HF WSPR bands during every two minute cycle and reliably uploads spots to wsprnet.org

To install it:

1) login to the Pi as user 'pi' (or other non-root user) and create the directory '~/wsprdaemon'.
2) copy the attached file to that directory, rename it to 'wsprdaemon.sh', and make it executable with 'chmod +x '
3) cd to that directory and execute it: './wsprdaemon.sh'. It should walk you through the installation of all of the utility programs it needs and create a prototype 'wsprdaemon.conf' file
4) edit the wsprdaemon.conf file following the directions in it
5) to start the daemon: './wsprdaemon.sh -a'
6) to see the daemon status: './wsprdaemon.sh -s'
7) to stop the daemon: './wsprdaemon.sh -z'
8) for help about the daemon: './wsprdaemon.sh -h'

During installation it creates a tmpfs files system '/tmp/wspr-captures/...' where all of the recordings and logs are kept, so 24/7 recording of 14 bands => 3 Mbps of wav files doesn't wear out your microSD in a few months
It also modifies the systemclt files so the daemon will autostart during a powerup or reboot.

I have tested installation and operation on a clean 'Stretch' OS. The script can run in other Debian servers, but installation may require some custom tweaks.