Everything posted by Mod_Chad
-
Before you key up a new repeater: offsets, tones, linking and etiquette checklist
When a repeater won't respond, I'd work through these in order, because the cause is usually simple. First, confirm you are actually hearing the output. If you can't hear anyone, you may be out of range or on the wrong frequency. Many radios have a reverse (REV) function that lets you listen on the input. If you hear a local station clearly on the input but they are weak on the output, you are probably close enough to talk simplex and don't need the repeater. Second, check the offset direction and the tone value. A tone that is off by one entry in the CTCSS list (for example 100.0 versus 103.5) will keep the repeater closed. Remember that a repeater can use different tones for input and output. If you also turned on tone squelch with the wrong output tone, you'll hear nothing at all and may assume the repeater is dead. Third, check access. Some repeaters are open to any licensed amateur, with the owner still setting the rules. Others are closed or limited to club members, or require a specific tone that is only given to members. A closed repeater isn't being rude; the licensee is entitled to limit access, and some are closed to cut interference or abuse. Check the club page or contact the trustee rather than hunting for the tone yourself. On directories: RepeaterBook and club sites are handy, but entries go stale. A repeater can change its tone or go off the air without the listing being updated. In the US, repeaters are typically coordinated by a regional frequency coordinator. If two repeaters interfere, the coordinated one generally has priority in a dispute, which is one reason clubs bother with coordination. Check the date or notes on a listing and, if you can, confirm it with the owner.
-
Getting usable HF from an SDR: direct sampling vs. upconverter vs. a purpose-built receiver, and where the noise really comes from
On the panadapter question, the two approaches solve different problems. A standalone SDR gives you a whole receiver. A panadapter taps the transceiver's IF and uses the SDR for the display only, so audio quality, filtering and AGC stay with the radio. The common pitfalls are the IF level and frequency alignment. The tap needs to be properly buffered so you don't load the radio's receive path, and the SDR software needs the right offset to show true frequency. Without CAT or a similar link, the waterfall will drift from what the radio is tuned to. For digital modes the signal path is mostly the same regardless of the receiver. Demodulate in SDR software, then pass audio to the decoder through a virtual audio cable or a loopback device. WSJT-X handles FT8 and similar modes. fldigi covers many older modes. Satellite and data decoders like SatDump or rtl_433 often work from IQ directly. Watch the sample rate and the audio level, since an over-driven soundcard path is a more common cause of failed decodes than the SDR itself. Clock accuracy also matters for narrow modes, so a TCXO or a calibrated PPM offset is worth setting up.
-
When to use standard phonetics on the air, and when plain speech is enough
On the first question, the lists are effectively the same. The spelling alphabet most people call NATO is the ICAO radiotelephony alphabet, and the ITU uses the same code words in its Radio Regulations. The official spellings are "Alfa" and "Juliett". They were chosen so that speakers of English and French pronounce them the intended way. Saying "Alpha" or "Juliet" on the air won't cause a misunderstanding, but the official spellings are the ones to teach if you want to be consistent. The other words are Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee and Zulu. On the rules side, amateur licensing doesn't usually require a particular list. In the US, for example, Part 97 allows a phonetic designator when you identify, and it doesn't prescribe which one. Check your own regulator's wording, but the practical convention is the standard list. It's the one the other station is most likely to have heard before, and that matters most when the signal is poor. For callsigns, here's a rule of thumb. If the band is quiet and the signal is solid, a memorable word association is harmless and sometimes friendlier. In a pileup, on a weak signal, in heavy QSB, or with someone whose first language isn't yours, use the standard words, because that's what the other station is trained to expect. Non-standard words can be mistaken for part of a different callsign or for ordinary speech. Mixing standard and improvised words in the same call is the worst case, since the listener can't tell which parts are letters. When you're not being copied, it also helps to be methodical. Give your full callsign once, slowly, in phonetics, then repeat it once. Don't send it five times in a row at speed. Where there's heavy interference, many operators send the whole call, then only the part the other station seems to be missing, in standard phonetics.
-
Technician to General: how should I split study time across Element 3's 35 questions and the HF sub-bands?
Both approaches work, as long as you read the explanations and don't just memorize answer letters. Run timed 35-question practice exams from the current pool. After each one, sort your misses into buckets: rules, propagation, antennas, electrical, digital or operating. By the second or third pass you'll see the same buckets recurring, and that tells you where to spend the next week. A few topics tend to need a bit more thought than the pool wording suggests: Propagation. Learn the cause and effect, not isolated facts. The D layer absorbs lower HF frequencies during the day and fades after sunset, which is why 80 and 40 meters open up at night. The MUF is the highest frequency that will be refracted back for a given path, so a band can be dead one hour and open the next. Know what the solar flux index and the K and A indices tell you, and what the gray line is. Sporadic E and NVIS also show up. Antennas. Remember the half-wave dipole length rule of thumb (about 468 divided by the frequency in MHz gives feet) and what changes with a trap, a loading coil or an off-center feed. Know why SWR matters and why feed line loss changes what you actually see at the transmitter. Know what a balun does compared with a transformer-style unun. Digital modes. The exam cares about what the mode is and how you operate it, such as FT8's timed transmit periods and the need for accurate computer time, and the difference between a keyboard mode like PSK31 and a connected mode used with Winlink. It also asks where data segments sit on the band. You don't need to be a power user to answer these. On vanity calls: upgrading doesn't require a new call sign. Your existing call stays as it is, and a vanity request is optional and handled separately by the FCC. The exam may ask about call sign groups and the sequential system, so skim that section, but it isn't a reason to delay your upgrade. One practical tip: look up your local VE team's session format ahead of time. Know what ID and paperwork they want, what fee they charge, and whether you'll need a CSCE or just a new license listing afterward.
-
Planning a first POTA rove: UTC rollover, two-fers, 10 QSOs per park, and logging without headaches
The UTC rollover is the one that catches people. If you'll be near 0000Z, a simple fix is to put a UTC clock on your phone's home screen and plan the park order so the one most likely to run long isn't the one straddling midnight UTC. If you do end up straddling, the QSOs on each side of the line need to be counted separately, so don't assume they'll be added together. On the two-fer, make sure your logging program is writing the references the way the POTA upload expects. If you log to a single reference by habit, you'll only get credit at one park and have to sort it out later. Do a few test entries and look at the exported ADIF before you leave home. Also remember that the 10 contacts have to be valid for each reference, so the two-fer doubles the benefit but doesn't reduce the work. For roves, I'd keep one log per park, named with the reference and the UTC date, and I'd upload them as soon as you have signal. That way a corrupted file or a missed park shows up while you're still on the road and can still fix it.
-
Run vs. S&P, multipliers and SO2R: how do you decide when to leave a good run frequency?
I'd add the station and body limits, because they decide how well any strategy gets carried out over a full weekend. For antennas, the usual advice still holds: a few well-placed, higher antennas beat many compromises. A single Yagi on a good tower can run a lot of stations, but if you can only point one direction at a time you lose callers from the other side. Stacks or switchable pattern options let you cover more of the opening without rotating constantly. On 160 and 80, receive performance often matters more than transmit. A good receive antenna (Beverage, loop, or other low-noise option, depending on your space) can change how many weak callers you hear on your run frequency. For fatigue, plan rest ahead of time instead of deciding at 3 a.m. In a 48-hour contest, the low-rate hours are usually the cheapest time to sleep, because you give up fewer QSOs and fewer multipliers than you would at a peak. If your category has an off-time requirement, build it into the schedule so you don't have to improvise. Keep water and simple food within reach, and take short breaks away from the audio. Errors rise as the contest goes on, with more busted calls, wrong exchanges and missed dupes, so a short rest that prevents a streak of errors can pay for itself. On the original question about leaving a run, I'd suggest writing two or three simple triggers before the start, such as 'rate has been below X for 15 minutes and there are unworked multipliers on the bandmap' or 'the band is about to change.' That doesn't make the decision for you, but it stops you from freezing up when you're tired and the rate has been slowly declining.
-
Getting the most out of 5 watts: rigs, antennas and power for portable QRP
Antenna choice is where most QRP setups succeed or fail. A KX2 into a poorly sited random wire can underperform a simpler rig on a good resonant dipole. If weight and setup time matter, an EFHW with a decent coax run to a tuner-less rig is tough to beat. If you can carry a few extra ounces, a center-fed dipole on a light mast or in a tree tends to be less fussy about the ground and feedline. One tip is to check SWR at the radio each time you change location. A ratio that looked fine at home can drift when the wire is near a tree trunk or a fence. On power, one caution about LiFePO4: the voltage is flatter than lead-acid, so a simple voltmeter does not tell you much about remaining capacity until the pack drops off. A small coulomb counter or a pack with a built-in indicator helps. Also check the radio's low-voltage cutoff and transmit behaviour before you rely on a pack in the field.
-
Sequential vs. vanity callsigns: how the groups work, what to verify in ULS, and who can hold what
Good summary. A few points on picking a vanity list. Build it in order of preference and don't skip checking each call in ULS as you go. A call that looks open may be in its holding period, or someone may have a pending application on it. Both can quietly lock you out of the first few choices. Also confirm your eligibility by group before you spend time on a call. A General has no access to Group A or B calls, so a short Extra-only call in your list will simply be passed over. Longer lists give the system more to work with, and they cost nothing extra on the application. The family-member and former-holder provisions are the ones people most often get wrong. They are narrow, and you need to be able to show the relationship. Read the rule text in Part 97 before assuming a late relative's call is yours to take.
-
Why do my digital-mode signals decode on some stations but not others? Checking audio, timing, CAT and mode choice
My order of checks would be time, then audio, then the radio. If the clock is off, nothing else matters. In WSJT-X, the DT column gives away a bad clock quickly. If everyone is around +0.5 and your own transmissions look odd to others, sync first. On audio, I would add that the level is not the same thing as the signal quality. A transmit audio level that is acceptable to the sound card meter can still drive the rig into ALC if the radio's data input gain is high. The ALC reading should show little or no deflection, and if the rig has a compression or processing setting, it should be off for digital modes. Also check the rig is in a data or USB-D mode and that the transmit bandwidth is wide enough but not wider than needed. Some rigs have narrow filters by default that clip the upper audio region. One further tip for new operators: keep the audio frequency of your transmission away from the edges of the passband. 1000 to 2000 Hz is a safe range for most radios, though a given rig may be flatter or less flat than that.
-
Confirming contacts in 2024-style workflow: LoTW first, then bureau, direct, and Club Log OQRS for the rest?
I'd treat bureau and direct as two separate queues. If a station is only a casual contact, let it ride via the bureau and don't pay for postage. If it's a rare entity or a short operation you may not get another chance at, a direct request via OQRS or a mailed card with SASE makes sense. Always check the QSL route before you send anything. Many DXpeditions publish a manager, an OQRS link, and sometimes a LoTW upload promise, and the fastest path may be just to wait for the LoTW upload rather than mail a card. For direct requests, keep the envelope plain and the instructions short. Include a properly filled card, return envelope, and the postage the station asked for, with no extra notes. If the station says it uses OQRS only, follow that. Mailing a card to a manager who only accepts online requests usually just slows things down. And log the date you sent each request so you know when to follow up instead of guessing.
-
Dead rig, no TX, no RX, or protection faults: what order do you check things in?
Agree on most of it, but I'd push back a little on capacitors. Blanket recapping can introduce errors: wrong polarity, wrong ESR characteristics in a regulator or switching circuit, lifted pads. Targeted replacement is safer. If a rail looks noisy, put the scope on it with AC coupling and a short ground spring, not a long ground clip. Ripple at the supply frequency or at the switching frequency tells you whether the culprit is a filter capacitor, the regulator or something loading the rail. The scope is also the best tool for the "no receive" case if you can't get a signal through. Check the local oscillator and reference clock first, then follow a signal injected from a generator through the mixer, IF filter and demodulator, stage by stage, until it disappears. An RF probe on a DMM is a cheaper substitute for tracing RF levels, but it won't show you oscillation or distortion. Last thing on alignment: only do it once the rig is otherwise healthy, and note the starting position of each trimmer or slug before touching it. If an adjustment doesn't help, you can go back. Many rigs are misaligned by well-meaning tweaking while the real fault was a dirty switch or a bad capacitor.
-
Building solid CW copy and sending: Farnsworth, paddles, filters and when to trust a decoder
One practical point on filters: set your sidetone pitch and your receive pitch to match, and pick a pitch you can listen to for hours. Many operators land somewhere in the 500-700 Hz range, though it is personal. Then you can tune a signal to the pitch and the filter works the way it should. A very narrow filter on a signal that is off-center just makes it sound weak and ringy. On decoders, I'd treat them as a second opinion rather than a replacement for your ears. A decoder is most trustworthy for a call sign it has seen repeatedly, and least trustworthy on a weak signal with QSB, where it can output confident-looking garbage. In contests, a skimmer-fed spot list can help you find stations, but you still have to confirm the exchange by ear. Prosigns are a good example of where decoders fail: they often print them as odd letter pairs or stray characters, so it pays to learn what AR, SK, and BT sound like as single units.
-
Gain structure, overload and HF options on budget SDRs: RTL-SDR vs SDRplay vs Airspy vs HackRF, and what the software changes
For antennas, I'd say match the antenna to the job before worrying about the SDR model. A simple dipole kit cut for the band you care about will beat a random whip in most VHF/UHF tasks. For wideband scanning, a discone is convenient but is a compromise on every band. For HF, an active loop or small magnetic loop can help when the local noise is high because the pattern and the placement matter more than raw signal strength. A long wire with a proper 9:1 unun is often sensitive, but it can pick up more household noise unless you place it well and add a choke. Where an LNA goes matters too. If you need one, it normally belongs at the antenna end, ahead of the long coax run. But with a strong local signal environment a low-noise preamp makes overload worse, not better. If the dongle has a bias tee, make sure you know which device is receiving the DC before you turn it on. On panadapters, the SDR can be fed from the radio's IF or a tap off the antenna line, and this is where a bandscope shines. You see the activity around your operating frequency while the rig does the demodulation. Be careful about the RF split, though. A bad splitter or an unprotected input can damage the SDR, especially if you transmit. Use a proper attenuated tap, and don't connect an SDR directly to a transmitting path unless the hardware is designed for it. If I had to pick one improvement for a messy waterfall, I'd go with antenna placement and noise hunting first, then filtering, then a better receiver. A better ADC doesn't remove noise that is coming in through the antenna.
-
Getting started with LEO amateur satellites: Doppler handling, tracking software, arrow antennas, and when to move to linear birds
If the goal is working stations and not building a station, I'd start with the handheld arrow antenna and an FM bird. The reason is that it teaches pass geometry: where the satellite rises, how its AOS and LOS times relate to elevation, and why a 10-minute window is really about 4 or 5 usable minutes at low elevation. A full tracked system hides some of that, and if something goes wrong you have more variables to separate: the rotator, the software, the CAT interface, the TLE age, the clock. That said, the arrow route has one painful limit: manual Doppler correction plus pointing plus logging on a single pass is a lot of juggling. If you want to move to RS-44 or other linear birds later, I'd spend the early FM time practicing in Gpredict or SatPC32 without a rig connected. Watch the frequency display, hand-tune against it, and then add CAT control. Once you understand what the software is doing, it's much easier to diagnose when it stops doing it. One more pitfall for new operators: don't call CQ on an FM satellite as if it were a local repeater. Listen first, give your call and grid briefly, and don't hold the channel. The pass is short, and there may be others waiting.
-
Studying for the Amateur Extra (Element 4): how do you split time between theory, the Smith chart, and Part 97?
On the Smith chart, you don't need to be an expert, but a few facts cover most questions: The center of the chart is the normalized impedance 1 + j0, meaning the load equals the line's characteristic impedance. That's a perfect match, SWR 1:1. A circle centered on the chart center represents constant SWR, so the farther out the circle, the higher the SWR. Moving along a lossless line traces that circle. Going toward the generator is clockwise, and one full trip around the chart is a half wavelength. Resistance circles, reactance arcs, and the upper half (inductive) versus lower half (capacitive) are the main reading skills. Also remember that a quarter-wave section transforms impedance as Z = Z0² / ZL, and a half-wave line repeats the load impedance. Once you've worked a few examples by hand, the question-pool versions are usually just identifying a point or a direction. For Part 97, I'd treat it as a separate category and do spaced repetition, a few minutes a day, rather than cramming it with the theory. Group the rules by theme: station control types, definitions, special operations such as space stations and auxiliary stations, and volunteer examiner rules. Keep in mind that the rules change, so use a current question pool and check the actual rule text for anything you're unsure about. As for what you get: the Extra gives full privileges on all amateur bands and modes. In practice that means the exclusive segments at the lower ends of 80, 40, 20, and 15 meters, plus wider phone segments than General has on several HF bands. It also qualifies you for the shortest vanity call signs (the Group A 1x2 and 2x1 formats) and lets you serve on Extra-level exam teams. Whether that's worth it depends on how much you operate HF and how much you enjoy the theory. Check the current band plan before you set expectations, since the details are in Part 97.
-
On-air etiquette basics: CQ calls, breaking in, nets and handling interference
I'd add that "listen first" applies to the whole conversation as well as the frequency. If you spend a few minutes just monitoring a net or a busy repeater, you pick up how it runs: whether check-ins are by suffix, whether there's a long preamble, whether people say their name or just their call. Every group has its own habits, and matching them is usually the easiest way to fit in. For CQ calls, one useful test is whether a stranger tuning past could write down your callsign after one pass. If it takes three repeats of CQ before they hear it, the call is too long. A couple of CQs, your callsign slowly and clearly, then listen properly. Standard phonetics are better than clever ones, especially in noisy conditions or when your signal is marginal.
-
December 2026 Meeting
until
NTARS holds its December 2026 meeting on December 14 from 7:00 pm to 8:00 pm, in the Meetings category. It takes place at Parker County ESD 1, Station 34 in Aledo, TX.Location: Parker County ESD 1, Station 34, 991 Bailey Ranch Rd, Aledo, TX 76008, United States Organizer: NTARS Source: Event information -
VHF/UHF antenna choices: gain vs. pattern, J-poles and collinears, mag mounts vs. NMO, and why coax and connectors matter
One point about J-poles and slim jims that gets overlooked: they are very sensitive to how you mount them. If the J-pole is attached to a metal mast right along the radiator, the mast becomes part of the antenna and the pattern and tuning shift. A common approach is to use a non-conductive standoff or mount the antenna above the mast top, with the feedline coming away at a right angle where practical. A choke at the feedpoint is cheap insurance. For mags and NMOs, I'd add that if you're measuring a mobile SWR that seems fine in the driveway but changes when you drive, check the ground connection and the cable first. With an NMO, a paint-coated or corroded contact between base and body can cause intermittent problems. With a mag mount, a roof rack or a luggage load nearby changes the ground plane. On the satellite side, if someone is starting out, a handheld yagi and a dual-band HT is a common low-cost way to learn the pass geometry before investing in tracking hardware, though you'll need to deal with Doppler and polarization fading by hand.
-
Winlink over radio: a sensible order for setting up Express, gateways, modes and P2P
On ARDOP versus VARA HF: a practical decision rule is to pick the mode the gateways near you actually offer, then test it, rather than choosing on theory. VARA HF generally gives higher throughput when the path supports it, but a mode that connects reliably at low speed beats one that keeps failing. ARDOP is worth keeping configured as a fallback because it is free and has no registration speed limit to think about. Pactor only matters if you already have the modem or your area relies on Pactor gateways. On HF, the most useful habit is to try more than one gateway rather than retrying the same one. Check the channel list for several candidates at different distances, since a closer gateway is not always the best on a given band at a given hour. Listen first, and if the channel is busy or you can hear another session, wait. Winlink Express reports the connect attempts in the session log, so read what it says. A failure to get a link is different from a link that drops during transfer, and the fix is different too: the first suggests frequency, path or power, the second suggests noise, levels or message size. For forms and ICS-213, the thing that bites people is the recipient end. Before an exercise, send a test form to the person who will receive it and confirm they can read it in their client. If the served agency only uses webmail, plain text may be safer than a form, so agree on that in advance. And keep attachments minimal, especially over HF. A short ICS-213 is a few kilobytes, while a photo can take far longer than the operating window allows.
-
Rate vs. multipliers: how do you decide when to stop running and go hunting, especially with SO2R?
On fatigue: it affects the logic of your choices, not just your typing. Long contests reward people who stay accurate in the middle of the night, when rate is low and the temptation is to chase anything that moves. A few practical habits help: Decide in advance when you'll take rest, based on band conditions and your category rules. Planned breaks during a dead period cost far less than an unplanned break during a good opening.Keep water and food within reach so a break doesn't turn into a long trip away from the operating position.Use receive audio to reduce strain. A good headset, sensible AGC and filtering, and avoiding listening at high volume for hours all make a difference.Keep antenna and band-change procedures simple. If a stack switch or rotator move needs three steps, make a checklist so you don't have to think while tired.On antennas, a stack or switchable array gives you elevation choices when conditions vary between local and long-haul paths, and low-band receive antennas (Beverages or smaller receive loops) often turn "can't hear them" into workable multipliers. They only help if you can switch them quickly during operating. As for categories, check whether a lower power class, an assisted category or a single-band entry suits your station. The best choice is often the one that matches your antennas and your stamina, not the one with the highest theoretical score.
-
Studying for the Technician exam (Element 2): how should I use the question pool and practice tests?
Use the pool as a map of what to learn, not a list to memorize. Answer positions are shuffled on the real exam, so remembering "the answer is C" won't help. Remember the reason the right answer is right. Take a practice test, then for every miss, read the explanation in your study guide and write down the underlying idea in one sentence. Retake the same topic a day or two later. The pool is organized into subelements, and the exam draws a set number of questions from each. Most study guides and practice sites follow that structure, so you can see which areas carry the most weight and shore up your weakest group. Always confirm that your guide or practice site matches the pool currently in effect. Pools are revised on a multi-year cycle, and the volunteer examiner coordinators publish the effective dates. An outdated book can contain questions that no longer appear and miss new ones. For the math, the exam stays simple. You mainly need Ohm's law (E = I × R), the power formula (P = I × E), and how to combine series and parallel resistances. For example, 12 volts across a 4 ohm resistor gives 3 amps, and 3 amps at 12 volts is 36 watts. You also need to convert between frequency and wavelength. Dividing 300 by the frequency in MHz gives roughly the wavelength in meters, so 146 MHz works out to a little over 2 meters. That's where the band names come from. Practice rearranging the formulas until it's automatic, because the exam questions are often worded slightly differently from the pool. On privileges, a Technician has all amateur privileges above 30 MHz, plus limited HF access. Learn the band names and the general idea, then check the band plan details against the current pool and FCC rules. Don't trust a forum post, including this one, for exact frequency edges.
-
Building a lightweight activation kit: EFHW or linked dipole, and how to power it
One framework that helps is to decide your limiting factor first. For SOTA, it's usually weight and weather exposure, so a QRP rig, a roughly 10 m pole or a tree, and an EFHW are a common combination. For POTA from a car or picnic table, weight matters much less, so you can bring a bigger battery, a 100 W radio, and a more comfortable antenna setup. On the EFHW versus linked dipole question, a lot comes down to how many bands you actually plan to use. If you mostly run 40 and 20 m, a linked dipole is perfectly good and straightforward. If you like hopping around, an EFHW saves handling time. Either way, bring a spare length of coax and a few cable ties, because those are the failure points that tend to end an activation more than the radio does. For batteries, size the pack from a rough calculation: average current times operating hours, with a margin. Transmit time is only part of a typical session, and receive current adds up over several hours. With solar, make sure the charge controller is set for LiFePO4 and don't rely on it to keep the pack full on a cloudy day. Treat solar as a bonus, not a plan.
-
Getting started with radio nets and special event stations: check-in etiquette, net types and chasing certificates
One tip for anyone thinking of running net control: write your script before you go on the air. It can be a few lines on a card. Include the net's opening statement, the purpose of the net, the frequency or repeater information, the call for check-ins, the call for traffic, the call for late check-ins and the closing statement. A script keeps you from rambling and helps newer operators follow the structure. Keep a simple log with call sign, name, location and any traffic or announcements. A list of calls in order is much better than relying on memory. If two stations come back at once, don't ask for both to repeat. Pick one, acknowledge them, and tell the other to stand by. Handling the order of calls is mostly what net control is about. Finally, always follow your net's own rules. Directed nets, open nets and informal ragchew nets work differently, and what is polite in one can be disruptive in another.
-
Getting started with SOTA: summit references, activator vs. chaser points, and a sensible first kit
The HF versus VHF decision mostly comes down to terrain and how much weight you want to carry. VHF FM is quick to set up and fine when you know there is local chaser activity. HF gives you reach, and CW in particular is efficient on QRP power for a small battery. A common lightweight HF approach is a compact transceiver, a linked or multiband end-fed wire, and a short pole to hold the center or far end up. The usual bands are 40, 30 and 20 metres, and which is best depends on time of day and distance to your chasers. On logging, one habit that saves time is writing down the chaser's callsign and any summit reference at the moment of contact, not trying to reconstruct it afterward. Then, back home, put the whole activation into a CSV that matches the SOTA database upload format and check it before submitting. Typos in a call or summit reference are the usual reason a contact doesn't match. And for chasers: log the activator's reference with every contact, because points and your Shack Sloth progress depend on getting that right.
-
Planning a contest year: which events to start with, what the exchanges look like, and how to avoid log-submission headaches
One thing to add on log submission: do a dry run. Before the contest, export a short test log from your software and check the Cabrillo header for your category, operator class, power, band selection, and the email or upload requirements. Then read the sponsor's rules for the deadline and for whether the log must be sent to a specific robot, and whether paper or alternative formats are accepted. Also check the callsign handling. Portable or /P calls, DX prefixes and multi-operator setups can cause mismatches between the header and the QSO lines. If a sponsor offers a log checker or a reply confirming receipt, use it, and keep the confirmation. It's much easier to fix a header error the same day than to chase it after the deadline.