In response to a user request, have tested and checked in enhancements to 3.0.2.4 which add support for the feature you requested which runs the quickest wsprd on those 'noise level only' bands like W

The WD 3.0 software has been running at my AI6VN/KH6, KPH and KFS sites for several months, and in the last two weeks I have helped bring it up on an additional 8 sites. In most of those installations

Hello Rob-- I've been playing around with v3 recently, and it seems to work much better than v2.8. I like the increased debugging when shutting down, and it's gotta be easier to maintain. But, anecdot

Yes it is Friday the 13th. Owner is doing his utmost to resolve. Hope for better news tomorrow morning. Fingers crossed. Good night from France.

Rob, Can 22 meters be added to wsprdaemon? There are a few transmitters now and I believe will be more. It is the Hifer band. Wsprnet is showing it now. 73 Steve KD2OM

When WSPR is receiving a signal, does it take the average SNR or the peak SNR during the 2 minute period. There is always Qsb during the transmission. Some times signals can vary many Db’s over a 2 mi

The first 64 bit version os a Pi OS was released in February and in the process of debugging WD installation on 'bullseye', I have been able to install Wd on that 64 bit version of the OS. I found one

When using wsprdaemon -le I am seeing errors like this: ERROR: Successful curl upload has completed, but only 25 of these offered 44 spots were accepted by wsprnet.org Various numbers show up and not

what does this mean? /tmp/wsprdaemon/recording.d/K74/40/W_120/decoding_daemon.log: Mon 02 May 2022 03:53:58 UTC: decode_wpsr_wav_file() ERROR: Command 'timeout 110 nice /home/zkd/wsprdaemon/bin/wsprd

It looks like the last spots accessible at wspr.rocks are from 0116 UTC today (26 April 2022). Or is that an error on my end?

I am (attempting) to run a special event WSPR beacon with "N1D" for the call sign. So far the only spots I see are for Kiwi 1.3 decoders...so I suspect that using a 3 letter call sign is not permitted

There is the known issue, that when the wsprd decoding program starts to decode the recorded Wav-file from wsprdaemon program it should finish it decoding after max 110sec. That is because the total w

I could not see the problem at kph today, but instead there was a similar signal about 20db weaker that yesterday observed at kfs at local morning time: Obviously a 'real' signal, perhaps related to m

Question: is it "normal", that currently there is no noise data shown at wspr.live for spotters running wsprdaemon v3.0 ? I cannot see any errors here at the client side running the new V 3.0a and noi

I'd like to compare/benchmark various WD platforms. Seems like wsprd decode is the heavy load. Would timing the decode of a single 2 minute wav file by wsprd be a good way to compare. -Jim

Hi, Does anybody know the status of db1.wspr.live and db2.wspr.live? They don't seem to be responding to database queries since yesterday morning. Thanks, 73 Stefan

Greetings y'all, I have not been diving into the WD deep enough and being short of time to educate myself in regards to the program. I have a question. Suddenly the tmp/ is filling up with sh.thd.xxxx

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 anyone

Greetings all, After 40 days at the beach in AL I am back home in WI. I guess I screwed up when setting up the Kiwi and WD again. This as I forgot to change the grid square from EM60eg to EN52wx in .c

Having had this great software running trouble free for ages, this evening I have noticed that out of LF, MF, 160, 80, 40, 17 and 10, the 40 meter band is no longer either decoding or uploading to the