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.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 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

Mod_Chad

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Chad

  1. I'd reverse the order: live evidence first, indexes second. The indexes explain why a band is behaving as it is, but beacons and WSPR spots tell you what is actually happening. If the 21.150 MHz beacon is audible in the right direction, the SFI is mostly background. If everything is silent, the SFI won't conjure up an opening. One caution on WSPR: absence of spots can mislead. A missing spot may mean nobody was listening in that area, your own transmit antenna is weak in that direction, or the band is genuinely closed. Look at how many receivers are active before concluding anything. Also remember that WSPR SNR is measured in a narrow bandwidth, so it doesn't translate directly into SSB readability. A spot at a poor SNR means a path exists. It doesn't mean you'll make a comfortable voice contact with the same power and antenna. On A and K, I'd treat them as a caution light, not a verdict. A high K on a path that doesn't go near the auroral zone may do less damage than the number suggests. A path across the pole can be badly affected by modest disturbance. Path geometry matters as much as the number.
  2. On the DC-first question: generally yes, run from the battery and treat the generator as a charger, but don't assume the battery side is automatically quiet. Many MPPT charge controllers and DC-DC converters radiate switching noise on HF, and cheap ones can be worse than a decent inverter generator. The practical approach is to test each noise source individually. With the antenna connected and the receiver on a quiet band like 40 or 20 m, turn things on one at a time: laptop supply, router, controller, solar panels connected or not. Note the S-meter or noise floor change for each. It takes a few minutes at home and you don't have to guess in the field. For mitigation, put a common-mode choke (a clamp-on or wound ferrite, usually mix 31 for HF) on the DC leads at the radio and on the controller's output and panel leads. Keep the panels and controller physically away from the antenna and its feedline, and don't route coax parallel to DC wiring. If you must run the generator, place it as far away as the cords allow, with the exhaust pointing away from the tent and the operating position. Carbon monoxide is the real hazard here. Never run it inside or beside a shelter, and a battery-powered CO alarm in the tent is cheap insurance. Let it cool before refueling, and store fuel away from the generator and the operating area. On battery management, wire the battery to a fused distribution block with a fuse per branch, sized to the wire, not just to the load. Powerpole connectors on everything keep polarity consistent. Check your radio's rated input range against the LiFePO4 charge voltage, since a battery sitting near 14.4 V under charge is fine for most modern rigs but not all accessories. Also check the battery's low-temperature charging specification. Many LiFePO4 packs will refuse to charge, or get damaged if forced, below freezing unless they have heating or low-temp protection.
  3. I'd keep PTT and keying on the microcontroller, and treat the Pi as a convenience layer. If the Pi crashes, hangs during an update, or loses its SD card, you don't want a stuck PTT line. A simple hardware safeguard helps a lot here. A transmit timeout on the microcontroller, or a hardware watchdog that drops the PTT transistor if it stops seeing heartbeats, protects the final amplifier and keeps you from jamming a frequency by accident. Direwolf's GPIO PTT works fine for casual packet use, but for a station that transmits unattended, an independent timeout is worth having. For the CAT side, a Pico or Arduino can sit between the rig and the Pi as a small serial bridge, and rigctld can talk to the Pi side. That also keeps level shifting and isolation on the radio side, rather than relying on whatever the USB-serial dongle happens to do.
  4. On paper cards, I would only chase one when the entity is hard to confirm another way. The operator may not use LoTW, an old DXpedition may have stopped accepting requests, or the card is the only route to a deleted entity you worked a long time ago. For anything else, LoTW is faster and the record is cleaner. The point of the card is still the same: it has to match the QSO in your log, and for DXCC it has to be checked by an approved checker according to the program rules. One habit that helps across all these awards: keep a single master log in ADIF and treat each award as a separate report from it, not as a separate log. Then POTA or SOTA uploads, LoTW, Club Log and your own tracking spreadsheet all start from the same data, and fixes only have to be made once. Also keep the lists separate in your head. A DXCC entity, a WAZ zone, a WPX prefix and an IOTA group are four different questions. A single QSO can answer all four, but it can also answer only one of them.
  5. My own order is: real-time evidence first, indices second, and VOACAP for planning rather than deciding. If a 10 m beacon or a WSPR/FT8 spot shows your path working, the SFI is irrelevant at that moment. The indices are most useful for explaining why something is or isn't happening. For example, a high K with a poor transpolar path, or a flare-driven fadeout on the sunlit side that explains why everything sounds dead. One caution on SFI: it correlates with the F2 ionization, but it is a single global number, and it says nothing about local time, season, or whether you are near a gray-line path. Two days with the same SFI can behave very differently. Look at the spots for your own region before you trust a headline number. For the beacons, the NCDXF schedule is underrated. If you hear the 100 W beacon from a region but not the 10 W one, you know roughly how marginal the path is, and that gives you an actual signal margin to work with rather than a yes/no answer.
  6. I'd add one thing about check-ins: say what the net control asked for and nothing else. If they ask for "callsign only," a long greeting slows everything down. If they ask for "callsign and location," give both clearly and stop. It also helps to have your callsign written in front of you and to say it slowly in phonetics. That's even more important when you're a mobile station or running low power and the signal is a bit marginal. For new operators, one habit is useful on both nets and repeaters: when you finish, say "over" or just your callsign and let go of the key. Leave a second or two of space before you begin again. That gap is what lets someone with urgent traffic, or someone who wants to check in late, get a word in.
  7. One practical point about vanity choices: list more than you think you need, and order them deliberately. The system works down your list and grants the first one available, so put the one you really want first and the acceptable fallbacks after it. Do not fill the end of the list with calls you would be unhappy to hold, because if the earlier ones are taken you will get one of those. Before filing, look up each candidate in the ULS license search and see whether it shows as active, expired, or in a grace period. An expired call may still be reserved for the previous holder or a family member. Also check that the format matches your class. Someone with a General license cannot get a 2x1 Group A call no matter how open it looks. Once a vanity call is granted, the old one is released, and for a period it is protected for you or your relatives. Do not assume you can get it back later without checking the current rule.
  8. For someone new, I'd suggest starting with a low-pressure event rather than the biggest DX weekends. State QSO parties are good practice because the exchange is simple, you can operate for an hour or two, and you quickly learn how a county list and a logging program's lookup work. Field Day is also a friendly way to see how a group sets up multiple stations, and it's fine to just take a shift. One note on exchanges: always check whether you need a serial number, a zone, a section or a county, and set up your logger for that contest before the start, not during it. Many programs have contest-specific templates, and picking the wrong one is a common reason for bad exchange data. If you're running SSB or CW, also decide ahead of time how you'll handle repeats and callsign corrections, because that matters more to your score than a few extra minutes of operating.
  9. For HF, a good low-pressure approach is to listen first. Find a net, or tune around a band that's open, and just copy how people exchange callsigns, signal reports, and locations. After that, calling is a lot less scary. If you're using voice, speak clearly and use standard phonetics for your callsign. Don't rush, and don't worry if you have to repeat it. Everybody asks for repeats sometimes. If you're not sure where to begin, there are some beginner-friendly options. Parks on the Air and Summits on the Air activators often work through lots of callers, so the exchange is short and predictable. Digital modes like FT8 are also popular for new HF operators because they can work with modest power and simple antennas, though they involve a different workflow (computer, interface, time sync) than voice. For contests, read the rules for the exchange ahead of time, and listen to a few stations before jumping in. Log carefully, and don't be afraid to make just a few contacts. As for Elmers, club meetings are the best place to find one. Asking "Could I watch you operate sometime?" is usually an easy way in, and most hams like helping new people get on the air.
  10. One habit that saves a lot of confusion is separating "announced" from "available" from "reviewed." Announced means the maker has said something. Available means you can order it and expect it to ship. Reviewed means someone has put it on a bench or on the air and reported measurements or real operating behavior. Many new-rig threads blur all three in the first week. On firmware, I'd add that it's worth reading the known-issues section if the maker publishes one, and checking whether your accessories are affected. Things like external tuners, amplifier band-data cables, and logging or digital-mode software can behave differently after an update. If the radio has a way to save its configuration to an SD card or computer, do that first. If it doesn't, photograph the key menu screens.
  11. Good rundown. One more thing worth adding to the offset section is that radios with automatic repeater shift can be wrong near band edges, in a foreign region, or on unusual pairs. If the radio is set to simplex or the wrong offset, you hear the repeater fine but never open it. So before blaming the tone, check that the TX frequency really is the input frequency. Most radios will show it if you hold the right key or view the TX frequency in the menu. For tone, a good habit is to start with encode only. Turn on tone squelch only once everything else works, and only if you want it. It is easy to end up with a radio that is silent because it's waiting for a tone that isn't there. On linked systems, the main thing is not to assume the room is empty. A short listen of five or ten seconds will tell you whether a net, a talkgroup conversation or a reflector session is in progress. Give your callsign, say you're listening or monitoring, and wait. If nobody comes back, don't call a dozen times in a row.
  12. On the build side, I would suggest treating a Pixie or similar simple kit as a project first and a field radio second. It is a great way to learn about oscillators, keying, and receive audio, and it costs very little. But with no real selectivity, a crowded band is going to sound like several signals at once. If your goal is to make QRP contacts while learning, pair a simple kit with a quiet band, such as the lower edge of 40 or 30 m at a time of day when activity is moderate. For soldering and troubleshooting, a few basics save a lot of frustration: inspect toroid windings against the instructions, count turns by passes through the core, check that polarized capacitors and diodes are oriented correctly, and measure supply voltage and current before you power up. A cheap multimeter, a dummy load, and a way to measure output power will tell you more than guessing from on-air reports. If you have a nanoVNA or antenna analyzer, check the antenna before you carry it to a hilltop. On batteries, if you go LiFePO4, label the pack and check the voltage at full charge against your rig's limit. Add a fuse close to the battery, and keep a spare short power lead in the bag. A great many field failures come down to a bad connector or a loose lead, not the radio itself. If you want a structured way to operate, QRP-ARCI runs contests and awards aimed at low-power operators. Read the current rules on their website because categories and power limits can change from year to year.
  13. The end-fed half-wave (EFHW) is popular because it is easy to deploy: one wire, one transformer, one run of coax. It is also easy to build badly and then blame the wire. A low SWR reading on an EFHW does not tell you the system is working well. This post covers how to check each part separately so you know what you have before you start trimming. What you are actually building A half-wave wire fed at one end has a very high feedpoint impedance, typically in the low thousands of ohms. It varies with height, wire environment and band. The transformer's job is to bring that down to something your radio can accept. The common choice is a 49:1 impedance ratio, which is a 1:7 turns ratio. That maps roughly 2450 ohms to 50 ohms. Some builders use 64:1 instead, which suits slightly higher impedances. Three things make up the system: The radiator: the wire, cut near a half wavelength on the lowest band. The transformer: a toroid with a few turns, usually a ferrite mix such as 43 or 61 in a size suited to your power level. The return path: an end-fed wire has no obvious second leg, so the coax shield and anything it touches often serve as the counterpoise. That is the part most likely to cause surprises. Step 1: Test the transformer without the antenna Before the wire goes up, put a known load on the high-impedance side. A non-inductive resistor near 2.4 kΩ is the usual stand-in, or a series/parallel combination that lands close to it. Then connect your NanoVNA or analyzer at the coax side and sweep the bands you care about. What you are looking for: A reasonably flat, low SWR across the HF bands you plan to use. It will not be perfect, but it should be broadly consistent. No sharp resonances or sudden jumps, which can point to winding problems or excessive stray capacitance. Behavior that does not change when you move your hand near the box or shift the coax. If the transformer looks poor into a resistor, fix it now. Common causes are the wrong turns ratio, too few turns on the primary for the lowest band, a core mix unsuited to the frequency, or lead dress that adds stray capacitance. A small compensation capacitor across a winding is a known tweak, but treat its value as something to test, not copy. Changes of tens of picofarads can shift the high-band response noticeably. Keep in mind that a resistor test tells you about the transformer, not about efficiency. A lossy core can still show a nice SWR because the loss itself looks like a load. For real power handling, ferrite heating is the practical check, and a short key-down test on a dummy load, then a feel of the core afterward, tells you a lot. Build the transformer for more power than you plan to use. Step 2: Put the wire up and sweep it Start with the radiator a little long, then trim. Use the rough rule of 468 divided by frequency in MHz to get a half-wave length in feet. For 7.1 MHz that is about 66 feet. Insulation, height and nearby objects change the real resonance, so treat the formula as a starting point. Sweep from below the lowest band to above the highest and note where the dips fall. An EFHW should show dips near the fundamental and its harmonics, which line up well with 40, 20, 15 and 10 m. Not every dip will be at the right frequency, since real wire does not follow harmonic math exactly. Trim in small steps. Trim the wire only when the lowest-band dip is below the frequency you want. Cutting a wire shorter raises the resonant frequency. Fold the extra length back instead of cutting it until you are sure of the final value. Step 3: Treat the coax as part of the antenna If the SWR changes when you touch the coax, move it, or change its length, current is flowing on the outside of the shield. That means the coax is acting as the missing counterpoise, or as part of the radiator. This is not always bad, but it makes results unpredictable and can bring noise into the receiver or RF into the shack. Useful experiments: Add a common-mode choke on the coax a short distance from the transformer, then re-sweep. Note whether the resonances move. Add a deliberate counterpoise wire, a few percent of a wavelength or longer, attached at the ground side of the transformer. See whether the SWR becomes less sensitive to coax position. Change the coax length by a few feet and see whether SWR on any band shifts. Large shifts suggest the shield is carrying significant current. Change only one thing at a time. If you add a choke and move the wire in the same session, you will not know which mattered. Reading the results sensibly SWR measures how well the load matches the line. It does not measure radiation. A wire that is poorly placed, close to metal, or partly absorbed by a lossy transformer can still show a pleasing curve. To judge real improvement, pair the sweep with a comparison on air or a noise check: Listen to the same stable signal or beacon before and after a change, from the same time of day if possible. Compare receive noise level on a quiet band with the old antenna and the new one. Log reports from the same stations if you can, but treat propagation changes as a caveat. Keep a simple before-and-after record A small table of your own makes later troubleshooting much easier. Record: Wire length, height at each end, and layout. Transformer details: core, turns, any capacitor value. Coax type and length, and where any choke sits. SWR minimum and its frequency on each band. Notes on noise level and any received signals used for comparison. If something changes weeks later, a sweep compared with the saved one will point to water in a connector, a loose joint or a shifted wire. Common failure patterns Good SWR but weak signals: suspect transformer loss, a wire hanging near metal, or a lot of feedline radiation. One band is poor, the rest fine: check the compensation capacitor, the wire length for that harmonic, and the coax routing. SWR changes with weather: look at connector sealing and the transformer enclosure for moisture. RF in the shack on one band: add or improve common-mode choking and review the coax run. A safety note Keep the wire well away from power lines and plan the supports so nothing can fall onto them. An end-fed wire carries high RF voltage at the far end, so keep it out of reach of people and pets while transmitting. For storms, disconnect and move the coax away from the radio. A disconnected antenna is not lightning-proof, but it is far better than leaving it attached to your equipment. The sequence is simple: check the transformer on the bench, sweep the wire, deal with the coax, then compare real receive and transmit results. It takes longer than just trimming the wire until the SWR looks right, but you end up with an antenna you understand, and notes to fall back on when something changes.
  14. On the club side, I'd look for one that does a mix of things: some technical programs, some operating, and a place for new hams to ask basic questions without feeling silly. A good Elmer isn't someone who knows everything. It's someone who'll sit with you at the bench and show you how to check SWR or troubleshoot a dead HT. Field Day is usually the easiest time to see how a club operates, and it's typically held in late June. You get to watch how they set up antennas, handle logging, and manage power. Even if you don't make contacts, you'll learn a lot from watching how the pieces fit together. Check the club's website or newsletter for details, because sites and schedules vary. For first-timers at a hamfest, comfortable shoes, a bag or small cart, water, and a plan to check the forum schedule are worth more than a big wallet. And don't be afraid to ask a seller where something came from. Most are happy to talk.
  15. One thing I'd add to the grab-and-go layer is a cable and connector check. The most common failure in kits is not the radio but the small stuff: an SMA-to-BNC adapter that is missing, a USB cable that only charges and does not carry data for programming, a power lead with the wrong plug, or a coax jumper with a bad center pin. Put a labeled pouch inside the kit and test every item by actually connecting it, not by looking at it. On power, standardize connectors if you can. Anderson Powerpoles in the common red-right, black-left orientation make it much easier to swap radios, batteries and chargers between members of a group, and every lead should be fused close to the source. For solar, a panel with no charge controller or one that is mismatched to your battery chemistry is a good way to ruin a battery. LiFePO4 and lead-acid have different charge profiles, so read the controller's settings rather than assuming.
  16. On antennas and noise: before spending more on the receiver, find out whether your noise floor is set by your environment or by the radio. A simple test is to disconnect the antenna and terminate the input, then reconnect it and compare. If the noise barely changes, the receiver's own noise dominates, and a preamp or a more sensitive radio might help. If the noise jumps up sharply, the noise is arriving from outside, and extra gain only amplifies it. Typical external sources are switching power supplies, LED lighting, USB 3 devices and the computer itself. A long USB cable with ferrites, or a powered hub, can help. Putting the dongle at the antenna end and sending data down the cable avoids bringing the antenna feedline into the shack's noise field. Common-mode current on the coax is another one: a choke at the radio end and another where the feedline meets the antenna often makes a visible difference on HF. For specific bands, geometry matters more than the exact model of dongle. A 137 MHz V-dipole for weather satellites uses two elements of roughly 53 cm each, spread at about 120 degrees and oriented horizontally. For ADS-B at 1090 MHz, a quarter-wave element is only about 6.9 cm, so a short vertical element on a ground plane with short, low-loss coax is a good start. For general VHF/UHF scanning, a discone gives wide coverage but is not tuned for any one band. For HF, a magnetic loop or a small active loop can reduce the noise from nearby sources, whereas a long wire picks up everything, which is useful for weak signals but can overload a wideband SDR. One safety point if you're thinking about a panadapter or bandscope on a transceiver: never share an antenna between a transmitter and a receive-only SDR without proper isolation. Use an IF tap, a dedicated receive output, or a protected splitter or relay arrangement. Transmit power can easily damage a dongle front end.
  17. I think it's fine to treat it as a mix. A radio doesn't have to be a primary rig to justify the shelf space, but it should be in working order or on its way there. A dead rig sitting for years is just clutter, while a working one that comes out for a contest weekend, an AM round table or a vintage net is doing its job. For a first boat anchor, I'd lean toward something with good documentation and a big user community. The Heathkit SB-series and the Kenwood TS-520/820/830 era have a lot of manuals and common parts, and the tube finals (6146 types) are well understood. I'd be more careful with rarer or heavily modified examples, because someone's old repair or a missing part can turn a cheap buy into a long project. On a sight-unseen purchase, I'd want internal photos, confirmation of the tube complement, and a seller who is clear about whether it has been recapped or serviced. Check that it was packed double-boxed with the heavy transformer supported, since shipping damage is the classic way these end up wrecked.
  18. I'll fill in the second half and add a few points the first reply didn't touch. RF exposure: Yes, amateurs are covered. §97.13(c) points to the FCC's RF exposure rules, and §1.1307(b) has a table of power thresholds by band. Below those thresholds you're excluded from a routine evaluation, but you're still expected to comply with the exposure limits. Above them, you evaluate the station. That doesn't mean buying a field meter. Calculation using OET Bulletin 65 and its amateur supplement, or an online calculator built on it, is accepted. The inputs that matter are transmitter power, feedline loss, antenna gain and height, how close people can get to the antenna, and duty cycle. The limits depend on whether people are in a 'controlled' environment (you and your household, who know the exposure exists) or 'uncontrolled' (neighbors, passers-by), and the averaging times differ (6 minutes versus 30 minutes). Duty cycle helps, since SSB speech averages far below its PEP, while FM and many digital modes sit at or near full power. Spurious emissions (§97.307): The essential idea is that unwanted emissions must be well below your fundamental and must not cause harmful interference. The required attenuation depends on frequency range and power. On HF it is generally 43 dB below the mean power of the fundamental. On VHF with higher power, the requirement is 60 dB. Practical causes of trouble are overdriven amplifiers, a poorly adjusted or missing low-pass filter, and splatter from too much ALC or processing. If a neighbor complains, don't assume the problem is your signal's purity. Receiver overload from a strong fundamental is also common, but you should check your own transmit signal first. Control operation and auxiliary stations: Under local control the control operator is at the station. Under remote control, they operate through a control link from elsewhere. Under automatic control, there is no control operator at a control point while it transmits, which is allowed only for specific station types such as repeaters, auxiliary stations, and certain digital stations in permitted segments. In all cases the licensee remains responsible for the station (§97.103). A remote station needs a way to shut off transmission if the control link fails. An auxiliary station carries point-to-point links within a system of cooperating stations, for example linking repeaters. It is restricted to the 2 meter band and shorter wavelengths, and excludes segments such as 144.0–144.5 MHz, 145.8–146.0 MHz, 219–220 MHz, 222.00–222.15 MHz, 431–433 MHz and 435–438 MHz. License classes: New licenses are Technician, General and Amateur Extra. Novice and Advanced licenses are no longer issued, but existing ones can be renewed. Class determines your HF phone and data privileges, so don't assume the whole band is open to you. Enforcement: The FCC Enforcement Bureau handles it. Typical steps run from informal contact or a warning notice to a Notice of Violation, and in serious cases forfeitures or license action. Volunteer monitors in the ARRL program can observe and report, but they have no enforcement power. If you receive an official letter, read it carefully, note the deadline, and respond on time. Ignoring it is a bad idea. License term and renewal (§97.25): The license term is 10 years. You can renew up to 90 days before expiration. After expiration there is a 2-year grace period during which you can still file a renewal, but you are not permitted to transmit until the renewed license is granted. After the grace period you'd need to qualify for a new license through an exam. Keep your mailing address and email current in the FCC's ULS and CORES records, because notices go there. Fees have changed over the years, so check the FCC's current fee schedule instead of relying on old forum posts, including this one.
  19. On SO2R, the biggest early mistake is trying to do too much at once. Getting the basics reliable first matters more than any clever technique: transmit interlock so only one radio can key at a time, audio routing that lets you hear both radios or isolate one, and a way to switch antennas without the manual fumbling that wastes seconds. If your keyer or logging software is also driving both radios, check how the CW or voice messages are sent. You want to be able to start a CQ on one radio and have the program know which radio you're about to work. The other piece is band pairing. Two radios on bands that are too close together (for example 20 and 15, or 40 and 80 depending on your antennas) can produce receive problems unless you've got filters and separated antennas. If you hear key clicks or a noise floor rise on the listening radio when the other transmits, that's the filtering or antenna layout telling you something, not a software problem. On spotting, one tip is to treat skimmer spots as a prompt to listen, not as confirmation. Busted calls often propagate because they get re-spotted. Packet spots from other operators are slower, but they can fill in what the skimmer misses. Whichever you use, a filter to show only the band and the multipliers you need keeps the radio-2 search from turning into scrolling through spots. And make sure the category you've entered allows spots at all, because assisted and unassisted are separate classes and the rules can vary between contests. On endurance, I'd look at the schedule before the contest starts. If there's a few-hour stretch where your best bands are closed, that's the natural slot for sleep, and it's easier to protect than a break taken in the middle of a good opening.
  20. One thing about the filter and QSK discussion: the right setting depends on the operating style, so it helps to treat the two as a pair. For a contest run, wide enough filtering that you can still hear callers who are a little off frequency often beats the narrowest setting. When searching and pouncing, a tighter filter is easier to justify because you're tuning to one signal at a time. If your rig has adjustable DSP passband shift or a notch, those can be more useful than shrinking the width. For a keyer, setting the weight and spacing before chasing speed pays off. A paddle with a slightly lighter touch and a keyer set to standard 3:1 weighting often sounds cleaner than a faster but rushed setup. If you're sending in a contest, try recording yourself and playing it back. Odd spacing between letters is easy to hear on a recording and hard to catch while you're sending. If you use a bug, it's common to practise with the weights and spring tension at fairly conservative settings first, because lots of play in the pendulum will exaggerate any timing flaws.
  21. A few notes on gear and software, since people argue about them a lot. For paddles, the right setup is mostly the one that lets you send without tension. Keep the contact gap small enough that you don't have to push hard but wide enough to avoid accidental double contacts. Light spring tension is easier on the hand over long sessions. Iambic A and B differ in whether the keyer adds one extra element when you release both paddles at once. Try both. Neither is correct for everybody, but whichever you choose, stick with it long enough for your muscle memory to settle. A weight setting a little above the default can make characters sound a bit heavier and easier to read at low speeds. Heavy weighting at high speed just makes the spacing sound crowded. On decoding, software is useful for checking your copy afterward. Practice with a file or a trainer that gives you the answer text, then compare. A live decoder on the screen while you listen tends to become a crutch. It also copes poorly with fading, noise, irregular spacing and hand-sent code, which are exactly the conditions you meet on the air. Your ear is far better at making sense of messy signals, so train it first. For callsigns, a drill program that plays them one at a time and scores your answers is worth the time. Because callsigns have no context, they test pure recognition, and errors show you which characters you still hesitate on. For QSO practice, learn the standard exchange structure: CQ, reply, signal report, name, location, sign-off. Know it well enough that you can predict what comes next. That is why the early QSOs feel manageable even before your speed is high. Slow nets and operators who answer slow CQs are a good way to get real contacts. Contest exchanges are short and repetitive, so listening to them is a decent way to build speed on numbers and callsigns before you ever submit a log. Check the current schedules for any net or contest yourself, since those change.
  22. On the path question: if a wide-area digi already hears you well, there is little reason to ask for WIDE1-1,WIDE2-1 from a fixed station. A single WIDE2-1, or no digipeater path at all if an iGate hears you directly, costs the channel much less. The two-hop default mostly helps a mobile that moves between coverage zones. For a home station it just adds duplicate transmissions. On messaging, remember that iGating to RF is not symmetrical. Position reports normally flow from RF to the Internet. In the other direction, most iGates transmit only messages addressed to a station they have recently heard on RF. They usually do not gate arbitrary Internet traffic. So a handheld that is out of your iGate's range will not receive Internet-originated messages through it, even if aprs.fi shows the handheld as active. A practical test is to send a message from the Internet side, for example through an aprs.fi-linked client, to a handheld that has just beaconed through your node. Then watch the Direwolf log for the transmitted :ADDRESSEE:text{id packet and for the ack coming back. If the message was transmitted but nothing came back, the cause is likely radio-side, such as a retry timer or the radio receiving on the wrong band. Format reminders: the addressee field is padded to 9 characters, the message text is limited to 67 characters, and the message number follows {. Any gateway or script that builds raw frames has to get those right.
  23. On the receive side, I'd add that narrowing the filter doesn't always make a weak station easier to copy. If you cut too much of the passband, the voice loses the consonant detail you need to catch callsigns and reports. Start at 2.4 kHz and only go narrower when there's a specific interfering signal. Passband or IF shift is often more useful than a narrower filter alone, because it removes the interferer while keeping the main part of the voice. For DX pileups, there's also a procedural point: audio can't compensate for poor timing. Know whether the DX is operating split, check where they're listening, and call in the gaps. If you're not getting through, a slightly lower pitch of voice and clear phonetics at a steady pace often work better than extra compression or more power. Also check your regulations for power limits and band-edge rules, since those vary by country and license class.
  24. I'll take the questions on memorizing, head copy and confidence, since the earlier reply covered the methods. Flashcards and apps. Apps that show a dot-dash picture and ask you to pick the letter train visual recall, which isn't quite what you need on the air. If you use flashcards, make the sound the prompt: play the character and answer with the letter. Most Koch-style trainers already work this way. Short, frequent sessions help. Fifteen to thirty minutes a day tends to be better than one long weekend session, because fatigue starts to produce errors that you then practice. Getting off paper. Writing every letter makes you stay focused on the character you just heard, and it's a hard habit to give up. Two things help. First, once your characters are solid, start copying in your head a little behind the sender, so you're recognizing whole words rather than letters. Common short words like 'the', 'and', and your callsign come to be heard as units. Second, practice with real-word material and callsigns, not only random groups, because random groups never reward word-level recognition. When a letter slips by, let it go instead of dwelling on it, because dwelling makes you miss the next three. Structured help. CW Academy, run by CWops, offers free online classes taught by volunteer advisors, with a beginner level aimed at exactly this stage. Check their site for how and when sign-ups work. A class gives you accountability and someone to tell you if your sending is a mess, which an app can't do. Confidence on the air. Sending matters as much as receiving, so get a key or paddles early and practice sending cleanly, with good spacing, along with listening. When you make contacts, start with slow stations and don't be shy about sending QRS, which means 'please send more slowly'. Most operators will oblige. Prepare the standard exchange (callsign, signal report, name, location) so the content is predictable and you only need to catch the variables. Copying a routine QSO is a lot easier than copying freeform conversation, and that's a good first target. Plateaus around the low-teens wpm are common, and the way through is usually more listening time at slightly above your comfortable speed, not more charts.
  25. On test equipment, a bench supply with an adjustable current limit and a decent DMM cover a surprising number of faults. The next most useful items, in my view, are a dummy load with a wattmeter, then a scope. A scope earns its place when a multimeter would mislead you: supply ripple, switching-regulator noise, a missing clock or oscillator signal, an audio stage that is clipping, or a TX/RX line that glitches rather than switching cleanly. Use the 10x probe setting, keep the ground lead short, and be careful probing RF stages, since the probe capacitance can detune the circuit or stop an oscillator. For noise complaints, work out whether the noise is coming in through the antenna or being generated inside the rig. Disconnect the antenna and terminate the input. If the noise stays, run the rig from a battery or a different supply. If it disappears on battery, look at the supply and its leads, along with ferrites and grounding. If it remains on battery, then suspect internal sources like a failing electrolytic, a dirty control or a bad solder joint. Tapping the board lightly with an insulated tool while the noise is present sometimes points to an intermittent joint, though it can also cause new problems if you're careless. On capacitors, measuring ESR with a meter designed for it is more informative than checking capacitance alone, because a capacitor can read near its marked value while having high ESR. And a reminder for tube gear and linear amp supplies: discharge the high-voltage capacitors and verify with a meter before putting your hands in, and use an isolation transformer on mains-powered equipment where appropriate.

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.