FYI, the WSJT-x packages are built for b'buster'. Until they support 'bullseye' WD can't be installed on it.

I started to look for ways to improve my spotting. I figure I should record baseline information. I thought I would calibrate the signal level with my Elecraft XG3. I placed a 50 ohm load at the KIWI-

This is again something for Arne, the developer of the great Grafana page wspr.live The following may be a possible bug-report - I just want to notice: The grafana page offers the possibility to compa

I wonder if anyone has ever done any rough calculations using the WSPR database to do some predictive calculations around the spot numbers that could be achieved in a continuous decoding (i.e. with a

I'm starting this as a new topic because I'm afraid we are verging on severe topic drift where it has been. This is revision 02 of the earlier draft with an addition intended to help reconcile the pre

Hi, My Kiwi is here - http://84.228.126.167:8073/ I am testing a problem where my Kiwi doesn't detect a local transmitter at 14.07Mhz. I am testing now a configuration where 1. "WSPR extensions" are o

Greeting y'all, Suddenly I have a new broad band QRM here centered on about 3.5 Mhz S9 - 40++. Looks like switcher or perhaps more likely a high power grow light nearby. I guess until I have located t

I have been helping a number of WD users today and encountered problems with installing v2.10k. It appears that in releasing the new 'bullseye' OS, the Pi people have changed an attribute of the previ

Hi, Because of some network configuration problem, my KIWISDR is changing its IP address every few hours. Is there a method to periodically update the address in the wsprdaemon.conf file ? Thanks Gur

Hi Chris, How nice to hear from you. I have finally resumed work on WD version 3.0 after being interrupted by a house move last February. LX1DQ experienced the same problem as you, and your problem is

Hi Alan, Since 'dups' are a frequent source of questions in my wsprdaemon group, I have included that group in this response. Your 60M 'dups' are certainly not a problem for wsprdaemon, but due to lim

Hi John, Yours is a common question, so I'm including the WD group in my response. There are some stations in the UK which transmit in two 60M channels at the same time. WD treats the 60Mand 60eu band

Geoff Fox 0fl15h1usia2tco6164 · Hi all. I'm K1GF, but writing in my capacity as science reporter for Newsy. I'd like to do a story about WSPR, the absolute opposite of broadband. I'm curious if any of

.....seeking feedback on this idea from a broad audience! In a month or so I'd like to give a talk to a group here in Arizona, a group of DX'rs who haven't used WSPR to study propagation. They have ke

Geoff Fox 0fl15h1usia2tco6164 · Hi all. I'm K1GF, but writing in my capacity as science reporter for Newsy. I'd like to do a story about WSPR, the absolute opposite of broadband. I'm curious if any of

I have recently become aware of how little many Kiwi users appreciate the importance of filtering the RF feed to a Kiwi so as to minimize RF overload events. Each Kiwi receive job run by WD logs those

Greetings, y'all I am now chasing ov events here. Have installed the Flamingo - am bandpass filter, but seemingly still have some ov events around daybreak. The culprit are likely to be traced to two

As far as I can determine wsprdaemon is running fine since I got it started a day or two ago. I have noticed that the log file is full of repeated error messages of this type: Mon Oct 18 12:30:01 UTC

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 message

One of my favorite pastimes over the past few years has been playing a WSPR "game" I have taken to calling "radio limbo", i.e how low in RF output power can I go and still be spotted. Since about 1540