[RTTY] Clipped calls

[John GW4SKA]

On the other hand, if there is a short break between your end returning to 
receive and the other station starting TX, make sure you are not using AFC. 
It can drift off and take a character or two to get right.
John GW4SKA

----- Original Message ----- 
From: <peter.jackson17 at ntlworld.com>
To: "Richard Ferch" <ve3iay at storm.ca>; <rtty at contesting.com>
Sent: Monday, November 11, 2013 6:15 PM
Subject: Re: [RTTY] Clipped calls


> Its on incoming calls  ie: KNU (sometimes &KNU) 599 001 001 G3KNU.
> My concern if they leave my call of the end I am not sure if they have my 
> call sign correct.
> 73 Pete G3KNU or &KNU
>
> -----Original Message----- 
> From: Richard Ferch
> Sent: Monday, November 11, 2013 3:37 PM
> To: rtty at contesting.com
> Cc: peter.jackson17 at ntlworld.com
> Subject: Re: [RTTY] Clipped calls
>
> If you mean that you are not seeing what the other station sends, rather
> than that the first character of your own messages is not being
> transmitted, that makes it sound as if your system is not returning to
> receive quickly enough at the end of your transmissions, and the start
> of the other station's message is getting covered up by your
> transmitter. Can you monitor your outgoing transmissions, and if so are
> you hearing a long squelch tail or period of diddle after the end of
> your transmitted texts?
>
> 73,
> Rich VE3KI
>
>
> G3KNU wrote:
>
>> Hi just about every time  during an exchange in a  contest the prefix of 
>> my
>> call sign is clipped or corrupted, but if my call ( I wish everyone 
>> would) is
>> put at the end of the exchange its ok. I also noticed during the wae 
>> contest if
>> I requested a repeat of a qtc the first one was garbage the second was 
>> ok. I
>> think there must be  an error in my basic setup, hope someone can put me
>> straight. I am using MMTTY with N1MM.
>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4158 / Virus Database: 3629/6820 - Release Date: 11/08/13
>