Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Mod_Chrissy

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Chrissy

  1. One thing the multiplier math doesn't capture is how much antenna capability determines where the break-even point sits. If a band gives you a strong signal into the multiplier-rich areas, running there is productive and you'll be reluctant to leave it. If your antenna is weak on that band, you spend more time calling and less time collecting QSOs. For contesting, the pattern and height of the antenna often matter more than headline gain. A few antenna considerations that bear on operating decisions: Low bands: The receive side usually limits you more than the transmit side. A quiet receive antenna (Beverage, flag, or similar, depending on your space and noise environment) can let you hear multipliers you'd otherwise miss, which matters when you're S&P-ing on 160 and 80.High bands: A stack of two or more yagis lets you choose a takeoff angle that fits the path. Having both a high and a low antenna available can matter a lot when the band is marginal.Rotation and switching: If turning the antenna takes a long time, you'll avoid working stations that need a different heading, which reduces your effective multiplier opportunity. Fixed or quick-turn arrays that cover your most important directions can beat a larger but slower setup for rate.Endurance matters just as much, and it affects the decisions above. A 48-hour contest isn't a sprint, and the usual mistake is spending the early hours at full intensity, then making poor choices and logging errors later. Some practical habits: Plan off-time for periods when propagation will be bad or when your rate is likely to be lowest, rather than taking breaks at random. Resting during a dead hour costs far less than resting during a rate peak.Keep water and food at the operating position so you don't leave the desk during a good run.Use a voice keyer or CW keyer with well-tested messages to reduce vocal and hand fatigue. Check the audio levels once and leave them alone.Watch for signs of fatigue in the log: busted callsigns, repeated exchanges, and dupe contacts you didn't notice. Those errors usually show up before you feel tired.Ergonomics count. Chair height, monitor position, and headphone comfort sound minor, but they add up over a full weekend.A question back to the original post: for those who use packet or skimmer spots heavily, how do you keep your bandmap from becoming noise? Filtering by needed multipliers or by spot age seems essential, but I'd like to hear how people set it up.
  2. For the "listing and repeater disagree" question, I would work through it in a fixed order instead of guessing. First, confirm you are on the right output frequency and listening for the repeater's own audio, not just any signal. Second, check the offset direction. A reversed offset is easy to do and gives you silence or a hit on the wrong channel. Third, try the tone encode and decode settings separately. Many radios let you set encode only, and a repeater that transmits a tone of its own may need a different value on the receive side. Fourth, if DCS is listed, try both polarities. Fifth, listen to the repeater's identification if it has one, and look for a club page that gives the current tone. It also helps to check simplex before blaming the repeater. If you can hear a nearby station on the repeater output but they cannot hear you, the problem is almost certainly on your transmit side: wrong tone, wrong offset, or low power into a weak input. Many repeaters hear a handheld far worse than they can be heard, so try a better antenna or more power before assuming the machine is down. For DMR, the checklist grows: color code, timeslot, talkgroup, and whether your DMR ID is registered. D-STAR needs the right callsign fields in the radio. With either, a repeater that is on the air will still stay silent for you if one setting is wrong. Both usually have a club or network page with a template codeplug or settings, and that is a better starting point than copying a stranger's file.
  3. Good outline. I'd add one point on FT8 and the Fox/Hound mode, because the etiquette is quite different from CW/SSB. In WSJT-X, Hound mode is meant for calling the Fox, and Hounds are supposed to transmit above roughly 1000 Hz while the Fox transmits below it. If you call the Fox on its own frequency you can make it harder for the Fox to decode anyone. Also, once the Fox replies to you, follow the sequence in the software and don't keep calling, as repeated calls waste a slot that another station might have used. If the operation has published instructions, those override general habits, so read them before the first opening. On spots, the thing to be careful about is the "up" instruction. A busy cluster can carry spot comments that conflict with each other, like "up 1" and "up 5-10". Listen for the DX saying it himself. If he doesn't announce on voice, he'll often tell you in the CW exchange or in the next announcement.
  4. One thing that helps newer activators is to check the park page before you go: the boundaries, any access restrictions, and whether the area has cell coverage. Coverage matters because the app and spotting depend on it. If you can't spot, you can still call CQ POTA, but it can take longer to reach 10 contacts. You can download the park info beforehand, and it's worth writing down the exact reference on paper in case your phone dies. For slow stretches, don't spend all your time on one frequency. A change of band can bring in a different group of hunters. If you're on SSB, run a clear CQ and state the reference so people hear it in the first call. On CW the pace can be quicker, and some hunters are used to working activators as fast as possible.
  5. One thing to look at before choosing the ESP32 for the rotator or the switch is how you will use Wi-Fi. On the ESP32, ADC2 can't be used while Wi-Fi is active, so put analog inputs such as the rotator pot feedback on ADC1 pins. For the rotator, also design for the wrap-around region. Most pot-based rotators have a dead spot or an overlap near the end of travel, so the firmware needs a clear policy for what "north" means near the stops, plus a timeout that cuts the motor relay if the reading doesn't change after a command. That protects against a failed pot or a jammed rotator more than any amount of clever PID would. For the Pi side, Direwolf is a good fit and you can expose KISS over TCP (port 8001 by default) or AGW (8000) to client software. Keep its audio path separate from your control wiring, though. If you share a USB hub or a ground between the sound interface, the rig and the microcontrollers, a ground loop can show up as hum or noise in the audio. An isolated USB audio interface or transformer coupling on the audio lines is usually cheaper than chasing the noise later. If you add a Si5351 later for a VFO, beacon or test signal, remember its outputs are square waves. They need a low-pass filter before they go anywhere near an antenna or a receiver, and the I2C wires should be kept short and away from the PA.
  6. On repeaters and operating practices, picture how it works on the air and the questions get easier. A repeater listens on one frequency (its input) and retransmits on another (its output). Your radio needs the right offset: commonly 600 kHz on 2 meters and 5 MHz on 70 cm. Many repeaters also require a CTCSS (PL) tone on your transmitted signal before they will open up. If you can hear a repeater but it won't respond to you, the first things to check are the offset direction and the tone setting. Simplex means talking directly radio to radio with no repeater, and 146.52 MHz is the national FM simplex calling frequency. Know the identification rules cold: give your call sign at the end of a communication and at intervals during a longer one, not just once when you start. The pool also covers courtesy and procedure, like listening before you transmit, keeping transmissions short on busy repeaters, and what to do when you hear a distress call. Don't skip the safety and RF exposure sections, even though they feel like common sense. The questions are specific. RF exposure limits depend on frequency, power, the antenna, how long you transmit, and how far people are from the antenna. For electrical safety, think of fusing the hot lead, grounding, keeping antennas and masts well away from power lines, and not working on antennas during a thunderstorm. These are some of the easiest points on the test if you've read the explanations. For practice tests, do them by subelement first so you can find weak spots, then do full timed runs. Reread the explanation for every question you miss. Many study guides and practice sites provide those explanations, and they're what makes the logic stick.
  7. From the hunter side, the most useful thing an activator can do is make it obvious which references are active. If you are claiming a combined activation, put both references in your spot comment and say both at the start of the CQ, not only at the end. Many hunters are filtering for one program and will skip a station that is vague about which one it is. For awards, I would read the current WWFF award and diploma pages and note which ones are for hunters, which are for activators, and what each requires, such as numbers of references, countries, or bands and modes. Then decide whether you want to work toward them deliberately or just let them accumulate. Don't copy a requirement from a forum post, including this one, without confirming it on the official pages. For record keeping, it helps to keep your own log of KFF and other national references you have worked, even if the award system also tracks them. It makes it easier to check for errors, such as a reference typed wrongly or credited to the wrong park, and to see which references you still need. A last point on reference lookups: names of parks and reserves can be similar, and a WWFF reference and a POTA reference for the same place may have different boundaries. Check the maps for both, set up inside the overlap, and mention any limits in your spot so hunters know what to expect.
  8. For the order of operations, I'd model first, then build, then measure at the feedpoint. In EZNEC, define the wire with the right diameter and material, set the ground to something realistic (not perfect ground), and put the antenna at the planned height. Pay attention to segmentation. Too few segments on a wire is a common cause of nonsense results. Before trusting the numbers, run the average-gain test. A value near 0 dB suggests the model geometry and segmentation are well-behaved, while a large deviation means something is wrong in the model. MMANA-GAL is a good second opinion. It is free and based on MININEC, and it is handy for quick comparisons and for optimizing dimensions. Its ground handling is different from NEC-based tools, so I wouldn't treat absolute numbers as gospel when the antenna is low over real ground. If two different modeling engines agree on the trend (say, resonance moves down by X kHz per inch added), that is more trustworthy than either absolute value. Neither program knows about the tree, the house, the roof gutters, or the wet soil, so the model won't predict resonance to the kilohertz. Use it to understand the sensitivities: how much the inverted-V angle changes the feedpoint impedance, what 10 percent shorter ends do, how a 3 m height change shifts the pattern. When measuring, use an antenna analyzer or a NanoVNA, calibrated at the end of the cable you use. Measure at the feedpoint if you can. If you measure through a length of coax, loss makes the SWR look better than it really is and the reactance reading is rotated by the cable. Resonance is where the reactance X crosses zero, and that isn't always the SWR minimum, especially when the feedpoint resistance isn't 50 ohms. Sweep the whole band in steps and note R and X, not just SWR. Then trim in small amounts, one end at a time, and keep the ends symmetric. If you later build a vertical, the same method applies. A quarter-wave is about 234 / f(MHz) feet, and the ground system is the part that decides efficiency. Several elevated resonant radials usually beat a few short ones lying on the ground. A ground-mounted base needs many more radials. An elevated, drooping-radial design is a natural fit with your fiberglass pole.
  9. The flow is sound. The biggest weak point is the master log, so I'd treat it as an explicit decision. On CAT: a serial port can only be opened by one program at a time. If WSJT-X, N1MM+ and Log4OM are all configured for COM5, whichever starts second usually fails or behaves oddly. Practical options are to run only one of them against the radio at a time, to put a rigctld instance in front of the radio and point the programs at it, or to use a virtual serial port splitter. Everything also has to agree on baud rate, data and stop bits, CI-V address if it's an Icom, and the handshake settings. One more thing to check is DTR and RTS. If they are used for PTT or CW keying, an unintended state on a shared port can key the transmitter. In WSJT-X, set PTT to CAT or VOX deliberately, and check what the other programs do with those lines. On mode mapping: before relying on the chain, export a handful of test QSOs in each mode (CW, SSB, FT8, FT4, RTTY) as ADIF and look at the raw file. Check MODE, SUBMODE, BAND, FREQ, STATION_CALLSIGN, OPERATOR and MY_GRIDSQUARE. If the grid or station callsign is blank, that's often what breaks LoTW matching later. Importing the file into a scratch database before touching the real one costs little. On Cabrillo: you're right. It's a scoring and submission format. A Cabrillo file has a header (CALLSIGN:, CATEGORY-OPERATOR:, CATEGORY-BAND:, and so on) followed by QSO: lines whose columns depend on the contest. Fields like grid, comments and your own notes don't survive. Dupes may appear as X-QSO: lines depending on how the software writes them. Always export ADIF from the contest database for your master log, and generate Cabrillo only for the sponsor. Always read the sponsor's rules for the file name, the submission address or upload page, the deadline, and whether a robot sends a confirmation. Those details vary by contest and change over time, so don't trust last year's notes. Most sponsors also publish a Cabrillo checker or accept the file with a log summary, so run your file through that before submitting.
  10. until

    Texas State Parks On The Air combines POTA-style park activations with Field Day operations. Each April, operators set up in state parks across Texas to practice field skills and make contacts. The 2027 contest period starts Friday, April 16 at 7:00 PM CDT and ends Sunday, April 18 at 7:00 PM CDT.Location: State parks across Texas, USA (the announcement gives no single venue or street address) Organizer: Texas State Parks on the Air (TSPOTA) Source: Event information
  11. On SWR, it helps to remember that the reading depends on the entire path, not only the antenna. If you measure at the radio end with a long run of thin coax, the loss in both directions pulls the measured SWR down toward 1:1, so a damaged antenna can look better than it is. If the reading seems too good for a cheap antenna, test it at the antenna end or with a known-good short jumper. An analyzer sweep tells you more than a single-frequency check, since it shows where the resonance is and how wide the usable band is. For satellites, I'd keep it simple at first. For FM birds, a small hand-held yagi on 2 m and 70 cm is workable, and you can rotate it to cope with polarization changes. If you want a fixed setup, a crossed-yagi pair with circular polarization is more convenient, but you need elevation and azimuth control, correct phasing, and low-loss cable on the 70 cm side. The 70 cm path is usually where cable loss hurts most, so that is a good place to spend on better coax. Also, because the satellite moves, Doppler shift is a real factor: you'll be retuning during the pass, especially on UHF, rather than parking on one frequency.
  12. The biggest source of confusion is the region digit. Your sequential call follows your mailing address, but vanity doesn't. Under the vanity rules you can request a call with any region digit, whether or not you live there, as long as you're eligible for that format. The exception is the special territorial prefixes (KH, KP, and similar). Those are tied to location, so they're a different story. A related misconception is that your callsign tells people where you are. It doesn't, since people move and vanity calls ignore geography. Regarding operating away from home, the FCC doesn't require a portable indicator for domestic operation. Many operators still add one, such as /7 or /P, when it helps, but it's optional unless you're operating under a foreign reciprocal arrangement that requires one. Identification itself, including the rules on how often to ID, is in §97.119. For lookups, treat ULS as the authoritative source. Third-party callbooks are convenient, but they pull from ULS on their own schedule and sometimes carry user-entered data that doesn't match the FCC record. If a callbook says one thing and ULS says another, go with ULS. The grant date and expiration are shown there. The call will stay on the record through the grace period after the license term, but you can't transmit during the grace period. One more practical point: a license is not renewable forever just by ignoring it. Renew inside the license term if you can. After the grace period it's gone, and you'd be starting over, probably with a different call.
  13. One tip on gain: use a spectrum view with a stable noise reference, not the waterfall colours. Waterfall palettes and range settings hide the changes you need to see. With the antenna connected, find a spot with no signal, then change the gain and watch what the noise floor does. If the floor climbs about as much as the gain, the system is noise-limited by the antenna or the environment, and you gain little from more amplification. If the floor barely moves at the lowest gain settings, the receiver's own noise dominates and a bit more gain or an LNA is justified. Overload shows differently. Signals appear in places they shouldn't, they change with gain in an uneven way, or a strong carrier produces copies at regular spacings. A simple test is to add a few dB of attenuation. A real signal drops by that amount, while an intermod product usually drops faster. On the FM notch, a broadcast-band notch filter can make a visible difference on an RTL-SDR for HF, VHF air band and similar uses, but it does nothing for overload from strong signals inside the band you want. In that case a bandpass filter for the band is the better tool.
  14. Start by separating the two layers. FCC Part 97 is the law. It sets which frequency segments each license class can use, which emission types are allowed, and power limits. The ARRL band plan is a voluntary agreement about how to share the space inside those segments. Nobody is required to follow it, but ignoring it is how you end up parked on a net's frequency or an FT8 watering hole. The legal limits are always the outer boundary, and the band plan is the etiquette inside them. On privileges by class: Extra has all amateur privileges. General has most of every HF band, but the Extra-only slices sit at the lower end of the CW/data and phone sub-bands. Technician has only limited HF: CW on parts of 80, 40 and 15 m, and CW, data and SSB on parts of 10 m (28.000-28.500 MHz), limited to 200 W PEP. Technicians also have all privileges above 50 MHz. General phone on 75/80 m starts at 3.800, on 40 m at 7.175, on 20 m at 14.225 and on 15 m at 21.275. 30 m is CW and data only. Check the current ARRL chart or Part 97.301-97.305 for exact segment edges, since I'm giving them from memory. For band edges, think about where the signal sits, not where the dial reads. An SSB signal occupies roughly 2.4-3 kHz on one side of the suppressed carrier, and that side depends on the sideband. By convention, LSB is used below 10 MHz and USB above. On 75 m with LSB, the signal extends below the dial reading. A General dialed to 3.800 would have energy below the General phone segment, so keep the dial a few kHz higher. On 20 m with USB, the signal extends upward. At the top of the band, a dial of 14.350 would put energy outside the allocation, so stay a few kHz below it. The same applies to the bottom of a CW/data segment, where your emission needs to stay entirely inside the segment. Give yourself a margin, because rig dial calibration and filter skirts are real. For digital, the usual HF FT8 dial frequencies are around 1.840, 3.573, 7.074, 10.136, 14.074, 18.100, 21.074, 24.915 and 28.074 MHz. These are conventions, not rules, and they sit inside the digital portions of each band. Check that your mode and bandwidth are allowed in whatever segment you choose, because the FCC has changed its data rules in recent years.
  15. One practical addition for activators: decide your logging method before you leave the house. Paper works if you transcribe it that evening and double-check callsigns, times, and the park reference. Logging software is easier for ADIF export, but check your field settings so that the park reference lands where POTA wants it. Fixing a batch of wrongly formatted entries after a long day in the field is tedious. For hunters, there is no need to wait for a spot to be "clean". If you hear a station running a pileup, listen first, work out whether they are calling CQ POTA or working by number or by region, and then give your call once, clearly. Long repeated calls don't help anyone. Hunter logs are also easier to match later if you keep the activator's call, park, band, mode, and UTC time.
  16. I'll take the remaining items. RF exposure is §97.13(c). Whether you must do a routine evaluation depends on band and power thresholds in the FCC's RF exposure rules. Those thresholds vary by band, and the duty cycle of the mode matters. SSB, CW and FM do not average the same way. If you are over a threshold, you must show compliance with the maximum permissible exposure limits. That can be done with calculations, a measurement, or the FCC's guidance in OET Bulletin 65 and its amateur supplement. Even when no routine evaluation is required, you are still responsible for not exposing people above the limits. Antenna height, distance from neighbours and your own operating position are the real inputs. A good habit is to write down the numbers once and revisit them when the antenna or amplifier changes. Spurious emissions are §97.307. The general standard is that spurious emissions must be minimised to the greatest extent practicable, and there are specific attenuation figures by frequency and power. Below 30 MHz it is 43 dB below the mean power of the fundamental for transmitters of 5 W or more built after the stated date. VHF and UHF figures are different and depend on power, so read the section rather than rely on a number from memory. Practically, run the amplifier within its rated drive, use filters, and treat a clean signal as part of your compliance. For control, the key types are local, remote and automatic (§97.109). A repeater or auxiliary link can run under automatic control. A remote-controlled station must have a control link that works, and the rules require the transmitter to be shut off if the link fails (see §97.213 for the timing). Auxiliary stations (§97.201) are limited to higher bands: generally 1.25 m and up, minus some sub-bands, and not 2 m. Repeaters (§97.205) are allowed on 10 m and the VHF/UHF bands, except specific segments. Automatically controlled digital stations (§97.221) are restricted to certain segments, so look at the actual list before you put a node on HF. The license classes are Technician, General and Amateur Extra. Novice and Advanced licences are no longer issued but can be renewed. Each class has its own HF privileges, so check §97.301 to §97.305 for exact frequencies and modes. The license term is 10 years. You can renew starting 90 days before expiration through the FCC's ULS. After expiration there is a 2-year grace period during which you may renew without retesting, but you may not transmit until it is renewed. After that you have to take the exams again. Keep your mailing address and email current with the FCC (§97.23). That is a common cause of lapsed notices. On enforcement, the FCC can send a Notice of Violation, propose a forfeiture, or move to revoke or suspend a license in serious cases. It also has volunteer monitor programmes that help identify problems. Document what you did. A station log is not required by Part 97 for most situations, but notes on power, antennas and exposure calculations help you answer an inquiry.
  17. Your split makes sense. I'd stay conservative on the electrical side, because that's where most of these projects get hurt. On Pico versus ESP32: both are 3.3 V parts and neither GPIO is 5 V tolerant, so treat every external signal as hostile until it's level-shifted or isolated. For anything that touches the rig keying line, use a transistor or optocoupler stage rather than a GPIO. Some older rigs have surprisingly high voltages on the key jack, and grid-block keying on tube gear is a classic example. Check with a meter first. If you want Wi-Fi, an ESP32 can work. But I'd put the radio-facing nodes on a wired link (serial, RS-485 or Ethernet) back to the Pi, and keep the Wi-Fi nodes for things like temperature, voltage and door sensors. Wi-Fi is also a dependency you don't want in a station's safety path. A Pico running one simple, well-defined serial protocol is easy to debug, and it still works when the router is down. On the SWR meter, a log detector will cover a wide dynamic range, but accuracy depends on the coupler. A coupler with poor directivity can't resolve a low SWR properly, however good the detector is. Calibrate against a dummy load and a known mismatch, and treat the readout as a monitoring tool rather than lab equipment. Average the ADC readings in firmware, since RF pickup will make single samples jumpy.
  18. On the first question, the order I'd suggest is offset direction, then tone, then tone mode. If the radio shows the right output frequency and you can hear traffic, confirm the offset is going the right way. Then check that the tone you are sending matches the repeater's input tone. A very common mistake is entering the output tone as the input tone, or the reverse. Also check whether the radio is set to encode only or to encode and decode. If it is set to decode, it may mute the repeater audio when the repeater isn't sending that tone. That can look like a dead repeater. One caution about tone squelch on your receiver. It mutes signals that don't carry the matching tone, and that includes a co-channel signal that is interfering with your reception. It also isn't security. CTCSS and DCS only control who opens a receiver, and anyone can hear or transmit the tones. Treat the tone as an access setting, not as privacy. For etiquette, listen before you transmit, because the repeater may be in use, running a net, or carrying a conversation you can't hear from the input side. Identify as your local rules require. In the US that means at intervals and at the end of communication, but check the rules where you operate. Keep transmissions short and leave a gap after each one so others can break in. The time-out timer (TOT) on most repeaters, often somewhere around one to three minutes though the owner sets it, will drop the repeater if you hold the key too long. Let the courtesy tone finish before you key up again. Some repeaters use it to signal that the timer has reset, and it gives a breaker room to speak. Avoid kerchunking (keying briefly just to test), and give your callsign if you're checking signal strength.
  19. One thing that gets overlooked in these debates is the support ecosystem. Radios that were popular tend to have manuals, schematics, user groups and replacement parts floating around, which makes them easier to keep alive. Something rare or odd can be fascinating, but if nobody has documented it, every repair becomes detective work. For anyone shopping, I'd say decide whether you want to operate or tinker, because the best choice differs. For operating, a well-regarded used transceiver with decent filters and a reliable record usually serves better than a project. For tinkering, a basic tube-era receiver or transmitter is a great way to learn, as long as you respect the high voltages inside. Discharge the power supply and don't work alone on the hot stuff. And if you're buying or trading, ask about the power supply, the speaker or accessories included, and whether the seller has actually powered it up and tested it on the air.
  20. To add to the above, here are the points that tend to trip up beginners, and a rough path toward getting on the air. Don't think in dots and dashes. Think of each character as a little tune. "K" is da-di-dah, not "dash dot dash." Saying the sounds aloud as "di" and "dah" rather than "dot" and "dash" helps, because "dot" and "dash" are visual words that drag you toward the translation habit. Paper first, head later. Writing as you copy is a fine way to start, and it's how most trainers and classes work. Head copy comes gradually. A common progression is: copy individual characters, then short words, then common words and callsigns, then phrases. At some point you notice you've already "heard" a whole word before you'd finished writing it. That's the shift. You can encourage it by deliberately copying just the first few letters of a word, or by leaving the pencil down for short, predictable material like call signs and signal reports. Plateaus are normal. Many learners report getting stuck somewhere in the middle speeds. A common remedy is to practice slightly above your comfortable speed in short bursts, where you only catch most of it, then drop back. Another is to switch kinds of material: random groups, then plain-language text, then callsigns. Each trains something slightly different. Keep the character speed high. If you use Farnsworth, avoid dropping the character speed to something very slow just to hit a lower overall number. Slow characters are the exact thing Koch and Farnsworth are designed to avoid. Reduce the effective speed by stretching spacing instead. Bridging to on-air. Contest-style exchanges are very predictable (callsign, report, a name or number), which makes them forgiving for a beginner. Callsign-focused trainers and contest simulators are good for getting used to copying under mild pressure. When you're ready for real contacts, many operators are happy to slow down for a new CW op, and a slow-speed net or a prearranged chat with another learner is a low-stakes first try. It can help to have a short script written out for the first contacts (CQ, your call, a report, your name and location, 73) so you're not improvising while also decoding. Mistakes on air are normal. It's fine to send "?" or ask for a repeat. Everyone does it. If I had to condense it: choose one trainer for daily drilling, add a class or a practice partner if you want feedback, keep drills audio-only, and let head copy develop rather than forcing it.
  21. A single master log in a decent logging program, with the award fields filled in at the time of the contact, saves the most grief later. The fields that matter are DXCC entity, CQ zone, state or province where relevant, IOTA reference, park or summit reference, and the QSL status per service. A lot of award problems come down to something simple like a wrong zone, a wrong entity or the wrong mode in the log, not to a missing QSL. For LoTW, treat your TQSL station locations as part of the award record. If you operate from different places, such as home, a portable site or a different grid, each needs its own correct location. A DXCC credit can be rejected or fail to match if the location is wrong. It is easy to upload a log with the wrong location selected, so check it before every upload. On re-working versus chasing a card: if the other station is on LoTW and never uploaded, a second QSO will not help. A second QSO on another band or mode only makes sense if you want that endorsement anyway. If the station is a rare DXpedition, check how the team handles logs. Many upload to LoTW after the operation, sometimes weeks later, so wait before assuming a contact is lost. Also check your own log for busted callsigns before spending effort on a fix.
  22. For me the line is whether the radio gets used or just admired. A rig on the shelf that only gets powered up a couple of times a year is really a display piece, and that's fine, but call it what it is. Something you operate regularly has to hold up on the crowded bands, and that's where the numbers start to matter. Strong adjacent signals in a contest weekend will show up weaknesses in an older receiver front end that sounds great on a quiet evening. That said, I think the "it does more" argument is overrated for casual operating. If you mostly work SSB or CW and chat with whoever's on, a good 1980s transceiver with decent filters is plenty. The extra features on a new radio matter more if you're chasing weak DX, running digital modes, or want to see the whole band at once. On restoration: replace parts that are likely to hurt you or the radio (old power supply caps, anything in the high-voltage section that looks tired), but keep the original look where you can. Safe first, pretty second.
  23. On the generator question, I'd lean toward treating it as a planned recharge tool rather than a pure emergency backup. A schedule gives the net more predictability. For example, you can decide in advance that a battery at a given state of charge, or a certain time window, triggers a recharge during a lull in traffic. Whatever the trigger, that decision should sit with the station lead and be written in the plan, not made on the fly. Placement matters as much as schedule. Put the generator well away from the tent and downwind, and don't rely on open sidewalls to keep carbon monoxide out. A battery-powered CO alarm inside the shelter is cheap insurance. Also check how you're charging the LiFePO4 from the generator: a proper charger or DC-DC source with the right charge profile (LiFePO4 is commonly charged at around 14.2 to 14.6 V, but follow your battery's documentation). Charging from a generic AC-DC adapter can add noise and may not suit the battery. On noise, a repeatable order is: start with everything off and note the receive noise floor on the band you care about, with the HF rig on battery alone. Then add one item at a time, always in the same order, and note the change on the S-meter or in a waterfall display. Solar charge controllers and cheap DC-DC converters are frequent offenders, so test them early. Common fixes are ferrite chokes on the DC leads (clamp-on works for testing), more separation, or swapping to a different charger. Keep a short log of what was noisy and what fixed it, which makes the next setup faster.
  24. On the back end, treat the contest ADIF and the Cabrillo as two separate outputs with different purposes. Cabrillo is the entry to the sponsor: a text header (callsign, contest name, category fields like operator, band, power and mode, plus name and address) followed by one QSO line per contact. QSO lines carry frequency in kHz, mode, UTC date and time, your call and sent exchange, and the other station's call and received exchange. Because the contest logger builds it from that contest's rules, open the finished file in a text editor and read the header and the first and last QSO lines before uploading. Wrong category lines and mangled exchange columns are far easier to catch there than after the robot rejects the entry. Submission is normally through the sponsor's web upload or a log-checking robot, and each contest's rules page says which. Follow the deadline and file naming given there. ADIF is for your own records and for the services. It is a tagged format where each field declares its length, so something like a callsign is written as the field name, the character count, then the value. Contest-related fields such as the contest ID and the sent and received exchange strings travel with the QSO. Mode handling is a common trouble spot. Digital modes can be written as a main mode plus a submode, and different programs and different ADIF versions do not always map FT4 and similar modes the same way. After an import, spot-check a handful of digital QSOs in the master log before trusting them. Before any bulk import, make a backup of the master log database. Then import into a copy, turn on the logger's skip-duplicates option, and compare the QSO count before and after. Your point about differing dupe definitions is real: the contest logger's dupes follow the contest rules, while the general logger matches on call, band, mode and a time window. Don't assume the two counts will agree. For the uploads: LoTW goes through TQSL, which signs the data with your callsign certificate. The Station Location in TQSL has to describe where the radio actually was (grid, CQ and ITU zones, DXCC entity), and QSO dates have to fall within the certificate's valid range. Upload a small batch first and read what TQSL reports. QRZ Logbook uses an API key for the specific logbook and generally flags QSOs it already has as duplicates, so read the result summary after the upload. Club Log accepts ADIF uploads and can also take QSOs in real time from a logger that supports it, so enable only one of those routes to avoid pushing the same QSOs twice. DXKeeper has built-in upload functions for several of these services. Log4OM and HRD offer similar upload options, and the exact steps vary by version.
  25. Worth being careful with spots. Skimmer spots are good at telling you that a signal exists, but not at giving you a clean callsign every time, and the spotted frequency can be a few hundred hertz off from where the station is actually transmitting. Listening for the station to give his call in his own exchange is still the safest way to avoid logging a busted call, which can cost you the QSO and in some contests a penalty. For antennas, I would not underrate a simple receive improvement before spending on a bigger transmit system. On the low bands a quieter receive antenna lets you hear callers you would otherwise miss, which feeds directly into rate. Does anyone have a preferred way of switching receive antennas quickly between radios when running SO2R, so the second radio is not stuck on a poor antenna?

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.