Everything posted by Mod_Dan
-
One-radio, one-wire activation kit: EFHW or linked dipole on a telescopic pole?
Linked dipole is the one I'd pick if the plan is to settle on one or two bands. A common SOTA pattern is to start on 20 m or 40 m, then change bands once, and the links make that quite manageable if the pole comes down easily. It's also quieter in the receiver in many setups, because a balanced antenna with a choke doesn't push as much common-mode noise through the coax. That's handy next to a noisy campsite or in a crowded park. Don't skip the boring parts, though. Label each link clearly, carry spare connectors or a few spare links, and keep the wire wound on something that won't tangle. For anything over a couple of hours I'd also bring a small tarp or windbreak, since a comfortable operator makes more contacts than a miserable one with a perfect antenna. And whichever antenna you choose, pack for the weather you might get, not the forecast you hope for, and tell someone where you'll be and when you expect to be back.
-
Building an HF shack around a 100 W rig: what to sort first, grounding and bonding or filters and gear?
I'd put common-mode control ahead of almost everything except safety. Adding more ground rods or a heavier ground strap is a common reflex, but a lot of shack RF problems are really about where the antenna current returns. If the feedline is part of the antenna, the shield carries RF back into the shack. A choke near the feedpoint (a stack of suitable ferrite cores, or coax wound in a coil) is cheap and often changes how the whole station behaves. One caution on the tuner point: the internal ATU in a rig such as the IC-7300 or G90 matches the radio to the line. It doesn't fix the antenna. On a non-resonant wire fed with coax, the tuner can make the transmitter happy while the coax runs at a high SWR and loses power as heat. If that's the situation, a tuner at the feedpoint or a different feed system may serve you better than a bigger amp.
-
Newly licensed? Share your first QSO, your first radio, and what you'd tell the next new ham
For anyone asking "what do I buy first," my answer is: not much, and not before you've talked to a few local hams. A basic dual-band HT, a decent spare antenna, and a programming cable (if your model uses one) will get you on the local repeaters. After that, wait until you know what you actually enjoy before spending real money. The mistake I see most often in new-ham threads is jumping straight to a big HF rig with no plan for an antenna, a power supply, or a place to put the antenna. The radio is only one part of the station. Feedline, grounding, RF safety, and a way to measure SWR all end up mattering, and they aren't glamorous purchases. Also, cheap HTs often have a very wide-open receiver, so you may hear interference or intermod in busy RF areas. If your radio seems deaf or noisy near a tower, that doesn't automatically mean you're doing something wrong. An outboard filter or a different radio might be the fix, but ask your local club first.
-
Sequential vs. vanity call signs: formats, groups, ULS steps, and the rules for holding a call
Two practical points for the reference thread. First, the numeral in a call does not restrict where you can operate. A call assigned for one region doesn't stop you from using it elsewhere, and you identify with your assigned call. Some people add a portable indicator like a slash and a numeral for clarity on the air, but check the current ID rules before you rely on that. Second, on holding a call: the license is what you renew, and if it lapses past the grace period the call goes back into the pool after its waiting period. That matters if you're attached to a call. Set a calendar reminder well before the ten-year date and make sure your ULS email address works, because the FCC sends notices there. For clubs, I'd add that the trustee should keep their own record of who holds the role, since a club call can become a headache when the trustee moves away or lets their own license lapse.
-
Prepping for the Technician (Element 2) exam: what to study, how to use the question pool, and where people lose points
On practice tests: use them to find gaps, not to rack up scores. A workable approach is to read a study guide section, take a short quiz on just that subelement, and for every miss, read the explanation until you can say why the other three choices are wrong. Many question-pool study sites show the reference material or an explanation next to the answer. If a miss doesn't make sense, look it up before moving on. Once you've covered everything, take full 35-question timed practice exams. If you're consistently well above 26 across different practice sets, you're probably ready. Avoid retaking the same set until you know it by heart, since that measures recall of that set, not the pool. On repeaters, the mechanics are a good source of easy points once they make sense: A repeater receives on one frequency and transmits on another. The difference is the offset. On 2 meters the standard offset is 600 kHz, and on 70 cm it's 5 MHz. The direction (plus or minus) depends on the band plan for your area.Many repeaters need a CTCSS (PL) sub-audible tone from your radio before they'll activate. The tone opens the repeater. It isn't a privacy feature.If you can reach the other station directly, use simplex and leave the repeater free. 146.52 MHz is the national 2-meter simplex calling frequency.Listen before you transmit, pause between overs, and keep calls short. Standard practice is to say your call sign plainly and use phonetics when needed.For RF exposure, the key ideas are that the limits (maximum permissible exposure) depend on frequency, power, and how long people are exposed, and that you're responsible for checking your station. Don't try to memorize every threshold. Know the concepts: duty cycle matters, antenna placement matters, and you should keep antennas away from people. For safety, know the basics: ground your station, keep antennas well clear of power lines, and use a proper disconnect or protection for lightning. Those answers are usually common sense plus the right vocabulary.
-
Gain staging and dynamic range on budget SDRs: why ghost signals appear and how to track them down
Good starting point. One thing I'd add is to check the displayed noise floor when you change gain, not just the signals. If turning gain up raises the noise floor by the same amount as the signal you want, you gain nothing, and you just move closer to ADC clipping. The aim is for the antenna's external noise to lift the floor a few dB above the receiver's own noise, and no more. On a quiet VHF band that usually means a higher gain setting than on HF, where atmospheric and man-made noise are already strong. The attenuator test is also worth doing with a known-clean signal. If a strong FM station is the cause, a notch filter at the antenna will make the ghosts disappear, and software tweaks won't. Filters belong before the first active stage; a filter after the LNA can't undo the overload that already happened in the LNA. For HF with an upconverter, check the converter's local oscillator frequency and remember that your SDR software will show frequencies offset by that amount unless you set the offset in the program. SDR#, HDSDR and others each have their own way to configure it, so verify with a known station such as a time signal or a broadcast carrier before trusting the dial.
-
Building a 5 W portable QRP setup: rig choice, antenna, and power. Where does the efficiency actually come from?
The antenna point is the one that gets overlooked most. Many people spend serious money on a radio and then hang a short wire six feet off the ground. A rough way to think about it: 3 dB of antenna or feedline improvement is the same as doubling your power, and at 5 W doubling is a bigger practical step than it sounds. On EFHWs, keep the matching unit's limits in mind. A transformer rated for QRP power is fine at 5 W, but the quality of the core and winding affects loss, and the coax shield will often act as part of the antenna unless you add a choke or a counterpoise. If you see SWR change when you move the coax, that is usually a sign the feedline is part of the radiating system. It is not necessarily a fault, but it does change patterns and noise pickup. For the rig, I'd pick by how you plan to operate. If you only want CW on a hill, a small dedicated CW rig keeps the weight and current draw low. If you also want SSB or digital, a KX2 or KX3 gives you a lot more flexibility, at the cost of price and a steeper learning curve. A Pixie is a fun build, but it makes sense to treat it as a project and not as your only field radio.
-
Planning your first POTA activation: 10 QSOs, spotting, logging, and two-fer questions
For hunters, I'd lean on the spot list plus a logger that can pull in or at least display park references. Then focus on being a clean caller: send your call once or twice, listen, and don't talk over the activator. If they're clearly running a net-style pileup, listening first will tell you whether they want a full call, suffix only, or something else. One thing I'd add for the two-fer question: if you work an activator in a multi-park location, your hunter log may need each reference entered or recognized properly. Check how your software handles multiple references. Misformatted ADIF fields are a common cause of missing credit, so compare your export against the current POTA logging instructions. Also, park-to-park contacts are a nice target because both stations can benefit. They're worth chasing if you're activating and have spare time between calls, but they shouldn't distract you from hitting your 10 QSOs.
-
What makes a rig a "keeper" when newer radios beat it on paper?
For me the receiver comes first, but not in the way spec sheets suggest. Numbers like third-order intercept and blocking dynamic range tell you a lot about how a radio behaves next to a strong signal. They don't tell you how pleasant the audio is during a long session of listening for weak stations. One caution on older radios: age matters as much as design. Electrolytic capacitors dry out, switch contacts get dirty, and alignment drifts. A radio with a great reputation can perform badly if it hasn't been recapped and checked, so a "keeper" often means the design plus the maintenance. If you're buying something vintage, look at how it's been cared for before you look at the brand name.
-
ARES, RACES, MARS, SKYWARN, CERT: how they differ and what to train for first
On net control, the thing that tends to help most is separating the roles. Directed nets run better when the net control station only manages the flow: calling for check-ins, assigning tactical calls, and prioritizing traffic. A separate logger records check-ins and messages. If one person tries to do both for hours, the log gets sloppy and the net slows down. Rotating net control every couple of hours is also sensible, because fatigue shows up as missed calls and unclear instructions. A few habits make nets smoother. Call for emergency or priority traffic first, then routine check-ins. Keep transmissions short and let stations pass traffic directly when they can instead of relaying everything through net control. Have a written script and a net roster template ready so that whoever sits down can run it cold. Practicing with simple scripted scenarios at regular weekly nets does more for readiness than an occasional big drill.
-
QSL workflow: LoTW first, then eQSL, QRZ, Club Log OQRS, bureau, or direct?
On design, the card is the only part of this that people actually keep, so it is worth making readable. A busy photo is fine as long as the QSO data block is clear, with callsign, date, UTC time, band, mode, and report in plain print. Dark artwork under the writing area looks nice online and then makes the card hard to fill in or read. If you are mailing direct, include the return envelope already addressed, and enough postage for the destination country. Looking up the current rate for that country is better than guessing. Some people also add a short note, like a list of the QSO details, in case the card gets separated from the envelope. And on the digital side, make sure your station details in each service match, since mixed-up zones or grid squares are a common reason confirmations fail to match.
-
Breaking a DXpedition pileup: split, timing, tailending and what actually gets you in the log
On choosing where to call: I'd say the most useful skill is working out the DX's "pattern" rather than guessing. If he's working up, listen to a few stations he picks and note whether he tends to move up, down, or hold one spot between calls. If he's hopping around within a range, calling where the last QSO happened is usually a bad bet, because everybody else is there too. A slightly offset call, within the permitted window and with a clean signal, often does better than the most obvious frequency. The caveat is that the offset must not be so wide that you sit on someone else's frequency or outside what he's listening to. On tailending: I'd separate it into two cases. If the DX is deliberately running a fast cycle, with a short exchange and straight into "QRZ", then calling on the first beat of his listening period is normal. If it's a slower operation where he's struggling to copy, any call over the end of a QSO just makes things worse. I'd always rather miss a cycle and be copied cleanly than be a partial that costs him another repeat. One more practical point on split: check the audio bandwidth and filters on the transmit side. If your signal has splatter or you're running a lot of processing, a split-frequency call can spill into the neighbouring slots and get you complaints even if your frequency is right.
-
Which radio mods are actually worth doing, and where do MARS/CAP and legal limits fit in?
Measure first, because many mods fix things that aren't broken. For noise, a cheap AM receiver or an SDR near the radio and power supply will show you where the hash is coming from. Switching supplies, USB chargers, LED lighting and laptop bricks are the usual suspects. Clip-on ferrites help, but the number of turns and the ferrite mix matter. A few turns of coax through a suitable core at the radio end often does more than a pile of random beads. For HF, a common-mode choke at the feedpoint and another near the shack entrance is a more reliable fix than a receive mod. On expanded receive: yes, it's useful for airband, public service monitoring where legal, and weather. But the front end in most handhelds is tuned for the ham bands, so outside them you can expect reduced sensitivity, image responses and overload from nearby broadcast or paging transmitters. An FM broadcast notch or a bandpass filter on the antenna port often helps more than any internal change. If a radio sounds worse after an unlock, that may be the front end doing what it was designed to do. TCXO is a good example of a mod that's only worth it if you can verify it. At 440 MHz, 1 ppm of error is about 440 Hz. That doesn't matter on wide FM, but it can matter for narrowband digital voice or weak-signal work on UHF. Check against a known reference such as a frequency counter or a calibrated SDR, and compare before and after rather than assuming the part improved things.
-
Getting my first ham license: how do I find an exam session, what does it cost, and how should I study for Technician?
I'll take the logistics first, since the acronyms are the confusing part. A VE is a Volunteer Examiner, an licensed amateur who is accredited to give exams. A VEC is a Volunteer Examiner Coordinator, an organization such as the ARRL VEC or W5YI that coordinates the VE teams and files the paperwork with the FCC. When you take a test you're usually dealing with a local VE team that works under one of those coordinators. To find a session, search the ARRL's exam session finder, and also check HamStudy's session search, which pulls in sessions from several coordinators. Local clubs often post their own schedules, and many teams run remote (online) sessions through video, which is handy if nothing is nearby. Most teams want you to register ahead of time or at least contact them, so don't just show up. Read the announcement, because it will tell you the start time, location, and what payment methods they take. On fees: the exam fee is set by the team or coordinator, not by a single national price, so check the session listing. It's typically a small amount and often cash, though some teams take electronic payment. Rules around FCC fees for amateur licensing have changed over the years, so verify on the FCC's amateur licensing pages rather than trusting a forum post, mine included. FRN: this is your FCC Registration Number. It's free, and you get it by registering in the FCC's CORES system. You need it before the exam, because the VE team has to put it on your application. Do it a few days ahead rather than the morning of, in case the FCC site gives you trouble. ULS is the Universal Licensing System, the FCC database where your license is recorded. You'll look yourself up there after you pass to see your call sign appear, and you'll use it later for address changes and renewals. For test day, bring a government photo ID, your FRN, a pencil, and a simple calculator if you want one (the Technician exam has very little math). If you already hold a license, bring a copy. The Technician exam is 35 multiple-choice questions drawn from a public pool, and you need 26 correct to pass.
-
From 5 to 20 WPM: what actually moves the needle, and how do you get past the plateaus?
On the keying side, a few settings are worth getting right early because they affect how your sending sounds, which affects how well other operators copy you (and how well you can copy your own sending in practice). Keyer speed. Set your sending speed to something you can copy, not to your aspirations. Sending faster than you can receive tends to produce sloppy spacing, and if you send badly it is hard to get good practice from it. Iambic mode. Most keyers offer Mode A and Mode B, and they differ in what happens when you release the paddles during a squeeze. Neither is objectively correct, and the choice mostly comes down to what you learned on. If you switch rigs or keyers, it is worth checking the mode, because mismatches cause extra or missing elements that feel like your own errors. Paddle adjustment. Contact gap and tension are worth experimenting with. A very light, narrow setup can cause double-dits and accidental contacts, while a stiff, wide one slows you down. Make small changes and give each one a few days before judging it. Decoding by ear versus software. A software decoder is handy as an occasional check, for example to see which characters you keep missing in a recorded file. As a real-time crutch it has two problems. First, it tends to struggle with fading, noise, and irregular hand-sending, so it produces garbage exactly when conditions get hard. Second, if you look at the screen you stop training your ear. A reasonable compromise is to copy first, then compare against the decoder or the original text afterward. Contests and nets. Contests are excellent for speed building because the exchanges are short, repetitive, and predictable, so you can practice at a higher speed than a rag chew would allow. Many people start by just listening and copying callsigns, then make a few contacts, then go in properly. Slow-speed CW nets and practice sessions exist too; check current schedules and rules with the sponsoring group before joining, since they change.
-
APRS on 144.390: how mic-E, SmartBeaconing, digipeater paths and iGates fit together (and where Direwolf, the D74/D75 and FT5D come in)
A few practical additions on the software side. With Direwolf, most trouble is audio level, not configuration. If the input level is too high or too low, decoding drops and you will see missed packets even though the config is perfect. Direwolf prints audio level information for each decoded frame, so use that to adjust the receive level, and make sure your radio's data or packet mode and its squelch behave as expected. Also watch the transmit side: overdriving the audio into the radio's mic or data input widens the signal and hurts decoding for everyone. For SmartBeaconing, keep the idea of the tradeoff in mind. A faster fast-rate gives a smoother track but uses more channel time, and 1200 baud channels are shared by everyone in range. A turn-triggered beacon is useful, but a very low minimum turn time can produce bursts on twisty roads. Start from the defaults your radio provides, watch your trail on aprs.fi, and adjust one parameter at a time. Walking needs different speed thresholds than driving; the slow speed and fast speed values should reflect your actual speeds. On weather stations: the packet format is simple, but units are specific (Fahrenheit, mph, hundredths of an inch for rain, pressure in tenths of a millibar), so a weather program that converts units is worth using rather than hand-building packets. Beacon the weather at a modest interval. Weather data rarely changes fast enough to justify frequent transmissions.
-
Field station planning: power, antennas and noise control, and what order do you set things up in?
On order of operations, a sequence that holds up is: safety and site layout, then power, then antennas, then radios, then a noise check, then a communications check. The site layout step gets skipped most. Before anything is unpacked, decide where the generator goes (downwind and well away from the tent and any air intake, never in or under the shelter), where the mast goes, and where the coax and power lines will cross walkways. Carbon monoxide is the hazard that actually hurts people at field sites, so a battery CO alarm inside an enclosed shelter is cheap insurance even when the generator is outside. On the generator question: with a LiFePO4 bus, the generator becomes a charging tool. Run it, fill the battery through a proper charger or DC-DC source, shut it down, and operate quietly. That cuts fuel use, noise and RF hash, and it also makes it simpler to stay on frequency during net traffic. If you need AC for a charger, check that it tolerates the generator's output and doesn't hunt when the load is small. Solar is more useful as a trickle supplement than a primary source unless the panels are big. Use an MPPT controller with a LiFePO4 profile, and note that LiFePO4 shouldn't be charged below freezing unless the battery has low-temperature protection or heating. Test the controller with your receiver on HF before trusting it, since some are noisy and the fix may be ferrites on both the panel and battery leads, or simply moving the controller. On grounding: for personal safety, make sure the generator is used per its manual and that any AC equipment is on GFCI protection. For RF, a ground rod rarely fixes an HF noise problem. If the antenna is a dipole with a good choke, common-mode current is usually the real issue. Also, nothing about a field antenna is lightning-safe, so the plan is to take it down and disconnect coax when a storm is approaching, not to rely on a rod.
-
Remote station control: how to pick a path (Icom LAN, Yaesu SCU-LAN10, RigPi, Flex, RemoteHams) without creating a security or compliance headache
Worth separating the audio chain from the CAT chain when you troubleshoot. With an IC-7610 over RS-BA1 or wfview, with a RigPi and Hamlib, or with an SCU-LAN10 setup, symptoms often look like "the radio is laggy" when the cause is a mismatch in audio sample rate, buffer size or codec settings at one end. Change one thing at a time and write it down. Also confirm what the software does with compression: some paths trade bandwidth for latency, and the default is not always right for a weak mobile or satellite uplink. For CW, I'd test the keying path with a sidetone at the operator end and a monitor at the station end, and compare what each hears. If the remote end is adding a visible delay or distortion, shorten the chain, use a keyer near the radio, or move to a text-sending approach. A decent paddle feel over a long, jittery path is not realistic for fast CW. For the rules side, keep a one-page document for each station: who is the licensee, who is the control operator, what call sign is used, which country the transmitter is in, and how the transmitter can be shut off by someone on site. If you ever share access with others, that page is also where you record who may transmit, on what bands, and under what license class. It saves arguments later, and it helps if a regulator or contest committee ever asks how the station is controlled.
-
Studying for the Amateur Extra (Element 4): where should I spend my time on the theory?
On the Part 97 side, read the questions together with the actual rule text, not only the answer key. The rules questions are the easiest place to lose points by assuming you already know the answer from General-level habits. Pay attention to the details: who can be a control operator, station identification requirements, restrictions on certain operations, how volunteer examiner (VE) coordination works, and the definitions in the rules. As for what the Extra gets you, the headline is that you get all operating privileges on all amateur bands and modes. In practice that includes the Extra-only segments at the low end of several HF bands, plus a few exclusive phone sub-bands. The exact edges and band plans have changed over the years and can vary by mode, so check a current ARRL or FCC band chart instead of relying on a memorized number from a forum post. Whether it's worth it depends on what you want from the hobby. If you chase DX, work contests, or regularly find the General segments crowded, extra spectrum matters. If you mostly do VHF/UHF or local nets, the benefit is smaller, though many people still upgrade for the theory and the ability to serve as a VE for higher-class exams. One logistical point: you need credit for Elements 2 and 3 (Technician and General) before you can take Element 4 for the Extra. Once you have your General, a good routine is to take timed practice exams in the same format as the real thing, track which subelements you miss, and drill those weak spots specifically.
-
Digital mode chain checklist: audio levels, time sync, CAT and picking the right mode for the band conditions
Troubleshooting order matters, so here is one that usually isolates things quickly. Start with the clock. Look at DT values in the decode window. If the strong stations cluster near 0.0 and yours is the one that looks off, fix time sync before touching anything else. A DT consistently beyond about plus or minus 1 second will reduce decodes noticeably, and beyond that you start losing them entirely. Next, check transmit audio. In WSJT-X, set the Pwr slider and the soundcard output level so the radio's ALC barely moves, if at all. FT8 and FT4 are constant-envelope modes, so you do not need to push the radio into ALC to get a bigger signal. All that does is spread distortion products on either side of your signal, which people see as a wide, splattery trace on the waterfall. If you are running 100 W rated gear, running well below full output is normal for these modes, since you are keying a continuous carrier-like signal for most of the 15 seconds. Receive level is the other half. The WSJT-X receive meter has a recommended zone, roughly around 30 dB, and the exact number depends on the app and sound card. What matters is that the noise floor on the waterfall is visible but not saturated. If you can see the waterfall going fully white or fully black, adjust before blaming propagation. On CAT, the usual traps are mismatched baud rates between the radio menu and the software, and a USB audio device that gets renumbered after a reboot, so the program is pointed at the wrong sound card. The software also needs to be told whether the radio is in USB or a data mode such as USB-D or PKT, and which filter width the radio should use. A 500 Hz filter can quietly clip a 3 kHz FT8 passband, so check filter width on the radio first. As for how to separate weak-signal from just a different way to send text: if the mode has strong FEC and a defined timing structure so the decoder can integrate over a known window, I call it weak-signal. PSK31 is more of an "is it readable" mode, whereas FT8, WSPR and Q65 are built around statistical decoding.
-
Winlink over radio: what's a sensible order for setting up Express, gateways, VARA/ARDOP/packet and P2P?
I'd start with Telnet, because it isolates the account and software from everything radio-related. Install Winlink Express, enter the callsign, and set the password. Then run a Telnet session to the CMS over the internet. If that works, the account, the password and the message database are fine, so any later failure is down to the radio side. Passwords are case sensitive, and the account password is the one thing to record somewhere safe. Winlink has a password recovery process, but it depends on the contact details on the account, which is a poor thing to discover mid-exercise. While you're in Telnet, practice message handling. Compose a message, post it to the Outbox, and run a session. Notice that nothing moves until a session connects. Posting to the Outbox only queues the message. The session exchanges whatever is waiting in both directions. Also get the group into the habit of keeping attachments small, since every byte costs airtime on HF. Pictures that are fine over Telnet are a bad idea over a marginal HF path. Next, do forms. In Winlink Express, templates are under the message composer's template selection, and the ICS USA forms include ICS-213. When you send a form, the visible message text carries the content and the form data travels along as an attachment. A recipient without Winlink Express can usually still read the text, but a recipient with it gets the rendered form view. Test the ICS-213 over Telnet first so people learn the template workflow before they add RF problems. For the radio side, do VHF first because it's the simplest path. With RMS Packet you need a TNC (hardware, or a software modem like Direwolf feeding Winlink Express through KISS) and an RMS gateway you can reach. Use Channel Selection to list gateways, make sure your grid square or location is set correctly, and sort by distance. Frequency and PTT setup are separate issues from gateway choice, so don't confuse them. A failed connection could be a no-copy, a PTT problem, or bad audio levels.
-
Building a wire dipole from scratch: wire, feedpoint, choke, ladder line, and how far to trust SWR and models
On the choke: the goal is a high common-mode impedance at the operating frequency, ideally in the thousands of ohms, so the coax shield doesn't become part of the antenna. A coil of coax can work, but it's narrowband and self-resonant, so the number of turns and the coil diameter need to be matched to the band. For multiband use, ferrite is easier to get right. Mix 31 is generally favored for lower HF, mix 43 for the upper bands, and stacking several cores on the coax raises the impedance. A choke at the feedpoint and a second one a quarter wave or so down the coax is a common approach on a dipole. At high power or high SWR, heating in a marginal ferrite choke is real, so don't choose the smallest core that technically fits. A quick way to see whether common-mode current is a problem: watch whether the SWR or the analyzer reading changes when you move the coax, touch the shield, or add a few feet of cable. If it does, the feedline is radiating or picking up. This isn't a measurement of choke impedance, but it is a good practical warning sign. For resonant versus non-resonant: a coax-fed dipole cut for one band is simple and efficient. A doublet of about 130 to 135 ft fed with ladder line and a tuner covers many bands, but the tuner and any balun at the tuner become part of the system. Use a good current balun there, and remember that the ladder line itself is low loss even when the SWR on it is high. The balun and tuner can be where the loss is. For trimming: build the dipole 3 to 5 percent long, hang it at its final height and shape (an inverted-V with a 90 to 120 degree apex will lower the feedpoint impedance), then shorten both legs by equal amounts while watching the analyzer.
-
Breaking pileups on rare DX: split, timing, tailending and what actually gets you in the log
For low-band DXing, a lot of what works on 20 metres either doesn't apply or becomes more important. On 160 and 80 metres the limiting factor is usually receive, not transmit. A good receive antenna such as a Beverage, a flag or a small loop array can let you hear the DX out of the noise when your transmit antenna hears nothing but static. If you can't hear the DX, no amount of power is going to help you. Timing matters too: the path often opens around grey-line sunrise or sunset, so the window can be short. Watch both ends of the path and be ready on the frequency before the opening, not after. DX cluster spots help, but treat them as leads rather than confirmation. Spots can be wrong, busted, or based on a skimmer decode of a partial call. Listen to the DX yourself before you call, and if you do spot, spot what you actually heard, with the frequency and the split information if you know it. Don't spot yourself. For planning your own chances, Club Log is useful in a few ways. The Most Wanted list gives you a rough picture of which entities are hardest for the community, and your own log's band and mode slots help you decide where to concentrate when a DXpedition is on. Many DXpeditions upload logs to Club Log, so you can search the expedition's log after the event to check that you're in it, and use their OQRS if they offer one. That said, check the expedition's official page for how they handle QSLs, because systems and rules differ between teams. Also, if the operation uses FT8 in Fox/Hound mode in WSJT-X, the rules are different from conventional SSB/CW. Follow the expedition's published instructions, such as keeping your transmit frequency above the stated threshold, and don't keep calling when the Fox hasn't selected you. Reading the DXpedition's instruction page carefully before the operation starts, including band plans, modes, and any pilot station information, will save more time than any trick on the day.
-
When is a new multiplier worth leaving your run frequency? Rate vs. score, and where SO2R actually helps
On skimmers and spotting: first check the category rules, because using packet, cluster, or Reverse Beacon Network spots generally puts you in an assisted category, while unassisted entries don't get those spots. Many people treat RBN as a gray area, but most rule sets are explicit, so read the current rules for the contest you're entering. If you're assisted, a skimmer feeding the N1MM band map can make S&P for multipliers much more efficient. You see who is on, and where, without moving the VFO. The caution is that skimmer decoding can be wrong on callsigns, especially in a busy band with weak signals or QSB, so verify the call by ear before you send it. Also use a bandmap filter so that already-worked stations and non-mult spots don't clutter the display, and make sure your logging program marks new multipliers clearly. For band changes, one habit that helps is to check what the band map shows on the next band before you leave the current one. If there are three or four spotted multipliers waiting and your run rate has dropped, that's a good moment to go. Antenna-wise, for the multiplier hunt, directionality and the ability to rotate quickly matter more than a few extra dB on a single heading. A stack that can cover different regions without a long rotor delay lets you grab multipliers in more directions while keeping the run frequency alive.
-
Building a ham go-kit that actually works: what to pack, what to test, and where GMRS/MURS/FRS fit
On GMRS and FRS, one thing worth talking about is channel discipline. Everyone in the family should know a primary channel and a backup, and the radio should be set to a specific privacy code or none, consistently. Mismatched settings are a common reason two radios "can't hear each other" when everything else is fine. Print the settings on the back of the radio card. Also, for the hams reading: a ham HT does not substitute for GMRS equipment. GMRS channels have their own rules and you need the proper license and type-accepted equipment. Many people keep a cheap FRS/GMRS pair for non-ham family members and a ham HT for themselves, with a plan that says when and where each is used. If you want a single rig for both, check that its type acceptance covers the service you are transmitting on. And regardless of service, check that your battery type and charging cable match what is in your car and in the bag. Mixing chargers is a hassle at the worst moment.