Everything posted by Admin_Lee
-
SOTA basics for new activators and chasers: summit refs, points, spotting, kit and logging
Two logging habits that save trouble later. First, treat the log as part of the operation: write the time in UTC as you go, because converting from local time after a long hike is where mistakes creep in. Second, record the other station's summit reference when you get an S2S, since that is the detail the database needs to match both sides. For pile-ups at low power, keep exchanges short: callsign, signal report, move on. Work the strongest stations first, then ask for the weaker ones by partial callsign. If conditions are poor, a quick change of band or mode can give you contacts you would never get on the original frequency. For chasers, listen to the activator's pace. Call once when they finish a contact, give your full callsign clearly, and avoid repeating yourself on top of other callers.
-
Part 97 compliance Q&A: ID timing, third-party traffic, power, RF exposure, control operation and license renewal
Picking up the rest. RF exposure (§97.13(c) and the exposure limits in Part 1). Amateurs are not exempt from RF exposure rules. §97.13(c) has a table of power levels by band. If your station's power stays at or under the figure for the band you're on, you're categorically excluded from performing a routine evaluation. Above those levels, you have to evaluate whether your station complies with the exposure limits, using the FCC's guidance (OET Bulletin 65 and its amateur supplement) or measurements or a calculator that models your antenna. The inputs that matter are frequency, power at the antenna, duty cycle (the limits are time-averaged, over a few minutes for controlled environments and longer for uncontrolled ones), antenna gain and pattern, and distance from the antenna to people. Mode matters too: SSB speech has a low average power, while FM, RTTY or FT8 at the same PEP puts far more on average. Neighbors and family count as the general-public category, so you should check where they can actually be, not only where you sit. Spurious emissions (§97.307). This is about energy outside your intended bandwidth. On HF, the requirement is that spurious emissions be well below the fundamental (43 dB below mean power, and not more than 50 mW, for most modern HF transmitters), with a smaller requirement for very low-power rigs. VHF and UHF have their own tiers that get stricter with higher power. The practical issues are overdriving a linear amplifier, which produces splatter and harmonics; running too much ALC or compression; missing or poor low-pass filtering; and bad key clicks. A clean transmitter feeding a well-matched linear and a proper low-pass filter is the best protection. A spectrum analyzer or a nearby SDR can tell you far more than the meter on your amp. License classes. The currently issued classes are Technician, General and Amateur Extra. Novice and Advanced licenses are no longer issued, but existing holders can renew them. Privileges are set in §97.301 through §97.305, and what matters on the air is the privileges of the control operator. A General holder, for example, can't use a segment reserved for Extras just because the station licensee is an Extra, unless the Extra is the one operating as control operator. Auxiliary and control operation. Local control means the control operator is at the station. Remote control means the control operator is at a control point and can turn the transmitter off, typically over a link. Automatic control, with no control operator at a control point, is limited to certain stations such as repeaters, beacons and some digital stations on specified segments (§97.109, §97.213). Auxiliary stations (§97.201) are links, for example between a repeater and its control point or input. They are restricted to the 2 meter and shorter bands, minus some exclusions in the rule. The station licensee is ultimately responsible for proper operation under §97.103, including for automatically controlled gear. Enforcement. The FCC's tools run from advisory letters and Notices of Violation to monetary forfeitures and, for serious or repeated cases, license revocation or suspension. A Notice of Violation sets a response deadline. Take it seriously and respond in writing. Cases in the public record have mostly involved deliberate interference, unlicensed operation, or operation outside amateur privileges. Volunteer observer programs may monitor and report, but the FCC makes the enforcement decisions. Term and renewal. The license term is 10 years. There is a grace period after expiration (currently two years under §97.25), during which you can't transmit but can still renew. Past that, you must requalify by exam. Keep your mailing address and email current in ULS, because FCC notices, including renewal reminders, are sent there. Fee and login details have changed in recent years, so check the FCC's current ULS instructions before you file.
-
Hamfest season prep: what to bring, how to buy used gear, and how clubs can get more out of the day
A good rule for a first hamfest is to walk the whole thing before buying anything, unless you spot something rare and priced fairly. Prices vary a lot between tables, and the same handheld, power supply, or antenna tuner might turn up three times. Take a lap, note the prices, and then go back to the best deal. If you're unsure of the value, look up recent completed listings and compare condition honestly. Remember that a shipped item costs more than the listing price once you add packing and shipping, so a local table can be a bargain even when the price looks similar. For testing, keep it simple. Power the radio and check that all keys, knobs, and the display work. Listen on a few bands, then transmit into a dummy load if the seller okays it. Check for key-up problems, hum, or odd audio. If a seller refuses any test at all, you can make an offer reflecting the risk or just move on.
-
Small lot, HOA, one band or many: which compromise HF wire antenna gives the best return? EFHW vs OCFD vs G5RV vs doublet
I would lean toward the doublet, with a caveat. If you can run balanced line out the window or through a wall plate, a 60 to 70 ft center-fed wire with an ATU and a good 1:1 current balun at the transition can be a very capable multi-band antenna. The part people underestimate is what happens at the transition from balanced to unbalanced. If you use a balun ahead of the tuner, the tuner sees a high-impedance load on some bands, and the balun core can overheat or get lossy. Check the rating and the core size. If your tuner has a balanced output, or you use a dedicated balanced tuner, you skip that problem altogether. For the EFHW fans: it is a perfectly good portable antenna and a good stealth option, since it needs only one support and a feed at the end. But treat the feedline as part of the antenna. A choke of at least several kilo-ohms of common-mode impedance on the coax near the transformer is cheap insurance. If the SWR changes when you move the coax, or your RF-in-the-shack symptoms follow the cable, you probably have common-mode current, not a mystery. Also, measure with an antenna analyzer, not just the rig's SWR meter, and look at both SWR and the resonant points. If an "EFHW" has a decent SWR on every band but the signal reports are poor, suspect loss in the transformer or the feedline. You can test by temporarily swapping in a dummy load or comparing against a simple dipole at the same height.
-
Starting Morse code from zero: Koch, Farnsworth, LCWO, G4FON, CW Academy. How do I pick and not stall?
The first thing to untangle is that Koch and Farnsworth aren't rivals. They answer different questions, and you can use both together. The Koch method is about which characters you learn and in what order. You start with just two characters sent at your target character speed, commonly 20 wpm or so, and copy random groups of only those two until you're getting roughly 90 percent or better. Then you add a third character, then a fourth, and so on. The point is that you never learn a slow, counted version of a character that you later have to unlearn. Every character is a single sound pattern from the first day. Farnsworth is about timing. Characters are sent at a fixed, faster speed, but the gaps between characters and words are stretched so the overall speed is lower. This gives your brain time to identify a character before the next one arrives. Many Koch trainers use Farnsworth spacing at first and let you shrink the gaps as you improve. The usual mistake is sending the characters themselves slowly, because then each one sounds like a string of separate dits and dahs you have to add up. On resources, here is how the ones you mention fit: LCWO (Learn CW Online) is a browser-based Koch trainer with an account system. It tracks your progress, and its lessons run through the character set. It also offers other exercise types, such as words, callsigns, and plain text, once you have enough characters. It suits people who want to practice from any device without installing anything. G4FON's Koch trainer is a well-known downloadable program for the same method. If you prefer a standalone app, or want to run it offline, it's worth looking at. Check the site for the current version and which operating systems it supports, since software like this changes. CW Academy, run by the CWops group, is a structured course with volunteer advisors and small online classes. The main thing a class gives you that an app can't is accountability, a schedule, and someone to ask when you're stuck. Look at the CWops site for current course levels, schedules, and requirements instead of relying on a forum post. Many people pair a class with a trainer app for daily practice. The class gives structure and the app supplies the repetition. If you can only choose one, pick whichever you will actually do five or six days a week. On flashcards and mnemonics: visual charts and word-picture mnemonics can help you remember which pattern belongs to which letter, but they work against you if you rely on them at speed. If you find yourself thinking dit-dah-dit to decode a letter, you're translating, and translating is what stalls people around the low teens in wpm. A quick look at a chart to confirm a character you missed is fine. Anything that makes you visualize dots and dashes while listening is a habit to drop early.
-
SSB audio setup: mic gain, ALC, compression and bandwidth for clean signals and weak-signal DX
Good list. One addition on ALC: some rigs have separate meters or settings for compression level and ALC, and it is easy to confuse them. Compression level normally shows how hard the processor is working, while ALC shows how close you are to overdriving the final stage. If your radio has a processor, set it in order: mic gain first with the processor off, then enable it and set compression, then check that ALC is still in range. Doing it in a different order often gives misleading readings. On the equalizer, make small changes and test them one at a time. A big bass cut and a big treble boost together can leave a thin, harsh sound that looks fine on paper but is tiring to copy over a long QSO. If you aren't sure, a flat or mildly adjusted setting with a good mic position is usually safer than a dramatic preset copied from someone else's radio, because their mic and room are different.
-
Field deployment layout: keeping generator and solar noise out of the receiver while staying safe on power and grounding
On power, I'd start from the loads and work backward. List every device, its current draw on receive and on transmit, and how long it will run. For 12 V systems the usual approach is a fused feed directly off the battery, then a distribution block with an individual fuse for each branch. Size the wire for the fuse and the length of the run so that voltage drop under transmit stays small. Many rigs misbehave or lose output if the voltage sags at the radio, so measure at the radio's terminals under transmit, not just at the battery. A LiFePO4 pack holds its voltage well during discharge, but check the radio's operating range, since a fully charged pack sits above 13 V. Most rigs tolerate that, but not all accessories do. Also don't charge LiFePO4 below freezing unless the pack has low-temperature charge protection, because that is a known way to damage cells. Cold weather matters for this reason. On masts and antennas: keep guy lines flagged so people don't walk into them, and keep the whole antenna system well clear of power lines. A common rule of thumb is to stay at least one and a half times the mast height away, but the safest approach is to pick a spot where the question never comes up. Fiberglass poles are popular because they don't conduct, though a wet pole isn't a reason to get complacent. Account for wind: use proper guying, stakes sized for the soil, and a plan for lowering the mast if the weather changes. Tents and shelters should be placed so that, if the mast fell, it wouldn't land on the operating position. Keep VHF antennas away from the HF antenna's near field and from the operators. A basic checklist structure that works for both setup and teardown: site survey and hazards first (power lines, ground, wind, access), then shelter and generator placement, then the mast and antennas, then the coax and power runs with strain relief and drip loops, then the station itself, and last a pre-operation test including a noise check, SWR check, and a radio check with a net or another station. Teardown should run in reverse, with the antennas and mast lowered first, a headcount of stakes and cable, and the generator cooled before it's packed. Print it, laminate it, and revise it after each exercise. The first few runs usually show what the list is missing.
-
VHF/UHF antenna choices: J-pole vs 5/8 whip vs collinear vs yagi, and where coax, connectors and SWR fit in
I'd add that the feedline and connectors can cancel out the choice of antenna, especially on 70 cm. Loss in coax rises with frequency, and small-diameter cable like RG-58 can eat a large share of your power over a long run at UHF. Check the manufacturer's datasheet for loss per 100 ft at your frequency instead of trusting generic tables. Low-loss cables like LMR-400 type or hardline are far better for runs of a few tens of feet or more. For a short mobile run, thinner coax is fine. On connectors, PL-259/SO-239 (UHF) connectors are common and work well enough on HF and often on 2 m. They are not constant-impedance and they aren't weatherproof by design, so they get worse at 440 MHz and above. N-type connectors are a 50 ohm design, have a gasket for weather sealing, and are much better for outdoor UHF and base or repeater installs. Whichever you use, seal outdoor connections with self-amalgamating tape and then a layer of vinyl tape, and form a drip loop so water doesn't run down the cable into the shack. On SWR: it tells you about the match, not about how well the antenna radiates. A dummy load has excellent SWR and radiates nothing. Also, long, lossy coax can make SWR look better than it actually is at the antenna, because the loss attenuates the reflected power on its way back. If you want to check the antenna itself, measure with a short known-good jumper, or at the antenna end of the feedline if possible. For mobile installs, an NMO mount through the roof gives the most reliable ground plane and keeps the whip centered. A magnetic mount is easier and non-destructive, but it relies on capacitive coupling to the body and can vary a lot with the surface and how clean the contact is. Mount magnetic bases on a flat area of the roof, away from the edges, and avoid putting them on trunk lids or places where the ground plane is small.
-
Getting the most from a budget SDR on HF and VHF: gain staging, dynamic range, antennas and decoding
My vote for the most common antenna mistake is skipping common-mode control. A dongle on a USB cable next to a PC is a perfect path for noise to travel along the coax shield and into the receiver. A decent common-mode choke at the feedpoint and another near the receiver often does more than swapping the antenna. A USB extension with ferrites, or a powered hub that is not a noise source, can also change the noise floor noticeably. If the waterfall is full of regular spikes every few kHz, suspect switching power supplies and LED lighting before blaming the dongle. On antenna choices, a random wire with a 9:1 unun, an end-fed half-wave with a 49:1 transformer, and a small active loop are all common for HF. Each one trades off differently. An active loop can sit away from local noise and is directional, which helps reject interference, but the active electronics can overload near strong broadcast stations. A longer wire picks up more signal and more noise. With an 8-bit dongle I would lean toward a passive antenna plus filtering, since strong signals are more of a risk than weak ones. One more point on your gain staging steps: if you use a bias tee to power an LNA at the antenna, remember that the LNA's gain and noise figure set the system noise before the dongle ever sees the signal. Placing the LNA at the antenna side, after the choke and before the long coax, is generally better for VHF/UHF reception. But more LNA gain also makes overload more likely.
-
APRS 144.390 setup notes: paths, Mic-E, SmartBeaconing, Direwolf iGate and checking results on aprs.fi
For checking an iGate, aprs.fi is useful because you can open a station's raw packets and read the path. Packets that came in over RF and were gated usually carry a q construct such as qAR or qAO along with the iGate's callsign, so you can see which iGate put them on the internet. If your own packets never show up there, work backward. First, is the radio really transmitting on the right frequency? Second, can another station or iGate hear you? Third, is the packet being decoded properly, and is the path sensible? Direwolf's console output is handy here because it shows what it received on RF. A couple of Direwolf notes. Use unique SSIDs so your iGate, digipeater and mobile don't all appear as the same station. Don't enable both digipeating and internet-to-RF gating without understanding the consequences, because careless IS-to-RF gating adds traffic to a channel that is already narrow. Many iGates only gate messages for stations they have recently heard on RF, which is the right design. On weather and objects, one practical point: the weather packet format is picky about field widths, and missing values are filled with dots or spaces rather than left out. If aprs.fi shows a station as a weather station but displays odd values, compare the raw packet to the format spec. Units are also easy to mix up, since temperature is in degrees Fahrenheit and pressure is in tenths of a millibar in the standard format.
-
Band plans vs. FCC rules: how to find where you can legally operate, and where you should, from 160 m to 33 cm
Start with the legal versus voluntary split, because it answers half your questions. Part 97 (mainly 97.301 to 97.305) is the law. It sets which frequencies each license class may use, which emission types are allowed in each segment, and the power limits. The ARRL band plan is a voluntary guide that says where the community has agreed to put CW, digital, SSB, beacons, repeaters and so on. Operating outside the plan won't earn an FCC citation, but you may cause interference, and other operators will tell you about it. Operating outside your privileges is a violation. US HF privileges by class are easiest to remember as slices. Extra has everything. General has most of each band but not the bottom of the 80, 40, 20 and 15 m phone bands. Those slices are Extra-only: 3.600 to 3.800, 7.125 to 7.175, 14.150 to 14.225 and 21.200 to 21.275 MHz. Extra also has small exclusive CW/data slices at the very bottom of 80, 40, 20 and 15 m (3.500 to 3.525, 7.000 to 7.025, 14.000 to 14.025 and 21.000 to 21.025). General phone starts at 3.800 on 80/75 m, 7.175 on 40 m, 14.225 on 20 m and 21.275 on 15 m. On 10 m, General can use 28.000 to 29.700 MHz. Technicians have limited HF: CW on parts of 80, 40 and 15 m, CW and data on 10 m from 28.000 to 28.300, and SSB on 10 m from 28.300 to 28.500, all capped at 200 W PEP. Technicians get all privileges on 50 MHz and above, which is why 6 m, 2 m and 70 cm are the usual starting bands. Novice and Advanced licenses are no longer issued but are still valid for existing holders, so you may hear those slices mentioned. Band edges are about occupied bandwidth, not your dial readout. A signal that reads 14.349 on the dial in USB puts its upper sideband above 14.350. Keep the whole signal inside, roughly 3 kHz for SSB. On USB, set the dial at least that far below the upper edge. On LSB, set it that far above the lower edge, so a General on LSB at the 3.800 edge should sit at about 3.803 or higher. Dial calibration errors and your own audio processing add more margin to worry about, so I leave a bit extra. Digital modes like FT8 sit at a dial frequency plus an audio offset, so the same logic applies. Add your audio tones to the dial frequency and make sure the highest tone is still in band. The 60 m band is channelized, not a continuous band, in the US. The five channels, listed as USB dial (suppressed-carrier) frequencies, are 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz. They're open to General, Advanced and Extra, but not Technician. Amateurs are secondary users there, so interference to federal users is a real issue, and the power limit is expressed as ERP relative to a half-wave dipole, not as transmitter output. The FCC also added a small power-limited segment around 5351.5 to 5366.5 kHz after WRC-15. Check 97.303 for the exact power and mode details before using it, because 60 m is the band where small details matter most. For digital on HF, the common FT8 dial frequencies are 1.840, 3.573, 7.074, 10.136, 14.074, 18.100, 21.074, 24.915 and 28.074 MHz. These are conventions, not rules, but they let everyone find each other. The 30 m band (10.100 to 10.150) is CW and data only, with a 200 W PEP limit, so no phone there. Also stay away from beacon frequencies like 14.100 on 20 m and the 28.200 to 28.300 beacon sub-band on 10 m.
-
Building a ham go-kit that actually works: power, antennas, and a family plan that doesn't depend on everyone having a license
I'd put a recurring test on the calendar before buying anything new. The most common failure with go-kits is stale gear: dead batteries, a cable with the wrong connector, a radio programmed with repeaters that changed. Pick a day each season (some people tie it to daylight saving time changes) to pull everything out, charge it, run each radio on its battery pack, make a contact on simplex, and confirm the weather radio alerts. Replace anything that fails and keep a short checklist in the bag so you know what's supposed to be there. On power, label each battery with the date you last charged it, and write the watt-hours on it so you can estimate runtime. If you're using lithium cells, follow the manufacturer's guidance on storage charge and temperature, since leaving them hot in a car trunk is hard on them.
-
What makes a rig a keeper? Ergonomics, receiver performance, or just the way it feels on the desk?
I'd add one more factor: how a rig fits the kind of operating you actually do, not the kind you imagine doing. A lot of radios get sold because the owner bought for contesting or DX pileups and then mostly ended up doing casual nets or ragchews. In that case a simpler radio with a comfortable receiver and good audio might have been the better buy. Resale is worth thinking about too, but I wouldn't let it drive the decision. Radios with large user communities, available manuals, and a reputation for repairability tend to be easier to sell and easier to keep running. That counts as a feature even if it never shows up in a review. As for the vintage question, I think the answer is that it depends on what you enjoy. If you like the restoration itself, a project rig is the hobby. If you just want to get on the air, buy something already sorted and spend the savings on a better antenna. That usually does more for your signal than any rig upgrade.
-
New to ham radio shorthand: what do QRM, QRN, QRP, QSY, 73, 88, K, KN, SK and the rest actually mean?
Q codes first. QRM, QRN, QRP, QRO, QRT, QRZ, QSL, QSO, QSY, QTH, QSB and QRL are all Q signals. They started as three-letter shorthand for radiotelegraph and are still very common in amateur use. CQ, DE, K, KN and SK are not Q codes. They are calls or prosigns. 73 and 88 are numeric shorthand. Here are the common meanings in ham usage: QRM is interference from other stations or man-made sources, such as a nearby signal on your frequency. QRN is natural noise, such as static or thunderstorm crashes. QRP means low power. By common convention that is about 5 watts on CW or 10 watts PEP on SSB. QRO means high power, or increasing power. QRT means stop transmitting or shut the station down. "I'm going QRT" means I'm signing off for now. QRZ means "who is calling me?" Sending "QRZ?" usually means you heard someone but missed the callsign. QSL means "I acknowledge receipt" or "understood". A QSL card confirms a contact. QSO is a two-way contact, a conversation. QSY means change frequency, as in "QSY to 14.250". QTH is your location. QSB is fading signal strength. QRL means "I am busy" or "this frequency is in use". On the question mark: a Q code with one is a question, and without one it is a statement or answer. "QRL?" asks whether the frequency is in use. A reply of "QRL" means yes, it's busy. "QTH?" asks where you are, and "QTH Denver" tells someone where you are. Similarly, "QSY?" asks if you can change frequency, and "QSY 7.040" says you're moving there.
-
Organizing award chasing: DXCC, WAS, WAZ, WPX, IOTA, Marathon, POTA and SOTA, and how to keep the credits straight
One practical point on confirmations: LoTW is convenient because the matches arrive without waiting for a card, but a match only happens when both stations upload and the QSO details line up closely enough, including date, time, band and mode. So when a QSO you expected to match doesn't, the usual cause is a mistake on one side: a wrong band, a wrong callsign, or a certificate that doesn't cover the QSO date for that station. It's usually worth checking your own log before blaming the other station. Also look at how each program treats confirmations. ARRL awards and CQ awards don't necessarily accept exactly the same things, and IOTA has its own checkpoint-based process, so read each program's current rules before you assume a credit transfers. POTA and SOTA are a different case again. As a hunter or chaser, you mostly need your log to match the activator's, so if a credit seems to be missing, compare callsign, date, band and mode with what the activator uploaded. For applications, a sensible approach is to submit once you have a meaningful batch, not one contact at a time, because it's easier to review what you're claiming. Keep your own record of what's been submitted and credited, so you don't count the same contact twice when you plan the next step. And for Marathon, remember that the score starts from zero each year, so a different plan is needed, for example concentrating on new entities and zones early in the year when everything is new.
-
Planning a first homebrew QRP station: what to build first, and what test gear actually earns its bench space?
On the transmitter side, the Tuna Tin 2 and Pixie are good to build as exercises, but treat them differently. The Tuna Tin 2 is a crystal-controlled transmitter of roughly a watt class. It is a good place to practise tuning the output network for maximum output into a dummy load and then checking that the result is clean. The Pixie packs a lot into very few parts, and its selectivity is limited. It is a good way to learn how the stages work, but a poor guide to what a well-designed receiver should sound like. For the SWR bridge, don't just trust it because it moves. Check it against known resistive loads. A 50 ohm load should read close to 1:1. A 100 ohm resistor, or two 50 ohm resistors in parallel to give 25 ohms, should read near 2:1. Do this at low power. If the forward and reflected readings are way off, check the diode orientation, the toroid winding sense and the symmetry of the layout. For low-pass filters, calculate the values with a filter tool, wind the toroids with the correct material and turn counts, and sweep the result with a NanoVNA. Powdered-iron cores such as the red (-2) and yellow (-6) mixes are common for this, but check the design's specified core before swapping. Also keep in mind that hand-wound inductors rarely land exactly on the calculated value, so sweeping the finished filter tells you more than the arithmetic does. For soldering, tin the ends of enameled wire properly and look at the joints under magnification. Cold joints and leftover flux cause strange faults that waste hours.
-
Remote station design: RS-BA1, SCU-LAN10, RigPi, Flex, and keeping the whole thing secure and legal
For CW, I'd separate the local sidetone from whatever comes back from the remote radio. If you only hear the received signal, the round-trip delay makes sending feel like speaking with an echo, and a lot of people find that more tiring than the actual delay. A local sidetone with remote keying handled by a keyer at the station is usually the fix. Some people prefer to send full characters or text to the remote keyer to avoid timing distortion altogether, at the cost of losing paddle feel. On the rules side, the key point worth stressing is that the remote station doesn't make you a guest in a legal sense. If you operate a station that isn't yours, whether through a shared platform or a friend's setup, check who is responsible as station licensee and control operator, and don't assume the platform has verified your privileges for the country where the transmitter sits. For anything non-trivial, the national regulator's guidance is the authority, not a forum post, and that includes this one.
-
Rate vs. multipliers: how do you decide when to stop running and go hunting (and where does SO2R fit)?
On Skimmer and packet spotting: treat spots as hints, not as logged data. Spots can be busted calls, a wrong frequency, or old news. With CW Skimmer or RBN-fed spots you usually get a callsign that's mostly right, but weak or fast stations can be decoded wrongly, and a wrong call logged is a lost QSO and sometimes a penalty. Click the spot, listen for the station to give its call, and only then log. If you're using a Telnet cluster in an assisted category, filter by band and mode so the bandmap isn't flooded, and remember that being in the assisted category is the price of using spots at all. In unassisted classes, spots from clusters or the Reverse Beacon Network aren't allowed, so make sure you're in the right category before you leave the telnet window connected. On antennas, the most useful lesson is that a few good compromises beat a single big antenna. A stack of Yagis lets you pick a takeoff angle for the path, and a single high Yagi alone may be poor for some openings. On the low bands, the receive antenna often matters more than the transmit one, since a Beverage or a small receiving array can make the difference between hearing weak stations and sitting in noise. For SO2R, being able to put the two radios on different antennas, ideally with different polarization or direction, cuts the interference problem a lot. For fatigue, the most reliable plan is to write one before the contest: when you'll sleep, when you'll eat, and which hours you expect to be slow. Making a call like 'band is dead, take a nap now' is much easier than staying on the radio at a 20-QSO-per-hour rate. Keep water and simple food within reach, lower the audio volume, and take short breaks to rest your ears and wrists. A rested operator usually makes far fewer mistakes in the last hours than one who stayed at the radio the whole time.
-
Lightweight go-kit for POTA and SOTA: EFHW or linked dipole, which pole, and what battery setup?
One thing that's easy to underestimate is how much the transmit duty cycle changes your battery math. A 100 W rig can pull in the region of 20 A on SSB peaks, but a 5 W QRP rig is closer to 1 to 2 A, and receive current is low in either case. For a rough planning number, estimate your average current over an hour of operating, multiply by the hours you expect to be on the air, then add a margin. A 6 to 10 Ah LiFePO4 pack covers a long QRP session and a decent amount of low-power SSB, but it won't carry a 100 W rig for long. It's also worth labeling your power connectors and fusing the battery lead close to the pack. Anderson Powerpoles are common because they are polarity-consistent when everyone uses the same convention, which matters for Field Day style group setups where gear gets borrowed. A small inline fuse costs almost nothing and protects the wiring if a lead gets crushed in a pack.
-
Choosing a first (or next) handheld: FT-65R vs Baofeng vs D-STAR/DMR HTs, plus batteries, antennas and CHIRP
I'd separate the choice into three questions: which modes you'll actually use, how much receiver quality matters where you live, and how much hassle you'll tolerate in programming. For analog-only, the FT-65R is a straightforward, rugged choice with simple controls. A Baofeng is fine for learning the basics, but check the rules for your country. Cheap radios can radiate harmonics and spurs, and as the licensee you're responsible for your signal. In a dense RF environment (near towers), a cheap receiver can also get swamped. On the digital side, D-STAR radios like the ID-52A and TH-D75 only help if there are D-STAR repeaters or reflectors you can reach. Check your local coverage before buying. DMR is the same story, but with the added step of getting a radio ID and building a codeplug with the right color codes, time slots and talkgroups. The IC-705 is a different animal: great if you want HF/SSB/CW portable operation as well, but it's not something you clip on a belt for a quick repeater check. For emergency use, a cheap spare analog HT and a good spare battery are often more practical than one high-end radio you're afraid to scratch.
-
Getting real results at 5 watts: rigs, antennas, calling frequencies and LiFePO4 power for portable QRP
Building is where QRP gets interesting. A kit teaches you how a superhet or direct-conversion receiver, a VFO or DDS, a low-pass filter and a keyed final fit together, and the same parts of a rig make troubleshooting easier later. If you have not built before, a simple single-band CW kit with a good manual is a better start than a multiband one. Basic tools help more than expensive ones: a temperature-controlled iron, a decent multimeter, and a dummy load. A 50-ohm load and an SWR or power meter let you check output and harmonics before you put it on the air. Low-pass filter design matters even at 5 W, since a clean signal is part of being a good neighbor on a crowded band. For operating, QRP-ARCI is the best-known organization, with contests, awards and a long tradition of QRP operating. Their rules and contest definitions are on their website, so check the current versions before entering. Contest exchanges often include your power level, which can make low-power stations stand out and often draws extra attention from stations hoping to log a QRP contact. For a first CW setup, a few habits help a lot. Send at a speed you can copy comfortably, call CQ for longer than feels natural, and listen for a full cycle before calling. Be patient on a crowded band and use the calling frequencies when the band is busy. And if you are choosing between a bigger battery and a better antenna for a portable setup, the antenna usually wins.
-
Making SET and Field Day Count: Scenario Ideas, Net Scripts, and What After-Action Reports Should Capture
On served agencies, I think the biggest gap in many exercises is that the agency isn't really in the loop. If SET only involves radio operators talking to each other, you learn whether the radios work, but not whether the agency can use what you provide. If possible, ask the agency's emergency manager or a designated contact to write the scenario injects or at least review them. They know what information they would actually need, such as shelter occupancy, road status, a resource request, or a welfare check, and in what form. Ask them how they want messages delivered, whether on paper, by phone, or hand-carried, and who is authorized to sign off or accept them. It also helps to be clear about roles. Amateur operators carry communications; they don't decide for the agency. Writing that expectation into the exercise and the after-action report prevents friction later. And when you write the report, include the agency's feedback alongside your own observations, since they may see problems you didn't, such as messages that were accurate but too long, or traffic that arrived with no clear action requested.
-
Planning a 100 W HF shack: signal chain order, power, and grounding vs. bonding
On filters, it depends on how the shack is used. A single operator on one antenna on one band at a time usually doesn't need BPFs. They start to matter with a multi-op or SO2R-style setup, where one transmitter's energy can reach another receiver. In that case the filter belongs on the receive/transmit path of each radio, ahead of the antenna switch. Check the filter's power rating and its SWR tolerance too. A BPF can get unhappy with a bad mismatch, which is another argument for tuning at the antenna and not just at the desk. Where an amp is concerned, be careful with the keying line and ALC. If the amp has band data and a keyline, make sure the radio releases the relay before RF goes out. If the drive is higher than the amp wants, back the radio down to the amp's rated input rather than hoping the ALC will sort it out.
-
APRS on 144.390: Direwolf iGate/fill-in digi plus handheld tracking with SmartBeaconing, paths, and messaging
On the stationary handheld question: if a digipeater or iGate hears you directly, extra hops add little. A reasonable starting point is a single WIDE1-1, or a longer interval with a modest path. The rule is that the path should only be as long as the number of hops you need. Anything that gets repeated by three digis shows up as three copies on everyone's receiver. For RX-only versus TX, the safest order is to run the iGate receive-only first and watch aprs.fi for a few days. That shows which stations you actually hear and whether the sound card levels are sane. Direwolf logs audio level per decoded packet, so aim for decode levels in a healthy middle range instead of clipping. Only turn on TX iGating once you understand local activity, and keep the internet-to-RF gating limited to messages for stations you've heard locally. A fill-in digi is only worth adding where a hill, a valley, or a building leaves an obvious hole that you can verify with test beacons. Otherwise you add duplicate traffic without adding coverage.
-
First power-up of a homebrew QRP rig: what to check before the antenna goes on
I'd put more weight on the dummy load. A badly made one can mislead you more than having none. A cluster of carbon resistors on short leads is fine at 5 W on HF, but a wirewound resistor can show reactance and give you strange SWR readings on the higher bands. If you're testing a 1 to 5 W rig, a few 100 ohm metal film resistors in parallel, with short leads and a decent ground plane, is an easy solution. Check it with the same bridge you plan to use for the rest of the testing. Also keep the first key-down periods short. A resistor can get hot faster than you expect, and a transistor PA without enough heatsinking can drift or die before you have time to look at the scope. Key it for a second or two, check the DC current, then stop and look. One more thing: if the DC current rises a lot but you see little RF on the load, don't just keep adjusting the trimmers. That usually points to the PA stage oscillating, a missing bypass capacitor, or a stage running without a proper load or bias.