I have been reading many posts by people complaining that they are
not getting decodes in FT2. Many are trying to "remote" into their
stations. The "latency" between their current station and the
remote station can be the problem. Also the computer's clock needs
to be
REALLY correct!
Alan, the time sync for FT2 is very tight. If
the DT is more than 0.06 secs, the signals won’t
decode. If the signals bleed over the time period lines on the
waterfall, this means the DT is too high to decode. Between the
other station's DT and any latency in your internet connection,
remote FT2 may be a tough go.
Although I don't have any insight of actual
implementation neither about the mode itself, with such short
turns I'd expect few decodes -if any - due poor timing between
ends and/or network latency. Sometimes
simply we cannot have it all.
To try and correct some of the timing issues, Uwe has released a
newer version today (February 28th). Here is the link to
SourceForge with the newest files:
https://sourceforge.net/projects/wsjt-x-improved/files/WSJT-X_v3.1.0/
Look for the 3 files that end with "260228.exe" (Stands for
2026-Feb-28th)
On 2/28/2026 12:48 PM, Uwe, DG2YCB via Wsjt-x-improved-community
wrote:
> Hi Hasan and all,
>
> The main reason for today's 260228 update was that we finally
found (and hopefully) fixed the root cause of a timing issue which
sometimes let the program switch to the wrong time slot. It was due
to a rounding error, by the way. Good when it works now.
>
> FYI: I will upload slightly enhanced "260228" Windows 64-bit
installers within the next 30 minutes or so. The only difference is
that we can now also use TCI for FT2 mode (including TCI audio).
>
> 73 de DG2YCB,
> Uwe
> ________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail:
dg2...@gmx.de
> Info:
www.qrz.com/db/DG2YCB
73, Clark, W8TN