Everything posted by Mod_Nancy
-
Building a first field kit: EFHW or linked dipole, which pole, and how much battery do you really need?
For a single-band-at-a-time style, the EFHW is hard to beat on setup time. Wire out, transformer on, a few meters of coax, done. The thing people tend to forget is that an EFHW has no true ground or counterpoise unless you provide one. The coax shield often ends up doing that job, which means common-mode current on the feedline. A common-mode choke at the radio end and a short counterpoise wire (a few meters, or about 0.05 wavelength on the lowest band) at the transformer often make the SWR more stable and the RF less likely to bite you or get into the rig. Reading SWR across the band before you fully commit to the layout saves a lot of fiddling. The linked dipole is nicer in one respect: you know what you have. Each band is a proper resonant dipole with a link in the right place, and it tolerates different heights and surroundings better. The cost is walking to the links, or lowering the pole, every time you change bands. If you plan to work one band for the whole outing, that cost vanishes. If you want to QSY quickly to chase contacts, a multiband EFHW or a tuner can be more practical. On the pole, whatever you use, guy it at the top section at least, even with light line. Fiberglass poles flex, and wind plus a wire load can pull the top sections out of alignment. A bit of tape or a hose clamp at the joints, if the pole design allows it, keeps the sections from slipping.
-
Baseline field station for a 12-hour EMCOMM shift: power, antennas, grounding and noise. What would you change?
I'd tighten the power section first. Putting the fuse at the battery is correct, but a lot of LiFePO4 packs have a BMS with a current limit. If a 100 W HF rig and a VHF mobile are both transmitting, plus an inverter running a laptop charger, check the continuous and surge ratings of the pack rather than assuming it will carry the load. A BMS trip in the middle of a net is a bad way to find out. Also check the low-temperature charging rules. Most LiFePO4 cells shouldn't be charged below freezing unless the pack has built-in protection, which matters if you plan to rely on solar or a generator-fed charger on a cold morning. On the generator, I'd treat it as an hourly-load question. Inverter generators are quiet but they are most efficient and least noisy at moderate load, so using the generator to recharge the battery through a proper charger in blocks can beat running it all shift. Keep it far enough away that its exhaust and noise are not at the tent, and put the CO alarm at head height inside where people sleep or rest. Don't run the generator under the canopy or backfeed the station from it.
-
Where exactly do I operate? Sorting out band plans, band edges, and calling frequencies from 160 m to 33 cm
For VHF/UHF the useful distinction is FM simplex versus weak-signal. The national FM simplex calling frequencies are 52.525 MHz on 6 m, 146.52 MHz on 2 m, 223.50 MHz on 1.25 m, and 446.000 MHz on 70 cm. You call there briefly, then move to another simplex frequency to talk. Don't hold a long conversation on the calling channel. Weak-signal work (CW and SSB, and digital modes like FT8) sits at the low end of each band. On 6 m, 50.125 MHz is the SSB calling frequency, with the DX window around 50.100–50.130, and 50.313 is the usual FT8 frequency. On 2 m, 144.200 is the SSB calling frequency, and the very bottom of the band is for CW. On 70 cm, 432.100 is the commonly used weak-signal calling frequency. Repeaters and FM live well away from these. That's the main point of the plan: if you tune a repeater-style FM signal into 144.200, you've wandered into someone else's territory. For 33 cm (902–928 MHz), the thing to remember is that it's a Region 2 allocation, and it's shared with non-amateur users, including unlicensed devices. Activity is sparse in many areas. The ARRL plan lists 902.100 MHz as a weak-signal calling frequency, but check the current plan for FM and repeater channels rather than relying on memory. Also note that parts of 70 cm have restrictions near the Canadian border (the Line A restriction), so check if you're in that area. On 60 m, the US doesn't give you a continuous band. It's five channels shared with other services, and you operate with a General, Advanced, or Extra license. The channel center frequencies are 5332, 5348, 5358.5, 5373, and 5405 kHz. In USB, the dial frequencies are 5330.5, 5346.5, 5357.0, 5371.5, and 5403.5 kHz. Voice must be USB, bandwidth is limited to about 2.8 kHz, and power is limited to 100 W ERP relative to a half-wave dipole. The rules also allow CW and some digital modes on these channels. Because it's a shared band, you're a secondary user and need to be careful about interference to the primary users. For international allocations, the ITU splits the world into Regions 1, 2, and 3, and the US is in Region 2. A few examples: 80 m is 3.5–3.8 MHz in Region 1 but 3.5–4.0 MHz in Region 2. 40 m is 7.0–7.2 MHz in Regions 1 and 3 but 7.0–7.3 MHz in Region 2. That's why US stations operating above 7.200 MHz can run into shortwave broadcasters in other regions. Also, 2 m is 144–148 MHz in Region 2 but 144–146 MHz in Regions 1 and 3. If you travel, you need to follow the local country's rules, not just the US chart. Check the licensing arrangement (reciprocal or CEPT, for example) for where you're going.
-
Technician to General: how should I study for Element 3, and what actually matters about HF sub-bands?
On the basics, you have it right. Element 3 is 35 questions and you need 26 correct (about 74%). You already hold credit for Element 2, so the General exam is the only one you take. The question pool is revised on a four-year cycle, so check the current pool's effective dates with the VE team or the ARRL/VEC page before you buy a book. A book for the wrong cycle is a common and avoidable mistake. On sub-bands: you don't need to memorize every kHz edge as a table, but you do need the structure. Each HF band has a CW/data segment at the bottom and a phone segment higher up, and General's phone segments start well above the bottom of the band. For example, on 20 m General phone starts at 14.225 MHz and runs to 14.350. Technicians get no phone there. On 10 m, the lower 300 kHz (28.000 to 28.300) is CW/data and phone is above that. Think "CW and data at the bottom, phone at the top, and General opens most of both." Then learn the oddballs: 30 m is CW and data only with a 200 W PEP limit, and 60 m is channelized rather than a continuous band. A study order that tends to work for Technicians: Week 1: Rules and privileges (the band plan material). Make your own one-page chart and redraw it from memory until you can do it without peeking. Week 2: Operating practices and digital modes. These sections are mostly vocabulary and procedure, so they give the fastest score gains. Weeks 3 and 4: Electrical principles, components, and antennas and feed lines. Work the math by hand a few times: Ohm's law, power, and the dB rules of thumb (3 dB is about 2x power, 6 dB about 4x, 10 dB is 10x). Last 1 to 2 weeks: Timed practice exams. Don't just count the score. For each miss, write down why the right answer is right. If you're consistently at 85% or better on random practice exams, you have a safety margin over the 74% pass line.
-
EME by band: what 2 m, 70 cm, 23 cm and 10 GHz moonbounce really demand, and how JT65/Q65, Faraday and libration change the plan
Picking up the microwave side, because the problems change character there. Once you go above 1296 MHz, Faraday goes away but libration spread takes over. The Moon's rocking motion spreads the echo in Doppler, and the spread scales roughly with frequency: a fraction of a hertz on 2 m, around a hertz on 23 cm, and tens of hertz at 10 GHz. That means the usual JT65 tone spacing can smear the signal, which is why wider spacing (JT65C, or the higher Q65 letters) is used. It also makes the echo sound rough and fade quickly, so a long decode period with fast fading is common. Libration spread is also not constant over the month, which is another reason to look at the spread figure in WSJT-X before a sked. Doppler shift is not small either. It is in the hundreds of hertz at 144 MHz, several kilohertz at 1296 MHz, and tens of kilohertz at 10 GHz. Stable references and software Doppler correction are routine. On the 23 cm band and up, the usual convention for circular polarisation is to transmit RHCP and receive LHCP, because reflection flips the sense. Confirm that with your partner rather than assuming it. Tracking accuracy is the other microwave catch. A 3 m dish at 1296 MHz has a beamwidth of roughly 5 degrees, so slight pointing error costs little. At 10 GHz the beam is well under a degree and about the size of the Moon. A flexible mount or a slow encoder will cost you decibels you cannot recover from the amplifier. Moon-noise and Sun-noise measurements are the practical way to detect that your pointing model is off. For sked planning, start with the mutual window: both stations need the Moon above a usable elevation at the same time. Then add selection criteria. Perigee gives the best path, low sky noise (Moon away from the galactic plane and the Sun) helps on lower bands, and the Moon at a reasonable elevation avoids ground noise. A common convention in JT65 is that the more easterly station takes the first period, but agree on it explicitly in the sked. Keep the exchange minimal and standard (callsigns, reports, a confirmation, then 73) so that a marginal QSO is not lost to a procedural misunderstanding. The short messages like RO and RRR are decoded at lower signal levels than full messages, which is why they exist.
-
Planning a first homebrew station: build order, and what to measure at each step
I'd swap 3 and 4 only if the builder has no transmitter license yet. A receiver can be built and used on day one, and nothing about it can cause interference. A direct-conversion receiver also doubles as a test instrument: tune it near your crystal oscillator and you can hear the signal, the drift and the key clicks. On direct-conversion problems, two fixes cover most of them. First, put a simple band-pass filter ahead of the mixer so AM broadcast stations are attenuated before they hit the detector. Second, keep the audio stage's gain and bandwidth sensible. A low-pass response in the audio chain, even a few RC sections, makes a big difference to how tiring the receiver is. Hum usually comes from the supply or ground layout, not the mixer, so check those before redesigning anything. For layout, Manhattan-style construction on copper-clad board, or dead-bug style for small circuits, is fine at HF. Short leads in the oscillator and mixer matter more than a neat appearance.
-
Combining POTA and WWFF activations: KFF references, logging and what to check before you go
From the hunter side, the main thing that helps is for activators to state the WWFF reference explicitly, not only the POTA one. A lot of hunters keep one program's spotting page open and miss stations who are only spotted on the other. If you are on both, spot on both, or at least make sure your CQ includes both names so people tuning past know what you are. It also helps to read out the reference slowly in the exchange. KFF numbers can be confusing over a weak path, and using standard phonetics for the letters and clearly spoken digits cuts down on repeats. If you are running low power with a lot of callers, keep exchanges short: callsign, signal report and reference only when asked. Then you spend your time logging contacts instead of explaining them. Hunters chasing awards should also keep their own list. If an activator's log has an error, being able to show your own record of the date, band and time makes any correction request much easier.
-
Building HF wire antennas from scratch: wire, insulators, chokes, ladder line, radials, and checking the build in EZNEC or MMANA
On the choke question, it's worth measuring before deciding. A cheap way to see whether the shield is carrying current is to watch the analyzer reading while you move or touch the coax a few feet below the feedpoint. If the resonance or R and X values shift, common-mode current is flowing. Adding a choke, or moving it closer to the feedpoint, should make the reading stable. Placement matters too. A choke at the shack end does little to stop the shield from acting as part of the antenna at the other end. If the antenna is low and the coax runs along the ground, the effect is stronger. For ladder line, I'd add one detail: a 4:1 balun is not required, and often not ideal. If the load is a high-impedance balanced line, a 1:1 current balun at the tuner usually does the job, and a well-designed balanced tuner can skip the balun altogether. Whatever the choice, check the tuner's loss on the band where the line SWR is worst. Most of the loss on a multiband ladder-line dipole is in the tuner and balun, not the line.
-
Which spotting and lookup tools do you trust, and how do you cross-check them?
One habit that helps is to treat each source as measuring something different. A cluster spot tells you what a person claims to have heard. An RBN or PSK Reporter spot tells you what a machine decoded at a specific location. Neither tells you whether you can work the station from your own location. If a rare call appears on the cluster, I'd check whether a skimmer has also spotted it, and whether the frequency and mode make sense, before tuning around for it. For busted calls, a quick look at the lookup data helps. If the callsign doesn't exist, or its listed country doesn't match the prefix people are reporting, the spot is likely wrong. Some logging programs warn you about that automatically, and it is worth enabling if yours does. Also remember that RBN and PSK Reporter are strongest where skimmers and FT8 stations are dense. Behind a mountain range or in a thin region, your absence from the map may just mean nobody was listening there.
-
SSB audio setup: mic gain, ALC, processor and bandwidth for a clean signal that still gets through
For DX and pileups, the setup matters less than technique. Listen long enough to understand how the DX station is working: split operation, call areas, or a net-style list. Then give your callsign once or twice, using standard phonetics, instead of long strings of repeated calls. If you're running an amplifier, keep drive within the linear range and check ALC from the amp too, since clean audio into a clipped amp still splatters and annoys neighbors on the band. On the receive side for weak signals, I'd narrow the filter before reaching for NR. Dropping from 2.4 kHz to something in the 1.8 to 2.1 kHz range often removes enough adjacent noise to make speech copyable without the underwater artifacts that heavy DSP noise reduction can add. Slow AGC and manual RF gain also make a big difference when a weak signal sits beside a strong one. Make one change at a time so you can tell what helped.
-
Getting started with SOTA: summit references, points, activating, chasing and a light kit that works
For a first outing I'd lean toward the simplest setup that can plausibly reach four contacts. On VHF that means a handheld, a better antenna than the stock rubber duck, and a spot posted before you start calling. Chasers can only find you if they know where you are, so the spot matters as much as the radio. With HF it helps to be organised about the wire. A pre-cut dipole or end-fed with the feedline wound on a small spool saves fiddly work with cold hands. Many people carry a short fishing-pole style mast, but a tree or a trekking pole can also work if the summit allows it. Whichever you choose, check that your antenna and your operating position stay inside the activation zone. On logging, write the callsign, time (UTC), band and mode on paper as you go, even if you plan to use a logging app. Batteries die and screens are hard to read in sunlight. You can enter everything neatly at home and upload it to the SOTA database from there.
-
Tracking award credits across DXCC, WAZ, WPX, IOTA, POTA and SOTA: how are you keeping the records straight?
On POTA and SOTA, it helps to think of them as database-driven awards rather than confirmation-driven ones. The usual problem isn't a missing QSL card. It's a mismatch between what you logged and what the activator logged. For POTA, if a contact doesn't show up in your hunter record, first check whether the activator has submitted the log yet, since uploads can lag behind the operation. Then check your own copy of their callsign and the park reference. A busted call on either side can leave the contact orphaned. If you keep your own log, record the park reference in the right field so it's easy to reconcile later. For SOTA, the activator needs enough contacts for the summit to count, and chaser points are tied to the logs the activator submits. Keep the summit reference, date and band in your records. Check the current association rules for the exact scoring and minimums, since they are updated from time to time. The mental split that helps me explain it to newcomers: DXCC, WAS, WAC, WAZ and WPX ask you to prove your contact, usually with LoTW or a QSL. POTA and SOTA mostly ask the other station's submitted log to prove it, and your task is making sure your contact is easy to match. For IOTA, check the group reference list and the program's current confirmation rules before counting a contact. A station on an island doesn't always belong to the reference you'd expect, so verify the group before you plan around it.
-
Building a Winlink station from scratch: Telnet first, then gateways, modes, P2P and forms
On modes: for VHF/UHF the practical split is between Packet and VARA FM. Packet is the more widely supported on gateways and tolerates modest gear, and a software TNC makes it cheap to try. VARA FM is much faster when both ends support it, and it has narrow and wide variants, so check that your radio's audio path can actually pass the wide one. A rig's 9600 data port is flat enough, but a mic-input connection often is not. VARA's free version is speed-limited and a registration key unlocks full speed, so a slow session on an unregistered install is not necessarily a propagation or setup problem. On HF it is mostly VARA HF versus ARDOP versus Pactor. ARDOP is free and open and is a decent fallback. VARA HF generally gets the higher throughput and is common on gateways. Pactor is hardware-dependent (an SCS modem such as the PTC series or P4dragon), so it makes sense if you already own one or need to reach Pactor-only gateways. Check the list for what your nearby HF gateways really offer before spending money. One suggestion for debugging: when a connection fails, work out which layer failed. If the modem never keys the radio, it is PTT. If the radio keys and the gateway never answers, it is frequency, offset, propagation or level. If it connects and then drops at login, it is credentials. If it connects, logs in and stalls partway through, look at signal quality and bandwidth choice. Switching to a narrower bandwidth for a weak path is often the cheapest fix. Also listen first. Most gateways are shared, and if the channel is busy and you start transmitting anyway, you will get nowhere and annoy other users.
-
Getting your first ham license: how do I find a test session, what is an FRN, and what should I study for Technician?
Here is the usual sequence, with a couple of things to verify locally. Finding a session. Exams are run by Volunteer Examiners (VEs). These are licensed hams accredited through a Volunteer Examiner Coordinator (VEC) such as ARRL VEC or W5YI. Search tools for sessions exist on the ARRL site and on HamStudy. Local radio clubs also post their own schedules. Many teams also offer remote sessions by video, so you may not be limited to your own town. Some sessions are walk-in and some require pre-registration, so read the listing and contact the listed person. Don't assume you can just show up. FRN. The FCC Registration Number is your identifier in the FCC's systems. You get one by registering in the FCC's CORES system. Do it before exam day, because the VE team needs it to file your application. Write it down and bring it. Your license will later show up in the Universal Licensing System (ULS), where you can look yourself up by callsign or name. Keep your CORES login details, since you'll need them for address changes or renewals. Fees. The VE team or its coordinator typically charges a small session fee for covering costs, and the amount varies between teams. Whether the FCC itself charges an application fee has changed over time, so check the session listing or ask the contact person before you go. Ask what payment methods they accept so you aren't caught without cash. What to bring. Bring a photo ID, your FRN, a pen or pencil, and a basic calculator if you want one (Technician has little math). Ask the session contact whether they require anything else, such as a printed copy of your confirmation.
-
Newly licensed? Share your first QSO plans, what to buy first, and mistakes to avoid
For a first repeater call, look up the repeater's output frequency, offset (commonly 600 kHz on 2 m and 5 MHz on 70 cm, but check your band plan), and required tone. Then listen for a while to learn how the local users operate. When it is quiet, say something simple like "This is [your call sign], listening." If someone answers, give your name and general location. A first contact is not a test. Common stumbling blocks are leaving the tone off, setting the wrong offset direction, and getting stuck on the "monitor" button so you hear noise. If you cannot reach the repeater, try simplex. Many places use 146.520 MHz as a 2 m calling frequency, but verify what your region uses. For HF and contests, you do not have to be fast right away. Practice copying call signs, use standard phonetics, and listen to a few exchanges before jumping in. A club meeting or Field Day-style event is a good place to try it with someone beside you. Many clubs have members who are happy to help with a first logbook entry, even if they are better known for tinkering with antennas than for chatting.
-
Which spotting and lookup tools do you actually keep open while on the air? (DX cluster, RBN, PSK Reporter, POTA/SOTA and more)
On RBN and PSK Reporter as an antenna test: they're very useful, but they only tell you who was listening, not who could have heard you. A skimmer or decoder that's close to you or has a quiet location will make a mediocre antenna look good. A gap in the map doesn't prove the antenna is bad, because there may simply be no receivers in that direction. For a fair comparison, keep the mode, power, band and time of day as close as you can between tests. Alternate between antennas in short blocks rather than running one all morning and the other all afternoon, because band conditions change. Then compare SNR reports from the same few stations that heard both. A handful of repeat reporters gives a cleaner comparison than a map full of dots. With FT8, make sure your software is set to report to PSK Reporter and that your grid square and callsign are entered correctly, or the data will be confusing. For cluster feeds, filters matter more than which interface you use. Limit by band and mode, and consider ignoring spots from skimmers if you only want to see human-confirmed ones, or the reverse if you want the early notice. Neither choice is right in every case.
-
Small lot + HOA: EFHW, doublet, or vertical? Comparing them on efficiency instead of SWR
Agreeing on the doublet, but a few other points on the same shortlist. On SWR: a bad SWR meter reading at the radio and a good one are both misleading when the coax is lossy. A long run of thin coax can make a terrible antenna look like a 1.3:1 match, because the loss masks the reflection. A quick check is to disconnect the antenna and look at the SWR with the far end open or shorted. A good line should show a very high SWR. If it looks decent, much of your power is going into the cable. For scale, a typical 100 ft run of RG-213 loses roughly 0.6 to 0.7 dB at 14 MHz when matched, and thin RG-58 loses about twice that. Mismatch makes both worse. The takeaway is to keep coax short, use a decent grade, and put the matching point as close to the antenna as practical. On verticals: a ground-mounted quarter-wave over a poor radial field can look great on the analyzer and radiate poorly. The base impedance over perfect ground is about 36 ohms, but ground loss adds resistance that makes it look closer to 50, so a nice SWR is partly lost power. The fix is radials, either many short ones on or just under the ground, or a small number of elevated radials (often four, each a quarter wave, at a few feet up or higher). Elevated radials are usually easier to live with on a small lot, and sloping them down can pull the feedpoint closer to 50 ohms. A vertical does well for low-angle DX but picks up more local noise than a horizontal wire. On inverted Vs: an inverted V at a 30 ft apex does something useful on a small lot, since you only need one support and the ends droop. An included angle of 90 to 120 degrees brings the feedpoint impedance down toward 50 ohms, and the resonant length is a bit shorter than a flat dipole. Keep the ends well out of reach, because the high-voltage tips are a safety issue. On magnetic loops: for a restricted site, a magnetic loop is a real option, indoors or in an attic too, but be honest about the numbers. Efficiency falls steeply on the lower bands for a loop of limited size, and the bandwidth is very narrow, so you retune often. Conductor thickness, the capacitor and the joints decide the losses, and the capacitor voltage can reach the kilovolt range at 100 W. It is a stealthy, quiet-receiving antenna, not a stand-in for a full-size dipole. A few notes on baluns and ununs. A 1:1 current balun or choke is for suppressing common-mode current, while a 4:1 or 9:1 unit is for transforming impedance. Check the core mix and how many turns or cores are used. Ferrite loss is what makes a choke work, but it also makes it heat up if it is badly chosen or saturated. For HOA stealth, thin dark wire (dark green or black) against trees works better than most people expect. In the US, the FCC's PRB-1 covers state and local regulations, not private deed covenants, so read your actual documents. It is also not legal advice, so check before you build. For the original question, I would pick the doublet plus choke plus a short coax run, and add a four-radial elevated vertical if the lot allows it. Does anyone have a better trade for 80 m on that lot?
-
Keep, sell, or restore: where do you draw the line between a useful rig and a shelf queen?
I like the idea of asking which radio you would rebuy, because the answer is often not the flashiest one. For a lot of people it turns out to be a workhorse that is easy to live with: good ergonomics, a receiver that doesn't tire your ears, and a layout you can run without looking. That tends to matter more than a spec sheet. I'd also push back gently on the idea that unused features mean a wasted purchase. Plenty of operators grow into a rig over time. Contesting, portable work, or a new digital mode can suddenly make a menu item you ignored for a year very relevant. Where I do agree is that antenna and grounding improvements usually pay off more than another radio, so if the shack feels stuck, it's worth looking at the wire before the box. As for keeping versus selling, I'd say hold onto anything you can't easily replace, like unusual or well-documented classics in good condition, and let go of the stuff you can find again at a fair price. Then the "shelf queen" question is partly a question about replaceability.
-
Building a Layered Go-Kit: HT, Mobile, Power, Antennas and a Family Plan That Doesn't Depend on Ham Licenses
On the family-plan side, I'd push back a little on putting too much weight on ham gear. If the plan only works when everyone has a ham license, it'll fail the first time the licensed person isn't home. FRS or GMRS handhelds are simple enough for kids and non-hams to use, and a shared channel plus a scheduled check-in time covers most neighborhood needs. MURS is a good option if you want something outside the crowded FRS/GMRS channels, though it has fewer consumer radios available. A few other practical points. Keep the radio's menu simple: lock the channel if the radio allows it, and write the channel number on the radio itself. Agree on what's worth transmitting and what isn't. And remember that your first message might be a plain "we're OK, at home" rather than a long conversation, so keep airtime short for everyone else on the channel.
-
From-scratch wire antenna build: what actually matters in wire, insulators, chokes, ladder line and modeling?
Modeling is worth doing before you cut wire, as long as you know what the model cannot tell you. With EZNEC (NEC-based) or MMANA-GAL (MININEC-based), the first checks are segmentation and junction geometry. Segments should be short relative to wavelength, and segment lengths should be reasonably similar where wires meet, particularly at the feedpoint and where wires bend. Sloping wires, inverted Vs and wires close to ground need more care. It also helps to run an average gain test where the program provides one, because a lossless free-space model should come out near 0 dBi. If it does not, the geometry or segmentation is suspect. Models are only as good as the ground assumption. Ground conductivity and permittivity change low-height patterns and impedance noticeably, and neither program knows your actual soil. So a model is better for comparing options (inverted V against flat top, 2 versus 4 elevated radials, trap placement) than for predicting the exact SWR you will see. The velocity factor of insulation and the capacitive loading from supports, rope and nearby trees will not be captured unless you add them. For verticals, radials matter more than almost anything else. Ground-mounted radials need a lot of wire, since the number of radials and how long they are both affect ground loss. Elevated resonant radials can work with far fewer wires. Drooping them down at roughly 45 degrees also moves the feed impedance upward toward 50 ohms, instead of the lower value you see with horizontal radials. A choke at the base is still useful, because the feedline can act as another radial. Traps trade simplicity for loss and bandwidth. In a dual-band trap dipole, the trap is parallel resonant at the upper band and isolates the outer wire, while on the lower band it acts as inductive loading and makes the antenna shorter than a plain dipole. Capacitor voltage rating, coil Q and weatherproofing all matter, and you should measure the trap's resonant frequency on the bench before installing it. A pair of plain dipoles fed from one point, or a fan dipole, is a simpler alternative for two or three bands, though the interaction between wires will shift lengths.
-
One clean log across N1MM Logger+, WSJT-X and Log4OM: CAT sharing, ADIF/Cabrillo, and LoTW/QRZ/Club Log uploads
On CAT, the cleanest pattern is to give the rig to exactly one program and make everything else a client of it. If you have WSJT-X plus a contest logger, point both at the same hub (OmniRig, FLrig, or a rigctld instance) instead of using a virtual-port splitter, which adds one more thing to break at 0000Z. If you do use virtual ports, keep the baud rate, data bits and stop bits identical on both sides, and check that PTT and CW keying lines aren't also getting passed through. For digital contest modes, keep the audio and PTT path in mind too. If WSJT-X keys the rig through CAT or a USB codec while N1MM+ also sends CW or voice-keyer commands, you can end up with two programs fighting over PTT. Decide which application owns transmit for each mode and disable the other's PTT method. Also check the PC clock. FT8 and FT4 need accurate time, and a log with sloppy timestamps can fail to match on LoTW or in a sponsor's cross-check. Sync before the contest starts, not during it. For the WSJT-X to contest-logger handoff, the options are either the WSJT-X UDP broadcast (which Log4OM can listen to directly) or a relay tool that sits between them. Whichever you use, run a few test QSOs and confirm the callsign, report, grid, band, mode and time all arrive intact before the contest starts.
-
Repeater basics checklist: offsets, tones, linking modes and etiquette. What would you add?
For linking, I'd start by telling newcomers that a repeater can be one of several things. It might be a standalone FM machine. It might be linked by RF to other repeaters. It might be connected to the internet through EchoLink, IRLP or AllStar. It might be a digital repeater using DMR, D-STAR or Yaesu System Fusion, with Wires-X for the networking side. Etiquette changes depending on which it is. On internet-linked FM systems such as EchoLink, IRLP and AllStar, remember that the audience may be much bigger than the local coverage area. Those systems also add delays. Pause a second or two after keying before you speak, because the link may need time to open. Listen for whether a link is active before you start a long conversation. A long chat on a linked system ties up every machine in the link, and the time-out timer applies to your transmission. EchoLink and IRLP nodes have node numbers and are controlled by DTMF. AllStar is built on Asterisk and also uses node numbers. Check the repeater's published instructions before sending commands, because link commands vary between systems and owners often disable some of them. On DMR, you need a registered DMR ID, a matching color code, the right timeslot and a talkgroup. A short key-up on a talkgroup can activate it across a network. Listen first, and don't press PTT just to see if it works. Remember that a talkgroup may be busy even if you hear nothing locally. On D-STAR, the call sign fields in your radio (MYCALL, URCALL, RPT1 and RPT2) determine where your audio goes, and link or unlink commands to reflectors are sent through the URCALL field. Wires-X works through rooms and nodes, and some Fusion repeaters can switch automatically between analog FM and digital C4FM, so an analog user may find the repeater suddenly changes behavior. One more point for the checklist: on any linked or digital system, you're talking to more people than you can hear. Keep language and topics suitable for that audience, and be careful about anything that might count as third-party traffic across borders.
-
Building a lightweight activation kit: EFHW or linked dipole, and how to power it
On logging, many operators write on paper first and transcribe later, because a phone can fail from cold, low battery, glare or rain. If you use an app, keep a paper backup of callsigns, times in UTC, band and mode, and the park or summit reference. For POTA, a valid activation usually requires a minimum number of contacts within a single UTC day, and SOTA has its own point thresholds and activation zone rules. Check the current official rules before you head out, since programs update them. On weather and safety, a telescopic pole and a long wire are not what you want near lightning. A common rule is to take down the antenna and leave exposed ground as soon as thunder is audible. Wind is the other pole killer, since a fully extended fiberglass pole with a wire on top catches a lot of it. Guy lines, or simply a shorter extension, can save the day. It's also worth telling someone where you're going and when you'll be back, and carrying extra layers, water and a way to call for help that doesn't depend on the radio you're operating. For Field Day style setups, the same ideas scale up: separate power sources for radios, a clear tent or shelter layout, and good cable management so nobody trips over coax. A simple checklist taped inside the go-box catches most forgotten items.
-
VHF/UHF antenna choices: gain vs. pattern, J-poles and collinears, mag mounts vs. NMO, and why coax and connectors matter
I'd start with the path rather than the antenna type. If the nearest repeater is in line of sight, a collinear with moderate gain on a mast is hard to beat. If it's on the far side of a ridge or well beyond the horizon, a small yagi may do more than a larger omni, because it adds gain in the direction you need and rejects noise from other directions. The cost is aiming it, which is why people often add a rotator or choose one repeater as the main target. On the 50-foot run: the usual answer is to spend on the cable first, because every dB lost in the coax is lost on both transmit and receive. For a 70 cm run of that length, a thin cable like RG-58 can eat a large share of your power, so a lower-loss type with N connectors is worth the extra cost. For a 2 m-only setup, you have more tolerance, but the UHF argument still applies if you ever add that band later. Also make a drip loop where the cable enters the building, and ground the mast and cable according to local electrical and lightning-protection guidance.
-
Remote station design: VPN or port-forward, where to put the latency, and what the rules expect from you
On the VPN question, I'd treat it as the default and port forwarding as the exception. The vendor software is convenient, but the radio's own network stack becomes the thing the internet sees. With a VPN endpoint on a Pi or a router, you expose one well-understood service, you can restrict it by key, and the radio never sees a stranger's packet. The trade-off is added latency from the tunnel and any relay, and some audio apps are fussy about MTU, so test with the real software before you commit. The other thing I'd add is a dead-man design. Do not rely on the remote operator's software to unkey the transmitter when the link dies. Have something at the station that independently drops PTT if packets stop arriving, plus a hard TX timeout in the radio itself. A controller like RigPi with a web relay can power the amplifier off, but it should be on a separate path from the radio so a single network fault does not leave you without control of both.