[WriteLog] [RTTY] Cut Numbers Revisited

K2MK k2mk at comcast.net
Wed Jan 8 09:18:00 EST 2014

Hi Dick,

Other posters have advised how a lost character can cause 599 to print as 
TOO. So we can all ignore TOO since we know what it means. The tougher 
problem is when there is a serial number following the TOO as DX stations 
had to send in the RTTY RU. WriteLog has a way of decoding this so you don't 
have to ask for a repeat. If you hold the shift key (or maybe it's the 
control or alt key) and press the first character in the letter string 
WriteLog will paste the numerical RTTY translation into the serial number 
field. This trick may also work if numbers appear for a state abbreviation 
such as 94 for OR or 28 for WI, 48 for RI, etc..

One caveat. If you forget to press the shift key WriteLog may paste the 
letter string into the callsign field.

Mike K2MK

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.



More information about the WriteLog mailing list