WSPR Notes
2023 Note the Princeton web site is no longer hosting WSJT. All pages will be found here https://wsjt.sourceforge.io/wsjtx.html
Minimum WSPR Power.
I see remarks on WSPRnet Chat or Forum that users claim their rig power will not go below 5 watts.
With all transmitters when using SSB the RF power out is a reflection of the level of audio that is applied to the input, the microphone or data port.
The power control of a radio when on SSB/Data modes limits the maximum power, not the minimum. All it does is apply ALC if the audio input exceeds a certain level. It is often advisable NOT to drive a transmitter into ALC with digital modes. [Note some users of the K3 say ALC works differently on this rig. In fact the first 4 LEDs show audio level, ALC does not start until 5 are lit.]
Many say they cannot measure power below 5 watts so do not try. There is a method where low powers may be set with fair accuracy.
July 2020 Latest Windows 10 Initial Sound Settings for TX:- Look here The essential is not to not exceed 0dB.
Reduce Audio Level.
There are several ways to reduce the input to a transmitter.
April 2020 Windows 10 keeps changing the way sound controls are accessed. The "traditional" panel is available by searching for "Control Panel" then selecting "Sound". Another way is to right click the speaker icon on the Taskbar and select "Open Sound Settings" then select "Sound Control Panel". All devices and settings are available here.
Click "Playback devices". Select your soundcard, click "Properties", go to the "Levels" tab. Here the "Speaker" slider controls the audio to your transmitter.
If you see another like this the "Line-in/Mic-In" must be muted. Click the speaker icon on that tab.
Right clicking on the slider on the "Level" tab enables you to choose dB readings. BUT I have found these dB scales may be very inaccurate, actually useless! Hopefully the 0dB level will mean no extra gain to overdrive the ADC. Also on a combined input "0dB" is the level that turns a microphone/line input from one to the other.
While you have this open make sure all special effects are disabled. On this soundcard the "Sound Blaster" tab has a box that needs to be ticked to disable them. Explore these tabs, maybe other buttons lead to other effects that need to be disabled. Enhancements may sound good through speakers but will not help WSPR!
WSPR itself has a digital output control. Shown version 1.6.0 Hover your mouse cursor over the "Pwr" slider and the level is shown in dBs. Use your mouse wheel for easy adjustment. Earlier versions had the control at "Setup - Advanced"
"Transmit digital gain" may be reduced by up to 45dB. The mouse wheel will move the slider one step.. It is possible to get exact dB values with steps of -0.1dB.
To set audio levels so the slider will set the power.
If, for example you do not feel your power meter will read accurately below 5 watts then set your power control to about 10 watts. Then adjust either or both of the sliders shown above so that 5 watts is indicated. Now your power is controlled by the audio and power sliders. You may have to reduce levels significantly. Note the dB readings on these sliders.
You now have the ability to reduce power by a known number of dB by using the WSPR Pwr control.
The box that shows the power value transmitted by your WSPR signal also shows dBm. 37dBm is the same as 5 watts.
So if you make the dB figure 7dB more negative on this or the audio control slider then you will be transmitting 7dBm less, 30dBm, 1 watt.
Then maybe reduce by a further 10dB. 37dBm -17dB is 20dBm, 100mW.
If your first step of setting 5 watts output is accurate then these powers will also be accurate.
Many SWR meters may be used to show lower powers more accurately. A meter that has a scale on it's reflected power display may be carefully used connected in reverse.
The reflected power meter will then read forward power.
Be careful, make sure your power control is at minimum and that you do not allow high power to be transmitted while you are testing.
Microphone Inputs.
Feeding audio from a computer into a microphone input is not ideal. A soundcard output is far too high to feed a microphone input directly. If the radio has a data input then use that.
To use a microphone input an attenuator will be required, just reducing the microphone gain is unlikely to be sufficient, If you manage to reduce the output power enough there may still be distortion and noise on your transmitted signal.
A suggested circuit, maybe one potentiometer may be enough but two give finer control. Almost any may be used, preset trimmers are small and convenient.
Using a 100 watt transceiver like this is not ideal, think about using a low power rig or maybe a home made transmitter, A Softrock or QRP Labs "U3S" is good. Others perhaps a little more complex are available maybe using the Raspberry Pi or Red Pitaya.
Another way to help reduce power is by using an attenuator in the antenna feed.
A 10dB attenuator will not affect reception, just about any commercial radio is sensitive enough. Note this attenuator must be built to be able to comfortably deal with at least 5 watts input.
A 100 watt transmitter will have a relatively high amount of broadband noise present on the output. An attenuator will have the effect of reducing the amount sent to the antenna.
Commercial attenuators are available. This page has an Excel calculator for building yourself. https://a29.veron.nl/hams/pa1b/pa1b-power-attenuator-calculator/
Windows 10 Audio Settings, problems
In August 2020 I decided to finally update from my XP SDR computer. This had the equivalent of about 10 stereo audio systems including a M-Audio 1010 and 2 Delta 44s. I wanted something that would replace that and run the latest wideband SDRs so purchased a Dell XPS 8930 with a Core I7-9700 @3GHz and Nvidia GeForce RTX 2060. I could not find suitable internal sound devices so had to accept that USB devices would have to be used.
To keep my Softrock RXTXs working I had to use multiple instances of HDSDR and virtual audio cables. I also use other receivers usually running 5 instances of WSJT-X. It was necessary to make sure that none of the sound devices on the computer was turned off by Windows for any reason. This includes HDMI audio which is stopped if the screen saver is allowed to operate. Permanently disabling HDMI or other audio devices in "Sound Properties" is a way of avoiding this. All USB power saving has to be turned off.
Fundamentally this worked well but not for long.
I was plagued by sound device disconnections, sometimes when plugging other USB devices, sometimes for no aparrent reason. I did not overcome this until I eventually fitted a PCIe USB3 card and used that for my sound devices. The on-board USB3 was not coping with my reqirements.
(SupaGeek PCI-E to Type C (1), Type A (4) USB 3.0 5-Port PCI Express Expansion Card, Capable of Expanding + 2 USB 3.0 Ports with Internal 19-Pin Connector)
The way HDSDR v2.80 selects sound devices made the sound device disconnection more frustrating. When a device is disconnected Windows re-orders the devices and HDSDR loses connection and has to be reconfigured. It is often best to close HDSDR and the WSJT-X instances and restart. I have not found any other soundcard RXTX program for Windows 10 that will run multiple Softrocks. Spectrum Laboratory and WSJT-X must use a different system because they do not require reconfiguration.
The 10 October 2020 Windows 10 update caused a problem with my on-board Realtek. The speaker output at the back of the PC stopped working. The facility to select the output had gone. The front socket did work but was very inconvenient as it is difficult to stop the cable obstructing the DVD drive. I rolled back but eventually had to take the update with the same result.
I tried Windows update, Dell and Realtek, found no compatible driver, tried a few and ended up with no output.
Looking again today I found certified drivers for Windows 10 October 2020 Update (20H2) release date 17 Mar 2021.
After 5 months the on-board sound now works properly again.
Something similar may possibly happen to others.
This computer was sold new about a year ago and I have troubles with the built-in sound. On the other hand I find that the old USB Sound Blaster Live! SB0490 24 bit 96000Hz is supported as are other Creative "end of life" devices. Other devices I use are the USB Sound Blaster X-Fi the 4 channel (2 stereo pairs) Maya 44 USB
Almost any USB sound device will work, the generic drivers will enable 16 bit 48KHz.
Sometimes at startup or restart one of the USB sound devices does not initialise properly and has to be unplugged to reset it.
Here, notes about USB sound problems http://g4jnt.com/ProblemsWithUSBSoundcards.pdf
If you use a SDR
at the bottom of this page https://sites.google.com/site/g4zfqradio/hdsdr_wsjt-x I describe a way to control and display your WSJT-X power output in HDSDR.
60 metre WSPR Frequencies
April 2017 60m WSPR Frequencies.
There are two main Dial Frequencies in use, the original 5.287200MHz and the new 5.364700MHz.
5.364700MHz is within the recently agreed IARU segment and is used for transmitting by most European countries that have an allocation. It seems likely to eventually become available to many other countries.
5.287200MHz is used for transmit by countries that have not yet been allocated the new IARU frequencies, South Africa is the most commonly active on this frequency. (Sometimes you see other countries transmitting but often it is not actually legal for them.)
Although the UK has not yet been allocated the IARU frequencies 5.364700MHz does fall within one of our band segments. Some use the old frequency, some the new and some both.
When the IARU band was first released quite a few Europeans started using Dial 5.364700.
At that time there was a lot of discussions led by Dutch stations and it was agreed to try to make 5.364700 the default worldwide frequency. (At that time there were several threads http://dev.wsprnet.org/drupal/comment/15786 is one.)
July 2021:-
5.355700 Dial is being used by VE8TEA (DP22) and other VEs, maybe some US. This is TX frequency ~5.357200 is the centre of one of their channels. It also falls inside the IARU segment and is in a UK segment.
WSJT-X v1.8.0 onwards has no default 60m frequency. An attempt to stop unauthorised transmissions. Note "Change WSPR Frequencies" below.
Outside Europe only South Africa has regular legal transmissions on 5.287200. But in time the IARU band could be adopted by more countries worldwide. I suggest 5.364700 is promoted as default for those who have that allocation.
December 2017. 80m WSPR The default frequency in WSJT-X v1.8.0 and onwards is now Dial 3.568600 (TX 3.5600-3.5800) to be within the Japanese allocation. The only official announcement http://wsprnet.org/drupal/node/7144 Now updated on WSPRnet.
Check 20m WSPR Frequencies.
September 2021:- Hans, G0UPL has a routine that does some "averaging" of reported spots to give a close estimate of a station's RX and/or TX frequency. Just 20m now, hopefully to be extended.
https://groups.io/g/QRPLabs/message/71438
20m. (Link may be changed sometime) https://qrp-labs.com/images/wsprnet/rxerror.html
And for transmitting stations https://qrp-labs.com/images/wsprnet/txfreq.html
Change WSPR Frequencies
To change/add frequencies in WSPR.
WSJT-X:- File - Settings (F2) Frequencies Tab:- Right click in the frequency list window - Insert. Select WSPR in the drop-down, type the frequency in MHz 5.364700 for example. - OK. (Do not select "Delete" unless you want the frequency you have selected to be deleted. If you do by mistake click "Cancel".
Both frequencies could be used simultaneously by using two WSPR profiles and two rigs/antennas.
Shown in the Manual:- Setting frequencies in WSJT-X V2.1.2 https://wsjt.sourceforge.io/wsjtx.html
Earlier versions of WSPR:- Type in the Dial Frequency in that box. Double click on the waterfall to set the TX frequency. This will be saved when you close WSPR. You may save two frequencies by using "Other" in the "Band" drop-down menu.
Your U3/S is likely to transmit 2Hz higher than set https://groups.io/g/QRPLabs/message/21931
===========================================
Playing with Fiq, BFO and Dial frequencies in older WSPR versions.
OLD (more than 10 years!) Change BFO so audio frequencies other than 1400-1600Hz may be used:- For RX only, with limitations.
WSPR 2.11_r2247 in non-IQ mode:- 600-800Hz audio.
Setup - Advanced BFO 700
Dial standard -800Hz
Then RX frequency listed in it's RX window is correct, and that saved in ALL_WSPR.TXT. But the waterfall scale is not. It does not upload spots.
This does not seem to work for TX, the TX frequency display is 1500Hz above the modified dial frequency. (Not tested this time.)
Change BFO in IQ mode.
WSPR 2.11_r2263 in IQ mode.
Setup - Advanced BFO 700.
Setup - IQ mode Fiq 12800 (Or reset LO frequency.)
Dial standard -800Hz
Then RX frequency listed is correct. But the waterfall scale is not. It does not upload spots.
This does not seem to work for TX, the TX frequency display is 1500Hz above the modified dial frequency. (Not tested)
So WSPR used this way will need manual uploads (or possibly an alternative script) and will give abnormally high SNR reports when used with narrow filters.
These older versions of WSPR do not run on my Windows 10 device. They did but stopped working after some update. The current WSJT-X includes WSPR but only for an ordinary mono 1400-1600Hz audio input, the BFO setting is not available.
https://sites.google.com/site/g4zfqradio/using_the_fcd this page shows Fiq adjustments.
WSPR, a note regarding use with non-standard Dial Frequencies. For the non IQ mode.
Stewart ZS6SGM uses a commercial transceiver with only 500Hz steps. We discovered that WSPR may be configured to use non-standard Dial Frequencies.
For 60m the closest transceiver frequency to the standard Dial frequency of 5.2872MHz is 5.2870MHz.
Set WSPR "Dial" to the actual frequency. 5.2870.
Set "TX" to the actual frequency you require (5.2886-5.2888MHz) WSPR will actually transmit on this frequency.
The dial is 200Hz lower than standard. Set RX BFO in WSPR to 1700Hz. WSPR will then report the correct frequency of stations spotted. The scale in WSPR will be incorrect showing 200Hz lower but this is a visual defect. Another problem is that you will report your dial frequency to the "Activity" page if nobody is spotting your signal.
And WSPR will not upload spots. Use the Old Database page. Or this may be done with a batch file. Look here http://wsprnet.org/automate.txt The main line requires changing, my example:-
"C:\MoreProgramFiles\WSPR\curl.exe" -F allmept=@"C:\MoreProgramFiles\WSPR\ALL_WSPR.TXT" -F call=G4ZFQ -F grid=IO90IR http://wsprnet.org/meptspots.php This could be executed manually or with a utility, I use Pycron but probably Task Scheduler could be used.
A way to shift audio frequency digitally using Spectrum Laboratory. See here http://wsprnet.org/drupal/sites/wsprnet.org/files/WSPR_BFO_800Hz.jpg Changes 800Hz, or other frequency, to suit the 1400-1500Hz requirement of WSPR. Note narrow filters are best not used with WSPR, misleading SNR figures are produced.
========================================
Anyone using the QRP Labs U3S and concerned with frequency precision should note that up to and including the current firmware v3.12a the WSPR frequency indicated on the U3S is the lower of the four tones. WSPR software reports the centre frequency which is 2.19Hz higher.
To Start Different Instances (Profiles.)
Each instance may be setup completely differently. Or, as for 30m the same RX may be used for WSPR and JT9 monitoring. Set 2 instances, one for WSPR, one JT9 both with the same soundcard.
Each will have a different folder in \Users\...\AppData\Local\WSJT.... containing the ALL_WSPR.TXT or other data for that instance.
Probably the easiest way is to copy the shortcut on the Desktop. (Hold "Ctrl" drag shortcut to free area.) Rename it to match rig or, as I have usage. Then edit "Properties" (Right click.)
My one here renamed WSPR2, --rig-name=WSPR2 added after wsjtx.exe. - Apply
Also WSJT-X may be started in "Dark Mode" by adding "–stylesheet :/qdarkstyle/style.qss " to this line.
Profile shown in WSJT-X Title Bar (--rig-name=FT840)
You may also go to the \bin location shown below then create and rename a Shortcut.
[Also note "Shortcut key" in Properties above. Enter a keyboard character in that box and in the above example Ctrl-Alt-5 (or Alt_Gr-5) will open WSPR2]
Method shown in WSJT-X Help. Main Page [was http://physics.princeton.edu/pulsar/K1JT/wsjtx.html] https://wsjt.sourceforge.io/wsjtx.html For help see https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.6.1.html [was http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-1.7.0.html] Section 14 and 15. Presumably the main WSJT-X page will link to any later versions. Note when installed the user guide is available on disc see "Help" - "Local User Guide".
Open a new text file in the WSJT bin folder found here on my setup C:\WSJT\wsjtx\bin wsjtx.exe will be here. Write the command, like this wsjtx --rig-name=WSPR Save, Rename to a batch file for example WSPR.bat Then make a shortcut to it, (right click). Rename shortcut to match rig or as I have, usage.
Make as many differently named ones as you need.
I guess if when installing WSJT-X you had ticked the box "Include WSJT in the Path" then the .bat file could be on the Desktop or somewhere else, Windows would know where to go.
(Or if you put the full path in the .bat file, for example "C:\WSJT\wsjtx\bin\wsjtx.exe --rig-name=WSPR")
WSPR, Upload Batch File
November 2020:- Note in late versi9ns of WSJT-X ALL_WSPR_>TXT needs to be modified to enable upload. Hopefully this is just temporary. See the second post here http://wsprnet.org/drupal/node/8507
Windows 10:- The batch file below will probably not work, due to Windows file system "pushd" may help. Something like "pushd "\\DELL\Users\dell\AppData\Local\WSJT-X - igname=AOR" but not tried yet.
:A
CLS
@ECHO ON
"D:\MoreProgramFiles\WSPR-Folder\curl.exe" -F allmept=@"D:\MoreProgramFiles\WSPR3-Folder\ALL_WSPR.TXT" -F call=G4ZFQ -F grid=IO90IR http://wsprnet.org/meptspots.php
@ECHO OFF
ECHO %TIME%
ping -n 200 127.0.0.1 >nul
goto A
rem For this to work get curl.exe from http://curl.haxx.se/dlwiz/?type=bin put it in your WSPR working folder.
rem Modify the 4th line above by editing the paths (in "inverted commas") so it is your WSPR folder. And change to your call and locator.
Rem Then double clicking this .bat file should upload your ALL_WSPR.TXT
rem You could place this bat file in a convenient place or make a shortcut to it.
rem You could place curl.exe in it's own folder, then the start of line 4 would be different, perhaps "C:\Curl\curl.exe"
rem This bat is just my updated version of the one on the WSPRnet site.
"DT" value, WSPR Timing
DT is displayed in the WSPR receive window. This gives some measure of the timing between your setup and the transmitted signal. You will be using a method of keeping your computer on time, something like rsntp (You must right click the shortcut and "Run as Administrator". Preferably disable Windows time, "Control Panel" - "Date and Time". rsNTP allows you to offset timing for testing).
Often recommended is the "Rolls Royce" Meinberg NTP service. A description for Windows here http://www.satsignal.eu/ntp/setup.html main site:- https://www.meinbergglobal.com/english/sw/ntp.htm
As an example a positive DT value means that your computer has measured that the start of a transmission was late. The DT value is not necessarily precise, several instances of WSPR on the same computer can give different DT values to the same signal. Note WSJT WSPR will still decode a signal about 4 seconds off.
I usually see a maximum DT value of around +/-1 second. If a few stations show higher then it is likely their timing is wrong. If ALL stations show a high value (all + or all -) then suspect your timing.
If you are unsure about your timing utility then sites like https://time.is/ will normally give an accurate check. A user in Turkey reported a 2 second difference from GPS timing.
Adding links to WSPR "Chat"
2023, take care, I think this has changed!
A web address is not normally converted to a link but HTML may be copied into the Chat window.
<A HREF="https://sites.google.com/site/g4zfqradio/setting_wspr_power" TARGET="_blank">The link</A> Inserted in WSPRnet gives me live, "The Link" [From Myles' instructions.] [ TARGET="_blank"> opens page in a new window.]
<FONT COLOR="red">Test</FONT>
Inserted in WSPRnet gives "Test" It is best not to use red, this is used on the Chat page when the user's callsign or name appears. Other colours aqua, black, blue, fuchsia, gray, green, lime, maroon, navy, olive, purple, red, silver, teal, white, and yellow.
<FONT COLOR="purple">Use WSPR incorporated in WSJT-X here </FONT><A HREF="https://wsjt.sourceforge.io/wsjtx.html" TARGET="_blank">https://wsjt.sourceforge.io/wsjtx.html</A> (https://wsjt.sourceforge.io/wsjtx.html)
Shows a live link Use WSPR incorporated in WSJT-X here. Opens in new page, tab.
The latest WSPR is incorporated here <A HREF="https://wsjt.sourceforge.io/wsjtx.html" (https://wsjt.sourceforge.io/wsjtx.html) TARGET="_blank">https://wsjt.sourceforge.io/wsjtx.html</A>
Shows the text above and a live web address.
Use WSPR incorporated in WSJT-X here <A HREF="https://wsjt.sourceforge.io/wsjtx.html" TARGET="_blank">https://wsjt.sourceforge.io/wsjtx.html</A> (https://wsjt.sourceforge.io/wsjtx.html)
An image Keep it very small! I do not know if there is a limit but filling the Chat page will not make you popular.
<FONT COLOR="Blue">TEXT<img src="WEBSITE/IMAGE.jpg">
64x64 pixels, JPG 1224 bytes. 1.1x1.1cm @150dpi.
---------------------------------------------
Latest WSPR in WSJT-X:-
March 2018 now 2023, these versions and pages seem to have gone from the web.
Note WSPR 2 is old. For a long time WSPR has been part of the WSJT-X suite
Primary WSPR page, but do not use WSPR v 2.0 or 2.12 unless you know you need to. [was http://physics.princeton.edu/pulsar/K1JT/wspr.html] https://wsjt.sourceforge.io/wsjtx.html it is 8 years old. Note on this page "New" WSPR-X is 5 years old! But the guide shows the beginning of WSJT-X, read all on this page to get to understand how WSPR works.
Latest WSPR in WSJT-X here [was http://physics.princeton.edu/pulsar/K1JT/wsjtx.html] https://wsjt.sourceforge.io/wsjtx.html and it's documentation, look at all of this large page.
Older versions of WSJT-X https://sourceforge.net/projects/wsjt/files/
September 2018 WSJT-X v2 is now available, another improvement to the WSPR decoder, changes to FT8 and MSK144 protocols will not be backward compatible.
If WSJT_X v2 WSPR does not make a positive decode it compares the possible decode with stations in the "hashtable.txt" file to see if there is a match. If there is then it uses this as confirmation of the decode and adds a"1" to the last column in "ALL_WSPR.TXT"
November 2020 WSJT-X v 2.3.0 With new modes and some modes depreciated is in "release candidate" form.
Beginners, look at these files,
and others:- Starting WSPR [Was http://physics.princeton.edu/pulsar/K1JT/wspr.html] https://wsjt.sourceforge.io/wsjtx.html WSPR_2.0_User.pdf WSPR-X_Users_Guide.pdf
Best forget transmitting until you understand what is happening by getting receive right, single band transmitting is then relatively trivial.
Do not forget time and frequency requires to be set accurately. I use rsNTP http://www.qsl.net/dl4yhf/rsNTP/rsNTP.htm Run as Administrator, a simple way to keep time correct, also the option to give an offset to decode wrongly-timed transmissions.
Frequency setting tips in the WSPR help files.
"False" WSPR Spots
Sometimes the decoder simply does not work correctly. It examines weak signals many times, maybe 8000 or more as shown in ALL_WSPR.txt. It attempts to compensate for fading, drift, time difference. Sometimes it comes up with either no decode or maybe one that fits the WSPR protocol but is wrong. Usually obvious if a Database search is made for the callsign, you are the only spotter.
False Decodes will Always Occur. This refers to FT4/8 decoding but the principle will also be relevant to WSPR. https://wsjtx.groups.io/g/main/message/10811
Operator configuration errors occur. Wrong band spots are common, often due to operator error, sometimes the WSPR program might be in error.
HASH TABLE ERROR
Complex calls or transmitting 6-figure locators can give rise to false spots.
Complex calls can cause WSPRNET to interpret the #tag incorrectly, giving a wrong location on the map. (Due to limited # numbers 2 stations may be active with the same #tag.) See the very last post here http://wsprnet.org/drupal/node/7240 You need to be logged into WSPRnet.
Another example http://wsprnet.org/drupal/node/7707 My call sign is "hijacked" Further down this page KB9AMG explains how this can happen. It can be due to the transmission of 6-figure locators. And even further down the discussion goes on to balloon telemetry, "calls" beginning with 0 (zero) or Q.
Wrong, invalid callsign seen by many spotters,
False decodes You need to be logged into WSPRnet. http://wsprnet.org/drupal/node/7538 GHOST DECODES D http://wsprnet.org/drupal/node/7404
Only use the default mode Type 1 unless you have a complex call or think it vital to send the full locator.
Type 1 messages contain a standard callsign, a 4-character Maidenhead grid locator, and power level in dBm.
Type 2 messages omit the grid locator but include a compound callsign, example:- PJ4/K1ABC 37.
Type 3 messages replace the callsign with a 15-bit hash. Type 3: <PJ4/K1ABC> FK52UD 37.
Type 2,3 messages require both parts to be received for a station to be identified, in marginal conditions you may not be spotted. Also it can happen that two stations are using the same hashtag, then the wrong locator may be reported.
Use Truer Decoding in WSJT-X Modes?.
A paper here https://www.sm2cew.com/Digital%20communications%20using%20minimal%20transfer.pdf puts doubt on the true decoding of weak signals by WSPR and other JT modes. The author says too much reliance is made of references to a database rather than actually fully decoding a transmission. WSJT-X has the option to reduce this, also reducing false "decodes". (In the Menu bar turn off "Decode - Deep" using "Normal" or even "Fast".) BUT also read this long page http://gm4fvm.blogspot.com/2018/04/jt65-eme-and-reality-of-deep-search-for.html
Transmit only stations need to send a report so their 6-figure locator is known.
TX Only? Get WSPRnet to give you a six-figure locator to avoid 2-part transmission:-
WSPRnet takes a station's locator from that station's uploaded data, regardless of band. if you do not use a WSPR receiver instructions for uploading full 6 figure locator.
http://qrp-labs.com/appnotes.html AN002.pdf Or, at the bottom of this page fill in your details. https://www.rfzero.net/documentation/tools/wsprnet-locator-update/
Co-ordinaled Hop Band/Minute [+20+40] 160/00 80/02 60/04 40/06 30/08 20/10 17/12 15/14 12/16 10/18
The QRP Labs QCX may be built as a WSPR RX/TX https://groups.io/g/QRPLabs/message/18257
Maps, Database search, Sort CSV Files
2023:- Data is easier examined, try http://wspr.rocks/ for maps and data Extensive personalised, fast search of the database http://wspr.rocks/livequeries/
Extracting data from the large CSV WSPR files. Some random notes extracted from QRPLabs group:-
A Database program is needed eg. Access for Windows
You could have a look at the OpenOffice version which is almost identical to Microsoft and includes the database as standard and is free to all. dot csv files can be imported into the database.
*****************************************
A Windows program developed for WSPR database sorting.
https://wsjtx.groups.io/g/main/message/11343
I've not tried it but it looks a useful program for those who worry about WSPR/PSKReporter data.
> Also this https://groups.io/g/ProgramsByW2JDB is where you find it. Windows, said not to work with Wine.
*******************************************
On a Windows computer you can install many of the common *NIX command line tools available in
cygwin https://www.cygwin.com/
or Gow https://github.com/bmatzelle/gow/wiki
and there are other WIN32 GNU command line tools sources as well.
BUT, these are not for everyone.
an alternative already exists with Windows.
There is a command line tool called FINDSTR.
Open a cmd.exe window and enter: help findstr and you fill a simple listing of how to use this tool
findstr will search a specified file for a specified string just like using grep in Michaels example.
for example, at the c: prompt: findstr callsignToSearchFor wsprFile.csv > results.csv
This will search wsprFile.csv for the string CallsignToSearchFor and will put the results in file results.csv
This will reduce that very large .csv file down to something more manageable that Excel can import.
Also, SQLite is a very good alternative to using Microsoft Access if you wished to go that way.
cheers, Graham ve3gtc
***********************************************
Hans Excel VBS to sort large files https://groups.io/g/QRPLabs/message/48606
*************************************************
C:\Users\micro\Desktop>FINDSTR 2E0THH wsprspots-2020-05.csv > 202005_WSPR_DB_results.csv
Check Files/Renew Windows 10 installation.
Alternative WSPR Map From VK7JJ
December 2023, Much More Data and Charts Available.
Investigate Phil's contributions http://wspr.rocks/ http://wspr.rocks/livequeries/ It is worth learning from the examples and customising the searches.
Some trials here can give amazing results Grafana charts https://wspr.live/gui/d/o_qTGcqik/home?orgId=1
5 Years of Reception of My 60m Signal by DP0GVN
The above Grafana site has the ability to show a lot of data! I was looking for a chart to show any seasonal or long-term propagation effects.
The "WSPR Paths" selection enabled me to reasonably quickly make this chart. 27071 spots of me in 5 years!
This appears to show the effect of the sun's activity on 60m propagation. I have transmitted 60m WSPR almost continuously for these 5 years.
I need to positively confirm that the Antarctic station DP0GVN has also been monitoring continuously. Reception reports have been made but not many. Grafana station activity shows very few 60m spots by DP0GVN in 2023, is this bad propagation or no receiver? DP0GVN is said to be doing an 11 year observation using modern multi-channel SDR receivers.
Once Grafana is setup it is easy to check other paths, to ZL2005SWL shows an apparent reduction. Looking on other bands gives inconclusive results.
This chart reminds me of a very unusual event. On 27th September 2022 I was contacted by a 60m operator about 40Km away from me. He asked what I was using to get a -1 SNR report from DP0GVN when his inverted V @ 50 feet was only getting -18.
All I could reply was that I use an inverted "L" at 40 feet.
The spike at the bottom right SNR chart actually covers a few days, usually I get SNR reports about the same as the station enquiring and averaging around -25 but on 24-29 September I received 31 reports of -5 or better. 60m is not used by many, only a few others were transmitting around this time. Could this be local pirate reports? Possible but no evidence.
The shot below shows the spike expanded. Shortly after this period spots stopped, propagation or no receiver?.
