DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=btopenworld.com;
  h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:In-Reply-To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE;
  b=lS9QbY6qScKoY560Uprs9aPpBK/G3/RV71FAiYYuXy89rnma/wCY83CjudFjxbi/nmhs57x7blz9I25+SoL102zLLf/Cz4l6/BRUR57rdAlch+N+fSwnhMt+a4Eykga2oa8tKxpZ2x+fgOJu6Umdjj4GJr6dXFj+CrZ74EK30jY=  ;
Message-ID: <E2A6ECE9D59543C5A01A6DAB0AF18E0B@JimPC>
From: "James Moritz" <james.moritz@btopenworld.com>
To: <rsgb_lf_group@blacksheep.org>
References: <01eb01c9832c$74945e50$a402a8c0@Inspiron><20090131111012.i80joik1ztc0wggk@webmail4.kuleuven.be><AD8469FDDC2A4CE1A2AD0DA3753E415C@JimPC><000f01c983b5$cfe04330$8d01a8c0@JAYDELL><20090131200626.39efb3dc@lurcher><071798B2D2F8408E9570FC11F569524C@AGB><27CD4CCC51DF4FEBB3972EA48A91D068@AGB><20090204223221.yd4hyv5n06ko8c44@webmail4.kuleuven.be><CF8E217110774A38BA0E6B3C169CA6AD@AGB><20090204232519.zgxyis76wx0kk8ck@webmail4.kuleuven.be><8D12605601E74486B002F1EF1D6B263C@AGB><20090205212652.29796780@lurcher> <20090205213158.32fbd1da@lurcher> <6B3A5CCB0A524F06A0739EC58BDE29A0@AGB>
In-Reply-To: <6B3A5CCB0A524F06A0739EC58BDE29A0@AGB>
Date: Thu, 5 Feb 2009 22:57:49 -0000
MIME-Version: 1.0
DomainKey-Status: good (testing) 
Subject: Re: LF: Fldig Flarq  mfsk16  
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


Dear Graham, Gary, LF Group,

Thanks for the QSOs this evening...

It seems MFSK16 works quite well in the presence of QRN, which is quite 
strong here tonight. There is always MFSK8 and MFSK4 to try as well.

The Flarq ARQ mode was quite interesting, although probably not what you 
want for a "traditional" QSO. I imagine it could work quite well when you 
actually want to transmit quite a large amount of text over a period of 
time, rather than "ur 599 wx not vy gud" etc. I set the packet length to 16, 
the smallest possible, with the idea of maximising the chances of receiving 
un-corrupted packets under weak signal conditions, at the expense of 
increased ARQ overheads. Timing out seems to be a problem; there are options 
to configure number of retries and timeout period, which it would probably 
be sensible to set to more than the default 5 retries / 60s timeout due to 
the nature of the QSB on 500kHz. Also, there does not seem to be a way of 
forcing a disconnection if you lose contact with the other station - I think 
this was causing trouble when I  was trying to "connect" G4WGT after G0NBD 
had timed out.

Cheers, Jim Moritz
73 de M0BMU