Everything posted by Mod_Mike
-
Good on-air habits: CQ calls, breaking in, nets and handling interference without drama
Nets are where a lack of structure shows up fastest, so the net control station (NCS) role is worth a mention. A good NCS announces the purpose of the net, the frequency, and the format at the start, then calls for check-ins in a consistent way. They might ask for stations with traffic or emergency priority first, then regular check-ins, then late arrivals. When you check in, give only your callsign, phonetically if conditions are poor, plus any extra information the net asks for, such as your name or location. Don't launch into a chat, because the NCS is trying to build a list. Wait to be recognized. If you have to leave early, say "short time" at check-in, or follow whatever phrase that net uses. Then the NCS can take you early without making everyone wait. Listen to the NCS's instructions and don't answer other stations' check-ins unless you're asked to relay. If you're ever the NCS yourself, a written script with the net's open and close announcements takes a lot of stress out of running it. Clear signing-off helps too: "Net control is closing the net, thanks to all stations." Even for a casual net, a net that starts on time and ends when it says it will tends to keep its regulars.
-
Hamfest game plan: what to bring, what to test, and how to get more out of the day than a bag of cables
Good list. I'd add a printed or saved shopping list with model numbers and the rough price range you're willing to pay. It's easy to get talked into a bargain on something you didn't need, especially when you're walking past forty tables. A small power strip or a battery pack with a 12 V output is also handy for testing. Not every seller has power at the table, and a dead rig with no power source is hard to evaluate. For HTs, a spare known-good battery or charger tells you quickly whether the radio is the problem or the battery is. One more tip: do a lap before buying anything. The first table with a rig you want isn't always the best price, and you can often spot the same model two rows over for less or in better shape.
-
Which awards are worth chasing first? DXCC, WAS, WAZ, IOTA, WPX, POTA and SOTA compared, plus LoTW and QSL pitfalls
I'd also separate the programs by who does the verification, because it changes your workflow. DXCC applications can use LoTW credits, and paper cards have their own submission route, so a pile of old cards can still be useful if you plan the submission carefully. CQ awards have their own application process and a separate checking system, so something that is confirmed for DXCC isn't automatically accepted for WAZ without the right paperwork or data. For IOTA, the island group and the reference number matter more than the DXCC entity. Verify that the operation was within the group and that the confirmation details are valid. Some operators work an island and only later realize that the specific group wasn't credited because the QSL listed the wrong operating location. POTA and SOTA are great for building an activity streak, but keep the QSO logs organized by reference. If you hunt and activate, one ADIF file for everything can get messy. Splitting exports by program, or at least tagging each QSO with the park or summit reference, makes submission to the right system much easier later. And whatever program you're chasing, save a backup of your logbook before any bulk edit, import or upload. Correcting a few bad QSOs by hand is better than discovering the mess after a mass change.
-
Planning an HF shack around a 100 W rig: amp, tuner, PSU, filters, and grounding/bonding
On the amp and tuner chain, I'd add that the tuner should be sized for the mismatch it will see, not just the power. A tuner rated 1 kW into a 1:1 load can arc or overheat into a high-impedance mismatch on a band where the antenna is far off resonance. If you need a tuner just to make a particular antenna work on some band, look at whether the antenna or feedline can be modified first. Also check the amp's input SWR and the rig's foldback behavior. Some rigs reduce power sharply above about 1.5:1 SWR, and that can look like an amp that's under-driven. The internal tuner in the rig can mask this, so watch the meter while tuning with low power before keying up the amp. For power, I agree about voltage sag. Measure voltage at the rig's DC connector while transmitting, not at the supply, because the difference shows you the loss in the cable and connectors.
-
Make Every Contest QSO Count: A Confirmation Plan for LoTW, QSLs, and Award Credit
A contest weekend can put hundreds of contacts in your log, but a contact only helps your DXCC, WAS, WPX, or IOTA progress once it is confirmed in a form the award sponsor accepts. Many operators finish a contest happy with the score and then let the log sit. A little planning before and after the event turns a pile of QSOs into usable award credit. Start with the award, not the contestDifferent awards reward different things, and a contest can serve several of them at once: DXCC counts entities, so ARRL DX and CQ WW are rich hunting grounds. Each new entity matters more than your hundredth contact with a familiar one.WAS needs all fifty states. State QSO parties and Field Day put many stations in many states on the air, which makes them useful for finding the last few.WPX counts prefixes. Because the prefix is part of the callsign, almost every contest contact has award potential, and CQ WPX is built around it.IOTA depends on island groups. Contest stations on islands often announce this, but you have to notice it and log the contact correctly.Knowing which award you are working on tells you which contacts are worth a second look in the log, and which are only points for the score. Set up confirmation before the contest startsLogbook of The World (LoTW) is the most practical way to confirm many contacts, but it does not work until both operators have uploaded. Do the slow steps well in advance: Install TQSL and request your callsign certificate. Identity verification can take time, so do not leave it for the Friday before a contest.Confirm that your station location in TQSL is correct, including DXCC entity, grid square, and the zone or state details that apply to you. Wrong location data can create confusing matches or rejected credit later.Test your logging program's export. Know where the ADIF file is created and how to feed it into TQSL.Remember that Cabrillo is the format for submitting a contest entry. ADIF is the format you will normally use for LoTW and other logbook services. They serve different purposes, so do not assume one file does both jobs. Log cleanly while operatingConfirmation problems often begin at the key or microphone. A few habits help: Check the callsign. A busted call is the most common reason a contact never matches. If a call is partial or uncertain, ask for it again. In a pileup this costs seconds, but it can save a contact that you will never get back.Match band and mode. LoTW matches on band and mode groups, so a contact logged on the wrong band because of a missed frequency change will not match.Keep your computer clock accurate. LoTW matching allows a time window, but a clock that is minutes off can still cause mismatches. Use a reliable time sync, especially if you run digital modes.Log exchange details faithfully. State, zone, serial number, and other exchange data should be what you received, not what you assumed.Understand the weak points of contest confirmationsA contest does not guarantee that the other station uploads to LoTW. Some operators submit a contest log and never upload to any confirmation service. Others use LoTW regularly. That means your confirmation rate will vary depending on who you worked, how popular LoTW is in their region, and whether the contact was made in a well-organized event. For rare entities, DXpeditions and island activations often have their own logging and upload practices, and IOTA activators may not always follow the same workflow as mainstream contest stations. Treat any one confirmation channel as helpful but incomplete. Use a simple post-contest routineBack up the log in its original form before editing anything.Fix obvious errors, such as a callsign typo or an incorrect band, before you upload anything. Do this carefully and only when you are sure of the correction.Export ADIF and sign it with TQSL, then upload. Check the confirmation message so you know the file was accepted.Wait for matches over the following days and weeks. Confirmations do not all arrive at once.Look for award-critical contacts. Flag new entities, new states, new island groups, or new prefixes that are still unconfirmed.Chase the gaps, not the whole logOnce uploads settle, build a short list of unconfirmed contacts that matter. For DXCC, those might be new entities that appeared only once. For WAS, they might be the states you still need. For WPX, you may care less about any single prefix, since a large number of them will arrive over time, but you can still check for missing ones near an award threshold. For each gap you can try several options. Check the callsign for a typo. Look at the station's published QSL information, if there is any. Send a polite follow-up with your log details if the operator accepts them. Paper QSLs and bureau cards are slower, but they can still be useful for contacts that never reach LoTW and for awards that accept those cards. Always check the current rules and accepted confirmation types for the specific award before spending time or money on cards. Keep an award trackerA simple spreadsheet or the tracking tools built into many logging programs can keep your progress visible. Record the entity, state, prefix, or island group, the date, the band and mode, and the confirmation status. Separate columns for LoTW, paper QSL, and other methods make it easier to see where a contact stands. Do not rely only on memory or on how many contacts you remember making. Award programs have specific rules, and your own tracker should reflect what has actually been confirmed, not what you hope to get credit for. Beginner lessons that pay offYou do not need to win the contest to benefit from it. A few hours of focused operating can add several new entities or states.Accuracy beats speed when award credit is the goal. A clean log is more valuable than a large one with many busted calls.Prepare your accounts and software before the weekend. Waiting until after the contest to learn TQSL is stressful and risks delays.Choose contests that match what you need. If your WAS list is short, a state QSO party may be better for you than a worldwide event.Be patient. Confirmation is a long game, and many matches arrive well after the contest ends.Contests are great for making contacts quickly. Award chasing is about making those contacts count. If you handle the logging and confirmation steps with the same care you give to tuning and calling, each contest weekend will do more for your long-term progress.
-
Contest season roadmap: which major contests fit your station, what the exchanges look like, and how to avoid log-submission mistakes
One thing that helps is to treat the calendar and the rules as two separate checks. A calendar tells you roughly when something happens, but the sponsor's page is the authority on start and end times, bands, modes, exchanges and the log deadline. Contest rules do get revised, so a note you made from last year's event might be out of date. For log submission, a few habits save headaches. Let your logging program handle the exchange fields and duplicate checking, and run a test export to Cabrillo before the contest starts. Open the file and look at the header: callsign, category, operator names, club if you're claiming club score, and soapbox comments. If the sponsor offers a web log checker or robot confirmation by email, use it, and keep whatever confirmation you get. For VHF contests, double-check that the logger is set up for four-character grids and that you aren't accidentally entering six-character locators where the rules want four. For state QSO parties, confirm whether you need county abbreviations in a specific format. A logger plugin or the party's own cheat sheet is worth having open on the second monitor. Finally, if you only made a handful of contacts, still send the log. Small logs help with cross-checking, and a lot of contests explicitly welcome them.
-
Planning an HF shack around the rig: where should the money and effort go first?
Antenna system first, then the station infrastructure, then the rig upgrade. That ordering holds until the receiver is the limiting factor, which is more often a matter of crowded bands than of the radio being poor. If the noise floor at your location is high from local interference, a better radio won't change that, but a better antenna placement or a receive antenna might. On tuners, the wording "the tuner makes the SWR 1:1" causes confusion. It makes the radio's output stage happy, but you can still lose power in a lossy feedline, especially at higher bands. If you run a multiband dipole fed with ladder line, the tuner and balun combination matters as much as the antenna. For the amp question, I'd settle the power supply and the mains circuit before you shop, since the amp's requirements can force electrical work. Also check that the radio's ALC and band data connection are compatible with the amp's interface. It's easy to buy the amp first and find out later that the cable doesn't exist.
-
Studying for the Technician exam (Element 2): how should I use the question pool without just memorizing letters?
Start with the pool version, since it changes on a multi-year cycle. The question pool is published by the NCVEC, and each pool has an effective date range. Check which one applies to your test date with the VE team running your session or on the NCVEC site, and make sure your book, app or website matches it. A guide for the wrong pool will have questions that never appear on your exam. The structure helps you plan. The pool is organized into subelements (T1 through T9, plus T0 for safety), and each subelement is divided into groups such as T1A or T5B. The exam draws one question from each group, so every group is worth roughly the same. You can't skip a whole area, because each group shows up once. The passing score is 26 of 35, so you can miss nine. For study time, I'd weight it by how abstract the material is for you. Rules and operating practices are mostly recall, so repetition works. Electronics and radio wave topics are where understanding pays off, so spend more of your first pass there and give it a second look later. For practice tests, take one early as a diagnostic and then study your weak groups. A missed question tells you something only if you can say why the right answer is right. If you can't, read the explanation in the guide, or look up the underlying idea, before moving on. Shuffled answer order helps, because it keeps you from memorizing 'it was C.'
-
Dead rig triage: no TX, no RX, or both. What do you check first, and in what order?
On blown finals, the key question is why they failed. Replacing the transistors without finding the cause usually means replacing them again. The usual causes are high SWR with weak protection, bias runaway, a failed driver stage overdriving the final, a supply over-voltage, or parasitic oscillation. Before applying power to the new devices, check the bias circuit: bias resistors, any bias-regulation transistor, and the thermal-tracking diode if the design has one. Also check the output network, because a shorted or open component there can destroy the new parts quickly. When you do power up, use a current-limited supply starting at low current, a dummy load, and the service manual's idle-current procedure. If the final stage is push-pull, use matched devices if the manual calls for them. Mount them with fresh thermal compound and make sure the heatsink is flat and clean. For a scope on this kind of job, check the drive waveform into the final, watch the ALC and protection lines during a short key-down, and look for oscillation when no drive is applied. A final stage that draws current with the drive removed is oscillating or has a bias problem, and you should stop there before it cooks the parts. On the older versus modern question: with older discrete rigs the service manual's alignment and voltage tables will usually take you most of the way. With newer radios, the firmware, the configuration, and the surface-mount parts make signal tracing harder, so check the settings and the power rails thoroughly before opening the radio up.
-
One field kit for SOTA, POTA and Field Day: where do you split the weight and complexity?
For a single antenna, an EFHW for 40/20/15/10 is hard to beat on weight. The thing people tend to underestimate is the counterpoise and feedline situation. With a typical EFHW the "other half" of the antenna is effectively the coax shield and whatever it touches, so a short run of coax with a common-mode choke near the matching unit makes the SWR and the radiation pattern far more repeatable. If you notice the SWR change when you move your hand near the coax, that's the cable telling you it's part of the antenna. A linked dipole is easier to reason about, but you pay for it in setup time and in small things like a link that's gone missing in the grass. A trick that helps is color-coding the link ends and keeping the whole thing wound on one card or spool so nothing separates. If you operate from a lot of summits where time and wind matter, simple often wins. On battery sizing, a rough way to think about it is to take the rig's average current rather than the peak. On SSB the average draw is a fraction of the transmit peak, because you're only transmitting part of the time and speech has a low duty cycle. Receive current is small but not nothing. A modest pack of around 6 to 10 Ah is generally enough for an activation at 10 to 20 W, but do the math with your own radio's spec sheet. Then add margin for cold, since capacity drops in low temperatures.
-
Getting from 5 to 20 WPM: plateaus, head copy, callsign drills and when to go on the air
I'd separate two things you've lumped together: copy speed and operating speed. You can be a 20 WPM copier and still get lost in a QSO, because a real exchange is not random text. It's patterned: CQ, callsign twice, DE, your callsign, K. Name, QTH, RST, rig and weather, 73. Once those patterns are familiar, a lot of the content becomes predictable and your head copy has less to do. It's worth writing out a standard QSO template and drilling it until each element feels automatic. For a first on-air contact, a few things tend to help. Pick a quiet part of the band rather than a busy one. Answer a CQ that is sent a bit slower than your limit. Keep your first reply short (callsign, RST, name) and use ? or AGN without embarrassment. Operators are generally used to being asked to repeat or slow down, and "QRS" is a normal request. If you freeze, a short "PSE QRS" is better than guessing. On nets: a slow CW net, where one is available in your area or on your band, can be a low-risk way to practice because the exchange is structured and the speed is capped. I wouldn't treat it as a replacement for drills, though. It's mostly practice at the skill of staying calm while copying live, which is hard to train any other way.
-
Stuck at 15 WPM: how do you split practice time between sending, copying, and gear tweaks?
On the sending side, record yourself and play it back. Most problems show up immediately: crowded letter gaps, short dahs, or an extra element after a squeeze. Listen for spacing before worrying about raw speed. Clean code at 18 WPM is usually easier to copy than ragged code at 25. For contests, a few habits help a lot. Send your callsign once and clearly, and repeat it only when asked. Learn the common cut numbers used in your contest, like T for zero and N for nine, if they're accepted. Don't match a faster station's speed if you can't copy cleanly; most good operators will slow down when you ask with QRS. If you want practice without pressure, tune around and copy exchanges before you call anyone. On gear, use a narrow filter, but widen it when you're searching or you'll miss callers. Skimmer or an RBN-style spot list is a good way to confirm what you thought you heard, but keep your own copy as the primary source. If your decoder and your ears disagree, that's a useful hint to listen again, not necessarily proof that either one is right.
-
Band plans vs. FCC rules: how do you decide where to operate on 160 m through 33 cm, and how close to the band edge is safe?
The short version is that the FCC sets the sub-band limits by license class, mode and power, and the ARRL band plan sits on top of that as a voluntary agreement about who goes where. Nobody can cite you under Part 97 for running FT8 at 14.080 instead of 14.074, but you'll annoy people. Running phone below 14.150 as a General, or on 14.225 as a General when you've mixed up the Extra-only slice, is a rules problem. The HF structure by class works like this. Technicians get CW only on 80, 40 and 15 m (3.525–3.600, 7.025–7.125, 21.025–21.200), plus 10 m from 28.000 to 28.500. On 10 m, 28.000–28.300 is CW and data and 28.300–28.500 is SSB, all at 200 W PEP. Generals get segments on every HF band, including 160 m, 30 m, 17 m and 12 m. Their phone segments are roughly 3.800–4.000, 7.175–7.300, 14.225–14.350 and 21.275–21.450. Extras get everything the General has plus wider phone and CW slices: phone from 3.600, 7.125, 14.150 and 21.200, and Extra-only CW/data slices at the bottom of 80, 40, 20 and 15 m. Advanced licenses are no longer issued, but existing holders keep privileges that fall between General and Extra. 30 m is a special case. It is CW and data only, no phone, with a lower power limit (200 W PEP). 12 m and 17 m are also data-friendly, and phone sits in the upper part of each. For band edges, remember that your occupied bandwidth has to stay inside the allowed segment, not just your dial frequency. An SSB signal is about 2.4–3 kHz wide. If you're on USB, the signal extends above the dial frequency, so on 20 m, 14.347 USB is not a good idea if the upper edge is 14.350. On LSB, the signal extends below the dial, so at the bottom of a phone segment keep your dial a few kHz above the edge. The convention is LSB below 10 MHz and USB above, which is why 80 m and 40 m phone edges are always about the lower limit and 20 m and up are about the upper one. Also remember your rig's displayed frequency can be off a little, so leave margin instead of operating 100 Hz from the line. 60 m is channelized, not a band with sub-bands. The five US channels are usually listed by their USB dial frequencies: 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz. They are open to General and above, with USB (plus CW and some digital modes) and a 100 W ERP limit referenced to a half-wave dipole. 5357.0 is the one FT8 and similar modes often use. Because the rules and the allocation have been changing (internationally there is a 5351.5–5366.5 kHz allocation, and the US rules have lagged), read the current §97.303 text instead of relying on a forum post from a couple of years ago. A few band plan items worth knowing: CW QRP calling is around 7.030, 14.060 and 21.060. The NCDXF/IARU beacons on 14.100, 18.110, 21.150, 24.930 and 28.200 are on fixed frequencies, so don't park on them. And 3.790–3.800 is an informal DX window on 75 m that domestic stations are supposed to leave alone for DX contacts.
-
LoTW, eQSL, Club Log OQRS, bureau or direct: how do you decide which QSL route to use?
On direct cards and bureau, here are the mechanics, since that's where people get tripped up. A direct request normally has your card (or a clear note of the QSO details), a self-addressed envelope, and return postage. For overseas stations, "green stamps" means US dollar bills, and the amount the operator asks for is the thing to follow. International Reply Coupons have become harder to use, so check what the station actually wants. Postal rates change, so look up the current ones instead of reusing an old number. Many people use a plain outer envelope without a callsign, and some slip a stiff piece of paper in so the card isn't obvious through the envelope. Use the address and QSL manager shown on the station's page, and send to the manager if there is one. Bureau is slower and cheaper. Cards are sent in bulk through your national society's outgoing service and then sorted by the destination country's bureau. Plan on months, sometimes longer, so don't treat a missing card after a few weeks as a problem. ARRL members can use the outgoing service, and incoming cards in the US come through the area bureaus, which usually want envelopes on file. For your own card design, put the essentials where they can be read at a glance: your callsign in large type, the other station's call, date and time in UTC, band, mode, RST, and a clear "QSL" or "TNX" line. Adding your grid square and CQ/ITU zones helps, and many people use the standard 9 x 14 cm size, which fits bureau handling better. Keep the back clear enough for the stamp and any marks from the bureau or checker. A nice photo is optional. Legible details matter more.
-
Run or Search and Pounce? Choosing an Operating Style That Fits Your Station and Your Awards
Every contest weekend, you decide between two ways of operating, often without noticing. You can run, which means parking on a frequency and calling CQ so others come to you. Or you can search and pounce (S&P), tuning the band and calling stations you find. Neither one is better in general. The right choice depends on your antennas, your power, the contest, and what you want out of the weekend: a score, a new multiplier, or progress toward an award. What each style is good at Running builds rate, the number of contacts per hour. A steady run frequency can produce long strings of QSOs with very little tuning. It works best when you can be heard reliably. That usually means a decent antenna, a clean signal, and a band that is open to a populated area. It also puts you in front of stations you would never have found by tuning. Search and pounce builds variety. You can work a station once, log it, and move on. That makes S&P a good way to collect multipliers, such as new countries, zones, states, or prefixes. It is also the practical choice with modest power or a small antenna, because a strong station calling CQ is far easier to work than being the weak one calling. Most good contest strategies mix the two. You run when the band is giving you rate, then switch to S&P to pick up multipliers that your run frequency never produced. Rate and multipliers: how they trade off Contest scoring generally combines points from QSOs with a multiplier count. That creates a tension. A new multiplier is worth more late in the contest than early, because it multiplies a bigger QSO total. Meanwhile, hunting for a rare multiplier can cost you minutes of rate. A few rules of thumb help: Early on, focus on rate and let the multipliers come naturally. When your run slows, use the downtime to tune for multipliers instead of calling CQ into silence. On each new band, a quick sweep for multipliers can be worth more than the same minutes spent running. Check the rules for your contest. Multiplier definitions differ, and some count per band while others count once overall. Match the contest to the style Different events reward different habits. ARRL Field Day is more of an operating event than a pure race. It rewards activity, emergency-style setups, and a wide mix of modes. Many groups run stations around the clock and rotate operators. It is also a friendly place to learn logging and exchange procedures. CQ WW (separate SSB and CW weekends) is a worldwide event where DX is the point. Zones and countries are the multipliers, so it suits anyone chasing DXCC entities. Because the whole world is on the air, even a small station can find multipliers by S&P. ARRL International DX Contest has a different shape depending on where you live. Stations outside the US and Canada work US and Canadian stations, and the reverse applies for those in the US and Canada. Check the current rules for your side of the exchange. State QSO parties are a good source of WAS contacts. In-state stations often work everyone, while out-of-state stations may chase counties or the local multipliers. These contests can fill in the awkward states that never seem to show up on ordinary band days. CQ WPX uses prefixes as multipliers, which suits people building a WPX tally. Each new prefix is a multiplier and a step toward the award. Always confirm dates, categories, and exchanges from the official rules. They change from year to year. SO2R without the hype SO2R (single operator, two radios) lets you use one radio to call CQ while the other tunes for the next contact. In practice you are filling dead time. Each CQ gap on radio one becomes a chance to search on radio two. It is not a beginner requirement, and it can hurt more than it helps if the station is not ready. The usual problems are: Receiver overload: a nearby transmitter can swamp the second receiver unless you have filtering and good antenna separation. Audio switching: you need to know which radio you are hearing and transmitting on, or you will send an exchange on the wrong one. Logging errors: two radios double the chance of a mismatched callsign or frequency. A reasonable first step is a simple version. Run on one radio and use the second only to listen for multipliers. Add transmit control later, after you are comfortable with the single-radio flow. Logging habits that protect your score and your awards Good logging does two jobs. During the contest it speeds up your exchanges. Afterward, it feeds your award records. Use contest logging software that handles the exchange and checks for duplicates. Confirm your CAT or rig-control setup before the contest starts, so the log records the right band, mode, and frequency. Fix callsign errors immediately. A bad call is a lost QSO and often a penalty. Keep your station location details consistent, because award software and confirmation services match on those fields. Turning contacts into confirmed progress A contact only counts toward most awards once it is confirmed. For DXCC, WAS, WPX, and IOTA, the details of what is accepted depend on the sponsor, so read the current award rules. In general: Logbook of The World (LoTW) confirms a contact when both stations upload matching logs. Both sides need to be valid, and the details must agree closely enough to match, including band, mode, date, and time. Paper or electronic QSL cards still matter for some awards, particularly where an operation is not on LoTW. Contest logs and award tracking work best when you upload promptly. A stale log leaves you with unconfirmed contacts you could have had weeks earlier. Track your progress by category as well as by total. DXCC is about entities, WAS is about states, WPX is about prefixes, and IOTA is about island groups. A single weekend can move several of those counts at once, but only if you note which contacts are new for each award. Beginner lessons that pay off quickly Enter for a few hours. You do not need the whole weekend. A short session teaches the exchange and the pace. Listen first. Hear a few exchanges before you call, so yours matches what people expect. Keep your exchange short and clear. Repeat only what is needed. Clarity beats speed when the band is crowded. Have a goal. A new state, a new zone, or ten more prefixes is easier to chase than a vague aim to do well. Mix running and S&P. Try both and notice which one fits your station. Upload your log and check your confirmations. Contest activity only turns into award progress once the matches show up. Choosing between running and S&P is really a question about your station, your time, and your goals. Start with the style that fits your antenna and your pace, and add the other when it makes sense. After a few weekends, you will know where your rate comes from, which multipliers you are missing, and which awards each weekend moved forward.
-
Part 97 compliance Q&A: station ID, third-party traffic, power limits, RF safety, spurious emissions, control operation and renewal
I'll take the first four. Identification (§97.119): you give your FCC-issued call sign at the end of a communication and at least every 10 minutes during it. You don't have to ID at the start of a contact. The ID has to be in a form the rules allow. On phone that means English, and you can use the ITU phonetic alphabet. On CW it's Morse. On RTTY or data it's in that same digital mode. On a repeater, each user station has its own ID obligation. The repeater's automatic ID does not cover you. A tactical call sign like "Net Control" or a served-agency designator is fine for operational clarity, but it doesn't replace your FCC call sign. Third-party traffic (§97.115): a third party is someone other than the control operator and the station you're talking to. Their participation is allowed as long as the control operator is present at the control point, monitoring, and able to stop the transmission immediately. The message also can't be something §97.113 prohibits. International third-party traffic is the usual trap. It's only allowed with countries that have a third-party arrangement with the US, or when the third party is eligible to be a control operator of that station. Check the current list before inviting a guest to talk to a foreign station. Power (§97.313): the headline limit is 1500 W PEP output from the transmitter, and you must use the minimum power necessary for the communication. There are lower caps in specific places. The 30 meter band is limited to 200 W PEP, and Technician HF privileges are limited to 200 W PEP. The 60 meter band is defined differently, in terms of effective radiated power relative to a half-wave dipole. Power is a separate issue from class. A license class decides which frequencies and modes a control operator may use. The power limit applies to everyone. Prohibited transmissions (§97.113): the big categories are communications for pay or in which you have a pecuniary interest, communications on behalf of your employer, broadcasting, music, obscene or indecent language, false or deceptive signals, and messages encoded to obscure their meaning. Be careful with the last one. Normal digital modes with published protocols are fine, but encryption meant to hide the content is not, with narrow exceptions such as control signals to a space station. There are also limited carve-outs, for example for teachers and for certain bulletin and code-practice transmissions. Emergency communications under §97.403 are a separate matter.
-
Getting from 5 wpm to 20 wpm: a practice plan, plateau fixes, and where software fits
On paddles and keyer settings, begin with the sidetone at a pitch that's comfortable for long sessions, often somewhere in the 500 to 700 Hz range, and set your receiver pitch to match. Keep the keyer at the speed you can send cleanly, which is often below what you can copy. Sending faster than you can copy invites bad habits. Weighting and dit-dah ratio are best left at the default 3:1 until your timing is solid, because a heavy or light weighting can mask sloppy spacing. Paddle adjustments matter more than people expect. Contact spacing that's too wide makes you work harder and slows you down. Too narrow and you'll get double dits or stray elements. Tension is a matter of comfort. Set it so the paddle returns reliably without feeling stiff. Iambic mode A versus B (and what a particular keyer calls them) changes what happens when you squeeze, so try both and look at what the keyer does with an extra element at the end of a character. Record yourself sending and listen back, since flaws in spacing are easier to hear on playback than while sending. On software versus ear, a decoder can be useful as a check after you've tried to copy something yourself. It tells you whether you misheard or just lost the thread. As a crutch, it works against you. Decoders also struggle with fading, noise, hand-sent timing and uneven spacing, which is exactly what real bands deliver, so relying on one doesn't prepare you for live copy. A reasonable use is to run it during a practice session, look only afterward, and treat the mismatches as a list of characters to drill. For on-air practice, a slow-speed net or a casual QSO with someone patient is a better first step than a contest, because you can ask for a repeat or slower speed. Contests are excellent for callsign and exchange copy once you can handle the exchange pattern, since the same short format repeats constantly. Check current net listings and contest rules and schedules from the organizers before you plan around them, since details change. Having a few canned phrases ready, such as PSE QRS, AGN and QTH, makes the first contacts less stressful.
-
Band plan vs. license privileges: how do you work out where you can operate, and how close to the band edge is too close?
On VHF/UHF the band plan matters even more, because FM voice, weak-signal SSB and CW, repeaters, satellites and beacons are all squeezed into relatively small slices. The usual pattern is that the very bottom of each band is for weak-signal work (CW and SSB, sometimes EME), with digital and beacons nearby, and FM simplex and repeaters above. On 6 meters, the weak-signal area is at the bottom of the band. The CW-only portion is at the very bottom, and 50.1 to 50.3 MHz is the usual SSB/CW area. The DX window is around 50.110 MHz, and 50.125 MHz is the common domestic SSB calling frequency. FT8 is typically near 50.313 MHz. FM simplex activity is higher up, with 52.525 MHz commonly used as a national FM calling frequency. On 2 meters, 146.52 MHz is the national FM simplex calling frequency. Many people use it as a rendezvous: you call, then move to another simplex channel to talk. Repeaters sit on pairs that vary by region, which is why your local frequency coordinator's list matters. For weak-signal work, 144.200 MHz is the SSB calling frequency, and FT8 is commonly on 144.174 MHz. On 70 cm, 446.0 MHz is the national FM simplex calling frequency, and 432.100 MHz is the usual SSB/CW weak-signal calling area. On 33 cm, activity is much thinner and is concentrated around the weak-signal calling frequencies in the ARRL plan (902.100 MHz, with 903.100 MHz as an alternate). Check the plan if you want to try it. Technicians have full privileges on all of these VHF/UHF bands, which is one reason they are such a good place to explore. Two caveats are worth keeping in mind. First, 70 cm and 33 cm are shared bands, and amateur operation there can be secondary to other services. In some areas there are geographic or power restrictions on 70 cm, and 33 cm shares spectrum with unlicensed devices, so noise and interference can be a real issue. Second, allocations differ by ITU region. The US is in Region 2. Examples include 40 meters, which is 7.0 to 7.3 MHz in Region 2 but narrower elsewhere (7.0 to 7.2 MHz in Regions 1 and 3), and 33 cm, which is a Region 2 allocation that isn't available in Region 1. 70 cm is 420 to 450 MHz in Region 2 but 430 to 440 MHz in Region 1. Your US license does not automatically grant operating privileges abroad. Look into the specific reciprocal or CEPT arrangements before you travel. IARU band plans for each region are also voluntary, like ARRL's, but they are what most operators outside the US follow.
-
When should hams stick to the standard phonetic alphabet, and when are alternatives acceptable?
Adding to the above for names, numbers, prosigns and nets. Names and locations: say the word normally first, then spell only if needed. For example, give the town name, then say "I spell" and go through the letters phonetically. Don't spell every word in a sentence, because it just slows the exchange. For locations you might add a Maidenhead grid square or coordinates when the name is unusual. Spelling the first few letters is often enough to resolve it. Numbers: speak digits one at a time. Say "one four seven" rather than "a hundred forty-seven" for anything that must be copied exactly, like frequencies, grid squares, serial numbers or addresses. The ICAO-style pronunciations ("niner" for 9, and so on) are used in aviation and some ham circles, but they're a convention rather than a requirement. "Niner" is common because "nine" can be confused with "five" or with the German "nein" in some environments, but plain digits are fine on most ham bands as long as they're clear. Prosigns: in voice, the equivalents are words. "Over" means you're handing the channel back and expect a reply, and "clear" or "out" means the contact is finished. "Over and out" is contradictory, so avoid it. In CW, prosigns are sent as a single run-together character, such as AR for end of message, SK for end of contact, K or KN to invite a reply, and BT as a separator. Don't mix CW prosigns or Q-signals into plain voice traffic where listeners may not know them. Nets: net control usually asks for check-ins by callsign suffix, the last letters of the call, to keep things fast. If you check in, say your suffix phonetically once and wait for acknowledgement. Don't give long-winded signoffs, because net control is managing a queue. Say your location and status or traffic if asked, and keep to the net's format. Emergency traffic: during a real emergency, clarity beats style. Break in only with emergency or priority traffic, say it plainly, and use phonetics for callsigns, names and anything that can't be mistaken. Many served-agency and incident-management guidelines recommend plain language over ten-codes or personal shorthand, since different agencies use different codes. In an exercise, the traffic should clearly state that it is an exercise so no one mistakes it for a real event. Repeat critical items, such as names, addresses and numbers, and read them back to confirm.
-
How should I study for the Technician exam (Element 2)? Pool tips, weak spots, and practice test strategy
Start by confirming which question pool your exam session will use. Pools are rotated on a published schedule, and a study guide or practice site built on the wrong one will give you outdated questions. Your VEC or the session coordinator can tell you, and good practice sites label the pool they use. On format: you need 26 of 35 correct to pass, and the 35 questions are spread across the pool's subelements, with a set number from each. Since every subelement is represented, ignoring one topic is risky. Strength in one area won't cover a blank in another. I'd read a guide first and then switch to practice questions. Pure memorization works for some people, but it tends to fail when a question is reworded or the answer order changes. If you understand why an answer is right, you can handle variations. For the pool's regulation questions, some memorization is unavoidable, so a few flashcards help there. For practice tests, don't just track your score. After each one, write down the topic of every miss and go back to those sections. A common rule of thumb is to score comfortably above passing, say 85-90%, on several fresh practice exams before booking. That's a guideline, not a guarantee.
-
Repeater programming checklist: offsets, CTCSS/DCS, linking modes and etiquette that matches the system
Etiquette gets more interesting once linking is in the mix. On a plain FM repeater, the usual habits apply. Listen before you transmit. Identify with your callsign as your licence requires. Leave a short pause between overs so others can break in. Use 'break' only for urgent traffic. Don't kerchunk to 'test' the repeater, because a short call with your callsign is a better test. On a linked system, add a longer pause, as the delay from the internet link or the link radios can mean someone else is already talking at a remote site. Each linking system works a little differently. EchoLink uses VoIP and node numbers, and it can link a repeater to a conference or to a single station. IRLP uses DTMF commands and numbered nodes and reflectors. AllStarLink is based on Asterisk and app_rpt, and is common for hubs and custom links with DTMF control. Wires-X is Yaesu's system for System Fusion, using nodes and rooms. Before you issue any DTMF command, listen for the system's published rules, because connecting a repeater to a busy net or reflector can disrupt people who didn't expect it. Also, announce when you change or drop a link. For DMR, the repeater's color code must match, and you need the right timeslot and talkgroup in your codeplug. You also need a registered DMR ID. A static talkgroup is permanently routed to the repeater, whereas a dynamic one is brought up when you key it. On a busy talkgroup it is considerate to listen first and not to key up just to check it works. On D-STAR, the RPT1, RPT2 and UR fields in your radio define how your call is routed, and reflector links (REF, XRF, DCS) need to be used with care. For all of these digital modes, the club or repeater owner will normally publish settings and rules, so read those before you transmit.
-
From FM Birds to Linear Transponders: Doppler, Tracking, Antennas and What to Expect on Each Pass
On linear birds, the thing that usually breaks people's first few attempts is not the antenna, it is the tuning loop. If you chase your own signal with the main dial while the software is also moving the uplink, you create a feedback problem. A cleaner method: let the software handle Doppler for the downlink you are listening on, and make only small corrections with the RIT/XIT or sub-VFO. Then the frequency you hear stays put, and the other station will not need to chase you. On an inverting transponder like RS-44, this also keeps the sideband logic straightforward: you transmit one sideband, and you will hear the opposite on the downlink. Also, test the full duplex path before you use a pass. Listen to the beacon, transmit at low power into a dummy load or a lower setting, and see whether your receiver front end desenses. 2 m and 70 cm are close enough for some rigs, and receive overload or desense from a nearby transmitter can look like a weak satellite.
-
Dynamic range and gain staging on budget SDRs: why the waterfall fills with ghosts, and what actually fixes it
The terminator test is the most underused one here. If the displayed noise floor doesn't rise at all when you plug in the antenna, you're receiver-noise-limited and more gain is worth trying. If it rises sharply, you are probably noise-limited by the environment, and a better antenna position or choking the feedline will do more than a new SDR. On HF, one thing to watch is that an electrically short antenna plus an upconverter doesn't need huge gain, because the band noise on the lower HF bands is often well above the receiver's own noise. Active loops and short whips can look great on a waterfall and still overload on strong mediumwave or shortwave broadcasters. A mediumwave notch or a switchable high-pass filter ahead of the converter is often cheaper than changing hardware. Check that the software's frequency offset really matches the converter's LO, or you'll chase "wrong" frequencies for an evening.
-
Picking a VHF/UHF antenna: J-pole, slim jim, 5/8 whip, collinear or yagi, and where the dB really go
On mobile installs, the mount usually matters more than the antenna on top of it. An NMO mount, which needs a 3/4 inch hole, gives you a solid electrical connection to the body and a repeatable ground plane. Placing it in the middle of the roof gives the most symmetrical pattern. A trunk-lid or fender location tilts the pattern and can reduce gain in some directions. A mag mount is a fair compromise if you can't drill. Clean the surface and the magnet, avoid routing the coax in a way that pinches it in a door or hatch, and remember that the coupling is capacitive, so it depends on the area under the magnet. Also lift it now and then and wipe off grit, which can scratch the paint. For a 70 cm mobile, a 5/8-wave or even a collinear-style whip can be a nice step up from a quarter-wave, but on a vehicle with a lot of roof curvature, check the SWR across the band and the actual performance rather than trusting the label. Cable length matters too. Excess coax coiled up behind a panel is fine, but a very long run of thin cable on UHF is a loss that no antenna gain will fix.
-
Planning a 24-hour EMCOMM station: generator or LiFePO4, and how do you keep noise and grounding under control?
On the battery side, a few details are worth checking before you buy. Voltage: a 12.8 V nominal LiFePO4 pack charges to about 14.2 to 14.6 V and sits around 13.2 to 13.3 V under light load, which is fine for most rigs rated for 13.8 V plus or minus 15%. Check your rig's spec. Sag under a 20 A transmit load is mostly a wire and connector problem, so use heavy enough gauge, short runs and properly crimped Powerpoles or similar, with a fuse close to the battery. BMS behavior: when a pack's battery management system trips on over-current or low voltage, it can cut power instantly, with no slow decline to warn you. Decide in advance what your low-voltage alert is, such as a voltmeter on the bus, and what happens when it trips. Also, most LiFePO4 packs shouldn't be charged below freezing unless the pack specifically supports it, so cold-weather deployments need a plan. Solar: use an MPPT controller with a LiFePO4 charge profile, and test it for RFI while it's actually charging. Panels in full sun can feed a lot of current, and the controller's switching noise can get into HF receive. Keep it well away from the antenna and feedline, and use short, tidy panel leads. Antenna: put a 1:1 current choke at the feedpoint of any end-fed or dipole, and consider another where the coax enters the shelter. If the coax shield carries common-mode current, it becomes part of the antenna and picks up noise from everything in the tent. Guy the mast at three points about 120 degrees apart, keep the whole fall zone clear of power lines, and set the stakes before you raise the mast. For HF, RG-8X or similar is usually fine at these lengths. For VHF/UHF, coax loss adds up quickly, so keep that run short or use a lower-loss cable. For the checklist, put the order of operations on paper: site survey and hazard check, shelter, generator or power placement, mast and guys, feedline, power bus, radios, noise check, then log your first contacts. Reverse it for teardown, and add a final step to walk the site for stakes, cable ties and fuel containers.