Everything posted by Admin_Lee
-
What makes a rig a keeper? Vintage tube gear vs. modern SDR in the shack
I'd argue the best setup is the boring one: a modern radio as the daily driver and a vintage piece for when you feel like operating slowly. Contesting or chasing DX on a crowded band is where an SDR's filtering and band scope really help. Working a casual AM net or a relaxed SSB ragchew on a classic receiver is a different pleasure, and it doesn't need to compete. One thing people overlook is the audio. Vintage receivers with a decent speaker often sound more natural on AM and SSB than a small modern rig's built-in speaker. An external speaker or good headphones narrows that gap a lot, so try that before deciding a modern rig sounds sterile. As for what makes something a keeper, I'd add serviceability. If you can find a manual, schematic, and replacement parts, it'll stay in the shack for decades. If it depends on a proprietary chip that's out of production, it's a bigger gamble, however good it sounds today. That applies to both vintage and modern gear.
-
SSB audio chain: mic gain, ALC, processor and EQ settings that help weak stations and DX get through
One point worth emphasizing is that ALC readings aren't comparable between radios. Some rigs show a lot of movement while still being linear, and others start distorting earlier. The manual's recommended range is the best starting point, and then it's worth confirming with an external look at the signal: a monitor scope, a second receiver, or a trusted report from a nearby station. On the processor, I'd treat it as a tool for specific conditions rather than a permanent setting. If the path is solid and the band is quiet, there is little to gain and a lot of naturalness to lose. If you're trying to be heard under a pileup or in marginal conditions, a small amount of compression can help, provided the ALC stays under control and you aren't amplifying room noise. A noisy shack or a fan in the background becomes a lot more obvious once compression is raised. For EQ, a low cut is usually the safest first change. It tends to make a mic sound less boomy without introducing a new problem. Boosting highs is where people tend to get into trouble, since a harsh, sizzly sound is tiring to listen to and can sound worse on a narrow receive filter.
-
Starting Morse from zero: Koch vs Farnsworth, which trainers to use, and how do you stop translating in your head?
On flashcards and mnemonics, be careful. Visual aids that show dots and dashes encourage you to translate, which is the habit you're trying to avoid. If you use flashcards, make them audio-first: hear the character, say or write the letter, then check. Ignore the dot-dash picture entirely. Mnemonics like word associations tend to work against you because they add a step between sound and letter. For the move from letters to head copy, a few things help. First, once you can recognize most letters, switch from random groups to short common words and then to callsigns. Your brain starts hearing chunks like "the", "and", and "ing" as units. Second, don't write everything down forever. Try a short session where you only listen and say or think the letters, then go back to writing. Third, if you miss a character, let it go instead of dwelling on it. Dwelling makes you miss the next two. A blank mark on paper and keep going is the standard advice. Fourth, as you get comfortable, try copying a letter or two behind the sound. This lets you recognize words instead of single letters. CW Academy, run by CWops, is worth a look for a beginner. It's structured as levels, starting with a beginner course for people who know nothing. You work with an advisor and a small group, with regular sessions and daily practice between them. The big advantage is accountability and feedback, plus a chance to hear real operators send. Check the CWops site for current class schedules, sign-up windows, and requirements, because they change. You can do it alongside LCWO practice. Plateaus around the low-to-mid teens in wpm are common. It's usually because you're still hearing letters instead of words. Keep sessions short and daily rather than long and occasional. Fifteen to thirty minutes with a rest in between is better than an hour once a week. Record your accuracy so you can see progress even when speed feels stuck. For confidence, try sending practice with a key or paddle so you hear your own timing, and listen to slow code practice transmissions or recordings before you go on the air. When you make your first contact, tell the other operator you're a beginner and ask them to slow down ("QRS"). Most CW operators are happy to oblige. A simple exchange of callsign, signal report, and name is enough to start. Lower your standards for the first few contacts, because the goal is to get used to the rhythm of a real conversation.
-
Technician to General: how would you split up the 35 Element 3 questions and the HF material?
I'd start with a baseline practice exam on day one, before reading anything. It shows you which subelements cost you points, and a lot of Technicians find that rules and operating procedures are fine while the circuit questions are the weak spot. After that, study by subelement and look at the explanation for every miss instead of just the right letter. The pool repeats concepts in different wording, so understanding why an answer is right is more durable than remembering its position. For the math, there are fewer calculation types than people fear. Ohm's law and power, series and parallel resistance, the dipole length formula, dB, and a few time-constant or reactance relationships cover most of it. Make a one-page cheat sheet of the formulas and rewrite it from memory until you can do it cold. Most calculations on the General test are simple enough to do without a scientific calculator. On vanity calls, upgrading doesn't change your callsign. You keep your existing call unless you apply for a different one, and vanity eligibility depends on your operator class and which callsigns are available. So it's not a study topic beyond the basic rules questions. Pass first, then look up the current ULS process and fee.
-
Is the band actually open? Comparing SFI, K index, beacons, WSPR and VOACAP for a quick answer
VOACAP is most useful if you treat its output as probability, not a yes or no. The reliability figure is about how often the circuit meets your required SNR over the month at that hour. A low number doesn't mean a path is impossible on a given day, and a high one doesn't promise it. The answers also change with your inputs: antenna gain at the takeoff angle, transmit power, the noise level for your location, and the required SNR for your mode. A CW or FT8 requirement is far lower than SSB. It also helps to compare it with beacons. If VOACAP says 20m should be strong to South America at a given hour but the 14.100 beacons from there are absent, the cause could be a geomagnetic disturbance, a flare, or just your local noise or antenna. That tells you whether to look at space weather or at your own station. For sporadic E, VOACAP won't help. Watch 6m beacons, spot clusters and other stations' reports, since those openings can start and vanish quickly.
-
Q codes and ham radio shorthand: what QRM, QRP, QSL, QTH, 73, K vs KN and RST actually mean
Q codes are three-letter groups that start with Q. They began as a compact way to exchange routine information in Morse. Each has a meaning as a statement and a slightly different meaning as a question. Add a question mark and QRL? asks "is this frequency in use?" Without it, QRL says "this frequency is in use." That dual meaning is why you hear "QRZ?" with a rising tone on voice. The ones you listed: QRM is interference from other stations, meaning human-made signals on or near your frequency. QRN is natural noise such as static crashes from thunderstorms. A quick way to remember it is that M is for man-made and N is for natural. Power-line noise and a neighbor's switching supply are usually described as noise too, but they aren't strictly "natural." QRP means low power, or "reduce power." A common working definition is 5 watts or less on CW and about 10 watts PEP on SSB, though conventions vary. QRO is the opposite: high power, or "increase power." It is often used jokingly when someone adds an amplifier. QRT means "I'm stopping transmitting," which in practice means shutting down the station for now. QRZ? means "who is calling me?" It is what you send when you heard someone but missed the callsign. It's also the name of a well-known callsign lookup website, so context matters. QSL means "I acknowledge receipt." On the air, a plain QSL means "understood." As a noun it means a confirmation of a contact, such as a QSL card or an electronic confirmation. QSO is simply a two-way contact, a conversation between stations. QSY means change frequency, as in "let's QSY to 7.140." QTH is your location, so "my QTH is Denver" or "what's your QTH?" QSB is signal fading, where strength rises and falls, which is very common on HF. QRL is the busy-frequency check. Before calling CQ on a frequency, listen, then send "QRL?" (or on voice, "Is the frequency in use?") so you don't talk over a weak station you couldn't hear. On voice: Q codes are used on phone, but mostly as nouns or verbs in casual speech: "What's your QTH?", "We're having some QRM," "I'll QSY up." Many operators prefer plain language on voice, and plain language is generally the better choice for public service and emergency communications, where clarity beats brevity.
-
Planning a multi-day field comms deployment: generator vs. LiFePO4 vs. solar, and where noise and grounding bite
For checklists, I'd separate setup into phases so nothing important gets skipped when people are tired: site survey, safety and power, antenna, station, and then a comms check. On the survey, walk the antenna fall zone and look up for lines and branches. A mast should have a clear radius larger than its height plus margin, so it can't reach power lines if it fails. Also check ground firmness, drainage, and wind exposure for the tent. Water pooling under a shelter wrecks gear, and a tarp or pallet under power distribution helps. Weights matter more than stakes on pavement. On grounding, it helps to say what you want it to do. A short ground rod at a field site won't protect you from a lightning strike, and it usually won't fix RF noise either. The practical goals are bonding the station equipment together so a fault doesn't leave different metal at different potentials, following the generator manufacturer's instructions for its grounding and neutral bonding, and reducing common-mode current on the feedline. A choke at the antenna feedpoint and another near the shack entry often do more for noise than a ground rod. If thunder is audible, lightning is close enough to be a threat. Disconnect the coax, take the antennas down if you can do so safely, and get people into a vehicle or a substantial building. Nothing about a field setup makes it safe to stay at the mast. Coax choice depends on band. At HF, losses on a modest run of RG-8X or similar are small and weight is the main concern. At VHF/UHF, thin coax costs more signal than most people expect, so use a lower-loss cable for any long run or keep the antenna close to the radio. Whatever you choose, label both ends, put drip loops where cable enters the shelter, and tape or strap connections so the first rain doesn't find them. On teardown, reverse the order: power down, disconnect antennas, lower masts, then coil cables and stow them with the correct labels, so the next deployment starts with known parts.
-
Where do I actually operate? Band plan vs. FCC rules, band edges, and calling frequencies from 160 m to 33 cm
I'll pick up with VHF/UHF, digital conventions and the international side. For VHF/UHF, the key idea is that the bottom of each band is for weak-signal work (CW and SSB, plus modes like FT8) and the FM activity lives higher up. The commonly used calling frequencies from the ARRL band plan are these. Confirm against the current plan, because regional plans can add local variations. On 6 m, 50.125 MHz is the SSB calling frequency, and the DX window sits just below it around 50.100 to 50.130. 52.525 is the FM simplex calling frequency. On 2 m, 144.200 is the SSB/CW weak-signal calling frequency and 146.520 is the national FM simplex calling frequency. 70 cm uses 432.100 for weak-signal calling and 446.000 for FM simplex. On 33 cm, 902.100 is the weak-signal calling frequency. Activity there is thin, so a lot of operators arrange contacts on a lower band first. Calling frequencies are for making contact, not for holding a conversation. Establish contact, then move off to another simplex frequency so the calling channel stays free. Most repeater outputs on 2 m and 70 cm are in segments set by the band plan, with standard offsets (commonly 600 kHz on 2 m and 5 MHz on 70 cm), but your local frequency coordinator decides what actually gets used in your area. On digital: FT8, FT4 and similar modes cluster around specific dial frequencies, such as 14.074 for FT8 on 20 m, 7.074 on 40 m, 3.573 on 80 m, 50.313 on 6 m and 144.174 on 2 m. These are community conventions, not FCC regulations, and not exactly the same thing as the formal band plan. They still fall inside the data segments for the classes that may use them, but verify your own privileges, especially near 40 m, where the General CW/data and phone segments are distinct. Two cautions on the upper bands. On 70 cm, there are geographic restrictions in the US near certain government radar installations and near the Canadian border for part of the band, so read Part 97 if you're in those areas. On 33 cm (902 to 928 MHz), amateur radio is secondary to other users, and it's shared with unlicensed Part 15 devices, so you may deal with noise and interference. Also, 33 cm is mainly a Region 2 allocation, so don't count on being able to use it overseas. For international allocations, the world is split into ITU Regions 1, 2 and 3, and the US is in Region 2. The differences affect what you hear and what you can work. 40 m is 7.0 to 7.3 MHz in Region 2, but only 7.0 to 7.2 in Regions 1 and 3, which is why you'll hear broadcast stations above 7.200 in Europe and Asia and why DX often operates split. 80 m is 3.5 to 4.0 in Region 2 but 3.5 to 3.8 in Region 1. 70 cm is 430 to 440 in Region 1 against 420 to 450 in Region 2, and 2 m is 144 to 146 in Region 1 against 144 to 148 in Region 2. 6 m isn't available in every country either. If you operate abroad, the host country's rules apply, not just your home license's privileges. Check whether an agreement covers you, such as CEPT recommendations for many European countries or the US's IARP arrangements with some others, and confirm the allowed bands, power and any required prefix or identification. The rules for 60 m in particular vary a lot by country. Finally, treat everything above, including mine, as a starting point and confirm it against the current FCC Part 97 and the ARRL band plan and privileges chart. Both get updated.
-
Dual-band mobile rigs: FTM-500D vs ID-5100A vs TM-D710G, plus how to wire and run them properly
On noise: first decide whether it is coming from the vehicle or from the radio's own wiring. Listen on a quiet frequency with the squelch open. Compare engine off, ignition on, and engine running at various speeds. Whine that rises with RPM points to the alternator or its wiring. Ticking points to ignition or injector noise. Hash that sounds like a hiss is often caused by LED lighting, DC-DC converters, USB chargers and dash cameras. Unplug accessories one at a time and see what changes. Ferrite chokes on power leads can help, but fixing the source is usually better than filtering around it. The antenna matters more than the radio. A roof-mounted NMO antenna with a good ground plane gives better results than a trunk-lip mount with a poor ground. Use coax that suits the run length, since UHF loses more in cheap thin cable than VHF does. Check SWR on both bands, because a dual-band antenna can look fine on 2 m and poor on 70 cm if the mount is not bonded to the body. Etiquette is mostly common sense. Driving comes first, so use a hands-free setup or pull over for anything that needs attention. Listen before transmitting, keep your calls short, and say your callsign clearly. On a busy repeater, you can say "mobile" in your call so others know you may have to pause. Do not hold a repeater for long conversations while you are fiddling with settings, and turn the volume to a reasonable level so a wide-open squelch tail is not disturbing everyone in the car.
-
Part 97 compliance check: ID timing, third-party traffic, power, RF safety, remote control and license renewal
I'll cover 5 to 8, and I'd add a note on responsibility. Under §97.103 the station licensee is responsible for the proper operation of the station, and the control operator can be held responsible too. A lot of 'I didn't know' situations land on the licensee. RF exposure: §97.13(c) requires you to evaluate your station for compliance with the FCC's RF exposure limits when it is above certain power thresholds, and exemptions depend on band and power. The thresholds were revised a few years back, so don't use an old table. In practice you work out your highest-duty-cycle mode, your antenna height and gain, and your distance to where people can be. Then you use a calculator or the OET Bulletin 65 Supplement B guidance to see whether any area exceeds limits for controlled or uncontrolled environments. If it does, you move the antenna, lower power, restrict access to that area, or use a mode with a lower duty cycle. Keep notes on how you did the evaluation, since you may need to show your work. Near-field exposure from low or loaded antennas, rooftop mounts and attic antennas is where hams most often have issues, because the limits apply to where people actually are, not to the antenna's far field. Spurious emissions are in §97.307. The numbers vary by frequency range and power. For HF, spurious emissions need to be at least 43 dB below the mean power of the fundamental for modern transmitters. For VHF and UHF the required suppression is stronger when mean power is above 25 W. Check the actual paragraph for your band. Rigs sold as amateur transceivers are generally built to meet these specs, but a misadjusted amplifier, overdriven stage, or poorly filtered third-party amp can change that. The easy checks are clean audio and ALC settings, no flat-topping, and a low-pass filter on HF amps where appropriate. Splatter, key clicks and out-of-band emissions can be violations even if the harmonic suppression is fine. Good engineering practice is also a requirement under §97.101(a). Control types are in §97.109. Local control means the control operator is at the station. Remote control means the control operator is at a control point away from the transmitter and uses a link, which can be radio, internet or phone. Automatic control means the station operates without a control operator at a control point. The rules limit automatic control to specific cases such as repeaters and certain data stations. A remote base or auxiliary link is an auxiliary station under §97.201, which has frequency restrictions and requires a control operator with appropriate privileges. Remote control rules in §97.213 add requirements about protecting the station from unauthorized operation and being able to shut the station down. If your club repeater is automatically controlled, the trustee needs a way to turn it off. Enforcement is handled by the FCC's Enforcement Bureau. Responses range from advisory or warning letters to formal citations, forfeitures (fines), license suspension or revocation, and in serious cases referral to the Department of Justice. There are also volunteer monitoring programs run with hams that report apparent problems and can send educational notices. Cooperating, correcting the problem and documenting the fix generally helps, while ignoring notices makes things worse. License term and renewal: an amateur license is valid for 10 years. You can renew in the 90 days before expiration through the FCC's ULS. If you miss that date, there is a two-year grace period in which you can still renew, but you cannot transmit until the renewal is granted. After the grace period ends, you need to retake the exam. Keep your mailing address and email current in ULS, because the FCC contacts licensees that way and a bad address can create real problems. Fees have changed over the years, so check the current FCC fee schedule instead of copying a figure into the handout.
-
POTA basics and field habits: 10 QSOs, park references, spotting, two-fers and logging, what trips people up?
On logging and rules, the biggest trap is assuming every park works the same. A state park, a national forest and a wildlife refuge can each have different rules about hours, antennas, vehicles and where you can set up. Read the park page and the agency's notice before you go, and keep a screenshot or note if cell coverage is poor. It also helps to know the boundary. A parking area can be in the park while the picnic spot across the road is not, so check a map if it isn't obvious. For two-fers, put the extra work in before the outing. Write down both references, confirm that your logger can store them correctly, and decide how you will announce them. Hunters often like to know all references so they can log each one, but be clear and don't turn the exchange into a long conversation. After the outing, upload promptly and check the POTA site for any errors. Matching your callsign format, UTC date and park reference to what you actually operated will save you from corrections later.
-
Building an HF shack around a 100 W rig: what matters more than the radio model?
I'd put the antenna system ahead of all of it, but your point about common-mode current is the one that gets overlooked most. A lot of new stations end up with RF on the coax shield, a USB interface resetting during transmit, and a hum or buzz on the audio. The fix is often a good choke at the feedpoint (a suitable ferrite mix for the bands in use, enough turns or enough cores to give high impedance) plus a second one where the line enters the building. It costs far less than a new rig. On grounding, I'd add that a ground rod in the yard doesn't make an HF ground. The point of the rod is safety and surge protection, and what matters most is that everything is bonded so no piece of gear sits at a different potential from another. For anything involving the mains panel, follow local code and have a qualified electrician check it. Surge protectors at the entry plate are only as good as their connection to that bonded system. On radios, the receiver architecture matters for crowded bands more than the headline power numbers. Direct-sampling radios like the IC-7300 and IC-7610 have excellent dynamic range with well-managed gain settings, but a good band-pass filter becomes more helpful the moment you have a nearby second transmitter or a strong local broadcaster.
-
Studying for the Amateur Extra (Element 4): which topics deserve the most time, and what do the full privileges get you?
On the study question, I'd split the pool into formula questions, concept questions and figure questions, because each wants a different kind of practice. Formula questions are the cheapest points. Op amp gain is a good example: an inverting stage is -Rf/Rin, a non-inverting stage is 1 + Rf/Rin. Q is reactance divided by resistance for a series circuit, and bandwidth is center frequency divided by Q. Once you have worked a few of each by hand, the numbers in the pool stop looking intimidating. The same goes for dB arithmetic, impedance transformation with quarter-wave sections, and the FM modulation index (deviation divided by modulating frequency). Concept questions are about knowing what a circuit does and why. Examples are the difference between Class A, AB, B and C amplifier operation, why a Colpitts, Hartley or Pierce oscillator is built the way it is, and what shape factor tells you about a filter. Butterworth, Chebyshev and elliptical filters trade passband flatness against how sharply they roll off, so understanding that trade-off helps with several questions at once. Figure questions are mostly the Smith chart and a few circuit diagrams. These look scary but are very learnable. The center of the chart is the matched point, circles of constant resistance are tangent at the right-hand edge, the upper half is inductive reactance, the lower half is capacitive, and one trip around the outside is half a wavelength. Work through the chart questions with the actual figure in front of you until reading it is automatic. One tip: after every practice session, write down why a wrong answer was wrong, not just the correct letter. That is what separates understanding from recognition, and it carries over to the questions that are worded slightly differently from the pool.
-
Getting clean, effective SSB audio: mic gain, ALC, compression, EQ and bandwidth for weak-signal and DX work
On the DX side, I think people over-process because they assume the DX station needs "louder." Often the real issue is that the other end hears your audio mixed with QRN and a pileup, so what you want is intelligibility. A low-cut around the 200-300 Hz region and a slightly narrower transmit bandwidth can help your voice stand out without piling on compression. For receive, I would separate two jobs. First use the 2.4 kHz filter or something narrower to remove adjacent signals, then adjust passband shift until the voice sounds natural. Noise reduction comes last, because heavy NR can make weak speech sound watery and hide the syllables you are trying to copy. When trying to work a weak station, listen to their rhythm, call when they stop, and keep your exchange short. Sending your callsign cleanly once or twice is better than sending it several times with a long preamble.
-
Digital mode setup baseline: time sync, audio levels, CAT, and what decode thresholds actually tell you
On the question of thresholds, I'd stress one practical point: the dB figure in the decode list is a signal-to-noise estimate in a 2500 Hz reference bandwidth. It is not the S-meter and does not map directly to it. A signal can decode at a very low number while your S-meter does not move, because the S-meter reflects total power in the receive filter and the decoder works on a narrow tone pattern. For interface setup, a quick sanity test is to transmit into a dummy load, check the output on a wattmeter and confirm the ALC is not moving. Then lower the audio gain until the power just begins to drop, and back off slightly from that point. After that, check your own signal on a remote receiver, such as a web SDR or the PSK Reporter map for your callsign, and see whether other stations are reporting a clean decode. If the reports vary a lot from one cycle to the next, look at timing, power supply sag, or RF in the shack before changing software settings. For Winlink and VARA, the same discipline applies: listen first, since these modes can run for a long time and a busy frequency makes the problem worse for everyone.
-
Sequential call vs. vanity: how callsign groups, ULS filing and holding rules fit together (US)
Worth adding some points about holding a call, since people assume it's owned like a domain name. It isn't. The license has a ten-year term, and you can renew starting 90 days before expiration. If it lapses there is a grace period where you can still renew, but you aren't allowed to transmit until the renewal is granted. After the grace period ends, the call goes into that waiting period and later becomes available to others. If you want to keep a particular call, set a calendar reminder for the renewal window. On identification, the call on the air is whatever your license shows, or an authorized special event call if you're running one. Say it at least every ten minutes during a contact and at the end. Prefixes and suffixes like /P or /M are optional in the US, and a portable designator isn't required just for operating away from home, though they're common as courtesy and in logs. If you operate abroad under a reciprocal arrangement such as CEPT, you need to follow the local rules, which normally means putting the country prefix in front of your call. Check the country's requirements before you go. One more thing on clubs: the trustee is the person the FCC treats as responsible for the club station. If the trustee moves on, the club should update the license and not just leave a name on the record. A stale trustee entry is one of the most common problems with club callsigns.
-
Planning a contest year: which major events fit your station, and what to get right on exchanges and logs
One more thing to add on the rules: read the category definitions closely before you operate, not just before you submit. Single Op Low Power versus High Power, assisted versus non-assisted, and the rules on spotting networks can affect which category you can enter. Different contests also define power limits and operating-time limits differently. Some events have off-time requirements, and the rules for remote operation and multi-transmitter stations can vary too. For Field Day, remember that your class depends on the number of transmitters and the type of station, and the section comes from the location of the operation, not your home address. Winter Field Day also has its own category letters, so don't assume the ARRL Field Day pattern carries over. The same applies to state QSO parties, where the county abbreviations and the rules for mobiles and out-of-state stations differ by event. For logs, save your raw log and a copy of the Cabrillo file before uploading, and keep the confirmation email or screen. If the sponsor publishes a log-received list, check that your call appears. For VHF contests, double check the grid square entries, since one wrong character shifts a multiplier. If you're unsure about a rule, email the contest sponsor before the event rather than guessing.
-
Building a QSL workflow: LoTW first, then Club Log OQRS, bureau and direct cards for the rest?
On the card design question, readability beats looks. A bureau card gets handled, sorted and stamped, so the QSO details should be big enough to read at a glance. Leave plain white or light space for the data fields. Dark photos behind the writing area look great on screen but are annoying to fill in, and a missing detail can make the card useless for confirmation. A practical checklist is your callsign in large type, the other station's callsign, UTC date and time, band or frequency, mode, RS(T), and a "2-way" or "please QSL" field. Add your grid, the QSL route, and your name or location if you want. The common size is about 3.5 by 5.5 inches (roughly 89 by 140 mm). If you use a QR code, treat it as an extra, not the only place the information lives. For direct requests, put your QSO details in a note or on the card, include a self-addressed return envelope, and follow whatever postage instructions the station lists. Many DX stations ask for no callsign or radio reference on the outer envelope, so a plain envelope is usually safer. Also avoid International Reply Coupons unless the station says they are fine. They can be hard to redeem in many places now. Finally, expect different timelines. LoTW can confirm shortly after both sides upload. OQRS and direct cards depend on when the operator uploads logs and sends cards, and the bureau can take far longer. A QSL tracker, even a plain spreadsheet with date requested, route and status, saves you from asking twice.
-
One logging workflow for contests and daily operating: N1MM+, WSJT-X, Log4OM, ADIF, Cabrillo, LoTW and QRZ
I'd add dupe handling to the list, because it behaves differently in the two places. In a contest, dupe checking follows that contest's rules, usually by band and often by mode. Your everyday logger probably has looser rules, so a contest QSO might look like a duplicate of an earlier casual contact once merged. Check that the import doesn't delete or skip records just because call and band match. For WSJT-X, the decode and log flow is a little different. WSJT-X can write its own ADIF log, and it can send logged QSOs by UDP to other programs. A general logger can listen for those. Decide which one is the source of truth and don't import the same QSO from both the UDP feed and the ADIF file. If you also run N1MM+ for a digital contest, read its documentation on WSJT-X support, as the setup depends on the version and contest. For club use, a shared database can work, but separate files per operator are easier to audit. Merge them after the event, then submit a single Cabrillo. Whoever submits should confirm the callsign, category and operator list against the contest rules before sending, because those header fields are easy to get wrong and hard to fix later.
-
Go-kit design for SOTA/POTA: EFHW or linked dipole, which pole, and how to power it?
Weather is the part I'd put at the top of the list. Before leaving, look at the forecast for the specific elevation or area, and set a firm rule for yourself. A common approach for lightning is the 30-30 rule: if the time from flash to thunder is 30 seconds or less, take shelter, and wait 30 minutes after the last thunder before returning. On a summit, that means being ready to drop the antenna quickly, so avoid a setup you can't take down in a couple of minutes. On power, one more LiFePO4 point: make sure the pack has a BMS and that you know what it does at low-voltage cutoff. Some packs shut off abruptly, which can cause a radio to drop out mid-QSO. A small voltmeter or a radio with a voltage readout helps you stop before the pack does. For logging, a paper backup is still worth carrying even if you plan to use an app.
-
Getting from 5 to 20 WPM: what actually moves the needle, and how do you break a plateau?
On the plateau question, it helps to work out what kind of plateau it is before changing the plan. If you are missing specific characters, that is a recognition problem, and a Koch-style drill on just those characters is the answer. If you recognize every character in isolation but fall apart in running text, that is a buffering problem. You are still decoding letter by letter and cannot hold the previous letters while the next ones arrive. Drilling words and callsigns attacks that directly, because it forces you to chunk. One concrete tip on head copy: when you stop writing, leave the first few words or letters unrecorded and just listen. Most people find that the first thing to go is the urge to write each letter, and they get lost when they miss one. Practice letting a missed character go and picking the thread back up with the next word. Real QSOs are full of missed characters, and recovering quickly is half of copying. On keyers: if you are building speed on iambic paddles, record your own sending and listen back. Spacing errors that feel fine while you send often sound uneven on playback, and that is a good way to catch problems before they become habits.
-
Learning Morse code from scratch: how do Koch, Farnsworth, LCWO, G4FON and CW Academy fit together?
Koch and Farnsworth aren't opposites. They answer different questions. Koch is about what you learn and in what order. Farnsworth is about how the timing is stretched. With the Koch method you start at your target character speed, commonly somewhere around 18 to 20 WPM, with just two characters. You copy random groups of those two until you're getting roughly 90% right, then add one new character. The point is that you only ever hear characters at real speed, so you learn each one as a whole sound (a rhythm, not a count of dits and dahs) and never have to translate. Farnsworth means sending characters at a fast speed but adding extra space between characters and words so the overall speed is slower. Most Koch trainers let you do both: fast characters with generous spacing, then you tighten the spacing as you improve. For tools, they're variations on the same idea: LCWO (Learn CW Online): a free browser-based Koch trainer. You can set character speed and effective speed separately, and it tracks your progress. Beyond the lessons it has other drills such as callsigns, abbreviations and plain text. Being browser-based, it works on whatever computer you have.G4FON's Koch trainer: a free downloadable program built around the same idea. It's good if you'd rather run something locally than depend on a website. Check the current download page and system requirements, since it's a desktop program.Morse Trainer apps: several apps share similar names, and quality varies. Look for ones that send real audio at adjustable character and effective speeds and let you control the tone. Avoid any that mainly show you a chart and quiz you on dots and dashes.CW Academy: run by the CWops club. It's structured classes with volunteer advisors and daily practice assignments, with levels from beginner upward. It adds what software can't: a schedule, accountability, and someone who can tell you what you're doing wrong. Check the CWops site for how and when to sign up, as availability changes.A reasonable first-month plan is 15 to 30 minutes a day, once or twice, rather than one long weekend session. Pick a tone you can listen to comfortably (many people settle between roughly 500 and 700 Hz). Don't look at a chart while you practice. Learn each character by sound only, and when you're unsure, guess rather than peek.
-
Studying for the Technician (Element 2) exam: how to use the question pool without just memorizing letters?
On using the pool without just memorizing letters, there's one trick. When you miss a practice question, don't only note the right answer. Read each wrong option and say why it's wrong. Distractors in this pool are often real facts that answer a different question. That turns one missed question into three or four facts, and it also stops you from learning answer positions, since many practice tools shuffle the order. Some areas worth extra attention: License terms: Technician licenses are issued for 10 years, and there's a grace period after expiration during which you can renew without retaking an exam. Know the difference between renewing and relicensing, and know the station identification rules. You identify at the end of a communication and at intervals during a long one. Privileges: Technicians have all amateur privileges above 50 MHz, which covers 6 m, 2 m, 1.25 m, and 70 cm. There are also limited HF privileges. Learn exactly which segments and modes, because questions can be specific about them. Repeaters: Understand input versus output frequency, the offset (commonly 600 kHz on 2 m, and 5 MHz on 70 cm), and CTCSS or PL tones for access. A repeater listens on one frequency and retransmits on another. Be able to explain what "offset" means and why a repeater won't respond if you're missing the tone. Know that you can use simplex when you can reach the other station directly and that doing so keeps the repeater free for others. RF exposure and safety: Know that the FCC sets maximum permissible exposure limits and that the amount of exposure depends on power, frequency, antenna, and distance. Also know basic electrical safety: lightning protection, tower and antenna work away from power lines, and proper grounding. For practice tests, take several full 35-question tests and track scores by section. Many people feel ready when they consistently score well above the passing mark rather than just at it, since test-day nerves and unfamiliar wording can cost a few points. Look at the weakest section, study it, and retest.
-
Dead rig triage: working out no RX, no TX and SWR protection faults before touching a screwdriver
On blown finals, I'd be strict about the dummy load and the first power-up. Replacement devices can die in a fraction of a second if the bias is wrong or the stage is oscillating. A bench supply with a current limit, a wattmeter and a bias set to the manual's idle current gives you a chance to catch problems before the new parts do. One caveat on SWR protection: a radio that shows high SWR on a dummy load may not have a detector fault. A dummy load that is not truly 50 ohms at the test frequency, a bad adapter, or a poorly seated connector can all cause it. Test with a known-good load and a short jumper first, then look at the sensing circuit. On noise, don't blame the radio until you check the external environment. Switch-mode supplies, LED lighting and poor grounding can produce noise that looks like a failing receiver. Running the rig from a linear supply or battery is a quick way to separate a radio fault from a noise source in the shack. If the noise stays with the radio on battery with the antenna removed and a dummy load connected, then start looking at internal causes, such as dried-out filter caps or a bad regulator.
-
2027 York Hamfest
until
The York Hamfest is a long-running amateur radio hamfest in Glen Rock, PA, with indoor, covered outdoor and tailgating spaces. It runs rain or shine, and parking is free. Vendor setup starts at 6:00 AM that morning.Location: Glenview Alliance Church, 10037 Susquehanna Trail S, Glen Rock, PA 17327, USA Organizer: York Hamfest Foundation (supporting two local amateur radio clubs) Source: Event information