I attach some c++ code that computes a 2-hour tx scheduling array tx[6][10]. Brief description and sample output included below.
If we decide to use this approach, the array would ideally be refreshed every
two hours. It would also need to be initialized at the beginning of WSPR-mode
operation and then re-generated whenever the Tx Percentage box was changed.
Steve k9an
In addition to the requested tx percentage, the other constraints are:
ntxlim (maximum number of successive transmissions)
ntxbandmin (minimum number of transmissions per coordinated band)
pctx < 17%: no constraints. completely random selection of tx times.
17 <= pctx < 33: ntxlim=1, ntxbandmin=1
33 <= pctx < 50: ntxlim=1, ntxbandmin=2
50 <= pctx < 60: ntxlim=2, ntxbandmin=3
pctx >= 60: ntxlim=3, ntxbandmin=4
I compiled the attached file using: g++ txmatrix.cpp -o txmatrix
Here is some sample output:
./txmatrix 25
Requested % 25 Actual % 25
0 1 0 1 0 0 1 0 1 0
1 0 1 0 0 0 0 0 1 0
0 0 0 0 0 0 0 1 0 0
0 0 1 0 0 0 0 0 0 0
1 0 0 1 0 1 0 0 0 1
0 1 0 0 1 0 0 0 0 0
./txmatrix 50
Requested % 50 Actual % 50
0 0 1 0 1 1 0 0 1 0
1 1 0 1 0 1 0 1 0 1
0 0 0 1 0 0 0 1 0 1
0 1 1 0 1 0 1 0 1 0
1 1 0 0 1 0 1 1 0 0
1 0 1 1 0 1 1 0 1 1
./txmatrix 66
Requested % 66 Actual % 66
1 1 1 0 1 0 1 1 1 0
0 1 1 1 0 1 1 1 0 1
0 1 1 1 0 1 0 1 0 1
1 1 0 1 1 1 0 1 1 0
1 0 0 0 1 1 1 0 1 1
1 0 1 1 1 0 1 0 1 1
txmatrix.cpp
Description: Binary data
> On Jun 3, 2015, at 1:40 PM, Bill Somerville <[email protected]> wrote: > > On 03/06/2015 19:00, John Nelson wrote: >> Hi Bill, > Hi John, >> >> Is this the type of hot switching you are referring to? (From my WSPR log >> - UDP status output.) >> >> --- >> 14:39:53: Dial: 28124600, Mode: WSPR-2, DX_Call: G4KLA, Report: -15, >> TX_Mode: WSPR-2, TX_Enabled: 1, Transmitting: 0 >> 14:39:53: Dial: 10138700, Mode: WSPR-2, DX_Call: G4KLA, Report: -15, >> TX_Mode: WSPR-2, TX_Enabled: 1, Transmitting: 0 >> 14:39:53: Dial: 28124600, Mode: WSPR-2, DX_Call: G4KLA, Report: -15, >> TX_Mode: WSPR-2, TX_Enabled: 1, Transmitting: 0 >> 14:39:57: Dial: 10138700, Mode: WSPR-2, DX_Call: G4KLA, Report: -15, >> TX_Mode: WSPR-2, TX_Enabled: 1, Transmitting: 0 >> --- > The potential hot switching I am referring to is what would happen if a > user defined hardware switching routine, for example to change aerials, > was still in progress when the tune up signal started i.e. switching a > relay when it is passing Tx RF. >> >> Band hopping: >> >> Do you have in mind producing a selection table with tune up similar to that >> in the WSPR guide? This provides a flexible choice of tune-up as well as >> TX fractions > Currently the only band hopping supported is according to the globally > coordinated schedule, the constraints of that schedule do not allow for > per band Tx fractions. Tune up is specified on a per band basis but only > for the 10 coordinated bands. > > My implementation current looks like this: > > https://dl.dropboxusercontent.com/u/4192709/band-hopping.JPG > >> >> --- John G4KLA > 73 > Bill > G4WJS. > > ------------------------------------------------------------------------------ > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
