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_Nancy

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Nancy

  1. I'd tweak the order a little. On the "clean the contacts" advice, I'd reflow and inspect before spraying anything on a rig that behaves intermittently. Contact cleaner can temporarily cure a symptom and hide a cracked joint or a failing connector that returns later. It's good for dirty switches and pots, but with relays, trimmers and board-to-board connectors, look first and work out which contact is bad. On SWR protection, one useful test is to put a dummy load on and measure the forward and reflected detector voltages at a low, safe power level. A properly terminated load should give a reflected reading near zero. If it doesn't, the bridge or detector is suspect. If the reading is fine at low power but protection trips at higher power, look at the PA output stage, the low-pass filter relays and any component that changes behaviour when heated. In blown-finals cases, check the driver stage and the bias network before you order a matched pair, because replacing the transistors without finding the cause often just repeats the failure.
  2. I'd add something about sending, because it gets less attention than receiving. If you send with a keyer set well above what you can copy, you'll get replies at that speed, and you won't be able to read them. A good rule is to send at or slightly below the speed you can reliably copy. Clean spacing between characters and words matters more than raw speed. A lot of people sound faster than they are because they rush the dits and shorten the gaps, which makes them harder to copy. On decoders, I think the useful distinction is between using one as a crutch and using it as a check. Recording a session, copying it by ear, and then running the audio through software or comparing against a known text tells you where your errors actually are. That's different from watching the screen while you listen, because then you aren't training your ear at all. One practical thing: write down which characters you keep missing. It's usually a short list, often similar-sounding ones like 6/B or sets with the same rhythm, and targeted drills on those pay off faster than general practice.
  3. The legal part deserves emphasis, because the capability and the permission are separate things. Being able to unlock transmit on a frequency doesn't mean you may use it. For MARS or CAP, the safest approach is to work through your organization's guidance on approved radios, programming and assigned frequencies, instead of assuming that a ham radio that can be set up for them is automatically fine. Also, an amateur license doesn't cover other services such as GMRS or business, and those typically have their own equipment rules. Check your own country's regulator if you're not in the US. On the technical side, I'd add one caution about alternative firmware and cheap handhelds: if the firmware changes how the radio transmits, test it on a dummy load first. Harmonics and spurs matter, and a radio that sounds fine on a receiver next to it can still be putting out junk. If you don't have a spectrum analyzer, a club or local test group might have one you can use. And for power mods: fuse close to the battery, use heavy enough wire, and don't rely on thin factory leads for a 50 or 100 W mobile. Voltage drop can show up as distorted audio or odd radio behavior, and it's an easy thing to blame on the radio.
  4. On the older and keyboard modes, which have different problems from WSJT-X: PSK31 and RTTY are still used, and Olivia, MFSK and Hellschreiber have niches of their own. PSK31 runs at 31.25 baud and is very narrow, so even a small amount of ALC distortion makes the signal wider and worse. Many operators keep power low. RTTY at 45.45 baud with a 170 Hz shift is common in contests, and it can be generated by AFSK from a sound card or by FSK keying where the rig supports it. FLDIGI handles these and many more, and it is a better choice than WSJT-X for any conversational mode. Olivia and the MFSK family are built to work in poor conditions with forward error correction. Olivia gives you the option of different tone counts and bandwidths, and both ends must match the settings. Hellschreiber is a different approach: the receiver displays the characters as an image, so you read the text visually instead of relying on a decoder. It tolerates certain kinds of noise well, but it is slow and not suited to precise exchanges. For Winlink, the radio side depends on the gateway. VARA HF/FM, ARDOP, packet and Pactor are all used, with VARA being a separate program with its own license terms. Whichever you choose, set up your sound card interface carefully: separate the audio paths if the rig has a dedicated data port, use isolation, and add ferrite chokes if RF is getting into the USB and audio leads. Most failures with these modes come from the interface level and RF feedback, not from the software.
  5. On packet, the choice between a hardware TNC and Direwolf mostly comes down to how many moving parts you want. A hardware TNC in KISS mode is one box with a serial or USB link, and it keeps working without audio drivers. Direwolf adds a software layer but lets you use the same sound interface you already have. In both cases Winlink Express needs the TNC type and port set correctly, and the callsign and SSID need to match what you intend to use. A common mistake is a mismatch between the KISS port in the software and the one the TNC is actually presenting. Another is leaving the TNC in a mode where it adds its own connection handling, so the gateway session never starts properly. For VHF levels, check the radio's data port deviation too. A TNC that is fed too hot makes a wide, distorted signal, and a gateway several miles out may fail to decode it even though the local monitor sounds fine. Run a test with a nearby station or a gateway you know is reliable before concluding the TNC is bad.
  6. I'd split the pool into "derive it" and "recognize it." Several of the math-flavored questions are short enough to work in your head if you know the relationships behind them. For op amps, an inverting stage has gain of minus Rf over Rin. With a 100k feedback resistor and a 10k input resistor, that's a gain of -10, and the negative sign means 180 degrees of phase inversion. A non-inverting stage is 1 + Rf/Rin, so the same resistors give 11. Once you know both and the virtual-ground idea, you don't need to memorize individual answers. Filter Q is similar. Q equals center frequency divided by bandwidth. A circuit centered on 7.1 MHz with a 71 kHz bandwidth has a Q of 100. A higher Q means a narrower response. FM modulation index is peak deviation divided by modulating frequency, so 3 kHz of deviation with a 1 kHz tone is an index of 3. Things like oscillator names or filter-family characteristics are more recognition. Make a one-line comparison for each: Colpitts uses a capacitive divider, Hartley uses a tapped inductor, Pierce uses a crystal. Chebyshev has ripple in the passband and a steeper skirt, Butterworth is maximally flat, and elliptical has ripple on both sides with the sharpest transition. On the Smith chart, the main points are these: normalize impedance to the line's characteristic impedance, the center of the chart is a perfect match (1 + j0), a circle around the center is constant SWR, and moving once around the whole chart is a half wavelength of line. Toward the generator is clockwise, toward the load is counterclockwise. If you remember those four things, many chart questions become a quick lookup.
  7. From the hunter side, the useful thing to understand is that you don't upload anything for WWFF. Your credit comes from the activator's log. So if you work a KFF station and the QSO doesn't show up, the likely causes are a callsign typo in the activator's log, a wrong date or time, a wrong reference, or the log not being uploaded yet. It's reasonable to give the activator a little time, then politely check whether the QSO is in their log. Don't assume you did something wrong. On the logging side for activators, check your ADIF before upload: reference format (prefix plus number, with the hyphen), UTC date and time, the right band and mode, and your own callsign on every record. Rejected or unmatched QSOs usually come from small formatting errors, not from anything complicated. On spotting, I'd say post to whichever system you want hunters to use and be clear about the reference in the comment. If you're dual-program, say so in the comment, which saves hunters from guessing. Always check the current spotting and logging pages for the program's present rules and tools, since these change over time.
  8. I'd put noise on that list ahead of visibility. In a small residential lot, receive noise from switching supplies, LED lighting and the like can matter more than a dB or two of transmit efficiency. A vertical sits close to those sources and picks up a lot of local noise because it's vertically polarized and low. A horizontal wire or a small loop often has a better signal-to-noise ratio even when its absolute signal is lower. S-meter readings are misleading here, so compare in terms of copyable signals, not signal strength. On the EFHW, the thing that most often causes confusing results is the missing or marginal feedline choke. If the coax shield becomes part of the radiator, the SWR can change when you move the cable, and the shack gets RF in it. A common-mode choke, such as a stack of type 31 ferrite beads or a coiled coax choke with enough turns, is cheap compared to chasing mysteries. Measure the choke's impedance on the bands you care about if you have an analyzer, because a choke that's fine on 20 m can be weak on 80 m. For a typical small lot with two supports, I'd lean toward a doublet or a simple dipole or inverted V with a tuner. They are predictable, easy to model, and cheap to modify. The EFHW is attractive for portable use and for a single support, but it isn't automatically better than a center-fed wire in the same space.
  9. A few notes on the less common modes and on Winlink. JS8Call uses FT8-style modulation but is built for keyboard-style messaging, relays and store-and-forward. It has several speeds (Slow, Normal, Fast and Turbo), and the faster ones trade sensitivity for throughput. That makes it good for casual weak-signal chats and for passing short messages, but it is not a replacement for a proper email system. Winlink is that email system. It is usually used through Winlink Express with a modem such as VARA HF, VARA FM, ARDOP or Pactor, depending on the gateway and the hardware. VARA is a proprietary modem, and the free version is speed-limited, so check the licence terms and what the gateway you plan to use supports. Whatever you choose, test the PTT and audio chain before relying on it for something important. Listen before you transmit, because gateway channels can be busy and a connection attempt can interfere with sessions already in progress. For Q65 and MSK144, it is worth reading the WSJT-X user guide for the specific submode and period before trying them. Q65 with a long period, say 60 seconds on 6 m or 2 m, behaves very differently from FT8 in time and frequency tolerance, and MSK144 depends on accurate time and a good meteor-scatter schedule. Olivia and Hell are best treated as experiments: agree the settings beforehand, start with a strong signal and a known partner, and then try weaker conditions.
  10. On the equipment side, I'd split coverage into three buckets: confirmed products, credible announcements, and rumors. Hamvention and other conventions are good for hands-on looks and talking to manufacturers, but a demo unit isn't a retail unit. Specs, pricing, and shipping timelines can change between the show floor and the first shipments. Early reviews are more useful when they list the firmware version tested, since behavior can shift between releases. For club news and awards, the best sources are usually the organizers' own pages or newsletters. Check the rules for DXCC, POTA, SOTA, or contest awards directly, because details like valid dates, logging requirements, and what counts as a confirmed contact do get updated. Reading the current rule sheet before you chase an award is quicker than learning later that a QSO doesn't qualify. As for hobby trends, I'd watch what people are doing on the air, such as digital modes, portable operating, satellite work, and homebrew antennas, rather than what gets the most clicks. If a trend shows up in activity logs and club meeting topics, it's probably real.
  11. For spotting with weak signal, set up your spot text before you lose service: reference, frequency, mode, and a short comment such as "QRP" or "CW only." If you can't spot at the field, you can ask a friend to do it, or you can start on a calling frequency and let CW or digital skimmers pick you up. Don't rely on that, though. An accurate spot is the single biggest help for hunters. As a hunter, I'd say go ahead and call when the activator is working stations, but listen first. If the activator is running split, only taking the last two letters of a callsign, or on CW only, you'll get through faster by following that pattern. Don't keep sending your call over a QSO in progress. One clean call, then listen. For a two-fer, say both references on the air if you can, but keep it brief. The activator still has to log them correctly, so hunters should be patient if the exchange takes a little longer. And for antennas: a simple, quick-to-deploy wire is a good first-time choice. Setup time counts as operating time, and a rushed, over-complicated station tends to cost more contacts than a small amount of extra power would gain.
  12. For dishes, the part I would not skip is the tracking and calibration side. At 23 cm, a beamwidth of several degrees is forgiving, so small errors in azimuth and elevation do little harm. At 10 GHz, the beam is narrower than the Moon is wide, and a small error in the mount, a sagging dish or a wrongly entered location can drop the signal completely. Since the Moon is a convenient target, many people check pointing by measuring Moon noise or Sun noise with a Y-factor method. Sun noise is a standard way to check system performance and feed alignment before a sked, and you do not need a signal from the other station. Libration matters most on the microwave bands, as mentioned above. On 10 GHz, spreading is wide enough that wider sub-modes may be necessary even with strong signals. For a first microwave attempt, it helps to check the other station's mode and sub-mode before the sked rather than trusting the band's habits. On sked planning, the common window is the thing to compute. Two stations far apart may only share a short stretch of Moon visibility, and the stretch may fall at low elevation for one of them. The same Moon on a day of high sky noise or near apogee can make an otherwise good sked fail. Choosing a time with better declination, lower degradation and, if possible, near perigee does more than adding a few watts. If you plan back-up sked times, put them in the same message, so a failed attempt does not need another round of coordination.
  13. On chokes, the goal is high common-mode impedance on the coax outside, not a perfect-looking SWR curve. A coax-fed dipole with no choke lets the shield carry current and act as part of the antenna. That distorts the pattern, can bring RF into the shack, and can make analyzer readings depend on how the coax is routed. A common approach is a stack of type 31 ferrite cores with the coax wound through them, which works well from the lower HF bands upward. Type 43 is often used toward the higher bands. A small coil of coax (an air choke) can also work, but it is naturally resonant and tends to be effective only on certain bands, so it is less broadband than ferrite. Also, ferrite can overheat if the choke is poorly matched or sees high common-mode voltage, so size the cores for your power level. For ladder line with a tuner, the best arrangement is usually to keep the line balanced all the way to the tuner's balanced output or a good current balun there. Window line has low loss even at high SWR, but it needs clearance from metal gutters, downspouts, and other conductors. Make bends gentle and use a few twists only if the line is a type that tolerates them. A 4:1 balun is a transformer, not a magic fix. At high impedance mismatches it can heat and lose efficiency, so a 1:1 current balun is often the safer starting point for a doublet, with the tuner handling the match. On traps: a parallel LC trap acts as a high-impedance isolator near its resonant frequency and as an inductor below it, which shortens the antenna's electrical length on the lower band. The tradeoffs are narrower bandwidth, some loss in the coil and capacitor, and the need for weatherproofing and capacitors with sufficient voltage rating. A fan dipole avoids traps, but the elements interact, so expect to prune each one in turn.
  14. On CAT, the underlying rule is that a serial port can only be opened by one program at a time. If N1MM+, WSJT-X and the logger all want the same COM port, someone loses. There are basically three ways around it. The first is to let one program own the rig and have the others talk to it. Hamlib's rigctld can do that over a network socket, and WSJT-X can use "Hamlib NET rigctl". OmniRig (Windows) and Commander in the DXLab suite fill a similar role for programs that support them. The second is a virtual serial port splitter that duplicates the radio's port. That works but adds a layer to debug if you see timeouts. The third is to use only one program for rig control at a time and shut the others' CAT off, which is fine for casual use but awkward in a contest. If frequency or mode readback goes strange, check the basics: baud rate matching the radio's menu, the CI-V address on Icom rigs, and whether the radio's own USB CAT is competing with a separate cable. PTT is another separate item. Using CAT PTT, RTS/DTR or VOX affects whether WSJT-X can key the rig correctly, and the settings differ between the digital program and the contest logger. Rotators follow the same logic. A single owner for the rotator interface is easier to manage, and then logging software reads or commands it. Many setups run a rotator control program or rotctld in the middle, and the logger just sends a bearing. That also keeps band maps and "point antenna at spot" features working without every program fighting for the controller port. One note on UDP: if WSJT-X is sending to both Log4OM and a decode helper such as JTAlert or GridTracker, check the UDP server address and port. Some listeners support multicast and some do not, so a second listener can silently get nothing. Check the manual for the program you actually run.
  15. On flashcards: be careful with anything visual. A card showing a letter on one side and dots and dashes on the other trains your eyes to read a diagram, and Morse isn't a visual code. When you hear a character on the air, there's no chart to consult. If you want flashcard-style drilling, use audio. Hear the character, say or write the letter, then check. Most Koch trainers already do this, with random groups instead of a fixed deck. When you're learning, say the sound as "dit" and "dah" rather than "dot" and "dash", and think of a letter as a rhythm. Don't count elements. If you catch yourself counting, that usually means the speed or spacing is too slow, or the character isn't learned yet. Drop the effective speed a little and go back to the shape of the sound. Many people will also tell you that when you miss a character, you should let it go. If you stop to puzzle over a missed letter, you'll miss the next two or three as well. Write a dash or leave a gap and keep going. With practice the gaps shrink. About CW Academy: it's run by CWops, which is a volunteer-led organization, and the beginner track is built around guided practice with an advisor and a small group, plus daily practice between sessions. The appeal is accountability, plus having a human to ask questions. If you do best with structure, it's worth looking at. Class availability, schedule and sign-up rules change, so check the CWops site for the current details. It also doesn't replace self-study. It mostly tells you what to do and keeps you honest. For moving from paper to head copy, there's no switch, just a series of steps. First, copy letters on paper in the trainer. Next, copy short words and common callsign-type groups. Then try to hold a few characters in your head and only write the word once it's finished. Finally, listen to slow, real CW and try to follow it without writing. Don't fight to eliminate paper. It drops away when you find you're not using it. Practicing with your pencil in your hand and no list of letters to look at keeps your recall honest. For confidence, think in layers. Practice the standard exchange (call, signal report, name, location) until it's automatic, since the first few QSOs are mostly predictable. Then listen on the air before you transmit. It's fine to send "QRS" (please send slower) or "PSE QRS", and most operators will happily slow down. Your own sending matters too. If you use a key or paddles, practice clean, evenly spaced characters. Crisp sending gets you answered more readily than fast, sloppy sending. One last practical point: avoid relying on a decoder app to "check" what you hear on the air. It can be useful to compare notes occasionally, but if it becomes your safety net, your ear never has to do the work.
  16. My advice is to walk the entire flea market once before buying anything. Don't buy the first good-looking item you see. Note what you like, how much each seller wants, and how many similar items are out there. A lot of the same handheld or power supply usually means you can wait or haggle. A rare item might not be there when you come back, though, so decide how much you want it. For testing, an antenna analyzer or a cheap NanoVNA is great for checking coax, antennas and filters on the spot. A dummy load and a known-good supply help with radios. For anything with a CRT or high voltage, like a scope, ask about its history and be careful if you plan to open it. A seller who shrugs and says "never tried it" has told you the price should be low. Also keep a small notebook or phone note of the radios and accessories you already own. It stops you buying a third mic connector adapter you didn't need.

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.