Everything posted by Mod_Dan
-
Breaking pileups on rare DX: split, timing, tailending and where to actually call
On choosing where to call: the useful thing to watch is the DX station's own receive behaviour. If they keep picking callers from one narrow part of the pileup, there is usually a reason, such as the DX antenna's directivity, a noise null at their site, or simply that they leave the receiver parked there. If instead they sweep slowly up and down, the best approach is often to be slightly off the biggest cluster, with a signal that is cleanly zero-beat on whichever offset you choose. On CW, a frequency that is off by a hundred hertz can make your call sound like the tail of someone else's. A sharp, stable signal on a slightly quiet spot often beats a louder one in the middle of the crowd. On tailending, the common-sense rule is to listen for the rhythm. When the DX operator is running tight exchanges, with callsign, report and then the next call, there is only one short gap per QSO, and everyone is competing for it. In that case calling just after the final DX transmission is the only practical choice. If the rate is slow, wait for the clear end and let the DX decide, instead of calling on top of their exchange. And stop calling whenever you hear the DX transmitting. It sounds obvious, but a lot of lost time in a pileup comes from people who keep sending through the DX's reply. For FT8 pileups, check the DXpedition's own instructions first. Some use Fox and Hound mode, where the DX transmits in a defined range of the audio passband and hounds are supposed to call above a set frequency. Calling on the fox's frequency harms the whole operation, so follow the published procedure exactly.
-
Go-kit philosophy for SOTA/POTA: what's actually worth carrying, and what's just weight?
Adding the group-operation angle, because Field Day-style setups put different pressure on the same decisions. With several stations on site, antenna separation, band filters and cable management matter more than weight. A transmitter on 20 m close to a receiver on 15 m can wipe out the neighbor's audio even when both are working perfectly in isolation. Bandpass filters and sensible antenna placement help far more than turning the power down. Power distribution is where group setups most often go wrong. A properly fused distribution block with a fuse per rig, adequate wire gauge, and labeled leads is boring but saves a lot of confusion when something trips at 2 a.m. LiFePO4 can supply very high current into a short, so fuse close to the battery terminal, not just at the radio. On logging, shared logging software on a local network is great until the Wi-Fi hiccups. Agree on a backup in advance: paper sheets per station, a clear rule on who is the master log, and a periodic export. Duplicate checking and clean ADIF export are much easier to sort out before the event than after it. For weather, treat it as part of the operating plan. Decide in advance who watches the sky, what the threshold is for shutting down, and where people go. Disconnecting antennas from the radios and lowering masts takes time, so start before you need to.
-
Chasing award credits without losing track: how do you organize DXCC, WAS, WAZ, WPX, IOTA and the rest?
On deleted entities, the main thing is to separate three questions: what counts toward your total, what counts toward Honor Roll, and whether the QSO date falls in the valid period for that entity. A contact with an entity that was valid at the time is a different case from a contact claimed after the entity was removed from the list. That's why a date-aware entity lookup matters more than a name lookup. Callsign prefix alone is not enough, especially for DXpeditions and for operations that straddle boundary changes. I'd also keep a separate note field for anything with a doubtful status, such as a new operation that might need approval for DXCC credit. Don't count those toward your total until the program has accepted them. It's easy to feel like you're 'one away' when the credit is still pending review. For paper QSLs, think about how much each card improves your odds. If the station uses LoTW and has a good upload record, waiting is usually cheaper. If the operation is rare, short-lived, and unlikely to upload to LoTW, a direct or bureau card may be the only realistic route. In that case, make sure the card includes the data the award checker will look for: callsign, date, time in UTC, band and mode. For WAZ and WPX, the quirks are different. Zones can be missed when you assume 'near enough', and WPX can reward prefixes you wouldn't normally chase. Keep those in separate views so you don't confuse entity progress with zone or prefix progress.
-
Getting from 5 to 20 wpm: what changes at each stage, and where do people stall?
The wall at 10 to 13 wpm is mostly about how you handle mistakes, in my reading of how learners describe it. If a missed letter makes you stop and puzzle over it, you lose the next two or three characters and your copy collapses. Practicing the habit of dropping a blank and carrying on tends to help more than another round of letter drills. For head copy, one gradual way in is to copy on paper but stop writing the easy words. Write only callsigns, numbers, and names, and let everything else go by in your head. Another is to listen to text slightly above your comfort speed without writing at all, and treat it as exposure instead of a test. Comprehension comes before accuracy. On software: it makes a useful answer key. Send yourself or a trainer's text, copy by ear, and compare. Having a decoder running live while you listen is where the crutch problem tends to start.
-
Getting the most out of 5 watts: rigs, antennas, power and where to find other QRP stations
Regarding the kit side, I'd split the choice by what you want from it. A Pixie is a good way to understand a transmit/receive switching idea, but it won't be the radio that fills a log, so treat it as a lesson. Something like the TR-35 or a Hendricks kit gives you a usable radio at the end, with a proper receiver, and that tends to keep a project from ending up in a drawer. If you're mainly interested in SOTA or park-style activations, the weight and current draw matter more than the feature list. A multiband CW-only rig such as a Mountain Topper is attractive because the whole station, including antenna and battery, can be packed small. If you want to talk on SSB as well, the KX2 or KX3 makes more sense, at the price of more money and more battery use. On contests, QRP-ARCI events are a friendly way to see how your station compares with others. Read the exchange and power classes before the weekend so you know what you need to send. Also log your actual output, not just the dial setting, because a rig's power meter can read differently from what is really leaving the antenna.
-
Getting usable HF from an SDR: direct sampling vs. upconverter vs. a purpose-built receiver, and where the noise really comes from
For overload versus real signals, the quick test is to change the gain and see what moves. Drop the RF gain or add attenuation. Real signals will fall by roughly the same number of dB and their relationship to the noise floor stays similar. Images and intermod products usually move by a different amount, or vanish quickly. If a ghost signal appears that doesn't match a known band plan, also check whether it still appears when you disconnect the antenna. If it stays, it's internal, and USB noise or a poor power supply is a suspect. On filtering ahead of an 8-bit dongle, I'd say it can be worth more than a hardware upgrade if you live near strong broadcast transmitters. A bandpass for the band you want, or a broadcast-band notch for FM, cuts the total power reaching the ADC. That matters more than the nominal noise figure, because the limit is the strongest signal rather than the weakest one. If you are in a quiet location, the difference may be smaller.
-
Moving from FM birds to linear: Doppler, tracking software and antennas for SO-50, AO-9x, RS-44 and QO-100
One thing that changes behavior with the Arrow-type antenna is polarization and body position. Since it is a linear antenna on a satellite whose polarization effectively spins from your point of view, you will get deep, slow fades. Rotating the antenna about the boom in small increments can recover a signal faster than changing your aim. Keep the antenna pointed at the predicted position and make the roll adjustment second. For RS-44 on SSB, a useful practice is to start by listening to the beacon and set the downlink frequency before you transmit. Then transmit low power and find where your voice or CW tone appears in the passband. It helps to keep a note of the transponder's inversion: moving the uplink up moves the receive frequency down. Most of the confusion on linear birds comes from this rather than from the radio. As for QO-100, don't underestimate the dish alignment. Since the satellite does not move, the pointing only needs to be set once, but a dish aimed slightly off can still cost you several dB at 10 GHz. The beacon is the right reference for fine alignment, and the AMSAT-DL and other QO-100 community pages publish current band plans and operating etiquette.
-
Building out an HF shack around a 100 W rig: what to sort out first (power, tuner, filters, bonding)?
I'd tone down the idea that a band-pass filter is the first purchase. For a single-operator station with one transmitter, it usually isn't. A BPF belongs in the chain when a transmitter on another band is close enough to overload the receiver, which is typical for SO2R and multi-op setups. For ordinary use, the common wins are a good low-pass filter for harmonics on the amplifier output, and a separate receive antenna, which the IC-7610 and K3S both make easy with their RX antenna connections. On the IC-7610 you can also make use of the second receiver for diversity-style listening. On bonding, I'd say the real goal is predictable behaviour rather than a magic ground. Tie the chassis together with short, wide strap. Run the coax through an entrance panel, with arrestors bonded to the same system as the house ground. Then deal with common-mode current, which is usually what causes RF in the shack. A choke on the coax at the radio and again at the entrance often does more for RFI than adding ground rods. USB and CAT cables are another common path, so use ferrites on them. If you get hum or noise on a digital interface, a ground loop through the computer and the rig is a likely cause, and USB isolation can help. Lightning protection is the one place I'd stay conservative. An arrestor does not make a station safe in a direct strike. The most dependable protection is to disconnect and move the coax outside the building when the station is not in use. Check local codes for how the entrance ground has to be bonded to the mains ground.
-
SSB audio setup: mic gain, ALC, processor and bandwidth for a clean signal that still gets through
I'd put a recording check ahead of the meters. ALC and compression meters are only a proxy; the rig can show healthy levels while the audio still sounds boxy because of a poorly placed mic or a harsh EQ curve. Record your transmission into a dummy load or listen via a second receiver and compare it against a station you know sounds good. Then you're adjusting for the sound, not for a needle position. One caution on the processor: the right amount depends on conditions. In a quiet band opening, you may not need any, and the unprocessed audio will be more natural. When the band is noisy and the other station is hunting for you, a little compression can help, but there is a point where more processing only makes you louder in the shack and not any more readable at the far end. If the other operator asks you to repeat something, turning the processor up is often the wrong response; slower, clearer speech and a good callsign delivery usually do more.
-
Building a Winlink station from scratch: Telnet first, then gateways, modes, P2P and forms
On Radio-only, P2P and forms. Radio-only is a message option in Winlink Express meant for situations where you want the message to travel only over radio paths and not through internet-connected delivery. It is aimed at emergency use where you do not want traffic exposed to or dependent on internet routes. It limits who you can address (Winlink users, not arbitrary internet email), so read the current help text on how it handles addressing before relying on it in an exercise. P2P (peer to peer) is different. Two stations connect directly with no gateway and no CMS, so it works with the internet down and no RMS in range. One station listens and the other initiates, in Packet, VARA, ARDOP or Pactor. It is a good fit for a served-agency site talking to a net control station. Test it before you need it, and confirm how outbound messages are selected for the P2P session (for example, addressed to the peer's callsign) in the current docs. Messages exchanged P2P also don't reach the CMS unless one end later forwards them, so if a message must leave the area, someone has to send it through a gateway. For forms, Winlink Express includes templates, including ICS-213 General Message. The form opens in a browser, you fill it in, and Winlink Express builds the message with the form data attached. The receiving station needs Winlink Express with the matching templates to see it rendered properly, so update templates while online, and make sure both ends have the same set. Keep form messages short and avoid large attachments, because every byte costs airtime, especially on a weak HF path or a busy packet channel. Winlink Wednesday is a good habit as a weekly practice. The exact format varies by group, so go by the instructions from whoever organizes it rather than assuming. A useful drill is to refresh the channel list, run a Telnet check, try one radio gateway session on each mode you own, and send a short ICS-213 to a known test address. That catches expired passwords, stale templates, sound card drift after a Windows update, and a missing PTT setting while the stakes are low.
-
Getting your first ham license: how do I find a test session, what is an FRN, and what should I study for Technician?
On studying, the key point is to use material that matches the current question pool. Technician questions come from a published pool that is revised on a multi-year cycle. Before you buy a book or trust an app, check that its pool dates cover the day you'll test. An old book can still teach the concepts, but you'll hit questions that don't match. Apps and practice exams. HamStudy gives you flashcard-style study, practice tests, and tracking of the questions you keep missing. Practice exams are most useful when you review the wrong answers and learn why they were wrong. A passing score on a practice test isn't enough if you just memorized answer letters. The real exam can scramble the order of the answer choices. The ARRL manual. It's optional, but it helps if you want explanations rather than only drilling questions. It covers things like how a repeater works, why antenna height matters on VHF/UHF, and what a band plan is. A common approach is to read a chapter, then drill the matching section of the question pool. If you learn well from apps alone, that can work too. Mixing both tends to stick best. Test tips. Technician is 35 questions and you need 26 correct. Read every word, because some answers differ by only a single term. Don't change an answer unless you can say why. Spend extra study time on the areas that trip people up, which are usually rules and regulations, station operation, and electrical basics such as Ohm's law and units. After you pass. The VEs submit your application. In a few days your callsign should appear in ULS, and the FCC will email you the official license, which is electronic. Don't transmit until your callsign shows up in the database. Then: Check your ULS record for the correct mailing address and email.Find your local club and the repeaters in your area, and listen before you transmit.Start with 2 m and 70 cm FM. Learn to identify with your callsign properly.If you buy a handheld, pick one you can program, and read the manual rather than copying a random frequency list.Technician also grants limited HF privileges, so there's room to grow later if you want to upgrade.
-
Technician to General: how should I split study time across Element 3's 35 questions and the HF sub-bands?
The exam is split into subelements, and the weighting should drive your plan. The long-standing layout is roughly: safety (2 questions), FCC rules (5), operating procedures (5), propagation (3), amateur practices (5), electrical principles (3), circuit components (2), practical circuits (3), signals and emissions (3), and antennas and feed lines (4). That adds up to 35. Check the current question pool release for the exact numbers, because the pool is revised on a cycle and the NCVEC publishes the current one. Notice that the rules and operating sections together carry about as many questions as everything involving math and electronics. A common mistake is spending most of the time on the technical chapters because they feel intimidating, while the sub-band questions are easier points. You need 26 of 35, so you can miss nine. Missing a couple of propagation questions won't sink you, but guessing at the frequency questions could. On sub-bands, don't memorize a table of numbers with no structure. Learn the pattern first: each HF band has a CW/data segment at the bottom and a phone segment above it. Then learn the exceptions. 30 meters is CW and data only, with a 200 W PEP limit. 60 meters works differently from the other bands, so check the current FCC rules and an up-to-date band chart before you rely on any old memory aid. Questions often hand you a specific frequency and ask whether a General can use USB or CW there, so practice with actual frequencies and not just band names. For pacing, many people with a Technician background, who already know the basics of rules and safety, plan something like three to six weeks of regular study. How long you need depends mostly on how comfortable you are with the math. A week of two or three short sessions is enough for the Ohm's law, power and dB questions if you work through them by hand.
-
Newly licensed? Share your first QSO plans, what to buy first, and mistakes to avoid
On "what to buy first": I would hold off on the big purchase until you know what you want to do. A cheap dual-band handheld is a low-risk way to find out whether you like local nets, repeater chatter and simplex. Check the model's programming options first. If you can load frequencies from a computer with a cable and free software, you will save a lot of frustration over typing in memories by hand. The stock rubber-duck antenna is usually a compromise. A better antenna, such as a roll-up J-pole or a magnetic-mount whip on a metal surface, often helps more than a more expensive radio. For HF, plan the antenna before the transceiver. A modest radio on a decent, well-matched antenna will outperform a fancy radio on a poor one. Also budget for coax, connectors and a way to check SWR, because those parts decide whether the radio gets out. One more thing: do not transmit into a disconnected antenna port. Some radios tolerate it for a moment, but it is not a habit you want.
-
Dual-band mobile setup: FTM-500D vs ID-5100A vs TM-D710G, plus wiring, noise and cross-band repeat
On picking among the three, I'd start from the features you'll use rather than the spec sheet. If you want APRS, the TM-D710G is built for it, with the TNC and GPS integration in the same radio. If you're on a Fusion repeater network, the FTM-500D fits that. If your local activity is D-STAR, the ID-5100A makes more sense. If your area mostly runs analog FM, any of them works, so look at control head size, menu layout and whether the speaker is audible over road noise. For noise troubleshooting, a quiet simplex frequency or an unused part of the band is better than a busy repeater, because you can hear changes clearly. Start with the engine off and accessories on, then start the engine and rev it, then add loads like blower fans, wipers and charger adapters. Whatever changes the noise tells you where to look. I'd also add a note about cross-band repeat and your handheld: use a different band for each side, set the power level deliberately, and make sure the person holding the handheld knows how to turn it off. Leaving it running after you walk away from the vehicle is how you end up retransmitting things you didn't intend to.
-
Planning a first POTA activation: park references, the 10-QSO rule, spotting and logging checklist
For antennas, I'd go with the simplest setup that fits the park. A vertical on the car or a small tripod is easy and quick to set up in most places. A wire antenna can be better for performance but only if the park allows you to hang it and you can do so safely. Keep wires out of walkways, don't damage trees and take everything with you when you go. If you're running QRP, a clear frequency and a good spot matter more than almost anything. CW and digital modes can help a low-power signal, but the hunter base for SSB is large, so it depends on your skills and the band conditions. A spot comment with your mode and power level can also help hunters decide whether to call you. For two-fers, I'd check each reference on the official map or park list before you operate. The areas may overlap only partly, and the best place to set up may not be inside both boundaries. If you can't confirm the overlap, log only the park you're sure about. And because rules and award details can change, treat any summary, including the one above, as a starting point and check the current guidelines on the POTA website before your first trip.
-
Radio mods and upgrades: what actually improves performance, and where does a mod cross the line?
I would put "fix the noise first" at the top of the list, because it is cheaper than almost anything inside the radio. A new filter does not help if the noise is arriving through the antenna or the power lead. A quick test is to run the radio from a battery away from the other equipment. If the noise drops, you know the source is in your shack and not the receiver. For the power side, I would also stress fuse placement and wire gauge. People upgrade to a bigger battery and then connect it with thin wire and no fuse near the terminal. The battery can deliver far more current than the wire can safely handle, so a short in the cable is the real danger. A fuse close to the battery protects the wiring, which is the part most likely to cause a fire. On TCXOs and similar internal mods, check whether the stock radio is actually the problem. If an older radio drifts when warming up, a longer warm-up may be enough. If you are working on high bands or narrow digital modes, a TCXO is reasonable, but only if you can calibrate it afterwards. The fitted part will not be perfect without a reference.
-
WWFF activations 101: KFF references, the 44-QSO rule, logging, and doubling up with POTA
On the 44-QSO planning point: it helps to think in terms of QSOs per hour and band conditions rather than just "how long will I stay." A POTA-style run of 10 contacts can take a few minutes, but 44 usually means committing to at least an hour or two, depending on how well your spots land. Setting up on two bands, such as 40 m and 20 m, spreads the audience and gives you a fallback if one band closes or gets noisy. With a dual reference, it is worth saying both references at the start of each CQ cycle but keeping the exchange itself short. Spotting twice, once on the POTA site and once on a WWFF spotting channel or cluster, brings in different groups of hunters. Some people only watch one of them.
-
Building solid CW copy and sending: Farnsworth, paddles, filters and when to trust a decoder
On Farnsworth, the main thing is to keep the character speed high enough that you can't count elements. Many people use something around 18-20 WPM character speed and then tighten the spacing in small steps as copying becomes easy. If you drop the character speed to match a slow overall speed, you lose the point of the method. A good test is whether you can write down the letter as you hear it, rather than hear a pattern and then work out what it was. For paddles, adjust before you blame technique. Set the contact gap just wide enough that you don't get accidental double contacts, and the spring tension just firm enough to release cleanly. Then choose a keyer mode and stick with it for a few weeks. Switching between Mode A and Mode B every session is a good way to never build a reliable muscle memory.
-
Measure First, Rebuild Second: A Practical Workflow for Fixing a Troublesome Antenna System
When an antenna system underperforms, the usual reaction is to build a different antenna. Sometimes that's right. Often the real culprit is a feed line acting as part of the radiator, a poor ground, a noisy neighbor (electrically speaking), or a tuning problem you could have found in ten minutes with a NanoVNA. Here is a repeatable workflow for working out what's wrong before you cut any wire. Step 1: Change one thing at a time and write it down This is the least glamorous advice and the most useful. Keep a simple log: date, band, antenna configuration, what you changed, and what you measured. Noise levels, SWR curves, and received signal reports all vary with time of day and conditions, so a single before-and-after comparison can mislead you. If you change a balun, a feed line, and a radial field in one afternoon, you'll never know which one helped. Step 2: Use SWR for what it is SWR tells you how well the load matches the line's characteristic impedance. It does not tell you how efficient the antenna is. A dummy load has a perfect SWR and radiates nothing. A short vertical over a sparse ground system can show a pleasant 1.3:1 while a good share of your power heats the soil. Useful things SWR can reveal: Resonant frequency: where the dip lands relative to where you want to operate. Bandwidth: a wide, shallow dip can hint at losses; a narrow, deep one usually indicates a cleaner resonance. Changes over time: if the curve drifts after rain, wind, or a season change, something is moving, corroding, or absorbing moisture. Step 3: Get the most from a NanoVNA A NanoVNA is excellent for antenna work, but only if you measure carefully. Calibrate at the right place. Perform the open/short/load calibration over the frequency range you're sweeping, at the connector where you'll attach the cable under test. Recalibrate if you change the sweep range significantly. Know your measurement plane. Measuring at the end of a long coax shows the impedance transformed by the line, not the antenna's own feedpoint impedance. With lossy coax the SWR at the shack end looks better than at the antenna, which can hide a bad match. Look beyond SWR. Check the Smith chart or the R and X readouts. Resonance is where reactance crosses zero. If X is zero at a different frequency from your SWR minimum, the feed line or transformer is playing a role. Keep cables and your body clear. Dangling coax and nearby metal can shift readings, especially on small or electrically short antennas. Step 4: Suspect common-mode current If SWR changes when you move the coax, touch the cable, or add a few feet of line, you may have common-mode current on the shield. That current turns the outside of the coax into part of the antenna. Symptoms include RF in the shack, odd SWR behavior, a distorted pattern, and increased noise pickup on receive. Common-mode chokes address this by presenting high impedance to current flowing on the outside of the cable while leaving the signal inside alone. Practical points: Place the choke at the feedpoint of the antenna first. A second one where the cable enters the building often helps with noise. Choke performance depends on the ferrite mix, the number of turns, and the frequency. Many builders use mix 31 for lower HF and mix 43 for higher HF, but check the datasheet for your cores and measure if you can. Winding turns closely on a core raises impedance at lower frequencies, while stray capacitance between turns limits it at higher ones. Test the effect, don't assume it. Compare noise level and SWR stability before and after. Step 5: End-fed halfwave builds and their counterpoise An end-fed halfwave (EFHW) is popular because it needs only one high support and one feed point. A matching transformer, commonly in the 49:1 to 64:1 range, converts the very high impedance at the wire's end to something coax can handle. A few cautions: An EFHW still needs something to push against. With no deliberate counterpoise, the coax shield often takes that role, producing the common-mode problems above. A short counterpoise wire and a choke can help. The transformer's core can heat at higher power. Check for warmth during testing, and size the core accordingly. Use the NanoVNA to check the sweep on each band the antenna is intended for. Harmonically related resonances don't always land exactly where you'd hope, especially with nearby objects or sloping wire. Step 6: Don't neglect the ground system For vertical antennas, the ground system is half the antenna. For a ground-mounted quarter-wave vertical, many shorter radials generally beat a handful of long ones, because the goal is lowering ground loss near the base. Raised, resonant radials work differently: a few well-placed radials can do much of the job, since they sit above lossy soil. Either way, avoid judging the system by SWR alone. Try comparing received signal strength against a reference antenna, then add radials in stages and see how much each batch improves things. You'll usually see diminishing returns, which tells you when to stop. Step 7: Hunt noise methodically If your noise floor is high, find out whether it's coming from inside or outside your house. Run the radio on battery power, with a portable receiver if possible. Turn off breakers one at a time and watch the noise. Remember that switching supplies, LED lighting, chargers, and solar equipment are common offenders. If the noise persists with the whole house off, it may be coming from outside, such as a neighbor or a power line. A directional approach, such as a handheld AM receiver or a small loop, can help you home in on the source. Check whether adding a choke on the feed line, or moving the antenna farther from the house, reduces it. Noise measured on a receiver should be compared at the same time of day, on the same band, with the same settings, such as AGC, preamp, and filters. Step 8: Lightning protection is about reducing risk No hobby setup can be made immune to a direct strike. What you can do is reduce damage from nearby strikes and induced surges: Disconnect and move coax away from equipment when storms approach, if safe to do so. Bond all station grounds and the entry-point ground together, so equipment doesn't develop dangerous voltage differences. Use a single-point ground or entry panel where cables come in, with surge protection that suits your cable types. Follow local electrical codes and consult a qualified electrician for the building's grounding. Never rely on a hastily driven rod alone. Documenting before and after When you finish a change, record: SWR sweep screenshots or saved files for each band. Noise floor readings on several bands at the same time of day. A/B comparisons against a second antenna, if you have one. Photos and sketches of the layout, including wire lengths and choke positions. Even if results are modest, the record helps you understand what each modification did and prevents repeating experiments. The best antenna improvements often come from small, measurable fixes: a choke at the right place, ten more radials, a corroded connector replaced, or a noisy charger unplugged. Measure first, then decide whether it's time to build.
-
Phonetics on the air: ITU/NATO alphabet vs. "creative" ham phonetics, and what to do when conditions are bad
On creative phonetics: the problem is that the improvised words are unpredictable to the listener. If you say "Lima" or "Lincoln" for L, a listener expecting the standard word has to decide on the spot whether you mean the letter or a place. A mixed set also fails more often when the receiving operator is writing down a callsign letter by letter and can't guess the pattern. For callsigns, use the standard alphabet and say it at a steady pace, not as fast as you can. If the other station asks for a repeat, say it again identically first. Only change words if a specific letter keeps being misheard, and then pick a clearly different word. Typical trouble pairs are B/D/P/T, F/S/X, and M/N. The standard words already separate those reasonably (Bravo, Delta, Papa, Tango; Foxtrot, Sierra, X-ray; Mike, November), but in heavy noise you may still need repeats. Giving your call as "W1ABC, Whiskey One Alpha Bravo Charlie" is better than rushing the phonetics. For names and locations, signal the change in mode with a procedure phrase like "I spell" before the letters, and "word after" or "figures" where it helps. Spell only the unusual part. Say the whole word first, then the spelling, then the word again if conditions are poor. For a place name, add the state, province or country, since many names repeat. For grid squares, use the same rule: a grid such as FN31 is read Foxtrot November three one, not just "F N thirty-one". When conditions are bad, a few things matter more than the exact word list: speak slowly, keep the same wording each time, say the callsign more than once, and don't run things together. In a pileup, giving your callsign once clearly and then listening beats repeating it quickly three times. If the problem is fading or QRM, brief bursts of information repeated twice generally work better than a long single transmission. Prosigns are mostly a CW matter: AR (end of message), SK (end of contact), BT (break), K or KN (go ahead). On voice you replace them with procedure words: "over", "out", "break", "say again". One habit worth dropping is "over and out", because over means you expect a reply and out means you don't. For nets and emergency traffic, the difference is discipline. On a net, follow net control's instructions, give the callsign phonetically at check-in, and keep transmissions short. Many nets ask for only the suffix (the last letters) in phonetics, so listen to how the net control asks. For emergency or priority traffic, say what the precedence is and use standard words. Messages in formal formats, such as radiograms, are read with spelled-out numbers and phonetic spelling of anything unclear, and the receiving operator may read the text back for confirmation. If it is a real life-threatening emergency and you're on a frequency that is in use, the usual phrases are "emergency" or "priority" (and "Mayday" or "Pan-pan" in maritime and aviation contexts) followed by your callsign, location and the nature of the problem. Follow any local emergency plan or net procedure.
-
Breaking pileups on rare DX: split, timing and tailending, and what changes for Clipperton or Bouvet-class targets
A few things to add on the rig side, because a lot of failed calls are equipment problems rather than technique problems. First, check your receive filter width. On CW a narrow filter helps you hear the DX's pattern, but if it is too narrow you will miss the stations calling around him, which are the ones that tell you where he is listening. A slightly wider setting while you work out the pattern, then a narrower one once you are in the window, is a reasonable approach. Second, check your transmit offset against the DX's actual zero beat. If your rig has RIT or XIT, do not leave them on from a previous QSO. Finally, use the rig's memory or a quick-swap function so you can jump between the DX's frequency and your call frequency without retuning. On the digital side, if the DXpedition runs FT8 in Fox and Hound mode, follow the instructions carefully. As a Hound you generally call above the Fox's frequency range and let the software handle the exchange. Calling in the Fox's own range or sending repeated calls after you have been answered causes problems for him and for everyone else. Read the DXpedition's operating notes before the start; they usually say which modes and bands are planned, and sometimes list the frequencies. One more point on the cluster: RBN and skimmer-based spots are good for checking whether the DX is audible at all and where, but they do not tell you whether you are in his pileup window. Use them for "is he there?", then listen.
-
Planning a 24-hour EMCOMM field station: power budget, generator vs LiFePO4, noise control and a setup/teardown order
A few points on the battery and antenna side. First, LiFePO4 holds close to a flat voltage curve and then drops sharply near empty, so a voltage meter won't warn you well. Use a shunt-based battery monitor if you can, and know what your BMS does at its low-voltage cutoff. If it just disconnects, your station goes dark suddenly, so set an operational threshold well above that, say at a state of charge you define in the plan. Check each radio against the pack's actual voltage range, since a fully charged 12.8 V nominal pack sits near 13.3 to 14 V and some gear is more sensitive to the top end than the bottom. Cold matters too. Many LiFePO4 cells shouldn't be charged below freezing unless the pack has low-temperature charge protection. If your solar or generator charging happens on a cold morning, confirm the specification for your battery first. Solar panels, for planning, usually deliver well below their nameplate rating once you account for angle, haze and controller losses, so size them as a top-up, not as the main supply, unless you've done the math for a real number of sun hours. On the mast, the main rules are about the fall zone: keep the whole mast and antenna well clear of power lines, with a distance greater than the full height of the mast plus the wire span, and guy it for the expected wind rather than the forecast average. Stake guys visibly, or flag them, so people don't walk into them. For the teardown half of the checklist, I'd reverse the order: stop transmitting, shut down and disconnect radios, drop the antenna and mast, recover coax and guys, then power down the distribution, cool and pack the generator, and do a site sweep for stakes, cable ties and fuel residue. Add a final line to the list for photographing or documenting any gear that failed or misbehaved, so the next revision of the checklist improves.
-
Building a 100 W HF shack: how much does the radio matter versus power, tuner, filtering and bonding?
On the power supply: a 100 W HF rig on SSB or CW usually peaks around 20 A or a bit more at 13.8 V. A "30 A" supply is a reasonable choice, but check whether that is continuous or peak and whether voltage holds up under a keyed carrier. Digital modes and long CW dashes load it harder than voice does. Modern switching supplies can be quiet or terrible. If you hear a comb of birdies or a raised noise floor that changes when you unplug the supply, the supply is a suspect. Ferrites on the DC leads and a shorter run often help. A linear supply is the heavier, quieter option, but it is not the only way to a clean receiver. Voltage drop is often overlooked. Use an adequate wire gauge for the run, keep it short, and use properly crimped connectors (Powerpole-style or similar) rather than relying on the thin cable that ships with the radio for extension runs. If the rig shuts down or output sags on peaks, measure at the radio's connector while transmitting, not at the supply. For bonding, the safety side is the AC mains equipment ground, which is separate from "RF ground." A ground rod at the operating position does little for RF, and a long wire to it can become part of the antenna. The practical aim is to tie equipment chassis together with short, wide conductors (braid or strap) so there are no big potential differences between boxes. Add a common-mode choke on the coax at the shack entry or the feedpoint, depending on where the common-mode current is being picked up. Lightning protection is its own subject: entry-point bonding, surge protection and tie-in to the electrical service ground. Check your local electrical code, and consider a qualified electrician for anything touching the service panel.
-
Weak-signal digital station checklist: clock, audio levels, CAT, and what decode thresholds really tell you
One caution on thresholds: sensitivity is not the only thing that decides which mode to use. A mode that decodes at -28 dB is no use if the exchange takes so long that the path closes, or if the other end cannot run it. FT8 became the default because it is fast and tolerant, and the cost is a rigid message structure. JS8Call gives you free-form text, heartbeats and relaying, but its slower submodes take noticeably longer per message, and the decodes are only as good as your clock and audio. WSPR is not for contacts at all. Its value is propagation data: transmit a beacon, then check the reports on wsprnet.org and see where you were heard. For VHF and up, Q65 and MSK144 depend on matching the mode to the propagation. MSK144 works from short, fast bursts off meteor trails, so you need fast alternating periods and a patient operator. Q65 has submodes with different period lengths and tone spacings, and the letter at the end (A, B, C and so on) sets the tone spacing. Wider spacing tolerates the Doppler spread of EME and some scatter paths, at some cost in sensitivity. Choose the submode to match the path, not just the biggest number you can find. For the fldigi modes, think of them as a trade-off between speed and bandwidth. PSK31 is narrow at about 31 Hz and easy on the rig, but it has no forward error correction and suffers on a fading path. RTTY at 45.45 baud with 170 Hz shift is simple and robust enough for contesting. MFSK and Olivia add error correction and interleaving, so they can hold up when a signal is going in and out of the noise, and the cost is slower typing and a wider signal. Hellschreiber is different: it paints the characters on the screen and your eye does the decoding, which can be readable when software decoders give up. It is mostly a curiosity, but a useful one. Winlink is a different use case: message transfer through gateways rather than live chatting. VARA HF and VARA FM run on a sound card like the other modes. VARA is proprietary, and the unregistered version is rate-limited, so higher speeds need a license. Whatever the mode, listen before you transmit, and check your band plan and local rules, since the digital sub-bands and permitted bandwidths differ between countries.
-
Before the first on-air contact: how do you verify a homebrew QRP transmitter (Tuna Tin 2, Pixie, BITX or uBITX)?
One thing I'd add to the filter step is that you can test the low-pass filter on its own before it ever sees RF power. A NanoVNA-type instrument can plot S21 through the filter, so you can see the cutoff, the passband loss and how deep the stopband goes at the second and third harmonic. Make sure the filter is terminated sensibly, and never connect a transmitter to the VNA ports. Component tolerance matters more than people expect. Toroid turns spacing and capacitor values shift the cutoff, so a filter built exactly to a table can still be a bit off. If the passband is lossy or the cutoff sits too close to the operating frequency, adjust the toroid turns by spreading or squeezing them, or swap in a close-value capacitor, and re-sweep. For the keying check, a direct-conversion or crystal-controlled rig can sound very different on a second receiver than in the sidetone. Listen for chirp when the supply is shared between the oscillator and the amplifier, and consider a separate regulator for the oscillator. A few milliseconds of rise and fall time on the keyed stage often cleans up clicks without hurting readability.