Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.5
Wind 385.0 km/s
Aurora 1
Updated 13:00 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Admin_Terry

Administrators
  • Joined

  • Last visited

Everything posted by Admin_Terry

  1. For combined POTA and WWFF from one site, the main thing is keeping the two logs straight. Contacts made for both programs are the same QSOs, but each program wants its own reference attached to your log, and each has its own upload process. Treat each program separately. Confirm the POTA park reference and the WWFF reference, make sure the location you are actually operating from falls inside both boundaries, then record both references for every QSO. Depending on your logging software, that may be two separate fields or a custom export. Test the export with a few practice entries before you rely on it in the field, and open the ADIF in a text editor to check that the right tags are present. When you spot, say that you are on both. On the air, "POTA and WWFF" with both references in the spot comment helps hunters from either program find you. Park-to-park contacts are also available on both sides, so it is worth answering a stray activator when you hear one, even if the other station is only on one program. Also expect the contact count to be driven by WWFF. If you aim for 44 you will clear POTA's 10 along the way, but not the other way around. Some activators set their schedule around the higher number and treat the POTA threshold as a bonus. One more caution: the two programs may define boundaries differently, and a spot just outside one boundary can be inside the other. If you are close to an edge, check a map of both before you set up.
  2. On batteries, the main point is to match the pack's voltage range to the rig's specification. A 4S LiFePO4 pack that reads 13.2-13.6 V resting is typically fine for gear designed for a nominal 12-13.8 V supply, but charging voltage can be higher, so check the input rating before connecting. A pack with a built-in BMS is a good idea because it protects against over-discharge, over-current and cell imbalance. Put an inline fuse close to the battery, use polarity-keyed connectors such as Anderson Powerpoles, and mark both ends of the lead. Reverse polarity does more damage than low power ever will. Size the capacity from the current the rig actually draws. Receive current dominates a long session, and transmit time is usually short, especially with CW. Look at the current figures in your rig's manual, estimate the hours you want to operate, and add margin for cold weather, which reduces available capacity. Don't forget the weight of the pack, charger and cables; a smaller battery plus an efficient, quiet rig may suit a summit better than a large pack. On QRP-ARCI: it is a long-standing club for low-power operators, and it organizes contests, awards and a members' publication. Whether it's worth joining depends on whether you'd use those activities. Even if you don't join, the contest rules are a good source of ideas for operating practice, such as how stations exchange signal reports and power levels. Always check the current event rules on the organization's website before entering. One more practical point: write down your station's setup time. A rig that takes five minutes to deploy gets used more often than one that needs twenty, so test the whole kit, antenna included, in your yard before taking it out.
  3. One thing I would add is the difference between a tactical call and an FCC call sign. During an activation, assigning tactical identifiers such as the location or function, like "Shelter One" or "EOC Net," helps agency staff keep track of who is where, and operators can swap out without confusing the log. Remember that you still need to identify with your FCC call sign as required by the rules, typically at the intervals Part 97 specifies. It is worth drilling both until it is automatic. Also check your frequency plan for a gap between what you assume will work and what will. Repeaters can lose power, so know your simplex fallbacks, and know when you would use HF or digital modes for longer distances. Whatever your county plan lists as primary and alternate, practice the move to the alternate on a drill day, not for the first time during an incident. For a served agency, the biggest value is often a reliable path that still works when normal communications are strained.
  4. Adding the chaser side, because it is a good way to learn the procedures without the hiking. Watch the spots, work out whether you can hear the activator, and keep your exchange short: callsign, report, done. The activator is working a pileup, and every second matters, especially in cold or bad weather. If you are unsure whether they heard you, repeat your call once and listen before sending more. I would also keep your own log tidy from day one: UTC time, band, mode, the activator's callsign and the summit reference exactly as spotted. That makes your chaser upload painless and makes it easier to catch mistakes. And remember that a spot is not a guarantee. Conditions change, and the activator may QSY or pack up. Check the frequency before you transmit.
  5. On the clock, one thing worth checking is how often your OS actually corrects itself. A PC that was fine yesterday can be several tenths of a second off after a long uptime or after waking from sleep. If WSJT-X shows DT drifting for everyone, don't chase the radio first. Force a resync, or run something that polls an NTP server frequently. If you have no internet at a portable site, a GPS puck feeding the PC's time service does the job. For sound cards: if you use a USB audio codec built into the radio, set both sample rates to the same value (48000 Hz is common) and disable Windows "enhancements" and system sounds on that device. Notification sounds going out on transmit are a classic embarrassment. Also keep the Windows output slider fixed and adjust only the WSJT-X Pwr control, so you know your reference point. On the interface: a separate isolated interface with a transformer and a separate USB ground can cure hum or RF problems. A built-in USB codec avoids that wiring but ties your audio to the radio's own ground and cable routing, so you still need chokes. Neither approach is better in principle; test with a dummy load first and watch for errors or odd ALC behaviour.
  6. On the access question, a VPN is the cleanest answer for most setups. With WireGuard or similar, the only thing exposed is the VPN endpoint, and the rig, Pi and PC just see a private address. That also solves the rigctld problem, since the unauthenticated control port is only reachable from inside the tunnel. The tradeoff is that mobile and CGNAT connections can be awkward, so a mesh VPN or a small VPS relay may be needed at the remote end. One thing that gets overlooked is audio. Vendor clients like RS-BA1 and SmartSDR handle compression and buffering for you. If you build your own chain with a Pi and a separate audio stream, you have to tune buffer size yourself. Too small and you get dropouts on a jittery link, too large and you get a delay that makes it feel like operating through a satellite. It's worth testing in both directions over the actual path you'll use, not just on a LAN.
  7. Here's how the pieces fit together. VEs are licensed amateurs accredited through a Volunteer Examiner Coordinator (VEC) such as ARRL VEC, Laurel VEC or W5YI VEC. They run the exam session, check your ID, grade the test and file your paperwork. The FCC doesn't give the exams itself. It relies on this volunteer system. To find a session, start with the ARRL's exam session search, which lists sessions from many teams, not only ARRL-affiliated ones. HamStudy.org also has a session finder, and local club websites often post their own schedules. Some teams run remote (online) sessions with a video proctor. Read each listing carefully. Some sessions are walk-in, some want you to pre-register by email or web form, and some cap attendance. If the listing gives a contact, send a short email and ask what to bring. Fees are set by the VE team or its VEC, so they vary. Look at the session announcement for the exact amount and the accepted payment method (cash, check or an online payment), and don't rely on a figure you saw somewhere else. The fee covers the team's costs, not an FCC charge. I'd check the FCC's current fee schedule before assuming anything about application fees, since that has changed over the years. An FRN (FCC Registration Number) is a free ID you get by registering in the FCC's CORES system. Get it before exam day, because the VE team will want it on your paperwork. Be careful if a site tries to charge you for one. Registering is free. For the session itself, bring a photo ID, your FRN, a pen or pencil, and any payment the listing requires. A simple calculator is usually fine, but check the team's rules, and the Technician exam rarely needs more than basic arithmetic.
  8. On the receiving side, I would stress that narrower is not always better. A 1.8 kHz filter can make a signal easier to copy in QRM, but if the other station has a naturally wide or bass-heavy voice, you may lose the part of the speech that carries the consonants. On a weak but clean band, try 2.4 kHz first and use passband shift to move away from an interferer before you narrow the filter. The same goes for noise reduction. Light settings can ease listening fatigue, but strong NR can remove the speech information that you need for a weak station. The notch filter and noise blanker are more targeted tools if the problem is a carrier or impulse noise. For DX, it also helps to check where the other operator is listening before you call. If you are using split, make sure the RIT or the second VFO really is where you think it is and that the TX bandwidth is not so wide that it overlaps the neighbors. A quick check of your transmit frequency on an SDR or second receiver before you call can avoid a lot of wasted calls.
  9. On the low bands, I would put receive antennas first, ahead of timing. A station that can hear the DX is a station that can follow his pattern, find a gap and identify when he is calling for a particular call area. On 160 and 80, you may have a very weak signal one moment and a good one a few minutes later as the grey line moves, so there are only short windows. Being ready at the right moment matters more than calling the whole time. It also helps to separate the DX's transmit and receive information in your head. Often the DX is on one frequency, and the callers are spread over a range that can be several kilohertz wide. Using a second receiver or the sub-receiver for the transmit frequency lets you hear both at once, so you know the DX frequency and where the pileup is. As for Club Log: I would treat it as an aid for planning, not as a promise. Check the expedition's own page for log search rules and for any OQRS details, because they differ from one operation to another. If you want to confirm that a QSO was logged, wait a reasonable time before you try again, and do not assume a missing entry means a failed contact until the logs are fully uploaded.
  10. One thing I'd add to the testing routine: do a deployment drill where you set up from the bag, with no home-station shortcuts. Bring the bag outside, set up the antenna, connect power, and make a few contacts on simplex or a distant repeater. Time yourself. Then write down every item you had to go back inside for. That list becomes your fix list. A kit that looks complete on a table can still be missing a barrel connector, a mounting clamp, or the one cable you always grab from the shack. On the battery side, label each pack with the date it was last charged and its chemistry. Lithium packs generally shouldn't sit fully charged or fully empty for long periods, so follow the manufacturer's storage guidance. Also, a battery bank that charges a phone is not necessarily able to run a radio, since many USB banks can't deliver the current or voltage a 12 V transceiver wants. Check the output specs before you count on it.
  11. Adding to the above, here are the areas that tend to need more attention than people expect, and a few ways to approach them. Privileges and license terms are pure recall, so use flashcards or spaced repetition. Technicians get all amateur privileges on frequencies above 30 MHz, plus limited HF privileges. Know which HF bands and modes you're allowed on, including the 10 meter phone segment, and know the power limits that apply there. A license is valid for ten years, and after it expires there is a grace period for renewal. Know the difference between the renewal window and the grace period. Station identification is also commonly tested: give your call sign at least every 10 minutes during a communication and at its end. Repeater questions are easier if you picture the setup. A repeater listens on one frequency and transmits on another, and your radio shifts its transmit frequency by the offset. On 2 meters the standard offset is 600 kHz, and on 70 cm it's 5 MHz. The direction (plus or minus) depends on where in the band the repeater sits. Access is often controlled with a CTCSS (sub-audible) tone that you have to transmit so the repeater opens up for you. Also learn the operating-practice items: listen before transmitting, say your call sign clearly, and keep transmissions short. Procedures like these appear in many questions. RF exposure and safety are usually less intimidating once you see the pattern. Exposure limits are defined as maximum permissible exposure (MPE), and what you have to evaluate depends on factors such as frequency, power, antenna location, and duty cycle. Safety questions cover things like keeping antennas away from power lines, grounding, and lightning protection. Don't treat them as filler, since they're worth the same as any other question. For practice tests, take full 35-question timed runs near the end of your prep so you get used to the format. Aim for scores comfortably above 26 correct rather than barely scraping by, since exam-day nerves and rewording will cost you a few. Then review every miss and group them by subelement. If you keep missing the same group, go back to the study guide for that topic instead of just retaking tests. And before exam day, confirm with the VE team what ID and paperwork to bring, and whether they accept pre-registration or walk-ins.
  12. I'd add one thing to the after-action section: separate people problems from equipment problems, because they get fixed differently. A dead battery is a checklist item. An operator who didn't know when to stand down is a training and scheduling item. Mixing them in one list makes it hard to assign owners. For a grid-failure scenario, a useful constraint is to run part of the exercise as if there's no internet. That means no looking up frequencies, no emailing forms, no checking a shared document for the roster. Print the net script, the contact list, the frequency plan, and blank message forms, and keep them in a go-kit. You'll quickly find which things only exist on someone's phone. Fatigue is also worth simulating even in a short exercise. You can't really recreate a multi-day hurricane response in an afternoon, but you can make people practice a clean shift change: what the incoming operator needs to know, which messages are still open, and what's pending a reply. A written handoff log is a small habit that makes long events much more manageable.
  13. On the ARES versus RACES question, the practical advice is to ask your local emergency management office what they use and what they require. Some counties lean on RACES for official activations, others work mostly with ARES groups under a memorandum of understanding, and many have both. Registration, ID badges, background checks and training requirements can differ a lot from one jurisdiction to the next, so don't assume your neighbor county works the same way. For go-bags, I'd add a second category: the things that keep you operating for a full shift rather than an hour. Think of a battery or power plan with a way to charge it, a headset or earpiece so you can work in a noisy EOC, a printed copy of your frequency plan and contact list (phones and printers may not be available), a notebook for logging, and any agency credentials. Keep a short checklist in the bag and test the radio gear before you need it. Check that programmed channels match the current plan, because stale memories are a common problem. SKYWARN and CERT are worth doing if your area uses them, but they aren't substitutes for each other. SKYWARN teaches you what to observe and report for weather, while CERT teaches you what to do on scene. Neither replaces being a reliable operator who shows up to the drills.
  14. A point on mobile 5/8 versus quarter-wave: the 5/8 usually wins only when the ground plane is large and the antenna is centered. On a trunk lip or fender mount, the pattern is lopsided toward the metal and the nominal gain is partly theoretical. A quarter-wave on the roof is often competitive on real roads, especially in hills where the low-angle advantage matters less than a clean, well-grounded feed. On the J-pole point, if the SWR changes when you touch the coax or move the cable, that points to common-mode current. Adding a choke a quarter wave or so below the feedpoint, or routing the coax away at a right angle, can stabilize it. And on the connector question, if a run is outdoors at UHF, using N connectors from the start is cheaper than chasing intermittent water-related loss later.
  15. I'll cover the topics the first reply didn't, since propagation, antennas and digital modes are where Technicians tend to feel least sure of themselves. Propagation: learn what each layer and index does rather than memorizing answers. The D layer absorbs lower HF during the day, which is why 80 and 40 m are better at night for longer distances. Higher solar flux generally supports higher MUF, so 15 m and 10 m open more reliably when the solar flux index is high. Know what MUF and critical frequency mean, how the gray line enhances propagation along the day/night boundary, and what the K-index and A-index say about geomagnetic disturbance. A high K-index usually means degraded HF paths, particularly at high latitudes. Antennas: a half-wave dipole is about 468 divided by the frequency in MHz, giving feet. At 7.1 MHz that's roughly 66 feet overall. A quarter-wave vertical needs a good radial or ground system to work well. Know the difference between coax, ladder line and open-wire feeds, why a balun or choke matters at a dipole feedpoint, and what SWR does and doesn't tell you. SWR measures match, not antenna efficiency or radiation. Digital modes: expect questions on FT8-style weak-signal modes (timed transmit cycles, so accurate computer time matters), PSK31, RTTY, and the general idea of sound-card modes where the radio sits in USB and the software does the work. Learn the terms: baud, bandwidth, ARQ, FEC. These are cheap points once you've seen them a couple of times. Vanity call signs are only lightly tested, so don't spend much time there. They come up again once you hold the license. After you upgrade you can apply for a vanity call if you want one, but your existing call sign stays valid as it is, and there's no reason to rush. Check the FCC's current rules on what call sign groups you qualify for before you apply. One caution applies to everything above: for exact frequencies, power limits and any recent rule changes, check the current FCC Part 97 text or a current study guide. A forum post (including this one) can be out of date.
  16. Most emergency communications failures aren't dramatic. A battery turns out to be half-charged. A coax jumper is still in the other bag. Nobody remembers which Winlink gateway worked last time. Net control starts talking and never stops. The good news is that nearly all of these problems can be found and fixed before a storm, a wildfire evacuation, or a long outage. This post walks through a practical way to think about storm-related radio use: power, go-kits, weather monitoring, nets, and digital messaging. It's general guidance, so adapt it to your local served-agency requirements and your group's plans. Start with the job, not the gearBefore buying anything, answer one question: what will you be asked to do? The answer shapes everything else. Skywarn spotting: Skywarn is the National Weather Service's trained-spotter program. Spotters report what they actually observe, such as hail size, wind damage, flooding, or rotation, using the reporting criteria taught in local NWS training. Radio is often the link between the spotter and a local net or NWS office, but the training matters more than the radio.ARES support: ARES is organized through the ARRL and typically supports served agencies such as emergency management offices, hospitals, shelters, and Red Cross operations.RACES operation: RACES is a government-authorized, civil-defense-oriented service, and its operating rules differ from regular amateur operation. Many operators belong to both programs, but you should know which hat you are wearing at any given moment.Personal and family communication: Sometimes the most important goal is simply reaching relatives and getting official information when cell service is degraded.Write your mission down in one or two sentences. If a piece of equipment doesn't serve it, leave it out of the go-kit. Backup power: do the math oncePower planning is mostly arithmetic. Find the current draw of each device, estimate how many hours you'll operate, and convert to watt-hours (Wh). Volts times amp-hours gives you Wh. A typical 100-watt HF transceiver draws far less on receive than on transmit, and your duty cycle matters. Voice and digital modes behave very differently, so check your radio's specifications rather than guessing.VHF/UHF handhelds and mobile radios are much easier to support on small batteries.Add the laptop, tablet, modem or sound-card interface, lighting, and phone charging. These small loads add up.Many operators choose LiFePO4 batteries for their weight, cycle life, and flat voltage curve, though sealed lead-acid still works and is cheaper. Whatever you choose, use a proper battery management system, appropriate fusing near the battery, and wire sized for the current. Keep the kit's charger, cables, and connectors together so you aren't hunting for them in the dark. For solar, size the panel to your daily consumption, not to the panel's label rating. Real-world output is lower than the rated figure because of angle, clouds, heat, and wiring losses. A charge controller suited to your battery chemistry is not optional. Then test the whole system on an ordinary sunny weekend, not for the first time during an outage. Generators can be useful, but they add carbon monoxide risk, fuel storage issues, and electrical noise. Run them outdoors and well away from windows, and never refuel a hot unit. Test your receiver with the generator running, because some inverters and chargers create noise that wipes out weak signals. The go-kit: build it in layersA go-kit that tries to be everything usually becomes too heavy to move. Think in layers instead: Personal layer: water, food, medications, weather-appropriate clothing, headlamp, gloves, and ID. If you're not safe and comfortable, you can't be useful.Radio layer: a handheld or mobile with spare batteries, a programmed memory list, a better antenna than the stock rubber duck, and printed copies of key frequencies.Digital layer: laptop or tablet, interface cable, Winlink software already installed and configured, and offline copies of the forms you expect to use.Power layer: battery, charger, fused distribution, and a way to recharge.Paper layer: logbooks, message forms, pencils, a clipboard, and a map. Pencils work in the rain.Label cables and put a short checklist in the lid. After every drill or use, restock immediately, so the kit is always ready. Weather monitoring that actually helpsKeep more than one source of information. A NOAA Weather Radio receiver with battery backup is a simple, reliable alert tool. Add a smartphone with offline-friendly resources, a local net's frequency, and, if you have one, a home weather station. When the internet is slow or down, a battery-powered receiver may be your only continuing warning source. Remember that Skywarn reports should be factual and specific: what you saw, where, and when. Avoid speculation. Never put yourself in danger to get a report, and follow your local program's safety guidance. Net control: the skill most worth practicingA well-run net feels calm even when the situation isn't. Some habits that help: Use a script. Open with the net's purpose, the type of traffic expected, and how to check in.Keep transmissions short. Net control sets the tone. If you're verbose, everyone else will be too.Prioritize. Emergency or priority traffic goes first. Routine check-ins wait.Log everything. Who checked in, when, from where, and what traffic was passed. A good log is invaluable for later review.Use plain language and tactical identifiers where your plan calls for them, and still observe station identification requirements.Plan relief. Net control gets tired. Name an alternate before you need one.Practice by running low-stakes weekly nets with a rotating cast of net controls. The more people who have done the job once, the more resilient your group becomes. Winlink during outagesWinlink is a radio email system that can move messages with attachments when normal internet or phone service is unavailable. Depending on your setup, it can work over VHF/UHF or HF, with different modes and gateways. It's useful for formal, accountable messages such as status reports, resource requests, and welfare traffic, where a written record matters more than a quick voice exchange. To avoid surprises: Install and configure your software before the event, and send test messages while everything is still working.Learn how to connect through RF gateways, not only over the internet, since the internet link may be exactly what's down.Keep a list of nearby gateways and the bands and modes they use, and expect propagation to change through the day.Practice using templates and forms, so you aren't learning them under pressure.Drills and Simulated Emergency TestsDrills exist to find problems while the stakes are low. The ARRL's Simulated Emergency Test is a common national exercise, and many ARES groups run their own local versions. Treat a drill as a place to try unfamiliar things: operate from a field location on battery power, pass a formal message by voice and by Winlink, or practice a net with a deliberately unreliable repeater. Afterward, hold a short debrief. Ask three questions: What worked? What failed? What will we change before next time? Write down the answers and assign owners. Lessons that aren't recorded tend to be relearned the hard way. Lessons that show up again and againAfter-action reports from hurricanes, wildfires, ice storms, and floods tend to repeat similar themes, even though no two events are alike: Cell and internet service can degrade or become overloaded, so have a non-cellular plan.Repeaters can lose power or links, so know your simplex options.Antennas and feedlines are common weak points, so keep spares.Fuel, charging, and rest are logistics problems, not afterthoughts.Training and relationships with served agencies matter as much as equipment.A simple next stepThis week, pick one item: run a power test on your battery, send a Winlink test message, check your go-kit against a written list, or volunteer to be alternate net control. Small, repeated practice is what turns a pile of radio gear into an actual communications capability.
  17. On TCXO and firmware, the key point is to measure before and after. A frequency counter or a known reference signal tells you whether the upgrade changed anything. A radio that is off by a few hundred hertz on UHF probably does not need a hardware change for FM voice, but for narrow digital work it could matter. And if drift only appears after the radio has been transmitting for a while, heat is a likelier cause than a poor reference, which brings us back to cooling and duty cycle. For firmware, I'd treat anything unofficial as a change that needs its own testing. Read what it changes, save your current configuration, and verify power output, deviation, and any extra features such as scanning or squelch behavior afterward. Be especially careful with batteries and power: flashing on a low pack is a classic way to brick a radio. And for any lithium conversion, fuse it, check the polarity twice, and make sure the charger matches the chemistry. A fan or a nicer speaker will not hurt anything, but a bad battery mod can start a fire. One last practical point: a modified radio should be treated like any other transmitter you are responsible for. If you changed something that could affect the signal, check it on a dummy load and with a second receiver before putting it on the air. Keeping a short log of what you changed, why, and what the measurements were also helps if you have to undo the mod or explain it later.
  18. On the run versus multiplier decision, one practical way to apply the Q/M idea is to set a threshold before the contest. For example, "if a needed multiplier is on the bandmap with a clean skimmer spot and my run rate is below X, I go get it." Deciding ahead of time keeps you from agonizing in the moment. Recalculate it a few times during the event, because Q/M changes as the contest goes on. For SO2R, the first thing to get right is the plumbing, not the strategy. You need reliable transmit inhibit or interlock so both radios can never key at the same time, good band-pass filtering, and enough isolation that your run radio is not blasted by your second radio's transmitter. A stereo headphone arrangement where each radio is in a different ear is common, with a way to focus on one ear or the other. A footswitch for PTT or for switching transmit focus is worth practicing with. Many operators find that most SO2R errors come from sending on the wrong radio, not from hearing problems. In N1MM Logger+, each radio has its own entry state and bandmap. A useful workflow is to keep the run radio in CQ mode and use the second radio's bandmap to look for needed multipliers, with the multiplier display and bandmap color coding showing what you still need. You can also use interleaved modes such as 2BSIQ, where you alternate between radios at the QSO level, but that depends on how fast you can copy and how well you manage both audio streams. Practice in a low-stakes contest before using it in one that matters. On skimmer and packet spotting: a skimmer spot is a starting point, not a verified callsign. Skimmers decode errors, busts and dupes, and spots can be old or from a different mode. Confirm by ear before you call, or at least wait until you hear the station sign. Also check the rules for your category. In most contests, using spotting networks, Reverse Beacon Network or a local skimmer puts you in an assisted category, but rules differ. Check the specific contest before you decide which category to enter.
  19. On the VHF/UHF side, I'd rank the hardware priorities like this: loss ahead of the preamp, then polarisation control, then more gain. Feedline loss matters twice. On transmit, every 0.5 dB lost in coax is power you paid for and never radiated. On receive, loss before the preamp adds directly to system noise. That is why serious setups put the preamp at the antenna through a low-loss relay, and why the sequencing and relay choice get as much attention as the preamp itself. A preamp with a very low noise figure behind a lossy relay is a false economy. On 2 m the sky temperature is high anyway, from several hundred K to well over a thousand K near the galactic centre, so there is a point past which a better preamp barely helps. On 70 cm and up, you notice the difference much more. Polarisation is where 2 m differs most from the other bands. Faraday rotation scales roughly with 1/f², so 432 MHz sees about a ninth of the effect at 144 MHz, and 1296 MHz sees only about 1/80. On 2 m, linear polarisation can rotate through large angles, and the signal fades in and out over minutes as the effective angle sweeps through the cross-polarised null. On top of that there is a purely geometric offset between two stations at different locations, because each sees the Moon from a different angle. That spatial term does not average out the way Faraday does. The usual fixes are the ability to switch between horizontal and vertical, to phase a cross-polarised array, or to physically rotate the antennas. Many serious arrays have it for a reason. Without it, you can be sitting on a perfectly good path and wait for the cycle to come around. With it, you often get a better stretch in the same window. If I were building up gradually, I'd get a good receive chain and polarisation switching working on one array, check echoes with the WSJT-X Echo mode, and only then scale up gain.
  20. Koch and Farnsworth aren't really rivals. They answer different questions, and you can combine them. Farnsworth is about spacing. Characters are sent at a fairly fast speed, say 18 to 20 WPM, but the gaps between characters and words are stretched so the overall speed is much lower. Each character keeps its normal rhythm, and you get time to think between them. The usual mistake is to send everything slowly, which makes each letter sound like a string of separate beeps instead of a single shape. Koch is about what you learn and in what order. You start with just two characters at full character speed. You copy random groups of only those characters until you're getting roughly 90 percent right, then add a third, and so on. Nothing is ever memorized from a chart. You learn the sound of each character as a whole, which is what you want when you're copying on the air. So a sensible plan is Koch for the order of learning, with character speed fixed around 18 to 20 WPM and the gaps stretched at first, then tightened as you improve. Most Koch trainers let you set both numbers separately. On visual charts: a tree or dot-dash table is fine for looking up a character you've forgotten. But if your brain learns A as 'dot dash' and then translates, you will hit a wall at around 10 WPM, because the translation can't keep up. Learn A as 'di-dah', a sound, from the first day. Say it that way too, not 'dot dash'. Short, frequent sessions beat long ones. Fifteen to twenty focused minutes a day is a commonly recommended range. Stop when you're tired, because accuracy drops and you start practicing errors.
  21. I'd flip your order a bit: choose the mode your local community actually uses first, then the radio. If your area runs mostly analog FM repeaters, an FT-65R or similar gives you everything you need for a lot less money. If nobody in your area uses D-STAR, an ID-52A or TH-D75 mostly becomes an expensive FM radio with features you'll rarely use. On the cheap clone question, I'd add that receiver quality matters more than the extra watt. In places with a lot of strong signals nearby, a radio with a wide-open front end can be noisy or get overloaded even when your own transmit is fine. A better antenna helps your transmit and receive, but a better radio helps with the strong-signal problem. If budget is tight, one decent HT plus one spare battery beats two bargain radios. For CHIRP, I'd stress one habit: always save an image of the radio before touching it, and keep a copy of your edited file somewhere other than the computer you programmed it on. Resetting a radio is easy once you have the file and annoying if you don't.
  22. On the QSO count, band choice matters more than people expect. If you only have a modest antenna and a few watts, trying to hit the target on one band can stall once the pileup thins out. Having a second band ready, such as 40 m for daytime regional contacts and 20 m for longer distance, keeps the rate up. If you can run CW or a digital mode as well as SSB, the extra contacts from hunters who look for specific modes add up quickly. Just remember that duplicate contacts on the same band and mode usually don't count again, so a repeat caller doesn't help the total. For logging, I'd keep a single master log in your normal software and make sure the reference fields are filled in on every QSO as you go. Fixing them afterwards from memory is how typos in the KFF numbers get into the upload. Then export once and check the file before submitting to each program. Most upload problems come from a missing or malformed reference, not from the log itself.
  23. On latency, I'd treat the whole thing as three separate paths: control (CAT), audio, and spectrum or waterfall data. They behave differently on a bad link. CAT can be slow without hurting much. Audio is the one where you notice jitter. The waterfall can lag and still be usable. If your software lets you set the audio buffer size, start larger and reduce until you hear dropouts, instead of starting small and chasing glitches. For CW, I'd put the keyer at the radio end if at all possible. Typing or sending text to a local keyer avoids sending key-down and key-up timing across the internet. Paddles over a network work with some systems, but the result depends on the software's timing handling, so test by listening to your own signal on a separate receiver, such as a KiwiSDR near the station. That's a good use for a public receiver: it shows you what the other side hears, not what your monitor audio sounds like. On security, I agree about not exposing ports. If you must have more than one user, a VPN with separate keys per person is better than one shared password, because you can revoke one person without redoing everything.
  24. For portable operating, I'd suggest planning for offline use, since this is where web tools fall short. Before heading out, save what you need: a repeater list for the area, your own grid square, band plans, and any park or summit reference details. Cell coverage on a trail or in a remote park can be spotty, and spotting itself needs a connection, even if only briefly. Some activators arrange spotting through a friend or use a messaging option for that reason. On the spots, remember that POTA and SOTA pages are largely self-reported. Hunters should confirm the frequency by listening, because activators move and spots go stale quickly. If you are spotting someone else, include the mode and reference, and avoid spotting while they are still tuning up on the frequency. And for RepeaterBook-style data, check the offset and tone against the repeater's own coordinator or club page when you can. It takes a minute and avoids transmitting on a pair that has been changed.
  25. One way to decide what stays in the pack is to split items into "operation fails without it" and "operation is nicer with it." In the first group: rig, a power source with margin, an antenna and something to hold it up, a feedline, a key or mic, headphones, pen and paper. Spare fuses and a couple of connector adapters probably belong there too, because one dead connector can end the whole outing. Everything else is comfort, and comfort is fine, but it should be a conscious choice rather than gradual creep. On EFHWs, if you see an unexpectedly high or drifting SWR, check the feedpoint environment first. Coax laid across wet ground, a coax run that happens to be near a resonant length, or your hand on the transformer can all move things around. Rerouting or coiling the feedline, adding a choke, or changing the counterpoise length is often cheaper than assuming the antenna is faulty. A short dedicated counterpoise isn't cheating, it's part of the design. For power, size the battery to the activation, not to your worst-case imagination. SSB at 10 W draws very different current from CW at 5 W, and receive current adds up over a long session. A simple capacity estimate (average amps × hours, plus margin) tells you more than the label on the battery.

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.