Hi Alex,
You'll have to use a free message and get creative.
73
Ria, N2RJ
On Tue, Jan 30, 2018 at 5:52 PM, SQ9UM wrote:
> Hi all,
>
> I've started in January the activity on FT8 using wsjt-x soft.
>
> I wanted to use my special callsign SN20UM (SN twenty UM) but wsjt-x does not
> accept this t
Hello Alex.
This is not something that can easily be solved in software because the
problem, as I understand it, is an inherent limitation in the FT8 protocol,
specifically the way it encodes callsigns into as few bits as possible. The
simple structure of conventional callsigns plus the limited c
Hi all,
I've started in January the activity on FT8 using wsjt-x soft.
I wanted to use my special callsign SN20UM (SN twenty UM) but wsjt-x does not
accept this two digits combination on third and fourth position in the callsign.
As I can imagine I'm not the first one who has reported this issu
Mike --
It's harmless -- and it's useful. You may comment it out if you choose.
-- Joe, K1JT
On 1/30/2018 11:10 AM, Black Michael via wsjt-devel wrote:
Is this code still needed? Or is "testing" done now? Was checking some
events and noticed this file check firing constantly.
//Ch
Is this code still needed? Or is "testing" done now? Was checking some events
and noticed this file check firing constantly.
// Check for "txboth" (testing purposes only)QFile f(m_appDir + "/txboth");
if(f.exists() and fmod(tsec,m_TRperiod)<(1.0 + 85.0*m_nsps/12000.0))
m_bTxTime=
Dear Sirs
Some 2 years ago I implemented JTSDK, but since the I have moved machines to a
PC running win 10.
I am now trying to implement version 2.0.6 and I downloaded the various
components starting with Vcredist 2010 to JTSDK update 4
but I can not seem to make any progress Vcredist 2010 and
