Very new to Linux & Pi, so being very cautious...but also not afraid to ask the very dumb questions that follow below. When I initiated a new installation of Wsprdaemon, it displayed a warning

Thank you Rob No doubt there could be a difference between a narrow band Air Spy and the Kiwi in a band hopping application. Another possible issue that could influence the outcome will be the

Hello, I am not sure what you mean with changing colors but I did a small change to the Station Noise Stats page to make the colors there more "stable". Hope that resolves your issue. Regards Arne

Dean The link you gave is to wspr.live, which is written and maintained by Arne. He takes the wsprdaemon noise data and provides these plots in Grafana. Your queries are best answered by him. If I

There are two noise level measurement techniques reported by wsprdaemon: In Red is the RMS noise level for the whole WSPR band taken from the 0-1 seconds and 110-120 seconds of each 2 minute WSPR

Hi Bruce, In case you and others in this group missed my posts' to Roland's WSPR Beacon Project Telegram group on this subject, I'll copy those remarks here, but the subject of how to construct high

From my experience on both my own and KD2OM kiwi, above 10 MHz or so, the Kiwi may need a bit on gain in the path depending on what antenna is used. You may note that both Steve KD2OM and

Rolf, I wouldn't be at all surprised if the Airspy HF+ Discovery outperforms the KiwiSDR for WSPR spot counts, give the different architecture and narrower bandwidth on the Airspy. In my informal

Greetings y'all HB9VQQ is presently performing a test of Kiwi with Rpi4 running WD against an Airspy HF Discovery running Wsjtx with Rpi4 on the same antenna through a splitter

Why do the colors of the lines change? The lines from my three receivers change, it seems to vary based on the noise level. 73 Steve KD2OM

Hello Rob, that is great to hear! A few more details on my setup: I am using a QCX connected to a very cheap USB soundcard connected to a raspberry pi 3B. The loopback device is just software created

Hi Martin, Your use of the AUDIO input feature has stimulated me to raise its priority in debugging of WD 3.0. Also, have you tried using a virtual audio channel as input to WD? Thanks, Rob -- Rob

Great, thank you for providing and maintaining wsprdaemon! It is a very nice standalone solution.

Hi Martin, Thanks for that welcome report. In WD 3.0 I will study how to incorporate your fixes. Rob

Hello, baseband audio is working for me, however, two things needed tweaking beforehand: 1. the name of my soundcard is "plughw:CARD=Loopback,DEV=1" which does not fit into the naming scheme of

OK, after 24 hours run time at -20 dBm output, the clear "winner" was W4HOD in Alabama (USA), spotting me twice in 24 hours. My setup is still running, and at 1742 UTC today another station in the

Ouch, I hate to bombard this group yet again with a post, but my UTC timing was off off today too! I commenced transmitting at 10 microwatts 1506 UTC today (October 6). Promise this will be the last

Correction and an oops...I hit the wrong button on the step attenuator when changing power a few minutes before 1600 UTC, and so had the power running 10 dB too high, at 0.1 mW, and K9AN "snuck in"

After nearly 24 hours running at 50 microwatts (-13 dBm), there were still 8 stations who heard me, though the total spot count and geographical diversity is narrowing. And some stations were hanging

Hi Bruce, well, we sure have to believe the statements on power sent :-). I myself on TX am using the WSPRlight flexi and I checked the power with a spectrum analyser. The settings seem to be about