Short answer: Stray RF from your own transmitter can get into keyboards, mice, USB cables, sound-card interfaces and computer power supplies. The result is odd behaviour: a dead keyboard when you transmit, repeated characters, a frozen logger or a sound card that clicks. Some of these faults put wrong characters into the log without you noticing. Test everything at full power on every band before the contest, fix the worst offenders with ferrites and better cabling, and keep an eye on the log for strange entries.
What RF in the shack really means
When you transmit, a small part of the power does not go where you want it. It travels on the outside of coax cables, on mains wiring and on any long cable in the shack. Computer equipment is full of cables that act as antennas: USB leads, headset cables, keyer lines, network cables and monitor cables. A strong field induces a current in these cables, and the electronics at the end of them may treat that current as a signal.
Most contesters have seen the classic symptoms. The keyboard types a few extra letters when you press the PTT. The mouse pointer jumps. The USB interface drops out and the logger loses the radio. The paddle keyer sends dots by itself. On some bands the problem is much worse than on others, because a particular cable happens to be close to a resonant length on that frequency.
Why it matters for the log
Most RF problems are loud and obvious, and you fix them at once. The dangerous ones are small. A keyboard that adds a single character to the callsign field now and then will create busted calls that look like ordinary typing mistakes. A logger that resends a message by itself can create a QSO line you did not intend. A computer that restarts in the middle of a run may leave a short gap in the log and a few lost QSOs.
When you look at your log after the contest, these faults leave traces. You may find callsigns with an unlikely extra letter, an exchange field with repeated digits or a short block of QSOs where the times jump. A page about busted callsigns helps you recognise ordinary causes, but if you find the same odd pattern several times, think about RF as well.
Find the problem before the contest
The best test is a deliberate one. Sit at the operating position with everything connected as in the contest, and open the logger. Transmit at full power, in the mode you plan to use, on each band you plan to work, and watch the computer while you do it. Type in the callsign field while transmitting. Move the mouse. Watch the radio control, the sound card level and the keyer. Do this on 160, 80, 40, 20, 15 and 10 metres, and on every antenna you will use, because the field in the shack changes with the antenna and its feed line.
- Note which band and antenna cause trouble, not only that something went wrong.
- Try a different keyboard or a different USB port; a cheap wireless dongle is a frequent weak point.
- Test with the headphones and the microphone in use, because audio cables are good receivers of RF.
- Write the findings into your station notebook so the next contest starts with a known state. A short station notebook is useful for exactly this.
Practical fixes that usually help
Start with the cheap ones. Clip-on ferrite cores on USB, audio and keyer cables, close to the equipment they connect to, cure many problems. A few turns of the cable through a larger ferrite ring is stronger than one pass through a clip-on. Use short, good-quality cables, and avoid long loops lying on the desk. Keep the transmitting antenna cable and the computer cables apart, and cross them at right angles where they must meet.
A common-mode choke on the feed line, close to the antenna and again where the line enters the shack, reduces the current on the outside of the coax. Good grounding of the equipment, and a single bonding point rather than several random ones, also matters. Powered USB hubs sometimes help, and sometimes make things worse, so test rather than assume. If one band is the problem, a different antenna position or a different feed arrangement may help more than any amount of ferrite.
Sound cards, interfaces and radio control
Digital modes and many CW and SSB setups depend on a computer sound card or a USB interface between the radio and the logger. These devices are sensitive to RF in two ways. The audio path can pick up the transmitted signal and produce buzzing or distortion, and the data path can drop out for a moment. In RTTY, a distorted audio signal can create decoding errors that look exactly like copying mistakes. In SSB, a voice keyer or recorded messages that pass through a noisy interface sound poor to the other station, who then asks for repeats.
Test the interface separately from the keyboard. Send a recorded message at full power and listen to the monitor. Check that the radio control link stays connected during a long transmission, for example when you send a long CW message or call for a minute on a quiet band. A control link that drops for a second can leave the radio in the wrong mode or on the wrong frequency, and the logger then records a frequency that does not match the QSO. The same applies to the band information that the logger reads from the radio: a wrong band in a QSO line is an error that is hard to see afterwards.
If you use a laptop, remember that its internal wiring and the charger can also pick up RF. A laptop on battery behaves differently from one on a switching power supply, and some chargers produce noise on the receive side as well. Try the laptop with and without the charger, with the charger moved, and with a ferrite on the charger cable. Write down what changes. Many contesters find that one simple change, such as moving the charger or replacing a cheap power supply, removes a problem that months of ferrite experiments did not touch.
Protect the log while you fix
You cannot always cure RF in the days before a contest. In that case, reduce the damage. Keep the logger on a stable computer with a good power supply. Switch off sleep and automatic update features. Use a keyboard cable with a ferrite, or a different keyboard that you have tested. If a band is bad, plan to operate there at lower power or from a different position.
Frequent backups are the second line of defence. A restart in the middle of the contest should cost you a minute, not an hour. The article on log backup during a contest describes simple habits that work with any logging program. Combine them with a regular look at the last few QSO lines: it takes a few seconds, and it is the fastest way to catch a glitch that adds characters.
Check the log for traces afterwards
After the contest, read the log with a few specific questions in mind. Are there callsigns with doubled letters or unusual extra characters? Are there QSOs where the exchange does not match the band or the country? Are there time gaps that match a computer restart? The time gaps in your log often show a computer problem more clearly than anything else. If you see such a pattern, check which band it happened on. That tells you where to look in the shack.
It is also worth looking at the statistics by hour and band. A band where the rate falls for no reason, or where errors cluster, is a good candidate for an RF problem. The numbers do not prove the cause, but they tell you where to test first. If you use a log checker, a flagged callsign with one extra letter that you are sure you did not copy should make you think about the keyboard as well as your ears.
A short pre-contest RF checklist
- Connect the station exactly as in the contest, including headset, keyer and interfaces.
- Transmit at full power on every band and antenna, and watch the computer and the logger.
- Type in the log fields while transmitting and look for extra or missing characters.
- Add ferrites to the cables that react, one cable at a time, and test again.
- Record the result in your notebook, with band, antenna and fix.
- Back up the log on a schedule and look at the last QSO lines regularly.
This takes an hour or two, and it is much better than finding the problem at three in the morning on the second night of a 48-hour contest.
Related reading
The bottom line
RF problems are usually fixable, but only if you look for them. Test at full power on every band, add ferrites where something reacts, keep backups and read your log for strange characters and time gaps. A glitching keyboard is not only an annoyance; it can quietly put errors into your log. For a fuller routine, see the FAQ of this site for what a log check does and does not look at.
FAQ
How do I know that a problem is RF and not a faulty keyboard?
If the problem appears only while you transmit, and changes with band or antenna, RF is the likely cause. A faulty keyboard misbehaves all the time.
Do ferrites always work?
No. They help with many common-mode problems, but the type, the number of turns and the position matter. Test after each change.
Can RF change a callsign in my log without me noticing?
It can, if a keyboard or interface adds or repeats characters. That is why a regular look at the last QSO lines is a good habit.
Is lower power a valid fix?
For a single band it can be a temporary workaround, but a proper fix on the cables and the feed line is better for the whole contest.
Should I test every band even if I only plan to use two?
Test every band you may use, including those you only visit for multipliers, because a problem there can appear at the worst moment.



