Hi Rob, Thanks very much for your reply, it confirms the feeling I had but just was not sure enough. I just found a Pi3 laying around for future use, so I will give it a go and try to get it

Hello Hans, I CPU on the Kiwi is 100% consumed by the Kiw's software, and it was at the suggestion of John Seamons (the author of teh Kiwi) that I started developing wsprdaemon as a stand alone

WD must be run on a platform separate from the KiwiSDR. There are simply not enough MIPS in the kiwi, ven with a BBAI wa2zkd

Hello, I am searching for the way to install wsprdeamon on my Kiwi SDR. Until now I did not find if this is possible or how this should be done. The only procedure I find is to install the

Hey Guys-- I also don't have GPS at my Kiwi location (I'll run another coax soon), so I gave the -w a try. I noticed that WSPRD_CMD_FLAGS="-w" overwrote the default wsprd command arguments, instead

Newer decoders do go through multiple passes, extracting energy from previously decoded spots to improve success and they seem to do a very good job of digging out spots on top of one another. But

Thanks Rob, I may indeed give the -w a try so see if it impacts the spot count any for my KX4AZ/T remote receiver, to catch some "strays" outside of the band. Right now I am only letting it run on 20

Hi Bruce, No questions are dumb, and yours is particularly insightful. WD uses the 'wsprd' binary to decode spots and when is it executed with the ''-w" (wideband decode) command line flag it will

I am not an experienced wsprdaemon user so I hesitate to ask what is probably a dumb question, but here goes anyway, my curiosity compels me... ...I was testing a 10 mW WSPR beacon on 20m today and

---------- Forwarded message --------- From: Mark Jessop <notifications@...> Date: Sun, Jan 30, 2022 at 1:15 PM Subject: Re: [rrobinett/wsprdaemon] Possibility of SpyServer Client Support? (Issue

FYI... ---------- Forwarded message --------- From: Mark Jessop <notifications@...> Date: Sun, Jan 30, 2022 at 2:53 AM Subject: [rrobinett/wsprdaemon] Possibility of SpyServer Client Support? (Issue

In the meantime I figured out to change the version wsprdaemon.sh asks for from 2.3.0 to 2.5.4. Seems to be running the new version fine now. .

I don't think WD 2.10k users suffer from that memory leak, perhaps because it uses the file in/out interface to wsprd. There are sites running WD untouched on a 1GB Pi4 for years without OS memory

How does someone upgrade wspr to V2.5?

Regardless of what OS or computer type you run, you should consider updating your wsprd executable to 2.5.x. As of that revision, a memory leak is fixed.

I may be the only one who uses one of those for WD, but just in case there are others... I compiled from source the latest version of wsprd and jt9 and have them running. An easy install and if

A second Raspberry is running the FiFiSDR Audio input devices: **** List of CAPTURE Hardware Devices **** card 1: FiFiSDR [FiFi-SDR], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0:

Well indeed. Edit the conf and rerun the script. E.

I have 2.10k working on my Raspberry Pi Buster It starts the test and finds the Audio Codec But what to do then ? Adjust the input gain and restart test? [-+q] => + amixer: Unable to find simple

This discussion stimulated me to resume WD 3.0 installation testing on my Pi4b running bullseye, but of course I immediately encountered the 'missing qt5' problem. However this thread on the Pi forum