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

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 ha

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 wsprdeamon

Hi Tom, WD V2.10k will fail to install on the latest 'bullseye'OS for the Pi. Is that what you are running on your PI? We are testing WD 3.0 installation on bullseye. Rob -- Rob Robinett AI6VN rob@...

Friday 18 February Due to housekeeping on the logs2 WsprDaemon server the response may be slow at times. I will be keeping an eye on performance through the day. Thank you for your patience. regards G

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 #

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.

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: subd