[Lowfer] 474.4 kHz FST4W

[Garry]

Hi J.B.,

No I did indeed mean 474.4 kHz, not the usual 474.2 kHz. Rob, k3rwr, has 
been running tests of the various FST4W rates, often at a power level of 
only 1mW like last night. The benefit of moving above the usual 474.2 
kHz +1400-1600 Hz is no interference, at least for now. That's very 
important as the transmission length increases to 1/2 hour. The good 
news is propagation-wise transmissions that long work fine even that 
high in frequency.

So that others know what is being sent I follow N1BUG's suggestion of 
appending the rate to my callsign. The wspr spot database now indicates 
the mode being used too, but it's not correct for 900 seconds and 
instead calls that just wspr-2 (it's not). In my special case to 
distinguish which of 2 eprobes I'm using I end the suffix with a 1 or 2 
rather than 0. Hence in my wsprx2.3.0-rc2 settings I enter k3siw/122, 
/302, /902, or /1802 as appropriate when using eprobe 2. You'll also 
have to define the frequency 474.4 kHz if you use it since the standard 
list only offers 474.2 kHz. I understand you can use 474.2 kHz anyway if 
you change the offset range to 1600-1800 Hz, but I believe Rob indicates 
that doesn't display the true frequency in the spot database.

And finally, to run multiple instances of wsjtx so that you can decode 
multiple rates 120, 300, 900, 1800 all at once you need to launch the 
program from a command window and enter commands like (depends on where 
you have the program installed): C:\WSJT\wsjtx2.3.0-rc2\bin>wsjtx 
--rig-name=k3siwXXXX, where XXXX indicated the T/R decode rate for this 
instance.
-- 
73, Garry, K3SIW, EN52ta, Elgin, IL