Everything posted by Mod_Chrissy
-
Hamfest season planning: swap meet tactics, club tables, VE sessions, and what to throw in the trunk
Good rundown. One thing I'd add for buyers is to check the stuff that's easy to overlook: the power cable and fuse holder, mic connector, and whether the rig has all of its feet and hardware. For older HF gear, a rig that powers up isn't necessarily a rig that transmits properly, so if the seller is willing, a quick check into a dummy load with a wattmeter tells you a lot more than a lit display does. If it's a tube amp or anything with high voltage, treat it carefully and be realistic about what you can verify in a parking lot. It's often better to pass than to buy a project you can't evaluate. Also, carry cash in small bills. Plenty of sellers can't take cards, and haggling goes smoother when you can offer an exact amount.
-
Planning a homebrew QRP station from scratch: build order, test gear, and what to check before you key up
One thing to know before the direct conversion receiver goes into the plan: it won't behave like a superhet. Because it has no IF filter, the audio stage does all the selectivity, so strong AM broadcast stations can break through, and you hear both sidebands at once. If the receiver breaks up near a strong station, a simple band-pass filter ahead of the mixer often makes a big difference, and so does a properly designed audio low-pass or CW filter. Hum and microphonics are common as well. If tapping the case produces noise, the mixer or a high-gain audio stage is probably picking up vibration or stray coupling. The Pixie is fun for what it is, but it's also a good lesson in why a separate receiver and a proper TR scheme matter. A Tuna Tin 2 into a dummy load, monitored on a separate receiver, teaches more about keying and spectrum than most first kits. Listen for key clicks too. A hard-keyed oscillator or final can splatter, and simple RC shaping on the keying line is cheap to add. On the power supply, yes to the fuse and the reverse-polarity protection, and I'd add one more thing: use a series resistor or a current-limited bench supply for first power-up on any new board. Raise the current gradually while watching for unexpected draw. For a keyer, an iambic keyer on a microcontroller or a simple kit is a low-risk project that gives you a fast result, and it's a gentle way to practice SMD soldering if it uses any. Check regulations for your country on spurious emissions before you go on air, since the limits vary.
-
Rate vs. multipliers: how do you decide when to stop running and go hunting, especially with SO2R?
On the trigger question, absolute rate matters less than rate relative to what the band can give you right now. A drop from 120 an hour to 90 might be normal as the band thins out. A drop to 90 with a clean frequency and a good signal might mean you've worked most of the people who can hear you. In that case it's a good time to go multiplier hunting. I'd also keep two lists in mind: stations you still need, and stations you could work later without losing anything. If a multiplier is on a band you'll revisit during the contest, it can wait. If it's on a band about to close, or an opening you may not get again, work it now. Check whether your contest has per-band multipliers, because that changes how many times you should expect to chase the same entity or zone. For SO2R, the second radio is most valuable when it is not simply a second run position. Running two frequencies at once can work in a high-rate contest, but the operator load rises quickly and accuracy suffers. A more conservative use is running on radio 1 and keeping radio 2 on a multiplier band, grabbing spots in the gaps. The key habit is to make every switch deliberate: know which radio has focus, know which keyboard macro you're about to send, and don't call a mult if you can't hear the full call.
-
Which radio mods are worth doing? Receive, TCXO, power, noise, and where the legal line sits
I'd put "measure first" at the top of the list. A lot of people buy a filter, a TCXO, or a fan and never establish a baseline. If the complaint is noise on HF, check the antenna system and the house first, because a DSP filter can't fix a bad noise environment very well. If it's overload on VHF, a bandpass or notch filter at the antenna port may do more than any board-level work. Without a before-and-after test, you can't tell whether the change helped. On expanded receive, I'd keep separate lists for "can the radio hear it?" and "is it good at it?" Many cheap radios can tune a wide range, but sensitivity, image rejection, and selectivity vary a lot across that range. A scanner or SDR may do a better job for monitoring, and your ham radio can stay as the transmit rig.
-
Planning a contest year: which events to start with, what the exchanges look like, and how to avoid log-submission headaches
For a first-year calendar, pick events by exchange complexity, not by prestige. CQ WW or WPX is a good starting point because the exchange is short and the band is full of people calling. A state QSO party is another low-pressure option: you can operate for an hour or two and still contribute, and you learn how multipliers work without running a full-time effort. I'd put Sweepstakes later in the list. The exchange is long, and getting the precedence, check and section right in a pile-up takes practice. Field Day is a good place to practice copying exchanges at a relaxed pace first. For logging, make sure the software knows each contest's exchange fields before the starting gun, not during the first hour.
-
POTA activation checklist: park refs, the 10-QSO rule, spotting, two-fers and logging
A tip on spotting and hunter behavior: pick a frequency that is clear before you spot, and listen for a minute or two first. Nothing wastes time like calling CQ on top of a net. Once you are spotted, hunters often arrive in a pile, so keeping exchanges short helps. A callsign, a signal report and the park confirmation if asked is plenty. For hunters, check the spot's age and the comment before you call. A spot from an hour ago may be stale. If you hear a P2P station, it is polite to wait for the activator to finish a QSO, and many activators like to take park-to-park calls out of turn, so listen to how they run the pile-up. For logging, read your ADIF before uploading. A mismatched park reference in one line is easier to fix on your computer than after upload, when you have to chase corrections.
-
Getting my first ham license: how do I find a test session, what do I need to bring, and what should I study?
Here's the process in a sensible order. Study first, then book. The Technician exam is 35 multiple-choice questions drawn from a public question pool, and the passing score is 26 correct. The pool is revised on a multi-year cycle, so make sure your book or app matches the pool in effect on your exam date. HamStudy and current editions of the ARRL manual state which pool they cover. Finding a session. Exams are run by Volunteer Examiners (VEs), who are licensed hams accredited through a Volunteer Examiner Coordinator (VEC). The ARRL and HamStudy both have session finders where you can search by location, and many local radio clubs post their own schedules. Some sessions are walk-in. Others want advance registration so they know how many exam sets to bring, so check the listing or email the contact. Several VE teams also run remote exams by video call, which helps if there's nothing nearby. FRN. The FCC Registration Number identifies you in the FCC's systems. You get one for free by registering in CORES, the FCC's registration system. Do this before exam day and bring the number, because the VEs need it to file your application. Enter your legal name and mailing address exactly as they appear on your photo ID. Mismatches cause delays. Fees. Each VE team sets its own exam fee to cover its costs, and it's usually modest. It varies by team, and sometimes by whether you pay in cash or electronically, so the session listing or the contact person should tell you. The FCC's own fee situation for amateur licenses has been a moving target, so check the FCC's current fee page rather than trusting a forum post, including mine. Bring: photo ID, your FRN, the fee in an accepted form, a couple of pencils, and a simple calculator if you want one (teams differ on which calculators are allowed, so ask). Also bring a working email address, because it's required on the application.
-
Phonetics on the air: when to use the ITU/NATO alphabet, when to improvise, and how to handle names, numbers and nets
On the alphabet itself: the ITU, ICAO and NATO versions are essentially the same list, and it is the one to default to. The words are Alfa, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu. The spellings "Alfa" and "Juliett" are deliberate, so that speakers of other languages pronounce them correctly. The list was designed and tested so that the words stay distinguishable across languages and through noisy, narrow-bandwidth channels. That is the main reason to prefer it over improvised words. Improvised phonetics ("Kilowatt", "Lovely", "Mexico", and so on) are common on the ham bands and usually harmless in a relaxed chat on a clean band. The problem shows up when conditions get bad or the other station doesn't share your first language. A word that is obvious to you may not be a word the listener knows, and you've lost the main advantage of a phonetic: a word the listener already recognises. Older lists, such as the "Able, Baker, Charlie" style from the mid-20th century, also still turn up. Sticking to the standard list avoids all of this, and DX operators will be used to hearing it. A practical approach is to give the whole callsign phonetically at least once, and again if asked. If a particular letter keeps getting copied wrongly, you can add a second word, but make it a clear, common word and say it as an addition ("Bravo, as in Bravo, Bravo") rather than inventing a replacement. If you operate in the US, the FCC rules allow phonetic identification but do not require it. Other countries differ, so check your own licence conditions.
-
Studying for the Amateur Extra (Element 4): where do the 50 questions get hard, and how do you prepare for the theory?
For most people the pool splits into two kinds of questions: ones you can answer from a short formula, and ones where you just need the right concept. Treat them differently. Formula questions are worth drilling because a calculator is allowed. Examples include op-amp gain (inverting gain is -Rf/Rin, non-inverting is 1 + Rf/Rin), Q as center frequency divided by bandwidth, and FM modulation index as deviation divided by modulating frequency. Carson's rule, bandwidth ≈ 2 × (deviation + highest modulating frequency), is another one worth knowing. Once you know the formula, the question is mostly arithmetic. Keep a one-page sheet of them and re-derive each rather than only memorizing the final form. The concept questions are where understanding pays off. Know that a Butterworth response is maximally flat in the passband, while Chebyshev trades passband ripple for a steeper skirt. Know that a Pierce oscillator uses a crystal, while Colpitts uses a capacitive divider and Hartley a tapped inductor. Know how a transistor's alpha and beta relate, and what a mixer's third-order intercept tells you about strong-signal performance. If you understand why the circuit behaves the way it does, rewording in the question will not trip you up. One caution: the pool is revised on a cycle, so make sure your study guide and practice tests match the pool in effect on your exam date. The VEC or the exam session can tell you which pool is current.
-
Before the first on-air contact: how do you verify a homebrew QRP transmitter (Tuna Tin 2, Pixie, BITX or uBITX)?
Good list. I'd stress the attenuator point for anyone using an SDR dongle as a poor man's analyzer. If you connect even a watt directly to the input, you can damage it, and a milliwatt-level signal can already overload it. Use a known attenuator chain, such as a few fixed pads or a tap from a directional coupler, and keep the numbers written down so you can add them back when you read the harmonic levels. Also confirm that what you see is real. If the third harmonic seems to move in level when you add or remove attenuation, the receiver is overloading. A correct reading should drop dB for dB as you add attenuation. Images and aliasing in cheap SDRs can show up as phantom signals, so check by moving the tuning slightly or by changing the sample rate. On the Pixie, don't expect miracles from the stock circuit. It works as a learning project and for very short-range CW, but a low-pass filter on the output makes it a much better neighbor on the band.
-
Planning a first SOTA activation (and how chasers can help): references, points, spotting, kit and logging
For a first outing, I'd choose a drive-up or short-hike summit with a clear activation zone and a well-documented route. That way the radio problems are the only new ones. Make the plan simple: alert posted a few days ahead, a realistic time window and one fallback band. If you're on 2 m FM, call CQ on the national calling frequency or the one you advertised in the alert, and ask a local friend or club to listen for you. If four contacts are slow to arrive, move up to HF or try a different spot. One logging tip: write contacts on paper as you make them, even if you plan to use an app later. Cold fingers, wind and a dying phone battery all make digital logging harder. Transcribe the log to the database at home while the details are still fresh, and double-check the summit reference field, because a typo there can invalidate contacts.
-
Go-kit layers: what belongs in the radio bag, the vehicle kit, and the home plan?
On power, do the watt-hour math before buying anything, because the numbers settle a lot of arguments. A 12 V 20 Ah LiFePO4 battery is roughly 256 Wh. An HF rig that draws about 1.5 to 2 A on receive will run for many hours of listening. At 100 W on transmit it can pull 20 A or more, so that same battery drains quickly if you transmit often. SSB and CW have low duty cycles, which helps, and dropping to 20 to 50 W often costs you very little in practice. Digital modes with long transmit periods are harder on a battery. For solar, a panel's rated watts are a best case. Angle, haze, temperature and wiring losses mean you should plan for well under the rating. A 100 W folding panel will not give you 100 W for most of the day. A charge controller matters too, and MPPT types usually harvest more than cheap PWM ones, especially when the panel voltage is well above the battery voltage. Check that the panel's open-circuit voltage stays inside the controller's limit, particularly on a cold day. Test the whole chain at home: panel, controller, battery, fuse, rig. Cables, polarity and connector mismatches are the things that fail first. Label everything. Also check the airline and shipping rules for lithium packs if you ever fly with a kit, since they restrict capacity per battery. For antennas, simple wins. A resonant dipole at a decent height and a good feedline will usually beat a clever compromise antenna. Write the cut lengths for your target bands on the bag itself.
-
One master log, several programs: keeping N1MM+, WSJT-X and Log4OM from fighting each other (ADIF, Cabrillo, LoTW, QRZ, Club Log)
For CAT sharing, the main rule is that only one program can open a serial port at a time. There are three common ways to get around it. A rig-control server such as FLRig or Hamlib's rigctld. The logger, WSJT-X and anything else connect to it over a network socket instead of opening the COM port directly. WSJT-X can use Hamlib's NET rigctl option, and many loggers can use Hamlib or FLRig as well. Check your version's documentation.A virtual serial port splitter. It works, but it adds a layer that can fail, and it can add latency.A hub program, such as DXLab Commander in the DXLab Suite, which owns the radio and shares frequency and mode with the other DXLab applications and, through its interfaces, with others.Rotator control follows the same pattern. Hamlib's rotctld or a dedicated rotator program owns the controller, and the logger sends a bearing to it. Most loggers can turn the antenna toward a station you've called or clicked on the band map. That's useful, but test it before the contest. For contest day, a few points: Dupes. Check what the contest counts as a dupe. Many contests work a station once per band per mode. Others, such as ARRL Sweepstakes, allow one contact per station regardless of band. Make sure the contest selected in N1MM+ matches the rules you're operating under. Don't let the logger's dupe sheet make this decision for you.Band map spots. Cluster and Reverse Beacon Network spots on the band map may count as assistance in some categories. Single-op unassisted usually means no spots at all, so check the category before you connect the cluster.Multi-computer networks. Clocks must agree, and every station must use the same contest, the same operator and station names, and the correct band and mode flags. A wrong PC clock produces bad timestamps in the merged log.Cabrillo. Before you submit, read the generated file in a text editor. Check the CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-POWER and CATEGORY-MODE lines against what you actually did. Make sure each QSO line has the right frequency, mode, UTC date and time, and exchange fields. Most programs let you edit the header and re-export, so fix it there.Submission. Most sponsors take either a web upload or an email to a log robot. Read the rules for the deadline, the file naming and the confirmation message. Keep the confirmation and your original files until the results are published.Also, don't upload contest QSOs to LoTW or Club Log until you've finished cleaning the log. Removing dupes and fixing mistakes is easier before the QSOs go out.
-
HF shack planning: radio choice matters less than the power, grounding and RF-environment decisions around it
Worth adding a few specifics on the grounding side, because 'ground it' gets thrown around as if it were one thing. For a typical home station, the safety question is whether lightning or a fault can put a dangerous voltage on the gear or the operator. The usual approach is to disconnect antennas from the radios when not in use, put surge protection or a grounded entrance panel where the cables enter, and tie that panel's ground to the building's main grounding electrode system. Separate, unbonded ground rods can leave different parts of the system at different potentials during a surge, which is why bonding them together matters. Because details vary with jurisdiction and house wiring, it's worth reading your local code and getting an electrician to check the mains side. For RF problems, the cure is often different: common-mode chokes on the coax at the radio and on USB, CAT and audio cables, and sometimes at the antenna feedpoint. A long ground wire to a rod outside can act as a radiating conductor on the higher bands, so it isn't always a cure. If RF is getting into a mic, keyer or computer, treat it as a common-mode current problem first. One more small thing: on DC, check your connectors and fuse ratings. With a 100 W rig it is the crimp quality and the connector, rather than the wire gauge, that often causes a voltage drop under transmit load. Measuring voltage at the radio during a key-down is a quick check.
-
How do you separate real ham radio news from rumor? Tracking rigs, firmware, FCC/ARRL items and band conditions
Good framework. I'd add a rule for new gear: wait for independent measurements before trusting any performance claim. Sherwood-style receiver tables and lab tests from ARRL's Product Review are useful, but only for models they've actually measured, and a marketing line like "improved dynamic range" means nothing without numbers. Look at third-order dynamic range, close-in blocking, and how the radio behaves on a crowded band, not just sensitivity. On firmware, one practical point: read whether the update touches the radio's main CPU, the DSP, the front panel, or all three, because some rigs need several separate files. Make sure the power supply is stable before you flash and don't touch the radio mid-update. A bad flash is a rare failure, but it's the kind you can't fix from the operating chair.
-
Planning a 24-hour EMCOMM field station: generator, LiFePO4, solar, and where noise and grounding bite
Your power math is reasonable, but I'd budget for the battery chemistry's behavior as well as its capacity. LiFePO4 holds a fairly flat voltage, around 13.2 to 13.3 V under modest load, then falls off quickly near the end. Many batteries also have a BMS that disconnects abruptly at its low-voltage or overcurrent limit, so the radio doesn't gradually fade, it just goes dark in the middle of a net. A small DC voltmeter or shunt-based monitor at the distribution block is worth having, and so is a plan to swap or recharge before you are down to the last 10 to 15 percent. Also check that the BMS continuous rating covers your peak draw with margin once the 100 W rig and anything else on the bus are all running. For wiring, fuse close to the battery terminal, use a fused distribution block with each branch protected for its wire gauge, and keep high-current runs short. 12 AWG is usually fine for a 20 A radio feed over a short run, but check the voltage drop at the radio when transmitting. A radio that sees 12 V on peaks may distort or fold back power, and it will look like an antenna problem. Whatever Powerpole orientation your group uses, label it on every cable, because the mistake you're guarding against is reversed polarity from a borrowed cable. One more caution on solar: LiFePO4 should not be charged below freezing unless the battery has low-temperature charge protection or a heater. Cold-weather deployments need either that or a different plan. And make sure the controller has a lithium profile, not just a generic setting for lead-acid.
-
Ham radio news thread: how do you separate confirmed announcements from rumor, and what should we post here?
For band openings and solar cycle news, I'd suggest pairing any "the band is open" post with the data behind it. The usual numbers are the solar flux index, the A and K indices, and whether there has been a recent flare or geomagnetic disturbance. NOAA's Space Weather Prediction Center publishes these, and they explain a lot. A high K index can wipe out an HF path that looked promising an hour earlier, especially on high-latitude routes. Then there's confirmation from the bands themselves. Beacon networks, PSKReporter, the Reverse Beacon Network, and WSPR maps show what is actually propagating right now, rather than what a prediction says should work. Reports are more useful if they include UTC time, grid squares, mode, and approximate power, since a path that works on FT8 at low power says something different from one that works on SSB. One caution: a single spot can come from a skimmer misdecode, a mislabeled callsign, or a local station. If a rare opening matters to you, look for several independent reports before treating it as real.
-
QSL strategy: LoTW, eQSL, Club Log OQRS, bureau or direct? What counts and what's worth your time
For DXCC, I'd put LoTW first and treat everything else as a supplement. It's the one electronic method that counts, and the awards tools can see it right away, so uploading regularly is the biggest time saver. The catch is that you have to keep your callsign certificate current and your station location details correct in TQSL. The common failure isn't the upload; it's a location mismatch, such as the wrong DXCC entity, grid or zone, which can make a good QSO fail to match or get credited incorrectly. Another tip: once a DX station is in Club Log, check whether they also upload to LoTW. A lot of DXpeditions do, which means you may not need a paper QSL at all. Paper still matters when a station isn't on LoTW or when you want the card itself, but check the digital options before spending postage. For direct requests, read the QSL instructions carefully and follow them exactly. Some stations want a specific amount of cash, some want a pre-printed label, and some say to use OQRS only. Sending the wrong thing is how cards stall.
-
Studying for the Technician exam (Element 2): how do you actually work through the 35-question pool?
On the topics people often underestimate: repeaters and RF exposure both look easy and then cost points. For repeaters, learn the vocabulary as well as the idea. The repeater listens on one frequency (its input) and retransmits on another (its output). The difference is the offset, and the standard offset on 2 meters is 600 kHz, with the direction (plus or minus) depending on the part of the band. On 70 cm the usual offset is 5 MHz. Many repeaters require a CTCSS (PL) tone before they'll open, and if you can hear the repeater but can't get in, a missing or wrong tone is a likely cause. Also know simplex, what a repeater directory is for, and the basic courtesy of listening before you transmit and keeping calls short. For RF exposure, you don't need to memorize the numeric limits so much as the logic: the maximum permissible exposure depends on frequency, power, duty cycle (how much of the time you transmit), distance from the antenna, and antenna gain. Several questions ask what you must do to stay in compliance, or what reduces exposure: lower power, a shorter transmit time, more distance, or relocating the antenna. Treat these as reasoning questions. The safety section (T0) is also mostly common sense once you read it: don't work near power lines, ground your station properly, use a safe approach to tower and antenna work, and pay attention to battery hazards. Read the explanations with each question you miss, because the rationale makes the right answer easier to remember than the answer alone. For format, I'd use both. A manual is better for the why, and the practice-test sites are better for finding what you don't know. Just check that the practice site says which pool it's based on.
-
Starting out with 5 W portable QRP: rigs, antennas and batteries that matter most
For power, I'd add a note on voltage sag and cut-off. A radio with a minimum operating voltage may behave strangely, or drop output, when the battery gets low, and that can look like an antenna problem. Measure the battery voltage under transmit load if the radio has a meter, not just at rest. LiFePO4 holds a fairly flat voltage through most of its discharge, which is nice for QRP, but it also means the voltage does not warn you before it falls off. A small voltmeter or a rig with a built-in readout gives you that missing warning. Also check the charger matches the chemistry. A charger meant for lead-acid or ordinary lithium-ion may not charge LiFePO4 correctly. If you're deciding between a KX2/KX3 and a smaller CW rig, the question is how much you want to operate SSB or digital. If you only plan on CW, a smaller radio may save weight and money. If you'd like to try several modes, a multimode rig gives you more room to experiment. Either way, a decent log of what you worked with each antenna will tell you more than any spec sheet.
-
Nets and special event stations: how do you get the most out of checking in and working them?
One thing that helps new check-ins is knowing the difference between a net's format and its culture. The format is on the net's web page: who runs it, what it is for, and whether it is directed or open. The culture you pick up by listening. Some nets want only a call sign and a location. Others expect a name and a short comment. If you listen through one full cycle before you call, you will usually hear how net control handles late check-ins, traffic, and signoffs. On the SKYWARN side, the key point is that reports should be observations, not guesses. Say what you saw, where you saw it, and when. A location like "two miles north of the intersection of Main and Oak" is more useful than "over by town." If you do not know what is reportable, ask your local NWS office or the net's organizers for their criteria before the next severe weather event, because the thresholds can vary from one area to another.
-
Digital modes and weak signal setup: where decode thresholds, time sync and audio levels actually decide your results
For interfaces, isolation matters more than brand. A lot of 'my decodes are weird' reports turn out to be ground loops, RF getting into the audio line, or a radio's USB audio and USB serial sharing a cable that picks up hash. If you hear birdies or the waterfall shows a comb of lines, try a ferrite on the USB lead and move the interface away from the antenna feedline before replacing anything. Isolation transformers on the audio lines are cheap and often fix exactly this. On the two-mode question, the answer depends on your station. If you run low power or have a compromise antenna, FT8 gives the best return on effort because the 15-second cycle and narrow bandwidth let you work stations that voice or PSK31 would lose. For a second mode, JS8Call is a strong pick if you want something closer to conversation, relayed messages and signal reports, while keeping similar sensitivity. If your station is more about emergency communications, Winlink with VARA or ARDOP is the more practical choice over any chat mode.
-
POTA basics: getting from a park reference to 10 logged QSOs (activator and hunter notes)
On two-fers and roving, the key point is that each park is evaluated separately. A two-fer is a location that sits inside two (or more) POTA references, for example a state park overlapping another designated area. You work one set of contacts, but each QSO is logged against each reference. Each park needs its own 10 QSOs, and the same contacts can count toward both if you log them correctly. Many loggers let you enter multiple park references on one QSO, but check how yours exports, because a malformed multi-park field is one of the more common reasons a log fails to match. For a rove, plan the UTC day, not your local day. Each park is a separate activation with its own log, so it helps to keep separate ADIF files, or to confirm that your logger splits them cleanly. Also allow for setup and teardown time. It is easy to underestimate how long it takes to reach 10 contacts when band conditions are poor, so have a fallback plan, such as a second band or mode, before you decide to move on.
-
Newly licensed? Let's talk first QSOs, first radios, and what to skip buying
On what to buy first, I'd say hold off on anything big until you know what part of the hobby grabs you. A decent dual-band handheld, a better antenna for it, and a way to program it (software and a cable, or the radio's menus if you're patient) covers a lot of ground for local FM. Cheap handhelds work, but they can be easily overloaded by strong nearby signals and their stock antennas are weak. If you can, ask a club member to let you try a few different radios before you decide. If HF is the goal, plan the antenna before the transceiver. A modest radio on a well-built wire antenna usually beats a better radio on a poor one. Good coax, a proper connector install, and a way to check SWR matter more than extra bells and whistles. Also remember that Technician-class operators in the US have limited HF privileges, including CW on parts of 80, 40, and 15 meters and voice on a segment of 10 meters. So the upgrade path to General is worth thinking about early if HF voice is what you want. One more habit worth building from the start: identify with your call sign at the end of a contact and at least every ten minutes during one, and keep a simple log even if nobody requires it. You'll appreciate the record later.
-
Building a ham go-kit that actually works: power, antennas, family plan, and what to do beyond the amateur bands
I'd add that it's worth separating "nice to have" from "single point of failure". If everything depends on one battery, one charger or one antenna, a single fault can end your operation. A spare coax jumper, a few adapters and a backup antenna that's very different from your main one (say, a simple wire dipole and a mag-mount) cost little and cover most connector and feedline failures. On the unlicensed services: it's easy to buy cheap blister-pack radios and assume they'll cover a few miles. Terrain, buildings and low power make real range much shorter. If a household is serious about it, GMRS with a proper license and a decent antenna is a step up, but check that what you buy is actually type-accepted for the service. MURS is a good option for rural properties where you can run an external antenna, and it's unlicensed. Whatever you pick, test it over the paths you actually care about, such as home to a relative's house or to the usual meeting place. As for drills, a simple one is to turn off the mains for an evening and see what you reach for. Then write down what was missing, what was in the wrong bag, and what you couldn't operate in the dark. That list is your real shopping list.