[RTTY] Cut Numbers Revisited

[Steve Dyer]

This is probably not about cut numbers in RTTY.

What you are seeing is usually caused by the LTRS shift being lost and leaving the decoder in FIGS mode. 

 

OH in FIGS should be 9# not 9h. Not sure why the lower h, so TOO 9# in FIGS. 


See http://en.wikipedia.org/wiki/Baudot_code.


This is why everyone should enable UnShit On Space (UOS) on RX and TX and *not* use hyphens between the parts of the exchange.


73,
Steve
W1SRD










________________________________
 From: DickT-W0RAA <dickt at w0raa.com>
To: Rtty Contesting Reflector <rtty at contesting.com> 
Cc: Writelog Reflector <writelog at contesting.com> 
Sent: Tuesday, January 7, 2014 1:12 PM
Subject: [RTTY] Cut Numbers Revisited
 

I am somewhat mystified why RTTY contesters send TOO for 599 in a RTTY 
Contest or 5NN.  Are they
saving anything (characters or time)?

I had one station in Ohio (I won't give his call) that was sending a report 
of TOO 9h.  When I asked his State
he kept repeating 9h.  Finally he sends OHIO.  This was the RTTY RU contest.

I looked him up on QRZ and dropped him an e-mail and mentioned (politely) 
that a 9h was a little confusing
and that he may not be aware that he was sending CUT numbers.  I suggested 
he check his program (I suspect
he was using N1MM and had a box checked to send CUT numbers).  He replied in 
an e-mail "OK".

I was just about ready to send him a NIL (Not in Log) response in the 
contest when he sent me OHIO.  Nobody
should have to spend time when running or S&Ping to try to figure out what 
somebody is sending.  It breaks
the rhythm in a contest and slows things down.  I guess I'll just have to 
learn that OH is 9h.  Duh!!!!!  I wonder
what the CUT number is for FL or AL or LA, etc, etc?

It would be great if all of these hotshot ops would drop the cut numbers and 
send just plain English.

SOAPBOX OFF.

Dick
W0RAA

_______________________________________________
RTTY mailing list
RTTY at contesting.com
http://lists.contesting.com/mailman/listinfo/rtty