[RTTY] Getting spotted by RTTY skimmers

[Jim W7RY]

But please remember to put the space between the last letter of the macro 
and the {RX}.

73
Jim W7RY


-----Original Message----- 
From: Jim Preston
Sent: Monday, September 29, 2014 11:34 PM
To: rtty at contesting.com
Subject: Re: [RTTY] Getting spotted by RTTY skimmers

Joe,

I agree 100 percent. My macros have CR/LF at the beginning but not at
the end. The other station doesn't have to chase anything, since my
macro stays on one line.

73,

Jim N6VH


On 9/29/2014 6:57 PM, Joe Subich, W4TV wrote:
>
> CR/LF is fine for the *beginning* of a macro as it does not move
> your call down the screen.  It *ending* a macro with CR/LF that
> causes chasing the call up the screen.
>
> On a proper scrolling display, CR/LF at the beginning of the macro
> will put your call at the left edge of the bottom line of the RX
> window ... generally right under the mouse cursor unless the user
> is making some rather gross mouse movements ... and where the user
> does not need to search for it in the garble at the end of the line.
>
> 73,
>
>     ... Joe, W4TV
>
>
> On 2014-09-29 9:45 PM, Neal Campbell wrote:
>> The CRLF is very frustrating for those trying to click on the callsign
>> and
>> having to chase it around the window. Please do not use!
>>
>> 73
>>
>> *BIG LABOR DAY SALE IN PROGRESS!*
>> Neal Campbell
>> Abroham Neal LLC
>>
>>
>>
>> On Mon, Sep 29, 2014 at 9:17 PM, Lee Sawkins <ve7cc at shaw.ca> wrote:
>>
>>> Starting your call macros with a couple of spaces does as well as
>>> <CR><LF>
>>> and has he added benefit of not causing the text to scroll down the
>>> screen
>>> if you press your callsign button several times.  All macros should
>>> start
>>> with something other than a printable character as many times they get
>>> tagged onto garbage characters and do not get decoded as intended.
>>> Sending
>>> your callsign twice with no leading and ending non printing
>>> characters will
>>> result in no callsign being decoded without extra characters.  This
>>> slows
>>> things down as the receiving op has to manually enter your call with the
>>> keyboard.
>>>
>>> Lee
>>>
>>> ----- Original Message ----- From: "Joe Subich, W4TV" <lists at subich.com>
>>> To: <rtty at contesting.com>
>>> Sent: Monday, September 29, 2014 12:29 PM
>>> Subject: Re: [RTTY] Getting spotted by RTTY skimmers
>>>
>>>
>>>
>>>
>>>> I did get spotted multiple times while S&Ping, but I think that was a
>>>> function of being fast on the draw, so that the skimmers could likely
>>>> have seen " CQ KA0XTT KA0XTT CQ N1EN N1EN N1EN "
>>>
>>> Start your macros with <CR><LF> .... that will make sure you don't get
>>> picked up with the trailing CW or TEST from the previous station.
>>>
>>> 73,
>>>
>>>     ... Joe, W4TV
>>>
>>>
>>> On 2014-09-29 3:09 PM, Michael Adams wrote:
>>>
>>>> There are notes in the second section of
>>>> http://wz7i.com/cw-skimmer/rtty-skimmer.html
>>>>
>>>> The primary trick is to leave trailing whitespace at the end of the
>>>> over.   I used "TEST N1EN N1EN CQ " («note the space) and "TU N1EN CQ
>>>> " («again, the space) and had almost no problems getting picked up.
>>>>
>>>> I did get spotted multiple times while S&Ping, but I think that was a
>>>> function of being fast on the draw, so that the skimmers could likely
>>>> have seen " CQ KA0XTT KA0XTT CQ N1EN N1EN N1EN "   A few times, the
>>>> S&P spots even came through tagged as "skimqsy" or "skimvalid" in the
>>>> CT1BOH logic.
>>>>
>>>> I apparently need to learn patience.  :)
>>>>
>>>> I do think that the smaller number of RTTY skimmers online, and the
>>>> challenges of decoding RTTY vs. CW probably contribute to the reduced
>>>> likelihood of getting spotted by a RTTY skimmer versus a CW skimmer,
>>>> especially on 80.
>>>>
>>>>   _______________________________________________
>>> RTTY mailing list
>>> RTTY at contesting.com
>>> http://lists.contesting.com/mailman/listinfo/rtty
>>>
>>> _______________________________________________
>>> RTTY mailing list
>>> RTTY at contesting.com
>>> http://lists.contesting.com/mailman/listinfo/rtty
>>>
>> _______________________________________________
>> RTTY mailing list
>> RTTY at contesting.com
>> http://lists.contesting.com/mailman/listinfo/rtty
>>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
_______________________________________________
RTTY mailing list
RTTY at contesting.com
http://lists.contesting.com/mailman/listinfo/rtty