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.

Ik heb onlangs wspr op de pc gezet
en ik werk met een YAESU FT-817
ik heb al eens een beetje kunnen ontvanger;
maar ik krijg het programma niet inzending via de cat aansluiting
via vox lukt het wel maar dan kan ik maar 1 maal inzending gaan;
en dan blijft mijn zender in ontvangst slaan.

Wie weet er een oplossing?

Jan 15th, my first day operating WSPR. I am in the northern woods and lake country of Minnesota, about 160miles north of Minneapolis. At this time I am running at .1watt (100mw) on 20m or 40m depending upon the time of day. Very curious to see paths at this power level. The rig is a Elecraft K3/10 and the antennas are an inverted Vee on 20m, the center at about 40ft and on 40m a dipole IN THE TREES about 15ft off the ground.

Schedules would be welcome on 40m / 20m as well as VHF ... it would be interesting to check frequency stability on the higher frequencies.

After about a month of tries, finally I get something in 600m.
See attachment: PA0A and SM6BHZ, for now :-)


Perseus + Wellbrook ALA 1530

I got the Softrock Lite II rx working on 40m using PowerSDR-sr40 v1.9.0, Virtual Audio Cable 4, WSPR2 and
half g5rv facing SW, on a Windows XP laptop. It's a bit deaf compared to the IC-706 but more fun :)
Thanks to all for excellent software, great sdr guides and help on the Net.

I saw the strangest thing when I went through the my WSPR log and the WSPR database this morning. Last night (12 Jan 10) at 1012Z (0212 local PST) I copied a garbled WSPR signal "UM2XUJ" on 503.814 kHz in gridsquare JO23 with 20 dBm of power. BTW I know my receiver usually reports about 30 - 50 Hz or so low. I initially thought this might have been some corruption of WD2XSH/12 or /10's signal but neither were transmitting in this time window.

I pulled the WSPR spot logs from the database and only found one station that was detected by others at the same time was LA3EQ on 503.916 kHz (as reported by a GM4 station). In that GM4 report LA3EQ had a gridsquare of JO28wj and a power of 20 dBm. Obviously the callsign and gridsquare are not the same but the major letter portion of the gridsquare is right and so is the power level. If this is was in fact was LA3EQ then this would be my first over the pole 600 meter DX.

BTW later I checked LA3EQ's website and Jan's gridsquare is JO28xj. It's interesting to note that X and J are included in the garbled callsign (same as the minor portion of his gridsquare).

Already a long time the beacon of Gernot, OE1IFM is running here with 0.5 Watt.
The used bands are 80 , 40 , 30 , 20 , 17 , 15 , 12 and 10 meter.
The last weeks it was on a trap-dipole for 40 and 80 meter.
Sinds yesterday (11-1-2010) I switch to trap-dipole for 30 , 17 and 12 meter.
So now I get less reports on 40 and 80 and more on 30 17 and 12 meter.

Thanks to Krzysztof Dabrowski, OE1KDA, a Polish translation of the WSPR 2.0 User's Guide is now available. A link has been placed on the WSJT/WSPR web site:

Translations of the WSPR 2.0 User's Guide are now available in French, Brazilian Portuguese, Polish, and Russian. Translations into other languages will be welcomed; if you are interested in doing this and would like a copy of the original MS Word file in English, please let me know.

Yesterday I went on site to see why my WSPR RX was stopped. Discovered freezed PC with "Not enough disk space" message. WSPR v1.2 occupied all disk space - 72 GB per one moth and a half period. Now we on-line again. 73! Gintaras, LY1GP.

Attached, a visual approach in XLS form of the freq correction as outlined by Joe K1JT.


I finally gave in, and loaded Windows XP onto my EEE PC so I could use it with WSPR. I made many attempts to get the Linux binaries working, but ran into so many dependency issues and compiler errors that I simply could not spare any more time on this. I like Linux, but it truly is an OS that has yet to mature, particularly driver-wise, and is not worth my time away from the XYL and 4 children.

I just started with the WSPR technique. My computer input was connected with the output of my FT- 450 Yaesu transceiver, using an audio cable. I did´t have the microphone socket for the transceiver, for that reason I simply connected the output of the computer to my station loudspeaker and brought it near to the microphone. After turning on the Vox, the set up worked perfectly and surprisingly I got down to a reception SNR of 28 db at a distance of 8821 km. Not more than 20 min work! The antenna was a magnetic loop on my balcony. I find the new technique very fascinating.

I'm new at a QTH and am RX only due to lack of HF antennas - I've tried internal antennas but local QRN flattens most WSPR frequencies.

I've connected my FT897 to my colinear for VHF/UHF for RX. I've just begun rxing stations.

A few mins ago on 30m (9th Jan 2010/15 my system incorrectly decoded EB1EHO as 4T/EB1EHO - it's corrected on the next decode.

Dave G0CER

I didn't expect much but the EH Antenna in the loft which is propped up at a 45 º Angle in a due east direction did make some European Contacts but appeared to display directivity. Going to play with this some more !

I'd like to try a WSPR QSO with VK6 around your local sunrise - maybe tonight (our time) early morning your time? I will be CQing on 3575.45 tonight starting at 20:50z until 21:50z. I know it can be done on CW.

So what happened on 3575.45 tonight between 2050z and 2150z?

  1. SP3IY calling me at 2108z SN=0dB, but did not send a report.
  2. RA3ALW CQing at 2120z, 2124z from KO85, SN=-5dB, slight QSB.
  3. OE1LIC calling at 2148z, SN=-7dB. Stopped after first minute TX, QSO not complete.

So much for tonight.

trying to make some QSO's
calling CQ in WSPR mode on 3575,45