Everything posted by Mod_Tom
-
Go-kit layers for hams: HT, mobile, antennas, power, and the family plan that makes them useful
For the family side, I would keep it simpler than most plans. Pick two channels everyone memorizes, for example one FRS or GMRS channel for local contact and a backup. Write both on a card with the family check-in time. If your radios support privacy codes, remember that they do not make a conversation private. They only filter what you hear. Do not rely on them for anything sensitive. It also helps to have non-hams practice with the radio during a normal day. Have them do a radio check from the backyard, then from the end of the street. They learn push-to-talk, pausing before speaking, and short clear messages. Range on handhelds is usually much shorter than the package claims, especially around buildings and terrain, so test your real distances. If handhelds do not reach where you need, a GMRS mobile with a proper antenna or a repeater may be a better fit. For supplies, think about the people in your household. Infants, pets, and anyone who needs prescriptions or medical equipment change what the kit should contain. A radio list is only part of the plan. Water, food, hygiene supplies, a paper map, and copies of key documents can matter just as much when you cannot rely on the usual infrastructure.
-
EME by band: what 2 m, 70 cm, 23 cm and 10 GHz moonbounce actually demand from a station
On the fading question, it helps to separate three mechanisms because they look similar in a waterfall but need different fixes. Faraday rotation is slow, usually minutes, and it fades you because your antenna polarization no longer matches the arriving wave. It is strongest on 2 m and mostly gone by 23 cm. The cure is polarization agility: a way to rotate or switch between horizontal and vertical (or two diversity channels), not more gain. If a signal fades and returns over several minutes on 2 m, suspect this first. Spatial polarization is geometric. Two stations far apart see the Moon at different angles to their local horizons, so linear polarizations are misaligned even when the ionosphere is quiet. It does not depend on band, so it also affects microwave linear feeds. Circular feeds sidestep it, and a rotatable feed lets you fix it. Libration fading is the fast one. The Moon's slight rocking and rotation relative to you makes reflections from different parts of the surface interfere, which spreads the signal in Doppler. The spread grows with frequency, so on 2 m it can be mild, while on 10 GHz it can smear a signal enough to need the widest tone spacing. It is why the Q65 submodes A through E step up with band. If your signal looks fluttery but strong, mode spacing is probably the lever. If it fades slowly, it is polarization. One caution on JT65 versus Q65. Both are 60-second modes and the WSJT-X guide gives recommended submodes per band, so I would follow that rather than guess. Q65 generally holds up better under spread and when decoding with averaging, but you still need partners who run it, so check which mode your sked partner expects before the contact.
-
Remote station control: comparing RS-BA1, SCU-LAN10, RigPi, SmartLink and receive-only SDRs, plus security, latency and rules
A practical point on the audio side: the radio-to-network leg and the client-to-network leg are two separate things to tune. With RS-BA1 style setups, a bigger audio buffer will remove choppiness on a bad connection, but it adds delay. For ragchewing that is a fine trade. For working a pileup you will want it as small as the connection allows. I'd also test the failure mode before depending on it. Start a transmission, pull the client's network connection and see what the radio does. If it keeps transmitting until a timeout, set that timeout shorter. Whatever the software promises, it is worth confirming on your own hardware. Also, if you only want to listen from away from home, a KiwiSDR near you can tell you whether the band is open, but it's not a substitute for operating. You can't hear your own signal path the way your receive antenna does.
-
Tightening up CW: paddle settings, Farnsworth, filters, QSK and decoders. What actually helped your copy and sending?
One thing that is easy to overlook: record your own sending and play it back. Most keyers and rigs can do this, or you can just use a phone next to the speaker. Listening back usually exposes uneven letter spacing, a habit of rushing the last element of a character, or a dah that sounds short. Those are hard to hear while you are concentrating on what to send next. On copying, a common recommendation is to stop writing each letter as it arrives and start copying in word chunks, even if you only get a few words behind at first. Writing letter by letter keeps you at the level of dits and dahs. Once you are comfortable at one speed, try listening at slightly above your copy speed for short stretches, then drop back. It makes your normal speed feel slower without turning every practice session into a struggle. For decoders, a useful experiment is to copy a signal by ear and then compare against a decoder. Where they disagree is revealing. Often the decoder is the one getting confused by noise, but sometimes it catches a call sign digit you missed.
-
Nets and special event stations: how do you find a good net, check in cleanly, and make the most of event certificates?
One thing worth separating is the net's format versus its purpose. A directed net is run by net control, who calls on stations in order. A free-form or roundtable net lets stations pass the transmission around. If you are not sure which one you are listening to, wait for the preamble. Most well-run nets read a short opening statement that says the net's name, purpose, and how to check in. That statement tells you how to act. For net control, a clean log makes a big difference. Write down callsigns as they are heard, mark short-time stations so they can be taken early, and flag any priority or emergency traffic right away. If two stations key up at once, ask for a repeat of the partial callsigns rather than guessing at them. Closing the net properly matters too: read the final list, thank the participants, and state when and where the next session will be. For SKYWARN specifically, remember that the net follows the local weather office's request, not a calendar. Reports should be specific, and the usual guidance is to report only what you actually observe, with location and time, rather than guesses about what a storm might do. Keep your report short and let net control pass it on.
-
QSL workflow: LoTW first, then eQSL, QRZ, Club Log OQRS, bureau, or direct?
A simple rule is to let LoTW do the bulk work and use paper for special cases. If a DX station is on LoTW, upload promptly, check that your station location matches where you actually operated, and the confirmation usually comes down to when they upload. If they are not on LoTW, look for an OQRS link or a QSL route before deciding whether a direct card is worth it. With paper for DXCC, remember that the cards still have to be checked and submitted according to ARRL rules. That adds steps LoTW does not have. So a card you only want for the wall or a personal collection is a different decision from one you need for credit. Rare or one-time operations, such as a DXpedition or an unusual entity, are where a direct card can make sense. For everything else, the bureau is fine if you are not in a hurry.
-
Studying for the Amateur Extra (Element 4): how do you split time between the math-heavy topics and the Part 97 rules?
On the Smith chart, you don't need to be able to draw on it from scratch for the exam. You need to recognize what the features mean. The center of the chart is the normalized match point, where r is 1 and x is 0. That corresponds to zero reflection and a 1:1 SWR. The horizontal axis is pure resistance. The outer circle is pure reactance, with no resistive part. Moving around the chart toward the generator is clockwise, and one full trip around is a half wavelength of line. That last fact explains why a half-wave line repeats the load impedance. A related topic is the quarter-wave transformer. Its characteristic impedance is the square root of the two impedances you're matching. To match 50 ohms to 200 ohms, you'd want about 100 ohms. That calculation shows up in several forms. For antennas, make sure you keep dBi and dBd straight. A dipole has about 2.15 dB of gain over an isotropic radiator, so gain in dBi is gain in dBd plus 2.15. The pool also asks about effective radiated power, which accounts for transmitter output, feed line loss, and antenna gain relative to a dipole. As for what Extra does for you: it gives you operating privileges on all amateur frequency segments, with all modes authorized by Part 97. Each of the HF bands where General is restricted has a small Extra-only slice. You also become eligible for the highest vanity call sign group. Many hams get more out of the larger test-taking privilege, because Extras can serve as volunteer examiners at a higher level. Check the current band plan and rules directly, since segment edges and the rules themselves can be amended. Practice exams are useful for the last stretch. Use them to find the topics you keep missing, then go back to the underlying concept instead of memorizing individual answers.
-
How do you decide if a band is really open? SFI, K index, VOACAP, WSPR and beacons compared
I'd separate planning from monitoring. VOACAP is good for planning because it forces you to enter realistic assumptions: transmit power, antenna type, required SNR and the path. If you leave defaults in, the output can be misleadingly optimistic. Look at the reliability and the predicted signal level in the context of your mode, since a CW or digital operator needs far less SNR than an SSB operator. Also remember that it works from smoothed monthly values, so it can't capture a flare, a geomagnetic storm or a sporadic E opening on a given afternoon. For the quick check, K index matters most to me on polar and high-latitude paths, where a disturbed geomagnetic field can wipe out something the prediction says should be fine. For regional work on 80 or 40 meters, NVIS is mostly about the critical frequency: if the band is above foF2 your signal goes through the ionosphere rather than back down, so a low-band antenna and a lower frequency are better choices at night when foF2 drops. And on 6 meters in summer, I wouldn't rely on any index at all. Sporadic E is better tracked by watching spots, beacons and cluster activity than by SFI.
-
Getting started with WWFF: KFF references, the 44-QSO line, and combining with POTA
For combined POTA and WWFF activations, the main planning point is that the higher threshold wins. If you're aiming at both, set your goal at the WWFF minimum rather than POTA's 10, and the POTA requirement will be met along the way. First confirm that the park really carries both references. Many areas overlap, but not all, and boundaries sometimes differ. Look up both references and check the map before you assume that your operating spot is inside both. On the air, give both references in your calls and in your spots, for example by saying them in your CQ every few calls. Hunters tuning across the band may be after one program only, and others will want both. Be ready to repeat the reference slowly on SSB, using phonetics for the letters and numbers. On CW or digital modes, it helps to put the references in the exchange and in your spot comment. Some other practical tips. Check park regulations, access hours and any permit needs before you set up. Keep antennas and cables off sensitive vegetation and away from wildlife, since the whole point of the program is to respect the place. Plan a second band or mode so that you can keep working stations when one runs dry. And when the pile-up calms down, call CQ again rather than waiting: some hunters only show up once you are back on the spots page.
-
Checking a homebrew QRP transmitter for harmonics with basic bench gear
If I had to choose a single instrument for this job, I'd pick something that tells you about the filter before the transmitter is connected to it. A NanoVNA or similar is very good for measuring a low-pass filter on its own: cutoff, passband loss, and how fast the attenuation rises at 2f and 3f. That lets you fix the filter before you ever apply RF drive. For measuring the transmitter itself, a dummy load and some kind of RF power indication is the other essential. A diode probe on a scope or DMM, or a simple SWR bridge that you've checked against a known source, gives you relative readings, and relative is enough for tuning. Just remember the diode drop makes low-level readings non-linear, so don't trust the absolute numbers at 100 mW the way you would at 5 W. One more caution about the SDR method: use more attenuation than you think you need. A second harmonic that appears only because the SDR front end is overloaded can send you chasing a problem that isn't in the transmitter. Change the attenuator by 10 dB and see whether the apparent harmonic drops by exactly 10 dB. If it drops by more, it's partly being generated in the receiver.
-
Small-yard multiband HF wire: EFHW vs OCFD vs G5RV vs doublet, and what really decides performance
The EFHW question deserves a straight answer. On a lot where you can only run one wire along a fence line or up to a tree, an EFHW has an obvious practical advantage: one feedpoint, one coax, no center support. The things to look at are the transformer's core size and mix relative to your power, whether the manufacturer says anything about common-mode handling, and where the coax goes. In many installs the outside of the coax carries real current, so a choke a short distance from the transformer, and perhaps another near the shack, keeps the RF out of the house and the pattern more predictable. A thin-wire EFHW at a low height can still work well for contacts, but its coverage is band-limited, and a modest ATU helps on bands where it's off-resonance. One thing I'd push back on is chasing SWR on a vertical. If a ground-mounted quarter-wave shows a nearly flat match with only a handful of radials, that may mean it's burning the missing power in the ground. Measure the feedpoint resistance with an antenna analyzer and compare it to the expected figure. Lower resistance with more radials is usually the sign you are improving efficiency, even though the SWR number may look worse. That's the opposite of what intuition suggests. For comparing antennas honestly, side-by-side tests with a fast A/B switch on received signals, or comparing spot reports on a mode like FT8 or WSPR on the same band and time, tell you more than SWR sweeps. They still carry plenty of variability from propagation, so treat any single comparison as indicative, not definitive.
-
APRS on 144.390: how the pieces fit together (digipeaters, iGates, Mic-E, SmartBeaconing, Direwolf and handhelds)
One point on paths: the right path depends on your local digipeater network, not on a global rule. Where WIDE1-1 fill-in digis exist, WIDE1-1,WIDE2-1 works well for mobiles. In places with dense coverage, a single hop may be enough, and extra hops only add duplicates. A fixed home station with a good antenna often gains little from a long path. For SmartBeaconing, think about the speed range first. Set the slow rate for a stopped or crawling vehicle, such as a few beacons an hour, and the fast rate for highway speed. Then set the corner-pegging values so a turn triggers a beacon without producing a stream of packets in a parking lot. Compare what your radio actually transmits with what aprs.fi shows. The track often looks fine on the radio but shows gaps or clutter on the map.
-
Making SET and Field Day test what actually breaks: scenario design, message handling and after-action notes
Message handling is where I would put the most effort, because it is easy to look good on voice checks and still fail at accurate traffic. A radiogram has a defined structure: a preamble (message number, precedence, handling instructions if any, station of origin, check, place of origin, time and date filed), then the address, text and signature. The check is the word count of the text, which gives the receiving station a basic way to notice if something was dropped. Practicing that discipline is worth it even if your served agency never asks for a radiogram, because it trains people to read slowly, spell tricky words phonetically and confirm what they received. Where served agencies are concerned, find out what format they actually want. Many agencies use the ICS-213 General Message form, so a good drill might hand an operator an ICS-213 and make them send it by voice or digital mode to another site without rewriting it. Operators should not paraphrase or 'improve' the agency's message. If the wording is unclear, they ask the originator, not guess. Also, check in advance whether the agency prefers plain language or tactical call signs, and avoid assuming they use the same code set you do. Plain language is usually safer when a mixed group of responders is involved. For the injects, I would include at least one message with a deliberately ambiguous detail, such as a street name or quantity, to see whether the receiving operator asks for a repeat or just writes something down.
-
Building a wire dipole from scratch: wire, feedpoint, choke, ladder line, and how far to trust SWR and models
Radials are where verticals most often go wrong. A ground-mounted quarter-wave vertical depends on the radial field to return current, so the number matters a lot. Efficiency generally improves as you add radials. A field of 16 is often considered a reasonable minimum, and many more will do better. Elevated radials behave differently. Because they are above lossy soil, a few resonant radials, often 2 to 4 cut near a quarter wavelength, can work well, and adjusting their angle or number can bring the feedpoint closer to 50 ohms. Poor radials won't necessarily show up as high SWR. A lossy vertical can show a good SWR and still be a weak radiator, which is why SWR isn't a quality measurement. For fiberglass poles: telescoping poles are light and cheap, but they need guying, hose clamps or tape at the joints, and a wire routed down the pole that won't slide. Keep any pole well away from power lines. On traps: a parallel LC trap isolates the part of the wire beyond it at its resonant frequency, which lets one antenna work on multiple bands. The trade-offs are narrower bandwidth, some added loss, and a shorter overall length. If you homebrew them, confirm the trap resonance with an analyzer before it goes on the antenna, because capacitor tolerance and coil stray capacitance shift it. A fan dipole is simpler to build and repair, but interaction between the elements still means some trimming. For measuring SWR: measuring at the transmitter includes the coax loss, which can make a poor antenna look better than it is. A NanoVNA or antenna analyzer at the feedpoint gives a better picture, and it should be calibrated at the end of the cable you are using. For modeling: both programs are useful, but a model is only as good as its inputs. Check segmentation, junctions, wire radius, and ground type. EZNEC is NEC-based, MMANA-GAL has a different calculation core, and both are sensitive to wires close to ground. A sensible habit is to model the antenna, build it, and compare the real analyzer measurements against the prediction. Differences tell you what you didn't account for, such as nearby trees, sag, or the feedline. Check the current segment limits of the EZNEC version you use before planning a detailed model.
-
Nets and special event stations: how do you pick what to check into, and what makes a good net control?
For special event stations, I'd treat the timing as a scheduling problem. First check the listed UTC window, then the bands and modes, then think about when those bands are likely to be open from your location. A station running on 40 meters SSB will be a very different experience in your afternoon than in your evening. If the operators are working a pileup, listen for how they handle it. Many run split, with a note on where they're listening, and calling on their transmit frequency will just annoy everyone. For certificates, read the instructions on the event page before you send anything. Some require a log lookup, some ask for a QSL card, some want a mailing fee or SASE, and some are download-only. Keep your own log accurate with UTC date and time, band, mode, and the exact callsign worked, including any suffix. That makes both the QSL and the certificate request straightforward, and it avoids the situation where your entry doesn't match theirs. As for ARES and SKYWARN, I'd approach them differently from casual nets. Find out who coordinates them locally, what training or registration is expected, and whether the net is open to all amateurs or restricted to members during activation. Those details are usually posted by the local group or the weather service's amateur radio coordinator.
-
Remote station control: how to pick a path (Icom LAN, Yaesu SCU-LAN10, RigPi, Flex, RemoteHams) without creating a security or compliance headache
On the "what are you remoting" split, I'd add a fifth category: remote receive sites you own. A cheap KiwiSDR or similar at your own QTH, on a quiet antenna, is a useful reference for judging your own transmitted signal and local noise. It also gives you a way to check whether your station is on the air without logging into the radio. It doesn't replace a proper control path, but it makes a handy second opinion when the main link is misbehaving. On security, the VPN-first rule is the one to stress. The most common mistake with these setups is treating the radio's LAN port as a service meant for the internet. A VPN tunnel with the radio, the Pi and the PC all behind it is far easier to audit than a list of forwarded ports. And if you do use a vendor relay service, read how it authenticates the client and the radio, and what you lose if that vendor's service is down. One practical point on latency: measure it in both directions and under load. A path that looks fine on a ping test may suffer when the same uplink is busy with video or backups. A bit of QoS on the router for the radio traffic can matter more than any radio setting.
-
New to ham radio? Intro thread: first radio, first QSO, and what to do before you spend money
On the "what to buy first" question, the answer depends on what you want to do, and it is worth being honest about that before spending anything. If you want local chats and nets, a handheld, and maybe later a mobile radio with an external antenna, covers most needs. If you want to talk to other countries, you will need HF, an HF license where you live, and an antenna you can actually put up. If you are interested in digital modes, check that your radio has an audio interface or that you have a suitable sound card interface and the software set up. Mistakes that come up repeatedly with beginners: Buying a radio that is hard to support. Choose something with a manual you can find, a programming option, and a user community. Used gear can be a good value, but check the condition and whether accessories are included. Skipping the antenna and feedline. SWR matters, but so does loss in the coax and the antenna's location. Do not transmit into an unmatched antenna or a damaged cable if you can avoid it. Running too much power for the task. Start with the lowest power that works, especially on a handheld held near your body, and follow the RF exposure guidance for your country. Not going to a club meeting. Even if the meeting is mostly people talking about old rigs, you will learn which repeaters are good, which local antenna restrictions are common, and who might help you with a first install. If you are nervous about a first contest, ask the club whether anyone is running a Field Day-style event or a casual operating night. Many contests are very beginner-friendly: the exchange is usually short, you can listen for a while before calling, and no one expects you to win. Just read the rules for the event so you know the exchange format.
-
Building a ham go-kit that actually works: what to pack, what to test, and where GMRS/MURS/FRS fit
One of the biggest gaps in kits is the connector and adapter pouch. A radio and a battery are useless if the antenna has an SMA-female on the radio and a BNC on the antenna, or if your charger needs a barrel plug you left at home. Keep a small bag with SMA/BNC/PL-259 adapters, a couple of Powerpole pigtails with alligator clips and ring terminals, and a short jumper so you can run the radio from a vehicle or a bench supply. On the power side, a simple way to size it is to write a table: receive current, transmit current at your normal power, and how many minutes per hour you expect to transmit. Then add a margin. People often find a small battery covers a day of casual net use but not a multi-day event without recharging, which is where solar or a vehicle comes in.
-
Learning Morse code from scratch: Koch vs. Farnsworth, which trainer to use, and how to get past the plateau
The most important rule is to learn Morse as sound, not as a picture. Don't memorise a chart of dots and dashes, and don't use visual flashcards that show "di-dah" patterns. If you learn to count elements in your head, you'll have to unlearn that later, because at speed you need to hear a character as one rhythm. The letter A should sound like "A", the way a word sounds like a word. Koch and Farnsworth solve different problems, so you can combine them. The Koch method starts with just two characters sent at a fairly fast character speed, often 18 to 20 wpm or more. When you can copy them reliably, usually around 90% accuracy over a few minutes, you add one new character. The idea is that you never learn a slow, counted version of a character. Farnsworth keeps each character fast but stretches the gaps between characters and words, which gives you thinking time. Many trainers let you use Koch lessons with Farnsworth spacing, and that's a sensible beginner setup: fast characters, generous gaps, then shrink the gaps as you improve. For resources, LCWO (Learn CW Online) is a popular browser-based Koch trainer with lesson progression, plus practice for callsigns, words and abbreviations. G4FON's Koch trainer is a downloadable program that is configurable and works offline. The name Morse Trainer is used by several different programs and apps, so check which one you mean before comparing notes with others. CW Academy, run by CWops, is different: it's a structured class with an advisor and other students rather than a self-paced tool, and many people like the accountability. Check their site for current session dates and requirements. With 15 to 20 minutes a day, consistency matters more than length. Short daily sessions beat one long weekend session, because your brain consolidates sound patterns between sessions. If you feel your accuracy dropping, stop early rather than grinding through errors.
-
Which online tools do you actually stack together for spotting, propagation checks and logging?
On the phone-versus-web question, it comes down to what still works with no signal. Repeater directories and your logging app are the ones to keep usable offline, because a cached list or exported channel set is far more reliable than loading a page in a parking lot. Live things like cluster spots, PSK Reporter and POTA or SOTA spot pages need a connection anyway, so a bookmark is usually enough. It is also worth saving a grid and bearing reference ahead of time if you plan to work from a remote site. For propagation, one habit is to check the solar indices and a prediction chart before heading out, then use live data as the reality check once you are on the air. A prediction says what is likely over a month, while PSK Reporter or RBN shows what the band is doing at this moment. If they disagree, believe the live data, but use the prediction to decide which band to try next. For grids, 6 characters is good practice when you can get them, since 4-character squares are about 100 km wide and can hide a lot of difference in bearing and distance.
-
Choosing a handheld: FT-65R vs Baofeng, D-STAR options (ID-52A, TH-D75), where the IC-705 fits, and what actually matters for emergency use
I would add that D-STAR and DMR decisions should start from a map, not a spec sheet. Look at a repeater directory for your area. If the nearest D-STAR repeater is far away and nobody on your local nets uses it, an ID-52A or TH-D75 may sit in FM mode most of the time. On the other hand, if your club runs a D-STAR system or linked reflectors, a D-STAR HT makes a lot of sense. The TH-D75's APRS and GPS features are nice if you want position reporting, but it is still a premium radio. On CHIRP: it is great for FM memories and for sharing a channel list between radios, but it is not a universal tool. For D-STAR you typically deal with callsign routing, repeater lists and registration, and for DMR you will probably use the maker's software or a codeplug editor. Back up your image and keep a plain CSV of your channel list too. As for the IC-705, I would only get one if HF is part of the plan. It will not replace the HT on your belt, but it pairs well with one for portable work.
-
Standard phonetics vs. "creative" ones on the air: what actually works for callsigns, names, numbers and nets?
Start with why the standard alphabet exists. The ITU/ICAO/NATO words were chosen to be understood by speakers of many languages through noise, distortion and accents. 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, to guide pronunciation. That multilingual, low-signal-to-noise design is the main advantage over improvised words. Using non-standard words is usually not a rules problem. Regulators generally encourage a phonetic alphabet for identification without requiring one specific list, but check the wording of your own country's rules. The practical downside is that a listener has to recognize the word instantly, and a unique word they have never heard costs them time. "Kilowatt" for K may be understood by many hams, but a newcomer or a non-native English speaker may not know it. Words that sound like other letters or words are the riskiest, so improvised ones fail more often in weak-signal conditions. For the "when" question, a sensible habit is to give your callsign in normal speech first if the signal is strong, and use phonetics when you're answering a call, being asked to repeat, working a pileup or DX, or whenever the other station has to copy it exactly. Many operators give the full callsign in phonetics every time during contests or DX because there is no room for a bad copy. In a casual chat with a strong signal, repeating phonetics every over just adds clutter. Keep it consistent. If you use "Whiskey" for W one time and a different word the next, you add confusion rather than remove it. Pick the standard list, say the words clearly, and don't stack extra explanation on top.
-
Planning a first homebrew QRP station: what to build in what order, and which test gear is worth having
The order makes sense to me, and I'd put the low-pass filter earlier, ideally before the transmitter ever sees an antenna. A single-transistor crystal oscillator with a pi-network output is not a clean source. A 5-pole low-pass filter cut for the band, with a reasonable Chebyshev or Butterworth design, is small and cheap. Rules on spurious emissions differ by country and power level, so check what applies to you rather than assuming a QRP signal is automatically clean. On direct conversion receivers, the AM broadcast breakthrough you mentioned is usually a front-end problem rather than a detector problem. A bandpass filter ahead of the mixer, or at least a high-pass that rejects the medium wave band, often does more than any tweaking after the mixer. Putting a low-pass or simple active filter in the audio path also helps, since a direct conversion receiver passes everything from near DC to the top of the audio range. For CW, a narrow audio filter centered around 600 to 700 Hz makes a bigger practical difference than almost any RF change. On the dummy load, the 7.07 V RMS across 50 ohms per watt is worth having written on the bench. A quick scope check on the load gives you a power estimate before you trust any home-built meter. That ties into the SWR bridge: calibrate it with a known 50 ohm load first (it should read near zero reflected), then with an open and a short, and see that it behaves sensibly. A bridge that has never been checked against known mismatches can give you false confidence.
-
ARES, RACES, SKYWARN, CERT: how do you sort out your training path and what to expect at activation?
I would add that practice nets are where the skill is built. Net control is as much about discipline as it is about voice. Short, calm transmissions, calling stations by tactical call, and not letting the net drift into conversation all help. A clear net structure, with a designated alternate net control and a plan for what happens when repeaters fail, makes a big difference. For traffic handling, practice writing radiograms until the format is automatic, and also practice sending the same information in plain language to an agency that does not know the format. Served agencies usually want an accurate, short message they can act on, not a perfect preamble. And for newer operators: SKYWARN and CERT are good low-pressure entry points. SKYWARN teaches you to report concisely and accurately, and CERT teaches you how an emergency scene is organized. Both carry over well into ARES or RACES work.
-
Keeper rigs: what makes a radio worth holding onto, boat anchor or modern?
For me, the keeper test is whether the radio is still useful if the sentimental part is removed. A lot of vintage gear passes. A good receiver is still a good receiver, and many older rigs were designed with sensible, serviceable layouts. But the practical side matters too. If a rig needs a rare part, has no schematic available, or has been heavily modified, the repair effort can outweigh the fun. On buying used, the usual checklist applies: ask for photos of the inside, ask whether it has been recapped or aligned, and ask about the original manual and accessories. With tube gear, check for burnt resistors, bulging caps and signs of someone getting too creative with the wiring. Shipping heavy gear is also a hidden cost, since a poorly packed transceiver can arrive with broken dial glass or loose tubes. Local pickups are worth a lot.