Everything posted by Mod_Nancy
-
Q codes and ham shorthand: what QRM, QRL, QSY, K vs KN, SK and RST actually mean
Your list is mostly right. The main thing to know is that Q codes began as questions and answers. Sent with a question mark, a code asks; sent without one, it states or answers. So QRL? means "is this frequency in use?" and a plain QRL answers "yes, it's busy." Many operators send QRL? or ask "is the frequency in use?" before calling CQ, so they don't step on an existing conversation. QSY works similarly: "QSY 14.250" means "let's move to that frequency." A few refinements. QRM is interference from other stations or man-made sources, while QRN is natural noise such as atmospheric static from thunderstorms. QRP is both "low power" and "please reduce power." By common convention, QRP operating is about 5 watts output on CW and 10 watts PEP on SSB, though the term itself doesn't define a number. QRO is the opposite: high power, or "increase power." QRT means "I'm stopping transmission," which is why you see it used as "going QRT" when someone signs off for the day. QRZ? means "who is calling me?" and is handy when you only caught part of a call sign, or several stations answered at once. QSL means "I acknowledge receipt" or "I confirm," and a QSL card is a written confirmation of a contact. QSO is simply a two-way contact. QTH is your location, so "my QTH is Denver" works fine. QSB is a signal that is fading in and out. For the structural bits: CQ is a general call to any station. DE is French "de," meaning "from." A typical CW call is "CQ CQ CQ DE W1AW W1AW W1AW K," which reads "calling anyone, this is W1AW, go ahead." K means "go ahead, anyone." KN means "go ahead, but only the station I'm working," which tells others not to break in. SK signals the end of a contact. Separately, in conversation "silent key" (also SK) refers to a ham who has died, so context matters. On 73 and 88: 73 means "best regards," and it is already plural in tradition, so "73s" is usually considered redundant. 88 means "love and kisses," used between friends or spouses, and often as a joke.
-
No TX, no RX, or both? A triage order for dead rigs (and where it usually goes wrong)
The order is good. I'd add one thing to step 4: when the SWR protection is suspect, put the rig into a known-good dummy load and compare its SWR and power readings against an external wattmeter. Protection circuits rely on a directional coupler, usually a small toroid or a pair of detector diodes feeding a DC amplifier. If a detector diode has gone leaky or a trimmer has drifted, the radio can believe it sees high reflected power and cut output when nothing is wrong. That looks exactly like a weak or dead transmitter. On blown finals, the dangerous mistake is swapping the transistors and applying full drive. Finals rarely die alone. Common causes are a bias circuit that has drifted or failed, a failed driver, a poor supply, an open or damaged protection path, or a parasitic oscillation. Before applying RF, check the bias network and set the idle current to the service manual figure with no drive. Use a current-limited supply and bring the voltage up gradually. Also treat replacement devices from open marketplaces with caution, since relabelled and counterfeit RF transistors are a known problem, and a part that does not match the original's gain and ratings can destroy itself quickly.
-
Part 97 compliance Q&A: ID timing, third-party traffic, power limits, RF exposure, remote control and renewal
I'll take 5 through 9, and I'd suggest the checklist link to the eCFR text instead of paraphrasing it. This isn't legal advice. RF exposure (§97.13(c) and Part 1): you are responsible for making sure your station complies with the FCC's maximum permissible exposure limits. The first step is to determine whether your station is exempt from a routine evaluation. That depends on power, band, antenna height and how close people can get to the antenna. If you aren't exempt, you do a calculation or a measurement. Exemption doesn't mean the limits don't apply. The reference most hams use is OET Bulletin 65 and its amateur supplement. Duty cycle matters (SSB and CW average well below the PEP number), as does the difference between controlled exposure (the licensee and family who know about it) and uncontrolled exposure (neighbors, the public). For a club, the places to look are the repeater site and any antenna people can walk up to. Spurious emissions (§97.307): the standards are phrased as attenuation below the mean power of the fundamental. For example, HF transmitters installed after 2003 must meet 43 dB below, and VHF has a tighter requirement, 60 dB for higher-power transmitters. An amplifier that is overdriven, poorly filtered or aging can produce harmonics and splatter even if the exciter is clean. There are also external-amplifier certification rules (§97.317), including exceptions for individually built amplifiers. Even if you build your own, it still has to meet the emission standards. Control (§97.201, §97.205, §97.213, §97.109): there are three types of control. Local control means the control operator is at the station. Remote control means the control operator operates through a control link from another location, and the rules require safeguards such as a transmit time limit if the link fails. Automatic control, such as a repeater with no control operator at the control point, is allowed only for specific stations, and the licensee must still have a designated control operator who can shut it down. Auxiliary stations (§97.201) are point-to-point links within a system of cooperating stations, such as a link between repeaters, and are limited to certain bands above 222 MHz plus parts of 2 m and 70 cm. Check the exact allowed segments. Enforcement: the process typically starts with a warning or a Notice of Violation and can escalate to a Notice of Apparent Liability for a monetary forfeiture, a cease-and-desist order, or license revocation or other sanctions after a hearing process. You, as licensee, are responsible for the operation of your station (§97.103(a)), and you have to make the station and its records available for inspection by an FCC representative on request. Don't treat ARRL Official Observer notices as FCC enforcement. They're courtesy notices. When you're the victim of interference, keep dates, times, frequencies and recordings instead of confronting the other party yourself. Term and renewal (§97.25 and the licensing rules in §97.21): amateur licenses are issued for 10 years. You can file for renewal within 90 days before expiration, and if you miss the expiration date there is a grace period of two years. During the grace period you can renew without retesting, but you can't transmit until the renewal is granted. After the grace period ends you have to take the exam again. You also need to keep your mailing address and email address current in the FCC's database, and you need an FRN. Fees have changed in recent years, so check the current FCC fee schedule instead of relying on a number from a forum post.
-
Operating etiquette check: CQ calls, breaking in, nets, and sharing a frequency
On nets, I think the biggest difference between a smooth one and a messy one is how clearly the opening is stated. If net control says what the net is for, how to check in, and whether it is taking calls by region, suffix, or in any order, most people will follow along. Check-ins tend to go wrong when several people answer at once. Waiting a beat after the call for check-ins and then giving only your callsign, using phonetics, makes list-taking easier. Net control also needs a good way to handle priority traffic. If there is a real emergency, say so right away, with your callsign and the nature of it, and let net control direct things. For a routine message or a question, wait to be called. If you are not sure whether to check in, listen for a round or two and ask for the procedure rather than guessing. That is usually the least disruptive way to join.
-
Hamfest game plan: swap meet tactics, VE sessions, and getting more out of your local club
On the club side, the meeting itself is often the least valuable part. The value is in what happens around it. A lot of clubs run informal Elmer time before or after the program, where someone will happily look at your SWR problem or help you figure out why your logging software won't talk to the rig. If your club doesn't have a formal Elmer program, ask. Often a couple of experienced members will be glad to be pointed at someone who wants help. Club projects are also a great way to learn without risking your own money on a mistake. Group builds like a J-pole, an EFHW, or a simple QRP kit let people at different skill levels work side by side. Portable go-kits, a repeater controller upgrade, or a Field Day antenna plan can all work as projects too. Field Day itself usually lands in late June, and the ARRL publishes the current rules each year. It's a good way to try HF, logging, and setting up antennas without needing a station of your own. One practical tip: if a club is thin on volunteers, take a small job rather than a big one. Running the sign-in table or hauling the coax reel gets you introduced to everyone, and it's easier to say yes to than a leadership role.
-
Stuck between 10 and 15 wpm: what actually moves the needle on the way to 20?
One thing to add on paddles and settings, since sending problems can look like receiving problems. If your sending is uneven, you will have trouble recognizing the rhythm of properly timed code when you hear it. A few things to check: Weight and ratio: leave the dah-to-dit ratio at around 3:1 unless you have a reason to change it. Odd weighting makes code harder to copy.Paddle spacing and tension: too light and you get false double dits, too heavy and your hand tires and the timing gets ragged. Adjust until the contacts feel firm but not stiff.Speed: set the keyer speed to a pace where you can send perfectly. Cranking it up will reward you with errors, not progress.Straight key or bug: nothing wrong with starting there, but the habits are different from iambic paddles, so pick one for the main practice block.For contests, a mini contest or a sprint-style event is a good first step. They are short, the exchanges are fixed, and you can learn the format on a Saturday afternoon without committing to a whole weekend. Run a pileup simulator like Morse Runner beforehand if you want to practice exchanges and copying callsigns under pressure. Set it to a speed a little under what you think you can handle, because real stations will often be faster than you expect.
-
First repeater programming checklist: offsets, tones, linking modes and etiquette
Etiquette on a plain FM repeater is mostly about leaving room for other people. Listen before you transmit, then give your callsign. You can also say you are monitoring or looking for a contact, which is more useful than saying only "testing". Keep transmissions short, and pause briefly between overs so someone with a more urgent need can break in. The pause also matters because of the time-out timer: owners set a limit on continuous transmission, and in many cases the courtesy tone tells you the repeater has reset. That limit varies by system, so don't assume a particular number of minutes. Over-long conversations are best moved to simplex when both stations can hear each other directly, and that is especially considerate on a busy or linked system. Identify according to the rules where you are, which in many places means at intervals and at the end of your communication. Don't assume the controller's ID covers you if your licence conditions say otherwise. Open and closed repeaters need a short explanation. An open repeater is available to any properly licensed operator within its stated rules. A closed repeater limits access, for example to club members or to people who know the access method, and it should still be used only with the owner's permission. Coordination is a separate matter. In many countries a recognised frequency coordination body helps assign pairs so that repeaters interfere with each other less, and coordination status and openness don't determine each other. For finding systems, use a directory as a starting point and then verify. RepeaterBook, club websites and printed directories can all be stale, and a listing can still show a repeater that is off the air, changed its tone, or moved to another site. If you find an error, tell the maintainer or the club contact. It helps to give the date, time, frequency, the tone you used, your location and what you heard. Repeaters cost money for sites, power, antennas and maintenance, so many clubs rely on membership dues or donations. If you use a system regularly, check whether the club accepts members or has a way to contribute.
-
Building out an HF shack around a 100 W rig: what to sort out before adding an amp, tuner or filters
On the grounding point, it helps to treat safety, lightning and RF as three separate jobs rather than one wire to one rod. Mains safety earth is mandated by code and isn't up for negotiation. For lightning, the usual advice is to bring all coax and rotator or control cable shields to a single entry panel outside, bonded to the electrical service ground with a short, heavy conductor. Ground rods at the antenna and service need to be bonded together so that no potential difference develops between them. Exact requirements depend on the jurisdiction, so check the local code or ask a qualified electrician. Inside the shack, the goal is simply to keep RF off the equipment. A short bonding strap between chassis helps with ground loops and shared noise. It won't cure common-mode current on the coax. For that, put the choke where the current is, which is at the feedpoint and again near the entry point. If you have audio or digital interfaces, a ground loop between the computer and the rig can add hum. A USB isolator or an audio isolation transformer is often a better fix than adding more ground wire.
-
Planning a first SOTA activation: summit references, points, VHF vs HF kit, and logging
Your understanding of the scoring is about right. Two points are worth checking in the rules. The activation zone is defined vertically from the summit, so confirm on the map where the legal operating area actually is before you set up. Also, the four-contact threshold is the minimum for points, not a target. If the band is quiet, you want a margin. On kit, I'd keep the VHF handheld in the pack. It's light, and 2 m FM is often the quickest way to get the first four in the log, especially if local activators and chasers are on a calling frequency. Check your local band plan, because the usual SOTA calling habits differ between regions. For HF, an end-fed half-wave is simple, but it needs a decent counterpoise and some thought about feedline length and mast height. Do a trial setup at home first so you aren't untangling wire in wind. For logging, write down the time in UTC, the frequency, the mode, the chaser's call and the report as you go. Fixing a messy log at a trailhead is much harder than keeping a clean one on the summit. When you self-spot, include the summit reference, frequency and mode in the comment, and update the spot if you move. Alerts and spots are what bring chasers to you.
-
The Small Moments That Keep Hams Coming Back to the Shack
Ask a room full of hams what they love about the hobby and you'll get a room full of different answers. Some talk about chasing distant stations, some about building circuits, some about emergency communications. But if you listen for what sits underneath all of those answers, it's usually something smaller: a good conversation, a piece of gear that finally works, or a person who took the time to help. This is a look at the everyday side of amateur radio, the stuff that doesn't make it onto a certificate but makes the hobby worth coming back to. The Rag Chew: Radio's Slow ConversationA rag chew is just a relaxed, open-ended chat on the air. Nobody is trying to log a rare entity or squeeze in a quick exchange of signal reports. The topics are whatever comes up: the weather, the antenna project that ate the weekend, what's cooking for dinner, the rig on the desk. What makes a rag chew different from a phone call is the way it starts. You tune around, hear a CQ, and answer a stranger. Within a few minutes you often learn their general location, their station setup and a surprising amount about how they spend their days. Many hams say the friendships that grow out of repeated contacts are the most lasting part of the hobby, even among people who never meet in person. A few habits make rag chews better: Ask open questions. "What are you running there?" beats "Copy?"Let silence be okay. Propagation fades, and a pause isn't a failure.Share something about your station. It gives the other person something to respond to.Close warmly. A sincere "73" (best regards) goes a long way.Favorite Rigs Are Rarely the Fanciest OnesSpend any time around hams and you'll notice that the "favorite radio" conversation almost never ends with the most expensive model. People get attached to a rig for reasons that have little to do with specs: It was their first HF radio, and every contact on it felt like magic.The receiver is quiet and pleasant to listen to for hours.The controls fall naturally under the hand.It was restored, repaired or modified by the owner, so it carries some effort with it.Older tube-era gear and vintage transceivers have a devoted following for exactly this reason. There's a tactile satisfaction in a big tuning knob and a warm glow, even if a modern software-defined radio outperforms it on paper. The reverse is also true: many operators happily embrace compact, digital-friendly rigs because they make portable operating easy. Neither camp is wrong. The best radio is the one that gets you on the air regularly. Club Nights: Coffee, Soldering Irons and Strong OpinionsRadio clubs vary a lot, but the best meetings tend to have a similar feel. There's a business portion that someone tries to keep short, followed by a presentation or demo, and then a long stretch of people standing around talking about antennas. If you've never been to a club meeting, it's worth knowing that nobody expects you to arrive as an expert. Clubs are often where newcomers find: Volunteer examiners who run license test sessions.Field Day and event planning that gives you a reason to operate with others.Loaner gear and shared knowledge, from tower climbing know-how to digital mode setup.Nets and group activities that make on-air time feel social.If you're nervous about walking in, remember that most clubs are glad to see a new face. Asking a question is usually the fastest way to make a friend. Elmers: The Quiet Backbone of the HobbyIn ham radio, an "Elmer" is a mentor, someone who helps a newer operator learn the ropes. There's no formal program or title. An Elmer might help you pick a first radio, talk you through an antenna install, or simply answer the same question you've asked three times without making you feel silly. The tradition lasts because the hobby is wide and genuinely complicated. No one learns everything alone, and the habit of passing knowledge along is baked into the culture. If you've benefited from that kind of help, the natural next step is to offer it. You don't need to be an expert to be an Elmer. You only need to be one step ahead of someone and willing to share. Hamfest Finds and the Art of RestraintA hamfest is part flea market, part reunion, part forum, and it's famously easy to come home with more than you planned. Tables of coax, connectors, meters, tuners, project boxes and mystery boards invite browsing. A few guidelines help: Bring a short list of what you actually need, plus a loose budget.Test before you buy when you can, and ask the seller what's known to work.Check connectors and cables. Damaged ones are cheap to avoid and annoying to fix.Be wary of "as-is" bargains unless you enjoy repair projects.Talk to people. Some of the best finds are tips, not items.Even if you leave with nothing but a handful of adapters, a day spent among fellow hobbyists tends to be time well spent. Mishaps: Every Shack Has a Few Lessons Written in Mild EmbarrassmentNearly every operator eventually runs into a classic mistake. Common ones include: Calling CQ for ten minutes before realizing the antenna was switched to the wrong radio, or not connected at all.Transmitting into a poor match because the tuner or SWR check was skipped.Leaving the microphone gain or processing set for a different mode.Chasing a noise problem for days, only to find a cheap power supply or charger was the culprit.Forgetting to unkey a transmitter, a good argument for checking your push-to-talk setup.None of these are disasters, and each one teaches a habit: check the basics first, keep a simple checklist, and don't assume the fault is somewhere exotic. Most troubleshooting in a shack comes down to power, ground, coax and connectors. Milestones, Big and SmallHobby milestones don't need to be dramatic. For many hams the list looks something like this: passing the first license exam, making that first contact, upgrading a license class, getting a homemade antenna to work, joining a net, or operating from a park or a mountaintop for the first time. Each one is a reminder that the hobby rewards curiosity in small, steady steps. What It Means Day to DayFor most people, ham radio isn't a headline activity. It's a few minutes of listening before bed, a Saturday of tinkering, a weekly net check-in, or a conversation with a voice that's become familiar. It's also a skill set that can matter when ordinary communications fail, which gives the hobby a purpose beyond fun. If you're thinking of getting started, pick one small thing: attend a club meeting, listen to a local net, or just turn on a receiver and tune around. The rest has a way of following. 73, and see you on the bands.
-
Building a first go-kit for SOTA/POTA: EFHW or linked dipole, and what else goes in the bag?
On power, the thing worth doing at home is a dry run with the whole station. Connect the battery, fuse, rig and key, transmit at your planned power into a dummy load or antenna, and watch the voltage under load. A pack that reads fine at rest but sags or trips its BMS on SSB peaks is better discovered on the kitchen table than at the top of a climb. For voltage, check the rig's upper limit. Many HF rigs are happy at 13.8 V nominal but have a ceiling a bit above that, and a fresh LiFePO4 pack can sit around 13.3 to 13.6 V, which is generally comfortable. Don't use a lead-acid float charger on a LiFePO4 pack unless it's designed for that chemistry. For logging, I'd keep the phone out of the critical path. Cold drains batteries quickly and there may be no coverage, so a paper log with the reference and UTC date at the top is the safest primary record. If you use a logging app offline, export a backup file before you pack up. And if your program expects you to be spotted, sort out your spotting method before you leave, because a park with no signal changes the plan. Finally, a simple rule that costs nothing: decide your turnaround time and weather limits in advance, and tell someone where you're going and when you expect to be back.
-
SSB audio checklist: mic gain, ALC, compression, EQ and bandwidth for clean signals and weak-station work
A useful addition: treat the ALC reading as a ceiling, not a target. Some radios show ALC only on the transmit path before the final amplifier stage, so a meter that looks fine doesn't prove your output is clean. If you run an amplifier, set drive so the amp's ALC shows little or no action and the output follows the exciter linearly. A common mistake is to boost compression to "get more out of the amp" and end up with a signal wide enough to bother neighbors up and down the band. On processors, it helps to test in steps. Turn compression off, say a few words, then raise it a bit at a time while watching the meter and listening on a monitor or second receiver. When the compression meter shows a few dB on peaks, stop and check for pumping on breaths and pauses. If room noise rises in the gaps, you've gone too far or the mic is too far away.
-
Radio mods that are worth doing, and where MARS/CAP, expanded receive and legal limits come in
Worth separating the clone-software and firmware route from physical board mods. A menu or software unlock can usually be undone by restoring a backup, but desoldering parts on a small handheld board is much harder to reverse. If you're undecided, start with the reversible change and see whether it solves the problem. On the MARS/CAP side, the cleanest approach is to ask the people who run your program what radios and programming they accept. Programs often have their own approved equipment lists or procedures, and a radio modified on your own may not be allowed on their nets even if it works technically. For amateur use, the better question is not whether the radio can do something but whether it stays clean on the air. A modified radio with a dirty signal is a problem, so check it into a dummy load and look at the output before putting it on a repeater. For power, the most overlooked item is the fuse. A good battery can deliver a lot of current into a short, so protect the positive lead near the battery rather than at the radio.
-
Studying for the Amateur Extra (Element 4): how do you split time between the math-heavy theory and Part 97?
Your two worked examples are both right, and they show a good way to study. Do the math on the circuits where the pool uses a small set of formulas, and learn the concepts on the rest. Worth calculating: op amp gain (inverting is -Rf/Rin, non-inverting is 1 + Rf/Rin), FM modulation index (peak deviation divided by modulating frequency), reflection coefficient and SWR, and basic LC resonance. The pool re-uses these with different numbers, so a few repetitions go a long way. A deviation of 3 kHz with a 1 kHz modulating tone gives an index of 3, for example. Fine to learn as concepts: amplifier classes (how much of the cycle the device conducts, and the efficiency vs. linearity trade-off), filter families (Butterworth is flat in the passband, Chebyshev trades ripple for a steeper skirt, elliptical gets the steepest transition by allowing ripple in both bands), and the receiver specs. For receivers, think of dynamic range as the span between the noise floor and the point where strong signals create distortion products. Third-order intercept is a figure of merit for how well the front end handles strong signals. Better numbers are better, but you rarely have to derive them. On the Smith chart, it helps to remember that the center of the chart is a perfect match, a normalized 1 + j0, which is 50 Ω on a 50 Ω system. Distance from the center is mismatch. Moving along a lossless line rotates you around the center, and one full lap is a half wavelength. Once you've internalized those three ideas, many of the pool questions become reading a point off the chart rather than doing math.
-
Starting Morse from zero: Koch, Farnsworth, LCWO, G4FON or CW Academy, and how do I stop counting dits?
Adding to the above, here are two parts of your question that are easy to skip: moving to head copy, and confidence. Head copy. Writing every letter down is a good first step because it gives you something to check. The trap is that you end up reading what you've written instead of listening. A gradual way out of this: Once individual characters are solid, start copying whole words and short phrases instead of random groups.Try writing only the first letter of each word, or only numbers, and carry the rest in your head.Then listen to a few words with no pencil at all and say or think what you heard once it ends.You will lose a character here and there while this is happening. If you stop to think about a missed character, you'll miss the next few as well. Let it go and keep listening. That habit of letting go is one of the main things you're learning. Structure. If you'd like a person to keep you on track, CW Academy (run by the CWops group) offers classes with an advisor and a small group of students, usually beginner through to advanced levels. Check their site for the current schedule, how to sign up and what the prerequisites are. A class gives you deadlines and someone to ask, and that matters a lot if self-study tends to fade out after a couple of weeks. Confidence. Being nervous about a first QSO is normal, and you can reduce it ahead of time: Listen to real CW on the bands before you try to transmit. Your goal is only to pick out callsigns and signal reports, since those are repetitive and predictable.Learn the standard exchange so you know what's coming. Much of a basic contact is formulaic, which helps your copying.Practise sending as well as receiving. If you're using a straight key or paddle, listen to your own sending, either on a code oscillator or recorded, to check your spacing.Be upfront on air. Sending something like "QRS" (please send slower) is perfectly normal, and many operators are happy to slow down for a newcomer.Plateaus are common, often around the point where new characters get added or speed goes up. When progress stalls, it can help to drop the speed slightly or go back over the characters you already know instead of forcing the next one in. Moving on when your accuracy is solid will usually get you further than pushing ahead when it isn't.
-
Winlink over radio: how the pieces fit together (RMS gateways, session types, sound card/TNC setup, forms and P2P)
On the message side, a few habits keep a radio session healthy. Keep messages small, especially on HF. Skip embedded images and large attachments, and send a plain text body, with a form when the receiving agency expects one. A short ICS-213 transfers quickly and still carries the structure that served agencies want. Remember that a recipient who only has ordinary email sees the text rendering of the form. The full form view needs Winlink Express or compatible form viewing on their side, so tell them what to expect when you send to a non-Winlink recipient. Inbound Internet email is another point worth knowing. Winlink applies spam controls to mail coming in from the Internet, so a message from an unfamiliar sender may not arrive the way you expect. Check the current Winlink guidance on whitelisting and on the subject-line conventions for mail sent to a Winlink address, because that is policy that can change and I wouldn't rely on memory. For practice, a Winlink Wednesday style exercise is more useful if you test more than one path. Send one message through a gateway, one by P2P to a nearby operator, and one Telnet message as a baseline for your account. Afterwards, compare the session logs. The log shows whether a failure was at connect, at login or in transfer, and that tells you whether to look at the radio chain, the password or the gateway choice. Finally, save your gateway channel list and your templates before an event. Both are fetched over the Internet, and the situation where you most need them is the one where the Internet may not be available.
-
How do you keep up with ham radio news without chasing rumors? Firmware, FCC, ARRL, band conditions and Hamvention season
On firmware, I'd split updates into two kinds: bug fixes for something that affects you, and feature additions you could live without. A fix for a problem you actually have is worth doing soon. A new feature can usually wait while other owners find the rough edges. Whichever kind it is, save the current settings, write down your version number, and keep the previous firmware file if the manufacturer still offers it. A rollback path matters more than being first. It also helps to separate the radio from the software around it. A rig firmware update can interact with logging software, a CAT control program, a digital mode setup, or a sound card interface. If you run FT8 or a contest logger, test one thing at a time after updating and don't change several things the night before an event. For regulatory news, I'd add that comment periods and rule drafts are not the same as changes in effect. A lot of confusion comes from treating a proposal like a final rule.
-
Building a clean digital chain: time sync, audio levels, CAT and choosing between FT8, JS8Call, WSPR, Olivia and the rest
For picking a mode, ask what you want from the contact. If it is a quick log entry or country count on a marginal band, FT8 is efficient because the exchange is structured: callsign, a 4-character Maidenhead grid, a signal report, then 73. If you want to type to someone, JS8Call or PSK31 gives you that, while Olivia is for when conditions are rough and you accept a slow pace. WSPR is better for finding out where your signal goes than for working anyone. Run it for a few hours on a band, then check the spots on WSPRnet to compare antennas or time of day. Remember that WSPR reports your power in dBm, so the data is only useful if you enter the right figure. Grid squares deserve a note, since they cause plenty of errors. Maidenhead locators go field (two letters), square (two digits), then subsquare (two letters), so FN31 is a 4-character grid and FN31pr is 6 characters. FT8 messages normally carry only 4 characters. If you are chasing VUCC-type awards or doing VHF weak-signal work, the 4-character grid is what you will log. Make sure you enter yours correctly in WSJT-X settings, because a typo sends wrong information with every CQ. One caution on decode thresholds: the -21 dB figure is a measure against noise in a 2500 Hz bandwidth, not a promise. Fading, a bad DT or a drifting transmitter can make a signal much harder to decode than the number suggests. Treat the table of thresholds as a comparison between modes, not a guarantee for any particular contact.
-
LoTW, eQSL, Club Log OQRS, bureau or direct: how are you confirming contacts, and what actually counts for DXCC?
The "both sides have to upload" point is the one new people trip over. LoTW is not a service that confirms contacts on its own. It compares two uploaded logs, so a station that never uploaded will never show as a match, however clean your log is. Before blaming your upload, check whether the other station is a LoTW user at all. Many logging programs and QRZ lookups show that, and Club Log has its own LoTW user information, so you can see up front who is worth chasing on LoTW and who needs a card. The other common headache is station location setup in TQSL. If you operate from more than one place, make a separate station location for each one, with the right grid, zones and entity. Uploading everything under one location will give you mismatches or wrong credit, and fixing it later is tedious. Keep a note of which locations you used for which dates, especially if you operate portable or from a different DXCC entity.
-
Splitting shack automation between a Raspberry Pi and microcontrollers: what goes where?
Adding to the above, on RFI I'd treat it as a system issue rather than a board-choice issue. A metal box and ferrites help, but the usual failure paths are the cables: USB, I2C runs to displays or sensors, and the leads to relays and rotator potentiometers. Each one can act as an antenna on HF. Common mitigations are a ferrite choke on each cable where it enters the enclosure, a small bypass capacitor and series resistor on sensor lines, short I2C runs with modest pull-up values, and a single well-considered ground point. If a unit misbehaves only while transmitting on a particular band, that points to RF ingress and not a software bug. Also note that the ESP32's Wi-Fi radio is a transmitter in its own right, so keep it away from sensitive receive antennas and consider whether you need it on at all for the module that sits next to the rig. On ADCs, the ESP32's internal ADC is known to be nonlinear and noisy, especially near the ends of its range. That matters for a rotator, where the position is a potentiometer voltage and you want repeatable readings. The Pico's ADC is usable but has its own limits and noise. An external I2C converter like the ADS1115 is cheap and usually a better fit for both the rotator and SWR sense lines. For SWR, a directional coupler feeding a log detector such as the AD8307 gives a wide dynamic range. Either way you will need calibration against a known load and a reference meter, because diode detectors are not linear at low levels. For the antenna switch, don't hot-switch under power. Build a sequence in firmware: PTT off, short delay, change relay, short delay, allow PTT again. Add a hardware or firmware lockout so a bad command can't key the rig while the relays are moving. If you use relays with DC on the coax, mind the DC path and the coil flyback diodes. Remember relay isolation drops as frequency rises, so a switch that works well on HF may leak noticeably on VHF. If the Si5351 does get added, remember its outputs are square waves with strong harmonics. Put a low-pass filter on the output before connecting it to a receiver or any antenna system. Its accuracy is only as good as the reference crystal, so don't expect it to be a lab-grade standard.
-
Band plan vs. FCC rules: how do you decide where to operate from 160 m through 33 cm?
To add VHF/UHF and the international side. Here the band plan carries more weight than the rules, because the rules give you huge blocks (Technicians can use all of it) and the band plan is how people avoid tripping over each other. Everything below is from the ARRL plan as I know it. Check the current version before relying on exact figures. 6 m (50–54 MHz): the bottom of the band is for weak-signal work. 50.0–50.1 is CW, mostly beacons around 50.06–50.08. SSB calling is at 50.125, with a DX window just below it at about 50.100–50.130. FT8 is on 50.313. The national FM simplex calling frequency is 52.525. 2 m (144–148 MHz): the bottom is weak-signal: CW at the very bottom, SSB calling at 144.200, FT8 around 144.174. The FM simplex calling frequency is 146.520, and the plan reserves a simplex segment around it. Repeaters use paired frequencies, usually with a 600 kHz offset on 2 m. 145.800–146.000 is set aside for satellite use. 70 cm (420–450 MHz in the US): SSB/CW weak-signal calling is at 432.100. The FM simplex calling frequency is 446.000. Repeaters typically use a 5 MHz offset. Satellites are around 435–438. Also note that amateurs are secondary on 70 cm, and there are geographic restrictions near some government radar installations, so look at the footnotes in Part 97 if you're near one. 33 cm (902–928 MHz): this is an underused band. The FM simplex calling frequency is 927.500, and weak-signal work happens at the bottom, near 902.100 and 903.100 per the plan, though I'd verify these. Amateurs share the band with Part 15 devices and other licensed services, so expect noise, and we're secondary here too. 33 cm exists in ITU Region 2 (the Americas), but it isn't an amateur allocation in most of the rest of the world. On international allocations, the ITU splits the world into three regions, and IARU coordinates amateur band plans for each. Region 1 is Europe, Africa, the Middle East and northern Asia. Region 2 is the Americas. Region 3 is the rest of Asia and the Pacific. The differences matter if you travel or work DX. For instance, 40 m is 7.000–7.200 in Region 1 but 7.000–7.300 in Region 2, which is why US stations above 7.200 are often not workable by European stations. The same goes for 80 m (3.500–3.800 in Region 1 versus 3.500–4.000 in Region 2) and for 2 m (144–146 versus 144–148). Power limits, license classes and even 60 m channel arrangements vary by country. If you operate abroad, your home privileges don't carry over by default, so look up the rules of the country you're in, or check reciprocal-operating arrangements. For day-to-day use, the practical approach is: use the FCC chart for what you may do, use the ARRL or IARU plan for where to do it, and listen for a minute or two before calling. Edges and channel lists do get updated, so confirm the current versions of both documents.
-
Run, S&P, or hop bands? How do you decide when a multiplier is worth the rate hit (and where SO2R fits)
The Q/M rule of thumb is useful, but keep an eye on the effective value of mults by band. In contests where mults count per band (CQ WW style), a mult on 10 meters is a separate chance from the same mult on 20, so it can be worth waiting for the band to open and then taking a quick swing. In contests where each mult counts once, a rare mult is worth less after you've worked it elsewhere. The "worth 10 QSOs" figure gets worse as your QSO total grows, which is why the typical advice is to stop chasing each one in the final hours unless it takes under a minute. For the trigger, I would not rely on a single fixed rate. A drop against your own rate on that band is more telling. If the current band gives 90/hr but the previous hour on a comparable band was 140/hr, that is a nudge to move. If you are hearing your own CQs returned slowly while the band map shows a lot of unworked mults, that is a nudge toward S&P. N1MM makes this easy because you can watch the rate window and the available-mults list at the same time. On SO2R, the less glamorous part is the discipline: sticking to a routine for what the second radio does. A common one is to keep the second radio on the next-best band, tuned to the band map's best mult, and only touch it when the run radio is between callers. Then, when the run radio has someone calling, don't leave it just to finish a second-radio contact. Prioritizing the running contact is where the rate comes from.
-
Choosing a handheld for ham use: Baofeng vs FT-65R vs D-STAR/DMR HTs, and what actually matters for emergencies
For a first radio I'd lean analog, mostly because it works everywhere there's a repeater and you can learn the fundamentals first: offsets, tones, squelch, simplex etiquette, and how much your antenna matters. The FT-65R is a reasonable choice if you want something simple. If you go with a Baofeng, buy a better antenna and spend a bit of time confirming the radio is programmed for legal frequencies and sane power settings. CHIRP makes that easy, but it also makes it easy to push in a bad channel list. On the digital side, D-STAR and DMR are fun but they add layers: callsign registration for D-STAR, a DMR ID and talkgroup structure for DMR, and often a hotspot if your area has no coverage. I'd only buy a digital HT if I'd confirmed there's something local to talk to, or if I already knew I wanted APRS or GPS features. The TH-D75 and ID-52A are capable radios, but they're not the cheapest way to learn.
-
Good on-air habits: listening first, calling CQ, breaking in and working nets
Good list. One thing to add on nets: if you are checking in, wait for net control to ask for check-ins, and don't call just because you hear a gap. Net control may be listening for a particular group, such as mobile stations or short-time check-ins, and a call out of order costs everyone time. When your turn comes, give your callsign with phonetics, and then stop unless you have something to add. Net control has a job to do too. A new net listener should hear the net's purpose, name, frequency and schedule, and any rules, such as whether traffic is handled or only check-ins taken. Keeping a log makes it easy to say who has already checked in. When the net closes, say so clearly, so people don't keep calling into dead air. Emergency or priority traffic always goes first, and a net should be ready to set routine business aside.
-
What does your spotting and lookup stack look like? DX cluster, RBN, PSK Reporter, POTA/SOTA and the rest
On filtering: the biggest improvement for most people is stopping the firehose. A cluster feed with no filters is nearly unusable on a busy weekend. Narrow it to the bands and modes you can actually operate, and consider whether you want skimmer-generated spots mixed in at all. Skimmer spots are good for seeing where CW activity is, but a human spot with a comment such as "up 2" or "listening 5-10" carries information a skimmer can't give you, namely how the DX station is working the pile. For PSK Reporter, treat it as a diagnostic tool. If you call CQ on FT8 and the map fills with reports, your station is radiating on that band. If you get only a few reports from nearby, the band may be short, or your antenna may favor a different direction. Also remember that the stations hearing you are a mix of good and mediocre receive setups, so not hearing you in a given country doesn't prove the path is closed. For RBN, SNR figures are relative to each skimmer's noise floor, so comparing numbers between different skimmers isn't meaningful. Comparing your own signal at one skimmer before and after an antenna change is a fairer test.