Content-Transfer-Encoding: 8bit
Message-ID: <3.0.1.16.20000510092314.2e5f6dce@mail.cc.kuleuven.ac.be>
Date: Wed, 10 May 2000 09:23:14
To: rsgb_lf_group@blacksheep.org
From: "Rik Strobbe" <rik.strobbe@fys.kuleuven.ac.be>
Subject: Re: LF: DFCW  Parameters
In-reply-to: <E12pDrN-0002RU-00@mserv1a.u-net.net>
References: <3.0.1.16.20000509164652.223f2124@mail.cc.kuleuven.ac.be> <3617AC3245C2D1118A840000F805359C017528C4@pdw-mercury-1.der a.gov.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Sender: <majordom@post.thorcom.com>

Hello Mike,

In theory there is no need for these 'gaps', but a series of tests (mainly
conducted by DF8ZR, DF6NM and me) showed that these small 'gaps' had 2
advantages :
1. It eases the reading of characters with a series of dots or dashes (eg.
O, S, J, 5 etc...)
2. It gives the TX a 'break' (reduces the 'on/off' ratio) during long
characters

The disadvantage is that is slows down the speed by 33% (but still leaves
an average speed increase of about 225% compared to QRSS).

In my opinion these 'gaps' should not be obligatory, so you can leave them
out if you wish so.

73, Rik  ON7YD


At 18:25 9/05/00 +0100, G3XDV wrote:
>Rik,
>
>Have I misunderstood, or are you saying there is a gap between 
>each dot and each dash? I thought there was no need to do this as 
>the frequency determines whether an element is a dot or dash so a 
>dot three times the dot lenght must be three consecutive dots.
>Probably me being dumb.
>
>
>Mike, G3XDV (IO91VT)
>http://www.dennison.demon.co.uk/activity.htm
>
>
>