I'd just leave it to the WSJT-X team, and only the WSJT-X team.
Neil, KN3ILZ
On 8/9/2018 4:08 PM, Andras Bato wrote:
George is quite right!
Leave it to the dev team -and to Igor!
It well worth to test what does JTDX dev team do.
gl de ha6nn
Andras
On Wed, Aug 8, 2018 at 1:10 PM, George J
George is quite right!
Leave it to the dev team -and to Igor!
It well worth to test what does JTDX dev team do.
gl de ha6nn
Andras
On Wed, Aug 8, 2018 at 1:10 PM, George J Molnar wrote:
> I think he is lamenting the “loss of sensitivity” with FT8 compared to
> JT65 now that the former has come
FWIW, my experience (in ~3yrs of use): lowest JT65 decode about -28, JT9 about
-26, FT8 about -20.
I have gotten a few low level JT9 QSO’s at times when I could not get them on
JT65 - I suspect due to band activity.
My WSJT-X is set for 2-pass, 6 erasure and 10 aggression.
Al Pawlowski,
FT8 was never supposed to have the same sensitivity as JT65 .. you can't
not with only 13 or 14 seconds of Tx time. As was pointed out,
you can have -24 reports on FT8 but its more a result of the noise floor
in your location or the receiving station's location.
Not to mention that
To All,
My rig did the same thing - checked timing with WWV - was exact, and still
no decode.
I'm using VAC's with my current rig - reset those - and wham! Works.
So, the ONLY reason this may not work IS NOT timing. Even if your timing
is off a bit you'll still see some decodes usually on
