Everything posted by Mod_Chad
-
Tightening up CW: paddle settings, Farnsworth, filters, QSK and decoders. What actually helped your copy and sending?
On the iambic question, it helps to test with specific letters. Send C and then K, and watch for a stray extra dit or dah at the end. If you get one, check whether it comes from releasing late or from the keyer mode. If you switch between modes A and B and one feels more natural, stick with it for a few weeks before judging. Muscle memory takes time to adapt, and hopping between settings can make everything feel wrong. For QSK, check the whole transmit chain before blaming the rig. Relays that click audibly at speed, or an amplifier that cannot switch fast enough, can leave the first dit weak or clipped. If you run an amp, confirm it supports the break-in rate you want and that the keying line timing is configured properly. Otherwise, a short semi break-in delay is the safer choice, since it avoids hot-switching stress and still lets you hear the band between words. As for filters, a good habit is to widen out when tuning and calling, then narrow once you have a station in the passband. In a crowded contest band, narrowing too far can make you miss someone calling slightly off frequency, so keep it a notch wider than the minimum if you can still hear cleanly.
-
Making SET and Field Day count: what do your exercises actually test, and what do the after-action reports say?
One thing that helps SET is making the scenario boring in the right way. Instead of an elaborate story, pick two or three measurable objectives, such as "pass ten formal messages between the EOC and three shelters" or "establish a backup path if the primary repeater is declared down." Then inject a failure partway through: the repeater goes away, the net control operator is "unavailable," or a served-agency contact changes the request. You learn far more from how people adapt than from how smoothly the planned part runs. For the AAR, I like separating observations from opinions. "Three of ten messages needed a second readback of the address" is something you can fix with training. "The net felt chaotic" is hard to act on. Ask people to write down specifics while they're fresh, then sort them into training issues, equipment issues, procedure issues and agency-coordination issues. Each category usually has a different owner.
-
Nets and special event stations: how do you find a good net, check in cleanly, and make the most of event certificates?
For special events, I would build a small routine rather than rely on memory. Write the callsign, dates, bands, and modes in a note, and put the log deadline on your calendar. Then keep your own log clean, since certificate applications usually ask for a callsign, date, time in UTC, band, and mode that match the event's own records. Time in UTC is the part people often get wrong. It is also worth knowing the difference between a QSL card, an electronic confirmation, and a certificate. A special event station may offer one, two, or all three, and they are claimed in different ways. Some groups use logging services such as LoTW or QRZ, others have their own request form, and some want an SASE for a paper QSL. The event's page is the authority. When the pileup is heavy, listen for how the operator is working it. Many special event stations take a quick exchange of callsigns and signal reports, and then move on. A long call or extra conversation makes it harder for others to get through. If you are chasing the certificate, make sure you have what the event needs, and then go back to listening for the next station. A net connects in a similar way, since many have their own certificates or awards for regular participation. It is worth asking the net manager what, if anything, is offered and how check-ins are counted.
-
Breaking a DXpedition pileup: split, timing, tailending and what actually gets you in the log
I'd add something on verification and etiquette, because those cause a lot of avoidable trouble. Always confirm the callsign and the QSL route from the official source before you start, particularly on a new or short-notice operation. Fake or mistaken spots do appear, and chasing a call that is not real wastes the band time that Clipperton or Bouvet type openings don't give you much of. On Club Log, I'd treat it as a planning and checking tool rather than a guarantee. Use the band-slot view to decide which band is your best bet first. If you work the DX, check the log search after the operator has uploaded, and give it time. Many expeditions upload in batches, so a missing QSO right after the contact doesn't mean you need to call again. If you do think you were not in the log, wait until there has been an update, and only then consider a repeat QSO. On the low bands, listen before you transmit for longer than you think you need to. A CW or SSB operator on 160 may be listening on a tight, specific frequency, and with the QRN and fading you can hear one half of the exchange and not the other. Knowing which stations he's actually answering is the best way to avoid calling blind. A good receive antenna lets you hear the callers and the DX's responses to them, which improves your timing more than adding transmit power. Finally, if the operator says "QRZ" or tells you to stand by, just stop. Nothing annoys a pileup, and the operator, more than someone who keeps calling after being told they are not the one being worked.
-
Scratch-building a 40 m wire dipole or vertical: wire, feedpoint, choke, supports, and checking it with a model and an analyzer
On the feed question, both work, and the choice depends on whether you want a single-band antenna or one that covers several bands. For a single-band 40 m dipole, coax with a 1:1 current balun or a choke at the feedpoint is the simplest setup. The goal of the choke is high common-mode impedance, so the outside of the coax shield doesn't become part of the antenna and radiate or pick up noise. Type 31 ferrite is a common choice for the lower HF bands. Roughly 8 to 12 turns of small coax through a large toroid, or a stack of clamp-on or bead cores over the cable, is a typical construction. A coil of coax with no ferrite can also work as a choke, but its useful bandwidth is narrower and it is better suited to higher frequencies than to 80 or 160 m. If you want multiband use from a single wire, open-wire or window line makes sense. Ladder line has low loss even when the SWR on it is high, which is why it pairs well with a dipole used on bands where it isn't resonant. The cost is that you need a tuner that can handle the resulting impedances, plus a balun or a balanced tuner at the shack end. Keep the line away from metal gutters and downspouts, and bring it away from the antenna at right angles for a distance. Some line lengths on certain bands give very awkward impedances at the tuner, so it is worth modelling the actual length rather than assuming any length will tune. One extra tip for measuring: when you check an antenna with an analyzer connected through coax, common-mode current on the shield can change the reading when you touch or move the cable. If the reading changes as you move your hand along the coax, that tells you the choke isn't doing enough.
-
Winlink over radio: choosing modes, setting up Winlink Express, and handling ICS-213 traffic
Start with how the pieces fit. Winlink Express is the Windows client. When you connect to an RMS gateway over RF, the gateway passes your traffic to the Winlink Common Message Servers (CMS) over the internet. A Telnet session in Winlink Express goes directly to the CMS over the internet with no radio involved. That's why Telnet is useful for first-time account checks, testing forms, and sending messages while you're still at home, but it doesn't prove your radio chain works. For the radio modes, think about what each one needs: Packet (1200 baud AFSK on VHF/UHF) can use a hardware TNC or a sound card with software such as Direwolf or Soundmodem. In Winlink Express you'll typically define the TNC type and port, or the KISS connection if you use software. VHF packet is simple and works well for local gateways, but it's slow and shares the channel with other users. VARA FM also uses the sound card, with the VARA modem running alongside Winlink Express. It's meant for VHF/UHF FM and is much faster than 1200 baud packet when the signal is solid. VARA is shareware: the unregistered version works but has a speed limit, and a license removes it. For a group, decide ahead of time who will register what. VARA HF is the same family for HF SSB. It's usually what you'll find on busy HF gateways because it's fast for the bandwidth it uses. Same licensing situation as VARA FM. ARDOP is a free alternative for HF with a sound card. It's often a good fallback if VARA licensing is an obstacle, and it's also available for P2P, but the available gateway list is generally smaller than VARA's, so check the channel list for your area. Pactor is the odd one out because it needs a dedicated hardware modem. Pactor 1 can be handled by some multimode controllers, but the higher Pactor levels need specific modems. Unless a member already owns one, most new groups skip it. On the sound card side, the usual HF setup is rig in USB (or the data mode your radio provides, often USB-D or DATA-USB), all audio processing off (compression, equalizer, noise reduction), and the transmit audio set so the ALC barely moves. If you're seeing steady ALC action, you're overdriving and spreading splatter. Gateway operators will notice. For PTT, use CAT control if your rig supports it reliably, or serial RTS/DTR or a dedicated interface's PTT line. VOX works in a pinch but can cause clipped starts. On gateway locations: the Winlink Express channel selection window pulls from a list that has to be refreshed over the internet. Update it before you go anywhere, because the cached copy is only as good as your last update. For HF, the window can also give you a propagation estimate, but treat that as a hint and not a promise. For VHF/UHF, the list gives you stations near your grid or location, but check the station's actual coverage with a test connection. Don't assume a listed gateway is up on any given day.
-
Which radio mods are actually worth doing, and where do MARS/CAP and legal limits fit in?
I'd add that power and cooling are where 'safe mod' advice gets neglected. If you swap in a different battery chemistry, check that the radio's operating voltage range, the charger and the protection circuitry all agree. A pack with no protection board, or a charger set for a different chemistry, is a fire risk, not an upgrade. For mobile and base rigs, put a fuse near the battery end of the power run, use wire gauge appropriate to the current and length, and use polarized connectors like Powerpoles so nobody can reverse polarity. Voltage drop under transmit is a common cause of distorted audio and reduced output, and it's easy to blame the radio instead. On fans: they help duty cycle on high-power rigs, but a cheap brushless fan can add its own noise to the receiver. Use a thermostatic or voltage-controlled fan if you can, filter its supply lead, and don't block the radio's own vents or airflow path. Test receive with the fan running, not just with it off. On firmware and legality: save your existing configuration, use the exact file for your hardware revision, and keep the radio on stable power during the flash. Third-party firmware can add features, but it may also remove limits that were there for compliance reasons, such as power or band restrictions. That shifts responsibility to you. After any transmit-related change, test into a dummy load and, if you can, check the output for harmonics or splatter. The unlock is easy. Proving the radio is still clean on air is the harder part. For MARS and CAP, I'd treat the radio as one part of the authorization, not the whole of it. Get the program's written guidance on equipment and frequency use. Don't assume that because a radio can be programmed to a frequency, it's approved for use there.
-
VHF/UHF antenna choices: gain, pattern, feedline and connectors, and where each trade-off bites
One thing to add on satellites: horizontal and vertical linear antennas can work for FM birds, but fades are common as the satellite moves, so people often try crossed yagis or switch polarization between passes. For a handheld yagi setup, aiming accuracy and body position matter as much as the gain figure. Also remember that the uplink and downlink are on different bands, so the antenna needs to work on both 2 m and 70 cm, and the feedline loss is different on each. On the mobile side, a quarter-wave on the center of a steel roof is a very dependable baseline. If someone is comparing it to a 5/8 whip, it would be useful to test both in the same position and judge them with signal reports or field-strength comparisons rather than relying on SWR alone. SWR only says how well the antenna matches the radio, not how well it radiates.
-
No TX, no RX, or both? A triage order for dead rigs (and where it usually goes wrong)
On the intermittent faults: a plastic stick or a chopstick is cheaper than most test gear. Gently pressing on boards, connectors and ribbon cables while the rig is running often shows a cracked joint or a flaky connector. Contact cleaner can help with dirty switches, rotary contacts and pots, but use it sparingly. Soaking a board can leave residue, and some old pots do not enjoy being flooded. Isopropyl alcohol and a soft brush are enough for most board and connector cleaning. For capacitors, I'd measure before replacing. An ESR meter, or a meter with in-circuit ESR capability, makes the job much more targeted. Switching supplies and DC-DC converters are the usual places where tired electrolytics cause noise, hum, hash on receive or unreliable start-up. When replacing, match capacitance, use equal or higher voltage rating, observe polarity, and choose low-ESR, suitable-temperature parts where the circuit needs them. If an old SMD electrolytic has leaked, clean the residue thoroughly and inspect the traces, because the electrolyte can eat copper and cause faults that remain after the new part is fitted. Finally, don't touch alignment unless there is a reason. If a fault is not clearly an alignment issue, you can make things worse. When you do align, use the service manual procedure with a dummy load, a power meter, and a signal generator, or at least a counter and a known-good reference. A scope is useful for seeing oscillator amplitude, audio distortion, ripple on rails and switching noise, which a multimeter will average out and hide.
-
Hamfest season planning: what to bring, how to buy used gear, and which club events are worth your time
On buying used gear, a lot of mistakes come from skipping the basics. A few things that are easy to check on the spot: Ask the seller if you can power it up. Most will agree if you have your own supply or they have one handy. Check that the display is complete with no missing segments, that the knobs and switches don't crackle, and that the receiver hears something on a few bands or at least through a known antenna. For a transceiver, keying into a dummy load and watching for output on a wattmeter tells you far more than the seller's word does. Handhelds need special attention to the battery pack. Old Li-ion and NiMH packs lose capacity with age, so a radio that looks fine may only last an hour. Look for corrosion in the battery compartment, a swollen pack or a cracked case. If the price assumes a good battery, factor in the cost of a replacement. Also look at the small things: missing mic connectors, broken tabs on coax connectors, a bent or damaged antenna jack, and a smell of smoke or mildew. Many items are sold as-is, so ask who the original owner was, whether it was ever modified or repaired, and whether the manual or accessories come with it. Finally, set a limit before you go, carry cash in small bills, and bring a wagon or a folding cart. Heavy items like linear amplifiers, tube gear and big power supplies add up quickly across a big flea market.
-
Checking a homebrew QRP transmitter for harmonics with basic bench gear
On the filter side, the calculated values in the schematic are only the starting point. Real toroids don't land exactly on the value you wound, so the cutoff can shift. Start from the core's AL value (L = AL × N²), wind to the calculated inductance, and then measure the filter. Powdered iron cores such as the T37-6 or T50-6 families are common in QRP filters, and the exact core mix matters, so match the part number to the design. For the capacitors, use C0G/NP0 ceramics or silver mica. Cheap general-purpose ceramic types can change value with voltage and temperature, and that shows up in filter response. Also look at layout: leave a little room between the toroids so they don't couple to each other, and keep the input and output leads of the filter physically separated, otherwise some of the signal bypasses the filter and your stopband attenuation is much worse than the design predicts. For multiband rigs such as the BITX or uBITX family, the filtering is relay-switched or band-selected, so you should measure each band separately. The upper bands tend to be the ones where a filter that looks fine at the lower frequencies is least effective, because the harmonic spacing and the transmitter's spurious content are different there.
-
Weak-signal digital setups: where do your decode problems really come from? (time sync, audio levels, CAT, and mode choice)
I'd separate "they hear me" from "I hear them," because the two failures point to different parts of the chain. If a spotting network shows you being received but you decode nothing, look at the receive side: audio level, a wrong sound device selected after a USB re-enumeration, or a clock that is off. If you decode fine but nobody replies, check transmit: ALC, a mismatched split setting, or a rig that is changing its own bandwidth or processing in data mode. One thing that is easy to miss is rig settings that are fine for SSB but wrong for data. Speech compression, noise reduction, and narrow DSP filters can all change how a digital signal looks. Many operators use the rig's data mode (USB-D or similar) with processing turned off and a wide enough filter that the whole decode window passes through. Also, make sure the TX audio is not being altered by a driver feature on the computer. For clock checks, the DT column is more useful than people think. If every station you decode is showing around the same DT offset, that is your clock. If only one station is off, it is theirs.
-
Newly licensed? Share your intro, first radio, first QSO, and the mistakes you'd tell others to skip
On the "what to buy first" question, I'd work backward from what you can actually reach. Before you spend anything, look up the repeaters near you in a directory such as RepeaterBook, or ask a local club. Check which bands they're on (2 meters and 70 cm are the usual ones in many places), whether they need a CTCSS/PL tone, and what the offset is. If the local activity is mostly on 2 meters, you don't need a fancy multiband radio. A few practical points for a first HT: - Budget radios can get you on the air, but compare them on more than price. Look at receiver quality, how easy it is to program, and whether it comes with a decent antenna. - Plan to program it with software like CHIRP, or at least learn the menu properly. Entering offset, tone, and mode wrong is a common reason a new ham can hear a repeater but can't get into it. - The rubber duck antenna that ships with most HTs is a compromise. A better antenna, or a mag-mount on a car roof, can make a big difference before you upgrade the radio itself. - An extra battery or a way to run from 12 V is handy for club events and public service nets. If you're leaning toward HF, think about the antenna first. A modest radio with a decent wire antenna that fits your yard usually beats a great radio on a poor antenna. Also make sure your power supply and coax can handle the job, since cheap cable loses a lot of signal at higher frequencies. And ask a club member before you buy. Someone local may have a spare radio to lend, or may know what's about to be sold at the next swap meet.
-
Getting started with WWFF: KFF references, the 44-QSO line, and combining with POTA
On the activation threshold: WWFF's commonly cited minimum is 44 QSOs for an activation to count, which is much higher than POTA's 10 QSOs in a UTC day. Check the current rules on whether QSOs can be accumulated across more than one session or day, because that affects how you plan a short outing. Also note that the two programs define their qualifying criteria independently, so don't assume one program's day-boundary or logging conventions apply to the other. On the logger side, WWFF has its own log submission and checking process, and it expects the reference in a consistent format. Before an outing, make sure your logging software can store your own reference (the one you're activating) as well as the hunter's reference when you're hunting. Recent ADIF versions have dedicated fields for park and flora/fauna references, but support varies between loggers, so export a small test file and look at it before you rely on it. Fixing a typo in a KFF number is far easier right after the trip than weeks later. For hunters, the useful habit is to log the activator's reference exactly as they send it, and confirm it against the official list if you're unsure. Similar numbers in neighbouring areas are an easy source of bad logs.
-
Technician to General: how would you split study time across the 35 Element 3 questions?
I'd split the study time by how well you already know each topic, not evenly. A rough order that works for many Technicians: Week 1: Rules, operating practices and the band plan. These are the most memorization-friendly. The topics include station identification, control operators, power limits, third-party traffic, the common Q signals, and the 60 m and 30 m special rules. Practice questions with the explanations turned on are more useful here than reading the rulebook cover to cover. Week 2: Propagation and antennas. Think in terms of cause and effect. The D layer absorbs lower HF frequencies during the day, and that absorption fades after sunset, which is why 160 and 80 m open up at night. The MUF is the highest frequency that will be refracted back for a given path. Higher solar activity generally helps the higher bands. Sporadic E and gray-line propagation each have a handful of questions. For antennas, know the half-wave dipole length formula (about 468 divided by the frequency in MHz gives feet), what velocity factor does to coax length, what a balun or unun is for, what SWR does and doesn't tell you, and the basic traits of a Yagi, a vertical with radials, and an end-fed wire. Week 3: Electrical principles and digital modes. Digital mode questions are mostly identification: FT8, PSK31, RTTY, Winlink, Pactor, how bandwidth relates to mode, and why those modes live in the CW/data segments. Spend the extra time on the electrical questions you got wrong earlier. Week 4: Full 35-question practice exams until you consistently score comfortably above the 26-correct line. Don't rely on exactly one pool run-through. Take them from at least two sources, and make sure the practice material matches the question pool currently in effect, because pools are revised on a multi-year cycle. Your VE team or the NCVEC can confirm which one applies. Once you pass, then look at vanity calls. Only decide that after you know which call sign group you'd be eligible for.
-
Planning a 100 W HF shack: rig choice, power, tuner placement, bonding and filtering
On the rig question, it helps to sort the radios by architecture and use case instead of trying to rank them. The IC-7300 uses a direct-sampling SDR design, and the IC-7610 builds on that with two receivers and two ADCs, which is the real draw for split-band listening and diversity. The TS-890S and K3S are traditional down-conversion superhets with selectable roofing filters, which is why they come up so often in crowded-band and contest discussions. The FTDX10 sits in between with a hybrid design. The FT-991A adds VHF/UHF coverage in a compact radio, so it fits a mixed-band station where HF performance is not the only priority. The G90 and KX3 are lower-power radios with different aims, a small portable station versus a compact 5 to 10 W QRP rig, so they shouldn't be judged on the same terms as the 100 W radios. For the power supply, a 100 W radio typically needs a 13.8 V source rated around 20 to 25 A. A nominally 30 A supply gives useful headroom. The thing people overlook is voltage drop in the DC cable. A long or thin run can pull the voltage down during transmit peaks and cause distortion or reduced output. Use a heavy-gauge cable, keep it short, fuse the positive lead close to the source, and follow the radio manual for the fuse rating. Switching supplies can radiate hash on HF. If you hear noise that changes when you unplug the supply, try ferrite chokes on the DC and AC leads, or try a different supply or a battery as a test. A linear supply is heavier but quieter in most cases. Test before you buy, because individual units vary.
-
Contest + digital logging workflow: keeping N1MM Logger+, WSJT-X and Log4OM in sync without duplicate or rejected QSOs
Keeping the contest log separate has the clearest audit trail. The contest program holds the log that gets submitted, and the master log only receives an ADIF export once you're done. That lets you fix typos, resolve dupes and double-check the exchange before the QSOs spread to LoTW, QRZ and Club Log. One practical point on WSJT-X: it can send logged QSOs by UDP to programs that support it, and it also writes its own ADIF file. Decide which one is the source of truth. If you use both the UDP path and a later import of wsjtx_log.adi into the same logger, you'll create duplicates unless the importer matches on call, band, mode and time within a tolerance. Many people use the UDP path only for live logging and keep the .adi file as backup. Also check time handling. All logs should be UTC, and the PC clock must be properly synchronized for FT8 anyway. A few minutes of drift will cause timestamps that don't match the other station's log, which can hurt LoTW matches.
-
Stuck between 10 and 15 wpm: what actually moves the needle on the way to 20?
On the decoding question: a software decoder can be useful for checking afterward, but it works against you as a crutch while you're learning. If the screen is filling in letters, your brain has little reason to build the sound-to-character link, and decoders tend to fall apart exactly when copy is hard (QSB, QRM, a fist with uneven spacing). They are also less reliable than a trained ear on weak or noisy signals. A more useful way to use software is as a coach. Generate your own practice text, play it back at your target speed, then compare what you wrote to the source file. That gives you error feedback without depending on a decoder for live copy. Programs like Morse Elmer, LCWO.net and similar trainers let you set character speed, effective speed and tone, and it is worth checking what each offers before settling on one. For a first on-air experience, a slow CW net or a friendly ragchew at a speed you can handle is usually a better step than a big contest. Nets run a predictable script (check-ins, traffic, sign-off), which makes them forgiving. Many operators will happily slow down if you tell them with a short "QRS PSE".
-
Nets and special event stations: how do you pick what to check into, and what makes a good net control?
For checking in, the main rule is to wait for the NCS to ask for check-ins, then give your callsign once, clearly, in phonetics, and stop. Don't pile on extra information unless the net format asks for it. Most nets state their format at the opening, so listening for a full cycle first will tell you whether they want name and location, a comment, or just the call. If you have traffic or are a mobile station on the move, say so as part of the check-in so the NCS can sequence you. Emergency or priority traffic is the one case where you break the order, and you do it with the correct procedure word, not just by talking. On the net control side, I'd add that a good NCS keeps a steady rhythm. Say the net name and frequency at regular intervals so listeners arriving mid-net know where they are. Repeat the list or the order when the band is noisy. And keep it from becoming a monologue. If you're hearing weak stations, ask a stronger station to relay rather than making everyone wait while you chase one call.
-
How do you keep up with ham radio news without chasing every rumor? Rigs, firmware, band openings and club updates
My filter for new gear is to wait for independent measurements. Sherwood-style receiver tables and ARRL Lab reviews, where they exist for a given radio, tell you far more than a feature list does. Two radios can both claim to be 100 W with a spectrum scope and still behave very differently when 20 m is packed during a contest weekend. A scope is nice, but strong-signal performance and clean transmit audio are what you live with. For antennas I'm skeptical of any compact multiband design that doesn't say where the losses are. If a short vertical or loaded wire claims broad coverage, ask about efficiency, not just SWR. A low SWR into a dummy load is also a low SWR, so it proves nothing about radiation. On firmware, I'd add that it's worth waiting a little after a major release. If a version breaks something, user reports usually surface within a few days, and you can read them before you flash.
-
Ghost signals and a lumpy noise floor on an SDR: overload, gain staging and antenna choice
I'd begin with the overload test, because it saves time. Put a step attenuator, or software gain reduction, in line and watch the suspicious signal. A real signal drops by roughly the amount you add. An intermodulation product usually drops faster, often by about double or triple the change, depending on the order of the product. That one test separates "weak but real" from "produced by the front end" without needing any theory. On the upconverter question: for HF on an RTL-SDR, an upconverter lets the tuner work in its normal VHF range, at the cost of an extra oscillator and mixer that can add spurs and its own images. The reported frequency is also offset by the local oscillator, so you must set the shift in the software (SDR#, HDSDR and others support this) or the dial will be wrong. Direct sampling on some RTL dongles avoids the converter, but the 8-bit ADC and the lack of selectivity mean strong shortwave broadcasters can swamp it, so a bandpass filter is worth adding. A receiver with real HF coverage, like an Airspy HF+ or an SDRplay RSP, skips that whole class of problem.
-
50 ft lot, HOA, 100 W: EFHW, OCFD, or ladder-line doublet for 80–10 m?
I would also add a vertical to the shortlist, but only if the radial situation is realistic. A vertical over poor or limited ground can lose a big share of power in the ground system. A few resonant elevated radials usually beat a handful of short wires lying on the lawn, but it is still a compromise. A short loaded vertical on a mast is even more dependent on loss in the loading coil and ground. On the plus side, a vertical often hears less man-made noise than a low horizontal wire near the house, depending on the local noise source. It can be a very good low-angle DX antenna, but it can also be a very quiet way to lose signal. As for what to measure: SWR alone is not enough. Use a modeling program such as 4nec2 or EZNEC with a realistic ground and the real height, and compare patterns. Then test on the air. WSPR or reverse beacon spots can show relative performance between two antennas on the same band at the same time of day, with the caveat that propagation changes. Check for common-mode current by touching the coax or the rig chassis at the highest-power band. If you feel RF burn or see SWR jump when you move the coax, the antenna system needs a better choke. On coax loss, check the manufacturer's attenuation table for your cable at 28 MHz and 3.5 MHz and apply it to your real run length. Loss is manageable on a short run at low SWR, but gets worse as SWR rises or the run lengthens. That is one reason ladder line to a tuner at the radio can be a good approach when SWR is high on several bands. For a magnetic loop, it is fine for an apartment or a spot with no other options, but remember it is high-Q and narrow. You retune when you change frequency by even a small amount, and efficiency depends heavily on conductor size, joint resistance and the capacitor. It is a legitimate stealth antenna, and the noise rejection can be a real benefit, but low bands will be a challenge.
-
Keeper rigs: what makes a radio worth holding onto, boat anchor or modern?
I think both camps are right, and a lot of operators end up with a mix. A modern SDR-style radio is hard to beat for day-to-day flexibility, especially for digital modes and crowded band conditions. But an older radio can be great as a second rig for casual listening or as a project. A fair point against the "modern is boring" argument is that the hobby has always had different ways in. Some people love building and restoring, others love operating, and plenty enjoy both. A shack tour discussion is a good place to see that, because the setups are rarely just about specs. They show what the operator likes to do. One thing I would add to the original questions: how do you handle the shack itself? Cable management, grounding, and keeping RF out of the audio gear matter as much as which radio is on the desk, and they are often overlooked in gear arguments.
-
How do you check band conditions before you chase DX? SFI, K index, MUF, beacons and WSPR compared
Don't forget that HF isn't the whole story. Sporadic E is largely decoupled from the sunspot cycle. In the Northern Hemisphere it is most common in the early summer months, with a smaller peak around midwinter. It can open 10m and 6m, and sometimes 2m, over single-hop distances of roughly 1,000 to 2,000 km. SFI and K are poor predictors, so spotting networks and beacons on 28 and 50 MHz are your best early warning. Tropospheric ducting is a different mechanism entirely. It depends on temperature inversions and stable high-pressure weather, and it helps VHF and UHF and above. Weather charts and refractivity forecasts are more useful there than solar numbers, and long overwater paths are classic cases. At the other extreme is NVIS, which is about short-range coverage. Signals leave at high angles and return within a few hundred kilometers, so what matters is the critical frequency of the F layer rather than the MUF for a long path. That is why 80m and 40m are typical NVIS bands, with the choice shifting between night and day. A low horizontal antenna is often better for this than a low-angle DX antenna. The point is that the best check depends on what you're trying to work: beacons for DX, local reports for NVIS, weather data for tropo.
-
Building a contest calendar for the year: which majors fit your station, and what to check before each one
For a 100 W station with a wire, I'd put the "serial number only" events near the top. CQ WPX and similar contests keep the exchange simple, so you can concentrate on finding a clear frequency, calling efficiently and getting used to your logger. Sweepstakes is a great event, but the precedence/check/section exchange takes some practice. Spend a few minutes in the logger's practice or simulator mode if it has one. Whichever one you pick, set your power category correctly and decide in advance whether you'll run (call CQ) or search and pounce. With a modest signal, search and pounce usually gets more contacts in the log early on, and you can try calling CQ once you're comfortable.