All, I am new to WsprDaemon, having only had things up and running for a couple of days. Pretty modest station - single KiwISDR with 8 WSPR channels into an end fed half-wave cut for 20M. Currently

Many thanks for all the explainations... it is clear now. So as a conclusion from the client point of view: In any case it is best, to just keep the system running and not to try some "tweek-action"

The WD clients independently upload spots to two servers: 1) 'Classic spots' (like those from WSJT-x) are sent directly to wsprnet.org 2) 'Enhanced spots' (the same spots with additional information)

Hello Ulli Some time ago I put a simplified data flow at the bottom of the webpage at: http://wsprdaemon.org/technical.html JIm, WA2ZKD has moved to using spots from wsprdaemon, database wsprnet,

Hi Gwyn, Does WA2ZKD's list reflect the spots in the wsprnet.org site, or does it show wsprdaemon database ? New spots are showing up now again on the WA2ZKD site as well as on Phil's website

I've emailed Rob with a note that many of the API requests to wsprnet.org are timing out and there are large gaps in the sequence numbers of spots being returned by wsprnet.org. There is certainly

13h50 utc can't find any spots on the wsprdaemon server database when connecting via Grafana... since early morning all bands. Originally I saw a lot of files on my local workstation in the wsprdaemon

Might be a loading/DDOS thing as I can see some of my spots (one band) but tried to refresh for all bands and no luck. The aggregation site pe1itr.com failed to tally today. On WA2ZKD's site i'm too

No spots sinds several hours... My local PC works normally with well above 2000decodes/hour... But nothing appears at the servers ??? Ulli

I have a suspicion that the fence pulse might be overloading the Kiwi frontt-end, in which case information is lost anyway before it gets to the noise blanker stage. Another option, assuming that you

Yes, It is my intention to compare the Noise blanker enabled WD script against a standard (original) WD script directly and see, if there is any significant difference in reporting statistics. For

Ulli, I remember articles written when WSPR was new and many were thinking of using noise reduction features. The developer recommended to not use any processing on the I/Q files as the WSPR

Yes, you must modify the WD.sh source code. So do as you say, run a modified version on one Pi reporting as one call sign, and compare it against a standard versionof WD.sh -- Rob

hi Rob, I updated to latest version of WD with git pull now on my main WSPR Supermicro workstation... I realize, that it is not possible to use the .conf-file, but edit directly in the wsprdaemon.sh

Hi Ulli, Make sure you are running v2.10i: pi@Pi-2-KJ6MKI:~/wsprdaemon $ git pull Already up to date. pi@Pi-2-KJ6MKI:~/wsprdaemon It will be interesting to learn the results of your experiment.

Rob, this is a question for the code-expert...: Sometimes I have some fence pulse noise on one of my antennas. I found out, that when listening on this antenna with the kiwi, I can completely erase

Nice condx from Belgium to west-coast USA on 40m this afternoon - 14h30 utc.... N7XM booming here from close to Carson City, Nevada in CW band ... many others now as well... the CW-band is full of

I may not be a "top" station, but I think I'm holding my own for a newbie.  And I have improvement plans for mid-2021. FSTW4W support would provide a great excuse for building an LW/MW antenna and

In Wednesday's Zoom meeting we discussed my plan to add this feature, and based upon that feedback I won't rush to implement it. However, since many of the top spotters are running WD, it is at the

From the v1.427 release notes: