Everything posted by Mod_Chrissy
-
Choosing a first (or next) handheld: FT-65R vs. Baofeng vs. ID-52A vs. TH-D75, and where the IC-705 fits
I'd add something about setup, because a radio that's programmed badly is a bad radio no matter the price. Save a clean image of the radio before you change anything, and in CHIRP, name memories consistently so you can find them under stress, for example by callsign or location rather than random labels. Put the repeaters you rely on first, then simplex, then anything else. For every repeater entry, double-check the duplex direction, offset and tone mode: Tone means encode only, while TSQL means encode and decode, and using the wrong one is a common cause of failure. For emergency kits, I'd test the full setup before you need it. Power the radio from the battery you plan to carry, try the antenna you plan to use, and make a simplex contact with another station. That quickly shows problems with a bad connector, a weak battery or a missing tone. Also keep the manual, or at least a summary of key operations, with the radio. Menu-heavy digital handhelds are much harder to operate from memory than an FM set with a simple keypad.
-
SSB audio that carries: mic gain, ALC, compression and filter settings for weak-signal and DX work
For the weak-station and DX side, receive settings matter as much as transmit audio. A 2.4 kHz filter is a good general-purpose starting point, but it isn't always the best choice. For a weak signal with QRM close by, narrowing to somewhere in the 1.8 to 2.1 kHz range can make a difference. The voice loses some fullness, but the signal can become more copyable. If your radio has IF shift or passband tuning, use it to slide the window away from an interfering signal rather than just narrowing it. Noise reduction can help, but it needs a light touch. Aggressive NR can turn weak speech into a warbly mess and remove the cues you need to copy a callsign. The same goes for AGC: a faster setting may help when strong signals are bumping around, while a slower setting can sound smoother on steady signals. Turning down RF gain on a noisy band can also improve the readability of a weak signal by reducing the noise the AGC reacts to, though how well it works depends on your radio and conditions. When working a DX station, much of the skill is procedural. Listen long enough to understand whether they're working split. If they are, set your transmit frequency accordingly, and never transmit on the DX's listening frequency. Keep calls short, say your callsign clearly using standard phonetics, and avoid stretching it out or repeating it endlessly. If the DX operator is working by callsign area or number ranges, wait for your turn. For your own audio in a pileup, an overdriven signal tends to do worse than a clean one. A moderate amount of processing and well-set ALC will usually be more readable than running the maximum compression and drive. Your power is also better spent on a clean signal than on distortion products on the neighboring frequencies.
-
Breaking the pileup on a rare one: split, timing, tailending and what changes for Clipperton/Bouvet-type targets
Good list. I'd add one thing to point 3: the most useful skill is listening to the operator, not just the pile. If he's picking stations from a narrow part of the range and ignoring the rest, there's usually a reason. He might be zero-beating on the loudest callers, or his receiver might be overloaded by a strong station nearby. Calling in the same place as everyone else isn't a strategy. On SSB, I'd stress keeping the whole call short and the delivery steady. If you're just one more voice in a wall of audio, the callsign that gets picked is the one that's easy to copy on the first attempt. That usually means a normal speaking pace, a clear voice, and no embellishments. Phonetics are worth sending only when the operator has asked for a partial or a repeat, and then you should use the standard alphabet. On FT8, don't assume it's easier. In Fox/Hound mode, the common failures are transmitting on the wrong frequency (below 1000 Hz, or on the Fox's own frequency), leaving the program on the wrong mode setting, or not noticing that your clock has drifted. Check all of these before the opening, not during it. And don't keep calling when the Fox has already sent you a report. Let the sequence finish.
-
SDR gain, dynamic range and noise: where do dongles, upconverters and software settings actually matter?
Lowering gain first is a good habit because it costs nothing and tells you quickly what kind of problem it is. A practical test is to change the gain or attenuation by 10 dB. If the false signals change level or appear and disappear, you are looking at intermodulation or overload and not real signals. Real signals should move up and down with the gain, along with the noise floor. For a dongle with a lot of FM broadcast energy around, a notch at 88–108 MHz is cheap and works well. If the problem is spread over a wider range, a bandpass or low-pass filter for the segment you actually want helps more. A better ADC cannot fix an overloaded front end in front of it. It only gives you more room before that point. One caution on the "more bits is always better" argument. Gain staging still matters on 12- and 14-bit receivers, and AGC can pump on strong bursts. For weak-signal digital modes it is often better to fix the gain manually than to leave the AGC hunting.
-
When is a multiplier worth leaving your run frequency? Run vs S&P, SO2R and band-change decisions
The Q/M estimate is a good start, but add one correction: it assumes every QSO has equal value. In contests where QSO points differ by distance or continent, a DX QSO that is also a multiplier is worth much more than a nearby QSO on the same band. A simple check is to compare the multiplier's value in QSO-equivalents against the expected time to work it. If the station is already spotted and calling, the time is short and the answer is easy. If you have to hunt through a crowded band for something that may not be there, the same multiplier costs more. On SO2R, the usual practical limit is receive-side interference, not the logger. Two radios on bands close in frequency can desensitize each other, even with different antennas. Bandpass filters on each radio, enough physical separation between antennas, and keeping the radios on bands that do not share harmonics all help. Operationally, many people practice with the second radio only for needed multipliers, meaning stations that are already confirmed and spotted, rather than trying to run two CQ frequencies at once. That is a much easier step than full two-radio running and still gives most of the benefit. One more thing about spots: a spotted multiplier that disappears is often a busted call or a station that has moved. Use the bandmap to click, listen briefly, and only commit if you hear the call correctly. A quick check of the contest exchange against the multiplier list also prevents logging errors.
-
Planning an HF shack around a 100 W rig: power, grounding vs. bonding, filtering, and where the RFI actually comes from
It's worth separating noise that is received from noise that is transmitted. Receive noise on 80 and 40 m is often a switching supply, LED lighting, or a nearby charger. A simple check is to run the radio from a battery, or to switch off breakers one at a time with a portable receiver, and watch the S-meter or the waterfall. That narrows it down quickly. On transmit, RF in the shack is almost always common-mode on the coax or on an end-fed or off-center antenna with no real counterpoise. Symptoms like a hot mic, a keyboard locking up, or USB audio dropouts point to this. Chokes with enough turns for the band, and sized to give high impedance on the lower frequencies, are better than one generic snap-on near the radio. Adding more ground rods rarely fixes this. One more point on grounding: bonding the station to the service ground is a safety step and shouldn't be skipped for an outside ground rod alone. Tying the two grounds together reduces the risk of voltage differences across equipment during a surge.
-
Prepping for the Amateur Extra exam (Element 4): how do you tackle the advanced theory without just memorizing 50 answers?
Memorize the formulas and relationships that show up repeatedly, and learn the reasoning behind everything else. The pool rewards understanding because the same concept gets asked several ways with different numbers or wording. Op amps are a good place to start because they're mostly two formulas. Inverting gain is minus Rf divided by Rin. Non-inverting gain is 1 plus Rf over Rin. Once you know the virtual-ground idea at the inverting input, the input impedance questions follow from it. For transistors, focus on what bias class means (A, AB, B, C), where each is used, and the tradeoff between linearity and efficiency. Know the difference between a BJT's current gain and a FET's transconductance, since the two are described very differently. For filters, the vocabulary matters: Butterworth is maximally flat in the passband, Chebyshev trades passband ripple for a steeper rolloff, and shape factor compares the bandwidth at two attenuation points. Q is reactance over resistance for a series circuit, and bandwidth is center frequency divided by Q. For modulation, learn these two: modulation index in FM is deviation divided by the modulating frequency, and Carson's rule estimates bandwidth as twice the sum of deviation and highest modulating frequency. Then separate PM from FM conceptually, since they're closely related and the questions like to test the difference. Receiver design is where understanding pays off most: dynamic range, third-order intercept, blocking, reciprocal mixing, and noise figure all describe how a receiver behaves near strong signals. If you understand why strong off-channel signals cause intermodulation, the answers become logical rather than arbitrary.
-
Planning a dual-band mobile install (FTM-500D, ID-5100A or TM-D710G): wiring, noise, cross-band and mobile manners
On picking among the three, I'd start from what you'll use on the road rather than the headline features. If APRS beaconing and a built-in TNC matter to you, the TM-D710G is built for that. If your local network is mainly C4FM or D-STAR, the FTM-500D or ID-5100A makes more sense, but confirm that the repeaters you plan to use actually support that mode. It's also worth looking at the control head. A touchscreen can be easy to use parked and harder to use while driving, and physical knobs and buttons are a plus for operation without taking your eyes off the road. On cross-band, I'd read the manual for the exact model before buying it for that purpose. If a feature matters to you, don't assume it's present across all dual-band mobiles. And if you do set up a cross-band link, test it at low power first, confirm the ID timing, and make sure the receiving and transmitting frequencies can't cause interference to someone else. A mobile radio sitting in a hot car running as a repeater for a long time is a good reason to keep an eye on heat. Finally, a point on mobile manners: say you're mobile when you check in, keep it brief, and drop out of a conversation if the traffic gets heavy. Nobody minds a driver who steps back to pay attention to the road.
-
Getting your first ham license: how do I study, find a VE test session, and what is the FRN and ULS stuff?
Here is the paperwork side, since that's what trips people up. FRN: The FCC Registration Number identifies you in the FCC's systems. You get one by registering in the FCC's CORES system. It's free, and nobody should charge you for it. Do it a few days before the exam, not in the parking lot. The VEs will need it to file your application, and registering can involve identity details you don't want to sort out on a phone at the session. Write down your FRN and keep your CORES login somewhere safe, because you'll need it later for address changes, renewals, and vanity call sign requests. ULS: The Universal Licensing System is the FCC database where amateur licenses are recorded. After you pass, the VE team submits your paperwork through a coordinator, and then the FCC grants the license. You can search your name or FRN in the ULS license search to see when it appears. Don't transmit until your call sign actually shows up there. A passing score on the day isn't a license yet. Fees: The FCC has not charged an application fee for new amateur licenses since it waived it, but check the FCC's current position. The VE team may charge a small exam-session fee to cover costs. The amount varies by team and is capped by the coordinating organizations, so look at the session listing or ask the contact before you go. Also ask what payment they take. Some sessions are cash or check only. Finding a session: Try the ARRL exam session search, HamStudy's session finder, and the websites of local clubs. There are also online sessions run by remote VE teams, which are handy if nothing is nearby. Contact the listed person first, because some sessions need pre-registration or have limited seats. What to bring: Photo ID, your FRN, a pen or pencil, and the fee. A basic calculator is usually fine, but ask the team about their calculator rules. If you already hold a license or a certificate for an element you passed, bring that too.
-
From FM birds to linear transponders: sorting out Doppler, antennas and tracking for a first LEO setup
On linear birds, the part that trips people up is inversion. In an inverting transponder, tuning your uplink higher moves the downlink lower, and sideband flips too, so an upper-sideband uplink appears as lower sideband on the downlink. A rig with split operation and software Doppler control helps, but you still need to understand what the software is doing. Otherwise you can end up chasing your own signal around the passband. A practical approach is to find the beacon or a strong CW signal, set the downlink to a reference point, then transmit a short carrier or a few words and adjust until you hear yourself on frequency. Keep your power moderate. Linear transponders are shared, and an overdriven uplink can suppress other stations. Listen to the passband before transmitting, and keep calls short. For software, I would pick Gpredict if you want a free, cross-platform tracker with Hamlib support, and SatPC32 if you are already in the Windows ecosystem and want its rig and rotator integrations. Whichever you choose, test the rotator on its own before relying on a live pass. Check azimuth wrap, elevation limits and any overlap or stop at north, since a rotator that swings the long way at the wrong moment can cost you half a pass.
-
Getting into radio nets and special event stations: check-in etiquette, net types, and chasing certificates
For net control, the main skills are consistency and clarity. Open with a script that states the net's name, its purpose, whether it's directed, and how check-ins work. Keep a log as you go, writing down callsign, name, location, and any traffic or announcements. Try to acknowledge every station, even if only with a quick callsign repeat, so nobody is left guessing. When two stations call at once, pick out a partial callsign and ask the others to stand by. Use a consistent phonetic alphabet. Close with a summary of check-ins and a reminder of the next session. Having a relief net control helps when conditions turn poor. For special event stations, a simple spreadsheet works fine: date, UTC time, callsign worked, band, mode, the event's callsign, and a column for whether you've requested a certificate or QSL. Many events upload logs to a service like Logbook of The World, Club Log, or QRZ, or run their own log search, but support varies, so read the event page. Remember that these stations can have long pileups. Wait for a break, give your callsign once or twice, and don't call over the station you want to work. If you want a certificate, follow the request instructions exactly, since some organizers only accept requests through a specific form or address.
-
Building a Winlink station for ARES use: Winlink Express, RMS gateways, VARA/ARDOP/Pactor/Packet, P2P and radio-only
On P2P and radio-only, I'd keep them clearly separate in your training, because people mix them up. P2P is a direct connection between two stations, using a P2P session type for the mode you're running (packet, VARA, ARDOP, or Pactor). No RMS gateway or internet is involved. One station calls, the other listens in the matching P2P mode, and they exchange the messages queued in their outboxes. It works well for a shelter, a command post, or any place where a gateway is out of reach. Practice it on a simulated loss of gateways, and agree in advance on frequency, mode, bandwidth, and who calls whom. Remember that P2P delivers to the other station's Winlink Express. It does not reach arbitrary internet addresses unless that station later has a gateway or internet path, so don't promise anyone off-site delivery. Radio-only is a different idea. It is a way of keeping messages off the internet path, so they move only among Winlink radio users. That can matter when the internet is down or when you simply want to avoid internet exposure. Check the current Winlink documentation for how your version of Winlink Express flags and handles radio-only messages, because the menu location and behavior can change between releases. Run a test message through the exact path you intend to use, and confirm that the recipient actually receives it. For forms, use the Template Manager in Winlink Express to update the templates while you still have internet, then make sure everyone is on the same set. ICS-213 and similar forms open in a local web page, and the data travels with the message so the receiving Winlink Express can display it as the form. A recipient without the templates may only see raw text or an attachment. Keep forms short and attachments to a minimum, because an HF session is slow and the message size directly sets the session length. Remember too that Winlink traffic on amateur frequencies falls under the usual amateur rules: no encrypted content, and identify properly. The account password authenticates you to the system and doesn't hide the message content. For Winlink Wednesday, treat it as a regular practice event and follow the current instructions published by the Winlink community, since the details of what to send and where to send it are what you most need to get right. Use it to test your setup. Send a short check-in with a form, try each gateway on your list, and keep a simple log of the date, time, band, mode, gateway, and result. After a few weeks that log will show you which paths work and which settings cause trouble. That is more useful than any general advice about which mode is best.
-
Starting EME: what 2 m, 70 cm, 23 cm and 10 GHz moonbounce really demand (JT65/Q65, Faraday, libration, skeds)
One caveat on the small-station question. The answer depends mainly on who is on the other end. A modest array can complete contacts with the large stations because they have the gain and the receive sensitivity to dig a weak signal out of the noise, but two modest stations may never hear each other. In practice, the sked list matters as much as your own gear. Look at which stations are active on your band and what they can copy, and match your target to that. Echo tests on your own signal tell you something about your own station. Note that hearing your own echoes does not prove you can complete with a small partner. Q65 deserves more attention. If you are choosing between modes for a new station, it makes sense to check what your partners are running before you commit, since both JT65 and Q65 are common. A mismatch with your partner costs more than a few dB of decoder advantage. Also be careful with the tone spacing: if you run the wrong submode for the band or for the libration spread, you throw away margin on the higher bands. On the 10 GHz side, it is worth practicing tracking on the Sun first. The Sun is easy to find and gives you a strong, repeatable noise signal to peak on. The Moon is a much fainter target, and dish pointing errors that are fine on 23 cm will cost you badly at 10 GHz.
-
Breaking pileups on rare DX: split, timing and listening habits for Clipperton and Bouvet-class targets
I'd separate two things that get lumped together: tailending as a timing strategy and calling over an exchange that's still in progress. Calling in the gap right after the DX operator has finished the previous QSO and before he sends QRZ is just good timing. Calling while the previous station is still sending the report is what actually costs everyone, because the operator has to ask for repeats. If you want a simple rule, listen to the DX's cadence for a few minutes. If he leaves a consistent gap, call into it. If he doesn't, nothing you do will fit, so wait for a pause. On the low bands the receive side is usually the limiting factor, much more than the transmit side. For 160 m and 80 m, a receive antenna such as a Beverage, a flag, or a small loop array often matters more than extra power. Most rare-DX openings on 160 are short and tied to gray-line timing, with sunrise or sunset at one end or both. Quiet geomagnetic conditions also help a lot. Use the traditional DX window near the bottom of the band, but check your band plan, because it differs by region. A narrow CW filter helps, but in a big pile it can also hide the thing you need to hear, which is where the DX is actually transmitting. Keep a wider setting for the first listen, then narrow down. On the cluster: set your own filter so that spots from your area or on your needed bands are the ones you see. Otherwise you'll see a stream of spots that don't match your path and can't be worked from your location.
-
ARCNEM Free General Class License Course (online)
The Amateur Radio Club of the National Electronics Museum's General Class License Course begins Tuesday, November 10, 2026 and runs through January 5, 2027, in 9 sessions. Sessions are weekly 3-hour classes on Tuesday evenings at 6:30 PM Eastern Time, held online via Zoom. Zoom links go to registered participants, and all sessions are recorded and posted on YouTube. The course is free.Location: Online via Zoom (links sent to registered participants) Organizer: Amateur Radio Club of the National Electronics Museum (ARCNEM, K3NEM) Source: Event information
-
Hamfest game plan: what to bring, how to size up used gear, and how to get more out of your local club
On the club side, a good meeting usually has more going on than the business agenda. If you're visiting a club, ask whether they have an Elmer or mentoring program, a net you can check into, or a regular VE session. Those are lower-pressure ways to meet people than showing up cold to a general meeting. If you're newly licensed, bring a specific question or problem. Things like "my 2 m vertical has a high SWR," "how do I get started with POTA or FT8," or "what should I look for in a first HF rig" get better answers than "what should I buy?" Operators love to talk about real setups. For selling, a tip is to clean the gear, include the manual or cables if you have them, and label what's included. A tidy table with honest descriptions usually moves faster than a pile of mystery boxes, and buyers trust it more. If something is sold as-is, say so plainly. It saves arguments later.
-
One master log across N1MM Logger+, WSJT-X and Log4OM: where ADIF, Cabrillo and uploads usually go wrong
On the double-logging problem, the cause is usually that two programs each log the same QSO. WSJT-X writes its own wsjtx_log.adi when you confirm a contact. If it also broadcasts the logged QSO over UDP to N1MM+ or Log4OM, you get one copy in the ADIF file and another in the logger's database. That's fine as long as you only import one of them into the master log. A simple rule is to treat the WSJT-X ADIF as an archive and the logger's database as the working copy. If more than one program needs to listen to WSJT-X's UDP stream, check the address and port settings under Settings > Reporting. Several listeners on the same port can conflict unless you use a multicast address or a relay tool that forwards to each program separately. Before importing into the long-term log, check the time base. Contest loggers and WSJT-X both record UTC, but if the PC clock has drifted, QSOs will be a few seconds off the other station's log. That can matter for LoTW matching and for sponsor log checking. Keeping the PC synced to an NTP source is cheap insurance.
-
Gain, overload and ghost signals: getting real dynamic range from RTL-SDR, SDRplay, Airspy and HackRF
Filtering gets overlooked in these threads. Broadcast FM is the usual culprit on VHF and UHF, and a notch costs very little compared with how much it helps. Several SDRplay models include switchable notches for broadcast bands, and standalone FM notch filters exist for dongles. On HF, a set of switchable bandpass filters or a tuned antenna such as a small magnetic loop makes a bigger difference than most software tweaks, because it keeps the strong out-of-band signals from ever reaching the ADC. On the HF-with-upconverter question: it works well if you account for the offset and check that the converter's LO and spurs are clean. Calibrate with a known signal, such as a time station or a broadcaster on a precisely known frequency, and apply a ppm correction if the software offers it. SDR#, SDRuno and HDSDR can all handle an LO offset, though the setting is in different places in each. If you also use the SDR as a panadapter or bandscope next to a transceiver, tapping the IF of the radio is cleaner than a shared antenna splitter. A splitter costs signal level, and you risk damaging the SDR if you ever transmit. Only connect an SDR to a transmitting antenna path through proper protection, and check the radio's documentation for a receive-only output. One more tip for finding noise sources: use the waterfall as a tool. Switch off breakers, unplug chargers and LED drivers one at a time and watch the floor. Birdies at regular intervals across the band often point to a specific switching supply, and moving the antenna just a few meters away can be enough to fix it.
-
Q codes and ham radio shorthand: what QRM, QRN, QRP, QSL, QTH, 73, 88, K, KN and SK actually mean
Here is the rest of the list, plus the logging and net terms. CQ is a general call meaning "any station, please respond." On CW a typical call is CQ CQ CQ DE W1AW W1AW K. DE is French for "from" and sits between the station you are calling and your own callsign. On phone most people say "this is" instead of DE. K means "go ahead, anyone may reply." KN means "go ahead, but only the station I'm in contact with," which asks others not to break in. SK is a prosign that ends a contact. Don't confuse it with "silent key," the same letters used for an amateur who has died. Which meaning applies depends on context. AR marks the end of a transmission or message, and BK means "break," as in back-and-forth chatter. Prosigns are normally sent with no gaps between the letters. 73 means best regards, and it is already plural, so "73s" is generally considered unneeded. 88 means "love and kisses." It is traditionally used between friends and spouses and sometimes jokingly, so it usually isn't how you sign off with a stranger. RST is the signal report: Readability (1 to 5), Strength (1 to 9) and Tone (1 to 9). The tone digit is used on CW only. So 599 is perfect on all three. On phone you give just RS, for example "five nine." In contests, 599 is often given out routinely, but in a normal QSO an honest report is more useful. Other common CW abbreviations: TNX (thanks), TU (thank you), FB (fine business, meaning excellent), ES (and), UR (your), PSE (please), AGN (again), WX (weather), ANT (antenna), OM (old man, a friendly term for a male operator), YL (young lady, meaning any female operator) and HI (laughter). Log terms: a basic log entry records date and time (usually in UTC), frequency or band, mode, the other station's callsign, and the RST sent and received. Many people add name, QTH, grid square and notes. Net terms: net control (NCS) runs the net and directs who speaks, a check-in is a station announcing itself to the net, traffic is a message to be relayed, and liaison means passing information between nets. In emergency nets, follow the net control's instructions and stay brief. On voice, spell callsigns with the standard phonetic alphabet when the signal is weak.
-
Getting digital modes right: time sync, audio levels, CAT and what the decode thresholds actually mean
Choosing between the keyboard modes mostly comes down to what you need from the contact. PSK31 occupies roughly 31 Hz and is easy on a waterfall, but it does not cope well with fast fading and it has no strong error correction. RTTY at 45.45 baud with 170 Hz shift is wider and less efficient, but it is still the standard for many contests and is tolerant of poor tuning once you understand it. Olivia and the MFSK family in FLDIGI add forward error correction, so you can sometimes copy text when a PSK signal would be garbage, at the cost of slow typing speed. Hellschreiber is a different idea, because the text is drawn on screen like a tiny fax, so it can be read even with some corruption. For Winlink, remember that the mode is only the transport. The Winlink Express client can use several, including VARA HF, VARA FM, ARDOP, Pactor and packet, and which ones work depends on the gateway and your hardware. VARA is proprietary software with a free version that is speed-limited and a registered version that is faster, so check the current licensing before building a plan around it. Also keep in mind that unattended or automatic operation has its own rules in each country, so check your local regulations and the band plan before running anything that could transmit on its own.
-
Standard NATO/ITU phonetics or "ham phonetics" on the air? How do you handle callsigns, names, numbers and nets?
Short version: most amateur regulations don't force one specific spelling alphabet on you, but the ITU/ICAO one (the one commonly called NATO phonetics) is the sensible default. Check the wording of your own licensing rules. US Part 97, for example, speaks of an internationally recognized standard phonetic alphabet being usable for callsigns on phone. It is not a rule that every letter must be spelled out. The standard alphabet is 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. It was built around words that stay distinguishable across many accents and languages, which matters on HF where you might be talking to someone for whom English is a second language. That is the main argument for it over improvised words. Improvised words tend to be fine locally and fall apart with DX. Traditional ham or police-style sets (Adam, Boy, David, Edward, Henry, Ida, Nora, Ocean, Sugar, Union, William and so on) work well enough between people who share the habit. The trouble is that two operators may carry different lists in their heads, and some choices are weak in noise: "Boy" and "Delta" aren't the issue, but a word like "Nancy" against "Mary" can blur on a marginal signal. If you mix systems, you force the other station to guess which list you're using. For the guide I'd write: use the standard alphabet by default, don't invent cute words for callsigns, and if you do get a creative one in a pileup, expect to be misunderstood by someone.
-
Part 97 compliance Q&A: ID timing, third-party traffic, power, RF safety, remote control, and renewal
I'll cover the remaining questions, and I'll flag where it's worth checking the rule text yourself. RF exposure (§97.13(c)). You're responsible for making sure your station doesn't exceed the FCC's exposure limits. There's a table of power levels by band below which a routine evaluation isn't required, and the thresholds are different on each band. That means a 100 W station might be exempt on one band and need evaluation on another. Above the thresholds, you evaluate with the FCC's guidance, OET Bulletin 65 and its amateur supplement, and calculators built around it. The limits are time-averaged, with different averaging times for controlled and uncontrolled environments. The practical factors are antenna type and height, mode duty cycle, feedline loss, and how close people, including neighbors, can get to the radiating elements. A mobile whip, an attic antenna, and a tower yagi are very different situations. Spurious emissions (§97.307). Emissions outside your necessary bandwidth have to be kept to the minimum practical level, and the rules set minimum suppression levels. Below 30 MHz it is 43 dB below the mean power of the fundamental. Above 30 MHz the numbers depend on power: at higher powers the requirement goes up to 60 dB. The real-world causes are usually overdriven amplifiers, bad filtering, and poorly adjusted audio or ALC settings that cause splatter. A clean transmitter is only part of it, because an amplifier can ruin it. Control and auxiliary operation (§97.109, §97.201, §97.205). There are three kinds of station control: Local control means the control operator is at the station's controls.Remote control means the control operator is at a control point away from the transmitter, using a control link. They must be able to shut the transmitter off.Automatic control means no control operator is present, and it is allowed only for specific station types, such as repeaters, auxiliary stations, beacons, and certain digital systems.Auxiliary stations, meaning links between a repeater and its control point or between stations, are restricted to 2 meters and shorter wavelengths, minus a list of excluded segments. The licensee still has to ensure a control operator is responsible for the station, including that it can be shut down if it malfunctions. The repeater coordinator side of things isn't in Part 97, so a coordinated pair doesn't change who is responsible. Enforcement. The FCC Enforcement Bureau handles amateur enforcement. A violation can lead to a notice of violation, and more serious cases can lead to a notice of apparent liability, a forfeiture, or license revocation or suspension. Volunteer monitors and Official Observers only notify operators informally and have no enforcement power. It is more common for a problem to go through an advisory letter than a fine, but that's a policy tendency rather than a guarantee. Also, §97.403 lets stations use any means of radiocommunication at their disposal in a life-or-property emergency, but that's for real emergencies, not convenience. Term and renewal. An amateur license is valid for 10 years. You can apply to renew starting 90 days before expiration through the FCC's ULS or through the FCC's online system. If it lapses, there's a 2-year grace period in which you can still renew without retaking the exam. You may not transmit during that time until the renewal is granted. After the grace period you'd have to test again. Keep your mailing address and email current in your license record (§97.23), because that is how the FCC contacts you. The FCC has also been moving toward electronic official license copies, so the ULS record is the one that counts. For any application fee, check the FCC's current fee schedule rather than relying on older posts.
-
Confirming contacts: LoTW, eQSL, QRZ, Club Log OQRS, bureau and direct cards. What's worth your time?
On the paper side, the decision is usually about how badly you need that specific confirmation and how long you can wait. The bureau is cheap, but it's slow, and the timeline is unpredictable. Cards move in batches between national bureaus and sort at each end, so many months to a few years isn't unusual. That's fine for routine contacts and for people who just like collecting cards. It's not great if you need one rare entity to finish a milestone. For those, direct usually makes more sense. For a direct QSL, first work out the correct route. Look the station up on QRZ, Club Log or the DXpedition's own page. Many operators use a QSL manager, so a card sent to the operator's own address may go nowhere. Then check whether the station uses OQRS. Club Log's OQRS lets you request a card online, and the operator or manager decides which delivery options to offer (bureau, direct, and what they charge). If the station only takes mailed requests, send your card with a self-addressed envelope and return postage. Return postage is traditionally cash, the 'green stamp', meaning US dollars, since foreign stamps are hard to use from the other side. International Reply Coupons used to be the alternative, but they're now largely obsolete and hard to redeem, so I wouldn't count on them. Check the station's page for the amount they want, because it varies with local postage costs. Put the cash inside the envelope with the card so it isn't visible from outside, and in countries known for mail theft some people leave the callsign and any amateur radio markings off the outer envelope. Writing a clear return address matters a lot. If you're designing your own card, make it easy to process. Include both callsigns, date and time in UTC, band or frequency, mode, signal report, and a 'please QSL' or 'thanks' line. Add your grid square, CQ and ITU zones, and the operator's name if it isn't obvious. A standard size around 9 x 14 cm (about 3.5 x 5.5 inches) is easiest for bureaus and for filing. A photo or artwork on the front is nice, but leave the back clear enough that the QSO details are readable. Fancy cards are fun, but a plain one with correct details is far more useful than a beautiful card with the time missing. One note on DXCC: paper cards can still count, but they have to go through ARRL's checking process, and a card that's missing details or has been altered won't be accepted. If you're mostly relying on LoTW, paper is just the backup for entities that don't upload.
-
Breaking the pileup on a rare one: split, timing, and how to prepare for Clipperton or Bouvet-class targets
On the low bands I'd separate two problems: hearing the DX and being heard. Receive antennas fix the first, but the second is about picking a good moment. On 160 m in particular, the DX may hear very little, with a high noise floor and lots of stations calling. Calling on a clear frequency a little way from the main group can be effective, but only if you've listened long enough to know where he is actually listening. If he moves his listening window, you need to follow. Also, think about band conditions as a schedule, not just a signal strength. Sunrise and sunset at both ends of the path, the geomagnetic activity, and local noise from storms all affect when a rare one is workable. For something like Bouvet, the path could be difficult at times and open for only a short window. That is a reason to have your station ready, and to know the DX's published band plan, rather than hunting around when the pile starts. For Clipperton-type operations, I'd also keep an eye on the cluster comments for patterns, such as which band the DX is strongest on at your time of day, or whether he has changed split. They are useful hints, but they are not proof. Verify with your own receiver. And if you're the one spotting, put the real frequency and the real split in the comment. A bad spot can send a few hundred stations to the wrong frequency.
-
EFHW or linked dipole for a quick SOTA/POTA setup? Plus what else belongs in the go-kit
For a park where you are close to the car and in no hurry, the linked dipole is easy to justify. You get a balanced antenna, a coax feed you can choke properly, and an SWR you can mostly predict. The annoyance is band changes. If you plan to hop between 40 and 20 m to chase contacts, lowering the pole every time gets old fast. One common workaround is to pick one band for most of the session and only change when the rate drops. For SOTA, where every gram and every minute counts, the EFHW has an obvious advantage: one wire, one transformer, no links to lose. The thing to watch is the feedline and counterpoise. If the SWR looks fine but the receive noise is high or the radio seems to "feel" the coax, add a choke at the radio end and try different counterpoise lengths. It often cleans up more than people expect. One small thing worth carrying is a few spare connectors and a short jumper, because that is what fails first, not the wire.