Everything posted by Admin_Terry
-
Radio mods that are worth doing (and the ones that cause trouble): expanded RX, filters, TCXO, power, fans, and staying legal
Agree on authorization for MARS and CAP, and I would go further: the mod discussion often skips the part where the program may specify certain radios, programming procedures, or frequency use. Check with your own coordinator first, because the rules differ between programs and can change. Treat any forum list of the right mod as a starting point, not permission. For firmware, one habit that saves headaches is to save the codeplug, read the radio's current settings, and write down the version before you flash. If you use third-party firmware, test the output on a dummy load with a meter and a second receiver or SDR to look at spurs, because features can be added without the same RF tuning the manufacturer did. For TCXO work, the calibration step gets skipped a lot. If the frequency is not measured against something reliable afterward, you do not know whether the mod helped. A GPS-referenced counter or even WWV on a frequency your rig can receive is enough to tell you whether you are close. Also check the radio's own service manual for the intended reference adjustment point before you start poking at trimmer capacitors.
-
Building a 5 W portable station: rig choice, antenna, and power for QRP CW and SSB
One thing I'd add about the kit and Pixie side of this: building is a legitimate reason to do QRP, not just a way to save money. A Pixie-style rig teaches you how a transmitter, keyer and receiver detector work together, and it's quick to build. Just expect the receiver to be broad and prone to overload from strong signals. If you're after contacts rather than learning, a more selective design or a commercial kit will be less frustrating. On LiFePO4, I'd double-check the voltage window at both ends. A fully charged pack can sit above 13.8 V, which is fine for many rigs but not guaranteed for all. At the low end, the flat curve means the voltage doesn't give you much warning before the protection circuit cuts off. A small voltmeter inline, or a rig that displays supply voltage, makes this easier to manage. Also, if your rig draws only a few hundred milliamps on receive, a small pack lasts much longer than people expect. So size the battery from current draw and operating time, and don't just buy the biggest cell you can carry. For operating, use the calling frequencies as a starting point, but also tune around and answer CQs. With 5 W you'll often have better results calling a station that is already listening than sitting on a frequency and hoping. Short exchanges, a clean CW fist and patience with repeats make a big difference. If you're interested in contests, QRP-ARCI-related activity is a good way to find other low-power stations.
-
ARES vs. RACES vs. SKYWARN vs. CERT: how do you organize training so you're actually useful at an EOC or net?
One thing that helps is separating the roles that tend to get blended together. A radio operator at an EOC is usually there to move information for the agency, not to decide what the information means. Keep a clean log with time, from, to and message text, and let the EOC staff make the calls. If a message is unclear, ask the originator for clarification rather than guessing. On training order, a reasonable path is the free FEMA courses for ICS vocabulary first, because they make everything else easier to follow. After that, do net procedure practice on a weekly net, then a tabletop exercise, then a functional exercise where you actually move messages between locations. Skipping the middle steps usually shows up as sloppy traffic during the big drill. Also worth practicing: what happens when the repeater is down. A plan that depends on one machine isn't a plan. Have a simplex fallback, agreed frequencies, and a way to relay if someone is out of range.
-
SSB audio that gets through: mic gain, ALC, processing and filters, from clean local audio to weak-signal DX
For weak stations and DX, the receive side matters as much as the transmit side. A 2.4 kHz filter is a good default, but narrowing to about 1.8 to 2.2 kHz can reduce noise and adjacent splatter when the band is busy. If it's still hard to copy, try the passband tuning or IF shift to move away from the interference before reaching for heavy noise reduction, which can leave speech sounding watery. Using a notch for a carrier is often better than narrowing further. AGC speed also matters: a fast or medium setting can keep a strong neighbor from making the weak station pump in and out. On the transmit side, speak slightly slower than normal, give your callsign clearly, and use standard phonetics. Calling in a DX pileup, short and precise beats loud and long. If the DX is working split, put your transmit VFO where they are listening, check that it's clear, and don't transmit on their frequency. Also listen for a while to learn their pattern before calling. Keep the processor moderate, since a clean, intelligible signal is more useful than an extra few dB of average power that comes with a harsh sound. If you have a second receiver or SDR, look at your own signal occasionally to check bandwidth and splatter, especially with a processor and an amplifier in the chain.
-
SOTA basics for new activators and chasers: summit refs, points, kits and staying safe
As a chaser, a few habits make life easier for activators. Listen first, make sure you have the callsign and frequency right, and send a short, clean call. Do not stack on top of a weak station. Give the report, confirm the summit reference when needed, and keep the exchange brief so the activator can reach four contacts and keep the pileup moving. It also helps to keep your own log organized by summit reference and date. If you want chaser credit, a messy log is a pain to sort out later. And if you hear a station you cannot work, a spot can still be useful, but only when you are sure of the callsign and frequency. Bad information on SOTAwatch wastes everyone's time. For activators building a lightweight kit, I would add one thing to the packing list: a short written checklist. It is easy to forget a coax adapter, a key, spare batteries or the pencil when you pack at home. A small list taped inside the radio bag solves that.
-
Where do I actually operate? Band plans vs. FCC privileges, band edges, 60 m channels, and VHF/UHF calling frequencies
Picking up the other half: 60 m, VHF/UHF, and the international side. 60 meters isn't a band in the usual sense. In the US, amateurs have access to five specific channels, not a continuous range. The channel center frequencies are 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz. Because phone on these channels is USB, the dial frequency you tune is 1.5 kHz below center: 5332.0, 5348.0, 5358.5, 5373.0 and 5405.0 kHz. This is the most common 60 m mistake, so check which number your logging software or a chart is quoting. The channels allow phone, CW and certain data modes within a 2.8 kHz bandwidth, with a power limit of 100 W PEP ERP relative to a half-wave dipole. General and Extra licensees can use them, and the amateur service is secondary there. There is also a newer international allocation at 5351.5 to 5366.5 kHz from WRC-15, but how it is implemented varies by country, so check current FCC and local rules before assuming it applies. On VHF/UHF, the useful simplex calling frequencies are: 6 m (50 to 54 MHz): 50.125 MHz is the SSB calling frequency, 52.525 is the FM simplex calling frequency, and 50.313 is the FT8 frequency. CW and beacons sit at the bottom. 2 m (144 to 148 MHz): 146.520 is the national FM simplex calling frequency, 144.200 is the SSB/CW weak-signal calling frequency, and 144.390 is APRS in North America. Repeater pairs are mostly 600 kHz offset (inputs and outputs in the 146.6 to 147.4 range), so stay out of the repeater subbands for simplex. 70 cm (420 to 450 MHz): 446.000 is the national FM simplex calling frequency, and 432.100 is the weak-signal calling frequency. Repeaters normally use a 5 MHz offset. This band is secondary, with geographic restrictions near some radar installations and near the Canadian border (Line A), so check 97.303. 33 cm (902 to 928 MHz): this is a Region 2 allocation, shared with ISM and Part 15 devices, and the amateur service is secondary. 903.100 MHz is a commonly used weak-signal calling frequency. Activity is far thinner than on 2 m or 70 cm, so check the current band plan for FM and repeater arrangements. Also be aware of the National Radio Quiet Zone restrictions. On the international side, the ITU divides the world into three regions, and allocations differ by region and by country. A few examples: 80 m is 3.5 to 3.8 MHz in Region 1 but 3.5 to 4.0 in Region 2. 40 m is 7.000 to 7.200 in Regions 1 and 3 but 7.000 to 7.300 in Region 2. 2 m is 144 to 146 in Region 1 but 144 to 148 in Regions 2 and 3. 70 cm is 430 to 440 in Region 1 but 420 to 450 in the US. 6 m is not available everywhere in Region 1, and where it is, the allocation is often narrower. Individual countries then add their own restrictions. So when you work DX, expect stations in other regions to be listening in a different subband than the one you'd use at home, and you may hear split operation for that reason. If you plan to operate abroad, check the host country's rules, including whether your license is covered by a reciprocal agreement and which local class it maps to, rather than assuming your US privileges carry over.
-
Small-yard HF antennas: how to compare EFHW, OCFD, G5RV, doublet and vertical options without trusting SWR alone
With one 30-ft support and about 60 ft of run, a doublet or a shortened dipole fed with ladder line is hard to beat for flexibility. A roughly 60-ft flat-top is close to a half-wave on 80 m only if you stretch it, so think of it as a good performer from 40 m up and a compromise on 80/160 m. Feed it with ladder line and a balanced tuner (or a tuner with a good 4:1 balun) and keep the ladder line away from metal for the first several feet. Avoid choosing the length purely for resonance on one band; check the modeled feedpoint impedance for each band you care about, because some lengths put you at very high impedance on a band you plan to use and make the tuner struggle. If you must use coax, a simple resonant inverted V for a single band plus a decent choke is much more predictable than a multiband design that depends on the tuner. SWR can be flat, but the pattern from a low inverted V on 40 m will still be mostly high-angle.
-
Callsign basics: sequential vs. vanity, groups, club and special event calls, and what to check before you change
One tip on vanity: put real thought into the order of your list. Your first choice is not guaranteed, and the system takes the first available call on the list, so a throwaway choice near the top can be granted before the call you actually wanted. Check each candidate in ULS first, then look at whether it was recently held and why. A call that looks open might be inside the waiting period, and an application for it can fail. Also think about how the call sounds on CW and phone. Suffixes with several similar letters, like long strings of S, F or M, can cause trouble over a noisy path. Say it out loud with phonetics before you commit, because once granted you will be saying it for years.
-
Building a ham go-kit that actually works: power, antennas, and what to do when the repeater is down
I'd add a rotation schedule. A kit that was complete once can be half dead a year later. A calendar reminder every few months to charge batteries, check dates on food and medications, power up every radio, and confirm the printed frequency lists still match the actual repeater coordination works well. Label each battery with the date you last charged it. On the grid-down side, treat repeaters as nice to have. Many have battery or generator backup, but the runtime is often limited and may not be known to you. So practice simplex: pick a few spots around your area and see what you can actually reach with an HT and with a mobile. Then you know which stations could act as relay points. A net control operator can also use that information when deciding where to send people. One more thing for the antenna bag: pack a few feet of paracord, tape, and a small tool kit. A lot of antenna problems on deployments come down to supports and connectors rather than the radio.
-
One master log across N1MM Logger+, WSJT-X and Log4OM: where ADIF, Cabrillo and uploads usually go wrong
For the post-contest order, I'd do the Cabrillo export first, while the contest logger is still the authority for the exchange fields. Before sending it, run the logger's own dupe check and check the score summary, then open the file in a text editor. Look at the header, the callsign, and whether the QSO lines have the expected number of fields. Most sponsors have a web upload page or an email robot that confirms receipt, so keep that confirmation. Rules and deadlines differ from contest to contest, so read the current rules for each one rather than assuming last year's settings still apply. After that, export ADIF from the contest logger and import it into the long-term logbook. Set a backup point first, because an import is hard to undo cleanly. A few things to check on the import: Does the band/mode mapping come through correctly, especially for digital submodes? Did the logbook flag duplicates, or just add everything? Are your own station fields (grid, zones, operator) filled in correctly? Only then sign and upload to LoTW, and push to QRZ and Club Log. On dupe rules: the contest logger applies the contest's own rules, such as one contact per band or per band and mode group. The long-term logbook has no such rule. A QSO that is a dupe for contest scoring is still a valid log entry, so don't delete it from the master log just because the contest logger marked it a dupe.
-
From-scratch wire antennas: wire choice, chokes, ladder line, radials and modeling before you cut anything
On the feedline, the choke matters more than the balun label. A dipole fed with coax can have current on the outside of the shield, which distorts the pattern, pushes RF into the shack and changes the SWR reading depending on how the coax is routed. A 1:1 current balun or choke at the feedpoint is the standard fix. Ferrite beads or toroids on the coax, or coax coiled into several turns, can both work. The core mix has to suit the band. Type 31 is commonly used on the lower HF bands and type 43 higher up. The choke's impedance at the operating frequency matters more than the turn count, and an analyzer can show you whether it's actually working. A second choke at the shack end is cheap insurance if the feedline runs near other wiring. If you use ladder line instead, the usual setup is 450 ohm window line or similar, run to a tuner. The line itself has very low loss even at a high SWR, so the loss comes from the tuner and any balun after it. Keep the ladder line a few line-spacings away from metal gutters or siding, and let it fall away from the antenna at right angles for a stretch rather than running parallel to the wire. Where it meets coax, put the choke on the coax side. A high-ratio balun on a very reactive load can overheat or lose a lot of power, so don't assume a 4:1 is automatically suitable. For SWR measurement, an antenna analyzer at the feedpoint, with the choke in place, tells you far more than a meter at the shack. The R and X readings tell you whether the antenna is short or long, and the lowest SWR isn't necessarily the resonance. Be aware that strong AM broadcast stations can disturb readings on 160, 80 and sometimes 40 m. Test the analyzer into a known dummy load first.
-
Online Amateur Radio License Exam Session (WEARC, SANDARC VEC)
until
The West Essex Amateur Radio Club's volunteer examiner team runs online license exam sessions for Technician, General and Amateur Extra candidates. This session is listed for Friday, November 27, 2026, 7:30–9:30 PM EST, under SANDARC VEC, and is a free exam. The club lists session times in Eastern Time (America/New_York). Registration and availability are confirmed on HamStudy. Remote sessions accept candidates from across the United States and from other countries.Location: Online (remote video exam session; register through HamStudy) Organizer: West Essex Amateur Radio Club (WEARC) Online VE Team Source: Event information -
Run vs. S&P, SO2R, and rate: how do you decide when to leave a frequency?
I'd start with the category, because it determines how aggressive the strategy can be. Single-op unassisted, single-op assisted, QRP, low power, and high power all reward different habits. In an assisted category, spots can make S&P much more efficient. In unassisted, your own ears and a local skimmer, where permitted, do all the work. Read the rules for the specific contest, because definitions and allowed tools vary. For leaving a run frequency, a fixed rate threshold can mislead. A rate drop from a QSB fade is different from a drop caused by running out of stations. If the bandmap shows several unworked multipliers while your rate is flattening, going to S&P is usually the better trade. If the bandmap is quiet and you are still getting callers between CQs, staying is often right. One thing that helps is to decide before the contest roughly what a multiplier is worth in QSOs, so you aren't improvising under pressure.
-
Starting Morse code from zero: Koch vs. Farnsworth, which tools to use, and how to stop translating in your head?
Koch and Farnsworth are answers to different questions, so they can be combined. The Koch method is about how you introduce characters. You start with just two characters sent at a fairly fast character speed (commonly 18 to 20 WPM). When you can copy them at around 90 percent accuracy, you add one more, and so on. Because the speed is high from the first day, you learn to recognize each character as a single sound pattern, a rhythm, instead of counting elements. Farnsworth is about timing. Characters are sent at full speed, but the spacing between characters and words is stretched, so the overall speed is lower. This gives you thinking time without distorting the sound of each letter. Many Koch trainers let you set the effective speed lower than the character speed, which is the combination you're asking about. As you improve, you shrink the extra spacing until it is standard. On the tools: LCWO.net is a browser-based site with a Koch course, and it keeps your progress and results online. It also has other exercises like callsign practice and plain text. G4FON's trainer is software that you run locally. It is more of a configurable drill machine, with a Koch mode, adjustable speed and spacing, and its own character order. Note that character orders differ between trainers, so if you switch tools mid-course you may need to adjust which characters you consider learned. CW Academy (run by the CWops group) is different in kind. It is a structured, free online class with an instructor and small groups, usually with daily practice assignments between sessions, rather than a drill program. Accountability is the main benefit. If you tend to drift without a schedule, a class like that can be more valuable than any software. You can combine it with a trainer for daily drills. Check the current signup schedule and level requirements on the CWops site, since sessions run on set dates. On tone: pick a comfortable pitch, often somewhere around 600 to 700 Hz, and keep it consistent between your trainer and your radio's sidetone so you aren't retraining your ear.
-
Chasing award credits: how do you keep DXCC, WAS, WAZ, WPX, IOTA, POTA and SOTA straight without losing credits?
I'd add a caution about letting the software decide everything. Logging programs often fill entity and zone from a prefix lookup, and that fails for portable operations, special callsigns, and stations that operate from a different entity than their callsign suggests. If you're building toward WAZ or Honor Roll, spot-check anything unusual before you upload it, because a bad auto-fill can create a confirmed record that later doesn't match what you need for the award. On the LoTW side, I'd keep separate TQSL station locations for each place you operate from, including portable and holiday operations. Using the wrong one is one of the easiest ways to upload perfectly good contacts with the wrong entity or zone. It's also worth separating the awards that depend on your own station location (DXCC and WAZ, for instance) from the activity awards like POTA and SOTA, where the park or summit reference and the program's own log upload matter more than LoTW.
-
Planning a combined POTA and WWFF activation: KFF references, the 44-QSO line, and logging
For logging, the main trap is that a single log with both references stuffed into one field can break one upload or the other. I'd keep the master log in whatever logger you normally use, then export per program with the correct reference in the field the importer expects. Before leaving, do a test import of a couple of dummy QSOs if the system lets you, or at least compare a sample record against the format described on the WWFF site and the POTA site. The other thing I'd check is callsign handling. If you operate with a portable suffix or a reciprocal prefix, make sure the callsign in your log matches what hunters would have logged. Mismatches there cause more confusion than reference typos. And if the site only exists in one program, just activate it for that program. It is better to have a clean, valid log for one than a questionable double-credit for two.
-
How do you separate real ham radio news from hype? A practical checklist for rigs, firmware, band openings and rule changes
On band openings, I'd stop trusting any single indicator. Solar flux can be high and 10 meters can still be dead if the MUF isn't rising along your path, and a geomagnetic disturbance can flatten the upper bands even on a good day. A quick routine is to check the NOAA Space Weather Prediction Center numbers for context, then look at PSK Reporter or the Reverse Beacon Network for your own band and region. If your callsign or similar stations in your area are being spotted, the band is open for you. If nothing shows up, listening on FT8 or a beacon frequency for a few minutes will tell you more than any forecast. Sporadic E on 6 and 10 meters adds another wrinkle, because it can open fast and disappear just as fast, and it doesn't follow solar activity the way F2 propagation does. That's a good reason to keep a spotting page or alert open during the season. For club news and awards, I'd add that club newsletters and the official award sponsor pages are the best place to confirm rules and deadlines. Social posts often compress the details, and things like required QSL methods, mode endorsements, or logging requirements can be missed.
-
Q codes and ham radio shorthand: what QRM, QRN, QRP, QSL, QTH, 73, 88, K, KN and SK actually mean
Start with how Q codes work. They are three-letter codes beginning with Q, originally built for radiotelegraph use so common questions and answers could be sent quickly. Add a question mark and the code is a question. Send it without one and it is a statement or answer. For example, QRL? means "Is this frequency in use?" and QRL means "Yes, it's busy." The ones on your list: QRM is man-made interference, such as other stations, carriers or electrical noise from equipment. QRN is natural noise, mainly static from thunderstorms and atmospheric crashes. A handy way to remember them: M for man-made, N for natural. QRP means low power, or "reduce power." In practice, QRP operators usually run about 5 watts or less on CW (10 watts PEP is often used as the limit for SSB). QRO is the opposite: high power, or "increase power." QRT means "I'm stopping transmission," which in practice means shutting down for the day. QRZ? means "Who is calling me?" You hear it when someone caught a fragment of a call but not the whole thing. It's also the name of a well-known callsign lookup website, so context matters. QSL means "I acknowledge receipt" or "Understood." It also names the confirmation card, or electronic confirmation, exchanged after a contact. QSO is simply a two-way contact, i.e. a conversation. QSY means change frequency. "Let's QSY to 7.150" means "Let's move there." QTH is your location, as in "My QTH is Denver." QSB is signal fading, where the strength rises and falls. This is very common on HF. Related ones you'll hear: QRX (stand by or wait), QRV (I'm ready), QRG (your exact frequency), QRS (send slower) and QRQ (send faster). On voice, the Q codes that turn up most are QTH, QSL, QSO, QRZ, QRM, QRN, QSY and QRP. Many operators prefer plain language for the rest, such as "Is the frequency in use?" rather than "QRL?" Either is understood, but plain language is clearer, especially on repeaters and with newcomers.
-
Part 97 compliance checklist: ID timing, third-party traffic, power limits, RF exposure, and license renewal
Taking the operating-side items first. Identification is in 97.119. You give your call sign at the end of each communication and at least every 10 minutes during one. On phone you use English or CW, and phonetics are fine if they're standard. Digital ID has to be in the emission type you're using. A tactical call such as 'Net Control' or 'Shelter 2' is fine for operational clarity, but it doesn't replace the FCC call sign. Same goes for a club nickname. If you operate someone else's station, the station's call sign is what goes out. You can add your own too, but the station call is what has to be there. Third-party traffic is 97.115. A third party is someone other than the two control operators at either end. They can take part in a QSO only if a properly licensed control operator is at the control point, monitoring and supervising, and ready to end the contact. The big limit is international: third-party communications with another country are only allowed if that country has a third-party agreement with the US. The exception is when the third party is themselves eligible to be a control operator of that station. Check the current list of agreement countries before putting a guest on the mic for a DX contact. Separately, 97.115 bars third-party participation by someone whose license has been revoked or suspended, with some conditions. Emergency communications for safety of life or property are handled under 97.403. Power limits are in 97.313. The ceiling is 1,500 W PEP output, but you also have to use the minimum power needed for the communication. Notable exceptions are 200 W PEP on 30 meters and 200 W PEP for Technicians on their HF segments. 60 meters is not a PEP-output limit at all. It's expressed as effective radiated power relative to a half-wave dipole, so antenna gain matters there. Technicians have only limited HF access: CW on parts of 80, 40, and 15 meters, plus CW/data/phone in the 10-meter segments. General and Amateur Extra have progressively broader privileges under 97.301 through 97.305. Novice and Advanced licenses are no longer issued, but existing holders can renew them. On prohibited transmissions, 97.113 is the section to reread. In plain terms: no communications for pay, no business communications (with narrow exceptions), no broadcasting, no music, no obscene or indecent language, no deliberately false or deceptive signals, and no messages encoded to hide their meaning. That last point is why encrypting content on amateur frequencies is a problem. Digital modes are fine as long as the protocol is publicly documented (97.309), so anyone can decode it. Selling personal station gear is allowed if it isn't done on a regular basis, but running a store over the repeater is not.
-
Keeping RF out of shack automation: ESP32/Pico nodes, CAT, antenna switches and SWR sensing
That split makes sense to me, with one addition: give the microcontroller a watchdog and a safe default state. If the Pi crashes or the network drops, the node should drop PTT, return the antenna switch to a known position, and stop the rotator. A hardware PTT timeout is cheap insurance, whether it's the watchdog timer on the Pico or ESP32 or the transmit time-out timer in the radio. On rotators, if the controller uses a potentiometer for position feedback, ADC noise can make the reading jump around. Averaging and a small deadband help a lot. It's also worth speaking a common protocol like the Yaesu GS-232 command set, because then rotctld (Hamlib uses port 4533 by default) and most logging or satellite tracking software can drive it without custom code.
-
Building a reliable Winlink setup: client, modes, gateway selection and message handling
For gateway selection I would start from the band and the distance, then the mode. On VHF/UHF, the packet or VARA FM gateway list shows what is in range and on which frequency. Check the listed frequency, offset, tone and mode, and make sure your radio is set up exactly for that channel. VARA FM has narrow and wide variants. Wide is faster but needs a radio and audio path that can handle it cleanly, so the narrow setting is often the safer starting point. On HF, the gateway list and propagation predictions help, but they are only predictions. Update the channel list while you still have internet, because the cached copy is what you will use when the connection is gone. Pick several candidate gateways on different bands, not just the closest one. Listen first and let the busy detector do its job, because stepping on an existing session wastes everyone's time. VARA HF is usually the fast option when the path is good. ARDOP is free and can work with narrower bandwidths, and Pactor performs well but needs the SCS modem. Also keep the licensing in mind. VARA is shareware, and the unregistered version is deliberately slow, so factor that in if you plan to move anything larger than a short text message.
-
Combining POTA and WWFF activations: how do you handle KFF references, the 44-QSO rule and logging?
For on-air technique, the biggest help to hunters is a clear, repeated exchange of the reference. Something like "CQ WWFF, CQ WWFF, this is [call], K F F dash and the number" lets a hunter who only wants the WWFF credit know they're in the right place. If you're also doing POTA, mention both, for example "POTA and WWFF", and give both references in a form that's easy to copy. Phonetics for the number are worth the extra seconds. On CW, send the reference at a speed you can keep up with if someone asks for a repeat. Spotting matters as much as it does for POTA. Self-spot with the correct reference and frequency, and update the spot if you move. Not every hunter watches the same spotting source, so don't assume a POTA spot will automatically reach WWFF hunters. Check which spotting tools and clusters the WWFF community uses now. A few practical things for reserves and nature parks in general: Confirm the boundary before setting up. Parking lots, visitor centers and trailheads are not always inside the protected area.Check whether you need permission or a permit, and whether antennas, masts or power sources are restricted. Rules vary by park and by country.Keep the footprint small. A lightweight portable antenna and no trampling of vegetation is respectful of the reason the area is a WWFF reference.As a hunter, don't rely on the activator to remember to log you. Keep your own log and upload it, because hunter awards and diplomas are based on confirmed QSOs.Finally, for the awards and diplomas, read the current requirements on the WWFF site before you start chasing. The categories, the counts and the way applications are made have evolved, and I wouldn't want anyone to rely on a forum summary of what they need.
-
Building solid CW copy and sending: keyers, paddles, filters, Farnsworth and where decoders fit
On filters, I would try a few widths rather than set one and forget it. A narrow filter can be very helpful when someone is close to your frequency, but it can make a signal sound unnatural and it can hide a station that is calling you off to the side. Wider settings give you more situational awareness, especially if you are tuning around or running a pile-up. In a crowded contest band you will likely go narrower. At a relaxed pace, a moderate width can be less tiring. About decoders and skimmers, they are helpful for confirming a callsign or exchange, but a decoder that is wrong looks just as confident as one that is right. If the decoded text and what you hear disagree, trust your ear and ask for a repeat. Also, if you are practicing for contest speed, try copying on paper first and then checking the decoder afterward, so you see what you are missing rather than letting the screen do the work.
-
Callsign basics: sequential vs. vanity, formats, groups, club and special event calls (US)
Two points about club and special event calls. For a club, the trustee is the person the FCC holds responsible, so the club should have a plan for replacing a trustee who moves or becomes inactive. If the club call gets stuck on a lapsed individual license, fixing it is more work than doing the paperwork up front. The club also needs to keep its ULS contact information current, because renewal notices go there. On special events, people often mix up the 1x1 calls with ordinary vanity calls. The 1x1 calls are handed out for a short operating window by a coordinator, not requested through a normal ULS vanity filing, and you need to contact the coordinator ahead of time. They also need QSL and logging planning: if the event is a one-off, decide who handles confirmations and log uploads, because the call will be reissued to someone else later. For ordinary operating, remember that a /portable or /mobile suffix is optional under current US rules for operating away from home, though you may see it used anyway. Do not confuse that with a DX prefix like KH6 or KL7, which indicates the station is licensed in that region.
-
Breaking the pileup on a rare one: split, timing, and how to prepare for Clipperton or Bouvet-class targets
One thing I'd add is that the real skill is working out the DX operator's habits, not just your own. Some operators will pick out a partial callsign from the middle of a pile and work the strongest fragment, so a short, clean call sometimes beats repeating the whole thing at a slower pace. Others will go through the pile systematically, often by the order of a call area, and they punish anything that interrupts that pattern. If he is clearly taking calls in a regular order, don't try to be clever. Wait for your turn. On phonetics, I'd stick to standard ITU phonetics, especially on SSB. Creative phonetics may help a station stand out in a quiet pile, but they can also slow the DX's copy if he's using a language that isn't his first. If you do get a partial back, repeat just the part that matters. Once you've been logged, stop calling. That sounds obvious, but a lot of QRM comes from stations still calling after the DX has already moved on. On Club Log, I think people underuse the log search. If you're in the log on a band and mode, calling again is just adding to the pile. If you're not in the log after a decent period, it may be worth reading the expedition's own notes before assuming your signal failed. Sometimes the problem is a busted call in the log, and the information on how to fix that is on the expedition's page.