Everything posted by Admin_Lee
-
Dual-band mobile setups: FTM-500D vs ID-5100A vs TM-D710G, plus wiring, noise and etiquette
On antenna placement, a roof-center NMO mount with a properly sized quarter-wave or 5/8-wave whip is hard to beat for a dual-band mobile. Trunk-lip mounts and magnetic mounts can work, but they depend more on the ground plane and the coax routing, and they are more likely to have SWR surprises and pattern lumps. Whatever you pick, check SWR on both 2 meters and 70 centimeters instead of just one band. A dual-band antenna can look fine on one band and mediocre on the other. Also check the coax run. Short runs of decent coax are fine at VHF, but UHF loss adds up faster, so long runs of cheap thin cable can eat a noticeable chunk of your power. If you're routing it under door seals, use a flat or thin section designed for it, and leave a little slack so a door isn't continually pinching it. One more point on the radio choice: if you plan to use a digital mode, check the coverage near where you actually drive. A radio that supports D-STAR or C4FM isn't much use for that purpose if there are no active repeaters you can reach.
-
Sequential vs. vanity callsigns: how the groups work, who qualifies, and what to check before you apply
On vanity, the main steps are these. You apply through the FCC's ULS, using your FRN and your CORES login. You can list multiple choices in order of preference, up to 25, and the system grants the first one on your list that's available and that you qualify for. Because of that, it's worth listing realistic fallbacks and not just a single dream call. A few rules catch people out: Waiting period. A callsign that has expired or been surrendered generally can't be requested by someone else for two years. That window is meant to let the previous holder reclaim it.Former holders and family. You can request a call you previously held. For the call of a deceased licensee, close relatives may be able to request it without waiting out the two-year period. The FCC's rules list which relationships count, so check the exact wording before assuming a cousin or friend qualifies.Class matters. You can only request calls in the groups your license class allows. An Extra can go for 1x2 and 2x1 calls, for example, and a General can't.Region doesn't have to match. A vanity call's number doesn't have to match where you live. Don't read too much into the digit of someone's call when you see it on the air.Some calls are off the table. Certain blocks are reserved, including the 1x1 calls, which are used for special events and are not available as vanity calls.For fees, the FCC has changed its fee schedule over the years, so look at the current schedule on the FCC site and don't trust a number you saw in an old forum post. The vanity application has its own fee, which is separate from general license application fees. Keep your mailing address and email in ULS current. The FCC sends official notices to what's on file, and a callsign you applied for can be lost if your contact details are wrong. A license term is ten years. There is a grace period after expiration to renew, but you can't operate until it's renewed.
-
Field station layout for a 24-48 hour deployment: what order do you set up power, antennas and noise control?
Agreed on the mission driving the antenna. For EMCOMM, I'd also separate the "primary" and "backup" paths on purpose: one HF antenna that covers the regional net, and a simple VHF/UHF setup that still works if the HF mast comes down in wind. A roll-up J-pole or a small vertical on a short mast takes minutes to deploy and covers local simplex or repeater traffic while the larger antenna is being built. For the tent, keep the radios inside but keep the feedlines and antennas outside with a defined cable entry, such as a gap in a wall flap, with a drip loop so water does not run along the coax into the shelter. Metal-framed pop-up canopies can couple to nearby antennas, so keep wires and verticals away from the frame and check SWR with the canopy in place, not just before it goes up. Stakes and weights matter as much as the radio gear, since an unsecured canopy in gusts is a hazard to people and antennas. On grounding, I'd separate the ideas. Bonding the radios, power supply and any metal chassis to a common point reduces shock risk and some noise. A ground rod does not make a station safe from lightning. If thunderstorms are anywhere nearby, the plan should be to stop transmitting, disconnect the feedlines, lower the antennas if that can be done safely, and move people to proper shelter. For teardown, I'd write the checklist in reverse order of setup: power down radios, disconnect antennas, lower masts, coil coax in a way that matches how it unrolls, then count stakes, guy lines and connectors against the packing list. Missing small items like adapters, spare fuses and Powerpole crimp tools are the usual losses, so I'd keep a printed inventory in the kit itself.
-
Pi, Pico or ESP32 for shack automation? Where to split rig control, SWR sensing, rotator and antenna switching
On the Pi-versus-microcontroller split, I'd keep the Pi out of the time-critical path and use it as the supervisor. Direwolf is a good example. It runs well on a Pi with a USB sound interface, but PTT needs to be dependable. You can drive it from a GPIO line through a transistor, or through rigctld when the radio supports CAT PTT. Either way, add a hardware timeout so a stuck process cannot hold the transmitter keyed. For an APRS tracker, an ESP32 or Pico plus a GPS module and a small radio module can do the job without Linux. If you want an I-gate or digipeater, that is where the Pi and Direwolf earn their place. The Si5351 comes up a lot for VFOs and beacon sources. It is an I2C clock generator with square-wave outputs, so expect harmonics. Anything that feeds a receiver mixer or a transmit chain needs filtering, and its output level and drive settings should be matched to the stage after it. Also check library behavior for frequency changes, because some libraries recalculate PLL settings in ways that cause glitches or phase jumps. For soldering, small SMD modules like the Si5351 breakout and level shifters tolerate a fine tip, flux and moderate heat better than a hot iron held on the pad. Put a drag of fresh flux on joints when rework gets messy, and inspect for bridges under magnification before applying power.
-
VHF/UHF antenna choices: J-pole vs slim jim vs 5/8 wave vs collinear, and where the feedline and connectors fit
One thing worth adding is that gain figures need context. A collinear rated at 6 dBd and a 5/8 wave rated at 3 dBd are not directly comparable unless you know the ground plane, the mounting height, and whether the number is dBd or dBi. A dBi figure is 2.15 dB higher than the same antenna in dBd, so some ads look better than they are. On connectors, I would keep PL-259 for HF and short shack jumpers and use N-type for anything outside, especially on UHF. If you are stuck with a PL-259 on the antenna, sealing it with self-amalgamating tape and then a layer of UV-resistant tape helps, but the connector is still a weak point. Also check that adapters are not stacked three deep, since each one adds loss and a possible leak. For mobile, I would test the mount grounding with an ohmmeter between the NMO body and the vehicle sheet metal, then check SWR across both bands. If the SWR is high on 70 cm but fine on 2 m, suspect the mount, the cable or the connector before blaming the antenna.
-
Starting out on LEO satellites: FM birds first, then linear? Doppler, tracking software and antenna choices
Quick additions on the linear side and the rotator question. With an inverting transponder, tune the downlink and let the radio handle the uplink arithmetic if you can. Software can maintain the relationship between uplink and downlink, so you only have one tuning knob to turn. If you tune by hand, you'll find the uplink is easy to lose while you are chasing a CW or SSB station. On CW, remember that tone and Doppler interact: if you're off by 500 Hz you won't hear the other station, and you could be sending somewhere you don't intend to. Listen to your own downlink first, and keep power low. Linear transponders are shared, and a loud station will desensitise the whole passband for everyone else. If you can hear yourself loud and clear, back off. On the rotator: azimuth-only is workable for casual operating with a lower-gain antenna that has a broad beam, but for any Yagi with real gain, elevation matters on high passes, when the satellite goes nearly overhead and the pointing angle changes quickly. Some operators with az/el rotators still don't track through the zenith because azimuth can swing very quickly at the top of the pass. That's a known quirk of overhead passes, so check how your rotator and software deal with it, especially with a pass that goes through 90° elevation. Don't forget polarisation. Linear antennas can fade as the satellite rotates, and the effect is more noticeable with weak signals. Circular polarisation is one common fix, and rotating the antenna slightly by hand on a handheld Yagi is another. QO-100 is a different thing entirely. It is geostationary, so there is no Doppler and no tracking after you aim the dish once, but you need a 2.4 GHz uplink, a 10 GHz downlink and a stable LNB. Treat it as a separate project once you're happy with LEO.
-
Reading the ARRL band plan vs. FCC rules: where to operate, band edges, 60 m channels, and VHF/UHF calling frequencies
Start with the legal/voluntary split. The FCC rules in Part 97 (the band and subband tables in 97.301 through 97.305, plus the special rules in 97.303 for particular bands) are binding. They set your frequency limits by license class, the allowed emission types per segment, and the power limits. The ARRL band plan is a voluntary recommendation that sits inside those limits. Nobody can cite you for parking FT8 on a frequency traditionally used for SSB, but you'll get QRM and a bad reputation. Using a mode outside the segment where the rules allow it is a different matter, and that's a violation. Privileges by class, briefly. Technicians get all modes on 50 MHz and up, plus limited HF: CW on parts of 80, 40 and 15 m, and CW/RTTY/data on 28.000-28.300 and SSB on 28.300-28.500 at 200 W PEP. Generals get segments of every HF band, including 160 m, 30 m, 17 m and 12 m, but not the whole of 80, 40, 20 and 15 m. Amateur Extra gets everything. The mode restrictions matter too: 30 m is CW and data only, with a 200 W PEP limit, and General phone on 75 m starts at 3.800 while Extra phone starts at 3.600. Novice and Advanced licenses are no longer issued, but existing holders keep their old privileges. Use the 97.301/97.305 tables rather than memory for the exact edges. Different classes have different cutoffs on 80, 40, 20 and 15 m and it's easy to misremember them. Band edges. The frequency on your dial is not the edge of your signal. On USB the signal extends from the dial frequency upward by roughly 2.5-3 kHz. On LSB it extends downward by the same amount. So if your phone privileges begin at 3.800 MHz and you're on LSB, a dial reading of 3.800 puts part of your signal outside the band. Keep the dial a few kHz inside, and do the same at the top edge. On 20 m with USB, the dial should be a few kHz below 14.350, not on it. Digital modes need the same care, because the whole occupied bandwidth must be inside, not just the dial frequency. Radio dials can also be off by a little, so leave margin for that too. On HF the main segments, going by the ARRL plan, are CW and narrow digital near the bottom of each band, then wider data, then phone. A few well-known conventions: QRP CW calling frequencies (14.060, 7.030, 21.060, 28.060 and 3.560), the 14.100 IBP beacon area, and the FT8/FT4 dial frequencies like 7.074, 14.074 and 21.074 for FT8. Those digital frequencies are conventions that spread by usage, not entries in the FCC tables. On 160 m the 1.830-1.840 stretch is generally treated as a DX window. 60 m is different. In the US it's five discrete channels rather than a band, available to General and above, with a 100 W PEP effective radiated power limit referenced to a half-wave dipole. The channel dial frequencies for USB are 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz. The channel center is 1.5 kHz above each of those, so check whether your rig expects a dial or a center frequency. Phone is USB only. The rules also allow CW and certain data modes on the channels, subject to the bandwidth limits. Read the current 97.303 text before using a new mode there.
-
LoTW, eQSL, Club Log OQRS, bureau or direct: how do you confirm contacts, and what counts for DXCC?
One thing that trips people up is that a LoTW account being active doesn't mean your confirmations will appear. You need a valid certificate for the callsign you used at the time of the QSO, and the other station has to upload using the right location, with the right callsign, DXCC entity, grid and zone. If you're operating from a different DXCC entity or portable, a QSO can fail to match because the location or callsign on one side was wrong. Check your TQSL station locations before you start uploading everything. For direct cards, follow the operator's instructions exactly. If they say SASE plus a specific amount, include exactly that. Don't write your own callsign on the outside of an envelope going to a country where radio mail attracts attention, unless their page says it's fine. Many DX operators ask for a plain envelope with no callsign visible. Put your own address on the inner SASE, along with a card or a printed request with the QSO details. Keep the details of every request somewhere, including date sent, so you know when it's reasonable to follow up. For DXCC, the practical advice is to use LoTW where you can and use paper cards for the gaps. Paper cards are checked by ARRL-appointed checkers or at the ARRL, so make sure the card clearly shows all the details and, where relevant, the operator's callsign for the entity. Read the current DXCC rules on the ARRL site before you submit anything, since I don't want to assume the details haven't changed. For everything else, I treat eQSL and QRZ matches as bonus confirmations rather than as the end of the process.
-
Radio mods that are worth doing, and where MARS/CAP, expanded receive and legal limits come in
On the TCXO point, measuring before and after is the step people skip. A frequency counter or a GPS-disciplined reference tells you whether the drift came from the oscillator at all. Sometimes the drift is thermal, caused by the radio sitting in a hot car or near its own PA, and a better oscillator won't change that. Warm the radio up first and check at a few temperatures. For expanded receive, I'd add a caution about reading too much into a strong signal on an odd frequency. If you hear something out of band on a wide-open receiver, it may be an image or a mixing product from a strong local transmitter, not the real signal. Test with an attenuator or a different antenna and see whether the signal behaves like a real one.
-
What makes a rig a keeper? Vintage vs. modern, and how you decide what stays in the shack
For me the dividing line is whether a radio is still usable day to day. A rig can be beautiful and historically important, but if it only gets switched on for a quick warm-up before going back on the shelf, it's really a display piece. Nothing wrong with that, but it's worth admitting to yourself. On the vintage side, I'd add a safety note for anyone tempted by tube gear. Plate supplies can be lethal, and filter capacitors can hold a charge long after the radio is unplugged. Before opening a transmitter or amplifier, make sure you know how to discharge the supply and check it with a meter, and don't trust bleeder resistors to be working in a 50-year-old chassis. Replacing old electrolytics and checking for leaky paper or wax capacitors is usually the first job on a restoration, and doing it right is much better than just "seeing if it powers up." For a keeper, I'd say a good receiver matters more than anything. You can always improve a transmitter's setup or add an outboard filter, but a receiver that's pleasant to listen to for hours is hard to replace.
-
Building an HF shack around a 100 W rig: what matters more than the radio badge?
On the rig choice side, think about the type of interference you actually have, because the designs behave differently. The superhet rigs with narrow roofing filters, like the TS-590SG and TS-890S, are often chosen for crowded-band performance. Direct-sampling SDRs like the IC-7300 and IC-7610 give excellent displays and flexible filtering, but strong out-of-band signals can still matter, so attenuators, preamp settings, and band-pass filters need attention. The G90 is a great compact option, but with 20 W and a more modest front end it makes sense to keep expectations realistic if you're near strong broadcast or other-station signals. With an amplifier, I would plan the signal path on paper before buying anything. Rig to amp needs the right drive level, ALC, and PTT or keying interface. Then amp to tuner or antenna switch, then to the antenna. If you use an auto-tuner such as the one in the rig, remember it should be set up with the amp in mind, and you should tune with low power before running the linear. If you have a Wattmeter that reads forward and reflected power at the amp output, use it, because it shows whether the antenna system is behaving. For KX3 users, the PA/ATU options and battery operation make it a good portable rig, but at the home station its 10 W limit means a driver for an amplifier is where it gets interesting. Check the amp's minimum drive requirement first, since many 500 W-class amps want more than 10 W for full output.
-
Repeater basics that trip people up: offsets, tones, time-out timers, linking and etiquette
On linking, the biggest etiquette gap is that people don't realize when the repeater is part of a bigger system. If the repeater has a link announcement, a different courtesy tone or a longer delay after you unkey, that's often a sign. A longer pause helps because linked systems can add delay, and other repeaters or nodes need time to drop and reset. Also, if a net or a scheduled link is in progress, wait for a clear break before you start a long conversation. For DMR and D-STAR especially, remember the radio programming matters as much as the frequency. On DMR you need the right color code, timeslot and talkgroup, plus a DMR ID, and some networks have rules about which talkgroups are for calling and which for conversation. On D-STAR, the routing fields must be right or you may key a repeater that never carries your traffic anywhere. Wires-X and AllStar tend to have their own local rules about which rooms or nodes to connect, so the club page or the system's net announcements are the right place to check. I'd also suggest using a directory only to find candidates. A listing may show a link or digital mode that has since been disabled, or the repeater may have changed to a new tone. The club site, a published net schedule, or a short question to the trustee or owner is more reliable than a stale entry. And when you find a repeater that's well maintained, joining the club is the best way to keep it that way.
-
How do you keep up with ham radio news without chasing rumors? Firmware, FCC, ARRL, band conditions and Hamvention season
For propagation, I like using the numbers to decide when to listen and the spot tools to confirm what's really happening. Solar flux and the K-index give a rough idea. Then PSKReporter or the Reverse Beacon Network show whether your band is open to the regions you care about. If you can't hear much, check whether your own receive noise is the problem before blaming the sun. Local noise from LED lighting, chargers, or switching supplies can hide a good opening. One more tip for news in general: look for the date and the issuer. A conditions report from last month, a conference slide, or a forum screenshot may be accurate for its time and useless now. For Hamvention and other conventions, the official schedule and exhibitor lists are better than social media summaries, and product announcements there often come with "available later" caveats. On trends, portable operating looks like the area with the most practical growth in conversation: lightweight antennas, small batteries, and compact rigs for park and summit activations. That's an impression, not a measurement, so I'd like to hear what club activity looks like where you are.
-
Radio mods worth doing, mods worth skipping: MARS/CAP, expanded RX, TCXO, filters, power and noise
The legal and practical sides of modified radios deserve a more careful line than they usually get. In many places, hearing a signal is largely unregulated, and transmitting is where the rules bite. Being technically able to key a radio on a frequency says nothing about whether you hold the authorization for that service. If your radio is modified for MARS or CAP use, make sure you know what that program permits, which channels you are assigned, and what its operating rules require. Program membership is the starting point, not the radio hack. Another point that gets overlooked: amateur gear and certified commercial or public-service gear are different categories in many jurisdictions. A radio that is approved for one purpose is not necessarily approved for another, and altering it can change that. If you want to run a radio on a repeater or in a regulated service, check the equipment requirements for that service first. On the noise side, a cheap clip-on ferrite is not always the answer. Many noise problems come from a common-mode current path, and ferrite choice matters by frequency range. A choke that works at 7 MHz may do very little at 144 MHz. If a ferrite doesn't help, try changing where it sits (closer to the noise source) or using more turns before concluding it can't work.
-
Technician to General: how should I split study time across Element 3, and what do I need to know about HF sub-bands?
On the HF sub-bands: you don't need to memorize every edge in the whole regulation, but you should know the pattern, because the exam asks in ways that reward it. The big idea is that General gets access to all the HF amateur bands, with segments reserved for Amateur Extra near some band edges. Compared with Technician, which only has CW on small parts of 80, 40 and 15 meters and limited 10 meter privileges, General is a large step up. Rather than learn raw numbers, build a mental picture for each band: where the CW/data portion is, where phone begins, and which bands are narrow special cases. Special cases worth tagging: 60 meters uses specific channels rather than a continuous band, with its own power and mode restrictions. 30 meters is CW and data only, with a lower power limit than the other bands. 17 and 12 meters are small bands, and you can operate phone there as well as CW and data. Check the FCC Part 97 privilege chart or the ARRL band chart for exact frequencies before the exam, and use the same chart when you're actually on the air. Band plans and the legal limits aren't the same thing, so don't assume a gentleman's agreement is a rule, or vice versa. For digital modes, the exam leans on rules and concepts. Know that data emissions on HF are limited to specific segments, and that there are symbol-rate limits: below 28 MHz the limit is 300 baud, and the limit goes up on higher bands. Understand the difference between modes at a conceptual level: FT8 and similar weak-signal modes use timed transmissions and need accurate computer time, PSK31 is a narrow keyboard mode, and RTTY is the classic FSK mode. Know that the sound card interface and audio level matter, since overdriving causes splatter. Also be ready to explain why you wouldn't run high power on a narrowband digital mode. Common watering-hole frequencies like 14.074 MHz for FT8 are conventions, not regulations. For vanity calls: once you upgrade, you can keep your current call sign or apply for a different one. Which call sign groups you can pick from depends on your license class, and General gives you more options than Technician does. It isn't something to study for the test. After the upgrade, read the FCC's vanity call sign information and check availability in the database before applying. Fees and processing details change, so don't rely on a forum post for those.
-
Small lot or HOA: EFHW, doublet, inverted V, vertical or loop? What trade-offs actually matter
One point on SWR and coax loss that's worth separating out. SWR at the rig tells you only how well the transmitter sees the system, and a dummy load would show 1:1. What matters is how much power reaches the radiator and how much is lost on the way. Matched-line loss for common coax rises with frequency, and with high SWR the loss increases beyond that figure. That is why ladder line plus a tuner can beat coax on a band where the antenna is far from resonance: the line itself has low loss even at high SWR. The loss often occurs elsewhere in the chain, in the tuner, the balun or a choke that has saturated or is being driven at a mismatched impedance. Balun versus unun terminology also trips people up. A 4:1 balun on a doublet or OCFD is there to convert unbalanced to balanced and to match impedance. A 49:1 unun on an EFHW is mostly a transformer. Either way, the coax outside can carry common-mode current, which is why a choke of sufficient impedance is a common fix. If changing the coax length or touching the cable changes your SWR reading, that suggests the shield is part of the radiating system. Finally, on magnetic loops: a small loop can be a good fit for an attic or balcony, and it often has a lower receive noise level than a wire. It also has very narrow bandwidth, so you retune it whenever you move more than a few kHz. Its efficiency depends strongly on loop size and on resistive loss in the conductor and the joints, and the capacitor voltages can be high at power. It is a legitimate tool for a restricted site, but not the first thing to choose unless the HOA problem leaves no wire option. A practical way to compare candidates: use an antenna analyzer to find the resonances, check the effect of a choke on a given feed line, and then compare receive signal-to-noise on real signals. Modeling software such as NEC-based programs is useful for seeing how height and ground change the pattern before you put anything up.
-
Part 97 Q&A: where do hams most often slip on ID, third-party traffic, power, spurious emissions, RF safety and renewal?
I'll take the first four. Station ID (§97.119). You identify with your FCC-issued call sign at the end of each communication and at least every 10 minutes during a communication. "Communication" is the key word. A long QSO or net needs an ID at least every 10 minutes, and you also ID when you finish. Phone IDs must be in English, and CW or data IDs are fine too. If you're running a digital mode, you can ID in that mode as long as it uses a permitted code with a published specification. Tactical names like "Net Control" or "First Aid 2" are fine as extras, but they don't replace your call sign. A repeater under automatic control has its own ID obligation. Don't assume the repeater's ID covers you, because each station is responsible for its own. Third-party traffic (§97.115). A third party is someone other than the two licensed operators communicating. They can take part in a contact as long as the control operator is present and ensures compliance. Domestically that's straightforward. Internationally, third-party traffic is only allowed with countries that have a third-party agreement with the US, unless the third party is themselves a licensed amateur eligible to be a control operator. Check the current list of agreement countries before assuming a particular one is covered. Also note that third-party participation doesn't permit anything that is otherwise prohibited. Prohibited transmissions (§97.113). The big ones are: Communications for pay or any compensation, and business communications. There are narrow exceptions, such as a teacher using ham radio in a classroom, or emergency messages involving imminent safety of life or property.Music, except in limited incidental cases.Obscene or indecent language.False or deceptive signals.Broadcasting, which is one-way transmissions intended for general reception. Code practice, bulletins and beacons are carved out.Messages "encoded for the purpose of obscuring their meaning," with a narrow exception for space-station telecommand.Encryption is where people get tripped up. Using a published protocol is fine. Hiding the content of a message is not. Using a password for authentication is a different thing from encrypting the message payload, but when in doubt, don't hide the content.
-
Getting from licensed to useful: how do you structure ARES/RACES training, activation readiness and net discipline?
On the requirements question, a tiered approach seems to work well for many groups. Tier one is licensed, registered, with IS-100 and IS-700 certificates on file. Tier two adds net participation, a basic traffic-handling check-off and a completed ID or credential process with the served agency. Tier three is for people who will staff an EOC, shelter or command post, and it adds IS-200 and a supervised shift or exercise. This keeps newer operators involved without sending anyone into a facility before they are ready. On the net: consider alternating formats. One week is a casual check-in. The next week uses a short scenario, such as a weather event with a shelter opening, forcing a station to relay a message to net control, switch to a tactical call sign, or move to simplex. Rotating the net control chair also exposes who needs more practice before a real event does.
-
Planning a first portable QRP setup: 5 W CW/SSB, kit vs. KX2/KX3, antennas and LiFePO4 power
I'd decide the antenna first and choose the rig second. At 5 W the antenna and the band conditions dominate the result, and a simple, well-matched, reasonably high dipole or inverted-V will often beat a fancy rig on a compromised wire. On the EFHW: it is a convenient design, but treat the coax as part of the antenna. A transformer at the feedpoint with a long unchoked run of coax can put current on the shield and change the pattern and the SWR from one setup to the next. A choke at the transformer and a feedline kept short and routed away from the radiator usually helps. A resonant dipole fed through a 1:1 balun or choke is more predictable, and a linked dipole is easy to tune for each band, though you have to stop and change links. For the rig, a small CW monobander is a good way to start if you already know Morse and want something light with very low receive current. If you want SSB, the KX2/KX3 class makes more sense because you aren't limited to CW. A kit like a Pixie is best thought of as a learning project. Its sensitivity and selectivity are limited, so don't judge QRP by it. Build it for the fun, then use a more capable rig for serious operating. A useful habit: keep your CW exchanges short and clear, send at a speed the other operator can copy, and call for a few cycles before changing frequency. Low power rewards patience as much as hardware.
-
First POTA activation checklist: park references, 10 QSOs, spotting, two-fers and logging
Good list. I'd add a short paragraph on frequency selection. Before you call CQ, listen for a while and check the POTA spots page to see who else is active nearby on that band. Activators sometimes park right on top of each other, and a bit of space makes a big difference for hunters and for you. Pick a slot in the usual activity areas for your mode, ask whether the frequency is in use, and then call. On the 10 QSO target, keep an eye on how you count. Duplicates on the same band and mode generally don't help your total, so if the rate slows down, a change of band or mode can get you the rest. A second band, such as 40 m and 20 m, also helps with propagation. Ground-wave range on one band might not be enough, while skip on another may bring in new callers.
-
Getting started with LEO satellites: FM birds, linear transponders, Doppler and tracking setup
On the first-skill question, I'd say learn to recognise your own signal in the downlink before you worry about making contacts. Pick an easy FM pass, or listen to a linear transponder beacon, and just practise the tune-and-correct routine without transmitting. Once you know how the 70 cm side moves through a pass, calling becomes much less stressful. For the arrow antenna, a practical tip is to use the sky plot ahead of time. Know where the satellite rises, where it culminates, and where it sets, and point the boom ahead of it rather than chasing it. With a handheld setup the common mistakes are pointing from the screen rather than from the sky, and squeezing the antenna too tightly so that you introduce movement. Also keep an eye on feedline: a short coax run and a decent connector matter more at 435 MHz than people expect. One caution on FM birds: do not assume that because a satellite was usable last season it is usable now. Always check a current status page.
-
Band plan vs. FCC rules: how do you decide where to operate from 160 m through 33 cm?
Start with the legal-versus-voluntary split, because it answers half your questions. Part 97 (the FCC rules) sets which frequencies amateurs may use, which license classes may use which segments, which emission types are allowed where, and the power limits. Those are enforceable. The ARRL band plan is a voluntary agreement about how to share the space within those limits. It matters because of the good-practice and cooperation rules in 97.101, which say no frequency is assigned for the exclusive use of any station and that operators should cooperate in using the spectrum efficiently. Parking an SSB QSO on a weak-signal frequency probably won't earn a citation, but it's bad practice and you'll hear about it. On privileges, here's the rough shape, and you should verify exact edges against the current rules chart. Technicians have all privileges above 50 MHz, plus limited HF: CW on parts of 80, 40 and 15 m, and CW/data plus SSB on 10 m (28.000–28.300 CW/data, 28.300–28.500 phone), at 200 W PEP. Generals get segments of every HF band, including all of 160, 30, 17, 12 and 10 m. On 80, 40, 20 and 15 m, though, the lowest slices are Extra-only. For example, General phone on 20 m starts at 14.225 and Extra phone at 14.150. Amateur Extra has everything. Novice and Advanced licenses are no longer issued, but existing holders keep their privileges. On HF, the FCC assigns emission types by segment. The CW/data portions at the bottom of a band and the phone portions higher up aren't interchangeable just because a mode feels like it belongs there. 30 m is CW and data only, with a 200 W PEP limit, and it's shared with other services, so keep it quiet. Common FT8 dial frequencies (USB) like 3.573, 7.074, 10.136, 14.074, 21.074 and 28.074 MHz were chosen to sit inside the data segments. The FCC has also changed the data-emission limits in recent years (a bandwidth limit replacing the old symbol-rate limit), so check the current text instead of relying on older study guides. For band edges, think about where the signal actually is, not where the dial says. In LSB, the signal extends below the displayed carrier frequency by roughly 2.7–3 kHz. If a General's phone segment starts at 3.800 MHz, a dial reading of 3.800 isn't a safe place to talk, so stay a few kHz inside. In USB, the signal extends above the dial, so near the top edge, such as 14.350, keep the dial about 3 kHz below it. Treat that as a margin of safety. Dial calibration isn't perfect, and drift matters. On 60 m, the US doesn't have a continuous band like the others. It has five specific channels, shared with other users, so amateurs are secondary. Privileges are General and above, with a power limit expressed as 100 W PEP ERP relative to a half-wave dipole, which accounts for antenna gain. The operating dial frequencies in USB as commonly listed are 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz. Check the current rule text for the exact wording on emission types and bandwidth, since this section has been revised before. 5357.0 is the one you'll see most often for FT8.
-
Making SET and Field Day Scenarios Expose Real Weak Points Before a Disaster Does
I'd put message handling near the top of the list. It's easy to run a net where everyone checks in cleanly but no one has ever had to move a written message from an originator to a recipient without it changing along the way. A few things worth building into the exercise: First, use both formats your group is likely to encounter. A served agency may hand you a form such as ICS-213, while the formal radiogram format has its own structure: message number, precedence, handling instructions, station of origin, check (the word count), place of origin, filing time and date, addressee, text, and signature. Having operators convert between the two, without altering the meaning, is a good skill test. Check counts are a useful habit as well, since a mismatch tells the receiving station something went wrong in transit. Second, practice precedence honestly. Emergency, priority, welfare, and routine mean different things, and in an exercise people tend to label everything priority. Include a deliberate mix and see whether net control can sort it. Welfare inquiries in particular behave differently from agency traffic, so decide beforehand how your group would handle them and who it would coordinate with. Third, make the message text awkward on purpose: numbers, street names, unfamiliar surnames, medical supply names. Phonetics and "say again all after" get exercised quickly. Ambiguity at the originating end is a common cause of bad messages, so it's worth having the originator practice writing clearly as well. On served agencies, it helps to agree in advance, preferably in writing, on what they will ask for, who is authorized to hand you traffic, and what you are not going to be responsible for. An exercise that includes a real conversation with the agency contact often reveals gaps that a purely internal drill never would.
-
How do you separate real ham radio news from hype? Sources, checks and habits for rigs, firmware, FCC items and band openings
On the propagation side, I'd move spots to the top of the list and the indices to second place. A high solar flux number says conditions can be good, but it doesn't tell you whether your path to a particular region is open at this hour. A K-index spike can flatten HF paths, especially ones crossing high latitudes, even when the flux looks great. A simple routine is to check the current indices for context, then look at PSKReporter or the Reverse Beacon Network filtered to your grid square and the band you care about. If FT8 stations on 17 or 15 meters are reporting your signal far away, the band is open for you no matter what the dashboard says. If it's quiet, listen for beacons before you decide it's dead. Also worth remembering that a MUF map is a model, not a measurement. It's most useful when you cross-check it against real reports.
-
Getting a CW station to feel right: paddles, keyer settings, filters, QSK and where decoders fit
On the contest side, the choice of filter and AGC often matters more than raw speed. In a crowded band, a narrow filter can help you pull a callsign out of the pile, but if you're searching and pouncing you may want a slightly wider setting so you can hear nearby stations and avoid calling on top of someone. Many operators change filter width depending on whether they're running a frequency or tuning around. If you use CW Skimmer or an RBN-style spot feed, treat the spots as hints, not confirmations. Skimmer errors, busted calls and partial decodes happen, especially when someone is fading or when two stations overlap. It's still worth confirming the call by ear before you transmit. A good logger setup with function keys for your CQ, exchange, TU and a repeat of your callsign saves a lot of effort, but it helps to be able to send manually when the exchange gets unusual. One more thing about QSK: if you intend to use it with an amplifier, check the amplifier's documentation for its supported switching speed. A radio that handles QSK fine may not be happy driving a relay-based amp at the same speed.