Discussion:
[Wsjt-devel] WSPR 2.20 r2283 beta tests
Joe Taylor
2010-12-07 20:12:38 UTC
Permalink
If you have been testing WSPR 2.2 with its frequency-hopping, feature,
please upgrade to revision 2283. Direct links for download are:

Windows:
http://www.physics.princeton.edu/pulsar/K1JT/WSPR2.20_r2283.EXE

Linux:
http://www.physics.princeton.edu/pulsar/K1JT/wspr_2.20r2283_i386.deb

This version has several new features:

1. A checkbox labeled "Coordinated bands" is now available at the bottom
of WSPR's Frequency Hopping screen. If this box is checked, the
first-choice selected band will be determined by the UTC minute at which
a 2-minute sequence starts:

UTC Band
Minute (m)
----------------
00 160
02 80
04 60
06 40
08 30
10 20
12 17
14 15
16 12
18 10

20 160
22 80
... etc

The sequence of ten possible bands repeats three times each hour. If
the first choice band has not been checked as an active band, a random
band choice is made among those that are active.

Decision whether to receive or transmit is purely random, using the Tx
fraction for the selected band.

If all WSPR stations using frequency hopping use the "Coordinated bands"
option, a sizable group of will move together from band to band. During
any particular sequence, something like 20% of the stations (depending
on their Tx fraction settings) will transmit, and the rest will receive.
The average number of spots will be much larger than that if band
selection is random. If a band gets too crowded -- say, if you often
see more than 6-8 stations in one sequence -- you should probably reduce
your Tx fraction for that band.

2. There is now an "ATU tuneup" feature. When WSPR hops to a new band,
if the "Tuneup" box for that band is checked the program will transmit a
carrier for 4 seconds. This should happen at about 115-119 s in the
basic 120-second cycle. The idea is that automatic ATU's would tune
themselves during this time. (It may turn out to be better to use a
shorter tuneup interval, say 1 second, or to make the duration a user
parameter. Automatic ATU's with memory need only a very short signal.)

3. Frequency-hopping parameters are saved on program exit and restored
when the program is restarted. The information goes to a new file named
"hopping.ini".

As usual, user feedback is encouraged!

I have been running in this mode for the past few days, and will
continue doing so this week. Please give it a try, so we can have a
significant number of stations moving together from band to band.

-- 73, Joe, K1JT
Joe Taylor
2010-12-07 20:22:43 UTC
Permalink
Hi Sivan, John, and all,

It's worth mentioning that WSPR r2283 includes code that sets priorities
for the Rx and Tx threads to +1 (slightly above normal) and the decode
thread to -1 (slightly below normal). This just might have some effect
on the apparent timing bug that Sivan noticed yesterday.

I hope I have done the priority-setting correctly. If anyone here knows
what he/she is doing in this respect, please look at and critique the
new code in start_threads.c !

-- 73, Joe, K1JT
Joe Taylor
2010-12-09 15:49:27 UTC
Permalink
A beta release of WSPR 2.21 r2286 has been posted at:

Windows:
http://www.physics.princeton.edu/pulsar/K1JT/WSPR2.20_r2286.EXE

Linux:
http://www.physics.princeton.edu/pulsar/K1JT/wspr_2.20r2286_i386.deb

As in r2283, this version includes a "Coordinated hopping" mode in which
the selected band is determined by the starting UTC minute:

UTC Band
Minute (m)
----------------
00 160
02 80
04 60
06 40
08 30
10 20
12 17
14 15
16 12
18 10

20 160
22 80
... etc

This sequence of ten possible bands repeats three times each hour. If
the designated band has not been checked as an active band, a random
band choice is made among those that are active.

In r2286 the algorithm choosing whether to Rx or Tx guarantees at least
one transmission on each active band every two hours. If all ten bands
are active there may be up to three transmissions on any band in a two
hour period. These choices will tend to maximize the number of
potential spots on all bands, by all frequency-hopping stations.

It's not hard to discover the identities of some stations who've been
doing "coordinated hopping" over the past few days. I have been using
all 10 bands (Rx only on 60 m). Here are a few who have spotted K1JT
many times on different bands during the past 24 hours:

Call Dist Total Bands
(km) Spots
----------------------------------------------
AK4DW 932 53 160 80 40 30 20 17 15
EA1FAQ 5703 59 80 40 30 20 17 15
G4KLA 5485 29 80 40 30 20
G8JNJ 5480 23 80 40 30 15
KC6KGE 3942 15 80 40 30 20
KE7A 2160 53 160 80 40 30 20 17 15
N4AU 1342 71 160 80 40 30 20 17 15 12
W3PM 1240 64 160 80 40 30 20 17 15

It's fascinating to watch the daily changes in ionization, causing each
band to open at an appropriate time.

-- 73, Joe, K1JT
Bill V WA7NWP
2010-12-09 16:37:27 UTC
Permalink
As in r2283, this version includes a "Coordinated hopping" mode in which the
 UTC   Band
Minute  (m)
----------------
00      160
02       80
04       60
06       40
08       30
10       20
12       17
14       15
16       12
18       10
20      160
22       80
... etc
This sequence of ten possible bands repeats three times each hour.
6 and 2 meters are not supported? I believe they will be a very
interesting addition to this new technology. It's hard to justify
dedicating a setup for bands where openings are so infrequent yet it
would be so cool to be there to catch the openings that do happen.
Fortunately we have rigs like the 817 and IC706 which make those
VHF/UHF bands available with all the others...

73
Bill - WA7NWP

Loading...