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_Tom

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Tom

  1. One thing I'd add on the RF side: treat every cable leaving the box as an antenna and decide up front what happens to it. For a switch box that means a filter or ferrite on each control line, a bypass capacitor where the line enters the enclosure, and a single clear grounding scheme. Daisy-chained grounds that wander around the bench are a common source of ground loops and hum on audio lines too, especially with a Direwolf setup. For Direwolf specifically, audio level matters more than people expect. Overdriven transmit audio gives wide, splattery packets, and a receive level that's too hot or too low costs decodes. The Direwolf documentation describes using its audio level reporting to set the radio's output and the sound card input, so use that rather than guessing. Isolation transformers on the audio lines between the radio and the sound card are cheap insurance against ground loop noise. For APRS trackers on an ESP32 or Pico, the main design decisions are the GPS module, the modulation method (many use a PWM or DAC-generated AFSK tone), and how you couple the audio into the radio's mic input with proper attenuation. The usual limits on beacon rate and path settings matter just as much as the electronics, since a badly configured tracker can clog a local frequency.
  2. On "what to buy first," a few suggestions that fit a lot of situations, but adjust them to your goals and budget. If you want local contacts and clubs, a decent dual-band handheld is a sensible start. Spend a little on a better antenna for it, like a roll-up J-pole or a magnetic-mount whip on a car roof, before spending on a second radio. The antenna usually makes a bigger difference than the radio. If HF is the goal, listen first. A used HF transceiver, a power supply that can handle its current draw, and a simple wire antenna like an end-fed or dipole will get you going. Don't ignore the feedline and the ground or common-mode choke. Cheap coax and a poor match can eat a lot of your signal, and noise from nearby electronics can drown out what you're trying to hear. An inexpensive antenna analyzer or a good SWR meter is worth having so you know what the antenna is doing. Common mistakes: transmitting into an unplugged or unmatched antenna, buying a pile of gear before knowing what you enjoy, and skipping the manual. Also get to a club meeting. Someone there can usually help you check your setup, lend a meter, or point you at a net or a Field Day station where you can watch a contest operator work before you try it yourself. For a first HF contest, search-and-pounce is gentler than calling CQ. Listen to a few exchanges, copy the format, and answer one when you're comfortable. Most operators are patient with newcomers, especially if you say it clearly: "say again" is a perfectly good thing to say on the air.
  3. One point that saves time is to treat the gateway list as a shortlist, not a guarantee. On VHF the question is whether the gateway is reachable from your antenna height and terrain. On HF it's the time of day and band, so a station that's listed as close may still be unusable while one a thousand miles away works. Prediction tools only estimate. It's worth connecting during the same hours you would need it, and noting which gateways answer at those times. A short list of a few reliable gateways on two or three bands is more useful in practice than a hundred entries. For packet, the usual snags are TNC settings and the AX.25 callsign/SSID being used to connect. For VARA, check that the modem program and Winlink Express agree on the TCP ports, and that the bandwidth setting matches what the gateway offers. For FM, the radio's deviation and the data-port audio settings matter more than people expect. Marginal audio can still connect but crawl. If an HF connection starts and then fails to hold, check three things before blaming propagation: the rig is on USB with the filter wide enough, the dial frequency is right, and audio levels aren't clipping. Also resist retrying the same gateway endlessly. Move to another one or another band, which costs less time than five failed attempts on one path.
  4. On 2 m and 70 cm, the array and the receive chain share the job. A common entry point on 2 m is a phased array of several long-boom Yagis (four is typical) with a legal-limit amplifier. Single-Yagi operation is possible, but you will mostly hear only the largest stations. Whatever the array, the first thing to check is the receive noise figure. A mast-mounted low-noise preamp with a very low noise figure and a good sequencer so the transmit relay never hot-switches are worth more than an extra dB of antenna gain you cannot hear. Feedline loss counts twice, once on transmit and once as added noise on receive. As a rule of thumb, 0.1 dB of loss ahead of the preamp adds about 7 K to system noise. That is why the preamp sits at the antenna and why the relay and connectors ahead of it should be the best you can get. On 2 m the sky itself is noisy, especially when the Moon is near the galactic plane, so the same hardware performs differently from day to day. WSJT-X's Astronomical Data window shows sky temperature and a degradation figure for exactly this reason. Polarization is where 2 m differs most from the higher bands. Faraday rotation in the ionosphere scales roughly with the inverse square of frequency, so it is severe on 144 MHz, much smaller on 432 MHz, and negligible from 1296 MHz upward. On 2 m the rotation changes over minutes to hours, so a fixed linear polarization can fade to nothing for a while even when everything else is right. There is also a geometric offset between the two stations' views of the Moon. Common answers are a crossed-Yagi array with a polarization switch or phasing network, or a mechanically rotatable array. Pure horizontal or vertical can work, but you should expect a share of unavoidable fades. For operating, put the quick things on your list: use the correct JT65 or Q65 submode, set your Doppler correction properly, and agree on which of you transmits in the first period. Use the shorthand messages sparingly and only when your partner's software expects them.
  5. On modeling first or building first, it depends on what the question is. For a simple dipole, cut-and-trim is quicker than modeling it. For asking something like how much a sloping radial angle changes feed impedance, or whether a trap or fan arrangement leaves a strange pattern, a model gets you the answer before you have wire in the air. One practical habit for both MMANA and EZNEC: model your measured antenna after you build it. If the model resonates a few percent away from the real one, adjust the ground or wire height assumptions until they line up. Once they match, you can trust the model more for the next change. Also keep segment count consistent when you compare two designs, otherwise the comparison can be dominated by numerical differences, not by the antenna. For verticals specifically, treat model results with some caution. Radial-field loss and nearby objects are hard to represent, so use it for relative comparisons, and rely on field measurements for the final tune.
  6. One point on hunting that's easy to forget is that your contacts with activators only count for your own awards if you check how the program wants hunter claims handled. Don't assume that being in the activator's log automatically produces a hunter record for you. Look at the award rules and see whether the logs and the claim process are separate steps. For activators, I'd add a note about mode choices. FT8 and other digital modes are useful for getting numbers when a band is unreliable for voice, but check that the program accepts those contacts for the activation count. Also be prepared for hunters who work you on SSB and then ask for a CW confirmation, or the reverse. A plain, consistent exchange (callsign, signal report, reference) keeps the log accurate and makes the upload easier. And as above, confirm the park's access rules and any permit or hours restrictions before you go. A WWFF reference can sit inside a more tightly managed reserve than the typical park.
  7. When WSJT-X shows an empty decode window on a band that should be busy, or the radio won't key, the cause is nearly always one of a handful of things: the clock, the audio levels, or the rig-control link. This checklist works through them in the order that saves the most time. Step 1: Confirm the basics before touching settings Frequency and mode. Make sure the radio is on a standard FT8 frequency, such as 7.074 MHz on 40 m or 14.074 MHz on 20 m (USB, dial frequency), and that WSJT-X is set to FT8 rather than FT4 or another mode. Band conditions. A quiet waterfall may just mean the band is closed. Try a band you know is open at that time of day before assuming something is broken. Radio mode. Use USB-Data (or the equivalent) so the radio passes a flat audio response and doesn't apply voice processing. Step 2: Fix your clock first FT8 works in fixed 15-second slots, and the decoder only tolerates a small timing error between your computer and the station you're hearing. If the waterfall shows signals but nothing decodes, or you only decode some stations, suspect time. Many operators try to keep the clock within a fraction of a second. Check that automatic time sync is enabled in your operating system. Default Windows sync intervals can be long, so many operators install a dedicated time-sync utility that polls more often. On Linux and Raspberry Pi systems, a running NTP or chrony service normally handles this. On a Pi without a real-time clock, remember it relies on the network to get the time right after boot. WSJT-X displays the time offset (DT) of each decoded signal. If most stations show a consistent DT of the same sign and size, the error is probably on your side. Step 3: Set receive audio levels In WSJT-X, the level meter at the bottom left shows your incoming audio. The user guide suggests aiming for roughly 30 dB on the meter, and you should avoid anything in the red, which means clipping. Too little audio won't hurt decoding as much as too much will, because overdriven input distorts and spreads signals across the passband. Adjust the radio's USB audio output level or the operating system's input slider, not both at once. Turn off any audio enhancements, AGC-style processing, noise suppression or microphone boost on the sound device in your operating system. Set the sample rate to 48,000 Hz, 16-bit, if your system offers a choice. In Settings > Audio, check that the input device is the radio's codec and not a webcam, headset or built-in microphone. USB devices often appear with generic names such as "USB Audio CODEC", and the order can change after a reboot or when you plug into a different port. Step 4: Get CAT control working In Settings > Radio, WSJT-X uses the Hamlib library to talk to most transceivers. Choose your rig model, serial port, baud rate, data bits, stop bits and handshake to match the radio's menu settings, then press Test CAT. The button turns green when the link works and red when it doesn't. If it stays red, check in this order: Baud rate mismatch. The radio's CAT or CI-V speed must match what WSJT-X is set to. Some radios also have an auto setting that can cause trouble. Wrong COM port. USB-serial adapters can be renumbered by Windows. Check Device Manager or, on Linux, the device list under /dev/serial/by-id, which is more stable than ttyUSB0 style names. Port in use. Only one program can open a serial port at a time. If a logger, rig-control program or another digital program already holds it, WSJT-X can't connect. Driver problems. Many radios use common USB-serial chips. A missing or outdated driver often shows up as a port that vanishes or can't open. Radio-side settings. Some radios need CAT enabled, a particular USB or serial function selected, or a CI-V address set to match. Step 5: Sort out PTT and split PTT can be keyed by CAT command, RTS or DTR serial lines, or VOX. CAT is usually the simplest on modern radios with built-in USB. Use Test PTT to confirm the radio actually keys before you try a real transmission, ideally into a dummy load. The Split Operation setting matters more than people expect. WSJT-X is designed to keep your audio tone in a sweet spot (roughly 1500 Hz) while the dial moves. Choosing Rig uses the radio's true split mode, while Fake It retunes the dial around transmissions. If the transmitted signal looks distorted or your radio keeps retuning, try the other option. Step 6: Don't overdrive the transmitter FT8 is a constant-envelope mode, but your audio chain still has to be linear. The usual approach: Set the radio to a modest power level. Use WSJT-X's Pwr slider and your computer's output volume to bring up drive until you see just a hint of ALC movement, then back it off so ALC reads zero or near it. Remember that more audio does not mean more power in a clean signal. It means splatter that annoys neighbors on the band. Mute system sounds, notifications and other applications so nothing unintended goes out over the air. Step 7: Check whether anyone hears you Once you're transmitting, PSK Reporter is a handy independent check. Enable spotting under Settings > Reporting, then look up your callsign on the PSK Reporter website to see which stations reported you and where. Your grid square needs to be correct in WSJT-X for the map to make sense. Spots appearing within a few minutes tell you the whole chain is working; no spots on a band that other stations clearly use points to an antenna, power or audio issue. For CW and RTTY, the Reverse Beacon Network does a similar job for those modes, though it won't see FT8. Step 8: Share the radio with logging software A common trouble spot is running WSJT-X alongside N1MM+ or Log4OM. Both of those programs normally want to control the radio too. Options include: Let WSJT-X own the serial port and have your logger read frequency and mode from it via UDP rather than direct CAT. Use a rig-control middleman, such as a program that shares the radio between several applications through virtual serial ports. Use the radio's second virtual port if it provides one. For logging, WSJT-X can broadcast its decodes and logged QSOs over UDP, which loggers and helper tools can read. Check that the UDP server address and port match on both ends, and that no firewall is blocking them. A quick diagnostic table Waterfall looks fine, no decodes: clock, wrong mode, or audio level too high. Waterfall is blank: wrong input device, muted input, or radio not in USB-Data. Test CAT is red: baud rate, COM port, driver or another program using the port. Radio keys but no output: output device set to the wrong sound card, or audio muted. Transmits but no spots: band closed, wrong grid, or no reporting enabled. Final thoughts Change one thing at a time and re-test after each change. Writing down the settings that work once you have a stable setup saves a lot of grief after an operating system update or a new USB port shuffles your devices. If you run a Raspberry Pi or a dedicated shack PC, consider documenting the device names and baud rates somewhere you can find them in a hurry.
  8. For nets, the main tip is to learn the format before you check in. Most nets have a net control station (NCS) who runs the order, calls for check-ins and keeps traffic moving. Listen to a full round first. Typical formats ask for short-time check-ins, then regular check-ins, then traffic or announcements. If you're unsure, wait for the call for check-ins and give only your callsign, and your name or location if requested. Don't start a conversation with the NCS or another station unless invited. Keep transmissions brief and let the NCS acknowledge you. If the net uses a repeater, pause between overs so others can break in. If you have emergency or priority traffic, use the net's stated method for it. Don't talk over the NCS, and if the net has a script, follow it. Check-ins can be tedious for the control operator, so keeping your transmissions clean helps a lot. It's also fine to say you're just listening. Many nets welcome new operators and guests, but they usually prefer you identify yourself clearly. If you want to take part in future, ask the net manager or look up the net's published procedures. Net control is a skill worth learning too: a calm voice, consistent phrasing and good note-taking keep a net orderly even when conditions are poor.
  9. Start with the layers. Part 97 (mainly 97.301 through 97.307) is the legal layer. It defines which bands each license class can use, which sub-bands are restricted by emission type, and the power limits. The ARRL band plan is a recommendation built on top of that. It tells you where CW, narrowband digital, SSB, SSTV, beacons and so on are customarily placed so they don't trample each other. Nobody gets cited for running PSK31 at the wrong spot in the digital area, but you'll get complaints, and 97.101 still expects you to cooperate with other users. The FT8 frequencies (7.074, 14.074, 21.074, 28.074 and so on) are convention only. They aren't in the rules or in any legal band plan. On license privileges, here's the HF picture for the US. Check the current Part 97 chart before relying on my summary, because details can change. Technician: CW on parts of 80, 40 and 15 m (roughly 3.525-3.600, 7.025-7.125, 21.025-21.200 MHz). On 10 m, 28.000-28.500 MHz, with CW and data in the lower part and SSB in 28.300-28.500. HF power is limited to 200 W PEP. Everything above 50 MHz is open to Technicians. General: most of 160 through 10 m, with the lower or edge segments of 80, 40, 20 and 15 m reserved for Extra. Examples: General phone on 75 m starts at 3.800, on 40 m at 7.175, on 20 m at 14.225, and on 15 m at 21.275. General CW/data on 20 m starts at 14.025. Extra: everything, including the Extra-only slices like 3.500-3.525, 7.000-7.025, 14.000-14.025 and 21.000-21.025 (CW/data), and the lower phone segments General can't use. Bands like 160 m (1.800-2.000), 30 m (10.100-10.150, CW/data only, 200 W PEP), 17 m (18.068-18.168) and 12 m (24.890-24.990) are shared by General and Extra. 30 m has no phone at all. 17 m and 12 m allow all modes. Those three are the WARC bands, where contests don't take place. Band edges: the rule is that your whole emission has to stay inside the allowed segment, not just your dial frequency. The two most common mistakes come from sidebands. Above 10 MHz, SSB conventionally uses USB, so the signal extends above the dial frequency by up to about 2.7-3 kHz. At the top edge of 20 m (14.350), keep the dial far enough below that the whole signal fits. Below 10 MHz you use LSB, so the signal extends below the dial. If you're a General on 75 m, 3.800 on the dial puts part of your signal below 3.800, which is outside your phone privileges. Keep the dial a few kHz inside, so 3.803 or 3.805 or higher, depending on your filter. Allow extra margin if your dial readout or transceiver calibration is off. For CW, keep the signal and its keying sidebands inside the edge too. For digital modes, remember that the dial frequency usually isn't the signal frequency. In USB-D, the transmitted audio tones add to the dial frequency, so a signal at 1500 Hz audio on a 14.074 dial is at 14.0755. Check that the highest tone you can generate still fits. For 60 m, the US allocation has historically been five channels rather than a continuous band, with the dial (USB) frequencies at 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz, and center frequencies 1.5 kHz above those. You tune the radio in USB so your signal is centered correctly in the channel, and the power limit is stated as 100 W effective radiated power relative to a half-wave dipole, so feed line loss and antenna gain matter. General and Extra only. Allowed modes have been expanded over the years to include CW and some digital modes in addition to USB voice. Because of WRC-15's international 5351.5-5366.5 kHz allocation and subsequent FCC action, the US rules on 60 m have been in transition. Read the current text of 97.303 and the FCC's latest notices on 60 m before you operate. Don't rely on a memorized channel list.
  10. For run versus S&P, don't judge by the instantaneous rate. Judge by the rate over a longer window, say the last 30 to 60 minutes, and compare it with what the other mode would give you. N1MM's rate display helps because it shows several windows at once. A short dip is often just a gap in callers, but if the longer-term rate has fallen and you're spending more time calling CQ than working stations, it's time to move. One easy rule: if you're calling CQ for several minutes at a stretch with nothing back, either change frequency, change band, or go multiplier hunting. Set the number of minutes before the contest so you aren't deciding it while worn out. Also remember that giving up a good run frequency costs something, because you may not get it back. That's the reason many operators use the second radio to check whether the next band is worth the move before they leave the first one. On the multiplier math, you've got it right. The practical point is that early on, multipliers come almost for free while running, because new stations keep calling you. Later they won't. So the common approach is to spend run time when the rate is highest and save the dedicated multiplier hunt for when the run rate has dropped below what a multiplier is worth. Compare Q/M against what you'd lose by leaving the run frequency for a few minutes, and the decision becomes less emotional. For band changes, keep a simple log of when each band opened and closed in previous years' propagation, or look at the typical band plan for the contest. A band change made for a reason (the other band is opening, this one is closing) beats a change made because you're bored.
  11. On the filter question, the usual advice is to use the widest filter that still gives you clean copy. A 200 Hz filter can sound great on a crowded band, but it also hides callers who are a little off frequency, and a very narrow DSP or crystal filter can ring on strong signals, which makes characters smear together. Something around 300 to 500 Hz is a common starting range for general operating. Tighten it when QRM requires it, and widen it again when you're searching or running a pileup. Matching your sidetone pitch to the receive pitch helps more than people expect. If your sidetone is at 700 Hz but you tune stations in at 500 Hz, you are making zero-beating harder than it needs to be. Pick a pitch that is comfortable for long sessions and keep it consistent across the radio, the keyer, and any logging or skimmer software. QSK is worth trying if your rig supports it properly. Hearing the band between your own elements lets you notice someone calling you, or a station already on frequency, without waiting for a hang-time delay. It does depend on the equipment, though. Some amplifier and relay combinations can't keep up with full break-in at higher speeds, so semi break-in with a short delay is a sensible fallback.
  12. Adding something on panadapters and bandscopes, since they get less attention. A panadapter takes the receiver's IF or a sample of the RF and shows you a spectrum display next to a conventional rig. It lets you spot activity across a band without tuning around. The details depend entirely on the radio. Some transceivers have a dedicated IF output, often at a fixed frequency that depends on the model. Others need a tap and an attenuator, and the SDR must then be tuned to match that IF. In HDSDR or similar software, CAT synchronization keeps the display centered on the rig's frequency. Check the rig's service documentation and be careful about adding a load to the IF path, because a bad tap can degrade the transceiver's performance. The other approach is a standalone bandscope: a second receiver, often an SDRplay or Airspy, on a separate antenna or a splitter. This is easier and safer since it does not touch the main radio, but the display and the rig's actual reception will not be identical because the antennas and filtering differ. A splitter also costs about 3 dB per leg, so check whether that matters at your noise level. One last point on dynamic range: a wide span is not free. Showing 10 MHz of spectrum at once means every strong signal in that span reaches the ADC. If you only need a 200 kHz slice of the 40 m band, a band-pass filter ahead of the SDR will usually improve the picture more than any software setting will. Filters are also the main cure for FM broadcast overload on VHF and UHF.
  13. On the logging side, the common mistake is mixing up the two references or leaving the WWFF reference out of the exported file. Before you go, do a test export from your logging program and open the ADIF in a text editor. Look at MY_SIG and MY_SIG_INFO for your own reference and SIG and SIG_INFO for hunter references. If one program wants the park in a different field than the other, you may need separate exports or a small edit before you upload. It also helps to confirm the exact reference and boundary before you leave home. Parks can have more than one reference, or a POTA park may cover a larger area than the matching WWFF reference. Look at the WWFF map or description and make sure your operating spot is inside the boundary. A parking lot at the entrance isn't always inside. Finally, expect hunter behavior to differ from POTA. WWFF activity varies by region and time of day. Some areas have active hunters and others are quiet, so don't be discouraged if the first 20 contacts are slow. A steady CQ with your reference said clearly, plus a spot, usually pays off over time. For anything that affects the validity of the activation or the diploma, trust the official WWFF rules over forum summaries.
  14. On net control: the main job is keeping the net orderly, not showing off operating skill. A few habits make a big difference. Announce the net's name, purpose, and any rules at the start. Keep a written or digital log as stations check in, and read back call signs in order so nobody gets skipped. If you can't copy a call sign, ask for a repeat with phonetics rather than guessing. For larger nets, calling check-ins by call sign suffix or region can reduce the pile-up. It also helps to have an alternate net control ready in case propagation or the primary operator's station drops out. For newcomers, it's perfectly fine to say you're new to the net. Most operators will appreciate a clear call sign and a short statement more than a long introduction. If you're a mobile or portable station, mention it, since some nets give priority to stations with limited time or poor conditions.
  15. On skeds, a few habits save a lot of failed attempts. First, work out the mutual window: both stations must have the Moon above their usable elevation at the same time, and the useful part is often much shorter than the Moon's time above the horizon at either end. Second, agree on the band, mode and submode, the frequency, the Doppler convention, and which station uses the first period. Don't leave those to be sorted out on the air, because mismatched periods waste whole minutes. Third, agree what to do if one side doesn't hear the other, such as repeating a fixed number of cycles and then moving to the next sked. For Doppler, set the software to the same convention. Doppler shift is in the hundreds of Hz on 2 m, several kHz on 23 cm and tens of kHz on 10 GHz, and a mismatch of a few hundred Hz may be larger than the decode range. Many operators transmit with their own Doppler pre-correction in the WSJT-X controls so that the partner hears them on the nominal frequency, and the Echo tool provides a good test to confirm that the correction is right before the sked starts. On the Q65 and JT65 choice, the decision often comes down to what your partner is running. Q65 offers advantages when there is a lot of spread or fading, and it has useful averaging features, but if the other station only has JT65 then that settles it. Large stations may also still use CW at a high enough signal level. For your first few schedules, pick a larger station with a well-known signal, since this tests your chain from the receive side before you have to prove your transmit side. Finally, for the Moon-tracking side, trust the software but verify the pointing with the Sun or Moon noise, and keep a log of any azimuth and elevation offsets. On a dish for 10 GHz an error of a fraction of a degree will cost you the whole path.
  16. Agree that the IC-705 belongs in a different category. It can cover 144 and 430 MHz, but its main appeal is portable HF, and you need an HF antenna setup to benefit from it. If your goal is a handheld to carry at an event or on a hike, it's probably the wrong shape. The ID-52A and TH-D75 are more interesting when digital voice or position features are part of your plan. Before paying for either, look at your area. Is there an active D-STAR repeater or a way to reach a reflector or hotspot? And do you need APRS or GPS features? If not, much of what you pay for will go unused. The TH-D75 also covers 220 MHz, but that only helps if 220 activity exists near you. For emergency use, I'd keep two things simple: a written list of simplex and repeater frequencies, and charged spare power. A radio with many modes is no help if nobody on your team can operate it quickly, so choose the one your group can all use the same way.
  17. The mistake I see recommended most often, and which is actually harmful, is "just keep calling." If you call constantly, you never hear what he is doing. Call, then listen. If he is working stations by a pattern, such as the same call area, the same continent, or a particular tone, wait for your turn rather than calling out of sequence. For FT8 and DXpedition modes, the same principle applies with different mechanics. Follow the operator's published instructions, use Hound mode if the expedition specifies Fox/Hound, and don't call on the Fox's transmit frequency. Don't keep retrying forever if you aren't being decoded. Check your clock sync, your power, and your audio level first, because an overdriven signal that splatters is a common reason for not getting through. One more thing about the spots: before you chase a new spot, check whether it has actually been confirmed by more than one source, and read the comment for "up," "down," or a listening window.
  18. For me ergonomics beats almost everything else. A radio with slightly worse numbers but a good layout will get used more than a technically better one that fights you every time you want to change something. If I have to open a menu just to change a filter bandwidth, I'm less likely to bother, and then I'm not really using the radio's capability anyway. On vintage gear, I'd say the money-pit line is crossed when you can't tell what's actually wrong. Replacing known-aging parts like capacitors and cleaning switches and pots is one thing. Chasing an intermittent fault with no schematic and no service notes is where the fun usually stops. Condition and documentation matter more than the badge on the front panel. For listings, I want to see the back panel, the label with the serial number, and some mention of whether it's been modified. Mods aren't automatically bad, but undocumented ones are a red flag.
  19. I'd put power wiring and noise at the top of the list, since they affect nearly every setup. For a mobile or base rig, check the supply voltage while transmitting, not just at idle. A thin wire or a poor crimp can make a good rig sound weak. Powerpole connectors, proper fusing, and a short, thick DC run are not glamorous, but they prevent more problems than most internal mods. On filters, I'd be a bit cautious about buying one just because it's available. First work out what is overloading the receiver. If it's FM broadcast, a broadcast-reject filter makes sense. If it's a local transmitter on a nearby band, a bandpass filter or a better antenna placement may be more useful. For fans, I'd choose a quiet one, power it from a switched or filtered source, and test for added noise on the bands you use before closing the case. For firmware, read the release notes and the user reports for your exact hardware revision. A newer version isn't automatically better, and a fix for one feature can change something else you depend on.
  20. For me the key idea is keeping a single log as the source of truth and treating every award program as a report generated from it. The details that cause trouble are the ones in the QSO record itself: the exact UTC date and time, the band and mode, the callsign as the other station actually used it, and the DXCC entity assigned. If the entity is wrong in your log, every downstream count is wrong too. On deleted entities, date matters. DXCC rules look at when the QSO happened relative to the entity's valid period, so a deleted entity that was valid on the QSO date can still count toward the main DXCC listing, but it will not help the Honor Roll. Keep a separate view of current-only entities so you can see what you actually need. Logging software with a regularly updated country file helps, but check any odd result against the official ARRL entity list instead of trusting the software blindly. For WAZ, don't assume zones follow entities. A few entities span more than one zone, and for those the station's actual location decides the zone, not the entity default. For big countries like the US, Canada, Russia, and a few others, a log that stores the zone per QSO saves a lot of confusion.
  21. Linking deserves its own etiquette section, because each system works differently and users sometimes assume they are all the same. EchoLink is a voice-over-IP system. Licensed users are validated and connect to nodes and repeaters over the internet, so a connected repeater may carry audio from far outside your local coverage. IRLP and AllStarLink also tie repeaters to internet-based nodes. Each has its own commands, often sent as DTMF, and its own node numbering. Never send a command you don't understand on a linked repeater, because you may drop a link someone else wants or connect to a net already in progress. If a repeater's page lists a link schedule or command rules, follow them. Digital repeaters add more settings. Wires-X uses Yaesu System Fusion, with connections made to nodes and rooms. DMR uses time slots, colour codes and talkgroups, and your radio needs a DMR ID and a correctly programmed contact and channel list. Programming the wrong talkgroup, or keying up on a busy one, is a common mistake. D-STAR relies on callsign routing fields and reflectors, so the MYCALL, UR, RPT1 and RPT2 fields need to be right. For all of these, read the network's or repeater owner's instructions. Many networks provide a test talkgroup or echo function, so check before you transmit into a busy group. On open versus closed: an open repeater is available to any licensed amateur who follows the rules. A closed repeater limits access to members, who may be given a tone or code. Don't treat a published tone as permission to use a closed system. Directories such as RepeaterBook and club pages usually say whether a system is open or closed, but entries can be out of date, so confirm tone, offset and status with the club or owner. Coordination bodies and national societies also keep lists and help resolve interference, and many repeaters are funded by dues. If you use one often, joining the club that supports it is a sensible way to repay the owners.
  22. Adding to the packet and message-handling side. For packet, Winlink Express can talk to a hardware KISS TNC, to some TNC-specific interfaces, or to AGWPE-compatible software. Dire Wolf is a common software TNC for the sound card, and it exposes an AGW and a KISS port you can point Winlink Express at. Check the baud rate matches the gateway. A lot of VHF packet is 1200 baud AFSK, and some places run 9600. Many gateways use an SSID like -10, but don't assume that. Copy the call exactly as listed in the channel selector, including any digipeater path if the gateway needs one. Don't skip P2P. A peer-to-peer session uses the same modems (packet, VARA, ARDOP, Pactor) but connects directly to another station instead of an RMS gateway, so it works when no gateway is reachable. Set up one station to listen and the other to call, using the P2P session types in Winlink Express, and make sure the listener is actually in the listening mode before you start debugging audio. There is also Telnet P2P for local network exchange, which is useful for testing and for a served-agency location with no internet gateway. Radio-only needs a clear explanation for a team, because it's easy to misread. A message marked radio-only is meant to travel only over radio paths and not be delivered through internet-based routes. That's useful when you want a message to prove the radio path or when an agency doesn't want the content moving over the internet. The trade-off is that it may not be retrievable the way a normal message is, so don't mark routine traffic that way without a reason. For forms, the ICS-213 General Message is part of the standard templates in Winlink Express. The form opens in a browser, you fill it in, and when you submit it, the data goes into the message. Keep templates updated before an exercise, because a mismatch can make the sender's form look different from what the recipient sees. A short, plain-text description of the key content in the message body is also worth adding. On message size, keep HF messages small. Skip photos, big PDFs and anything else that eats up airtime. If the content isn't needed, don't attach it. For messages to a normal internet address, use the SMTP: prefix in the To field when needed. Internet senders replying to a Winlink address may be filtered, which is why the subject prefix //WL2K is sometimes used. That's worth testing before you rely on it. For Winlink Wednesday, I'd confirm the current details with the organizer or the group running it, since I can't verify a schedule from here. As a drill, a good one is a short check-in message using the radio mode you actually plan to use in an emergency. Record which gateway you reached, the mode, the time and any errors. That log gives you the real list of what works from your location.
  23. until

    A free online Technician license course held on four Sundays (Jan 3, 10, 17 and 24, 2027), 6:00-9:00 pm Eastern, by Zoom only. The class prepares students for the Technician exam, the first of three license levels.Location: Online via Zoom (no physical venue) Organizer: NESCITech Source: Event information
  24. I'd start with FM, mostly because it teaches pass geometry without needing CAT control or a full-duplex rig. Look up the pass, note AOS and LOS, the maximum elevation, and which direction the satellite approaches from. Then practice just hearing the downlink before you transmit. Plenty of people find that after a pass or two of listening, the Doppler on 70 cm makes sense. The signal is high at AOS and slides lower, and you need to follow it. On the handheld-Yagi question, a few habits help. Point the boom at the satellite rather than toward where it is on the map. Use the elevation as well as the azimuth, because the main lobe of a 3-element Yagi is not wide. If the signal fades up and down, try rotating the antenna about its boom axis a quarter turn. Linear polarization against a spinning or tumbling satellite antenna will not always give a stable signal, so you have to tolerate some QSB. Also use a headset or earphone if you're running full duplex. Hearing your own downlink in a speaker can feed back into the handheld's microphone. For TLEs, update them before every operating session if you can, not once a month. It takes seconds and avoids "the pass was ten degrees off" confusion.
  25. Starting with FM is a good call. It teaches you pass timing, antenna pointing and half-duplex discipline without the extra variable of SSB tuning. On Doppler: at 435 MHz, a LEO satellite's radial motion can shift the frequency by roughly ±10 kHz over a pass. At 145 MHz it's about a third of that, around ±3 to 3.5 kHz. FM voice has a lot of tolerance on paper, but that's enough drift to make you miss the satellite's receiver passband if you ignore it. The usual approach for FM is to tune the 70 cm side in steps (or let software do it) and keep the 2 m side fixed, or split the correction between the two. Gpredict and SatPC32 will both show the corrected uplink and downlink for the current moment, and both can drive a radio over CAT if you want to automate it. For a first pass, manual stepping with a printed pass sheet is fine. For the FM birds, check the current setup before each attempt. Several of them use a CTCSS tone on the uplink to open the transponder, and the tones and frequencies can differ per satellite, so verify rather than assume. The commonly cited arrangement for SO-50 is a short arming tone followed by a regular tone, and AO-91/AO-92 use a continuous tone, but again, confirm them on the AMSAT pages for the date you're operating. Also, an FM satellite is a single channel, so keep it short: callsign, grid, signal report if there's room. A longer chat just blocks the next person. As for the antenna, a handheld dual-band Yagi works fine. The main skill is pointing it at the satellite while keeping the radio, the antenna and the pass sheet manageable. A homebuilt 2 m / 70 cm Yagi is a reasonable project too, but a cross-polarization mismatch or an unexpected feedline loss can hide in a DIY antenna. If your first attempts fail, you'll want to know whether it's the antenna or the technique. A tape measure and an SWR/return-loss check on both bands will tell you a lot. The ISS APRS is a good low-pressure test. A packet digipeated through the ISS at 145.825 MHz proves your receive chain, Doppler handling and antenna pointing without needing a QSO partner. It's less useful for voice practice, though, because the crossband repeater is only on at certain times. You'll want to look up the current ISS amateur radio status before planning around it.

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.