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_Nancy

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Nancy

  1. A few notes from the logging side. Keep one source log, then export per program. Don't try to put both references into a single MY_SIG_INFO field. The ADIF fields are one-to-one, and an upload system will either reject the record or credit only one reference. Some loggers let you add a second reference under a different field or run two profiles. Whatever your software does, test it with a small sample file before you rely on it after a long day in the field. Also check callsign details. If you operate portable or under a different prefix, make sure the callsign in your log matches what the program expects. Hunters can fail to get credit if their callsign is entered inconsistently, and mistakes like a wrong date or time zone can invalidate contacts. For hunters, the useful habit is to confirm your own log against the activator's uploaded log if credit does not appear. Wait a reasonable time first, since processing is not instant. If a QSO is missing, contact the activator directly rather than assuming the program has lost it. For rules on corrections, resubmissions and award applications, rely on the official WWFF documentation rather than forum summaries, including this one.
  2. Ask a room full of hams what they like about the hobby and you'll get a dozen answers. Some love building antennas, some chase faraway stations, and some just like a good long chat on a quiet evening. Underneath all of that, most of us end up collecting the same kind of thing: small lessons picked up a little at a time, often by accident. Here are some that show up again and again around shacks, club tables, and band conditions. The best rig is the one you actually use Every ham has a dream radio, the one with the big color display and a price to match. But a favorite rig is rarely the fanciest one. It's the one whose knobs fall naturally under your hand, whose receiver you trust, and whose quirks you know well enough to work around without thinking. An older transceiver you understand completely will often make more contacts than a new one you're still learning to navigate. That's why you'll hear people talk fondly about radios that are long out of production. Familiarity builds affection. You know how the audio sounds when a signal is barely above the noise, and you know what the dial feels like when you're tuning across a busy band. Rag chewing is a skill A rag chew is simply a relaxed, unhurried conversation on the air, with no contest exchange and no rush to the next contact. It sounds easy, but a good one takes some practice. A few habits help: Ask open-ended questions. "What's the weather like?" gets a short answer. "What are you working on in the shack this week?" gets a story. Listen for hooks. If the other operator mentions a half-built antenna or a trip to a hamfest, follow up on it. Share a little, not everything. Trading turns keeps the conversation balanced. Leave room. Pauses are fine, and they let the other person jump in. Some of the best on-air friendships start this way. Two operators trade signal reports, discover a shared interest in vintage gear or portable operating, and a few weeks later they're meeting at the same frequency on purpose. That's one of the nicest parts of the hobby: the friendship exists mostly through radio waves. Club nights are where the real education happens Meetings are officially about agendas, treasurer reports, and upcoming events. Unofficially, they're about the conversations before and after. This is where a newcomer can ask, "Why does my antenna tuner keep clicking?" and get three different answers, plus an offer from someone to come look at it. If you're new, here's a simple tip: show up, and ask questions. Hams generally enjoy explaining things, and most clubs are glad to see fresh faces. If you've been licensed for years, consider bringing something to show, such as a homebrew project, a new key, or a portable setup. Even a modest show-and-tell gives everyone something to talk about. Elmers are made, not born "Elmer" is the long-standing ham term for a mentor, someone who patiently helps newer operators learn the ropes. The role doesn't require being the most technical person in the club. It just requires being willing to share what you know and admit what you don't. Good Elmers tend to share some traits. They let you do the work instead of grabbing the soldering iron. They explain why, not just what. And they're comfortable saying, "I'm not sure, let's look it up." If you've been around the hobby a while, it's worth thinking about who helped you and how you might pass that along. Hamfest finds: buy smart, enjoy the hunt A hamfest or swap meet is part flea market, part reunion. Tables of cables, connectors, meters, and mystery boxes make it easy to leave with more than you planned. A few sensible habits make the day more fun and less regretful: Bring a short list of what you actually need, plus a little room for happy surprises. Ask whether you can test equipment before buying, and look for obvious signs of corrosion, cracked cases, or missing knobs. Bring a small bag or cart, and consider carrying a few basics such as a multimeter or a power supply for testing. Walk the whole event once before buying big items, so you can compare. Talk to sellers. The story behind a piece of gear is often half its charm. And if you come home with a box of random coax adapters you may never use, you're in excellent company. Mishaps are part of the hobby Nearly every operator eventually has a moment that's funnier in hindsight than at the time. Common examples include talking at length with the microphone gain turned down, calling CQ on the wrong band, or wondering why the receiver is silent before discovering the antenna switch was on the wrong position. A dropped screw in a radio, a stuck PTT, or a headphone cable tangled around a chair leg are classic hazards too. The nice thing about these moments is that they teach good habits. Check the basics first: is it plugged in, is the right antenna selected, is the mode correct? Many experienced operators suggest working through the simple possibilities before assuming something is broken. Another useful habit is checking your setup into a dummy load before transmitting on a new configuration. It keeps your signal off the air and protects your gear while you work out the kinks. Milestones don't have to be big to matter There's the first license, the first contact, the first time you hear a station from another country, and the first time someone answers your call from the other side of a continent. But there are quieter milestones too: finishing a wire antenna that actually works, sorting out a persistent noise problem, or finally understanding how a band behaves at different times of day. Keeping a simple log, on paper or software, helps you notice your progress. Looking back at early entries often reveals how much you've learned. Many operators also like to note things beyond callsigns and signal reports, such as the equipment used and what the conversation was about. What the hobby means day to day For plenty of hams, radio isn't a big event. It's a quiet habit: turning on the rig with a cup of coffee, listening across the band, checking into a local net, or helping a friend troubleshoot a problem. It's a way of staying curious, staying connected, and staying useful to others. The technology is fascinating, but the people are what make it last. A weak signal that becomes a friendly conversation, a club member who shares a spare part, a new ham who gets their first contact: these moments are small, but they add up. A few things to try this week Spend twenty minutes just listening to a band you rarely use. Check into a local net, even if you only say your callsign. Ask a newer ham what they'd like to learn, and offer to help. Tidy one corner of the shack, and label a few cables while you're at it. Have a longer conversation than usual with the next station you work. None of these require new equipment or a big time commitment. They just ask you to show up, pay attention, and enjoy the odd, wonderful hobby we've chosen. Often, that's exactly what keeps people coming back to the shack.
  3. I'd keep that order and add one rule: don't touch any alignment slugs or trimmers until you know the fault is not a hardware failure. Alignment fixes drift, not dead stages, and tuning a faulty circuit just buries the evidence. If you must adjust something, mark the original position first. On the voltage table: measure with the radio in the state the table describes (RX, TX, or specific mode), because the readings differ a lot between them. A rail that reads right on receive and collapses on transmit usually points to a load fault or a regulator that can't supply the current. For capacitors, electrolytics in switching regulators and in the DC-DC sections are common failures in older rigs, and an ESR meter finds them faster than a capacitance meter does. Replace with the same or higher voltage rating and the correct temperature rating, and use low-ESR types in switcher circuits. Check the orientation twice, and clean up any electrolyte residue, since it can eat copper traces. Don't swap RF-path ceramics, mica, or trimmers at random. Use the right dielectric and tolerance for those, or you'll shift the tuning. For contacts, use a proper contact cleaner on switches, pots, and relay contacts, and go easy on the quantity so you don't float dirt into other areas. A band switch that works on 20 m but is erratic on 15 m is often just a dirty wafer.
  4. I'd add that the training path depends heavily on what your served agencies actually want. Some counties want people credentialed and badged before an incident, with background checks and specific courses. Others want a roster and a quick call-out system. Ask your Emergency Coordinator or the emergency management office what the activation process looks like: who can activate the group, how you get notified, where you report, who you report to, and what happens to your assignment if the situation changes. On net control, the skills are mostly about discipline rather than gear. Keep the net directed, take check-ins in a consistent order, separate emergency or priority traffic from routine traffic, keep a log, and have an alternate net control ready so you can hand off when someone needs a break. Liaison stations to other nets and to the EOC are a big deal too. A simple practice is to run short drills where you handle traffic with deliberately awkward conditions: weak signals, a station that needs a relay, two stations calling at once. That teaches more than a long scripted exercise. As for the go-bag, test it. A lot of people find during an exercise that their cable is the wrong one, the battery is dead, or the antenna doesn't work with the radio they brought. Pack it, take it to a park, and make contacts with it before you need it.
  5. CHIRP is the practical answer for programming, but check the supported-models list for your exact radio and firmware before buying a cable. Cheap cables with poor chipsets and driver problems cause a lot of failed reads, so use a recommended cable. The main habit to get into is to download the current configuration from the radio first and save it as a backup before you write anything. For offsets, don't trust a generic memory. In the US the usual 2 m offset is 600 kHz and the usual 70 cm offset is 5 MHz, but the sign (+ or -) varies by region and by band plan, and other countries use different values. A repeater listing, such as a local coordinating body's database, will usually give you the input and output frequencies and the CTCSS tone required. If the repeater needs a tone to access it, enter it as the transmit tone, and keep tone squelch off unless you actually want it. For emergency use, build a short, well-organized channel list rather than a huge one: local repeaters, a few simplex frequencies, the weather channels, and any agreed net frequencies for your group. Practice simplex before you need it, because repeaters can go down when power or links fail. Knowing your radio's menu without looking at the manual is worth more than any extra feature.
  6. For modeling, EZNEC and MMANA-GAL are both useful, but each tells you only what you put in. In either one, check that your segments are short enough relative to wavelength, especially where wires bend, join, or change diameter. Place the source on a segment that is properly connected to both legs. Choose a realistic ground model, because a free-space result and a result over average ground at 15 feet can look quite different. The EZNEC demo has a segment limit, so a complicated antenna may need the full version, while MMANA-GAL is a free option that many builders use for simpler wire shapes. The biggest modeling trap is leaving the feedline out. If you want to explore common-mode current, add a wire representing the coax and see how pattern and feedpoint impedance change with its length and routing. For traps, model the coil and capacitor as loads, but treat the result with caution. Real traps have finite Q, so a model may show more efficiency than the built antenna. Use the model to choose starting lengths and compare designs, then use measurements on the real wire to adjust. When the two disagree, check height, wire diameter and insulation, and nearby objects before you decide which one is wrong.
  7. For me the deciding factor is what you do with the log afterward. If you chase awards, a single long-term logbook is worth the effort, because worked-before status, DXCC/WAS progress and confirmation tracking all depend on having everything in one place. In that setup the contest program is a short-term tool. You run the contest in its own database, export ADIF when you finish, and import it into the general logger once, with a dupe filter active. A few things I would check on the import. Make sure the band and mode columns are not being rewritten into something different, especially for digital modes. Confirm that contest exchange data lands in sensible fields and does not overwrite your normal comment or name fields. Keep the original ADIF file untouched in a backup folder. If an import goes wrong, you can restore a copy of the logbook and try again instead of trying to fix individual records by hand. The other thing I would flag is clock accuracy. FT8 and FT4 depend on a well-synchronized PC clock, and the time in the log goes out to LoTW and QRZ. A clock that is a few seconds off can hurt decoding, and a bad timezone setting can put QSOs on the wrong date. Log in UTC and use a time sync tool.
  8. The biggest gap I see people discuss is the difference between being a good operator and being a good communicator. Passing traffic accurately matters more than speed. Read it back when asked, use the form your served agency wants, and don't editorialize. If you're handed a message to relay, send what was written. Also worth saying plainly: activation comes through your group's chain of authority. Self-deploying without being asked can complicate things for the agency. Be ready, stay reachable, check in on the designated net if one opens, and wait for a task. Practice it in exercises so it becomes habit. And keep your backup plan simple: primary repeater, secondary repeater, simplex fallback, written down.
  9. For latency, separate delay from jitter. A constant 150 ms is workable for SSB because you adapt to it. Variable delay and packet loss are what make voice choppy and PTT unpredictable. Wired Ethernet on the client side beats Wi-Fi for that reason, and a larger audio buffer will often sound better than a minimal one. For FT8 and similar modes, a common approach is to run WSJT-X (or whatever decoder you use) on a machine at the station and remote-desktop into it, rather than streaming audio across the internet. The time-critical part then stays local, and you only need the screen link to be tolerable. Just keep the server clock disciplined. For CW, sending by keying over the internet in real time is the hard case. It is generally better to send from a keyer or text-to-CW function at the station end, so timing is generated locally and your link only carries characters. Full break-in with a long path will never feel like being at the key. On the rules, I'd read the actual regulations of both places involved, not summaries. In the US, Part 97 covers station control and the control operator's responsibilities (sections on control types and on telecommand are the ones to look at), including requirements about limiting transmission if the control link fails. Other countries have their own licence conditions, and some tie the station licence to a named address or require the operator's privileges to match the station's location. Reciprocal or visitor licensing doesn't necessarily cover remote operation either. Contest and award sponsors also publish their own remote-operation rules, which can differ from the regulator's. Check them before you plan a weekend around a particular station, because the answer may not be what you expect.
  10. On the power side, I'd put a regular check of the kit on the calendar, because batteries are where kits quietly fail. Lithium packs self-discharge slowly but not to zero, and AA cells in a battery case can leak if you leave them for years. A practical routine is to pull the kit twice a year, charge everything, run the radio on the battery for a while, and write the date on a piece of tape on the case. For solar, a modest panel with a proper controller is often better than a big one you can't carry. If you have a LiFePO4 battery, check that your charger or controller has a profile for that chemistry, because lead-acid settings can leave it undercharged. Also check your cables. A voltage drop through thin wire can make a 12 V radio misbehave at transmit, and it's much easier to find out at the dining table than at a staging point. One more thing for the checklist: a small adapter and connector pouch. SO-239 to BNC, BNC to SMA, a Powerpole pigtail, and a barrel connector or two have saved more setups than extra batteries have.
  11. Common-mode current is the sneaky one, because the SWR meter can look great while the coax is doing half the radiating. With an EFHW especially, I'd put a proper choke at the feedpoint and, if the run is long, another choke where the coax enters the shack. A choke made of coax wound on a ferrite core needs the right material for the band. Mix 31 and 43 behave differently across HF, and a choke that is good on 20 m can be mediocre on 80 m. If you can, measure the impedance of the choke rather than assuming. For comparing antennas, avoid judging by who you hear on a single band. Use a consistent method: WSPR or RBN spots over several days at similar times, or a switchable A/B setup with a second antenna and S-meter readings on a steady signal. Your noise floor will often change the result more than the antenna's gain. A quieter antenna that hears slightly weaker signals can still give better readable copy. On doublets: with open-wire line, I'd avoid a feedline length that happens to be a multiple of a quarter wave on your busiest band, because it can bring extreme impedance to the tuner. Changing the line length a few feet can make the tuner's job a lot easier, and the effect is easy to model with free software like 4nec2 or MMANA-GAL before cutting anything.
  12. For FM passes, one practical point is to separate the two jobs: pointing and operating. With an Arrow-style Yagi, the elevation mismatch with the satellite at low angles is rarely a problem; at high elevation passes, you must change your pointing fast near closest approach because the satellite sweeps quickly across the sky. Plan the pass in Gpredict or SatPC32 before AOS (acquisition of signal), write down the maximum elevation and the time, and know whether the pass is east or west of you. Low passes (under about 15 degrees) are often more trouble than they are worth with ground clutter and trees. For logging, keep the exchange minimal: callsign and grid, perhaps a quick report. If you are using the ISS APRS digipeater, remember it shares one frequency with everyone else. Long beacon texts or frequent transmissions create collisions, so keep packets short. And if you are using a rotator, check that your software and controller agree on the protocol (many use GS-232 style commands) and the elevation range. A rotator that stops at 180 degrees of elevation is a different setup from one that goes to 90 only, and it affects how you handle overhead passes.
  13. I'd treat it in three buckets. Rules and definitions (Part 97, operating procedures, safety) are recall, so use spaced repetition on them. Calculation questions are the second bucket. They look intimidating, but they reuse a small set of formulas. The third bucket is the concepts that make many questions easy once you see the idea. A few formulas cover a lot of ground: Inverting op amp gain is -Rf/Rin. Non-inverting gain is 1 + Rf/Rin. With a 100 k feedback resistor and a 10 k input resistor, that's -10 or 11 respectively. Resonance is f = 1/(2π√LC). Q for a resonant circuit is center frequency divided by bandwidth, so a 7.1 MHz filter with 100 kHz bandwidth has a Q of about 71. FM modulation index is deviation divided by modulating frequency, and a rough bandwidth estimate is Carson's rule, 2 × (deviation + highest modulating frequency). A 5 kHz deviation with a 3 kHz tone gives an index of about 1.67 and roughly 16 kHz of bandwidth. For oscillators, remember the Barkhausen idea: loop gain of at least one, with total phase shift of 0 or a multiple of 360 degrees. That one idea answers a surprising number of questions. For the rules section, memorize from a current pool. The question pool is revised on a multi-year cycle by the volunteer examiner coordinators' committee, and Part 97 itself can be amended. Check the effective dates for whatever study material you're using, and look at the pool's own list of changes if you studied from an older book.
  14. Ask a room full of hams what they love about the hobby and you'll hear a dozen answers. Some talk about chasing distant stations. Others like building antennas, tinkering with old tube gear, or running a handheld on the local repeater during the morning commute. But keep the conversation going and the answers start to overlap. Sooner or later, they're about people, curiosity, and the odd satisfaction of making something work. This post is a loose tour of the everyday side of the hobby: the stuff that doesn't make it onto a certificate or a contest scoreboard but keeps the shack light on. The Rag Chew: Conversation With No AgendaA contest exchange takes seconds: callsign, signal report, a serial number or grid, and on to the next one. A rag chew is the opposite. It's an unhurried, open-ended chat that might wander through weather, antennas, grandkids, gardening, the coffee you're drinking, and why your neighbor's new LED lights are wrecking 40 meters. What makes a good rag chew isn't dazzling conversation. It's the willingness to talk without a goal. Some tips that tend to help: Ask open questions. "What are you running there?" invites a story. "Do you copy?" doesn't.Share something about your own station so the other person has something to grab onto.Let the pauses breathe. On a weak, fading band, patience is part of the conversation.Don't be afraid to say you're new. Most operators are glad to slow down for a newer ham.Ham radio is one of the few places where two people who would never otherwise meet can chat easily, because they already share something: they both built, bought, or borrowed the means to reach each other through the air. Favorite Rigs Are Rarely the Fanciest RigsHams love to debate gear, but notice how people describe their favorites. It's rarely the one with the longest spec sheet. More often it's the radio with a great receiver on a crowded band, a tuning knob with just the right feel, or a simple design that never gets in the way. Sometimes the favorite is the first rig, kept long after something better came along, because it's familiar. A few reasons a radio earns a permanent spot on the desk: It's easy to operate. If you can find the setting you need without the manual, you'll turn it on more often.It's good at listening. A solid receiver makes weak signals readable, which matters more than a few extra watts of output.It has a story. A rig you restored, built from a kit, or inherited carries more than its function.The best radio is the one that gets you on the air regularly. A modest station used every week beats a showpiece that sits cold. Club Nights: Where the Hobby Becomes LocalOnline forums and digital modes are wonderful, but a club meeting offers something that's hard to reproduce: faces, handshakes, and the chance to ask someone, "Hey, would you mind looking at this?" A typical club night is a mix of business, a presentation, and a lot of side conversations. The side conversations are often the best part. If you've been thinking about going to a club meeting, here's what you can expect in general terms: A short business meeting covering upcoming events, finances, and projects.A talk or demonstration, often on antennas, emergency communications, digital modes, or a member's project.Informal chatter before and after, where much of the real learning happens.Opportunities to volunteer, from public-service events to Field Day planning.Clubs vary a lot. Some are heavy on emergency communications, others on contesting, building, or just social time. If the first one doesn't feel right, try another. Most welcome visitors, and many are happy to see anyone curious, licensed or not. Elmers: The Quiet Backbone of the Hobby"Elmer" is the ham radio word for a mentor, someone who helps newcomers get started and keeps them going when things get frustrating. An Elmer might help you pass a license exam, check your first antenna install, or explain why your signal sounds muddy. Good Elmering is more about attitude than expertise. The best mentors: Answer questions without making anyone feel foolish.Encourage hands-on experimenting instead of just handing out answers.Admit what they don't know and point to someone who does.Know when to let the beginner make a small, harmless mistake. It's often the best teacher.And the tradition continues because Elmers tend to become more of them. Most people who were helped along eventually find themselves helping someone else, and that cycle is a big reason the hobby stays alive. Hamfest Finds and the Thrill of the HuntA hamfest is part swap meet, part reunion, part forum, and part treasure hunt. Tables of cables, connectors, meters, key paddles, old receivers, and boxes of mystery parts invite you to dig. Some practical habits make the day more fun and less expensive: Walk the whole place first before buying anything big. You'll often see a better deal two aisles over.Bring a short list of what you actually need, plus a little room for a surprise.Test before you buy when possible, and ask the seller about the condition and what's included.Bring a bag or small cart. Your future self will thank you.Talk to people. The vendors and the folks wandering the aisles are half the value.The most satisfying finds are often small: the right adapter you'd been missing, or a manual for a radio you already own. Humorous Mishaps and Lessons LearnedEvery ham eventually has a face-palm moment. They're so common they're practically a rite of passage. Some familiar categories: The "why is nothing working?" mystery that turns out to be a disconnected coax, the wrong antenna selected, or the volume knob turned all the way down.The microphone surprise, such as leaving the transmitter keyed or the audio gain set far too high.The connector that looked fine but had a poor solder joint, intermittently ruining an otherwise good antenna.The frequency mix-up, where you call into a net or a conversation without listening first.The lessons from these are consistent: listen before you transmit, check the simple things first, label your cables, and keep a dummy load handy for testing. Most mishaps are harmless and funny in hindsight, and nearly every experienced ham has a version of the same story. Milestones That Matter (Even the Small Ones)Ham radio has plenty of official goals: a first license, an upgrade, working all states, earning an award. But the personal milestones count just as much. The first time your voice goes out through a repeater. The first contact made on a antenna you built yourself. The first time you hear a faint station from far away and manage to pull it out of the noise. These moments are small on paper and very big in the moment. Don't wait for a certificate to celebrate them. A simple log entry or a note in the margin can be enough to mark the day. What It Means Day to DayFor many hams, the hobby is less a single activity than a background hum in daily life. It's the check-in on the local net, the antenna project on a weekend, the quick listen to the band before bed, the shared understanding with a stranger on the other end of a signal. It's a reason to learn a little electronics, a little physics, a little weather, and a lot about being patient. It also gives you a place to belong without much pressure. You can be a casual weekend operator or a deep technical tinkerer, and the hobby has room for both. So if you've got a little time this week, turn the radio on. Listen for a bit, say hello, and see who answers. Odds are it'll turn into more than just a contact. 73!
  15. On noise, start with the antenna and coax, because a poor antenna installation makes every other noise problem worse. A roof-center mount on a proper NMO base gives the best ground plane and keeps the antenna away from most vehicle electronics. A trunk-lip or magnetic mount can work, but expect more variation in SWR and pattern. Solder or crimp the connectors carefully, check SWR on both bands, and keep the coax away from power cables and engine harnesses where you can. For alternator whine that follows engine RPM, check the power connection first. Poor grounds and long power runs are common causes. Ignition noise sounds more like ticking or buzzing and also follows RPM. Dash cameras, LED lights, USB chargers and DC-DC converters are classic culprits too, and they're usually easy to find. Turn accessories off one at a time while listening to a weak signal or an empty channel. Ferrite cores on a noisy accessory's power lead can help, but the cause should be found rather than just covered up. Also keep the radio's own power leads from running beside the noisy device's wiring. As for etiquette, the main rule is that driving comes first. Use memory channels or preset frequencies, keep transmissions short in heavy traffic, and don't start long technical discussions when the road needs your attention. Listen before you key up, since mobile signals can be hard to judge when you're driving through fringe areas. Give your callsign properly, and say "mobile" if that's how people usually announce it on your local nets. Don't hog a busy repeater: if you only need a quick check-in, say so and clear. Also check your audio level. Road noise can push you to shout, and over-modulation makes you harder to copy. Last tip for APRS or digital use: if you enable beaconing or digital modes, confirm the settings so you aren't transmitting more often than local convention suggests. A mobile that beacons constantly in a congested area is a good way to become unpopular.
  16. On combined activations, the main thing is to keep the two programs' records separate even when you operate once. The same contacts can count toward both, but each program has its own reference format, log requirements and upload process. A common approach is to log everything in one program, then export two ADIF files, one tagged for POTA and one for WWFF. Use the ADIF fields for the activator's program and reference (MY_SIG and MY_SIG_INFO) and check what each program's checker expects. Do not assume a multi-reference field will be accepted by both. Spotting also needs care. Announce the right reference for each program in each place: a POTA spot for the park number, and a WWFF spot for the KFF reference. Say both clearly on the air. A hunter who only needs one program should be able to log you without asking for a repeat. Something like 'CQ POTA and WWFF, K-1234 and KFF-1234' works if you are on CW or phone. Adjust it to match the actual reference numbers, because they are rarely identical. Before leaving home, check that your chosen spot is inside both boundaries. The areas can overlap only partly. Look at each program's map and, if you can, the park authority's own boundary map. Operating a few hundred meters outside the line is a common reason for an invalid claim.
  17. I'd decide CW versus SSB first, because it determines almost everything else. If you're comfortable with CW, a small CW-only rig makes a lot of sense: very low receive current, easy to pack, and a 5 W CW signal is much more readable than a 5 W SSB signal in the same noise. The Mountain Topper and TR-35 class of rigs are built around that idea. If you want SSB, a KX2 or KX3 is more flexible, but expect a bigger bag and a bigger power budget. On the kit side, a Pixie is better treated as a learning project than as a main field rig. The very wide receive passband means you hear everything in the neighborhood at once, so it's hard to copy anything on a busy band. A better-filtered kit gives more satisfaction for the same build time. On the antenna, a resonant dipole or inverted-V on one band is hard to beat for simplicity. Cut it a little long and trim it, and you won't need a tuner at all, which saves weight and loss. An end-fed is more convenient for one-person setup, but the transformer, counterpoise and feedline length all affect performance, so expect to experiment a bit.
  18. For callsigns, a workable habit is to give the full callsign in standard phonetics at the start of a contact, and then only the plain callsign for routine exchanges. When conditions are bad, go back to phonetics. That includes QRM, QSB, a weak signal, a noisy mobile, or a station that has asked for a repeat. If the other operator asks for "the last two letters" or "the suffix again," give just that part slowly, in phonetics, rather than repeating the whole call faster. In a pileup, the usual advice is to send your callsign once, clearly, and listen. Repeating it ten times does not help, because the DX operator is trying to pull out one partial and cannot copy a stream. If you are asked to repeat only part of it, repeat only that part. For names and places, spell only the part that is likely to be misunderstood. "My name is Jon, J-O-N: Juliett Oscar November." For a location you can give the name, the state or region, and then spell it if asked. Mixing in a known landmark often helps more than spelling does. If you spell something, pause between letters, and say "I spell" or "phonetics follow" first so nobody mistakes a letter for a word. On nets, especially emergency or priority traffic, net control normally wants standard words and no experiments. Names, street addresses, and medical or supply quantities are the items where an error does real harm. A good method is to say the item, spell it in phonetics, and ask for a readback. On CW, phonetics are not used; instead, prosigns and procedure matter. AR ends a transmission, SK ends a contact, BT separates sections, and K invites the other station to transmit. On voice, say "over" when you hand the frequency back and "out" when you are finished, but not "over and out" together, since the two mean opposite things. For urgent traffic, state clearly that you have emergency or priority traffic, and follow what net control asks for. Terms like Mayday and Pan-pan are for real distress or urgency, so keep them out of drills unless the exercise rules say how to mark them.
  19. On batteries, the main thing I would add is to measure rather than assume. A small inline voltmeter or a rig with a voltage display shows you how the pack behaves under transmit load. Some rigs sag or reduce power when the supply voltage drops, and some have a low-voltage cutoff that surprises you in the middle of a QSO. For LiFePO4, a proper BMS (battery management system) or protected pack is worth having, and so is a charger meant for that chemistry. Keep the wiring tidy: fused positive lead, decent connectors (Powerpole is common), and a short cable to the radio. If your rig has a stated upper voltage limit, check it against the full-charge voltage of the pack, not just the nominal figure on the label. For QRP-ARCI events, it is also worth reading the exchange and power rules before you go out, so you know whether to log power class or other details. Contesting at low power rewards patience and a good listening ear: find a clear spot, call a few times, and move on if nobody comes back. Working the stations calling CQ often gets you contacts faster than waiting for answers to your own call.
  20. Adding the practical side: sked planning and tracking usually decide success more than raw gain. For planning, start with the mutual Moon window, meaning the hours when the Moon is above a usable elevation at both ends. Then look at sky noise. The WSJT-X Astronomical Data window gives you Doppler, sky temperature and a degradation estimate. A day with the Moon far from the galactic plane and away from the Sun can be several dB better on 2 m. Also check perigee versus apogee, about 2 dB of round-trip loss, because a marginal station can swing from copy to no copy on that alone. Agree on mode, submode, who transmits in the first and second minute, and Doppler handling before the sked. Both ends need accurate time sync, and a clock off by a second or more will cost you decodes. On the hardware side, the preamp sequencer matters. Transmit power must never reach the preamp, so the usual order is to switch the preamp out of the path before RF is applied, and reverse that on receive. Relay and connector loss ahead of the preamp counts directly against noise figure, which becomes critical on 23 cm and above. On 2 m, sky noise dominates, so there is little to gain from chasing the last 0.1 dB of preamp noise figure while ignoring local noise sources or the array's low-elevation ground pickup. For tracking, work out beamwidth first. A rough figure is about 70 times wavelength divided by dish diameter, in degrees. At 23 cm with a 3 m dish that is about 5 degrees, forgiving. At 10 GHz it is under a degree, so you need rigid mounting, accurate encoders, and calibration against sun noise before the Moon. A dish that tracks perfectly on the Sun but is off on the Moon often points to elevation or timing errors in the software, so check those before assuming the feed or preamp is bad. Lastly, own-echo testing is a good gate before any sked. If you can hear your own echoes in the WSJT-X Echo mode, you know the whole chain works, and any remaining problem is on the other end.
  21. For a first summit, I'd pick something where the walk is easy enough that you can focus on the radio. A modest-points summit with a clear trail and good cell coverage lets you sort out spotting and logging without also worrying about route-finding. Chasing the high-point summits comes later. On kit, the biggest decision is whether to start with VHF only. A handheld on 2 m FM can get your four contacts if there's local activity and the summit is open. It's lighter, there's no wire to deploy, and there's nothing complicated to set up. The risk is that if nobody's listening, you're stuck. A lot of activators carry HF for that reason, and others deliberately choose a summit and day where local chasers are likely to be on air. Posting an alert on SOTAwatch ahead of time helps there. For a first HF setup, an end-fed half-wave on a telescopic pole with a short counterpoise and a small CW or SSB rig is a common starting point. A linked dipole is more fiddly to set up but tends to need no tuner and little fuss once it's up. Either way, practise assembling it at home first. A tangled wire in wind on a cold summit is a bad time to learn. One thing I'd add to the list: carry a paper copy or offline screenshot of the summit reference, activation zone notes and the frequencies you plan to call on. Phones die in the cold.
  22. For a first radio I'd lean toward an analog dual-bander over something digital. FM on 2 m and 70 cm covers the most ground for the money: repeaters, simplex, nets and most emergency groups. Digital modes are fun, but they add a code-plug, IDs and network dependencies before you've learned basic repeater operation. One thing I'd add to the budget-radio discussion is the receiver. Baofeng-type radios are very popular and CHIRP-friendly, but they can overload in strong RF environments, such as near a repeater site or a high-power transmitter. If you plan to use it in a city, or at a club event with several radios around, an FT-65R or similar may be less frustrating. If money is tight, buy two cheap radios and a decent antenna, which is often a better use of funds than one expensive radio. On programming, CHIRP is a great starting point because you can see everything on one screen. Just make sure the cable is good, since a poor USB cable is a common cause of failed uploads. Keep your CSV of channels so you can move to a new radio later.
  23. I'd separate the programs by how credit is verified, because that decides your workflow. DXCC, WAS and the Challenge go through ARRL and LoTW or accepted QSL evidence. WAZ, WPX and the Marathon go through CQ's own rules and submission processes. IOTA has its own references and checking, and POTA and SOTA have their own databases. If you mix them up, you can spend effort confirming a contact in a system that doesn't help the award you actually want. One thing that helps with WAZ is to confirm the zone from the other station's actual location, not just from the prefix. A prefix can suggest the wrong zone. For IOTA, check the reference number against the current list and the operator's stated location, because a lookalike group can lead you astray. For POTA and SOTA, I'd keep hunting and activating records separate from your DX award logs. They answer different questions: "did this contact count for the park or summit program" versus "did it count for entity, zone or state credit." Exporting from one system and importing into another without checking the fields can introduce duplicates or odd mode and band entries. Finally, before applying, do a dry run on a small subset. Pull a handful of contacts per band and read them against the rules. Catching a systematic error early beats finding it after you've built a full application.
  24. On power, I'd add that it pays to know the actual current draw of your radio on transmit, and to check that the battery and wiring can supply it. A 100 W radio running at full power for a long Field Day-style session is a very different load from a 5 W backpack rig. For the bigger setups, size the battery in amp-hours against average draw, not just peak, and put a fuse close to the battery. Check that connectors are rated for the current; Powerpoles are a common choice because they're easy to swap and hard to wire the wrong way around. For solar, an MPPT controller with a LiFePO4 setting does a better job than a simple regulator, but a panel is only worth carrying if you'll operate long enough to get meaningful charge. For a two-hour activation, a fully charged battery is often simpler than carrying a panel. For multi-day camping or a longer event, a panel makes more sense, and it's worth knowing what the BMS and charger do at low temperatures. For a Field Day-style setup, think about noise too. Generators, inverters and cheap switching supplies can put noise on HF. If you can run the radio from a battery, you'll often get a quieter receive than if you power it from a noisy source, so it's worth testing before the event.
  25. On sound-card interfaces, I'd say the main choice is between a rig's built-in USB audio and an external interface, and both can work. Built-in USB is simpler, with fewer cables and fewer ground loops, but you depend on the rig's firmware and drivers. An external interface with isolation transformers gives you more control over levels and can help with RF in the shack, but it adds more places to set the wrong level. If you get hum, buzz or random PTT keying, look at common-mode RF and grounding first. Ferrites on USB and audio cables are a reasonable step before replacing anything. On Winlink, I'd add that choosing the mode depends on the band and the gateway as much as the software. VARA HF, ARDOP and Pactor have different strengths and costs, and gateway availability changes over time, so check a current gateway list instead of assuming one exists near you. Also confirm that your CAT and PTT work reliably in the Winlink software before going on air, because a link that keys and unkeys on the wrong cycle wastes everyone's time. For the weak-signal modes, I'd add one more thing: use a quiet receive environment. Many decode problems are really local noise, and a mode with a -20 dB threshold gains nothing if your own noise floor is 10 dB higher than it should be.

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.