Not Quite the Answer for WSPR on 23cm WSJTx dev

WSJTx dev has WSPR (only 2 not 15) on it, I suppose no one on the development team has a use for 15 so it is being forgotten. During my tests on MF I had my doubts about the advantage of WSPR15 over WSPR2 but by no means is the case proven.

“WSJTx 1.6 dev handles 1296MHz fine”. Now that will be nice, I installed it. But I run XP, do the developers test on XP ? During set up Test PTT locks in TX mode the only way out is to kill the program..

Despite a few foibles the thing works nicely on on 1296MHz displaying the reports correctly and producing an ALL WSPR log that works. Next day is when the problems start WSJTX.bin does not work. Other WSPR and WSJT software works OK still. Ah well shut down the computer, it wont, part way through close down the computer  locks up and you have to crash it. Wanting to use WSJTX dev for tests I uninstalled the program WSJTX.bin does not get removed, after much struggling you can remove it and re install. Running the Program produces an error message ‘A File is Locked would you like to remove it’, say yes and nothing happens.

At computer close down after the first or re-install there is an odd period of blank screen, suspicious behavior.

So we have no version from the JT stable that runs 1296MHz WSPR on XP and sends usable reports to the Database.

Want to run WSPRx dev. on XP ? Here is how to do it.

Install at the beginning of the session, after use before you close the computer, uninstall WSJT dev.

Tomorrow re install.

As I say my activity on air is plagued by flaky software. I lost faith in JT stuff working properly years ago waiting for a few moths before gong to the next release. I found it a thankless task reporting the problems, things have not changed.

WSPR 2.11 and 1296MHz

I am sure at some time I have had sensible results on 23cm WSPR. The problem of wrong tabulation of data I seem to remember was with WSPR2.

I have tried WSPR2.11 and that is the same as WSPRx.

151104 2244 1296.500000 Transmitting G3ZJO IO92 7
151105 1120 36 3 -1.01296.501503 G3ZJO IO92 33 0 1 0
151105 1128 36 3 -1.01296.501503 G3ZJO IO92 33 0 1 0
151105 1138 36 3 -1.11296.501503 G3ZJO IO92 33 0 1 0

Needless to say these Spots are not acceptable for the Database.

Interestingly there was a comment submitted by JH1GYE on Wed, 2014/01/22 – 13:00 on WSPR.net #Today, we tested 23cm 2-way WSPR. Our callsign was displayed on Activity list and Map. But T/R data was not displayed on the Spot Database. #

There were no responses on this subject.

There are an awful lot of Amateurs setting themselves up as programmers these days, my life on air and off is plagued with poorly written and buggy software.

Come on guys if you can’t do it, admit it and give up writing the stuff. Otherwise its not Rocket Science, it might be Amateur but that’s no excuse for amateurish.

WSPR on 23cm and WSPRx 8 v.xxxx

It was only a matter of time before G6AVK got set up for 1296MHz again and he won the challenge to get some signals 2 way outside the county on 23cm.

2015-11-04 13:08  G3ZJO  1296.501599  -18  0 	 IO92ng   2 	G6AVK 	 JO01ho

I was amazed to find that WSPRx does not cope with 1296MHz. I told JT years ago that in the WSPR display field the data is Nomadic. That is it wanders about the display and is not aligned with the Labels above. I even gave him the code to cure it which I was using when I compiled WSPR for Linux, the advice was not appreciated.

Well not only has the 1296.501xxx wandered across into the DT column making the display look horrific, it does the same in ALL WSPR.txt so the  Spots are not uploaded. I have to manually edit all reports by adding a [SPACE] between DT and Freq.