What is the status of the WSPR background and autostart features? [added in v1.181]
edited April 2018 in Problems Now Fixed
I see them listed on the Bug/Wish List page as a higher priority but no indication of in test nor checkins in github.
I have found that I cannot keep browser-initiated WSPR sessions running for more than a few days, even when the browser and Kiwi are wired to the same switch.
So I am trying to decide if I should invest time in a multiple Rasperbrry Pi + SDRPlay solution for a multiband WSPR receiver appliance.
The Kiwi seems a much better (and cheaper!) solution, so I would rather invest time in advancing that aspect of Kiwi functionity.
What is the version of the WSPR decode library? I see your sources are dated 2015 and I thought there was a recent upgrade to that library in WSJT-x 1.8.0, but I am lost trying to find the WSJT-x source repository.
The WSJT/WSPR-X etc. codebase is a complete nightmare and there is no way I'm going to spend any time trying to unravel that stuff. If someone wants to do it and contribute a working, debugged and tested update to the existing Kiwi WSPR code that's fine.
Also be aware that there is some controversy regarding the frequencies used for WSPR on 80m.
"with WSJT-X v1.8 we intend to correct an anomaly that has existed for a long time in that Japanese amateur radio operators have no privileges for the frequencies commonly used for WSPR, JT65 and JT9. The current frequencies (USB dial frequency) are:
WSPR 3.592600 MHz, JT65 3.576000 MHz, JT9 3.578000 MHz
because we strongly prefer that WSPR and JT mode frequencies are globally coordinated where possible, the proposed new frequencies are:
WSPR 3.568600 MHz, JT65 3.570000 MHz, JT9 3.572000 MHz, FT8 3.573000 MHz
This places the conventional 200 Hz wide WSPR sub-band (centred around +1500 Hz audio offset) into the lower 200 Hz the JT65 sub-band. The lower 200 Hz of the JT65 sub-band is not used due to SSB filter roll off."
Most folks are sticking with the original allocations, but you may wish to include the new(ish) proposed frequency in the KiWi WSPR decoder list of frequencies.
Martin - G8JNJ
Ah OK, I hadn't realised the significance of "80m_JA" as my understanding was that this is a new IARU proposal affecting all regions.
However the current autorun code extracts only 1/2 of the signals that WSJT-x v1.9.1, so on 20M I am running a broswer on my Mac and feeding audio to WSJT-x.
This is an awkward and fragile SW architecture and I am looking at how to replace it.
One approach is to run the Python kiwirecorder on the Mac/Pi/.. and capture the IQ data to a file and then execute the wsprd app included in WSJT-x, but that would force me to synchronize time between the two.
As an alternative, I am studying writing a Kiwi extension modeled on the auto-wspr extension which simply writes the 2 minutes of IQ samples to a file on the Kiwi and then each 2 minutes it transfers that file to a PC/Mac/Linux server for processing by the WSJT-x sw on that machine. Such an approach would disconnect the Kiwi-PC connection from time-critical functions and also free the Kiwi from a need future changes/enhancements to the WSPR processing code base.
Does writing such an enhancement seem a useful approach to solving my problem?