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.

Do you enjoy making very precise measurements? Have you always wanted to enter the ARRL Frequency Measurement Test (FMT), but held back because you assumed that expensive laboratory equipment must be required?

Appendix C of the WSPR 2.0 User's Guide, ,
explains how to calibrate your WSPR transceiver to an accuracy better than one Hertz using over-the-air standard-frequency signals. Many WSPR users have used this procedure to establish calibration constants for their own radios, resulting in significantly improved frequency accuracies of reported WSPR spots.

About six months ago, I wrote some simple software tools that largely automate the procedure described in Appendix C and extend it to enable measuring the frequencies of unknown test signals. I used it for the ARRL FMT held last April, and my resulting measurements of all seven FMT test signals were within less than 0.3 Hz of the published "true" frequencies. (See for results of the April 2010 FMT.) My equipment was very simple: nothing more than my normal WSPR setup, a Kenwood TS-2000 with the software mentioned above. Any CAT-controllable radio would do. I've even tested it with my SoftRock, with excellent results.

The next ARRL Frequency Measuring Test is less than three weeks away: November 11, 2010, starting at 0230 UTC (the evening of Nov 10 in US time zones). Details are in November QST and on the ARRL web site at .

If there is significant interest from others who would like to try entering the November 2010 FMT, I'd be happy to write some brief instructions on using the new frequency-measuring software tools, and make them available for free download. It will probably be simplest to just include everything in a packaged release of WSPR 2.1. If you are interested, please let me know (k1jt at arrl dot net).

"Discovered" WSPR in the Nov QST...installed the software and am amazed at the signals being heard mid-day on 30M. Great fun and looking forward to learning more!

I have placed the WSPR mode on the backburner for almost a year. FInally, I have been able to get confirmations of being heard and also hearing stations on the bands. Am using a Kenwood TS-450S and a homebrewed dipole.

I moved back to 20 meters running .17 watts as best as I can measure

Yaesu FT-817 running 2W into a ZeroFive 50ft vertical which is fence-mounted with a few additional buried radials. Had RX working last two nights. Tonight I dusted off my old RigBlaster, reconfigured it for the FT-817, and bingo! Spotted by a VK7 on 40m in the first few hours of operation.

trying 6 meters for a while, beam now at 300 deg running 3.5 watts

I made the splash last night to try out WSPR for the first time. I had been fighting with the website to actually get a working password in addition to proxy problems related to internet explorer that kept me from communicating with the server. Who knew that Internet explorer's proxy settings were different from the Firefox proxy settings... I didn't (for those of you that are as slow as I am, I use Firefox and hadn't opened IE ever on this machine).

Being a low band guy, I started out on 160. I was heard by a few stations in CA and in between but activity was generally kinda slow. I already knew that aurora activity was going to make any real worthwhile test a bit of an impossibility. Furthermore I am going to have to figure out how best to deal with automating my RX antenna selection process or at least come up with a protocol, perhaps listening to EU through their sunrise and then switching around to JA or VK/ZL. Fortunately the F/S is poor enough that I can probably avoid missing signals to the NW of me.

I switched down to 80m and there were plenty of signals so I fired up around 40 dbm and was heard by a number of station in the northeast in addition to G0 and EA4. Even with all the noise from listening vertical, I was hearing most of those reporting me, including the Europeans. I was excited to find that VK4 had been hearing me on his sunrise, about 3800 miles from my antipode.

I am currently sourcing parts to modify my RX antenna switching logic as well as changing how I de-tune my TX antenna on receive to avoid noise coupling into the RX antennas and hope to have all of that working in a couple of days. Until this is worked out, I apologize if I don't hear some of you. I am spoiled by the RX antennas and live in a noisy location just south of Dallas, Texas so some things just cannot be helped.

I hope to be back on the air tonight about an hour before Sunset on 80m and look forward to running this evening!
73 es DX,



Running WSPR 2.0_r1714 on Windows XP Pro SP3 and a Ten-Tec Omni VII (588).

Since the O7 has an octopus breakout cable which brings audio line in and out to phono plugs, all I had to do was hook up to my PC's sound card line in and out connections and I was ready to go.

Although the WSPR application doesn't have a rig selection for the O7, the Jupiter config worked fine for changing frequencies, and VOX works for transmit control.

I notice that when WSPR is first fired up, the rig is NOT automatically set to the frequency for the selected band. Changing to some other band and then back to the desired band will then select the correct frequency.

I spent a while trying to get XMIT levels working right. At first, I simply cranked the XMIT power all the way down to 5 watts, but had a hard time adjusting the rig's line level input and the PC's line level output to a point just below ALC activation. I finally found that running the rig at full power (100 watts), but with a lower audio level gave me a less touchy range of settings that allowed me to get 5 watts out as indicated by the rig's own internal watt meter (assuming that it's correct). Another advantage to setting the rig's power this way is that the internal antenna tuner still works; when the transmit power is set below about 15 watts, the tuner won't activate when the TUNE button is pushed.

I spent a few hours playing with the program for the first afternoon, and was pleasantly surprised by how many people I was hearing and how many people were hearing me.

The big surprise was that I appear to be something of an alligator on 40m and 30m, where I'm heard by lots more people than I can hear myself. This runs counter to my real-world experience of not being able to work the folks I hear, especially on 30m.

I really expected better results when I left WSPR running in receive-only mode overnight on 40m. Reports from only two European and one Australian, with the rest confined to North America.

hello and hope to sqo with you soon.more to come.k2csx mark.

I just wanted to welcome all the new users of WSPR and this site. We have had a flood of new users as a result of the publication of the WSPR article in QST, and I hope the site holds up under the new load. There are about 7500 active users of this site (meaning someone has registered, been activated, and subsequently logged in). About 600 of those have come since the publication of the QST article a week or two ago. As you can see from the Stats page, we are now seeing about 500 active call signs using WSPR on the bands each day. There are two main purposes of this site:

Transmission locks on ignoring the TX time interval setting. When I use the tune control the TX stops at the set time interval. Signal is transmitted as I have confirmations from the database. I am using a TS-2000 with a Rigblaster Plus interface. Thanks for any advice.

Finally got the Yeasy 817 running, had to run the audio straight into the mic connector, running 1 watt into a tribander.