Consider this: There are only 10 kinds of people in this world. Those who understand binary and those who don’t.

RTTY Contesting Basics Doug Haft KY4F

Introduction My background – KY4F RTTY contesting: differences and similarities with other modes Employing the information covered here today should: Entice you to try RTTY Contesting, or If already in the RTTY Contests…. Improve your score

Topics: A Brief History of RTTY Its been around a long time Garbled Print Its inevitable. We must live with it. Parsing & Phantoms Why these are critical to understand Macro’s What is the most efficient way to format your message buffers?

Topics: Running vs. Search and Pounce Summary Thank you to Dan Murphy, K7IA who’s eBook, Contesting and RTTY--The Basics, was the inspiration and primary source for this presentation.

Topic 1: A Brief History of RTTY Most of us think of RTTY based on WWII movies etc. Uses a five bit code for each character. The Baudot code was patented in 1874! No computers in those days. Teletype (TTY) machines were electro mechanical devices. Guam: Late 1960’s bottom row - AN/UGC-25 printer middle row - TT-176/UG keyboard/printer top row - TT-187A/UG tape reader plus TT-192A/UG tape punch wall - KWX-7 sync switch for crypto gear

Topic 1: A Brief History of RTTY Being only five bits, a maximum of 32 discrete combinations. This presents a problem: 26 letters 10 digits Various Control Characters The 32 limit is exceeded! What to do?? Shift the carriage. LTRS & FIGS. The Baudot Code Letters mode Figures mode Control characters

Topic 1: A Brief History of RTTY Originally, TTY was carried out over landlines using a DC circuit. A mark (1) was interpreted when the circuit was closed and space (0) when the circuit was open. In RTTY we create the mark and space by sending on two frequencies. Mark on one frequency space on the other These frequencies are 170Hz apart. Hence 170Hz shift Marks and Spaces

Topic 2: Garbled Print Your decoding software is constantly trying to interpret what it “hears” into marks and spaces. Results in garbled characters. Ltrs when not desired Figs when not desired Incorrect characters printed USOS For Example Sent Text: KY4F KY4F First “4” hit by garbled and interpreted as RX Text: “KY! (64!” With USOS : “KY! KY4F”

Topic 3: Parsing & Phantoms Parsing is not a new concept If you’re reading this easily, you’re parsing. Ifyoufindthisalittlemored ifficulttoreaditsbecauset heparsingelementshave beenremoved Let’s make copy at the distant end as easy as possible by using parsing elements. Phantom characters appear because the transition from sending to receiving is not a smooth one. Almost ALWAYS 1 or 2 characters will appear on the screen when the distant end transitions. When you transition from Tx to Rx, locally generated phantoms will appear on your screen as well.

Topic 4: Macro’s/Message Buffers  Run Macro’s F1 CQ Message F2 Exchange F3 TU & QRZ {tx}{enter} CQ CQ SARTG { MyCall} {MyCall} {enter}{rx} {tx}{enter} {HisCall} TU 599-#- # {MyCall} {enter}{rx} {tx}{enter} {HisCall} TU QRZ SARTG {MyCall} {enter}{tx} **These examples are from K7IA’s ebook Understanding RTTY Contesting SARTG Examples

Topic 4: Macro’s/Message Buffers An example: Always put a Space before and after your call sign. Always remember there WILL BE phantoms and garbles Build your message buffers to minimize the impact CQ SARTG K4TD V --a phatom V appears on TD’s screen Answered by K6ABC VK6ABC K6ABCYQ -K6ABC is not using parsing elements. If he/she were, the print would be: V K6ABC YQ

Topic 4: Macro’s/Message Buffers  Run Macro’s F1 CQ Message F2 Exchange F3 TU & QRZ {tx}{enter} CQ CQ NA {MyCall} {MyCall} {enter}{rx} {tx}{enter} {HisCall} TU DOUG AL AL {MyCall} {enter}{rx} {tx}{enter} {HisCall} TU QRZ NA {MyCall} {enter}{tx} **These examples credit to K7IA’s ebook Understanding RTTY Contesting NAQP Examples

Topic 4: Macro’s/Message Buffers  S & P Macro’s F2 Exchange F3 TU F4 My Call x 2 And NOTHING else {tx}{enter} {HisCall} TU 599-#- # {MyCall} {enter}{rx} {tx}{enter} {HisCall} TU {MyCall} {enter}{tx} {tx}{enter} {MyCall} {MyCall} {enter}{rx} **These examples credit to K7IA’s ebook Understanding RTTY Contesting SARTG Examples

Topic 5: Running vs. S&P Running Turn on AFC Turn on USOS Construct Message Buffers with parsing elements S & P Turn off AFC Turn on USOS Never send the running station’s call sign when answering his CQ!! Do not use “de” … ever Construct Message buffers with parsing elements.

Summary RTTY uses the 5 bit Baudot code Requires LTRS and FIGS Phantoms and Garbles WILL occur Construct your message buffers to minimize the ill effect of Phantoms and Garbles Never send 5NN Never send the running station’s call sign when responding to the CQ

Summary Most of this information is from Contesting and RTTY – The Basics by Dan Murphy K7IA Dan asks that you him to request a copy* Available for ACG members in the file download area of our web site. Visit Questions or comments? Feel free to me at * Dan’s address is available on qrz.com