Thanks Bob.
Makes sense once you know about it.
I don't know how much I'm going to worry about it.
Out of the thousands of contest QSO, this one like this.
TNX es 73
Bob, K1VU
At 10:33 PM 11/11/2012, Robert Chudek - K0RC wrote:
>If he was sending REQ REQ, he was NOT using cut numbers. Your decoder was set
>to 'unshit of space' and his decoder was not placing a 'shift' before the
>number string.
>
>Using N1MM if you Shift Click on an unshifted string of numbers and it will
>automatically convert to the equivalent numbers.
>
>You will see on the keyboard QWERTYUIOP = 1234567890 (look up and left of that
>top letters row for the equivalent numbers).
>
>73 de Bob - KØRC in MN
>
>------------------------------------------------------------------------
>On 11/11/2012 8:45 PM, rjohnson wrote:
>>Hi:
>>During the WAE TTY contest I had a DL station send his Serial Num, using Cut
>>Numbers.
>>
>>This caused me a lot of problems. N1MM wouldn't read it when I clicked on the
>>SN.
>>I wasted a lot of time trying to make the exchange, finally after sending NR?
>>NR? several times
>>he came back with 431 431 431.
>>
>>Why would anyone want to use Cut Numbers in a RTTY contest ???
>>
>>I can see using them in a CW contest, but even there it causes confusion.
>>
>>In RTTY, the only thing that I can see is you don't need to send FIGs (SN)
>>LTRs.
>>
>>If there is another reason to do this, please enlighten me.
>>
>>TNX es 73
>>Bob, K1VU
>>
>>
>>_______________________________________________
>>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
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|