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.5
Wind 385.0 km/s
Aurora 1
Updated 13:00 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

Admin_Terry

Administrators
  • Joined

  • Last visited

  1. A few areas where people lose points even after plenty of practice tests: Licence terms and identification. These are easy to blur together. The standard license term is 10 years, and there's a grace period after expiration during which you can still renew without retesting. Station ID has its own rule: identify at the end of a communication and at intervals during a long one, not once per overall session. Read the actual wording in the study guide. Answer choices in this area often differ by a single word. RF exposure. Questions here are usually about the principles. Exposure limits are expressed as maximum permissible exposure (MPE), and whether you must do a station evaluation depends on factors like power, frequency band, and antenna location. Ways to reduce exposure include lowering power, using a directional antenna pointed away from people, increasing distance, and reducing transmit duty cycle. Know why distance helps so much, because field strength falls off quickly as you move away from the antenna. Safety. These tend to be common-sense, but still need review. Examples: put the fuse in the hot (positive) lead of a DC power connection, keep antennas and masts well away from power lines, use proper grounding and bonding, and never work on a tower or climb without proper fall protection. Know what lightning protection and a station ground are meant to do. For practice tests, take them in a format close to the real thing: 35 questions, no looking things up, then reading the explanation for every miss and for every guess that happened to be right. If you can't explain why the wrong answers are wrong, you've memorized a letter, not learned the concept. Finally, check with the volunteer examiner team running your session about what to bring (ID, fees, a calculator policy) since those vary by session.
  2. Adding to the above, I'd think of the tools as a lineup rather than a choice. A trainer such as LCWO or G4FON is good for drilling characters, and for later practice with words, callsigns, and numbers. A CW Academy class adds what software can't: a human advisor, a schedule, other learners, and live practice. CW Academy is run by CWops with volunteer advisors. Class availability and format change, so check the CWops site for the current signup process rather than relying on anyone's memory of it. For head copy, a common progression goes like this. First, write down each character as you hear it. Then move to whole words and callsigns, where you hear a chunk and write it afterwards. Last, try listening without writing and keeping up mentally. If you fall behind on one character, let it go and catch the next one. Dwelling on a missed letter makes you miss the next two. Pick a pitch you find comfortable, often somewhere in the 500 to 700 Hz range, and keep it the same across tools. Also practise with a little noise or fading once the basics are solid, because real bands don't sound like a clean trainer. For confidence, build a script. Most early contacts follow a predictable pattern: CQ, callsign, signal report, name, location, and 73. Practise copying that exchange until it's automatic. Practise your own callsign and the common abbreviations too. Then listen on the air before you transmit, and look for slower stations or other beginners. Many operators will happily slow down if you send something like "QRS PSE" (please send slower). Plateaus are normal. Progress often stalls for a while at some speed, and adding new material or slightly raising the speed can help. Keep sessions short and regular, and don't expect smooth progress every week.
  3. On the antenna and noise side, a better receiver cannot fix a noisy antenna location. At HF, a lot of what people attribute to a weak dongle is local noise from switch-mode power supplies, LED lighting, USB hubs and the computer itself. Common-mode current on the feedline is a frequent route for that noise. A choke on the coax near the receiver, a USB extension with a ferrite, and moving the dongle away from the PC can make a noticeable difference. A small active loop or a properly mounted wire with a 9:1 or similar unun, placed away from the house, often beats a bigger antenna sitting in the noise. For VHF and UHF, a resonant antenna cut for the band (a dipole, discone or ground plane) is usually a better starting point than a telescopic whip. A bias-tee LNA is most useful close to the antenna, so it can overcome feedline loss, but putting it ahead of the filter lets strong out-of-band signals overload it before the filter can help. For 1090 MHz ADS-B or similar, a band-specific filter and LNA combination is more effective than a wideband preamp. Upconverters are a reasonable way to get HF into a dongle that tunes above about 24 MHz. You need to apply the correct frequency offset in the software, and the sideband orientation should be checked against a known signal. For decoding, a virtual audio cable plus WSJT-X works for FT8 and similar modes, and tools such as multimon-ng, dsd-based decoders and rtl_433 each expect a particular audio or IQ format. If you are connecting an SDR as a panadapter to a transceiver, use an IF tap or a dedicated receive output rather than a passive split from the transmit antenna, because transmit power can destroy a dongle front end.
  4. For band openings, I'd say make the spotting networks your first stop and the forecasts your second. Solar indices tell you the odds. PSK Reporter, RBN and WSPRnet tell you what's happening on the air. If FT8 stations in your region are being decoded on 15 or 12 meters by receivers in Europe or South America, the band is open on that path, whatever the flux number says. One caveat is that spotting data reflects who is transmitting as well as propagation. A quiet band on PSK Reporter may only mean nobody is calling. Sending a few CQs on a digital mode and then checking where you were received gives you a quick measurement from your own station. That also tells you whether a poor result comes from the band or from your antenna. On solar cycle news, check whether an article is describing a forecast or an observation. Smoothed sunspot numbers lag behind, and a single geomagnetic storm can wipe out HF for a day or two even when the cycle looks strong. Space weather alerts are worth following for that reason.
  5. On the battery question, the usual practice is direct DC from the LiFePO4 pack, because most modern HF rigs are rated for roughly 13.8 V nominal with a tolerance of around ±15%. A fully charged 4S pack falls comfortably inside that. The part to watch is the knee at the end of discharge. Voltage doesn't sag gradually the way a lead-acid battery does, so a voltmeter alone can mislead you. A coulomb-counting battery monitor (shunt-based) gives a real state of charge, and it is what lets you plan the night instead of guessing. If your pack's BMS has a hard cutoff, set an informal rule to swap to a spare or start charging well before it, since a rig that powers off during a transmission is a bad way to learn where the limit is. Fuse placement matters more than most people expect. Put the main fuse or breaker as close to the battery terminal as practical, then use smaller fuses per branch. A 100 W HF rig can draw in the neighborhood of 20 A on transmit, so wire gauge and connectors need to be chosen for that with margin, and the leads should be short. Check polarity with a meter at every new connection, and agree on one Powerpole orientation convention for the whole group, because a mixed-up kit is a hazard when multiple operators share gear. For noise, the biggest offenders in a battery system are often cheap switching devices: USB chargers, 12 V to 5 V adapters, LED lights, and some solar charge controllers. Test them one at a time on the actual band you plan to use, with the receiver on a quiet frequency, before the deployment. If something produces a carpet of birdies or a raised noise floor, a ferrite choke on both leads, or a replacement, usually solves it. An inverter generator is generally quieter than an old conventional one but not noise-free, and its output feeding a switching supply can radiate. Distance and a ferrite on the power cord help, and the final check is simply to run it and listen. Bear in mind that it depends on the specific unit and the band.
  6. On sending, a useful self-check is to record your own transmission and listen to it with no sidetone and no screen. Common problems are short spaces between letters, so that "EN" sounds like "A", and uneven dahs. A keyer fixes element length but not spacing, which is still up to you. If you use iambic paddles, slow the speed down and focus on making the gaps between characters as clean as the elements themselves. Also check the weighting setting, if your keyer has one. Heavy weighting makes elements long and spaces short, and it can make a good fist harder to copy. The default (often 50 or the equivalent) is the safest start. On the filter question: in a contest with a strong neighbor a few hundred hertz away, narrowing the filter helps. If you are tuning around or hunting weak stations on a quiet band, a wider setting makes it easier to find them and tell where they are relative to your zero beat. Switch between settings as conditions change.
  7. Here's one angle on the RigPi and Pi-based route, and on where the latency really goes. A Pi controller is a good middle ground when your radio has no native network interface. It typically handles CAT through Hamlib, PTT and band-data switching, and it can also manage antenna switches and rotators through the same web interface. That's a big plus over a pure vendor solution, which only talks to the radio. The tradeoff is that you own the integration: audio, a USB sound interface, and keeping the OS patched. Whether you buy it or build it, treat the Pi as an internet-facing device that needs a lock-down plan, not as an appliance. For latency, measure before buying anything. Run a continuous ping and look at jitter and packet loss over a few days, at different times of day, between where you'll operate and the station. A link with 40 ms steady is nicer than one that averages 25 ms but spikes to 300. Audio streams buffer to hide jitter, and every buffer adds delay. That's why CW and break-in feel better when the station end does the keying, and why digital modes belong on the radio side with a local clock. On licensing, don't assume. Whether you're allowed to operate remotely from one country into another, or use a club or commercial remote station, depends on the regulator and your licence class. A service like RemoteHams.com may publish its own conditions, so read those and the local regulations before transmitting, and keep your station identification and logging consistent with where the transmitter physically is. For listening-only use, public WebSDR and KiwiSDR nodes are a good way to practise handling remote audio and latency without any of these questions.
  8. On scouting versus buying, a lot of people do one lap with no wallet out. Note what's on each table and how much it's priced at, then go back for the things worth buying. The exception is anything rare or clearly underpriced. Good items on tailgate tables can disappear quickly, so decide beforehand what you'd grab on the spot, such as a specific HF rig, a quality antenna analyzer, or a good set of Anderson Powerpole parts. For pricing without internet, do the homework ahead of time. Write down a rough range for the five or six items you want, using completed listings and club classifieds, and keep the numbers in your phone notes or on paper. It's also worth remembering that gear with the original box, manual, and accessories tends to be worth more than a bare radio. A tested rig is worth more than an untested one. When a seller offers a demo, ask to see it receive and transmit into a dummy load or a known antenna. If there's no power available, that's your cue to adjust your offer. One more thing: be wary of very cheap "new" items from unknown sellers, such as finals, connectors, or cables that look too good to be true. Counterfeit and mislabeled parts exist, so check connectors and markings before you pay.
  9. For me the line between a "keeper" and a "good radio" is whether I would miss operating it, not whether I'd miss its specs. A lot of great receivers are sort of forgettable to use. Menus, layers of soft keys, the tuning knob that feels like nothing. Meanwhile some older rigs with a heavy flywheel tuning knob and a real S-meter are just a pleasure to sit down at, even if the receiver front end wouldn't survive a contest-weekend 20 meter band. That said, I'd push back a bit on the romance. Strong-signal performance genuinely matters if your neighbors run big antennas or you operate near a broadcast station. Old tube front ends can be wonderfully smooth sounding, but they can also overload badly. If you're deciding between the two, think about your RF environment first. The best-sounding radio isn't any use if a station down the band is splattering across it.
  10. I'd add something about the human side of this, because it's easy to overlook. Introducing yourself on the air or at a club meeting is a skill like any other, and it gets easier with repetition. A few habits help: listen before transmitting, speak clearly, give your callsign properly (phonetics are fine and often helpful), and don't worry about sounding polished. Everyone starts somewhere. At a club meeting, it helps to ask specific questions rather than general ones. "What antenna would you put up with an HOA?" or "Which repeater should I try first on the way to work?" will get you more useful answers than "What should I buy?" It also gives people something concrete to help with. If you can, find a mentor who operates the way you want to. A contester, a POTA/SOTA portable operator, and a digital modes enthusiast will each point you in a different direction, and all of those are good ways to learn. Finally, keep notes or a simple log from the start. Even a paper log with date, time, frequency, mode, callsign, and signal report is useful, and it makes it easier to look back later and see how far you've come.
  11. On nets and contests, it helps to separate the types, because they train different skills. A slow, friendly CW net with a patient net control is mostly about structure: check-in format, handling a callsign list, and passing a short message with minimal fuss. The speed is often forgiving, and you get real on-air copy without much pressure. Ragchew QSOs are different, because the other operator sets the speed and the content is open-ended, so they are better for building head copy once words are coming easily. Contests are very good for callsign and exchange skill, because the format is repetitive. You hear the same pattern over and over: callsign, signal report or serial number, and sometimes a name or section. Contest exchanges often use cut numbers such as 5NN for 599, and learning those speeds things up. Some contests have a QRS or slower-speed segment, and many operators will slow down if you send your callsign slowly and ask. You don't need to be fast to work a few stations, and listening to a contest without transmitting is also a decent way to practice callsign copy. Two practical suggestions. First, record a few minutes of on-air CW and copy it later, so you can replay a passage you missed instead of guessing. Second, don't try to log everything in real time at first. Write only the callsign, or only the part you actually need.
  12. For the first question, the mode usually decides the tool. On CW or RTTY, call CQ for a few minutes and then check the RBN spots page for your callsign. You'll see which skimmers heard you, the SNR and the band, which is a much more objective check than waiting for answers. On FT8 or FT4, enable PSK Reporter in WSJT-X and look at the map for your call. Both methods show how you were received at specific receivers, not whether the whole band is open. Your signal into a skimmer in Europe doesn't tell you what a particular station in Asia hears. On coverage gaps, I'd compare the results with what's heard on the band at the same time. If lots of other stations in your region are getting reported in a direction and you aren't, the problem could be your antenna or power. If nobody in the region is reported there, it's probably just thin receiver coverage.
  13. Q codes were designed as three-letter shortcuts for CW. Sent with a question mark, a Q code asks; sent without one, it answers or states. So "QRL?" means "Is this frequency in use?" and "QRL" means "Yes, it's busy." "QSY?" asks "Shall I change frequency?" and "QSY" is an instruction or statement. The ones on your list: QRM is man-made interference, such as other stations, a buzzing power supply or a neighbor's electronics. QRN is natural noise, mainly static from thunderstorms. A handy test: if lightning is the culprit, it's QRN. If a human or a device caused it, it's QRM. QRP means low power. The usual working definition is 5 watts output or less on CW, and 10 watts PEP on SSB is commonly used. QRO is the opposite: running high power. QRT means "I'm stopping transmission," so an operator signing off says "QRT" and goes off the air. QRZ? means "Who is calling me?" You'll hear it when someone caught a partial callsign in a pileup. (QRZ.com is also a well-known callsign lookup site, which is a separate use of the letters.) QSL means "I acknowledge receipt" on the air. Said or sent alone it means "Got it." It also names the confirmation of a contact, historically a postcard and now often a Logbook of the World or similar electronic confirmation. A QSO is a two-way contact. QSY is to change frequency. QTH is your location, so "My QTH is Denver" tells the other station where you are. QSB is signal fading, where the strength rises and falls. Then the general-purpose words. CQ is a general call to anyone: "CQ CQ CQ de [your call]". "CQ DX" asks for distant contacts, and "CQ TEST" signals a contest. DE means "from," so the called station comes first and your call after DE. K means "go ahead, anyone," and KN means "go ahead, but only the station I'm talking to." Use KN when you don't want others to break in, for example in a rag chew or when answering a specific station. SK ends a contact, and "73" means best regards. 73 is already plural, so "73s" is technically redundant even though people say it. 88 means love and kisses and is traditionally friendly and affectionate, so it's usually kept for close friends, spouses or YLs. Don't use it casually if you're not sure it will land well. One more point: SK can also stand for "silent key," which is how the community refers to a deceased ham. Context makes it clear. At the end of a QSO it just means "end of contact."
  14. I'd put message handling at the top of the list. Many operators are comfortable with voice nets and uncomfortable with writing something down accurately and passing it on exactly as written. A decent test is to have an exercise "agency" hand over several messages of different lengths and priorities, then check what arrives at the destination. Compare the original with the final copy word by word. Differences usually show up in numbers, names and addresses. For formal traffic, the standard radiogram structure is worth practicing: preamble (number, precedence, station of origin, check, place of origin, time and date), address, text, signature. Precedence matters too. Emergency, priority, welfare and routine are not interchangeable, and in an exercise you can deliberately mix them to see whether net control orders them sensibly. Many served agencies use their own forms, often the ICS 213 general message, so it helps to practice converting between the agency's form and radio traffic without altering the content. Ask the agency which form they actually want before the exercise, not during it. On served agencies: invite someone from them to write the injects or at least review them. If your scenario doesn't resemble the questions they would really ask, you're practicing for your own exercise rather than their needs. Also, ask them plainly what they do not want from volunteers. Sometimes the most useful finding is a boundary, such as who is authorized to speak to the media or who decides when a shelter is full.
  15. A couple of things to add on the EFHW side, since it often gets treated as a no-tuner miracle. The match is good on the design bands because the wire is a half-wave resonator, but the transformer ratio sets the impedance it can hold, and real feedpoint impedance moves with height, nearby objects, and wire routing. A 49:1 box that gives 1.3:1 on a test in the open can show something different once the wire is draped along a fence. This is also why there are variations, like added series capacitors or different ratios. The other point is the counterpoise. A half-wave end-fed antenna has little current at the feed end, but the shield of the coax can still pick up current, so the radio end is where I'd put a choke. Some designs include a short counterpoise wire (often around 0.05 wavelength on the lowest band) to give the transformer a reference. If you get RF in the shack, a hot microphone, or an SWR that changes when you touch the coax, those are signs of common-mode current. For the magnetic loop question: a small loop can be a real option when nothing else is allowed, and it can receive quietly because of its nulls and its rejection of local electric-field noise. But the efficiency depends heavily on the loop diameter relative to the wavelength, the conductor, and the joints in the loop, and on 40m and 80m small loops can be quite inefficient. They also need retuning when you change frequency by even a small amount. They are fine for 20m and up if you can get one clear of metal and a few feet off the ground, and a mixed approach, such as a loop for the upper bands and a wire for 40m, may serve better than trying to cover everything with one design.

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.