Overload reporting requests
1) Improving propagation conditions are causing more overload events at the wsprdaemon receive sites. Currently the only kiwirecorder overload ("OV") report mechanism is to print 'ADC OV' stdout to a log file. To avoid overloading the file system with log files filled with 'ADC OV' lines, wsprdaemon must kill and restart a kiwirecorder session when it log file grows too large. Such restarts result in the WD client missing recording at least one 2 minute WSPR cycle.
If the current overload count were reported on the Kiwi's /status page, there would be no ever-growing log files and thus no need for restarts. Alternatively, perhaps kiwirecorder could write the count to a 'ov.status' file. I'm not trying to dictate a solution, just suggest a couple which occur to me.
2) In addition or as another feature, it would help us control an RF attenuator board we are developing for the Kiwi if we could learn the peak ADC value (high watermark) during a sample interval.
#1 would seem easy to implement and the most needed, while we could understand if #2 required a lot more work due to changes required to the FPGA.
Thanks for considering these requests,
[edited: "kiwireporter" => "kiwirecorder"]