Everything posted by Mod_Tom
-
Starting out on LEO satellites: FM birds first, then linear? Doppler, tracking software and antenna choices
FM first is the usual route and I'd stick with it. The main thing it teaches you isn't Doppler, it's pass geometry: working out when the satellite is high enough to use, how to point at a moving target, and how to listen while transmitting. If you start on a linear bird, you have to deal with all of that plus inverted tuning and a very weak downlink. On Doppler, manual tuning is a good way to learn what is actually happening. For FM, a common approach is to correct the downlink in steps as the pass progresses and leave the uplink at the nominal value for the first passes. That's good enough to start. Once you move to full duplex and linear birds, though, hand-tuning both ends gets tiresome, and CAT control in Gpredict or SatPC32 is worth the setup effort. Remember that many software setups are set up for a specific rig and may only follow one radio, so check the rig-control documentation before you buy anything. On grid squares: they are 4-character Maidenhead locators like FN31, usually extended to 6 characters. Get yours from a locator map or from a GPS app, not from memory. On the satellites it is normal to exchange callsign and grid only, so a quick exchange is expected. Be sure you're not mixing up neighbouring squares, particularly if you are near a boundary. For the arrow antenna, expect to move your whole body while holding it. The main skill is keeping the elements pointed at the satellite while following the track, and not dropping out of the beam when the satellite is close and fast. It is useful to print or display AOS time, maximum elevation and the azimuth of the pass before you start.
-
Planning a from-scratch wire antenna build: wire, insulators, feedline choke, and how much to trust SWR and models
On the choke question, I'd separate what you're trying to achieve from how you get there. The goal is high impedance to common-mode current on the outside of the coax, and the usual rule of thumb is to aim for at least a few kilohms resistive at the lowest band. Coax coiled on a ferrite toroid is a good way to do that for HF. Type 31 mix tends to work well on the lower bands, and type 43 gets more useful as you go up. The number of turns matters because the choking impedance depends on both the core and the winding capacitance. Too many turns can lower the self-resonance, so there is a point where more turns hurts at the top bands. A second small thing is placement. A choke right at the feedpoint is good for keeping the shield from becoming part of the antenna. A second choke at the shack entrance can help with noise, and the two do different jobs. If you are using ladder line, the line's own balance matters, so pay attention to how it leaves the antenna and stays symmetrical. A line that droops against a gutter or a pole can unbalance the system even with a decent choke. For the fan versus trap question, I'd lean toward fan dipoles for a first build because each element is a plain wire you can trim independently. Trap antennas have more parts to fail, and traps that are not weatherproofed can drift in tuning as moisture gets in.
-
VHF/UHF antenna choices: J-pole, slim jim, 5/8 wave, collinear, yagi, and what matters more than the antenna type
For the coax-and-connector question, consider the whole run before choosing. If you have a short run of 15 to 20 ft on 2 m, RG-8X or similar is usually fine. If it is 70 cm or longer, go to a low-loss type with N connectors. PL-259s are easy to get wrong: a cold solder joint, or a shield that is not tight at the back of the connector, gives intermittent noise and SWR problems, and they also let water in unless sealed. Use the correct reducer for the cable diameter. For satellites, a small hand-held yagi like an Arrow-style, or a pair of crossed yagis on an az/el setup, is the usual pair of options. A fixed omni, such as a turnstile or a quadrifilar helix, is a quieter choice if you want to avoid a rotator and are OK with lower gain. For a repeater, the question is different. The Tx and Rx need isolation, so the choice is either a duplexer, with a single antenna, or two antennas separated vertically with a good gap, which is cheaper than cavities but needs a tower.
-
Repeater basics that trip people up: offsets, tones, time-out timers, linking and etiquette
Good list. One addition on the tone settings: when you're not sure whether the issue is the tone or the offset, the "reverse" function on most radios (it swaps your receive and transmit frequencies) is a useful test. If you can hear a nearby station directly on the repeater input, you know the offset is roughly right and the problem is likely tone or distance. It's also worth knowing that a repeater can require a tone to access it while not sending any tone on its output. In that case, turning on tone squelch (TSQL) would silence a repeater you can actually hear. If you hear it but can't open it, check "Tone" first. If you can't hear it at all, check whether you've enabled decode with a tone the repeater doesn't send. With DCS, the codes sometimes come with an inversion option (N or I) on the radio, and a mismatch there will also prevent access. If the listing gives a DCS code, confirm the polarity setting too. One more point on closed repeaters: "closed" doesn't always mean secret or hostile. Some are closed to prevent heavy use on a small system or because the owner wants to keep it for a specific group. If the listing says closed or shows no access info, the polite approach is to ask the owner or the club instead of probing.
-
One master log or several? Keeping N1MM+, WSJT-X and Log4OM in sync for contests, LoTW, QRZ and Club Log
I'd lean toward a single authoritative log and treating contest software as a temporary working copy. The usual pattern is to run the contest in N1MM+, export ADIF and Cabrillo from the same finished contest database, and import the ADIF into the long-term logger afterward. Then you only upload to LoTW, QRZ and Club Log from one place, and the duplicate problem mostly goes away. Before importing, set up a rule for the contest data. Some loggers will happily put an exchange like a serial number or section into the comment or notes field. That's fine for archive purposes, but it can make later searches messy. Also check whether the import preserves the original QSO time. Some programs write the import time to the log's own timestamp field, which is harmless, but you want TIME_ON to stay intact because LoTW matches on it. For the UDP issue, if the WSJT-X UDP server is set to a multicast address, several listeners can receive the same stream. A single unicast target is the more fragile setup. Test with every program open at once, log a few QSOs and confirm each one records them exactly once. One caution on dupes: dupe rules belong to the contest, not the program. In some contests a station can be worked once per band, in others once per band and mode group, and in a few once for the whole event. Select the right contest definition at the start, because changing it midway can leave the dupe sheet disagreeing with the score summary.
-
Studying for the Technician exam: how do you use the 35-question Element 2 pool without just memorizing answers?
For sequencing, one approach is to read a study guide chapter, then take a practice quiz limited to that subelement. Save full 35-question practice exams for later, when you want to test timing and find weak groups. Most practice sites report results by topic, so use that to decide where to reread. For the rules-heavy material, tie each fact to a situation: Privileges: Technicians have operating privileges on amateur bands above 30 MHz, plus limited HF access. Learn exactly which HF segments and modes those are from the current rules text or your study guide, not from memory of a forum post, mine included.License terms: Know the license term length, the grace period concept, and that you must ID with your call sign at the intervals the rules require. Understand how those work in practice, not just the numbers.Repeaters: Learn what an offset is, why you need the right input and output frequencies, what a CTCSS (PL) tone does, and the courtesy practices: listen first, identify, keep transmissions short, and don't assume a pause means a free machine.RF exposure and safety: Understand that exposure limits depend on frequency, power, antenna type and distance, and that you must evaluate your station. Pair that with the electrical safety questions on grounding, lightning, towers and power supplies.When you miss a practice question, ask why the right answer is right instead of just noting it. If you can explain it in a sentence, you'll likely handle a reworded version on exam day.
-
Winlink over radio: how the pieces fit together (RMS gateways, session types, sound card/TNC setup, forms and P2P)
My checklist for 'connects, then stalls' goes in this order, starting with the cheapest checks. First, confirm the radio is in the right mode and bandwidth. For VARA FM that means the right wide or narrow setting on the rig and in the software, and for HF it means USB with the filters wide enough for the bandwidth you chose. Second, check the audio levels. VARA gives you level feedback in its own window, and the point is to avoid both clipping and a starved signal. A weak transmit level and an overdriven one both show up as repeated retries, so they look alike from the outside. Third, check PTT timing. A rig that takes a moment to switch can clip the start of every frame. On HF there's one more thing. Make sure the frequency you enter lines up with how the gateway list expresses it. Dial frequency and centre frequency differ by the audio offset, and entering the wrong one puts you slightly off the gateway's passband. Winlink Express usually handles this once rig control is configured, but it's worth verifying against the gateway's published information when something is off. As for the test order, Telnet then P2P then gateway is a good one. Telnet proves the account, P2P proves your own audio and PTT chain with a friendly station on the other end, and the gateway test only has to prove the path. Unregistered VARA also runs at a reduced speed, which can look like a poor link when it's really just the licence limit, so factor that in before blaming propagation.
-
Build a Park Activation Kit That Works: Antenna, Power and Safety Basics
A good portable station isn't the one with the most gear. It's the one you can carry in one trip, set up in about 15 minutes, and use for a couple of hours without something failing. Whether you're activating a park for POTA, a summit for SOTA, a WWFF reference, or just practicing for Field Day, the same few decisions decide how the day goes: the antenna, the power, the logging plan, and the weather. Start with the activation goal Each program has its own thresholds, and they change, so check the current rules before you head out. As a general guide, POTA asks for a minimum number of contacts (ten) within a single UTC day for a valid activation. SOTA awards activator points for a small number of contacts (four), and WWFF uses a higher threshold (44). Knowing the target helps you plan time, band choice, and battery capacity. It also tells you whether you can afford to spend an hour on a fussy antenna. Antennas: keep it simple and repeatable Two designs dominate portable operating because they are light, cheap, and forgiving. End-fed half-wave (EFHW) What it is: a wire cut to a half wavelength on the lowest band, fed at the end through a matching transformer (commonly 49:1 or 64:1) that converts the very high end impedance to something your radio can accept. Why people like it: a 40 m EFHW is also resonant on 20, 15, and 10 m. No band switching, no coax run to the far end, and a light feedline. Watch for: common-mode current on the coax. A choke near the transformer or radio often makes a noticeable difference to both noise and SWR. Trim the wire in small steps and write the final length down. Deployment: run it as an inverted L or sloper from a pole or tree branch. Keep the feed end off the ground if you can, and keep the wire away from metal fences, vehicles, and your body. Linked dipole on a pole What it is: a center-fed dipole with sections joined by small links. Connect the links for lower bands, disconnect them for higher ones. Why people like it: it is a true dipole with a predictable feed point and usually a low SWR on each band it was built for. It needs no tuner. Watch for: more connectors mean more things to mislabel or lose. Mark each band section clearly, and bring a spare link or two. Deployment: a fiberglass or telescoping pole (roughly 6 to 10 m) holds the center up, forming an inverted V. The wire ends can be tied off low with cord and stakes. Either way, pack a small bag of the things that fix most antenna problems: cord, a few tent stakes, a throw line and weight, spare connectors, and a short jumper of coax. If your antenna is resonant where you expect it to be, you have already solved most of the common field problems. Power: calculate, don't guess QRP, typically 5 W for CW and digital modes or up to 10 W on SSB, makes power planning easy. A rough way to size a battery: Find your radio's current draw on receive and at your transmit power. Check the manual or measure with an inline meter. Estimate a duty cycle. CW and SSB activations are mostly receive and short transmissions, but running POTA calls or digital modes raises the average. Multiply the average amps by the hours you plan to operate, then add a healthy margin (50 percent is reasonable). Battery capacity is often given in amp-hours at a nominal voltage. A 12.8 V, 6 Ah LiFePO4 pack holds roughly 77 Wh. For a radio averaging around one amp, that is several hours of operating, but cold weather and heavy use cut that down. Why LiFePO4 is popular It gives a flat voltage curve, so your radio sees stable power until the battery is nearly empty. It is lighter than a sealed lead-acid battery of similar capacity and tolerates many charge cycles. A fully charged 4-cell pack sits around 13.3 to 14.6 V depending on how recently it was charged. Confirm that your radio's maximum input voltage covers that range. Include an inline fuse close to the battery, use properly rated connectors, and check polarity every time. Charge LiFePO4 only with a charger designed for that chemistry, and avoid charging at freezing temperatures unless the pack explicitly supports it. Solar is a supplement A small foldable panel can extend a long day or top up a pack between trips, but cloud, angle, and shade reduce output a lot. Use a charge controller appropriate for your battery and don't count on the panel to run the radio on its own. Treat it as a bonus and size your battery to complete the activation without it. Operating tips for activators and hunters Activators should find a clear frequency, call CQ with the program name, and self-spot if the program's network allows it. Spotting is often what turns a quiet frequency into a pileup, so make sure the frequency and mode you post are accurate. Keep exchanges short and precise, and log as you go. If the paper log and digital log disagree, you will thank yourself later for writing the time and callsign down immediately. Hunters can help by listening first, sending a callsign once or twice at a steady pace, and not calling over the person who is mid-exchange. Weak QRP signals reward patience. If the activator says to listen for a specific station or region, follow that. Park-to-park contacts are a fun extra for those running portable too. Weather and safety come first Lightning: if you hear thunder, take down the antenna and move to a safe shelter. A common rule is to wait around 30 minutes after the last thunder before resuming. Never use a tall pole or wire antenna during a thunderstorm, and especially not on a summit. Power lines: set up far from overhead lines, with more clearance than the full height of the pole plus a margin for it to fall in the wrong direction. Heat and cold: bring more water than you expect to use, sun protection, and a warm layer. Hands get cold fast when working a key or keyboard. Wind: a tall pole is a sail. Guy it, or lower it if it starts to flex. Tell someone your plan: where you're going, when you plan to be back, and what you'll do if plans change. Cell coverage in parks and on summits can be patchy. Respect the site: follow park rules, stay out of restricted areas, don't stretch wire across trails where someone could trip, and pack out everything you brought. A short pre-departure checklist Radio, key or mic, headphones, and a spare power lead Fused battery, charger, and a way to check voltage Antenna, feedline, choke, pole, cord, and stakes Logging gear (paper and pencil are fine) and a printout of the park or summit reference Water, food, first-aid kit, sun and rain protection A fully charged phone and a simple map or offline navigation The best lesson: test at home Most field failures can be found in a backyard trial. Set up the antenna, run the radio on the battery, make a few contacts, and time how long it takes. Fix whatever annoyed you, then repeat until the kit feels boring. A boring setup in the field means more time for the part you came for: making contacts, enjoying the outdoors, and maybe hearing a faint signal come back to your call.
-
Building a yearly contest plan: exchanges, rules and log submission for the big HF, VHF and portable events
On the casual versus serious question: most contests offer low-power, QRP, single-band and assisted/unassisted categories, so you can pick a category that fits your station and time. Entering a few hours in a low-power category still counts as a submitted log, and sponsors typically appreciate logs of any size. Even a short log counts toward club scores where the contest has a club competition, though you should check that contest's rules for the details. Two practical notes. First, read the rules for operating-time limits and band-change rules in your category, since some have restrictions on how often you can change bands. Second, after you submit, check the sponsor's published results and any public score listings to see how your numbers compare. That feedback is the quickest way to find out whether a higher-power or multi-band entry is worth trying next year. For VHF contests, the same logic applies with a different challenge: the activity is lower, so grid-square count and rovers matter more. Check which bands are allowed in the category you choose, and read the rule on rover grid changes before you plan a route.
-
Newly licensed? Share your first radio, first QSO, and the advice you'd give the next new ham
Congrats to everyone who's newly licensed. One tip for anyone planning to visit a club meeting: go even if you feel like you don't know enough yet. Clubs usually include people with very different interests, such as emergency communications, DXing, antenna building, and digital modes, so you can often learn what's worth your money before spending any. Asking "what would you buy first for the kind of operating I want to do?" tends to get better answers than "what's the best radio?" Also, if someone offers to help program your radio, ask them to show you what the settings mean. Learning what frequency, offset, tone, and power level do will help you troubleshoot later, and software like CHIRP is much less mysterious once you know that.
-
What does your spotting and lookup stack look like? DX cluster, RBN, PSK Reporter, POTA/SOTA and the rest
For field use, I'd split it into what you need online and what you need offline. Propagation pages, POTA/SOTA spot lists and cluster feeds all need a connection. RepeaterBook-type data and your logging software can be cached or exported ahead of time, so download what you need before leaving coverage. Repeater listings are user-contributed and can lag behind reality, so it is worth double-checking offset, PL tone and whether the machine is still on the air before you rely on it for a trip. On grids: know whether you need a 4-character or 6-character Maidenhead locator for what you're doing. Many contests and awards only ask for four, while VHF/UHF work and some digital-mode exchanges benefit from six. A grid map tool or a phone app with GPS lets you confirm your square instead of guessing from a rough map, especially near a boundary. For study, HamStudy-type practice tools work best if you also read the explanations for the questions you miss, instead of just memorizing answers. HamCalc and similar calculators are useful when you want to sanity-check a dipole length, a coax loss figure or a link budget, but treat the output as a starting point and confirm with an antenna analyzer when you can.
-
Making SET and Field Day Scenarios Expose Real Weak Points Before a Disaster Does
I'd add Field Day to the practice list, with the caveat that it only helps if you deliberately use it that way. As a contest-style operating event, it's built around making contacts. That has value, since it forces you to set up antennas, power, and stations in the field, often on generators, batteries, or solar, and to do it under a time limit. But the scoring doesn't reward the things that matter in a deployment, so you have to add them. Some ways to turn Field Day into useful practice: Treat setup as the exercise. Time it, and note what was forgotten: adapters, extension cords, fuel, logging supplies, a working copy of the net script. Also, who knew where things were stored? If the answer is "only one person," that's a finding. Run a short, informal traffic-handling segment alongside the contacts. Even a handful of formatted messages passed between stations will show whether people remember the procedure. Many Field Day rules also include credit for message handling, but check the current rules for the exact details instead of relying on memory. Rotate people into roles they don't usually fill, such as logger, net control, or the person handling the written message queue, so the group doesn't depend on the same few operators. Then actually write the after-action notes before everyone goes home or the next morning. Details fade quickly. Short bullets on power, antennas, operating positions, comfort and fatigue, and what you would carry differently are enough. Fatigue and weather are underrated: a station that works fine for two hours in good conditions may be a different story overnight. One caution: Field Day success can create false confidence. Good HF contacts under open conditions don't prove you can support a hospital, shelter, or emergency operations center, where the constraints are mostly about people, procedures, and relationships. Pair it with a separate, agency-facing drill so the two kinds of practice cover different gaps.
-
Choosing an SDR chain for HF and VHF: dynamic range, upconverters, antennas and which software to pair with it
Start with dynamic range, because it explains most of the confusion. An ideal ADC gives roughly 6 dB per bit, so 8 bits is about 48 dB before real-world losses, and the effective number of bits is lower. Everything the antenna delivers across the whole sampled bandwidth competes for that range, not just the signal you are tuned to. A strong FM broadcast station or local AM transmitter can push the converter near full scale while the weak signal you want sits near the quantization noise. That is why turning the gain up often makes things worse. Set gain so the noise floor on the spectrum is just visibly above the receiver's own floor, then stop. If the waterfall fills with ghost signals or spurs that move when you change gain, that is overload or intermodulation, not an antenna problem. Filtering helps more than extra gain. A broadcast-FM notch is a common first step for RTL-SDR on VHF, and bandpass filters for the band of interest help at HF. SDRplay receivers include switchable notches for broadcast bands in hardware. Pre-LNA filtering is where it matters: filter before amplifying, not after. At HF, external noise (atmospheric, man-made, local interference) usually exceeds receiver noise, so a low noise figure is less important than at VHF/UHF and above. A modest antenna and a clean receiver often beat a high-gain preamp feeding a weak converter. At VHF and up, noise figure and feedline loss matter more, so a mast-mounted LNA (powered via bias tee if your hardware supports it) can help, as long as you check that nothing in the path presents a DC short to the bias voltage. Antennas: a dipole or discone is a sensible starting point for VHF/UHF. For HF, a longwire with a 9:1 unun, a small active loop, or a magnetic loop each have different noise and overload behavior. Active antennas can overload your receiver on their own. Local noise from switching power supplies, LED lighting and the PC itself can swamp everything, so put the dongle on a USB extension, add ferrites, and use a common-mode choke on the coax. If the noise floor drops when you unplug things, you've found the problem. Direct sampling on an RTL-SDR works for casual HF listening, but sensitivity is limited and aliasing and overload are more likely without a lowpass filter. It is workable, not great. A native HF receiver is cleaner. Check the published specs for your specific model; frequency coverage and bandwidth vary by version.
-
On-air etiquette basics: listening first, calling CQ, breaking in and running a tidy net
On interference, it helps to separate what's happening: another legitimate station that didn't hear you, a local noise source, or deliberate jamming. A first step for the first kind is a polite, brief notice with your callsign and a statement that the frequency is in use. Don't escalate. The other operator may be a mile or a continent away and truly unable to hear the existing contact. If it persists, change frequency or give them the benefit of the doubt. With deliberate interference, the usual advice is not to respond or argue, since attention is what the person wants. Note the time, frequency and a description, and if it keeps happening, report it through the channels your national society or regulator provides. A repeater with a problem user is best handled by contacting the repeater owner or coordinator rather than talking about it on the air. For noise you cause, check your own station. Keep your audio from being overdriven, since splatter makes you wider than your neighbors expect. Do your tuning into a dummy load or on a clear frequency with a quick listen first. Keep your power sensible, not as high as possible. And if you hear a stronger station nearby, a small drop in your own bandwidth or audio processing is usually a better fix than asking them to move. For newcomers, a quick check before keying: am I on the right frequency and mode, is my callsign ready, and have I listened long enough? That habit prevents more problems than most rules do.
-
Dual-band mobile radio planning: FTM-500D vs ID-5100A vs TM-D710G, plus wiring, noise and cross-band basics
Cross-band repeat is worth thinking through before you rely on it. The radio receives on one band and retransmits on the other. A typical use is a handheld on UHF reaching the mobile, which repeats on VHF through the vehicle's better antenna. Whether it's a good fit depends on the radio's menu options and your local rules. Your station still needs proper identification, and you are the control operator. Never set it up on or near a repeater's input or output frequency. Choose frequencies where you aren't interfering with anyone, and consider adding a CTCSS tone so stray signals don't trigger the system. Remember that transmitting continuously generates heat. Using a lower power setting is often enough, and it is easier on the finals. Read the manual for your specific model, because the way cross-band is configured, and whether you can use it with digital modes, varies between Yaesu, Icom and Kenwood. The TM-D710G is commonly associated with a cross-band function, but verify the exact menu steps in its manual instead of assuming it works like another brand's. Also test with the vehicle parked and the engine running. Some noise problems and RF feedback into a handheld only appear under real conditions.
-
Getting my first ham license (Technician): where do I start with study, FRN, and finding an exam session?
Adding to the above on sessions, fees and first steps. Finding a session: exams are given by Volunteer Examiner (VE) teams, accredited through a Volunteer Examiner Coordinator (VEC). Two ways to find one: the exam session search on the ARRL website (ARRL is one VEC, and other VECs list sessions too), or the session finder on HamStudy. Many local clubs run sessions on a regular schedule, and plenty of VE teams also offer remote exams over video. Read each listing, because some sessions require pre-registration or have limited seats, and others accept walk-ins. If it's not clear, email the contact listed. Fees: the fee goes to the VE team or VEC to cover exam costs, not to the FCC. It varies by team, and it's generally a modest flat amount, but check the listing, since some take cash only or specific payment methods. The FCC's own application fees for amateur licenses have changed over time, so don't rely on an old forum post, including this one. Look at the FCC's current fee info, and the listing for your session, before you go. What to bring to an in-person session: a valid photo ID, your FRN, the exam fee in the accepted form, a pen or pencil, and a calculator if you want one. Ask the team about calculator rules in advance, because they may require that it has no stored data. Also have an email address you check, since it's part of the application. After you pass: you can legally transmit once your call sign shows up in the ULS database. That usually takes a few days, but it varies. Search ULS by your name or FRN to confirm. You can download an official copy of your license from there. First steps as a Technician: you have all amateur privileges above 30 MHz, which includes the popular 2 meter and 70 cm FM bands where most local repeaters live, plus limited privileges on some HF bands. Practical early moves: find your local club and the repeaters in your area, listen on the repeater for a while before you talk, and learn how to identify with your call sign, which is required at least every 10 minutes and at the end of a communication. A handheld is the usual first radio, and the club is a good place to ask which models people have had good results with. Many clubs run regular nets where a new licensee can check in and get comfortable on the air.
-
Building a contest year: which HF, VHF and portable events fit together, and what to check before each one
For a first contest I'd pick one with a simple exchange and a long window, so a few hours still counts. CQ WPX is a good example: report plus serial number, nothing to memorize. CQ WW is similar but you need to know your CQ zone, so look it up and write it on a sticky note before you start. Operators with modest stations often do well by working a couple of bands for short stretches rather than trying to run the whole 48 hours. Whatever event you pick, set up your logging software before the contest. N1MM+, N3FJP and others each have contest-specific templates, and they check dupes and track multipliers so you don't have to. Run a mock QSO or two to confirm the exchange fields match the rules, and know how to export Cabrillo before the deadline day arrives. Plenty of logs are lost to a bad header or a wrong category rather than a bad score.
-
Choosing a digital mode and fixing the usual FT8 problems: time sync, audio levels, CAT and what the decode thresholds mean
I'd go in this order: clock, audio, radio mode, then CAT. Time first, because the timing-based modes depend on it. In FT8 the decoder shows a DT value for each message, the time offset between the signal and your clock. If most stations show a consistent offset such as +0.5 or -0.8 seconds, your clock is probably the one that's off, not theirs. A decent target is a clock well within a second of true time, and closer is better. Windows' default time sync can be loose, so many operators run a dedicated NTP client or a GPS-based source. If you're not sure, check the DT column before touching anything else. Then audio. Set the sound card to the sample rate and format the software expects, usually 48 kHz, 16-bit. Disable audio enhancements, system sounds and anything that could route notification beeps into the transmit path. On receive, aim for a modest input level in the WSJT-X meter. The software's guidance is roughly the low end of the green zone, not pinned at the top. On transmit, the common mistake is driving the rig too hard. Keep the ALC barely moving, and reduce power instead of pushing audio. Overdriving causes splatter, which hurts everyone on the band even if you still log contacts. Radio mode matters too. You want USB (or the rig's data-USB mode), with speech processing off and any narrow filters opened enough to pass the whole audio passband, not FM or AM. For CAT, make sure the serial port settings match the radio's menu (baud rate, stop bits, handshake), because Hamlib will otherwise report errors or hang. If PTT is on RTS or DTR, check that opening the port doesn't key the transmitter by accident. Some USB-serial adapters toggle those lines when the port opens. Good isolation, ferrites and keeping audio cables away from RF also prevent the strange sporadic problems that look like software bugs. One more thing on the numbers: the S/N in a WSJT-X report is referenced to a 2500 Hz noise bandwidth, so it's an estimate of signal against noise, not an S-meter reading. A -18 report doesn't mean a weak signal in the usual sense. It's just a different scale.
-
Tube-era boat anchors vs. modern SDR rigs: what actually earns a spot on the operating desk?
My vote goes to "both, but for different jobs," and I think that's the honest answer for a lot of people. A modern transceiver is hard to beat for everyday operating. You get memory keying, a spectrum display, good filtering, and a rig you can turn on without wondering whether a capacitor is about to give up. The vintage gear earns its place when the radio itself is part of the appeal. Using a rig with a smooth mechanical tuning dial and real analog meters is a different experience from clicking through menus. I wouldn't pretend it's more efficient, though. If someone's main goal is working new entities or running a contest, a current radio is the practical choice. One piece of advice for anyone buying their first boat anchor: budget for restoration, not just the purchase price. A cheap rig that needs a full capacitor replacement and alignment can cost more in time and parts than a better-sorted one. Get a service manual and schematic before you commit, and be careful around the high-voltage sections.
-
VHF/UHF antenna choices: when does each design actually make sense? (J-pole, slim jim, 5/8 whip, collinear, yagi)
On satellites, the main issue is that a LEO pass sweeps across the sky, so a fixed omni gives little margin at low elevation. Many operators use a small handheld yagi on a dual-band FM radio, and a good design can work the bird at both ends of the pass. Since the satellite's orientation changes, polarization is not fixed, and crossed yagis with circular polarization reduce fading. A single linear yagi can still work if you rotate it to minimize the fade. Doppler is also a factor on UHF, so you retune the receive side during the pass. Gain alone doesn't solve it. A higher-gain beam needs better pointing and a narrower tracking window. For beginners, a modest beam and short low-loss cable are usually more productive than a large array on a tall mast.
-
Small lot, HOA limits, 80m–10m: what's the best compromise between an EFHW, a doublet and a vertical?
I'd argue for keeping the EFHW on the list, but with realistic expectations. The EFHW is attractive because it is one wire and a small box, and it comes up quickly. It resonates on 40, 20, 15 and 10 because those are harmonics of the 40m fundamental. The feedpoint impedance is high, in the thousands of ohms, hence the 49:1 or 64:1 transformer. Two things make or break it. First, there is no true balanced feed, so the coax shield and whatever counterpoise you give it become part of the antenna. Without a good choke on the coax, you can see a nice SWR and still be pushing a lot of current onto the shield. Second, the transformer's core and windings determine how much power you lose as heat. That is a minor concern at 5 to 10 W of FT8 or CW, but a more serious one at 100 W of continuous digital mode on a cheap core in a hot box. The OCFD (Windom-style) has a similar appeal, being fed about a third of the way along the wire, usually through a 4:1 balun, and covering 80/40/20/10 on harmonics. The pattern can break up on higher bands, and 15 and 12m are often a poor match without a tuner. The 1:1 current choke at the feedpoint is not optional there either. On the vertical, the radial system is the antenna as much as the vertical element is. A ground-mounted vertical with only a handful of radials wastes a lot of power in the ground. Many short radials, a dozen or more, laid on or just below the surface, give a noticeably better result. Alternatively, a few resonant elevated radials, four or so at a quarter wave each, work well. On a small lot the radials may be hard to place, but they don't need to be straight. Loaded verticals, such as short whips with a coil, are narrow-band and lossy at 80 and 40m, and efficiency suffers badly when the radiator is a small fraction of a wavelength. A magnetic loop is the best fit if you truly can't hang wire. It is quiet on receive, compact, and has a deep pattern null you can use. The tradeoffs are a very narrow bandwidth, so you retune for each change of a few tens of kHz on the lower bands, and efficiency that depends heavily on conductor size, joint quality and capacitor losses. On 40m and below, small loops give up a lot of efficiency compared with a full-size wire. Keep people away from the loop and capacitor while transmitting, because of the high voltages and the RF exposure close to the antenna. Whatever you choose, check the covenants as well as local rules. In the US, PRB-1 deals with state and local regulation, but it doesn't necessarily override private deed restrictions or HOA covenants, so the practical answer can depend on your own paperwork.
-
Planning a 24-hour EMCOMM field station: power budget, generator vs. LiFePO4, antennas, grounding and noise
The sequencing is right, but I'd add one thing to the power section: decide your failure behavior up front. If the battery is the primary source, what happens at the BMS cutoff? A LiFePO4 pack that disconnects abruptly can drop the radio, laptop and logging in the middle of a net. Put a low-voltage warning on a shunt monitor, and set a rule such as "at 20 percent remaining, we start the generator or shed non-essential loads." Distribution matters here too. A fused DC panel with separate circuits for the radios and for lighting/charging lets you drop the less important loads without touching the radio side. On the generator, one thing is easy to overlook. A lightly loaded inverter generator on eco mode can have worse regulation and sometimes more noise than one at a steadier load. If you only run it as a charger, test whether the charger or the generator's output is the source of the hash. Plug a small AM or SW receiver near the cord. Sometimes a few turns of the cable through a large ferrite fixes the noise, and sometimes moving the whole generator 30 ft farther away is the only cure.
-
Building HF wire antennas from scratch: wire, insulators, chokes, ladder line, radials, and checking the build in EZNEC or MMANA
On modeling versus real measurements, the biggest gap usually comes from the ground. A dipole at 30 ft over average ground can look quite different in a model than over very dry or very wet soil, and a vertical's feedpoint impedance depends even more on radials and ground quality. Try running the model with a couple of ground types, such as poor, average and good, and see how much the feedpoint resistance and pattern move. If the antenna's behavior swings widely across those, you know to rely on trimming against the analyzer rather than the exact model number. For traps and short loaded antennas, the model is helpful but less so for efficiency, since real coil and capacitor losses are not captured unless you add load elements with a realistic Q. In EZNEC you can put in resistive loss with the loads, and it makes a visible difference to gain. That is a fairer way to compare a trap dipole with a linked or fan dipole than looking at SWR curves alone. For the vertical, one more point is that radial count and length interact with the model's ground setting. If you simulate a ground-mounted quarter-wave with a perfect ground, you will see a gain that real soil will not deliver. Use a real ground with a radial set in the model, and compare 4, 16 and 32 radials to see how the efficiency changes.
-
Newly licensed? Let's talk first radios, first QSOs, and what you wish you'd known sooner
One mistake that trips up a lot of new operators is buying the cheapest handheld and then finding out it's hard to program from the keypad. Look at whether it works with free programming software such as CHIRP, and whether you can get a programming cable. Being able to load your local repeaters, simplex frequencies and a weather channel from a computer saves a lot of frustration. Also, before you key up, check your power setting, your offset and your tone. Most failed repeater calls come down to one of those. If you can hear the repeater but it can't hear you, the usual suspects are a missing CTCSS tone, the wrong offset, or too little signal from a bad antenna position. Try stepping outside or moving near a window, and ask a friend or club member to listen for you. And ID properly. Give your callsign at the required intervals and at the end of your transmissions, and keep it simple. You don't need a speech.
-
Chasing award credits without losing track: how do you organize DXCC, WAS, WAZ, WPX, IOTA and the rest?
I'd keep one master log and treat every award as a report generated from it. Most of the pain comes from having several partial copies that disagree. Store the full ADIF fields: band, mode, date and time in UTC, DXCC entity, CQ zone, state or grid where relevant, and any IOTA, POTA or SOTA reference. Then each award's tracker is just a filter. On LoTW mismatches, the usual causes are fairly mechanical. First, a small time difference or a wrong band. Second, a different mode that falls in another category; FT8 and similar modes are grouped as digital, but a mislabeled mode can still stop a match. Third, a callsign typo in one of the logs. Fourth, the other operator's LoTW location being set to the wrong entity, zone or state. That last one is outside your control, but it explains why a QSO can look perfect in your log and still not confirm for the award you need. One caution: LoTW is a confirmation source, not the award itself. You still need to apply, so check the program's current requirements before you assume a credit is already counted. For IOTA, POTA and SOTA, don't rely on LoTW at all. Check what each program wants for logs and references, because the confirmation path is different.