Starting in WD 3.0.3.3, when ARCHIVE_WAV_FILES="yes" is defined in wsprdaemon.conf a currently running WD client will start to cache all wav files after they are decoded and queued for posting to wspr

Ranking system will resume operation later today. Normal data will start at 0000Z. There is some improvement is trapping false decodes but more to follow.

When do old ov events clear? I am showing some from the 6th of August still today the 11th. 73 Steve KD2OM

Some of you may have noticed that I stopped ranking on my http://jimlill.com:8088 page. I did it to allow easier/riskfree changes to the scripts that run that. With the proliferation of false decodes,

I am getting these errors: Found 8 new 'ERROR:' lines in /dev/shm/wsprdaemon/recording.d/VE/160/decoding_daemon.log among its 4470 new log lines. Thu 11 Aug 2022 09:31:37 UTC: decoding_daemon() ERROR:

I am debugging one of the final new capabilities of WD 3.0 and need a WD site which experiences frequent overload events. Until now WD has monitored the number of OV events by instructing kiwirecorder

I host a meeting which frequently runs to 19:00 UTC or longer where we discuss the use of WD, antennas and a range of associated (mostly technical) topics. PM if you are interested in joining the meet

I vaguely recall Phil, KA9Q, commenting on the effects of higher values. 500 is the default, I know some are running 10000. Do the odds of false decodes increase with those highers values? 73 Jim WA2Z

Yes, one Bodnar Mini will feed two Kiwis at the default (32dB) output level, making them more affordable for people with multiples. Or, at least, all seems to be working fine over the last 45 minutes

I took all the spots I had scraped, good and bad, during the period 8/7 0000Z-1300Z and ran them through my script that validates them against qrz.com. Attached is the output of the "bad" ones. There

While it's difficult to exactly quantify the number of these, as I mirror the wsprnet database (via wsprdaemon.org), I've been able to dig in and examine them. Here are a few of my observations: they'

Whether Bodnar or other, it seems like this is only needed for FST4W "slow" modes, am I correct? Besides the added cost, I wonder if there is any penalty with the required hook-up adding common-mode o

The HF bands, 10, 15, 20, 30, 40 and 80 are IMHO GPS stabilized with homebrew hardware. The amplifier I am driving is now holding. SWR is not great so power (EIRP) is taking a hit. That said Tom WA2TP

I'm planning to connect two Bodnar dual-output reference clocks to my 4 KiwiSDRs. I already have one working successfully with my AirSpy R2 using its default configuration. I understand I will have to

My first time using GROUP, sorry if I botched this… The 160M system will being broadcasting (1 watt into a 43’ vertical) MINIUTE MODE PERIOD 0 WSPR 120 5 FST4W 300 (skipping 120 as it is redundant wit

02:20 UTC / 7:20 PM PST Begin FST4W 20M Mode 15 2 watts Big skyloop San Jose, CA

Past 10 hours FST4W 80m Mode 5 2 watts big sky loop San Jose, CA ------------ Past 10 hours WSPR 80m Mode 2 200 milliwatts small sky loop San Jose, CA -------- 14:50 UTC / 7:50AM PSTBegin FST4W 15m Mo

Hi Rob, I found a strange problem with my pi4, wondering why the spotting results became very different suddenly on the lower frequency bands with nothing changed of the antenna setup. here is the res

Just last night I learned that when the WD server doesn't have enough CPU to finish a WSPR decode in 110 second, it falls behind by one WSPR cycle and never catches up. Until I find the time to fix th

All, Just starting with FST4W on Wsprdaemon used it a lot on 2200 and 630 in the winter time with wsjt on PC and RSP dx. So beam to Europe in daytime evening to USA and North through the night. KIWIA,