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. On the transmitter side, the minimum I'd want before going on air is a dummy load, a way to measure power (an RF probe and a calculation is acceptable at QRP: P = V_rms² / 50, with V_rms roughly the peak reading divided by 1.414 after correcting for diode drop), and some way to look at harmonics. A low-pass filter is not optional on a single-transistor final, because the output of a Class C or hard-driven stage can have strong harmonics. A 5-pole Chebyshev low-pass for the band is a small build and the values are easy to look up. For harmonic checking, an SDR or general-coverage receiver works, but never connect the transmitter output straight to it. Use a dummy load with a sampling tap or a good attenuator, or the front end can be damaged and you will see overload spurs that aren't really there. A NanoVNA is useful for sweeping the filter itself and for checking antenna match, but it is not a spectrum analyzer, so it doesn't replace checking what the transmitter actually emits. For the uBITX and similar multiband kits, the output filtering and spurious output are worth checking on each band you plan to use, since a filter that is fine on one band may be marginal on another. Treat any published performance numbers as a starting point and verify them on your own unit. On soldering: a temperature-controlled iron, thin rosin-core solder, fresh flux and a clean tip fix most intermittent problems. Cold joints on toroid leads are common, so scrape the enamel properly or use a tinned lead test before winding another coil.
  2. One distinction I'd add is between remote control of your own station and operating a shared or hosted one. The second case gets murky quickly. If a station owner or service provides the equipment, you still need to know whose license is in play, which privileges apply, and what the host's own rules say about modes, power and band use. I would read the host's terms and the regulator's guidance together, and ask the host directly if anything is unclear. On the hardware question, the IC-7610 with RS-BA1 or wfview and the Flex SmartLink route both keep the rig-side computer out of the picture, which cuts the number of things to patch. The RigPi or PC route gives you flexibility for older rigs, amplifiers and antenna switches, but then you own the operating system updates, user accounts and logging. Neither is wrong, so it depends on how much maintenance you're willing to do remotely. For the watchdog, I'd want something that does not depend on the same network path as the radio control. A separate switched power outlet on a different connection, or a cellular-connected relay, gives you a way to cut power if the main link is half-alive. Use it as a last resort, since cutting power to a radio or amplifier abruptly isn't ideal, but it's far better than a stuck carrier.
  3. The deciding factor is usually what you need the confirmation for. If a contact is for DXCC and the station uses LoTW, check LoTW first. It costs nothing, and a match often shows up within a day or two of both sides uploading. If the DX station isn't on LoTW, look at their QRZ page and their Club Log OQRS status before writing a direct letter. Many stations state their preferred route and who their QSL manager is. Before requesting a card, confirm the QSO is actually in their log. Busted callsigns and time errors cause plenty of wasted postage. Club Log's log search, where a station has made it available, can help with that. Always send UTC date and time, band, mode, and the exact callsign you worked. If the manager can't find the QSO in a quick lookup, the request often gets set aside. For direct requests, the rules are simple: send a legible card, include return postage in a form the destination can use, and keep the envelope plain. Postal rules vary a lot, so I wouldn't treat any single dollar amount as universal.
  4. I'll take the operating-rules half. Verify everything against current 47 CFR Part 97 on eCFR. Station ID (§97.119): you must identify with your FCC-issued call sign at the end of a communication and at least every 10 minutes during it. You don't have to ID on every over. Phone IDs are given in English (a standard phonetic alphabet is allowed), and CW, RTTY and data IDs are sent in the mode being used. A tactical call like "Net Control" or "Shelter 2" is fine for operational clarity, but it doesn't replace your call sign. Repeaters have their own ID obligation, which the trustee or control operator normally handles with an automatic ID. Your own call is still required for your own QSO. Third-party traffic (§97.115): a third party is someone other than the two licensees in the contact. A control operator must be present and continuously monitoring so they can terminate the communication. For international contacts, third-party traffic is only permitted with countries that have a third-party agreement with the US, or when the third party is themselves a licensed amateur eligible to operate. Content for international communications is also limited under §97.117 to personal remarks of relative unimportance and technical matters. There are some restrictions on who can be a third party, such as someone whose license was revoked or suspended. Power (§97.313): the general ceiling is 1500 W PEP output, but some bands and segments have lower caps. Examples are 200 W PEP on 30 meters and 200 W PEP for Technicians in their HF segments. The 60-meter rules have their own channel and ERP framework, so check the current text. Also read §97.313(a): you must use the minimum power necessary to carry out the desired communication. Running full power into a local repeater input is something you can reasonably be questioned about. Prohibited transmissions (§97.113): a few main categories. First, no communications in which you or your employer have a pecuniary interest, with narrow exceptions. These cover things like occasional sales of your own station gear, emergencies involving immediate safety of life or property, and certain teaching situations. Second, no music, no obscene, indecent or profane language, no deliberately false or deceptive signals, and no broadcasting. Third, no messages encoded to obscure their meaning. This is why modes with publicly documented protocols are fine, but encrypting traffic on amateur frequencies is not. Narrow exceptions exist for control of space stations and some telecommand uses. And §97.101(d) bars willful or malicious interference.
  5. I'd start with the doublet, then work backward from the compromises. A balanced, center-fed wire on ladder line is the most forgiving multiband option when you can't make the geometry ideal. Open-wire line has very low loss even at a high SWR. The mismatch loss is mostly paid in the tuner, not in the feedline, and a decent tuner handles that. The wire doesn't have to be straight, symmetrical, or any particular length. Avoid lengths where the feedpoint impedance becomes extreme on your favorite band, and a quick model will show you which lengths to dodge. A G5RV is really just a doublet with a short ladder-line section and a coax run. It can work, but it doesn't have any magic. On most bands you still need the tuner, and the coax between the ladder-line section and the radio carries a high SWR on those bands, so you pay more loss than with ladder line all the way to the shack. Height matters more than most people expect. A horizontal 40m dipole at 30 ft is only about 0.2 wavelength up, so it has a high takeoff angle. That is fine for regional contacts and NVIS-type work, but it isn't a DX antenna on 40. On 20m, the same 30 ft is nearly 0.45 wavelength, which is much better for lower-angle radiation. The same wire improves as you go up in frequency. Fold the ends down into an inverted V if you have to. Keep the included angle above roughly 90 degrees, and keep the ends out of reach of people and pets, because the voltage at the tips can be substantial. Common-mode current is the quiet problem with every option here, whether or not it shows up as SWR. A 1:1 current balun or common-mode choke at the feedpoint helps, and so does a second choke where the feedline enters the house. Ferrite choking impedance of a few thousand ohms or more across the band you care about is a reasonable target. If the antenna sits near the house wiring, put the chokes in before you start chasing noise or RFI.
  6. One thing worth adding is a power budget on paper. Write down each device, its approximate draw, and how many hours you would run it. A typical HT on receive uses very little, while a 50 W mobile on high power can pull well over 10 amps while transmitting. If you list this out, you quickly see whether your battery is sized for the net or just for show. On the solar side, a modest panel can keep a small battery topped up for receive-only monitoring and light transmitting, but it will not keep up with heavy 100 W HF operation all day. The battery is what carries the load. The panel mostly buys you time. Also remember to fuse the positive lead close to the battery, and to keep your connectors consistent between the panel, controller, battery and radios. It is easy to reverse polarity when swapping cables in the dark. For antenna planning, I would keep a no-tools VHF/UHF option and a more capable HF option separate. The VHF/UHF one is for quick local contact, while the HF one is for when regional repeaters are down and you need to reach outside the area.
  7. On net procedure, the main point for newcomers is that formal nets are about clarity, not speed. For a traffic net, don't try to improvise message handling. Use the net's own format, and if you aren't sure how to handle a radiogram, say so and let net control assign someone to help or just copy the preamble. For ARES and SKYWARN, avoid chatting on the frequency. Keep your report short: who you are, where you are, what you observed, and when. Leave out guesses. Also, a weather net is not a general-purpose frequency. If a net is active for a real event, hold off on casual calls and wait for the all-clear or the net's closing statement. For DX nets, the opposite applies: be patient, don't call out of turn, and don't talk over the DX station. If you're unsure how a given net works, many of them post a script or a short guide on their website, and reading it ahead of time is worth the five minutes.
  8. Start with the fields that identify the station. If STATION_CALLSIGN, OPERATOR, MY_GRIDSQUARE and MY_STATE (or the equivalent) are missing or inconsistent, the other fixes only hide the problem. Set them once in each program's station profile. A contest exported with a club callsign as station and your own call as operator is handled very differently by LoTW and QRZ than one where both fields say the same thing. That mismatch can cause rejected or unmatched uploads. Time is the second common source of doubles. ADIF expects UTC date and time, and an import with the wrong timezone assumption shifts QSO times. Dupe checking in the master log then fails, because a QSO that is the same contact looks like a different one. Test the import with a handful of QSOs near midnight UTC, since date rollover is where mistakes show first. On Cabrillo, I'd treat the exported file as a read-only artifact. If something is wrong in the file, fix the log in N1MM+ and re-export, rather than editing the Cabrillo by hand. Hand edits tend to be forgotten, and the next export overwrites them. The exception is a header typo, which is fine to change in a text editor as long as the file still follows the sponsor's format. For dupes during the contest itself, N1MM+ checks by callsign plus band, and for mode it uses mode groups (CW, phone, digital), not each mode separately. That matches how most contests count QSOs, but some sponsors count differently. Look at the contest's rules before assuming the defaults suit it.
  9. Numbers first, because they're where voice traffic most often goes wrong. On amateur phone, most operators just say "one, two, three". Some use "niner" for nine, because "nine" can sound like "five" or "nein" in noise. The aviation-style forms ("tree", "fower", "fife") are part of the ICAO procedure but are rare on ham bands. Whatever you pick, say digits individually when accuracy matters ("one four seven point five two"), not "a hundred and forty-seven". For times, use UTC and 24-hour format, and say "UTC" so nobody has to guess. For spelling names and locations, announce it first with something like "I spell" or "spelling". Then give the word once, spelled in standard phonetics. A name with an unusual spelling, or a street or town that sounds like another place, should always be spelled. A good habit is to say the word normally, spell it, then say it normally again. If the other station reads it back, correct it right away and let them fix it. Don't just say "that's correct" to a read-back that's slightly wrong. Prosigns on CW (AR to end a transmission, SK to end a contact, BT as a break, K or KN to invite a reply) don't carry over to voice. Phone uses procedure words instead: "over", "clear" or "going clear", "break", "stand by", "say again" (not "repeat", which on military-style nets can mean something different), and "copy" or "roger". Nobody has to speak in a style that sounds like a movie, but use words that are unambiguous when the signal is bad. On nets, net control sets the procedure. Typical elements are a check-in order (often suffix-only callsigns, which makes standard phonetics important), "short time" for stations with brief business, and a clear way to say you have traffic. Emergency or priority traffic usually gets a break-in procedure such as "break" or "priority", and most nets define theirs in writing. Learn those local rules in advance. Real distress calls use "Mayday", and urgency uses "Pan-pan". Don't use them in ordinary exercises unless the exercise explicitly says so. In emergency traffic, standard phonetics, short sentences, read-back of numbers and addresses, and no improvised abbreviations are all worth the extra seconds.
  10. On the CAT side, the biggest gotcha is how the software and the radio decide which frequency is the reference. In Gpredict's radio control, you pick a target satellite and transponder from the module's list, engage the rig, and choose whether the downlink or uplink is locked. For linear work most people lock the downlink and let the uplink follow, so turning the VFO knob moves your transmit frequency in the correct inverting or non-inverting direction. If it moves the wrong way, check the transponder entry for the sign of the mode first, before blaming the radio. SatPC32 works similarly but has its own satellite and frequency files, so keep those updated. It also relies on you loading recent Keplerian elements, and old TLEs are a classic reason a pass seems to start early or late, or why an elevation looks wrong. Update elements before you head out, especially for low satellites whose orbits change quickly through drag. For FM, a decent baseline is to program the radio's memories with the center frequency and then trim using a few steps per pass, especially if you don't yet have CAT control. You can still make plenty of contacts that way.
  11. Your last two questions are about technique more than tools, so here are some points on those. Flashcards and apps. A flashcard can work if it's audio-based: the card plays the sound and you recall the letter. A card that shows ".-" and asks "what letter?" teaches the wrong skill. The same goes for apps. Check whether they play characters at a decent character speed with spacing, or whether they just show a chart and a slow tone. Short sessions help more than long ones. Twenty to thirty minutes with full attention usually beats a tired hour, and frequent shorter sessions let your brain consolidate the new sounds. Reaction time. When you hear a character, respond right away, or write it as soon as you recognize it. If you have to think about it, you are decoding, which is slow. If a character fails to register, leave a blank and move on. Stopping to puzzle over it makes you miss the next two or three, and that's how copy falls apart. Accept the gaps while you learn and let the ear improve. Copying in your head. Paper is useful early on because it holds the characters while you build speed. At some point, try listening without writing. Start with plain words and common short words, which your brain learns to recognize as whole units. Later you can listen to slow code practice sessions or recordings and just follow the content without writing anything. Don't try to go straight to head-copy at full speed. Treat it as a gradual change, and write less as the sounds become familiar. Confidence. A common reason people hold off is fear of making mistakes live. A few things lower the pressure. Start with a short, scripted exchange: call sign, signal report, name, location. It's the same every time, so you only need to copy a few items. Calling or answering at a slow speed is normal, and many CW operators will slow down if you ask politely. You can also listen first for a while without transmitting. Pick up the key once you can copy calls and reports with reasonable reliability. Nobody on the air expects perfect copy from a beginner. Finally, consistency matters more than which tool you choose. Daily short practice with a trainer you trust will take you further than switching resources every week.
  12. Start with the format shorthand. A call sign is described as prefix letters, then a numeral, then suffix letters. W1AW is a 1x2: one prefix letter, the digit, two suffix letters. KA1ABC is a 2x3. The FCC sorts these formats into four groups, and your operator class decides which groups you can draw from: Group A: 1x2 and 2x1 calls, Amateur Extra only.Group B: 2x2 calls, Extra and Advanced. Advanced is no longer issued but is still renewable.Group C: 1x3 calls, Extra, Advanced, General and Technician.Group D: 2x3 calls, open to every class.The sequential system assigns the next available call in a group based on the mailing address on your license. Where you live sets the numeral. It runs through the pool in order and skips calls that are already taken. Because the shorter formats are mostly spoken for, new licensees often receive Group D 2x3 calls these days. How deep the pools run varies by region, so treat that as a general pattern rather than a promise. Sequential assignment, upgrades and renewals don't carry an application fee, though VE session fees are a separate matter. Vanity is the route when you want a particular call. You file through ULS using your FCC Registration Number and CORES login, and you can list multiple choices in order of preference. The call has to come from a group your operator class is eligible for. There are carve-outs for things like a former holder of a call or certain close relatives of a deceased holder, so read 97.19 before assuming anything. Calls that are already assigned aren't available, and there is a waiting period before a lapsed or deceased holder's call comes back into circulation. The FCC also holds back certain combinations, such as ones resembling distress signals or Q-signal-style suffixes. The vanity application has a fee, set by the FCC and subject to change, and it is paid per application, not per call listed. Look at the current fee schedule before filing. Two practical notes. First, the numeral on a vanity call doesn't have to match your location, since you can pick any call in an eligible group. Second, some prefixes tied to specific territories carry geographic conditions, so confirm the rules if you're eyeing one.
  13. One habit that has served many operators well is separating "measured" from "claimed." Independent lab data, such as receiver testing with a stated methodology, is much more useful than a feature list. Even then, check what the numbers mean for your situation. A rig with excellent close-in dynamic range matters if you operate contests or live near other stations. It matters less if you mostly work quiet-band SSB with a modest antenna. On firmware, my rule of thumb is to treat an update like any other change to a working station. Write down your current version, save the settings, read the changelog for anything touching CAT control, digital modes, or audio levels, and keep the previous version file if the manufacturer still offers it. If your logging or digital software talks to the radio, check that its developer supports the new release before you flash. For regulation, I'd add that comment deadlines and effective dates are easy to miss. The ARRL usually summarizes, but the FCC docket is where the exact wording lives.
  14. Ask ten hams what the hobby is about and you'll get twelve answers. Some chase DX, some build antennas, and some like fixing old tube gear. Others just like having a friendly voice on the air at the end of a long day. That variety is much of the appeal. Underneath it, though, there's a shared texture to ham life: small routines, familiar frustrations, and a community that tends to show up for you. This post is about that everyday side of the hobby. It covers the parts that don't make it into contest scoreboards or award certificates but are why many people stay licensed for decades. The Rag Chew: Radio's Version of Sitting on the PorchA rag chew is a relaxed, no-agenda conversation. Nobody is trying to complete a quick exchange or grab a new entity for the log. You talk about the weather, the rig, the antenna that's getting wrestled into place this weekend, the grandkids, or the book on the nightstand. Several things make a rag chew work: Curiosity beats cleverness. Asking "What are you running there?" or "How long have you been licensed?" opens more doors than any rehearsed line.Let the other station steer. If someone clearly loves talking about their vintage receiver, let them. You'll learn something.Keep over lengths reasonable. On a net or a busy band, short transmissions are courteous. In a two-way chat, a bit more room is fine, but leave pauses so the other person can jump in.Remember the callsign rules. Identify as required where you operate, and remember that a casual tone doesn't change the regulations.The charm of a rag chew is that you may never meet the other person, yet over months of contacts you can know their habits, their sense of humor, and what their station looks like. These on-air friendships are one of ham radio's quieter marvels. Favorite Rigs Are Rarely About SpecsSpend any time around hams and you'll hear someone defend their favorite radio with real affection. It's often not the one with the best numbers. It might be the transceiver that was the first HF rig on the desk, the one with a satisfying tuning knob, or a hand-me-down that still works fine decades on. A few reasons a rig earns a permanent spot in the shack: It's comfortable to operate. Good ergonomics, a readable display, and knobs that do what you expect matter more than a long feature list.It has a story. A radio acquired from a fellow club member, or one built from a kit, carries meaning that a new box from a store may not.It's forgiving. Radios that you can learn on without fear of breaking something encourage experimentation.Modern software-defined radios, handhelds, and QRP kits all have devoted fans. The best rig is the one that gets you on the air regularly. Club Nights and MeetingsLocal radio clubs vary a lot. Some are tiny groups meeting in a library room, while others have their own buildings and repeaters. Most share a few ingredients: a business meeting, a presentation or demo, and plenty of conversation before and after. If you've never gone to a club meeting, a few suggestions: Go once without expectations. You don't need to join on the spot or volunteer for anything.Bring a question. "I'm trying to get started on HF. Where would you begin?" will usually start a long and helpful discussion.Stay for the parking lot conversation. Many of the best tips are shared after the formal meeting ends.Clubs also run public service events, Field Day operations, license exam sessions, and informal nets. Even if you're a solo operator at heart, a club offers shared equipment, collective knowledge, and a reason to leave the house with a radio-related purpose. Elmers: The Mentors Who Make the Hobby StickIn ham circles, an "Elmer" is a mentor who helps newcomers learn the ropes. A good Elmer isn't necessarily the person with the biggest antenna farm. It's someone patient who remembers what it was like not to know, and who explains the why behind the advice. If you're looking for one, try your local club, an online forum, or a regular net. Be specific about what you want to learn, whether that's setting up a first station, understanding propagation, or troubleshooting a noisy receiver. If you're the experienced one, consider paying it forward. Answering a beginner's question without making them feel foolish may be the most valuable contribution you can make to the hobby. Hamfest Finds and the Art of the Flea Market LapHamfests combine a swap meet, a reunion, and a treasure hunt. Tables are packed with radios, cables, connectors, tools, books, and boxes labeled "misc." Some practical habits help: Do a full lap before buying. You'll see the range of prices and avoid snapping up the first item you spot.Ask if you can test it. Many sellers have a power supply handy. If a radio can't be powered up, price it as a project.Bring a short list. Without one, a bin of interesting connectors can easily become a bag of things you'll never use.Check basics. Look for cracked cases, corroded battery compartments, missing knobs, and unusual modifications.Talk to people. The seller often knows the equipment's history and quirks.Some of the most satisfying purchases are the cheap ones: a bag of coax adapters, a used paddle key, or a book that explains something you've been wondering about. Humorous Mishaps Every Operator Eventually Learns FromNearly everyone in the hobby has a version of the same few mistakes. They're common enough that they've become part of the culture: Calling into a dead radio. The volume is down, the wrong antenna is selected, or the mic is unplugged. Always check the basics first.Transmitting into the wrong antenna or no antenna. It's why many operators test with a dummy load and watch SWR before going on the air.Forgetting to unkey. A stuck push-to-talk, a hot mic, or a foot switch in the wrong place can broadcast more than you intended.Tuning on top of a QSO. Listen before you transmit, and ask if the frequency is in use.Debugging for an hour, then finding a loose connector. Check cables, power, and connections before assuming something is broken.The lesson in each is a good habit: slow down, check the simple things, and treat mistakes as normal. Experienced operators tend to be generous about them, having made the same ones. Milestones, Big and SmallHobby milestones don't need to be dramatic. Many hams mark moments like: Passing a license exam or upgrading to a new class.Making a first contact on a new band or mode.Getting a homemade antenna working.Finishing a kit build.Helping someone else get licensed.Each one is a reminder that this hobby rewards steady curiosity. You don't have to master everything. Learning one new thing at a time adds up. What It Means Day to DayFor many people, ham radio becomes a background hum of connection. It's tuning across a band while having coffee, checking in to a local net, or tinkering with a project on a quiet evening. It's also a skill set that can be useful when other communication fails, which is why so many operators take emergency communications seriously. Mostly, though, it's about people. The antenna, the radio, and the license are tools. The real draw is the conversation, the shared problem-solving, and the sense of belonging to a community that spans the street and the globe. If you're new, get on the air, introduce yourself, and ask a question. If you're a longtime operator, say hello to someone new. A friendly call may be the thing that keeps someone in the hobby for decades. 73, and see you on the bands.
  15. I'll cover 4 through 6. RF exposure (97.13(c) and the FCC's general exposure limits). Every amateur station licensee is responsible for ensuring the station doesn't expose people to RF levels above the FCC limits. A routine evaluation is required when the station's power exceeds certain thresholds listed in a table in 97.13, and those thresholds vary by band. Below the threshold you're not required to do the full evaluation, but you're not exempt from the exposure limits themselves. Inputs to a proper evaluation include power at the antenna, feedline loss, antenna gain and pattern, duty cycle of the mode (SSB and CW average far lower than FM or a carrier-heavy digital mode), frequency, and the distance to areas where people can be. The FCC's OET Bulletin 65 and its amateur supplement describe methods and worksheets. Pay particular attention to antennas close to occupied space, such as attic or low rooftop installations, where the public or family members might be within the near field. The limits for controlled and uncontrolled environments differ too. Spurious emissions (97.307). The general rule is that spurious emissions must not cause harmful interference to other services, and there are numeric standards by frequency range and power. For HF transmitters the requirement is on the order of 43 dB below the fundamental for typical modern radios. For VHF and above, stations over a given mean power level, around 25 W, must be at least 60 dB down, while lower-powered ones have a less strict figure. Check the exact wording in 97.307 for your band and power level. Practically, trouble tends to come from overdriven linear amplifiers, splatter from excess audio or ALC problems, out-of-band harmonics when a low-pass filter isn't used, and homebrew gear without proper filtering. Good engineering practice under 97.101(a) means testing and filtering, not just assuming a commercial radio is clean once you add an amplifier. Control and auxiliary operation. The control operator is the licensed amateur designated to be responsible for the station's compliance at a given time. Local control means you're at the station's control point with direct access. Remote control means you operate over a link, and you must be able to shut the transmitter off. Automatic control means no control operator at the control point, and it's only permitted for specific station types such as repeaters, beacons, auxiliary stations, and certain digital stations in designated segments. An auxiliary station is a link or control station, for example a link between repeaters or a control link to a remote base, and it's limited to certain bands (generally 2 meters and shorter, with some exclusions that are spelled out in 97.201). Telecommand rules in 97.213 govern remote control of the station itself. Enforcement. The FCC's Enforcement Bureau handles amateur radio violations. Typical steps can include a notice of violation, a notice of apparent liability for forfeiture, license revocation or suspension proceedings, or a cease-and-desist order. Non-FCC volunteer monitoring programs run by amateur organizations observe and report but don't have enforcement authority. Willful and malicious interference, unlicensed operation, and operating outside privileges are the types of behavior that tend to draw attention. License classes, term, and renewal. The currently issued classes are Technician, General, and Amateur Extra. Novice and Advanced licenses are no longer issued, though holders can renew them. An amateur license is generally valid for 10 years. Renewal can be filed shortly before expiration. After expiration there is a grace period during which you can still renew without re-testing, but you're not authorized to transmit while the license is expired. After the grace period ends you'd need to qualify again. Keep your address and contact information current in the FCC's licensing system, because the FCC uses it for correspondence, and check the FCC's current instructions for filing and any fees, since processes and systems can change.
  16. For a first contest, I'd point people toward something with a short exchange and a flexible time commitment. CQ WPX is a good one, since the exchange is just a report and a serial number, and you can operate for an hour or for the whole weekend. Sweepstakes is great too, but the precedence, check and section exchange is longer, so it's worth practicing it on paper before the weekend starts. A bad copy of the exchange is the most common reason for a busted QSO, and it can cost you points as well. One thing that gets overlooked: read the category definitions closely. Low power, QRP, assisted vs. non-assisted, and single-op vs. multi-op each have different definitions, and the rules differ between sponsors. A log submitted in the wrong category can end up reclassified or left out of the results, so pick yours deliberately before you start.
  17. For a newcomer I'd put the order roughly like this. First, get comfortable with the basics of your own station: a handheld that you can program from memory, a mobile or portable setup on at least VHF/UHF FM, and a simple way to run a backup power source. Second, take the FEMA ICS-100 and IS-700 courses, because they cost nothing and teach you the vocabulary the people in the EOC will be using. Third, sit in on nets before you try to run one. Listening to how a net control station handles check-ins, priorities and breaks teaches a lot. On net control specifically, a few habits are worth building. Use plain language and tactical call signs tied to the location or function (for example, a shelter or hospital name) rather than personal call signs. Remember that your legal station ID is still required at the intervals Part 97 sets. Do not use 10-codes or other jargon that a served agency may not understand; ICS leans toward plain language for a reason. Keep a log of who checked in, when, and what traffic was passed. Ask for emergency or priority traffic first, then routine check-ins. Hold the net frequency clear when something urgent is happening and move routine business to another frequency. For written messages, the ICS-213 form is a common standard for passing messages inside an incident, and the ARRL radiogram format is used for formal traffic that has to move between stations. The two are not the same, so it helps to know when your group uses which one.
  18. On the post-contest side, I'd separate the two tasks: submitting the contest entry, and updating your permanent log and QSL services. They use different files and don't need to happen in the same session. For submission, open the Cabrillo file in a text editor and read it before uploading. Check that the callsign and category lines match what you entered, that the QSO lines have the exchange in the order the sponsor expects, and that the band and mode fields aren't blank. Then upload through the sponsor's page and wait for the confirmation or robot reply, and read it. A confirmation that says the log was received is not the same as a log that parsed cleanly. If there are format warnings, fix the header or the exchange fields and resubmit before the deadline. For the permanent log, import the ADIF export into a copy first. Look at a sample of records for the right MODE and SUBMODE (FT8 and FT4 are the ones that tend to cause trouble), the right band, and the contest exchange fields. Then turn on duplicate detection and import into the real log. Then upload to LoTW through TQSL, with the correct station location selected. Next, push to QRZ and Club Log through the logger's built-in sync, if it has one. Watch for rejected QSOs in the response, because a bad callsign or an unsupported mode usually shows up there first. If the logger supports it, record each QSO's upload status so you can see what's been sent and what hasn't. One last tip: keep the untouched original ADIF and Cabrillo files somewhere safe. When a sponsor, LoTW or Club Log disputes something later, the original is your reference.
  19. On the test equipment question, here is what tends to give the most value for the money, roughly in order: A decent multimeter and a current-limited bench supply (or at least a fuse and series resistor while you bring up a new board). Many first-time failures are a reversed electrolytic or a solder bridge, and current limiting turns them into non-events. A dummy load, so you never have to test a transmitter into an antenna. A resistive load built from non-inductive resistors in parallel is fine at QRP power levels. Keep in mind that resistors heat up, so don't leave a 5 W transmitter keyed down into a few small 1/4 W parts. An RF probe for your multimeter, or a simple diode detector. It will not give you exact power, but it shows you whether a stage is working and lets you peak a tuned circuit. An oscilloscope with a bandwidth well above your operating frequency, if you can afford one. Use it with a 50-ohm termination on the dummy load to estimate power with P = Vrms² / R, taking Vrms = Vpp / (2 × 1.414). Be sure about the probe's compensation and the scope's input impedance before trusting any number. A NanoVNA or similar for filters, antennas and SWR checks. It is excellent for confirming that your low-pass filter's cutoff and passband loss are where they should be, and it can double as an SWR meter for the dummy load. For harmonics, a spectrum analyzer is ideal, but if you do not have one, you can compare the transmitter's output before and after the filter with a receiver that has an S-meter, or borrow time on a club's analyzer. Many licensing regimes set limits on spurious emissions, so check your local rules rather than guessing. On the uBITX in particular, it is a kit-based platform and a good one for learning, but the stock design is known in the community for spurious output on some bands, so verifying the filter set and output is a worthwhile step, not an optional one. For soldering, a temperature-controlled iron, flux, a clean tip and good lighting matter more than brand. Tin the tip, heat both the pad and the lead, then feed solder to the joint. For hand-built RF circuits, dead-bug or Manhattan construction on copperclad is fine, as long as ground connections are short.
  20. Start with the split between rules and plans. Part 97 is the regulation. It defines which bands and sub-bands each license class may use, which emission types are allowed where, and the power limits. The ARRL band plan is a voluntary coordination document. It suggests where weak-signal work, beacons, digital modes, repeaters and so on should live so they don't step on each other. Violating the band plan isn't a federal violation, but it's how you end up in an interference argument. Ignoring a Part 97 boundary is a violation, and you're responsible for it. For HF, the usual US pattern is CW and narrow digital modes in the bottom part of each band, with phone in the upper part. The General class phone segments start above the Extra-only portions on bands like 80, 40, 20 and 15 m. Tables change, so check the current Part 97.301 through 97.305 and the current ARRL chart. Don't rely on a memory of Novice-era or pre-2000s charts. Technician HF privileges are limited: CW on 80, 40 and 15 m, and CW, RTTY/data and phone on a segment of 10 m. General adds large chunks of every HF band, including 160 m, and Extra gets the full allocations. The WARC bands (30, 17 and 12 m) have no phone on 30 m, and by convention contests stay off all three. On digital, the FT8 and FT4 frequencies (for example, around 14.074 MHz on 20 m and 7.074 MHz on 40 m) are conventions, not regulations. They exist so everyone is in the same place. Rule changes to data limits on HF have been in the news, so check the current text before assuming old baud-rate limits still apply. On band edges, think about which sideband you're using. If you're on USB, as is the convention above 10 MHz, the signal extends upward from the dial frequency. At the bottom of a phone segment, such as the General 20 m phone edge, being right at the limit is fine, though leaving some margin for dial calibration is wise. At the top of a band you must keep the whole signal inside, including any splatter, so stay a few kHz down. On LSB, as is the convention below 10 MHz, the signal extends downward from the dial, so the lower edge needs the margin instead. A typical SSB signal is about 2.4 to 3 kHz wide, and a transceiver with a poorly calibrated display or an overdriven audio chain can spread further. Spurious or over-processed audio is why many operators keep 3 kHz or more of margin at the edge. That margin is not a rule, just good practice. 60 m is different from the other HF bands. It's channelized, not a continuous segment, and in the US it has five channels with USB specified. The commonly listed dial frequencies are 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz, with center frequencies 1.5 kHz above each. The power limit is expressed as effective radiated power, not as a PEP figure at the transmitter. The FCC rules for this band have been revised before, and new allocations from international conferences may change things, so check the current Part 97.303 text before operating.
  21. I would lean toward independent nodes with the Pi as an optional supervisor. The rule I would apply is that anything that can damage equipment or cause a bad transmission must fail safe without the Pi being alive. PTT, amplifier bias and antenna selection are the obvious ones. In practice that means a Pico or similar handles the time-critical and safety-critical logic: PTT sequencing with delays between relay and amp keying, a watchdog timer, and a default state at power-up. Choose relay logic so that the de-energised state is the safe one. For an antenna switch that might be a dummy load or a known-good antenna, and for PTT it is receive. The Pi then sends high-level commands such as 'select antenna 3' over USB serial, and the node can refuse commands that would be unsafe, for example switching a coax relay while the PTT line is active (hot switching). The same applies to a rotator controller. Put limit handling and motor timeouts in the microcontroller. If the Pi is the only thing that knows where the stop is, a hung script can drive the rotator into the stop. A simple rule such as 'stop if the potentiometer reading hasn't changed in N seconds while the motor is on' protects the motor and cables. For the link between the two, a plain line-based ASCII protocol over USB serial is easy to debug from a terminal, and you can add a checksum later. MQTT over WiFi is convenient for ESP32 nodes, but for anything that touches PTT, I would keep it on a wired link.
  22. On planning, don't treat the Moon as just 'up or down'. Sky noise matters a lot on 2 m, and it depends on where the Moon is against the galactic background. Distance also matters, as noted above. Planning tools such as the EME calculator by VK3UM can help estimate whether a given pair of stations has enough margin on a given day. Check the current version and how it treats the numbers you enter, because the result is only as good as your inputs. Community chat and logging pages such as ON4KST and HB9Q are where skeds are usually arranged. Their formats change, so look at how current users do it before you post. Before your first sked, test the station on your own. WSJT-X has an Echo mode that lets you hear your own signal return from the Moon with the expected round-trip delay of about 2.5 seconds. If you can't see your own echo, you won't help a distant station that has to dig for you. On 23 cm and above, measure Moon noise and Sun noise as a pointing and system check. This is a standard way to tell whether your feed, preamp and dish are doing what they should. Tracking precision scales with beamwidth. A rough rule is about 70 λ/D degrees for a dish. For a 3 m dish that is roughly 5 degrees on 23 cm but only around 0.7 degrees at 10 GHz, which is not much larger than the Moon's own half-degree disc. At 10 GHz you need good encoder resolution, a stiff mount and reliable pointing models. On 2 m a loose 5 degree error may be survivable, but it still costs signal. Before the first sked, confirm which period each station transmits in, since the cycle assignment is agreed between the two stations, and make sure Doppler correction is set up consistently on both sides.
  23. On grounding, follow the radio manufacturer's instructions, because the details vary by vehicle. The common advice is to take the negative lead to the battery negative or a chassis ground point designed for that purpose. Whichever you choose, keep the connection clean and tight. Poor grounds cause odd symptoms: resets, noise and unstable power readings. For vehicles with smart alternators or start-stop systems, check your vehicle manual and the radio's operating voltage range. Battery voltage can vary more than on older vehicles, so measure at the radio terminals while the engine is running and transmitting. If you see the voltage sag on transmit, look at wire gauge and connection quality before you blame the radio. One suggestion on fuses: use a proper in-line holder rated for the current and keep a couple of spares in the glovebox. A blown fuse is annoying, but it's the design doing its job.
  24. On keyer settings, there is a common mismatch to watch for: people set the keyer speed to match their copy speed, then find sending feels frantic. Sending slightly slower than you can copy is usually cleaner, and nobody on the other end minds well-formed code at a modest speed. Iambic A versus B is worth testing both ways. The difference is what happens when you release the paddles mid-squeeze, and one mode will feel more natural to your hands. Whichever you pick, stay with it long enough for muscle memory to form. For QSO practice, a good ladder is to listen first, then answer a CQ using a canned exchange (name, QTH, rig, weather), then gradually go off-script. The canned part gives you a safety net while you get used to the pace. Many people find that the first real contact goes better than expected because the exchange is so formulaic, and the second goes worse because the other operator wanders off-script and your head copy has to keep up. Straight key versus paddle is mostly a preference. Sending with a straight key can help you internalize rhythm and spacing, while paddles make sustained higher speeds easier on the hand. Neither replaces copy practice, though. Sending speed and receiving speed develop somewhat independently, so schedule time for both.
  25. I'd add a section on finding reliable information, because repeater listings go stale. Directories like RepeaterBook and the lists kept by regional coordination bodies are useful starting points, but they depend on volunteer updates. A tone may have changed, a machine may have gone down, or an owner may have restricted access without anyone updating the entry. If the listing gives a club or trustee contact, check there before assuming you're doing something wrong on the air. The open versus closed distinction also needs explaining properly. An open repeater is available to any licensed operator who follows the rules. That doesn't mean there are no rules. A closed repeater limits use to members or to people who have asked for access. Under US rules, a repeater owner can restrict who uses the machine. If you hear a repeater and nobody answers calls from outside the group, that may be why. Many clubs ask for support in the form of dues, donations or volunteer help, and that is how the site rent, power bill and maintenance get paid. On coordination, a frequency coordinator exists to reduce interference between repeaters in an area. In the US, a coordinated repeater is generally in a stronger position than an uncoordinated one if there is a dispute. That's the practical reason for a club to coordinate before putting a new machine on the air. It's also why new users shouldn't program a frequency they found somewhere without checking whether it is a repeater at all. Last tip for the checklist: when a repeater won't open, check offset direction first, then tone, then power and antenna. Most of those new-user problems come down to one of those four.

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.