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

Admin_Terry

Administrators
  • Joined

  • Last visited

Everything posted by Admin_Terry

  1. On receiving, the habit that holds many people back is translating each sound into a letter and then into a word. Aim to hear characters as units, then short words and common call signs as units. That's the reason Koch-style training with full-speed characters and Farnsworth spacing works for many learners: you don't build a habit of counting. Start with a few characters, add more as your accuracy is reliably high, and keep the character speed high enough that you can't count elements. If you have to, set the extra spacing wide and then shrink it over time. Copying in your head, a character or two behind the sender, helps once you get past the beginner stage. Writing every letter as it arrives keeps your attention at the pencil, not on the next sound. A short note of call signs, names and signal reports is enough for most QSOs. For filters, tune the sidetone and receive pitch to something comfortable, commonly in the range of 500 to 700 Hz, and make sure you're centered on the signal. A narrow filter can cut QRM dramatically, but very narrow filters can cause ringing that smears the characters together, and they make it easy to miss a station calling slightly off frequency. Use wider settings when searching and tighten them when working a crowded spot. CW Skimmer and similar decoders are strong at picking out many call signs across a band at once. The Reverse Beacon Network is built on that sort of tool, and it's useful for checking where your signal is being heard. As a training aid, though, decoders do poorly with fading, noise, odd spacing and hand-sent irregularities. Use them to confirm what you thought you heard, not as a replacement for your ears. In contests, much of the work is predictable. Learn your common prosigns and abbreviations (AR, SK, BT, KN, AS, BK, TU, and so on) and the usual cut numbers, such as N for 9 and T for 0 in a 5NN report. Set up memory keyer messages, send your call clearly rather than fast, and repeat only what's needed. Matching the other station's speed, or going slightly slower when the band is rough, is a courtesy that often gets more contacts in the log than blasting along at your maximum.
  2. One thing to add to the gain discussion is that the right gain setting is rarely the maximum. A practical method is to watch the spectrum while raising the gain. The noise floor should come up a little above the dummy-load level, but if strong signals start producing spurs that move in the wrong direction when you change the gain, or you see a lot of symmetrical junk around a strong carrier, you are probably overloading the front end. At that point, adding gain only makes things worse. A broadcast FM band-stop filter and a medium-wave high-pass or band-stop filter are often the most cost-effective improvements on a dongle. They remove the strongest signals before the tuner and ADC, so the AGC and gain controls don't have to back off for them. On the antenna side, noise from nearby electronics can enter through the coax shield as common-mode current, not through the antenna itself. If the noise changes when you move or touch the feedline, a choke made from a few turns of coax on a suitable ferrite core is worth trying. For active whips, the bias tee supply can be a noise source itself, particularly if it is powered from a noisy USB port or laptop, so try a separate clean supply or a ferrite-isolated USB cable before blaming the antenna.
  3. I'll take the first four, since they're the most common sources of confusion. Station ID (97.119). Your own call sign has to go out at the end of each communication and at least every 10 minutes during one. The 10 minutes is a maximum, not a schedule. Identify on the same channel you're using, in the mode you're using or another mode permitted in that segment. On phone that means English or CW, and data or RTTY IDs follow the rules for those modes. Each station is responsible for its own ID. A repeater ID covers the repeater, not you. Tactical designators like 'Net Control' or 'Shelter 2' are fine as extras, but they don't replace the call sign. Third-party traffic (97.115). A third party is anyone other than the control operator and the station you're talking to. Third-party messages are allowed within the U.S., and the control operator has to be present, monitoring, and able to stop the transmission. With foreign countries it's allowed only if the U.S. has a third-party agreement with that country, or in an emergency or disaster. The exception is when the third party is a licensed amateur who could operate under their own call sign. There are also limits on third parties whose own amateur license has been revoked or suspended. And passing traffic for someone doesn't override the business restrictions below. Power (97.313). The general ceiling is 1500 W PEP at the transmitter output, but there's more to it. You must use the minimum power necessary for the communication. 30 meters is limited to 200 W PEP. Technician HF privileges are capped at 200 W PEP. 60 meters has its own special channel and power rules, and some areas restrict 70 cm power near certain government radar installations. The 1500 W figure is output power, not ERP, so antenna gain doesn't change the number. 60 meters is the exception, where the limits are defined differently. Prohibited transmissions (97.113 and related sections). Broadly: no transmissions for pay or in which the control operator or their employer has a pecuniary interest, with limited exceptions (a teacher using it in class, occasional equipment sale or trade announcements, emergency communications). No music or broadcasting, no obscene or indecent language, no messages in codes or ciphers meant to obscure meaning, no false or deceptive signals, and no willful or malicious interference. Passwords for telecommand or control links are treated differently from encrypting message content. One thing worth adding to the cheat sheet: privileges follow the control operator. A Technician on a General's station can use General privileges only if that General is serving as control operator and takes responsibility. This comes up at Field Day with guest operators.
  4. For top-band and low-band work, I'd put receive antennas ahead of transmit power. On 160 m, 80 m and sometimes 40 m, the signal from a remote island can be barely above the noise. A Beverage, flag, loop or similar receive antenna can make the difference between hearing a faint DX station and hearing nothing. Many stations can transmit effectively with a modest setup but can't copy the DX in their local noise, so if you can't hear them, you can't work them. Timing matters more at low frequencies. The DX path may only open during a narrow sunrise or sunset window, and grey-line enhancement can be sharp but short. Check that your own location and the DX's location are both in the right phase, and keep an eye on geomagnetic conditions. A disturbed field can degrade low-band propagation and paths that run near the poles. For places like Clipperton, the path from your side may favour certain bands at certain times of day. For Bouvet, the geography and the amount of the world that has a workable path can be very different, so look at the great-circle path, not just the distance. Club Log is useful for planning on both sides of the pile. As a chaser, check the Most Wanted list to prioritize which entities you still need, and see whether the DXpedition uploads logs while operating. These logs are often a good reference for dupes and callsign checks, but an absent callsign doesn't prove that your QSO failed, so don't make decisions from a single check. If you're on the planning side of an expedition, think about how you'll balance bands, modes and operating hours. Rare entities usually need many hours at the right time of day on bands with good propagation to the main population centres, and the schedule has to account for weather, landing conditions and equipment failures. Operations at sites like Clipperton or Bouvet may have less time on the air than the plan suggests, so efficient pileup management matters. Finally, on the etiquette front, keep your transmitted signal clean, don't use more power than you need, and be prepared to move on if the pile isn't working in your favour. Good conduct keeps rates high and helps the expedition team, which is ultimately what gets everyone into the log.
  5. On leaving a run, I'd define a trigger in advance rather than deciding mid-pileup. Something like: if the rolling rate over the last 15 minutes falls below some fraction of your best recent hour, do a quick check elsewhere. The exact number matters less than having one, because tired operators tend to stay put out of inertia. N1MM's rate display makes that comparison easy, but the real information comes from what you hear while tuning: how many unworked stations are on the other band, and whether you can hear multipliers you still need. On multipliers, the marginal-value formula works well when you track what you still need. A band map with worked and needed stations color-coded lets you see at a glance whether a spot is a new mult, a new station only, or a dupe. Check how your logger treats multipliers by band, because a station worked on 20 may still be a new mult on 15. Spotting tools like the skimmer or packet help most here, because they bring needed multipliers to you without much tuning. In an unassisted category, you are doing that scanning by ear. One caution on self-spotting. Some contests and categories don't allow you to spot yourself or ask others to, and the rules differ between events. Reading the rules before the contest costs far less than a disqualification or reclassification afterwards.
  6. The legal side deserves more weight than it usually gets in mod threads. In the US, unlocking transmit on a radio does not change what you are authorized to transmit. Amateur privileges stop at the amateur bands, and anything beyond that needs separate authority, such as a MARS or CAP assignment that covers the specific frequencies and your use. Equipment rules also differ by service. A radio certified for one service and altered for another can run into equipment authorization issues, which is a separate matter from the license. Rules differ elsewhere, so check your national regulator. One practical habit is to keep a note of the original configuration, the change you made, and your authorization for the channels you program. If you ever have to answer a question from a repeater coordinator, program officer, or interference complaint, that record is the best defense. On power, fuse the battery side as close to the terminal as practical, and don't assume a battery labeled 12 V behaves like a 13.8 V supply. A radio's rated input range and the pack's voltage under load both matter. For LiFePO4 packs, the charge and discharge profile is different from lead-acid, so check what your radio does at the low and high ends.
  7. On the listening side, a KiwiSDR or WebSDR is a good way to gauge latency expectations before committing money. Both stream audio and a waterfall to a browser, so you get a feel for the delay, buffering and dropouts of a typical internet path. That is not identical to the traffic of a full-duplex remote base, but it will tell you quickly whether your connection has jitter problems. The caveat is that public receivers have their own policies, user limits and sometimes frequency or time limits. Treat them as a reference tool for checking propagation, not as a substitute for a receiver you control. For comparisons, note the receiver's antenna and noise environment, because a quiet site can make a band look far better than it will sound at your own QTH. Also, for anyone planning to operate remotely in contests, make sure the rules say remote operation is permitted for your category. Some events require the transmitter, receiver, antennas and operator to be at a single location, while others allow a remote setup if it follows specific conditions. This varies between sponsors and between years, so read the current rules rather than assuming.
  8. On the radio choice, I'd start from the local repeater list rather than from the spec sheet. If the area is mostly analog FM, the TM-D710G is a practical match, and its APRS and cross-band features are the reason people pick it. If the busiest nets or rooms near you are on D-STAR or C4FM, the ID-5100A or FTM-500D respectively makes more sense. Digital modes only pay off when there are people on them to talk to. For noise, a useful method is to do it in steps. Check the radio with the engine off, then with the ignition on, then running, then with the HVAC, wipers and lights on. Whatever changes the noise tells you where it comes from. Alternator whine that follows engine RPM points to power-lead filtering or routing. Hash that appears with a certain accessory points to that accessory, and the fix is often moving a charger or LED light, not the radio. Also test SWR before blaming the radio for poor range. A mount with a bad ground connection or a damaged coax end can make a good radio sound weak, and it's easy to overlook on UHF where losses and poor connections show up faster.
  9. One distinction that trips people up is the difference between a drill that tests radios and a drill that tests information flow. Checking that everyone can hear the repeater proves little. Better tests: send a message with a number, a date and a long place name, then see whether the receiving end copies it exactly. Switch to simplex, lose the repeater, and see whether the net adapts. Hand net control to a new person halfway through. For deployment decisions, many groups use a simple readiness roster: who can respond within a defined window, who has operated an EOC or shelter position, who is certified for specific agency duties, and who has the right equipment for HF, VHF or UHF. Also plan for fatigue. A person who has been on the air for many hours is more likely to mishear a number, so shift lengths and relief should be arranged before the incident. For SKYWARN, keep the roles separate. Weather spotting reports follow NWS guidance and are not the same as an ARES emergency net, even if the same people take part. Know which net you are on, who the net control is, and what the local NWS office wants reported.
  10. For the low bands, I'd add that the receive chain matters more than people expect. For 160 and 80, small receiving antennas such as Beverages or loops can make an unreadable signal copyable, and a good transmit antenna cannot compensate for a noisy location. Because DXpeditions are often limited on those bands, the target may have low power and a compromised antenna, so there may only be a narrow window around grayline, which means you should have your station ready before it opens, not while it is happening. On top band, calling away from a crowded frequency is more important still. The DX often listens up by a small amount, for example 1 to 5 kHz, and calling on their transmit frequency can disrupt the whole operation. So confirm your VFOs, check that your rig is not set to transmit simplex, and keep your calls brief. If the DX is calling CQ with a listening instruction, follow it exactly. If you are not sure, keep listening a little longer. For digital modes, if the operation uses the Fox/Hound mode in WSJT-X, read the instructions carefully. Fox transmits on a specific region, hounds should call above the stated frequency, and the rules about where to call can be different from a CW or SSB pileup. The usual advice for hounds is to avoid calling on Fox's own frequency, and to follow the software's workflow rather than improvising. On the cluster, use it for discovery and then judge by ear. Spot only what you have actually heard, include the listening frequency when you know it, and avoid adding noise with repeated spots. A good spot comment can save others a lot of guessing; a vague one adds to the problem.
  11. One thing I'd add to the plateau discussion is that the plateau is sometimes a measurement problem. If you test yourself with random five-character groups and then listen to real QSOs, the two speeds can differ a lot. Real text has redundancy. You can guess a missing letter from context, so real-world copy is often easier than a random-group test, but it also lets you hide weaknesses. It helps to keep both kinds of practice in the schedule and track them separately, so you can tell whether you have a character problem or a word and context problem. On the keyer, I agree about not setting the speed higher than you can send cleanly. A practical test is to record a minute of your own sending and play it back at the same speed. If you can't copy your own recording easily, slow down. Spacing errors between letters are the most common culprit, and they make your sending harder for others to copy, especially the sloppy gap that turns 'ME' into 'ANT' or similar mix-ups.
  12. Start by confirming which pool is valid for your exam date. The NCVEC publishes each pool with effective dates, and the pools rotate on a four-year cycle. Many study sites and apps carry old versions, so check that the edition matches your session. Your VE team or the ARRL exam page can confirm this. On what to work through versus memorize: Worth understanding: Op amp gain is the most reliable one. Inverting gain is -Rf/Rin. Non-inverting gain is 1 + Rf/Rin. Once you see that the virtual-ground idea drives both, the variations are easy. The same goes for Q and bandwidth (Q = center frequency / bandwidth) in filter and resonant-circuit questions. FM modulation index (peak deviation divided by modulating frequency) is another short calculation that shows up in different forms. For digital topics, know that the sampling rate must be more than twice the highest signal frequency (Nyquist), and that more ADC bits means finer resolution. Fine to memorize: Oscillator types are mostly recognition. Colpitts uses a capacitive divider, Hartley uses a tapped inductor, and Pierce is a crystal oscillator. Many logic gate, flip-flop and component-symbol questions work the same way. Learn the pattern and don't over-derive. For Part 97, read the rules in context alongside the pool. Questions on station control, third-party traffic, spurious emission standards, and the privileges tied to each license class are easier to remember once you know why the rule exists.
  13. My rule is to sort everything by how close it is to the primary source. A manufacturer page, an FCC docket, or the ARRL's own publication comes first. After that come independent measurements and reviews, and last comes social media chatter. When something sounds big, I look for the document behind it. Most of the confusion about FCC changes comes from people treating an open proposal as if it were already in effect. For rigs, I wait for independent receiver measurements and for early firmware to settle. First production runs often have teething problems, and a firmware release a few weeks later can change the picture, for better or worse. If I can't find noise floor, blocking, and reciprocal mixing numbers or at least solid field reports from people near strong signals, I just don't factor the marketing into my decision. On firmware itself: save the configuration before any update, keep a copy of the previous version if the vendor allows it, and don't flash it the night before a contest. A USB cable and a laptop with a low battery is how people end up with a bricked radio.
  14. Adding to the above, with a focus on head copy, session design, and confidence. Session length: short and frequent generally beats long and occasional. Fifteen to thirty minutes of focused copy once or twice a day is a common recommendation, because fatigue makes your accuracy drop and then you're practicing mistakes. If your copy falls apart halfway through a session, stop for the day. Plateaus: nearly everyone hits stretches where speed doesn't seem to improve. A common cause is that you're still consciously decoding each character. The fix is usually to move to a slightly higher character speed or tighter spacing, accept more errors for a while, and keep going. Another is to practice with whole words and common callsign or contest-style patterns, so your brain learns chunks, not only single letters. Moving to head copy: this tends to happen in stages. First you write every character. Then you start recognizing whole short words, such as common ones like THE, AND, and your own callsign, and write them as units. Then you start letting letters go by without writing them while you hold the word in mind. The key skill is to stay a character or two behind the sender and not chase the one you just missed. If you drop a character, let it go and pick up the next one. Dwelling on the miss makes you lose the following three. A practical approach is to copy on paper first and then gradually reduce what you write, for example writing only the first letter of each word, then only numbers and names, then nothing for easy material. Practicing with plain-language text, not only random groups, is what builds this skill. Ear training also includes getting used to real conditions. Trainer audio is clean, but on the air you get QRN, QSB, drifting tones, sloppy fists, and different pitches. Once you have most of the alphabet, mix in recordings or on-air listening, and try different tone frequencies in your trainer so you aren't tied to one pitch. For confidence, the biggest step is lowering the stakes. Listen to real QSOs before you transmit anything, and write down callsigns and signal reports even if you miss the rest. Work up to answering a CQ from someone sending at a speed you can handle, using a simple exchange you've practiced: callsign, signal report, name, and location. Many beginners find that standard exchanges and abbreviations such as CQ, DE, K, R, 73, and QTH make early contacts much more manageable, because you know roughly what's coming. Slow-speed practice nets and class-organized practice contacts exist for exactly this reason. Nobody expects a new CW operator to be fast, and most operators will slow down if you tell them you're a beginner. It also helps to send practice with a key or paddle. Sending well teaches you to recognize good timing, and you need clean timing so that other operators can copy you. Record yourself and listen back if you can.
  15. On the bandwidth question: narrower is not automatically better. A very narrow transmit passband can make speech sound muffled, and some listeners find it harder to understand, especially with accents or poor receive conditions. Something around 2.4 kHz tends to be a solid default, and you can narrow it a bit when the band is crowded or a pileup is running. The sensible test is a report from a station that can tell you how it sounds, rather than your own preference at the monitor. On receive, I'd also say don't rely on a filter alone when the interference is right on top of the signal. Try shifting the passband, switching sideband briefly to see which side is cleaner, or lowering RF gain so strong nearby signals don't overload the front end. Those simple steps often help more than stacking noise reduction and notch filters.
  16. On interference and shared frequencies, the best default is to avoid escalating. Band plans are mostly voluntary agreements, not property rights. Check the published plan for your region before choosing a frequency, because narrowband digital, CW, SSB and beacon activity are often meant to sit in different segments. If a net or scheduled group is using a frequency, a quick, polite question usually settles things. If you hit interference, first check your own station. Overloaded receivers, bad audio settings, a noisy power supply or a poorly adjusted amplifier can cause splatter or noise that looks like someone else's problem. After that, work out whether it's occasional QRM, a local noise source or deliberate jamming. For ordinary QRM, a slight change in frequency, a narrower filter, a different antenna or a change of band can help. Don't respond to deliberate interference with insults. The usual advice is to ignore it, note the time, frequency and mode, and report it through the proper channels if it's serious. For new operators, a few simple habits go a long way. Keep your audio clean and avoid over-driving the microphone. Use only the power you need. Say your callsign clearly. Be patient if a contact fades, and don't assume someone is ignoring you. And if you make a mistake, such as calling on top of a QSO or forgetting your ID, just correct it and move on. Most of the community would rather help you than criticize you.
  17. For anyone starting out with kits, I would separate two goals: learning to build, and having a good radio. A Pixie-style rig is great for the first, but its receiver is so broad that it can be frustrating for the second. If you want a first contact with a kit you build yourself, look at something with a proper superhet receiver and a narrow filter, and keep the Pixie as a fun side project. On calling frequencies, listen for a while before you call. Many QRP stations tune up and down the calling frequency instead of sitting on it, and a CQ on 7.030 or 14.060 will get answers more often than a CQ in the middle of a crowded segment. Sending your power in the exchange, such as 5W, tells the other operator that you are running QRP, and good operators will often slow down and repeat. If you are chasing QRP-ARCI-style events, keep a log of both the power you ran and the power the other station reported, since that is how the scoring typically works.
  18. On decoders, I would treat them as a spotting aid rather than a substitute for copying. CW Skimmer can decode many signals across a band at once, which makes it very useful for seeing who is active, especially during contests. But the output depends on clean timing and a decent signal. QSB, QRN, a heavy fist, or two stations overlapping can produce confident-looking text that is simply wrong. Using the decoded callsign to find the station, then confirming it by ear, is much more reliable than copying a whole exchange from the screen. For contest work, I would build on a few specific habits. Learn the cut numbers used in the exchange (for example, N for nine and T for zero) so you aren't thinking about them while the pileup builds. Send at a speed you can also copy when the other station replies at that speed. Use AGN, a repeated callsign, or a single number only when you truly need it, and keep the exchange short and consistent. Practice with a contest simulator or recorded pileups, because copying a callsign in a pileup is a skill you won't get from ragchewing. On the abbreviations and prosigns: AR ends a transmission, SK ends a contact, KN invites only the station you are working to reply, and BT separates parts of a message. Learn them as single sounds, not as letters sent together, and your sending will sound more natural, whatever key you are using.
  19. A sorting rule that works for many people: digital by default, paper only when there is a reason. Upload everything to LoTW on a regular schedule, since weekly or after a contest is plenty. Sync to Club Log so you can use OQRS and see match rates. Keep eQSL and QRZ as secondary records. Paper is for entities that don't use LoTW, for awards that require it, or for a card you simply want to keep. On the card itself, the basics are your callsign in large type, the other station's callsign, date and time in UTC, band or frequency, mode, RST, and a clear 2-way confirmation line. Add your grid square and CQ and ITU zones if the award or the recipient might want them. Bureau sorters work from the callsign printed on the card, so put the recipient's callsign where it's easy to read, not tucked in a corner. The standard card is about 14 x 9 cm, and a bureau or mail slot handles that size without trouble. A photo or artwork on the front is fine, but leave a plain area on the back for the log data. A busy photo behind small text makes the card hard to read. For direct requests, put everything in one tidy package: your card, a clear SASE, and the postage the operator asks for. Small mistakes such as a missing callsign or an unreadable address are what make someone put your envelope at the bottom of the pile.
  20. On the POTA and SOTA side, the main thing to know is that spots drive the whole hunting experience. Hunters watch the spot page and activators depend on being listed. For POTA, the site accepts spots and also shows automated ones for some CW activity, so check the current help pages for what is supported. Self-spotting rules and etiquette differ by program, so read each one's guidance instead of assuming they match. Give an accurate frequency and mode, and update or retire the spot if you move or QSY. For repeater and mobile use, RepeaterBook is useful for finding nearby repeaters with offset, tone and mode. The listings are user-maintained, so confirm that a repeater is still on the air and that the tone is correct before relying on it. Keep any phone app use for when you're parked, not while driving. A few smaller points. QRZ and HamQTH are both callsign databases, and many hams keep their logs in one and mirror them to the other for convenience. Be aware of what you publish in a profile, especially a home address. For study, HamStudy's practice exams and spaced repetition are aimed mainly at the US license pools, so confirm they cover your exam system. For grid squares, a Maidenhead map is handy for POTA, VHF contests and FT8, where a 4-character grid is the usual exchange. HamCalc is best kept for the occasional antenna length, impedance or filter calculation, and I wouldn't treat it as a live tool.
  21. On the choke question: measure it if you can. A ferrite choke with a stated mix can still be poor for your band, because the impedance depends on the number of turns, the core size and the frequency. Putting turns of coax through a core adds capacitance between turns, which can pull the peak impedance down in frequency. For 40 m and below, a stack of type 31 cores or a single large toroid with a handful of turns often works better than a few beads. If you have an analyzer, put the choke on a short test lead and compare the reading before and after. A choke that looks fine on 40 m might be marginal on 10 m, and for a multiband antenna you may want two different chokes, or one at the feedpoint and another a quarter wave or so down the line. For the radial minimum, it depends on the layout. Elevated and tuned: 2 to 4 per band is a defensible floor. On the ground or buried: I'd consider 16 a reasonable starting point and more worthwhile. The difference shows up as efficiency, and it can be hard to see from SWR alone, since poor ground loss often makes the SWR look good. An antenna with a nice 1.1:1 match may simply be a good dummy load.
  22. I'd go to spots first and numbers second, because the spots are measurements and the indices are indirect indicators. If I check 20 m or 15 m and the beacon network shows several stations at decent strength, I don't need the SFI to tell me the band is open. The indices matter more when I'm planning ahead or trying to work out why something is behaving oddly. One caution on WSPR: it shows what is possible with a low-power transmitter and a good receiver, not what your own station can work. A 200 Hz-wide decode at around -25 dB SNR means the path exists, but an SSB QSO needs a lot more signal than that. A useful trick is to run WSPR with something close to your normal power and antenna. Then the spot reports tell you more about your own setup, not just about the band. For the NCDXF beacons, the four power steps are handy. If you can hear the 100 W transmission but not the 10 W one, the band is open but weak. If you hear all four, it's really open. It takes only a few minutes of listening to learn something useful.
  23. I'd treat the pool as three buckets. First, the concepts that repeat in different wording. Oscillators are a good example. The Barkhausen idea is that a loop oscillates when gain around the loop is at least unity and the feedback phase shift is 0 or 360 degrees. Past that, you mostly need to recognize the family. Hartley uses a tapped inductor, Colpitts uses a capacitive divider, and Pierce uses a crystal. Amplifier classes work the same way: Class A conducts for the full 360 degrees of the cycle, Class B for about 180, Class AB for between 180 and 360, and Class C for less than 180. Learn the definitions once and those questions are easy points. Second, the formulas you should be able to run with a basic calculator. For op amps: Inverting gain = -Rf / Rin Non-inverting gain = 1 + Rf / Rin With Rf = 47 k and Rin = 4.7 k, the non-inverting gain is 1 + 10 = 11. The inverting gain is -10, which also means a 180-degree phase inversion. For FM, modulation index = peak deviation / modulating frequency. A 3 kHz deviation with a 1 kHz tone gives an index of 3. Deviation ratio is similar but uses the maximum deviation and the highest modulating frequency. Third, the stuff you simply have to memorize. That includes filter terminology: Butterworth is maximally flat in the passband, Chebyshev allows ripple for a steeper cutoff, and Bessel preserves phase and group delay better. Also learn shape factor, which is the ratio of the stopband bandwidth to the passband bandwidth, so a lower number means a sharper filter. I'd start with the calculation topics, since they're where wrong answers come from, and leave the pure memorization for the final week or two.
  24. On paths: it helps to check what your local digipeaters actually do before choosing. Some areas run only WIDE1-1 fill-ins plus WIDE2-n wide digis, and others use regional aliases. Reading nearby digipeater beacons and comments, or asking the local APRS group, is better than copying a path from a forum post. If you transmit from a high point, a single hop is often enough, and a long path will only cause duplicates over a larger area. On SmartBeaconing, the cleanest way to tune it is to think about what each setting is for. The slow rate is the heartbeat while you're stopped. The fast rate is for highway speeds. The turn settings are there to keep the track from cutting corners on the map. If you see lots of beacons while stationary, the likely culprit is GPS jitter making the unit think it's turning, so raise the minimum turn time or the turn angle. For walking, you'd usually lower the high-speed threshold so the fast rate actually kicks in. For the TH-D74/D75, FT5D and others, also check whether the radio is set to digipeat, whether it uses its internal TNC or an external one, and which frequency the APRS band is set to. A surprising number of "it doesn't work" cases come down to the radio sitting on the wrong band or channel.
  25. On band choice, the honest answer is that it depends on what you can build and host. If you have room for a stack of long Yagis and a tall mast, 2 m is the most accessible, but you will have to handle polarization and noise. If you have a decent dish and a good feed, 23 cm tends to make better use of a smaller footprint, and polarization trouble largely goes away. 70 cm is a decent middle path, but it is usually the least crowded on the calendar. Faraday rotation is the thing most people underestimate on 2 m. The ionosphere rotates the plane of polarization, and this varies with time, ionospheric conditions and path geometry. On top of that, there is a purely geometric offset between your horizontal and your partner's, depending on where each of you is relative to the Moon. Fixed horizontal polarization can give you deep nulls for long stretches. The practical fixes are a polarization-rotatable array, which needs cross-polarized Yagis with switching or a phasing system, or receive with both polarizations and use software that can combine or choose between them. On 70 cm the effect is much smaller, and on 23 cm and above it is usually negligible, so the issue becomes circular versus linear and agreeing the convention with your partner. For checking the station, measuring Sun noise is the standard approach for evaluating the receive chain, and Moon noise follows as you get better. If your Sun noise numbers are far from what your gain and system temperature should give, fix that before you spend weeks chasing weak calls. Tracking errors, a badly placed feed, hot LNAs and a leaky transmit-receive relay are all typical culprits.

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.