The Weak Signal Propagation Reporter Network is a group of amateur radio operators using K1JT's MEPT_JT digital mode to probe radio frequency propagation conditions using very low power (QRP/QRPp) transmissions. The software is open source, and the data collected are available to the public through this site.

I am trying to receive CG3EXP, I am using WSJT-X, I can see their locator but the call sign is not decoding? just (-----) can anyone help.


Home QTH is Calgary, in western Canada, but we do spend a great deal of time during the summer in Southern Ontario - about 3000 km away

Basic setup here is Butternut HF6V vertical, and 80 m dipole fed with open wire, along with FT817 and old FT767 transceivers

Hearing virtually no DX on the air, I thought I would try WSPR with 0.5 watts from the FT-817

It took a week or so of trying to get WSPRMAP to get my location moved, but it is OK now.

I'm not even sure if I can state my question clearly enough, but here goes.

By design, the WSPR protocol has FEC which allows for a decode even though some received bits are missing.

My question is: From a time perspective, what's the minimum window of reception in order to "completely" decode the data embedded in a WSPR transmission? Or is the better question, how many bits of data (stated as a percentage of the total number of bits encoded) are required for a successful decode? I'm not seeking precision in the answer, only a ballpark idea.

Hello to all,

I'm the new electronic QSL manager for the CG3EXP WSPR expedition, and am happy to announce that the CG3EXP eQSL account is active and ready to accept your reports. CG3EXP has "AG" certification so it will also qualify for any additional eQSL awards for those requiring "AG" status eQSLs.

I'm running a QRP Labs QRSS kit on 20 meters (14.097.100). I would like to see how far it will transmit on 250mw into an end fed long wire.

This posting describes a way to gauge a 20m WSPR station’s noise floor and performance using transmissions from one of the high altitude balloons which carry WSPR around the world.

Recently by applying surface wave transmission line theory, I’ve been working to create efficient, small dipoles for the amateur LF through HF bands. Application of this theory to very small dipoles, even ones less than 1 meter tip-tip has provided very good results for amateur HF WSPR use.

From the DARC Facebook page July 5th, 2017
WSPR-Funkbake in der Antarktis

KP4MD/P is active on WSPR until July 12, 2017 from (FK68xk) Carolina, Puerto Rico, on the north shore of the island.
Radio: Elecraft KX3, 5 watts on 20, 30 and 40m.
Antenna: Buddistick monopole at 24m elevation over the Atlantic Ocean.

Possible false band reporting Problem when using Band Hopping and "Tune" Mode with latest WSJTX or JTDX.

Anyone confirm ?
73's de HB9VQQ

Going to try some low power mobile WSPR and see what happens.

2016-2017 season on 160m WSPR is now over.
Last NA/EU dx spot dates back to June28, the first one Jul04-2016. Season was amazing with a series of all-time record activity.
Three figures to remember:
- best all time session was Jan08-2017 with 435 unique NA-EU dx spot (see
- number of session with NA-EU dx spot: 317 nights (272 previous season)
- 484 stations (NA+EU) were able to listen to a station on the other side of the Atlantic (193 previous season).

Just hit the US from Rotterdam with 0.5w!

Running an experiment at least through tonight. I'm running 1 watt to a 40m Hamstick at 6 feet on a tripod, with 3 15 foot radials under it. Running WSPR2.12 and a Softrock SDR using HDSDR.

WSJTX 1.7 installation appears to work fine on RPi2B with Ubuntu 16.04, a bit slow on JT65 decodes, but to be expected, I used image with ssh installed so could avoid using connected monitor and keyboard. Then installed VNC and gnome so can use remote GUI for access. Only problem so far is incorrect keyboard mapping when trying to fill in callsign and locator text boxes. Got round it by cutting and pasting from terminal window. This would be a big problem for a chatty protocol like psk31, but not for the minimal text jt protocols.