The new noiseblanker algo's which are inplemented in the kiwi-software recently are sometimes quite efficient in blanking the noise. Does it have effect in the kiwirecorder, when it records the wave files for WD ?
Is there a way to implement the noise blanking system of the kiwi-rx for WD users ?
Thanks for info - forgot to ask this question during our weekly meetings...
Re: Kiwi-SDR Noiseblanker with WD has any effect ?
Rob, this might be a misunderstanding:
My question is, if the kiwirecorder within wsprdaemon will recognize, that at the kiwi-gui a noiseblanker function is choosen and active and therefore the wav-recordings wsprdaemon does will be pre-processed by the noise-blanker.
According to the kiwi-forum there must be a function inside the kiwirecorder to incluse the kiwinoiseblanker, when used/activated (ext. "-nb", if I understood correctly)
In the meantime I made the following test:
situation: on 80m at daytime I have a noticable electrical noise from a fence here in the neighborhood. While the band is not very busy I compared the spots from the kiwi-build-in wspr decoder to the S/N-numbers wsprdaemon is reporting.
With kiwi Noiseblanker acticated (std position) = kiwi-decodes consistantly 4db better than wd-decodes
Without kiwi Noiseblanker - kiwi decodes are exactly same than WD-decodes
That is the background I ask, what I can do, to preprocess the kiwirecorder wav-files with the kiwi-noiseblanker...
I tried to find the kiwi-recorder configuration file (or something similar), but couldn't find anything
What do I need to change or configure in WD to get the kiwi-noiseblanker pre-process the wav-files any in WD - it seems for WD it is not using any noiseblanker, regardless if I switch it on or off...
Based on my many hours testing it is clear, that in my noise situation using the kiwi noiseblanker definitely improves decoding significantly. How to implement in Wsprdaemon ?
Thanks for advice for a 'non-expert' of Linux...
(Couldn't even call the help page of kiwirecorder..., etc... ON5KQ=Linux idiot...hi)
Rob, one more question:
Once you have shown, how to view the helpfile of the kiwirecorder.
You input something in the Linux terminal window and then a overview helpfile of the kiwirecorder could be viewed - unfortunately I forgot, how to do that.
It also might be necessary to call that helpfile from a particular folder ...
By the way: I am now running wd on a Raspberry 4 with 4Gb.
In the coming weeks I will also finish the complete relocation of all the WSPR stuff into the other room. It requires some new network cables and distribution amps - I also hope to get decent GPS reception, which I don't have here at the old place... so the system may be down for some time...
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
666 pi 20 0 459848 328936 25000 S 2.9 8.2 633:43.04 lxpanel --profile LXDE-pi
3465 pi 20 0 43012 19444 9304 S 2.9 0.5 780:28.82 python -u /home/pi/wsprdaemon/kiwiclient/kiwirecorder.py --freq=474.2 --server-host=192.168.158.74 --server-port=8073 --OV --user=wsprdaemon_v2.9g --password=ki+
3802 pi 20 0 43012 19280 9136 S 2.9 0.5 778:21.33 python -u /home/pi/wsprdaemon/kiwiclient/kiwirecorder.py --freq=3592.6 --server-host=192.168.158.74 --server-port=8073 --OV --user=wsprdaemon_v2.9g --password=k+
4745 pi 20 0 43012 19428 9296 S 2.9 0.5 777:32.54 python -u /home/pi/wsprdaemon/kiwiclient/kiwirecorder.py --freq=28124.6 --server-host=192.168.158.75 --server-port=8073 --OV --user=wsprdaemon_v2.9g --password=+
To get help on kiwirecorder:
<nabble_embed>pi@Maui-Pi85:~ $ ~/wsprdaemon/kiwiclient/kiwirecorder.py -h
Usage: kiwirecorder.py [options]
-h, --help show this help message and exit
-s SERVER_HOST, --server-host=SERVER_HOST
Server host (can be a comma-delimited list)
-p SERVER_PORT, --server-port=SERVER_PORT
Server port, default 8073 (can be a comma delimited