The LONGWAVE MESSAGE BOARD
Re: Focusing on SIW weak signal modes


[ ]     [ View/Post Followups ]     [ Read Msg Board FAQ ]

Posted by Mark Kostora on February 24, 2023 at 18:00:41.

In Reply to: Re: Focusing on SIW weak signal modes posted by Garry, K3SIW on February 17, 2023 at 02:21:35.

Hi Garry,
Thanks for your efforts of attempting to help me find a binary version of wsprx. After digging for information on this myself it does turn out that WSJT-X 2.6.0 is capable of decoding WSPR15 but there is a catch. WSJT-X does not decode WSPR15 in real time but using the DOS command line utility binary wsprd.exe that is in the wsjtx binary directory, there is the capability of decoding the saved .wav files that includes the option -m to decode wspr-15 .wav files. But it is not just a matter of using the -m option. A combination of using some of the other options is necessary to successfully decode those weak signals. And of course I have some catching up to do on improving the LOW end receiving capabilities of my rig. I don't have room for a mile long beverage receiving antenna but I am working on a homebrew 'shielded' loop antenna and a pre-tuner. Will keep you posted on any victories I achieve on my own homebrewed flavor of a rig. (see the wsprd.exe options below)

C:\WSJT\wsjtx\bin>wsprd
Usage: wsprd [options...] infile
infile must have suffix .wav or .c2

Options:
-a path to writeable data files, default="."
-B disable block demodulation - use single-symbol noncoherent demod
-c write .c2 file at the end of the first pass
-C maximum number of decoder cycles per bit, default 10000
-d deeper search. Slower, a few more decodes
-e x (x is transceiver dial frequency error in Hz)
-f x (x is transceiver dial frequency in MHz)
-H do not use (or update) the hash table
-J use the stack decoder instead of Fano decoder
-m decode wspr-15 .wav file
-o n (0

------------------------------- 73s Mark Kostora KD7NEB (NEBLF)

Follow Ups:



Post a Followup?

*Name:   *Subject:

*Name, *Subject, *Message Required   E-Mail (option):

* Your Followup Comments: