Everything posted by Admin_Lee
-
LoTW, eQSL, Club Log OQRS, bureau or direct: how do you decide which QSL route to use for which contact?
A few points on the card design side, since they affect whether a card gets answered. The essentials are both callsigns, date and UTC time, band or frequency, mode, and signal report. Put them in a clear block and leave room for the receiving station's details. For a bureau card, standard postcard-ish size (about 9 x 14 cm, or 3.5 x 5.5 inches) is the common convention and is easy to sort. A fancy photo on the front is nice, but a cluttered back makes the QSO data hard to read and the manager's job harder. It also helps to put your grid square, CQ and ITU zones, and any IOTA or award references on the card. Those are the details people want for awards, and having them printed saves a lot of correspondence. If you use a QSL manager, say so clearly on the card and on your online profile, so requests go to the right place. On timelines, I'd plan around this: electronic confirmations are quick once both stations upload; direct replies depend on distance, local post, and how fast the operator or manager answers; bureau cards can take a long time with no real guarantee. Keep a simple spreadsheet or log field recording when you sent each request and by which route, so you aren't guessing months later whether to resend.
-
Breaking pileups on rare DX: split, timing, tailending and where to actually call
Two more areas where the thread could go: low-band conditions and the tools around the pileup. On 160, 80 and 40 metres, the biggest gains often come from receive improvement, not from more transmit power. A rare entity on top band might be audible only in very weak peaks, and a receive antenna such as a Beverage, loop or other directional system can be the difference between hearing the DX and not hearing them. If you cannot hear them through the noise, you cannot tell whether the DX is calling you. Grey-line timing matters too: sunrise and sunset at both ends of the path often create the best short windows, so predicting those windows is worth the time. Check where the DX is listening, since on the low bands operators often use the recommended DX windows and may also listen outside them in split. For tools, a DX cluster spot is a hint, not a guarantee. Spots can be wrong, outdated, or busted, and a spotted frequency may be the DX transmit frequency while the actual listening range is somewhere else. Check the DX station's information page or announcements for the listening plan. For preparation, Club Log's tools can help you see how wanted an entity is, check which bands and modes you still need, and, where the DXpedition has chosen to publish them, check whether you appear in the online log after a contact. Most DXpeditions that use Club Log publish a log search so you do not have to call repeatedly to be sure of a QSO. The etiquette side comes down to a few habits. Do not call when the DX is not listening for your region. Do not use spotting as a replacement for listening. Do not ask for repeats of information that was just given. Once you have worked the DX on that band and mode, move on to let someone else have a chance, unless the DX is asking for extra contacts. For DXpedition planning from the operator side, the important thing to remember is that the operation has limited time, power and antenna capacity, and a well-behaved pileup makes the whole team's schedule more likely to be completed.
-
Part 97 compliance Q&A: station ID, third-party traffic, power, RF exposure, remote control and license renewal
Here is the technical and administrative half. RF exposure (§97.13(c) and the exposure limits in Part 1): you're responsible for evaluating whether your station meets maximum permissible exposure (MPE) limits. §97.13(c) has a table of power thresholds by band. Below the threshold, you generally don't need a routine evaluation, though you still have to comply. Above it, you need to evaluate, which means calculation, modeling or measurement. Duty cycle and mode matter, as do antenna height and distance to where people can be, including neighbors. The FCC's OET Bulletin 65 and its amateur supplement are the usual reference, and many online calculators implement it. Treat a calculator as a starting point, because ground reflections and nearby structures can change the picture. Spurious emissions (§97.307): emissions must be minimized, and they're limited to specified attenuation levels that differ by band. HF stations have an attenuation requirement below 30 MHz, and VHF/UHF stations have stricter requirements depending on power. Check the exact numbers in the section, because they depend on power and when the transmitter was installed. Common causes of problems are overdriven amplifiers, splatter from excess audio or ALC, and missing low-pass filtering. A spectrum analyzer or a good SDR with an attenuator and a proper sampling setup can show you harmonics. Also look at §97.315 if you're building or selling amplifiers, since there are certification rules. Control and auxiliary operation: every transmission has a control operator, and the station licensee is responsible too (§97.103). The three control types are local, remote and automatic (§97.109). Remote control means a control point where the operator can terminate transmissions. Automatic control is limited to certain station types, such as repeaters, auxiliary stations and some data stations. An auxiliary station (§97.201) is point-to-point linking between cooperating amateur stations, for example linking repeaters or feeding a remote receiver. It is restricted to certain VHF and UHF-and-above segments. Repeaters (§97.205) are also restricted to specified bands and still need a control operator who can shut them down. Enforcement: the licensee has to make the station available for FCC inspection (§97.103(c)). The FCC's Enforcement Bureau can send warnings or Notices of Violation, and for more serious cases can propose forfeitures or start license revocation or modification proceedings. Volunteer monitoring programs exist, but their reports are informational, and the FCC itself decides on enforcement. License term and renewal: an amateur license is normally valid for 10 years. You can renew within 90 days before it expires. After expiration there is a grace period of two years during which you can still renew without re-testing, but you can't transmit until the renewal is granted. After the grace period ends you'd have to re-qualify through the exam process. Keep your mailing address and email current in the FCC's ULS database, because renewal and enforcement notices go there. Fees and filing mechanics change, so check the FCC's current instructions before filing. This is a general summary, not legal advice. For anything involving a real violation notice or a business use case, read the exact text of the rule or ask the FCC.
-
Newly licensed? Let's talk first radios, first QSOs, and what you wish you'd known sooner
For anyone thinking about their first club meeting, it's fine to go as a listener. Many clubs have a mix of people: contesters, emergency communications volunteers, satellite fans, antenna builders, and people who haven't turned on a radio in a year. Ask what the club actually does, whether there's a weekly net, whether they run Field Day or similar events, and whether anyone offers help with installs and antenna projects. If you're curious about contests, you don't need to treat them as a serious competition on day one. Many events let you make a handful of contacts, learn the exchange and log what you hear. Listening first is a good way to pick up the rhythm: call sign, exchange, confirmation, move on. Just be sure you know the rules for your license class and band before transmitting. And for HF, safety is part of getting started. Keep antennas well away from power lines, don't work on a roof or mast alone, and get advice on grounding and lightning protection before you put up anything permanent. A club member who has done it before is worth more than another gadget.
-
Dead rig on the bench: what's your order of operations for no TX / no RX faults?
I agree with starting at the supply, but I'd go further on ripple and noise. A DMM only tells you the average voltage. Put a scope on the rail, AC-coupled, and look for ripple, spikes and a rail that dips when the radio switches to transmit. Many strange problems, like intermittent resets, hum on audio, birdies and a noise floor that changes when you touch things, come from a poor supply or filter capacitor and not from the radio's RF circuitry. If the rig is noisy only on one supply, try it on a linear supply or battery. If the noise disappears, the culprit is probably a switching supply or its wiring. If it stays, try moving the rig away from LED lamps, chargers and computers, and see whether ferrites on the DC lead make a difference. On the bench, remember that the scope ground clip is the same as mains earth on many scopes, so be careful where you clip it. In mains-powered gear without an isolation transformer, a grounded probe on the wrong node can cause damage. On capacitors, in-circuit ESR meters are useful, but a low reading in-circuit can mislead if parallel paths exist. If a cap looks suspicious, lift one leg before you condemn it.
-
Nets and special event stations: how do you choose, check in, and keep a clean log?
On logging: it helps to treat net check-ins and special event contacts as different categories, even if the same software holds both. Net check-ins are often short and don't always count as a normal confirmed contact. Special event contacts usually need exact UTC time, band, mode, and the full call sign of the event station, including any suffix, because that is how the sponsor matches your entry for the certificate. A field for net name or event name in your notes saves a lot of searching later. Another tip for special events: read the sponsor's instructions about how many contacts count. Some count each band and mode separately; others allow only one contact per station. Working the station once on a clean band and then going back for a different mode can be worth more than repeated calls on the same frequency.
-
Sequential vs. vanity callsigns: how the groups work, what to verify in ULS, and who can hold what
On club calls, the trustee point deserves more attention. The club license is only as stable as its trustee, so make sure the club's records name an alternate who is licensed and willing to take over. If the trustee's license lapses or the trustee dies, the club call can be affected, and the administrator will want proof of who now represents the club. For special event 1x1 calls, apply early. Several clubs can want the same call, and the volunteer coordinators handle requests by their own procedures. Remember the call is for the event, not a standing license. On the air, ID with the special call during the event, and make sure every control operator knows the ID schedule. Logging who operated under which call matters if QSL requests come in later. For lookups, check ULS first and treat QRZ or similar sites as a convenience. If something looks wrong, such as an old address or a missing class, go back to ULS and fix the source record rather than editing a profile page.
-
Getting ready for activation: how do you split ARES, RACES, SKYWARN, CERT and ICS training so you're useful on day one?
Adding to the go-bag question, I'd split it into what you need to get on the air and what you need to stay functional for a long shift. For the radio side: a handheld with spare batteries or a battery case, a better antenna than the stock rubber duck (a roll-up J-pole or a mag-mount for a vehicle), a short length of coax with adapters, a headset or earpiece for noisy rooms, and a charger that works from 12 V. For the paperwork side: a copy of your license, your agency or group ID, a printed frequency plan with primary and backup channels, blank ICS-213 forms, pencils (they work in the wet), a notebook for a log, and a clipboard. For personal needs: water, food, medications, a headlamp, hi-vis vest if your group requires one, weather-appropriate clothing, and a phone charger. Most guidance recommends preparing to be self-sufficient for a period so that you are not a burden on the people you are supporting. Ask your EC what duration your group plans for. One more caution on deployment. Check your group's rules on self-deployment. In most organized programs the expectation is that you wait to be activated and report where you're told, rather than showing up at an EOC or incident on your own. A call-out message, a check-in point and a clear chain of command usually matter more than any single piece of gear. After an exercise, look at what failed: dead batteries, unreadable forms, an unprogrammed channel, or confusion over who was in charge. Those are the things to fix before an actual activation.
-
SSB audio setup: mic gain, ALC, compression and bandwidth for clean signals and weak-signal work
One thing I would add to the ALC point is that the setting depends on your whole chain. If you run an amplifier, set your drive power first so the amp is not pushed beyond its rating, then adjust mic gain and processor around that. Many clean-signal problems show up only when an amplifier is added, because a transceiver that sounds fine on 100 W can distort badly once its output drives a linear past its comfortable level. If your radio has an adjustable output limit for the amp, use it rather than trying to control power with mic gain alone. For checking splatter, a second receiver or SDR showing your signal on a spectrum display is useful, as long as it is protected from the transmitter. Compare your signal width with a clean station on a similar band. If your signal shows sharp skirts a few kHz away when you speak loudly, back off the mic gain and processor before blaming the band.
-
Making Field Day and SET Count: Building Disaster Comms Drills That Produce Useful After-Action Reports
Worth separating two audiences for the report. The members want the lessons, written plainly: this link failed, this form confused people, this role had no backup. The served agency wants a one-page summary showing what capability was demonstrated and what they might do differently. Trying to serve both in one document usually makes it too long for the agency and too thin for the members. On Field Day, one practical suggestion is to treat the Saturday-night shift change as a mini-exercise. Hand over a station with a written log, open traffic, and current status, and see what gets lost. Shift handoff is where a multi-day deployment tends to break down, and Field Day is a low-stakes place to find that out. Also, if you can't get an agency person to the site, at least ask them for three sample messages beforehand. Even that small step makes the traffic more realistic.
-
Homebrew build order: receiver first, or go straight to a QRP transmitter? What test gear actually matters?
I'd keep the receiver first, with one tweak: build the audio chain and the LO as separate boards or at least separate sections, and test each on its own. A DC receiver is mostly a story about gain distribution. With the mixer and the audio amp together on a single piece of copperclad, you can't tell whether the hiss is the mixer, the preamp or the layout. A few things commonly cause grief in DC receivers: First, LO leakage to the antenna. If the LO is strong and the mixer is not well balanced, the LO radiates and also produces DC offsets at the mixer output that get amplified by the audio chain. A balanced mixer (diode ring, or an SA612-type double-balanced mixer) and a bit of buffering help. Second, AM broadcast stations overloading the first stage. A simple bandpass filter in front of the mixer, rather than just an untuned antenna connection, makes a very noticeable difference on a long wire. Third, the image problem. A DC receiver has no sideband selection, so both sides of zero beat come through. You can accept it for CW, or build a phasing type with a 90-degree audio network if you want a quieter band and better single-signal reception. That is a good second receiver project. For the transmit side, a low-pass filter should be on your list as soon as you pick any transmitter stage, even a Tuna Tin 2. Square-wave-ish switching stages are rich in harmonics, and the usual advice is a 5-element Chebyshev design for the band. Wind the toroids carefully and verify them with a VNA or at least an RF probe and a signal source.
-
Getting started with LEO amateur satellites: Doppler handling, tracking software, arrow antennas, and when to move to linear birds
I'd lean toward the opposite order if the person already has HF or VHF/UHF SSB experience, because the hardest linear-satellite skill isn't hardware, it's the tuning discipline. On an inverting transponder like RS-44, set a fixed point on the downlink, let the software walk the uplink, and make small manual adjustments with the RIT or the VFO knob. Trying to do it entirely by ear on a handheld is possible, but frustrating for someone who hasn't done it before. For equipment, a small Yagi pair on a light az/el rotator plus a radio that supports satellite mode and CAT gives a much more forgiving setup than a handheld on a weak SSB signal. Keep an eye on feedline loss on the 435 MHz side, since it hits the receive noise figure, and consider a preamp at the antenna for the downlink if the coax run is long. Remember also that if you transmit on 2 m and receive on 70 cm, you need adequate filtering or physical separation, or the receiver may desense. A practical tip: before trusting any rotator setup on a real pass, run it against a simulated pass and check that azimuth and elevation limits, the parked position, and the 'overhead flip' behavior all match what the software expects. Errors there tend to show up on the nicest passes, the ones at high elevation.
-
Hamfest season planning: swap meet tactics, club tables, VE sessions, and what to throw in the trunk
For the club side, I'd say don't underestimate a simple 'new to ham radio?' sign at the table. People who just got licensed often don't know where to start with a first HF antenna, a local net, or even how to program a repeater into an HT. A handout with the club's repeater frequencies, offset and tone, meeting time, and a contact for Elmer help is more useful than a pile of general brochures. For Field Day, a short pre-event meeting helps a lot: who's bringing antennas, who handles logging, who's setting up the GOTA station if you run one, and who is responsible for power and safety. A lot of clubs also use the weeks before to test the generator, check coax runs, and make sure the digital station software actually works. It's much easier to fix that in a garage than at the site.
-
Q codes and ham shorthand: what do QRM, QRL, QSY, KN, SK, 73 and 88 actually mean, and when do you use them?
Here is the rest of your list, then the voice and net side. CQ is a general call meaning any station may answer. Variants add what you're looking for, such as CQ DX, CQ TEST in a contest, or CQ POTA or CQ SOTA for portable activations. DE means "from," so "CQ CQ CQ DE W1ABC" is a call from W1ABC. K means "go ahead, any station." KN means "go ahead, but only the station I named," which keeps others from jumping in. SK is the end of a contact. Capitalized as "silent key," it's also how operators note that a ham has died, which is a different use that deserves some care. 73 means best regards, and it's already plural, so "73s" is generally frowned on. 88 means love and kisses, and it's usually kept for friends or spouses. RST stands for Readability (1 to 5), Strength (1 to 9) and Tone (1 to 9). Tone is only used on CW. Voice reports use just R and S, such as "5 by 9." On CW a perfect report is 599, often sent as 5NN with the N standing in for 9 to save time. In a contest the report is often just a formality, and real signal reports usually give more detail than 599. Other common CW shorthand: TNX (thanks), FB (fine business, meaning good), OM (old man, a male operator), PSE, UR (your), WX (weather), ANT, AGN (again), ES (and), TU (thank you), GL (good luck), HI (laughter). On voice, plain language is usually preferred. Saying "what's your location?" is perfectly fine, but "what's your QTH?" is common too. Q codes like QSL, QSY, QRM and QTH are widespread on phone. Don't mix in CB-style codes like "10-4." Use the phonetic alphabet for callsigns, and identify according to your licensing rules. In the US that means giving your call at the end of a communication and at regular intervals during it. For nets, the net control station (NCS) runs things. You'll hear check-in, roll call, traffic, relay, and "short time" for someone who has to leave soon. QNI is often used to mean checking into the net. Always listen first to learn how that particular net runs, since formats vary. A basic log entry usually includes date and time in UTC, callsign, band or frequency, mode, RST sent and received, name, QTH, and QSL status.
-
On-air etiquette basics: CQ calls, breaking in, nets and handling interference
On shared frequencies and repeaters, the bigger issue is often the length of a transmission rather than who's allowed to talk. Leave gaps between overs on a repeater so someone can get in, especially if there may be urgent traffic. It's also worth remembering that a repeater is a shared resource. If you and one other station are having a long conversation, simplex is often a better place for it, and it frees the repeater for others. On interference, I'd stress documenting before reacting. Note the time, frequency, mode, how it sounds, and whether it's constant or intermittent. That information is far more helpful to a coordinator than "somebody's jamming us." It also helps you work out whether it's malicious, accidental, or something like local noise that no one on the air is causing.
-
Breaking pileups on rare DX: split, timing and tailending, and what changes for Clipperton or Bouvet-class targets
On etiquette, I would say the line is simple: if you can hear that the DX is still in a QSO, do not transmit. A short tailend call after he has clearly finished and is about to call CQ or ask for a call is a different case from calling over the final exchange, even though from the other end of the pileup they both look like tailending. The operator will usually tell you what they prefer. If they say "only call when I say", then that is what you do. It also helps to understand the DXpedition side. Planning for a rare entity covers permits, transport, power, antennas, band plans and operating schedules. The team often has to make choices such as splitting operators across bands and modes, or favouring low bands during certain hours, because they have limited time. When they ask for certain regions or modes, that is usually a deliberate plan to share the contacts around. Respecting it makes the whole operation more efficient. For your own approach: keep a log of what you need by band and mode. Many people chase an entity on one band and ignore the others, but on a short DXpedition you may have better chances on a band that is less crowded. Check the Club Log Most Wanted list and the operation's own notes, and plan your effort accordingly. Also know when to stop. If the pileup is huge and you are not getting through after a reasonable effort, trying a different time or band is more productive than calling continuously.
-
Planning a homebrew QRP station from scratch: build order, test gear, and what to check before you key up
I'd put the dummy load and a way to see the RF at the very top of the list, ahead of an SWR bridge. Until the transmitter is happy into a resistive load, an antenna just adds variables. A dummy load made from several 1/2 W or 1 W carbon film resistors in parallel is fine at QRP levels. Ten 510-ohm resistors in parallel give 51 ohms, which is close enough, and the power is spread across the resistors. A diode RF probe on the multimeter then gives you relative output, and a scope gives you the waveform shape. That helps you spot an oscillator that is running but distorted, or a final stage that is clipping. On the SWR bridge: a simple tandem-match or Bruene-style bridge is a good build in itself. Calibrate it on the dummy load first (reflected should read near zero), then try it with a known mismatch such as a 100-ohm resistor, where you expect roughly 2:1. A bridge that has never been checked against a known load is a guess. For harmonics, a general-coverage receiver or an SDR tuned to the second and third harmonic frequencies, with attenuation between it and the transmitter, will tell you a lot. It won't replace proper measurement, but it will show you if a low-pass filter is doing nothing. A NanoVNA is useful for sweeping the filter on its own, before it ever goes into the transmitter, and for checking antenna match. I'd buy it second, after the dummy load and probe. For toroids, keep a few T37-type cores and some scrap wire to practice on. Count turns by the number of times the wire passes through the center hole, not around the outside. Tin the enameled ends and check continuity before you install anything.
-
Dead rig triage: how do you separate power, receive and transmit faults before pulling the finals?
One thing I'd add under noise: swap the supply for a battery, or any known linear supply, early on. If the noise disappears, you've isolated it to the supply or its wiring, and a lot of time is saved. If it stays, then it's either coming from the rig itself or arriving through the antenna and ground system. Digital noise from the rig's own CPU or display is another candidate, so check whether the noise changes with the display brightness or when you press buttons. For capacitor replacement, my advice is to replace electrolytics in groups that share a function, such as the whole filter and decoupling stage of a supply, rather than a single part that tested badly. Meter readings on ESR can be misleading while the capacitor is in circuit. Also mind the orientation and the lead spacing, and use a heatsink or a low-temperature approach on small SMD pads. Lifted pads on a crowded board are harder to fix than a bad capacitor. Does anyone have a preferred way of confirming a PA transistor is truly dead without desoldering it? Diode-mode checks seem to catch only the obvious short-circuit failures.
-
Planning a 24–48 hour EMCOMM field station: how are you splitting power, antenna and noise decisions?
Your power budget step is the right place to start. Two details are easy to miss. First, size the wire for the worst-case load, not the average. At 20 A or more on a 12 V system, voltage drop is real, so keep DC runs short and use adequately heavy conductors. A rig that sags to 11 V on voice peaks can splatter or shut down even when the battery is fine. Second, check the battery's rated continuous discharge and the BMS cutoff. Some small LiFePO4 packs have a BMS limit that a 100 W rig plus accessories can trip, and the radio just dies with no warning. On LiFePO4 specifically, read the manual for charging temperature limits. Most cells should not be charged below freezing unless the pack has low-temperature protection or a heater. If you plan to charge from a generator or solar on a cold morning, that matters. Also make sure the charger or MPPT controller has a LiFePO4 profile. A generic lead-acid charger may not fully charge it or may overcharge it. For solar, an MPPT controller with a panel sized for a few hours of sun can carry the receive-heavy baseline load of a net-control station, but don't count on it for HF transmit without a lot of panel. I'd treat solar as extending the battery, not replacing the generator, unless the deployment is long and the loads are small. On generator placement, the usual guidance is to keep it well away from tents and openings, downwind, on level ground, with a battery-powered CO alarm in the shelter. Treat that as a hard rule on the checklist, not a preference. Also plan for refueling. Let it cool first, and keep fuel away from the generator and the shelter.
-
EME station planning from 2 m to 10 GHz: what actually limits your first moonbounce contacts?
For 2 m and 70 cm, think in terms of the whole receive chain, not the preamp alone. On 2 m, galactic and sky noise often dominate the system temperature, so feedline loss between the antenna and the preamp matters more than shaving a few hundredths of a dB off the noise figure. Mount a low-noise preamp at the array, keep the relay and cable loss before it small, and use a proper TR sequencer so the relay switches and the preamp is protected before the PA keys. Sequencing mistakes ruin more preamps than weak signals ever do. Gain is the other lever. A four-Yagi 2 m array of long boom Yagis lands around 20 dBi, which is a common starting point for JT65 work with big stations. Larger arrays help, but stacking distances, phasing lines, and mechanical wind loading grow quickly. On 70 cm the elements are shorter, so more of them fit in the same space, and 70 cm arrays of 8 or more Yagis are common. Check the combiner losses and the connector quality, since in a stacked array a bad connector can cost you more than another Yagi gains you. Polarization is where 2 m gets interesting. Faraday rotation twists linearly polarized signals as they pass through the ionosphere. On 2 m this causes slow polarization fades, and the effect falls off with frequency, so on 70 cm it is smaller but still present at times. Above that, it matters little. There is also a geometric spatial polarization offset between two stations that depends on where each sees the Moon. A station that can switch between horizontal and vertical, or can rotate the feed or array, can chase the best polarization. If you can only run a fixed polarization, you will miss some windows. Some stations use dual polarization with phase and combine control to cover a whole range, which is more complexity than a first station needs, but it is worth knowing about. Before the first sked, I would do a Sun-noise measurement and a Moon-noise measurement to verify the pointing and the receive system, and look for your own echo when the system is ready. If you cannot hear your own echo on a decent day, there is no point calling a partner.
-
Learning Morse code from zero: Koch or Farnsworth, which trainers, and how do you get from copying letters to copying in your head?
Koch and Farnsworth are two separate ideas, and they combine well. Koch is about the order and pace of learning. You hear characters at a fairly high speed from the start, commonly around 18 to 20 wpm character speed, but you begin with only two characters. When you copy them accurately, usually around 90 percent, you add one more. The point is that you never learn a slow, 'counting' version of a character. Each one is learned as a single sound pattern, a rhythm, not as dits and dahs to be added up. Farnsworth is about spacing. The characters are sent at a faster speed, but extra time is inserted between characters and words so the overall speed is lower. That gives your brain time to recognize one character and write it down before the next arrives. Many Koch trainers let you set the character speed and the effective speed separately, so you can use Koch's order with Farnsworth spacing and then reduce the extra spacing as you improve. The mistake to avoid is learning at a very slow character speed, say 5 wpm sent with long dits and dahs, and later trying to speed up. That tends to produce a plateau, because the sound of the characters changes as you speed up, and the habit of counting elements gets in the way. On flashcards and charts: a printed chart is fine for a quick check, but visual dot-dash memorization works against you. If you catch yourself thinking 'dit dah dit dit, that's L', you're translating. The aim is to hear the sound and write L with no step in between. Anything that makes you look at dots and dashes before you've heard the sound is training the wrong thing. If you want an app that works like flashcards, choose one that plays the sound first and makes you respond before showing the answer. For head copy, the usual progression is this. First you copy every letter on paper. Next you start recognizing common short words as whole sounds: 'the', 'and', 'de', 'CQ'. Then you try to hold a few words in your head and write only the ones you miss. Doing this gradually works better than trying to stop writing all at once. For sessions, short and regular beats long and occasional. Fifteen to twenty minutes a day is a reasonable target. If you notice your accuracy falling off or you're getting tense, stop and come back later. Tired practice mostly reinforces mistakes.
-
Where dynamic range actually gets lost in an SDR chain: gain, filters, upconverters and antennas
On LNA placement, the standard rule is that the noise figure of the first stage dominates the system. Loss in the coax before an LNA adds directly to noise figure, so at 1090 MHz for ADS-B or 137 MHz weather satellites, putting a filtered LNA right at the antenna is generally the better arrangement. The filter matters, though. A cheap broadband LNA can push strong out-of-band signals into overload, so a band-specific filter is often chosen to go with it. Check also how the LNA is powered. A bias tee sends DC up the coax, and you want to be sure that the DC does not reach anything that cannot handle it, such as a splitter without DC pass, or a different antenna. For the panadapter safety question: the safest options are an IF tap if your transceiver offers one, or a separate receive antenna. If you must share an antenna, a purpose-built TX/RX switching arrangement, with the SDR path grounded or isolated during transmit, is what you want. A passive splitter is not protection. Even low-power transmissions can exceed what an SDR front end tolerates, so confirm the power levels in the manuals for both devices before connecting anything. For HF with upconverters, one more detail: calibrate the offset. A converter with a crystal LO has its own frequency error, so signals will be off by an amount that scales with the LO frequency. If you decode weak-signal modes such as FT8, check a known carrier and correct it in the software, or tolerate it where the mode permits a wide enough frequency window.
-
Getting from 5 to 20 wpm: what to do about plateaus, head copy and when to put the pencil down
On the plateau: a stall around 10 to 13 wpm is common because it is where counting stops working and recognition has not fully taken over. Raising the speed of your drills a little, even to a level where you only get 70 to 80 percent, often forces the jump. Then drop back to a comfortable speed for a while. Alternating between "too fast" and "comfortable" sessions seems to work better than grinding at one speed. On callsign drills versus real copy, I'd use both for different jobs. A trainer like Morse Runner, RufzXP or a callsign mode in a web trainer builds quick, accurate recognition of suffixes and number-letter patterns. Real on-air or recorded QSOs teach you the predictable structure of exchanges: CQ, DE, RST, name, QTH, 73. The more of that structure you know, the less you have to decode character by character. If you are only practicing one of these, add the other. For decoders, I'd use one as a scoreboard rather than a copy source. Copy by ear first, then run the same audio through the software afterward and compare. If you are watching the screen while copying, your brain learns to read instead of hear.
-
Upgrading from Technician to General: how should I split study time across the 35 questions?
I'll add the antenna, digital mode, operating practice, and vanity call parts, since those are the areas people tend to skim. Antennas: expect questions on dipole length and radiation pattern, what a trap does, what a balun is for, and feed line loss. A half-wave dipole is roughly 468 divided by the frequency in MHz, in feet, but understand why it's a bit shorter than a free-space half wavelength rather than just memorizing the formula. For feed lines, know that loss increases with frequency, and that a high SWR on lossy coax can look better at the radio than it really is at the antenna. Know that SWR is a measure of impedance mismatch and not a direct measure of how well the antenna radiates. Impedance-matching ideas like a 1:1 versus a 4:1 balun come up as concepts, so know what each is for. Digital modes: the exam doesn't expect you to run them, but it asks about characteristics. Know that FT8 operates in fixed time slots and so requires accurate computer clock sync. Know that PSK31 and the other narrow modes use very little bandwidth, and that RTTY is a frequency-shift mode with a defined shift. Also know where digital operation sits in the sub-bands. A lot of this is about the difference between a mode's bandwidth and where it's legal to transmit. Operating practices: these questions cover station identification, third-party traffic, band plan courtesy, how to call CQ, how to respond to a DX station in a pileup, and not transmitting on top of an ongoing contact. Read the explanation for each answer, because the correct choice is usually the polite and legal one. Vanity calls and your call sign: passing General does not change your call sign. You keep what you have. A vanity call is optional and is applied for through the FCC system, with a fee. As a General you can request calls from the groups available to your operator class, so a 1x3 call (one prefix letter, one number, three suffix letters) is an option if it's available in your region. Don't pick a target call from memory: check the FCC's rules and the current availability lookup, since both change. One more practical note for exam day: bring valid ID, your existing license information, and any CSCE if you have one. If you take it at a VE session, you don't need to retake the Technician element, since your existing license already covers it.
-
Where do I actually operate? Band plan vs. FCC privileges, band edges, 60 m channels, and VHF/UHF calling frequencies
Adding the pieces that tend to trip people up beyond the main HF bands. 60 meters is the exception to "pick any spot in a segment." In the US it is not a continuous band but five discrete channels, available to General and above, and they are shared on a secondary basis with other users. The channel dial settings (suppressed-carrier USB) are 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz. The channel centers are 1.5 kHz above those, which is why you will see two sets of numbers depending on whether the source lists the carrier frequency or the center. USB is the voice convention there, and CW and certain digital modes within the channel bandwidth are also allowed. There is also a power limit expressed as ERP relative to a half-wave dipole, rather than the usual PEP figure, so check the current rule text before you transmit, especially with an antenna that has gain or loss. Internationally, 60 m is a patchwork. A worldwide secondary allocation was added at 5351.5 to 5366.5 kHz, but individual countries implement it differently, so the US channels do not map cleanly to what operators elsewhere can use. Which brings up the ITU regions. The US is in Region 2, and a lot of band-edge differences between countries come from that. For example, 80 m is 3.5 to 4.0 MHz in Region 2 but only 3.5 to 3.8 in Region 1. 40 m is 7.0 to 7.3 in Region 2, but only 7.0 to 7.2 in Regions 1 and 3, and above 7.2 there are international broadcast stations, which is why US phone operators near 7.2 and above sometimes hear them at night. 2 m is 144 to 148 MHz in the US but only 144 to 146 in Region 1, and 70 cm is 430 to 440 there instead of 420 to 450. 33 cm (902 to 928 MHz) is allocated only in Region 2, and in the US it is shared with Part 15 devices and other services, so amateurs have secondary status and noise is common. If you are travelling or talking to stations overseas, find out what they can legally use, and check whether you need a reciprocal permit or something like a CEPT arrangement. For simplex calling, these are the ones to remember. On 6 m, the SSB/CW weak-signal calling frequency is 50.125 MHz, and the FM simplex calling frequency is 52.525. On 2 m, 146.52 is the national FM simplex calling frequency, 144.200 is the SSB/CW weak-signal calling frequency, and 144.390 is the North American APRS frequency. On 70 cm, 446.000 is the national FM simplex calling frequency, and 432.100 is the weak-signal calling frequency. On 33 cm, 903.100 is widely cited as the weak-signal calling frequency, and the ARRL band plan lists the other segments. On 10 m, 29.600 is the FM simplex calling frequency. Calling frequencies are for making contact and then moving off to another frequency, not for a long conversation, so QSY once you've made contact. One last point on 2 m and 70 cm: the band plan separates repeater inputs and outputs (offsets are typically 600 kHz on 2 m and 5 MHz on 70 cm in the US) from simplex and weak-signal segments. A repeater output frequency looks identical to a simplex one on your radio's display. Check your local coordination or the repeater directory before you assume a frequency is open, and keep weak-signal and satellite sub-bands free of FM.