> Many 1 by 2 calls and K calls ended their macro transmissions with
> the letter K. A few ended with a carriage return. I found that the
> carriage return separated the macro's content cleanly while the "K"
> often did not.
Several DX stations had neither a K or CR at the end of their messages.
When coupled with no trailing spaces, their calls were often cut off.
Since a CR generally contributes to the "jumping line" syndrome, the
best solution is to add *at least three* spaces after any printing
character at the end of a line to terminate a message macro.
If PTT is dropped early only the spaces get lost ... if the interface
and software properly handle PTT there is a clear space before any
garbage characters get added to the line. The "penalty" for the three
extra spaces is less than 1/2 second so it should not impact even the
stations with the highest rate.
73,
... Joe, W4TV
On 2/13/2011 7:20 PM, W70m@aol.com wrote:
> Many 1 by 2 calls and K calls ended their macro transmissions with the
> letter K. A few ended with a carriage return. I found that the carriage
> return separated the macro's content cleanly while the "K" often did not.
> Others had there macros set to end with the final message, often a number or
> call. Then the noise got hold of the received line and often confused the
> receiver as to is the number complete and/or the call was right.
>
> For purposes of a thread, I find the use of carriage returns at the
> termination of a macro to save a lot of repeats; not to mention busted calls.
>
> Those ending a macro with their 1 by 2 calls should at least introduce a
> space before terminating the transmission.
>
> 73
>
> Rod W7OM
>
>
>
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|