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.

According to web cluster, 6m condition seems good.
Now, beaming to North America.


Tonight, I upgraded the core content management system used by WSPRnet. Not everything is back to where it was, but I'm done for the night. I will clean up some of the formatting and presentation tomorrow. Thanks for your patience!

we are in Spain allow to TX in 4m. band from 70,150 Mhz to 70,200 Mhz. So I set my 4m. WSPR in 70,153 (RX). I am Beaming from Madrid to Central Europe and UK. 73, EA4ETR Juan Carlos.

Ok. I swapped out the RK20 kit receiver for my beloved IC703 receiver.

With just a few hours of use its clear its maybe up to 13db more sensitive on the same stations I'd been receiving on the kit receiver for a few days now.

No big surprise in that. Interesting to see the differences in signal strength.

What is unclear is why I'm just hearing the one station. I would have thought that even with the in-office-dipole it would hear a few more distant stations with the better receiver in the IC703. It would seem not to be the case.

For the last few days nearly all I've heard are local stations with a few ZL spots.
Clearly my antenna and Rx combination is sub sub sub-optimal.
Next test is to swap out the Rx for a full commercial Rx and compare.

I spent the last few days experimenting with modifications to WSPR to enable it to transmit at variable power levels. I had the idea when I was playing around with the Tx output level from my SignaLink box. I realized that I could reduce the power output of my WSPR signal from my transceiver by varying the audio drive levels. I guess that's obvious. However, I also realized that I could achieve the same thing if I could vary the amplitude of the generated wave file in the WSPR application.

After a few experiments I discovered that I could modify the fortran code to reduce the wave file amplitudes and achieve a corresponding reduction in output power. One thing I found out in the process was that once the audio levels dropped below a certain point, the VOX capability on the SignaLink failed to trigger the PTT. There is a jumper (JMP4) inside the SignaLink that increases the sensitivity. With that in place I was able to vary the power level down -13dB from the maximum. I could probably achieve a lower drive level if I used CAT control to enable the PTT.

So far I have a version of WSPR compiled on Ubuntu 14.04 that sequences my WSPR transmissions through 20, 17, 13, 10 and 7 dBm. I haven't modified the GUI yet - so any changes have to be compiled into the code.

The key to getting it to work is to measure the power output very accurately (I use an oscilloscope to read voltage) and adjust the SignaLink drive Tx level to give the correct output at the highest power level in the sequence. The modified WSPR software then varies the power over the ranges I have programmed in. It's important to make sure the drive level is below the ALC of the transceiver to ensure that it is accurate. In my case I am using an FT-817 at 500mW nominal output, with the SignaLink driving it to produce 100mw (20dBm) at the maximum power level.

See attached picture.

Recently I changed the stage after
the DDS module into a single 2n2222.

Rx built in an hour. Aligned. Antenna is hookup wire 2 m high run around the office. No gound wire, just DC power cable to the PC. Not tuned. Complete rubbish as an antenna! If I can receive you, you've got a great signal!
Things will only get better.
Goal is to leave it running (with a much better antenna of course).
Not being a transceiver, means it can happily stay working 24/7.

I will be pointing to North America on 6m WSPR.
Schedule is from 20:00z to 24:00z on 27th and 28th of June.
Please give it a try.


Les invito a visitar el sitio

5 to 7 april 2014 - 14 & 21 MHz - Test period with 5 mW (good results),
1 mW (significantly less reports) and 200 µW (no report during a 2 hour test only).
Mostly embedded into RTTY activity. To be continued during quiet periods.

Using vector voltmeter HP8405A for power calibration and a vertical antenna.

Thanks to all WSPRnet contributors and operators from Marc F6EMT

New two and fifteen min modes, transmitting! Tone out of computer erratically interrupted randomly. Any clues?
Thanks. G0OKX Kim.

Occasionally, I like to head out in the truck and run JT65, or even let WSPR run a while from some remote or hilltop location.

The laptop I use for mobile op happens to have a pretty crummy clock – it can easily loose several seconds per day. (Of course this is not a problem when at home and connected to the net – I use Dimension4 to keep clock synch.) I imagine that the internal clock in many laptops suffers from this same problem – and as you know this makes any type of timed operation difficult or impossible when mobile.

To address this issue, I made a little windoze app that synchronizes the laptop clock to “0” seconds when a button is clicked. - See attached image...

One button syncs to the current second - I use it for JT65 operation – listen for when everyone else starts TXing, click the “Zero to CURRENT Minute” button, and next time around JT65 will be close enough to decode and be decoded.

The other button syncs to an even second – I use it for WSPR operation - listen for when everyone else starts TXing, click the “Zero to EVEN Minute” button, and next time around WSPR will be close enough to decode and be decoded.

Both functions work quite well, but as you can imagine, it’s not hard to be “off” by an integer minute or a few integer minutes. This doesn’t really matter for JT65. But for WSPR, this will put good decodes, but possibly with the wrong minute value, into the WSPR database. In fact, the decodes shown in the attached screenshot are in the WSPR database, but are 2 minutes off – bad me!

I am thinking of releasing the app for download. Mobile JT65 and WSPR is fun. I have no problem releasing the JT65 version – being off a minute or 2 is not an issue. But, if I do release this little app with the WSPR “Zero to EVEN Minute” button, then eventually bad times are going to end up in the data base. Probably not many, but it will happen.

I've been playing with WSPR for about 4 years now.

I've kinda taken it for granted really, and I admit I don't even know who runs it or the work involved.

I suppose because it works so well I have taken it for granted.

But it's time to say thanks to all involved - thanks for being here, and provide one of amateur radio's most
unique slant on the hobby (in my opinion).

(I say one, because my hat goes off to the QRSS grabber chaps who provide another unique slant in the world of QRPp).

72/3 de Andy G0FTD

Been talking about this WSPR for a long time and finally managed to configure it,,,
So easy to use and fantastic distances with such low power...