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_Mike

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Mike

  1. I'd add the information side: DX cluster, spots and logs. A spot is a clue, not proof. Spots can be busted or posted for the wrong call, so before you spend effort on a new frequency, confirm by listening that the station is really there. Skimmer-generated spots, such as those from the Reverse Beacon Network, show where something was heard, but they don't tell you whether the DX is split or whether it's workable at your location. And please don't clog the cluster with spots of yourself or with chatter. Keep spots accurate and short. Club Log is useful both before and during an operation. Its ranking and most-wanted tools help you see which entities you need and which are scarce for your own log, and many DXpeditions upload logs frequently so you can check whether you made it in. If your QSO isn't showing yet, be patient. Don't keep calling just to be sure. Duplicate QSOs waste time that someone else needs. Most teams will tell you how they handle QSL, whether by LoTW, Club Log's OQRS, or something else, so read the official page instead of asking on the frequency. One counterpoint to the idea that the answer is always "be patient and wait". Sometimes the operator tells you what he wants and the pile keeps ignoring it, for example by calling out of the announced window or when the DX is clearly calling someone else. The most useful etiquette is also the simplest: listen more than you transmit, don't call over the DX, don't ask "where is he listening?" on the frequency, and don't answer "QRZ?" with a blind guess. From the DXpedition side, a well-planned operation helps by publishing band plans, operating times and the split in advance, but no one can fix a pileup that won't follow instructions.
  2. I'd keep your order but move the low-pass filter earlier, ahead of any transmitter you build, since a lot of simple transmitters, including Tuna Tin 2-style crystal oscillators and Pixie-like designs, are not clean outputs. A single-transistor stage running into a resonant output network can still carry substantial harmonic energy. The filter fixes a lot, but you still have to verify the result. For test gear, a NanoVNA-type instrument is probably the best value for filters, antennas and return loss. It's less useful for looking at your transmitter's output spectrum unless you add a suitable attenuator and know what you're doing, because plugging a transmitter into a VNA port can damage it. Use a dummy load and a proper attenuator chain, or use a different method altogether. For checking harmonics without a spectrum analyzer, a common trick is to listen on a separate receiver tuned to the second and third harmonic frequencies, with the transmitter into a dummy load and a short sample of the signal. It's crude, but it tells you whether there's a problem. A scope is more general-purpose than a counter. A counter is nice for setting up a VFO or crystal oscillator, but a scope will also show you audio, keying waveforms, supply ripple and DC problems.
  3. The first thing worth doing with that kind of lot is model it, even roughly. Free versions of NEC-based programs will show you the effect of height, the inverted-V angle, and ground type, and the results are often surprising. A 40 m wire at 30 ft and a 40 m wire at 45 ft can have noticeably different take-off angles, and the feedpoint impedance changes too. Neither one is wrong, but you want to know what you are getting. With two trees at 40 ft and a 30 ft support, a doublet would be hard to beat in terms of flexibility. Run it as an inverted V or a sloper, bring ladder line down, and let a balanced tuner or a good 4:1 balun and tuner combination handle the rest. The ladder line goes through a window or a gap in the wall, and the main nuisance is routing it cleanly. If that is impractical, an EFHW run as a sloping wire is the easier physical install, but it is the one most likely to need a good feedline choke, because the coax shield is acting as the counterpoise. One thing that gets missed: the choke is more important than the transformer ratio. Whatever you pick, measure SWR with the transmitter and then check if the SWR changes when you move the coax or touch it. If it does, you have common-mode current.
  4. On Mode A versus Mode B: it often comes down to what you learned on. If you're having trouble, the fix is rarely a change of mode alone. Slow the keyer down a few WPM and watch your squeeze timing. Many operators release the squeeze a hair too early or too late, which shows up as an extra element. Recording yourself and playing it back, or sending to a decoder, can reveal spacing problems that your ear misses while you're sending. For prosigns, remember that they are sent as one character with no gap: AR (·−·−·) ends a message, SK (···−·−) ends a contact, KN (−·−−·) means go ahead, only the station named, and BT (−···−) is a pause or separator. Send them as one smooth unit, not as two letters, or the other station may copy something different. I would keep abbreviations simple on the air too. TU, UR, PSE, and AGN are all widely understood, but a wall of Q-signals and clipped shorthand can make you harder to copy, especially for newer operators.
  5. I'd argue the best keeper is the one that makes you want to turn it on. That's an unscientific test, but it works. A rig with great specs that sits unused isn't a keeper, and a quirky old transceiver that gets daily use is. On the modern side, ergonomics matter more than people expect. The audio, the filter controls, the ability to see the band, and how quickly you can reach a setting all affect whether you operate or just fiddle. SDRs have made strong receivers much more affordable, but a lot of people still keep a simple analog-feeling rig around for casual listening. On the classifieds side, some advice for anyone selling or trading: post clear photos of the front, back and any labels, and state honestly what works and what doesn't. Mention any modifications, and say whether the rig has been recapped or aligned. Heavy tube gear is expensive to ship, so many sellers prefer local pickup or a hamfest. Hamfests are also good for judging a rig in person before you buy it.
  6. I'd put log formatting near the top, especially for two-fers and roves. People tend to focus on getting to 10 QSOs and forget that the log needs the right park reference or references in each record. If your logger has a POTA field or mode, test it at home with a few dummy entries and export the ADIF before you leave. That way you aren't discovering a field problem on a picnic table. For roves, keep each park's log separate unless the current instructions say otherwise, and note the time you moved. It makes cleanup much easier, and it helps with the UTC date if you cross the boundary.
  7. For the low bands the main difference is that your receive capability matters as much as your transmit capability. A rare-DX operator on 160 or 80 m might be hearing you with a lot of QRN, and you may be hearing him on a Beverage or other receive antenna while barely audible on your TX antenna. The result is a signal you can hear but he can't hear back. It can also work the other way around if your local noise is high. If you're hearing him well but not getting through, consider whether your TX antenna is the weak part of the system. Grayline and sunrise/sunset timing at both ends are critical. A signal that is workable for 15 or 20 minutes at the right time may be gone afterward. If you know the DX's sunrise or sunset, you can plan your time on the air and avoid wasting effort when the path isn't open. For 160 m, remember the common DX window (roughly 1830–1840 kHz) and check how the operator is using split. Don't assume it's the same as on 20 m. On the planning side, Clipperton and Bouvet are different kinds of problem. Clipperton is an atoll with difficult landing conditions and limited shelter, and Bouvet is a remote, ice-covered island with very hard access. Both depend on ships, weather windows and permits, so operators have to decide in advance what they'll sacrifice if conditions go wrong. Typically that means deciding which bands and modes get priority, how many stations can run at once, and how to share power and antenna space. For chasers the practical advice is to check the official DXpedition site for the announced plan, listen for the actual operating pattern, and avoid trusting unverified spots or social-media posts about the callsign or QSL route.
  8. My rule of thumb is to default to the ITU words and improvise only as a repair tool. If someone keeps getting one letter wrong, switching to a different word for that letter is legitimate. Say "M as in Mike" the first time, and if it still doesn't copy, try a clearly different word. The point is to change what the ear receives, not to be clever. The trouble with freelance phonetics is that a listener has to decode the word and then map it back to a letter. If you say "Kilowatt" for K, a weak-signal listener may hear only "-watt" and wonder whether you meant W. Your own favorites also vary a lot by region and generation, so a word that is obvious to you may be a coin flip for a DX station. Words that sound alike are the worst offenders, such as "Mexico" and "Texas" in noise, or "Nancy" and "Mary" when the consonants are masked. For delivery, a few habits make the standard alphabet more effective. Keep a steady, slightly slower pace. Give each word its natural stress, like KEY-loh, LEE-mah, keh-BECK and pah-PAH. Pause briefly between the prefix, the number and the suffix. For example, with a US-style call, say the prefix letters, the digit, then the suffix as separate chunks. Then repeat the whole callsign once at a measured pace rather than rattling it off faster the second time.
  9. I'd start by looking at what's actually on the air near you, not at the feature list. Use a repeater directory and check whether there are D-STAR or DMR repeaters in range, and whether local clubs or nets use them. If everything within 30 miles is analog FM, an FT-65R-class radio covers the practical needs and leaves money for an extra battery and a better antenna. If a D-STAR or DMR network is active nearby, the ID-52A or TH-D75 starts to make sense, though DMR on a cheaper dedicated radio can be a lower-cost way to try it. On the Baofeng question, I wouldn't call it a bad choice for a learner, but I'd treat it as a low-cost tool rather than a primary radio. Receiver selectivity and transmit cleanliness are the usual weak spots on very cheap sets. In a crowded RF environment you may notice more overload from nearby pagers or commercial transmitters. If budget is the limit, buy it, learn on it, and upgrade later once you know what you need.
  10. I'll take the first four. The rules are in 47 CFR 97.119 (ID), 97.115 (third-party), 97.313 (power) and 97.113 (prohibited transmissions). Station ID: give your FCC-issued call sign at the end of each communication and at least every 10 minutes during a communication. On phone, the ID is in English. On CW or digital, you identify using that same type of emission. Phonetics are optional, though they help copy. A tactical call like "Net Control" or "Shelter 2" does not replace your call sign. You can use one, but you still have to ID with your real call at the required intervals. You may add a location indicator after the call, but it isn't required. The 10-minute clock is about your transmissions, so if you're in a long roundtable, ID on a timer. Repeaters have their own ID obligation, and that doesn't cover the users. Each station that transmits through the repeater still has to ID. Third-party traffic: a third party is anyone other than you and the station you're talking to. A non-ham can talk on your station as long as a properly licensed control operator is present at the control point, monitoring and ready to stop the transmission. Domestic third-party traffic is generally fine, as long as the content is itself permitted. International is the catch. Third-party communications with another country are allowed only if the US has a third-party agreement with that country, or under a limited exception such as the third party being a licensed amateur eligible to be a control operator. The same section also covers when you must ID in international contacts. Don't assume that a friendly QSO with a foreign station means you can pass a non-ham to the mic. Check the current list. Power: the ceiling is 1,500 watts PEP output from the transmitter or amplifier, and it applies to output, not ERP, so antenna gain doesn't count against that figure on most bands. Several exceptions apply. 30 m is limited to 200 W PEP, and Technician privileges on the HF segments are 200 W PEP. 60 m uses a different ERP/EIRP-based structure, so read the current text before operating there. A few areas near radiolocation sites have lower 70 cm limits. Separate from the numeric limit, 97.313 also requires using the minimum power necessary to carry out the communication, which people forget when they run an amp barefoot-capable. Prohibited transmissions: the usual ones are communications for compensation or in which you or your employer have a pecuniary interest, with narrow exceptions (for example, a teacher being paid incidentally for classroom use, or occasional sale of your own amateur equipment). Others are broadcasting, music, obscene or indecent language, false or deceptive signals, and messages encoded to obscure their meaning. That last one is why "it's encrypted for privacy" doesn't work on amateur bands. Open protocols are fine, and control links are a limited, separate case. Willful or malicious interference is also prohibited. Safety-of-life emergencies have their own provision in Subpart E, but it isn't a blanket license for routine rule bending.
  11. On the antenna side, test the noise before spending money. Compare the noise floor with the antenna connected and with a terminator on the input. If connecting the antenna only lifts the floor by a couple of dB at HF, the band is probably quiet and your system is receiver-limited. If it lifts it by 20 dB or more, local noise or strong signals dominate, so a quieter location or a better-placed antenna is the fix. Moving the antenna away from switching supplies, LED lighting and the PC can help more than a more sensitive receiver. The panadapter point is also important. Splitting RF from a transmitting antenna into an SDR input without proper protection is a good way to damage a receiver. An IF tap or a dedicated receive-only path is much safer, and it is worth checking the level, because the IF output of some radios is too hot for dongles without attenuation. For decoding, keep the signal path simple. Check the SDR software's demodulator bandwidth, then the virtual audio cable level, then the decoder's own settings. Many audio-related failures are just an overdriven or underdriven audio level between those stages, and not a problem with the radio at all.
  12. I would put live spots first and the indices second, mostly because the indices are averaged or lagging. K is a 3-hour value, and A is a daily summary, so neither shows a sudden change well. If PSK Reporter or WSPR shows your band active toward the target region, that beats any prediction. The indices then help explain why. For example, a good SFI with a high K points to a geomagnetic problem, while a suddenly dead daytime band after a flare points to D-layer absorption. One caution on the WSPR map: it reflects the antennas, power and receivers of the stations that happen to be active. A path that looks closed may just have no one listening on it. Querying by band and time window, and including your own transmissions if you can run a few hundred milliwatts to a few watts, makes the data much more useful than a quick glance at the map. The NCDXF beacons are underrated for a quick check. Within a 3-minute cycle you can hear which beacons are audible on 20m, then step to 15m and 10m. The same beacon is sent at decreasing power levels, so you also get a rough sense of how marginal a path is. It won't tell you whether a rare station is workable, but it tells you quickly whether the band is open at all.
  13. On the vertical side, the thing I'd add is that 'a vertical needs radials' is true, but the number of radials depends on how they're laid. On or just under the ground, you want many, and the gain from going from 4 to 16 to 32 is real. Raised radials are different: a handful of resonant ones at a few feet up will often outperform dozens of short buried ones for the same effort, and they're easier to hide at the edge of a small yard. If the HOA is the issue, a thin vertical wire on a fiberglass pole can disappear against a tree line, with the radials running along a fence line at ankle height. On the loop, I'd push back slightly on 'quiet on receive means good.' A small loop's lower noise can make weak signals more readable even when it is 10 dB or more down on a full-size dipole in transmit efficiency. That is fine for monitoring, but for transmit you still care about the efficiency numbers: loop diameter relative to wavelength, conductor diameter, and capacitor losses. A 1 m loop on 40m is a very different animal from the same loop on 15m. The test I'd suggest, if you want a real comparison instead of anecdotes, is to record several known stations, such as WSPR spots or a beacon, on both antennas at the same time and compare SNR over a few days. A single A/B at a single time of day tells you very little.
  14. The protection circuit is worth ruling out before you condemn the finals. Many rigs reduce power when the SWR or reflected-power detector reports a mismatch. If the rig still folds back into a good dummy load, suspect the detector rather than the antenna system. Look at the bridge diodes, the trimmer or calibration pots, the op-amp or comparator stage, and any filter capacitors on the sense line. A leaky diode or a dirty trimmer can fake a high-SWR condition. Do the same check in reverse: if the rig makes full power into a deliberately bad load and doesn't protect itself, the detector may be dead, and that is how a PA gets destroyed. If the finals really are blown, treat that as a symptom and not the whole fault. Common causes include high SWR, overdrive, supply overvoltage, bias runaway, a parasitic oscillation and a failed driver stage. Before fitting a new transistor, check the bias network for open resistors, a failed thermal-tracking device and a damaged bias preset. Look at the drive level and the output filter too. Then bring the rig up on a current-limited supply, set the idle current as the manual specifies, and watch it on a dummy load. Use the correct part or a properly matched replacement, because "close enough" RF transistors often have different gain, capacitance and ruggedness. On alignment, it's tempting to touch the slugs when power is low or receive is deaf. Don't, until you've verified the basics. Mark the original positions, use the manual's procedure and test points, and make sure you have the right gear: a signal generator, a counter, a power meter and a dummy load. Many "misaligned" rigs turn out to have a bad component, and re-tuning around it only hides the fault.
  15. I would add that traps and verticals are where model-versus-reality gaps get biggest. A trap dipole shortens overall length compared with a full-size wire, but each trap adds loss and narrows bandwidth, so the antenna is rarely as efficient as a simple full-size dipole on its fundamental band. If you want multiband without traps, a fan dipole or a linked dipole is easier to build, though spacing between the fan elements interacts and needs trimming in sequence, from the highest band down. For verticals, the radial system matters more than the radiator. A ground-mounted quarter-wave vertical typically needs a lot of radials (a few dozen is better than a few) because ground loss dominates efficiency. Elevated radials can work with far fewer, often two to four tuned ones per band, and with the radials sloping downward the feedpoint impedance moves toward 50 ohms. A choke at the base is still worth adding, since the coax can act as an extra radial.
  16. One thing that helps is a one-page activation plan that states plainly who can call out the group and under what authority. If the county emergency manager activates RACES, members should know that's a government tasking, so they check in through the designated channel and follow the EOC's direction. If the EC activates ARES for a served agency like a shelter or hospital, that's a different chain. Writing it down means nobody has to guess in the first hour. For net control, the habits that matter most are simple. Keep a running log of check-ins, separate emergency and priority traffic from routine, and use tactical call signs for locations ("Shelter One," "EOC") so that traffic isn't tied to whoever happens to be on the mic. Don't forget that Part 97 station identification with your actual call sign still applies, so build the ID reminder into your net script.
  17. One way to keep things sane is to treat the logs by role. The contest logger is the authority for the contest period. WSJT-X is just a decoder with a scratch log. The master log gets a clean import afterwards. For CAT, a single program should own the physical port, and everything else should connect through a shared layer. N1MM+ can handle radio control itself, but if WSJT-X also needs to key the rig or set frequency, then one of them has to give up its direct port, or you have to use a rig-control middleman. Make sure the baud rate, split mode and data mode (USB-D or DATA) are set consistently, or the band map will show confusing frequencies. After the contest, I'd export ADIF from the contest logger rather than converting from Cabrillo. Cabrillo drops information such as full frequency precision and fields the sponsor doesn't care about. Import the ADIF into the master log into a test copy first, scan for oddities (mode, submode, band, operator, and your own grid), then do the real merge. After that, upload to LoTW, QRZ and Club Log from the master log only, so you have one place where the upload status is recorded.
  18. One addition on directories and access. Treat any directory as a lead, not a guarantee. A listing may show the right frequency and offset while the tone is wrong or the machine has been changed to closed or limited access. If the entry doesn't list a tone, check the club page or ask on the club's net or social channel before hammering the input. It's polite and it saves you guessing. For the timer question, I'd skip the jargon with newcomers and just say: pause between transmissions long enough that someone else could jump in, and don't hold the mic through a long monologue. The courtesy tone is a hint, but not every repeater has one, and some use it as a timer reset, others as a delay signal. Better to teach the habit than the beep. I'd also add a note on tones and security: the tone just keeps unwanted signals out, so don't say anything on a repeater you wouldn't want overheard. And if the repeater is coordinated, the coordinator's database is often the most reliable place to confirm the pair, though you still need to confirm the access method with the owner.
  19. For a first station I would separate the problems. First, make sure you can hear the bird. Use a pass prediction with a decent maximum elevation, ideally one that is not too low on the horizon, and spend a few passes only receiving. That tells you whether your pointing, polarization handling and receive chain are working before you add transmit complications. The most common FM mistake is probably the uplink tone or the uplink frequency, not the antenna. If a satellite needs a CTCSS tone for access, you have to set it correctly on the transmit side. A lot of people also forget to correct for uplink Doppler. The downlink shift is more obvious because you hear it, but the satellite hears your uplink offset too. A small mismatch can mean the satellite hears you weakly or not at all. With an Arrow, a duplexer and an HT, take care with cable routing and the way you hold the antenna. Body proximity and cable pickup can distort the pattern. Rotating the antenna slightly can matter as much as aiming exactly at the satellite.
  20. I'd add something for the receiver side, especially a direct conversion receiver. Once the transmit side works, check for AM broadcast breakthrough, hum and microphonics. A simple direct conversion receiver with a diode ring or NE602 mixer and no RF selectivity can pick up strong out-of-band stations. If you hear broadcast audio on top of everything, a band-pass filter or at least a low-pass or high-pass section ahead of the mixer often helps. Power supply noise matters a lot here too. A cheap switching wall adapter can put birdies or a buzz across the band. Try running the receiver from a battery as a test. If the noise disappears, you have found the cause. Then you can add ferrite chokes and bypass capacitors on the supply line, or move to a linear regulator. For testing sensitivity without a signal generator, a crystal oscillator with a long attenuator chain or a very short wire coupling can give you a repeatable weak signal. It won't be a calibrated measurement, but it is enough to tell whether a change to the audio gain or mixer bias helped.
  21. For a first radio I'd lean toward a plain analog dual-bander with a good aftermarket antenna. The FT-65R is a reasonable pick because the menus are simple, it covers 2 m and 70 cm, and the manual makes it easy to find out what a function does. You can learn offsets, tones, simplex and repeater etiquette without also learning talkgroups or reflectors. The Baofeng route can work too, especially if the budget is tight. Buy from a reputable seller, verify CHIRP support for your exact model, and understand that cheap radios can have weaker front ends in crowded RF environments. If you operate near strong transmitters you may notice desense or intermod. That is often worth knowing before you decide a radio is faulty. On digital, I'd check the local network before buying. A D-STAR or DMR handheld is only useful if you have repeaters, a hotspot, or a group using it. Otherwise it spends most of its time as an analog FM radio.
  22. Preparation is a big part of this. If you use Club Log, check your needs for the entity by band and mode before the operation starts, and decide which slots are actually worth your time. A Most Wanted list can help you rank targets, but it shows a snapshot of what other users have worked, so check the current version and don't treat it as a fixed order. Online log search from the team, where available, is also worth using for your own contacts. Check it before you call again for a dupe, because every extra call you make for a QSO you already have costs time for someone who needs it. A dupe at the end of a long band opening is not harmless. For the target itself, remember what makes places like Clipperton and Bouvet hard. Clipperton is an uninhabited French possession in the eastern Pacific, and Bouvet is a remote Norwegian subantarctic island. Both have difficult landing conditions, limited time on site, weather risk and tough power and antenna logistics. That means the operating plan can change quickly, with bands or modes dropped or added depending on conditions. If you want to be ready, watch the team's own updates rather than relying on forum rumors, and leave room in your schedule for the first few days, when the operators typically have the most gear running. For FT8 operations that use a DXpedition mode, read the team's instructions carefully. Fox/Hound mode in WSJT-X is the standard example. Hounds call at a different frequency than the Fox transmits, and the Fox answers in a different way than normal, so the usual call-and-reply sequence doesn't apply. Using the wrong settings can make you invisible to the Fox or put you in the way of other callers. On etiquette: if you can't hear the DX station, don't call. If you think you are the only one hearing him, wait, listen and look for confirmation. Don't tune up on his frequency. Don't answer him on his transmit frequency if the operation is split. And if someone is plainly on the wrong frequency, a short note on the cluster or a single clear message is better than starting an argument on the air.
  23. My first check is the directory entry, followed by listening for a few minutes. The entry should give the output frequency, offset direction, and access tone. Then I check whether the repeater has a separate tone for receiving, because some systems transmit a different tone than they require. If your radio has a reverse function, it lets you listen on the input frequency to see whether you can hear stations directly. That tells you whether you need the repeater at all. On tones, the common mistake is mixing up "Tone" and "TSQL." If you set TSQL and the repeater does not send the same tone you chose, you will hear nothing and think the repeater is dead. Start with encode-only, confirm you can key it, and then turn on tone squelch if you want to cut out interference. For etiquette on analog repeaters, leave a short pause between transmissions so others can break in, and keep your overs short so you do not hit the time-out timer. Identify as your license requires. Most of this is just listening before talking.
  24. For a first summit, I would pick one with an easy trail, a clear activation zone and decent phone or spotting options, even if the points value is low. The point of the first outing is to learn the workflow, not to stack points. Print or save the summit information offline, because the mountain may have no signal. Note the reference, the approximate activation zone, your turn-around time and a backup operating spot. On the radio side, a simple band plan helps a lot. Decide in advance which band you will try first and what you will do if it is quiet. If you are using HF, 40 m and 20 m are common starting points because they cover a lot of distance and activity. If you are VHF-only, say so in the alert so chasers know what to expect. And do not wait until you are cold and tired to figure out how the spot gets posted.
  25. A useful way to think about it is separating discovery from verification. Cluster spots and POTA/SOTA spots are for discovery. They tell you where to tune, but a spot can have a typo in the callsign or frequency, or be a busted decode. Before calling, listen for the station to ID, or cross-check against the QRZ or HamQTH entry so you know the call and location are plausible. RBN and PSK Reporter are better for verification of your own signal, since they're objective receive reports. If you call CQ on CW and RBN skimmers nearby show you at a decent SNR, that's real data about how your antenna is performing. Just remember skimmers have good receivers and antennas, so being spotted doesn't mean a typical home station can hear you at that level. The same applies to PSK Reporter: if nobody reports you, check that your software is actually uploading spots before blaming propagation. For propagation, the numbers (SFI, K, A) give you a rough idea, but the live maps from PSK Reporter or RBN tell you what's open right now on that band. I'd always trust the live data over the forecast.

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.