RTTY Tutorial



RTTY Tutorial

 This document was originally posted by K4WW on rttyinfo.net but this domain has expired since some months at time writing. I’ve archived a copy that I believe could be usefull for beginners.
This is not intended to be an “etched in stone” indication of how to operate a RTTY contest, so please don’t take it that way! Whatever works the best for you, is what you should do, as long as it allows your participation to be fun! These hints were obtained from RTTY contesters, world wide, and only reflect how they try to make their operation more efficient! The more efficient “we” make our contest exchanges, the more efficient we make it for all involved! Band conditions certainly play an important part in the exchanged data, so establishing a “different” buffer could make your exchange more efficient in “not so good” band conditions!

There are many web sites to obtain RTTY contesting information, and for fear of slighting anyone, I will only suggest that if you intend to participate, regardless of the level, that you visit rttyjournal and acquaint yourself with the rules, or at least the necessary exchange! Subscribing to rtty@contesting.com is also advisable, as most all RTTY operators, especially those primarily interested in contesting, can be found here. Someone there can answer most any question that you may have! Some contest managers do not allow points for “unique” callsigns in the submitted logs! There are varying definitions of “unique”, or the specific number of logs that a callsign must appear in to not be classified as “unique”! Having this knowledge, if you choose to just work your friend just to give them a point, make sure that you work a few (4-5) others, to insure that the contest manager will allow the contact with your friend!


RTTY For Newcomers

by Bill, W7TI
RTTY is a fun mode and easy to operate, but there are some questions every newcomer has. Please take a moment to read the following and much of the mystery will disappear.



A RTTY transmitter sends out a carrier that shifts back and forth between two frequencies. There is no amplitude modulation, only a pure carrier which shifts frequency. The lower RF frequency is known as the SPACE frequency and the upper RF frequency is known as the MARK frequency. The difference between the two is known as the SHIFT. For amateur radio, the SHIFT has been standardized at 170 Hz. It is customary to refer to the MARK frequency as your operating frequency. For example, if you say you are transmitting RTTY on 14080.00 kHz, which means your MARK frequency is 14080.00 kHz and your SPACE frequency is 170 Hz lower, or 14079.83 kHz. While 170 Hz is the standard shift, sometimes you will find stations using a shift of 200 Hz, but don’t worry about it. Your equipment will copy it fine in almost all cases.



You will often hear the terms FSK and AFSK when talking about RTTY on the HF bands. FSK means Frequency Shift Keying and AFSK means Audio Frequency Shift Keying. Regardless of which method is used, the RF signal sent out over the air is identical. MARK is always the higher RF frequency and SPACE is always the lower RF frequency. If the transmitter is operating properly, the station receiving the RTTY signal can not tell any difference at all. So what is the difference? It’s the way your transmitter generates the RF signal.

With FSK, your transmitter receives a simple on-off signal which causes the carrier frequency to shift back and forth. This signal may come from a TNC (Terminal Node Controller) such as a Kantronics KAM, an AEA PK-232, HAL DXP-38 or some other, or it may come from a soundcard program via one of your computer’s com ports. FSK is simpler, easier and more foolproof than AFSK and is highly recommended if your transmitter supports FSK input. Check your owner’s manual if you’re not sure.

Since not all transmitters support FSK input, there is another method available - AFSK. AFSK can be used with any SSB transmitter. AFSK is a bit trickier to set up and use, but when it is done correctly, it works just as well as FSK and will transmit a perfect RTTY signal. Also, AFSK can do some things FSK can not, such as Automatic Frequency Control (AFC) of the transmitter. With modern transmitters, drift is not a problem and transmit AFC is generally not needed. With older tube-type equipment, it may offer some advantage.

To operate with AFSK, you put your transmitter in the SSB mode instead of FSK mode, and you put an audio signal into the microphone input (some transceivers have a rear connector for audio data input). When you transmit your TNC or soundcard will put out a pair of audio tones that cause your transmitter to send the required RF output. Sounds simple, right? Here’s the tricky part: The tones are two simple sine waves, but the frequency and amplitude of the tones is critical. Let’s say you want to transmit on 14080.00 kHz, as in the previous example. Remember that your MARK signal has to be on 14080.00 kHz and SPACE 170 Hz lower. How do you do that with AFSK? Here’s how. With your transmitter in the LSB mode (Lower Side Band), whatever frequency goes into the microphone input will be subtracted from what your dial says and be transmitted on that frequency. For example if your dial says 14080.00 kHz and you put in a 1000 Hz audio tone, your transmitter will put out an RF signal at 14079.00 kHz, exactly 1000 Hz lower than your dial. So in this case, if the 1000 Hz represented your MARK signal, you would have to set your transmitter to 14081.00 on the dial, and your MARK signal would be transmitted on 14080.00, just as you wanted. Ok so far? Now, what about SPACE? Remember, you want your SPACE signal to be transmitted 170 Hz lower, on 14079.83 kHz. What audio tone will give you 14079.83? Simple - 14081.00 minus 14079.83, or 1170 Hz. So the MARK audio frequency is 1000 Hz and SPACE is 1170 Hz.

There you have the basics of AFSK. Your TNC or soundcard generates the two audio frequencies and your transmitter converts them into two RF frequencies. For technical reasons related to harmonic generation, audio frequencies of 1000 Hz and 1170 Hz are NOT recommended. They are used in this example just to keep the math simple. The recommended audio frequencies are 2125 Hz for the MARK audio frequency and 2295 Hz for the SPACE audio frequency. Making the frequencies higher like this will reduce second harmonics while keeping the tones within the passband of your SSB transceiver.

If you’ve been paying close attention, you may have noticed the SPACE audio frequency is higher than the MARK audio frequency, just the opposite of the RF frequency. This happens because you’re using lower sideband. If you happen to forget and set your transmitter to USB instead, two things will happen. Because your MARK and SPACE are now reversed in your receiver, any RTTY signals you hear will not print correctly. All you will see is random characters that make no sense at all. The other thing is that YOUR transmissions will also be nonsense to the other guy. So just remember - always use LSB. In the real world of course, sometimes USB gets selected accidentally. Nearly all software has a means to quickly reverse the tones, either a keyboard command or an on-screen button to click. When you have a station tuned correctly but all you see is nonsense printing reverse the tones. Now you can print the other fellow and tell him he is “upside down”, as it’s called. After he reverses himself, just reverse again and you will both be back to normal.

Also, you should know that in some parts of the world, especially Europe, the standard is to use USB instead of LSB. This works fine as long as you also reverse the two audio tones. In the US, nearly all equipment defaults to LSB. If you prefer to use USB, be sure your tones are reversed all the time.

The really critical part about AFSK is the amplitude of the signal fed into the microphone connector (or rear panel connector), together with the microphone gain setting. You must NOT overdrive your transmitter or spurious signals will be transmitted. In general, keep the audio drive low enough that your transmitter does not generate any ALC voltage. Never try to drive your transmitter to maximum output. Around 80 to 90 percent of maximum is about right. Consult your owner’s manual for more information on how to do this. If you ever hear a station at two or more frequencies at the same time, the cause is almost always overdrive. None of this applies to FSK, of course. With FSK, you can run full power and not worry about overdrive.



RTTY uses the Baudot code, invented before radio even existed, and still widely used throughout the world. The Baudot code uses data bits to represent letters, numbers and punctuation, much like your computer does. Unlike your computer, which uses eight bits for each character, the Baudot code uses only five, plus a start bit and stop bit. Using fewer bits is good because it speeds up transmission and reduces the chance of errors, but there is a complication. Five data bits can only represent 32 different characters. Since there are 26 letters in the English alphabet plus ten numbers, plus some punctuation, 32 different characters is not enough, even if you only use capital letters, as Baudot does.

Mr. Baudot could have chosen to use six data bits or even more, but he found a better solution. He reasoned that most of what is sent would be letters rather than numbers or punctuation, so he assigned all the letters to the basic 32. He then had six characters left over and he did a very clever thing with two of them. He made one of them a FIGURES SHIFT and another a LETTERS SHIFT. The way it works is this: When sending one of the basic 32 characters, nothing special happens. But when a number or punctuation is to be sent, a FIGURES SHIFT character is sent first (it’s a non-printing character - you won’t see it on your screen). Whatever follows will still be one of the basic 32 characters, but the receiver will interpret it differently. For example the letter Q uses the same five data bits as the number 1, but when the receiver gets a FIGURES SHIFT, it prints the following character as a 1, not a Q. This continues until a LETTERS SHIFT character is received, at which time the receiver goes back to “normal” printing. All of this shifting is done by the system - there is no key marked LETTERS SHIFT or FIGURES SHIFT. It’s all-automatic and you will scarcely notice it happening.

In fact, the only reason to mention it at all is because we are using radio instead of wires, and radio is susceptible to interference from various sources such as lightning static, man-made noise, QRM, etc. If a burst of static should happen to wipe out a LETTERS SHIFT or FIGURES SHIFT character, the characters following will not print correctly until another LETTERS SHIFT or FIGURES SHIFT is received. For example, suppose you are sending a signal report of 599, but the FIGURES SHIFT character gets wiped out by a burst of static. Instead of printing 599, the other fellow’s computer will print TOO. TOO is exactly the same as 599, without the FIGURES SHIFT. So how can he read what you sent? It’s easy if he knows the secret. Here it is: Look at the top row of letter keys on your keyboard - QWERTYUIOP. Now look just above each key and to the left. Each of those number keys is the same as the letter key below and to the right, plus the FIGURES SHIFT. In our example, TOO = 599. Likewise, the word PIPE, if the LETTERS SHIFT were missed, would print as 0803. If 0803 lost its FIGURES SHIFT, it would print as PIPE. Some RTTY programs have a way to highlight the erroneous characters and change them to the correct shift.



All TNCs and soundcard programs have to have some means of tuning in a RTTY signal. If you have that hearing ability known as “perfect pitch” you might get along with ears alone, but the rest of us need something to look at. For now, use what your equipment provides, but if you get really hooked on RTTY, you will probably want to invest in an oscilloscope. A scope works by having the MARK and SPACE tones from the receiver drive the X and Y channels, without any internal sweep. The pattern on the scope will be a pair of ellipses (flattened circles) at right angles to each other. When properly tuned, the ellipses are exactly vertical and horizontal. When the receiver is mis-tuned, they lay over at an angle. Properly set up, a scope provides an instant indicator of any tuning error. Fortunately, even a very inexpensive scope will do just fine. High speed and lots of bells and whistles are not needed.



When the bands are nearly empty, you can use practically any receiver bandwidth with good success. Your SSB filters are probably between 2.1 and 3.0 kHz wide and as long as no other stations are nearby, copy will be fine. For optimum performance however, less bandwidth is better, in fact MUCH better. 170 Hz shift RTTY only needs about 250 Hz for proper copy. If you don’t have a 250 Hz filter, 500 Hz will do pretty well, but anything wider than that will not be satisfactory in the long run.

You may wonder why, for 170 Hz shift, you need a 250 Hz filter? Why not 170? The reason is that shifting the frequency generates sidebands adjacent to the actual signal and if the sidebands are attenuated, the signal will be degraded. RTTY (as used on HF) is actually a form of FM, and FM does produce sidebands, believe it or not. If you’d like to understand FM a little better, the ARRL handbook is a good reference.

Depending on your transceiver, you may or may not be able to use a narrow filter for RTTY. Some of the less expensive transceivers do not have a true FSK mode, and also are unable to select a narrow filter while in the LSB mode. Using an outboard audio filter between the speaker output and the TNC or soundcard input can make some improvement, but unfortunately, that will not prevent a strong adjacent signal from causing the receiver’s AGC circuit to reduce gain, often to the point where the desired signal disappears. The best solution is to upgrade to a transceiver which has FSK mode built in, AND which allows you to select a narrow filter while in that mode.



It’s easy to remember the HF band plans for RTTY. Most activity will be found between 80 and 100 kHz up from the bottom edge of the band, except for 80 meters which goes an additional 40 or 50 kHz higher, and 160 meters. 160 meter RTTY activity is rare, but when found, it is usually between 1800 and 1820. Avoid the CW DX window between 1830 - 1840. At present, there is not much activity on the WARC bands, although 30 meters can be active at times.
Here is where you will find most of the RTTY activity:
80 meters: 3580 - 3650 (3520 - 3525 in Japan)
40 meters: 7080 - 7100 in the US (see note below)
30 meters: 10110 to top of band
20 meters: 14080 - 14099 (avoid the NCDXF beacons at 14100)
15 meters: 21080 - 21100
10 meters: 28080 - 28100

RTTY allocations for 40 meters vary greatly all over the world. In the US, RTTY is permitted between 7000 and 7150, although most US activity is between 7080 and 7100. DX activity is often found between 7020 and 7045. The ARRL promotes 7040 as the RTTY DX calling frequency, but the CW QRP’ers use it as their calling frequency too. Be a gentleman!

For US operators, remember that RTTY is not allowed in the phone portions of the HF bands except on 160 meters, where it is legal anywhere in the band.



Chasing DX on RTTY is highly popular with the RTTY crowd. As you might guess, 20 meters is the premier DX band for RTTY, and most rare DX stations and especially DXPedetions operate on 14080. Just as with CW or phone, if the DX is calling CQ and getting no answers, you can feel safe in calling him right on his frequency. If things are busy however, he will often work split, which means you should call him on a different frequency, usually 2-10 kHz higher. He will say “up 2-10″ or something similar at the end of his transmission, and that’s your clue. Your transceiver owner’s manual will explain how to do “split”.



RTTY contesting is a passion with a lot of hams. There are more than two dozen major RTTY contests each year and when they are on, the bands will be full! Even if you don’t care to compete, it’s a great way to pick up new states or countries. Many of the rare DX stations are serious contest operators. A list of RTTY contest times and rules can be found on the web all.

  • Contesters are in a hurry, of course, so please send only what is required by the contest. Plenty of time for chatting after it’s over.

    If you get serious about RTTY contesting, you will probably want to get a program designed specifically for it. The major ones are WriteLog for Windows (not free) and RTTY by WF1B for DOS (free).



    Ok, you’ve learned a lot and you’re ready to get on the air! For your first time on RTTY, try the 20 meter band. 20 has the lion’s share of RTTY activity and you can usually find someone, day or night. Try calling CQ between 14080 and 14087 kHz. A typical RTTY CQ would go like this: CQ CQ CQ CQ CQ CQ DE W7TI W7TI W7TI AR PSE K
    Practically all RTTYers add the “PSE” at the end. Just a friendly touch. Some will add their name and QTH, some will add the time and date. You’ll find a lot of variety and it’s all ok - just get on the air and try it out!
    If you’re familiar with CW procedures, you’ll be right at home with RTTY. RTTYers use most of the Q-signals, as well as DE, K, KN, and most of the CW abbreviations. And if you accidentally find yourself “upside down”, don’t get embarrassed - we’ve all done it! RTTYers are some of the nicest people you’ll ever meet. Things like jamming, profanity and rudeness are almost unheard of.



    In spite of the newer digital modes like PSK, Pactor, G-Tor and others, RTTY remains the favorite of contesters and DXers. RTTY does not use error correction, handshaking, or synchronizing, all of which slow things down. When quick back-and-forth exchanges are important, RTTY is the mode of choice. Roundtable discussions and nets that would be difficult or slow with other modes are a natural for RTTY. RTTY is likely to be around for a long time to come.
    I hope this has answered some questions for you.

    CR: A Carriage Return inserted in your “exchange” buffer, prior to, and after the “sent” data will allow the receiving station to view your “exchange” on a new line, not mixed in with the “alphabet soup” that appears during receive! You should insert “the name of the contest” in place of “contest” in the data line!
    Example: “CR” CQ CONTEST DE K4WW K4WW CQ “CR”
    CQ: Placing a CQ after your callsign, when calling CQ, will allow tuning stations to immediately know you are calling, not answering another station!
    Example: See above!
    Call Sign: When calling a CQ’ing station there is no need to send their call, just send “CR” DE your call your call ” CR”! The calling station already knows their call and, especially in “less than good” band conditions, the first data sent is usually printed well, then all the following is “alphabet soup”!
    Example: “CR” DE K4WW K4WW “CR”
    FT-1000MP: You need to set radio menu setting 6-1 to ‘reverse’ so that your RTTY signal is really ‘normal’
    What filter settings to use for RTTY (250Hz or 500Hz for most). There are a couple of sub-points here:

  • in AFSK to use the settings you have to use the ’shift’ on your radio in order to make the filter bandwidth
  • in FSK the filter settings are built in

    Unshift-On-Space - To Use It or Not?

    USOS is not the easiest concept to understand. Here’s another way of thinking about it: The transmitting station and the receiving station must always be synchronized regarding LTRS case and FIGS case. When signals are strong this is no problem, but when sigs are weak or covered by QRM/QRN/QSB often the synchronization is lost. This is how we get those TOOAPPQAPPQ messages. Think of the space character as a “synchronizer”. With USOS ON (the default in most TNC’s), every time a space character is sent, the transmitter and receiver are BOTH re-synchronized automatically. This happens with EVERY space character, not just in the exchange. For example, when you send 599-001-001, the synchronizing is done only once - at the start of the transmission, just before the “5″. On the other hand, if you send 599 001 001, the synchronizing is done three times - once before the “5″ and once before each “0″. Your chance of receiving the correct FIGS character has improved significantly.

    So, here’s a suggestion for folks who prefer using the hyphens: Set up a separate F-key with ONLY the significant part of the exchange, and do it WITH SPACES. For example, 001 001 001 001. Use it only when asked for a repeat. In this example, the “synchronizing” space character is sent four times, greatly improving the chances of correct reception. Use this only when requested and it should not impact your QSO rate/hour much at all, and I think you’ll find your repeats are reduced noticeably.

    The key to the issue is a type of operation called unshift-on-space (USOS). USOS is used by most TNC’s by default, but there is a little quirk of contesting which can make it ineffective. Here’s a little background: As you are probably aware, the Baudot character set uses a figures shift character and a letters shift character to change between letters and figures and other punctuation. This is needed because Baudot only uses five bits and five bits can only display 32 characters - not enough for all the letters, numbers and punctuation. For example the letter Q and the number 1 are identical in Baudot - except the 1 is preceded by a figures shift character. This is a non-printing character of course; you don’t see anything on your screen. It is merely an instruction to your receiver to treat what follows as a figures-shifted character instead of a letters-shifted one. Likewise, when you return from sending numbers to sending letters, a letters-shift character is sent. This is how your receiver keeps things straight. The problem comes about when some QRN, QSB, QRM or whatever causes a loss of the shift character. Baudot was originally devised for wired communication where this is not a problem. With radio, unfortunately it is.
    In an attempt to correct the problem, USOS was devised. What happens in your receiver is that when a space character is received, the receiver resets itself to letters-shifted characters. This works because your USOS transmitter knows that after sending a space character, if the next character is a number, the figures shift character has to be sent first. The reasoning behind this is that letters are much more common in ordinary conversation than numbers are and it works quite well for ragchewing… but contesting is a little different. Often in a contest exchange, what follows a space is a number, not a letter. The problem (follow me closely here) happens when the transmitting station does not send a space before the number, but rather sends a hyphen. For example, 599-001-001. If the ORIGINAL figures shift character is lost, the receiver will print TOOAPPQAPPQ, the hyphen being a figures-shifted “A”. In the same situation, but with a space in place of a hyphen the receiver would print TOO 001 001. The missing ORIGINAL figures shift character causes the 599 to print as TOO, but the subsequent (and more important) serial number prints correctly, thanks to USOS. The reason people use hyphens is that the transmission goes faster - a hyphen character takes the same time interval as a space, and (here is why it’s faster) the hyphen is also on the figures shifted set so therefore does not require sending another figures shift following the reset to letters shift caused by USOS.
    I don’t blame you if you have to re-read that a few times. It is anything but readily apparent. To summarize, hyphens make the transmission faster, but spaces along with USOS make reception more accurate when QRM, QSB or QRN is present. I can understand the folks who want a fast transmission - in a contest, faster is better IF IT’S ACCURATE. But if it isn’t accurate, a lot of time is wasted asking for repeats. Anyway, I prefer accuracy, so you will always see my exchanges with spaces. For the folks who prefer speed, may I suggest setting up an F-key which repeats only the significant part of the exchange? You’ll be using it more than you would otherwise. :-)
    Now the contest is finished and you will want to submit your log to the proper contest manager. These may be found at http://www.rttyjournal.com/contests/index.htm along with the rules, recent year scores and email addresses for log submission. The following article written by Eddie, W6/G0AZT will give you step by step instructions to insure that your log is correctly formatted for submission.


    Submitting Contest Logs and Files for 2001 and Onward

    By Eddie Schneider, W6/G0AZT

    There are generally four options for submitting logs for the major RTTY contests. Please follow closely these log submission rules for the specific contest. The options, in order of preference, are as follows:

    1. Electronically, using the Cabrillo format.
    2. Electronically, using the relevant files produced by your logging software, e.g. .all and .sum.
    3. By mail, using only a correctly formatted and packaged 3.5 inch diskette with the information specified in alternatives 1 or 2 above. Note, larger diskettes will not be accepted.
    4. By mail, on paper, either hand written or computer generated. However, if the log contains more than 100 entries in a CQWW contest, this option is not available; only options 1,2 or 3 may be used.


    Electronically Submitted Files

    The Cabrillo * format is here to stay. From November 2000, the ARRL accepts ONLY this format for electronically submitted logs. Both RTTY CQWW-DX and CQWW-WPX now require this format for any log produced by your logging software and containing more than 100 QSOs. BARTG Sprint, BARTG HF, SARTG, SCC and EAWW will also be requesting this format.

    As more and more contest organizers realize the simplicity of a Cabrillo formatted log, they will no doubt follow suit in the not too distant future. If your favorite contest logging software does not support the Cabrillo format yet, get in contact with the author. An alternative would be to purchase a converter utility and/or log checking software from WT4I #

    One of the main features of a correctly formatted Cabrillo log is that ALL the contest-specific data required is written to just ONE .log file.
    There is no need to send a summary, dupe or multiplier sheet and generally, separate band files are no longer required either. Besides simplifying the entire process of log submission for the entrant, Internet bandwidth is reduced and assuming that the checkers have appropriate log checking software, their lives are made a whole lot easier.

    Here is an example of how much time can be spent by a contest manager obtaining the correct files for just one contest. For WPX2000, I received 533 logs via e-mail. I generated over 1300 contest related e-messages in a five-week period. Deducting the 533 confirmation messages plus approximately 100 other e-mails, passing logs to the other two log checkers, leaves 360-odd e-mails asking entrants for missing files, incomplete summary sheets, unreadable .bin, .wl, .xls files etc. It is NOT the log checker’s responsibility to convert these files into a readable format! The onus is on the entrant to know how to produce the required files using his preferred logging software. In other words, if in doubt, read the manual :-)

    Contest managers, usually unpaid, are trying to reduce the delay in posting the results, so you can appreciate that spending time and effort having to ask for missing data could be well spent actually checking the logs and finalizing the results in a timely manner. Log submission deadlines are also being reduced in an effort to expedite the results.

    Sophisticated log checking software # is now available to any contest manager interested in making his life a lot easier. This same software is also available to contesters who would like to thoroughly check their logs before submitting them.

    If you operate in a single band class but make contacts on other bands to relieve boredom or help out friends, please submit CHECK logs for those bands. If you don’t submit a check log for those other bands, the other station(s) you worked on your non- competitive band, will lose credit for
    those QSOs. So lets get down to the nuts and bolts of preparing and submitting an electronic log to managers who accept and/or require the Cabrillo format.

    1. When converting your log to Cabrillo make sure that you complete FULLY and ACCURATELY the Cabrillo Header with the required information for the specific contest.
    a. Call sign used. In the case of multi ops, all call signs of operators and names of persons involved in the contest, even the tea lady:-). For those of you using special calls, add your personal call sign in the appropriate field.
    b. Class of operation, e.g. Single op, all band, high or low power where appropriate.

    CAUTION. Be very careful when selecting your category. If your Cabrillo log indicates SOABH expect to see your results in THAT category when the final results are published, even if you actually operated as SOABL, SB or SOA. Any unnecessary summary sheet with a different chosen category from that recorded in the Cabrillo header will be ignored.
    If the contest does not have ’special’ categories like Over 50, TB wires etc., leave those entries blank.
    c. Claimed score.
    d. Your name and FULL postal address. Adding an e-mail address in the ‘Soapbox’ field would be helpful in case of queries.
    e: The name of the contest that the log refers to. This may seem obvious but we’ve had contestants send SSB or CW logs for CQWW RTTY!
    f. For non US/VE entrants, select “DX” for the ARRL Section.
    g. US/VE entrants select the appropriate state or province. For ARRL sponsored contests, select your US section or VE province/territory abbreviation.

    Once you are satisfied that all the relevant information is accurate and has been included in the Cabrillo Header, now comes the part that many entrants have a hard time with, naming their files correctly in order to submit them via the Internet.

    Contest managers are not at all interested in what you actually named your files on your hard drive. Names like QWWRTTY2000.x, WPXSOABL.x and so on, have little meaning and only cause confusion and possible errors if the manager has to rename them. So, number one priority is to rename all the files you intend to send, with the CALL SIGN you used during the contest. For example, XX0XXX.log, XX0XXX.sum
    The second priority is to zip or ‘pack’ the files. By doing this, your original file format has less chance of being corrupted in transit.
    Thirdly, make the subject line in your e-mail as meaningful as possible. If lots of files received by the manager are called CQWW2001, there is a good possibility that one or more logs will be accidentally over-written. Been there, done that :-) So please use your call sign in the subject header.
    Including the entry class would also be appreciated, e.g. XX0XXXsoabl, XX0XXXsoa etc.

    Finally, do not forget to include your zipped file as an attachment to the electronic submission!



    Copyright © 2009 - 2015 IW9HMQ| All Rights Reserved

    Design by Mauro IW9HMQ | Modified by Team IW9HMQ | Powered by ARUBA.it | W3C XHTML 1.0 | W3C CSS 2.0


    Il sito www.iw9hmq.com utilizza solo cookie tecnici, rispetto ai quali, ai sensi dell'art.122 del codice privacy e del Provvedimento del Garante dell'8 Maggio 2014, non è richiesto alcun consenso da parte dell'interessato.

    - Coockie Policy -  /  - Direttiva EU