Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Mod_Tom

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Tom

  1. On tactical versus formal traffic, the biggest thing is knowing which one the situation calls for. Tactical traffic is short, real-time and usually uses plain language and tactical call signs, like "Shelter One" or "EOC," so the net does not depend on who happens to be sitting at the radio. Formal traffic is written, structured and meant to be delivered exactly as received. That is where the ARRL radiogram format comes in, with its number, precedence, station of origin, check count and so on. A served agency will most likely hand you something on an ICS-213 or its own form, so be ready to adapt rather than insisting on radiogram format. Also drop the 10-codes and ham-style jargon when working with agencies. ICS calls for plain language, and an agency that uses different codes from the next county is a good reason to avoid them. Say what you mean, repeat critical items like names, numbers and addresses, and use phonetics for anything that could be misheard. For net control, a simple structure helps: announce the net purpose, call for emergency or priority traffic first, then check in stations by category, and keep a log as you go. Net control should not be the person who has to leave to run an errand, so have a relief operator identified before it starts.
  2. On the linear side, I would add that you should practice by listening first. Tune the RS-44 downlink and just follow a couple of CW and SSB signals through a pass while watching how the tracking software shifts the frequency. If you understand the inversion and the Doppler in receive-only mode, transmitting becomes far less confusing. When you do transmit, begin with low power and confirm your signal on the downlink, then go up only until you are comparable with other stations. Some people also find CW easier than SSB at first because the narrow bandwidth gives a better chance of copying through fading. For rotators, I think the decision depends on the antennas. If you are using a lightweight handheld Yagi, hand tracking is simple and keeps costs down. A rotator makes sense once you have a heavier crossed Yagi system, since it frees your hands for logging and tuning. In both cases, make sure the pointing is correct and that cable routing doesn't get tangled during az/el movement, especially at the 0/360° crossover point.
  3. One thing that makes a big difference is building the exercise around injects instead of just "traffic." An inject is a timed event handed to a participant: a shelter reports a generator failure, a road is closed, a served-agency contact asks for a status update, the primary repeater goes "down" and everyone must move to a backup. It forces decisions. Without injects, a net can look busy while nothing is being tested. For message handling specifically, vary the difficulty on purpose. Some messages should be short and clean. Some should have numbers, street names or medical terms where mistakes matter. Practice phonetics for those parts, read-backs for critical items, and the habit of saying "I'll repeat the numbers" without being asked. Also check the word count (the "check") on formal messages, because it catches dropped words on the receiving end. Another useful twist: make some messages undeliverable. The addressee has moved, the shelter has closed, the phone number is wrong. The group then has to practice what to do with a message that can't be delivered: log it, notify the originator, and decide whether to retry. Real traffic does not always end neatly, and a message log that shows what happened to each message makes the after-action review much more honest. One more point on scripts: keep tactical call signs tied to a location or function ("Shelter North," "County EOC") rather than a person, so operators can swap without confusing the net. And still identify with your FCC call sign as required. The tactical call does not replace that.
  4. Koch and Farnsworth solve different problems, and you can combine them. The Koch method starts with the characters sent at a fast speed, commonly around 20 wpm character speed, but with only two characters at first. When you copy them at roughly 90% accuracy, you add one more. Because the speed never drops, you learn each character as a whole sound (a rhythm) rather than a count of dits and dahs. Counting only works at slow speeds, and you'd have to unlearn it later. Farnsworth sends each character at a fast speed but stretches the spaces between characters and words, so the overall speed is lower. It gives you thinking time without distorting the sound of the letters. You can use it with Koch: keep the characters fast, add generous spacing at first, then shrink the gaps as you improve. The thing to avoid is learning at 5 wpm with every element sent slowly. It feels easier, but you will hit a wall and have to relearn the sounds at higher speed. On the tools: LCWO.net is a free, browser-based Koch trainer. It tracks your progress and lets you set character speed, effective speed and tone pitch. The G4FON trainer is a downloadable program built around the same Koch idea, and some people prefer working offline. Both are good, so pick whichever you'll actually open every day. Mobile Morse trainer apps are handy for short sessions, but check that they let you control character speed separately from spacing and don't just show you a chart. For flashcards, skip the visual kind. A card showing 'K' on one side and '-.-' on the other trains you to read symbols, not hear them. If you want a card-style drill, use audio only: you hear the character, you say or write it, then you check. Closing your eyes during a drill also helps.
  5. On the Smith chart, I wouldn't try to master the whole chart. The pool questions usually test a few skills: find the normalized impedance point, recognize the matched point at the center, understand that a constant-SWR circle is centered on the chart, and know that a half wavelength of line brings you back to the same impedance. Learn those four ideas well and you'll get most of the points. A free Smith chart tool lets you plot points and watch them move as you add line length, which makes it click faster than a static diagram. For Part 97, I'd split study into two buckets. One is stable material like control operator duties and station identification, which you'll learn once. The other is frequency allocations, power limits and band segments, which are worth checking against the current rules text since details can change. If you pass, remember that the Extra license gives you all privileges on every amateur band and in every authorized mode, including the Extra-only segments on 80, 40, 20, and 15 meters, but you should still read the actual segment limits before operating near the edge.
  6. For noise, an A/B test saves a lot of guessing. With the squelch open on an unused frequency, note the noise with the engine off and accessories off. Then start the engine and turn items on one at a time: headlights, blower motor, dash cam, phone charger, seat heater. Whatever changes the hiss or whine points you at the likely source. Alternator whine on the receive audio, or heard by others on your transmit, tends to point toward the power connection. A buzz that changes when you turn on one accessory points to that accessory. Also check the antenna side before you hunt for noise. A poor ground connection at the mount, a pinched coax, or a poor connector can both raise the noise floor and hurt transmit performance. If you get high SWR on UHF but a fine reading on VHF, check the antenna's length and mounting before blaming the radio. Mobile antennas that look similar aren't always tuned for 70 cm, and the vehicle body affects the result. Doing it in a clear open area gives a more reliable reading than a garage with metal all around.
  7. A few notes on the specific parts mentioned. Si5351: its outputs are square-wave-like, so there will be harmonics. If the signal goes anywhere near an antenna or a receiver front end, add a low-pass filter sized for the band. Keep the I2C wires short, use the correct pull-ups for 3.3 V, and don't run the clock outputs in a ribbon next to the I2C lines. The drive-strength setting changes output level, so check it with a scope or a power meter into a 50 ohm load instead of assuming a number from a forum post. ESP32 as a sensor board: the ADC is not very linear, and ADC2 can't be used while Wi-Fi is active, so plan your pins around that. Wi-Fi transmit bursts also cause current spikes, and a weak supply or a long thin power lead leads to brownouts that look like firmware bugs. Put a bulk capacitor near the module and keep the antenna end of the board clear of metal. SWR meter: a diode detector is simple, but its response is nonlinear at low power. SSB also makes a mess of the reading because the power is constantly changing. Sampling several times and keeping the peak value works better than a single reading. A log detector gives you a much wider dynamic range, but you still have to calibrate it against a known power meter. Direwolf: most of the pain is audio level and PTT, not software. Set the transmit and receive levels deliberately instead of turning everything up. For PTT, you can use a GPIO line, a CM108-type USB sound adapter with a GPIO pin, or rig control through Hamlib, depending on your hardware. Check the TX delay and the deviation with a second receiver before putting a tracker on the air.
  8. One tip is to write a short wish list before you go, with the model, a fair price range, and the dealbreakers. Hamfest tables are very good at turning "I'm just looking" into a trunk full of stuff you don't need. A list keeps you honest, and checking recent completed listings for typical prices helps you know whether a deal is actually a deal. For the testing side, a NanoVNA and a 50-ohm load tell you a lot about antennas, coax, and tuners. If a seller has a tuner or a coax-fed antenna, you can check it in under a minute. Also, take a photo of the front and back panels of anything you're considering. If you need a manual or want to compare serial numbers later, it helps.
  9. One thing worth separating is the "which mode" question from the "why isn't it working" question. The mode should follow the path and the purpose. For general DX on HF, FT8 is the default because of the activity level, and FT4 is for contests where a 7.5-second cycle matters. JS8Call uses FT8-style modulation but adds free-text keyboard messaging with several speed settings. Its slower speeds trade throughput for sensitivity. It is good for casual messaging and relaying, but it is not a fast QSO mode. For VHF and above, MSK144 is designed for meteor scatter: you are decoding short bursts and pings, so the software uses fast decoding and short messages. Q65 is intended for paths with fading or slow Doppler spread such as EME, tropo, ionoscatter and rain scatter, and it has multiple T/R period options. Pick the period according to the path rather than just the longest one, since longer periods need more stable timing and frequency. WSPR is a beacon mode. It does not make contacts, but it is a very good propagation and antenna test. Run it for a while on one band and compare your spots with the numbers other stations get. It also tests whether your frequency stability and clock are good.
  10. On club and special event calls, I'd stress that the trustee role is a real responsibility, not a formality. If the trustee's own license lapses, the club license has a problem, so clubs should have a plan for passing the trustee role on instead of relying on one person's memory. Keep the club's email and mailing address in ULS current so FCC notices actually reach someone. For special event 1x1 calls, read the coordinator's current instructions before planning on-air promotion or QSL cards. The call is only held for a short window, so your station ID and your publicity should match the dates you're actually authorized for. And whichever call you use, remember that ID rules still apply. Station control, band privileges and power limits come from your own operator class, not from how short or flashy the call is.
  11. Two things that helped structure the tougher areas for other candidates: tie each topic to something you'd actually do on the air, and use the practice-exam explanations to find your weak subelements instead of re-reading everything. For receiver design, think about a crowded band. Dynamic range is the span between the weakest signal you can hear and the strongest one before the receiver distorts. Third-order intermodulation matters because the products land close to the desired signals, so a higher third-order intercept point is better. Reciprocal mixing is oscillator phase noise mixing with a strong nearby signal and raising the noise floor. That context makes it easier to keep the terms straight. For antennas, keep a few reference facts handy. dBi is measured against an isotropic radiator and dBd against a dipole, and the difference is about 2.15 dB, so dBi = dBd + 2.15. Radiation resistance is not the same as ohmic loss, and efficiency is the radiation resistance compared with the total resistance, including losses. Many mistakes come from mixing those two. On the privileges question: yes, it's a good motivator, but it shouldn't drive your study. The Extra class has all amateur frequency privileges on all bands. That includes the Extra-only portions at the bottom of the 80, 40, 20 and 15 meter bands, which are the segments General licensees can't use. Check the current FCC Part 97 band chart rather than relying on a memorized list, because the exam tests rules as written in the pool and band plans can be confusing in practice. For Part 97, I'd read the actual rule sections that the questions reference. The pool wording is condensed, and the original text usually clarifies why the right answer is right.
  12. On the 44-QSO target, the thing to plan for is rate. Ten contacts is easy to hit even when conditions are poor, but 44 needs either a decent band or a willingness to move around. A sensible plan is to start on the band that's best for the time of day, work it until the rate drops, then QSY and spot again. Change mode if you can, since CW and digital hunters often aren't the same people as SSB hunters, so a mode change refreshes the pool. If you're running QRP, expect a longer session and allow for it. For the dual CQ, keep it short and give the reference in your exchange, not in every CQ. Something like "CQ POTA, CQ WWFF" is fine. Then when you answer a station, give your callsign and both references once, and let hunters tell you which one they need. Hunters who chase one program will ask or just copy their own reference. One caution: boundaries. Before activating, look at both reference maps and make sure your operating position is inside both areas. If it's inside only one, log it for that one only. That's the most common mistake in a dual setup, and it's easy to avoid with a quick map check.
  13. Koch and Farnsworth are separate ideas that people often blur together, and they can be combined. The Koch method starts with just two characters sent at a fairly fast character speed, commonly around 20 wpm. You copy them until you reach a set accuracy, usually about 90 percent. Then you add one new character and repeat. The point is that you never learn a slow, counted version of a character, so you never build the habit of counting dits and dahs. Everything is recognized as a sound pattern from the start. Farnsworth is about spacing. Characters are sent at a higher speed, but the gaps between characters and words are stretched so the overall speed is lower. It gives your brain time to identify each character before the next one arrives. You can use a Koch character-adding scheme with Farnsworth spacing, and many trainers let you set both the character speed and the effective speed separately. As your recognition gets quicker, you tighten the gaps until the effective speed catches up to the character speed. On tools, LCWO is a free browser-based trainer built around Koch lessons, so it's easy to start without installing anything. G4FON's Koch trainer is a downloadable program built around the same idea, and it's popular for offline practice. Their character orders differ, so pick one tool for your main progression and don't hop between orders in the first few weeks. Jumping around muddies which characters you've actually passed. I'd skip dot-dash charts. Learn the sound of each character, and think of it as a rhythm: the letter L is not 'dot dash dot dot', it's a little lilt. Visual charts tend to encourage translating, which becomes a bottleneck later.
  14. On go-bags, I'd think in layers: what you need to stay functional for the first several hours, what you need to operate, and what you need for the agency you're supporting. The first layer is personal: water, food, any medications, weather-appropriate clothing, a flashlight or headlamp, a first aid kit, and a photo ID or whatever credential your group issues. The operating layer is a handheld with spare batteries or a charger, a better antenna than the stock one, a mobile or portable option if you have it, a power source, coax and adapters, a pen and pencil, logbooks, message forms, and a printed copy of frequencies, repeaters and contacts. Phones and apps fail, and paper doesn't need power. The easiest things to forget are small: extension cord or power strip, headphones for a noisy EOC or shelter, tape, a clipboard, and a way to label your gear. Also forget the idea that your bag is the whole plan. Know whether the activation is a request to report somewhere or just to monitor a net. Don't self-deploy without being asked by the proper authority. Showing up uninvited can create problems for the people running the incident. For net control, practice a clean routine: state the purpose of the net, take check-ins in an orderly way, keep a roster, prioritize emergency or priority traffic, and keep a rhythm so stations know what to expect. The worst nets tend to be the ones where everyone talks at once or no one is sure who is in charge. Rotating the net control seat during exercises helps more people build the skill.
  15. For the nervous-first-call crowd: you're allowed to be a little awkward. Operators on repeaters and nets are generally glad to hear new voices, and a short, clear call is enough. Something like "This is [your call sign], listening," or answering a net control's call for check-ins, is perfectly good practice. Speak at a normal pace, and leave a short pause before you key up so others can break in if they need to. For first contests, pick something low-stakes. You don't have to chase a big score. Exchanging call signs and the required info a few times teaches you more about copying accurately, logging cleanly, and working with a crowded band than reading about it does. Read the contest rules first, since each one defines its own exchange, bands, modes and categories. If you're meeting a club, ask whether they have a new-ham night, a loaner radio, or a testing session. Those small things often turn a license into actual operating.
  16. One distinction is how much Q code belongs on phone. On CW the codes save time, but on voice you can just say what you mean, such as 'the frequency is busy' or 'I'm changing frequency.' A few have become normal spoken words anyway. QTH, QSL, QSO, QSY and QRZ are the ones you'll hear most on SSB and FM. Others, like QRN and QSB, show up less because plain words like 'noise' and 'fading' are easy to say. On CW, a few non-Q abbreviations help you keep up: TNX (thanks), FB (fine business, meaning good), OM (old man, a friendly term for a male ham), YL (young lady), XYL (wife), PSE (please), UR (your), ES (and), AGN (again), WX (weather), RIG, ANT, HW? (how copy?), BK (break), and TU (thank you). Prosigns like AR (end of message) and SK are sent as run-together characters without gaps, which is why they are often written with a line over the letters. Also, QRP and QRO are not just labels for how you feel about your transmitter. They are a reduce-power request or an increase-power request. In everyday ham talk, people say 'I'm running QRP' to mean low power.
  17. Start with the weighting. The Element 3 pool is divided into subelements, and each exam draws a fixed number of questions from each. Roughly: Commission's rules about 5, operating procedures about 5, radio wave propagation 3, amateur practices 5, electrical principles 3, circuit components 2, practical circuits 3, signals and emissions 3, antennas and feed lines 4, and RF/electrical safety 2. That adds up to 35. Check the subelement breakdown printed in the current pool, since the pool is revised on a cycle and you want the one in effect on your exam date. Because you need 26 of 35, you can miss 9. That changes how you should study. Don't try to be perfect on everything. Make the rules and operating-procedure groups close to automatic, since those are mostly recall and pattern recognition. Then be competent, not flawless, in the math-flavored groups. On propagation, the questions are less about memorizing and more about a few cause-and-effect ideas. The D layer absorbs lower HF frequencies during the day and fades at night, which is why 80 and 40 meters open up for longer distances after dark. Higher bands like 15 and 10 meters depend on the F layer being ionized enough, so they track solar activity. The MUF is the highest frequency that will be refracted back for a given path, and the critical frequency is the highest that returns a signal sent straight up. Know what the solar flux index and the A and K indices indicate in general terms: a higher SFI usually means better conditions on the upper bands, and high K or A values point to a disturbed geomagnetic field and degraded paths. Once those relationships make sense, most of the questions can be reasoned out. For antennas, the pool leans on a few reusable facts. A half-wave dipole is about 468 divided by the frequency in MHz, in feet, so a 40-meter dipole is roughly 66 feet overall. A quarter-wave vertical is about 234 divided by the frequency. Know what SWR does and doesn't tell you, why feed line loss matters more at higher frequencies, and the basic radiation pattern ideas for dipoles, verticals, and Yagis. For electrical principles, practice Ohm's law and the power formulas until you can do them without hesitation. P = I × E, P = I²R, and P = E²/R cover most of it. Also memorize the decibel shortcuts: 3 dB is about double the power, 6 dB is four times, and 10 dB is ten times. Know the difference between peak, RMS, and PEP, because it comes up in the signals and power questions. A practical schedule for someone with a full-time job: about four to six weeks at 30 to 45 minutes a day. Spend the first week or two reading explanations by subelement, not just drilling answers. Take a full 35-question practice exam each week, and keep a log of every question you miss. In the last week, re-study only your miss list and take several timed practice tests. When you're scoring comfortably above 85 percent on fresh randomized practice exams, you have a buffer for exam-day nerves.
  18. On top band the first thing that changes is that receiving usually matters more than transmitting. Many stations can transmit a strong signal, but if you cannot hear the DX well enough to hear the instructions, you will spend most of your time guessing. A dedicated receive antenna, such as a Beverage, a flag, a loop or a small receiving array, can make the DX audible above local noise. It also helps you identify where the DX is listening and when he is replying. Propagation is another difference. On 160 and 80 m, the useful window for a specific path can be short. It is often around sunset, sunrise or the gray line at one or both ends, and it depends on geomagnetic conditions, local noise and seasonal effects. So it is worth working out in advance when your path should open, rather than calling at random times. Even a short opening may only give a few minutes of workable signal. In that case, being on the right frequency, with split already set up, is more useful than a lot of trial and error. Also, avoid assuming the DX hears you as well as you hear him. On the low bands, many expeditions run compromise antennas near salt water, and conditions at their end can vary. Calling a little more patiently often works better than raising power and calling continuously. The same discipline applies to the etiquette: no calling on the DX's transmit frequency, no tuning up in the pileup, and no calling after the DX has said who he wants.
  19. The harmonic check deserves more emphasis. A lot of people stop at "I measured 1 W into a dummy load, so it works," but that tells you only how much total RF there is, not where it is. A scope reading includes every harmonic, so a rig that looks like 1 W on 40 m might put out less than that in the fundamental. If you have to use a scope, put a 50 ohm termination at the load and use the shortest ground lead you can on the probe, because the long ground clip on a typical probe adds enough inductance to distort readings at HF. A small test-point pickup, or a probe tip with a ground spring, will get you closer to reality. One more caution for bench work: a toroid filter built with the wrong material or a miscounted turn count won't show a problem until you actually check the output. Counting turns by passing the wire through the core's center hole (each pass is one turn) is easy to get wrong. An LC meter or a nanoVNA is cheap insurance for verifying a filter before it goes into a rig.
  20. I'd suggest chasing first, even for a weekend. Watching SOTAwatch teaches you how activators announce themselves, how fast they work stations, and how spots are worded. Then your first activation feels familiar instead of chaotic. For the first summit, pick one with an easy trail, a reliable approach, and a wide margin before sunset. Lower-point summits are fine. The point is getting four clean contacts and a clean log. Start on 2 m FM with a handheld, spot yourself with the right summit reference, frequency, and mode, and add HF later if you enjoy it. One practical tip: write the summit reference at the top of your notes before you leave home, so you aren't hunting for it with cold hands.
  21. On callsigns in poor conditions, the main trick is to avoid saying the whole thing the same way twice. Give the callsign with phonetics once, then give it again at a measured pace, rather than stringing it together faster each time. If the other station answers with a partial copy ("W-something-something-ZED"), fill in only the missing letters rather than starting over. Many QSOs go wrong because both sides keep repeating the full call instead of fixing the one unclear character. Some practical details: Numbers: say them clearly. In callsigns, "zero" is generally better than "oh", and "niner" is common for 9 because plain "nine" can be mistaken for "five" in noisy audio, and has historically been confused with the German "nein". Formal ITU number pronunciations such as "tree" and "fife" exist, but most hams use normal English numbers with "niner" being the common exception.Portable/mobile suffixes: "stroke" or "slash" are both widely understood. Many operators say "portable" or "mobile" if they are announcing the operating condition.Names: say the name normally first, then spell it only if needed. "I spell" is a useful procedure phrase before you begin spelling, because it tells the listener the next words are letters.Locations: do not spell the whole town. Spell the confusing part. For example, with a name that has a silent or unusual letter, spell only that part, then say the name again.Grid squares and signal reports: these are short, so they benefit from phonetics for letters, with digits spoken separately and clearly.Prosigns are mainly a CW matter. Characters such as AR, SK, BT and KN are sent run together as a single unit. On voice you use words instead: "over" to return the transmission, "clear" or "out" to end it, "say again" for a repeat, and "break" to interrupt. Avoid saying "over and out" because the two words mean different things and normally are not used together in careful procedure. On nets, shorter is better. Net control usually gives instructions in a fixed pattern: call for check-ins, ask for stations with traffic, then close. Check-ins should give the callsign in phonetics once, and any extra information (name, location, status) only when asked. For emergency or priority traffic, keep to the net's own rules and the plan the group has agreed in advance. Plain language is preferred over improvised codes, and the message text should be read in a steady pace with names and numbers repeated or spelled, as the receiving station may be writing it down. If a message contains an important number, repeating it as individual digits is better than saying it as a large number.
  22. A common split is to put anything that must keep working when the network or OS misbehaves on the microcontroller, and everything that benefits from a full OS on the Pi. Relay sequencing, rotator stop limits and watchdog timeouts belong on the Pico or ESP32. Logging, Hamlib, Direwolf and web dashboards belong on the Pi. The microcontroller can expose a simple serial or TCP command set, and the Pi talks to it through a small daemon. If the Pi crashes mid-rotation, the microcontroller can still stop the motor after a timeout or at a limit. On CAT: check the radio's manual for the actual electrical levels before wiring anything. CI-V is an open-collector style single-wire bus, so the usual approach is a transistor or small buffer circuit with a pull-up to the logic supply, rather than connecting TX and RX straight to a GPIO. For RS-232 levels, use a MAX3232-type converter or a ready-made USB serial adapter. For radios with built-in USB, plugging that into the Pi is usually the simplest and most robust option. Hamlib's rigctld gives you a TCP interface (default port 4532), so other software doesn't need to fight over the serial port. On ADCs: the ESP32's internal ADC is nonlinear, noisy and not good near the rails. ADC2 also can't be used while Wi-Fi is active. For rotator position or detector voltages, an external 16-bit ADC such as an ADS1115 over I2C is usually the less painful route. The Pico's 12-bit ADC is better behaved, but its reference is the 3.3 V supply, so add filtering and averaging, and keep analog traces away from the switching regulator. For a SWR meter, remember that SWR is computed from forward and reflected voltages, so detector linearity and calibration matter more than the display. A simple diode detector is nonlinear at low power. A log detector like the AD8307 gives a wide dynamic range, but you still need to calibrate against known power levels and a dummy load. Treat the displayed SWR with suspicion at very low power.
  23. For me the dividing line is whether the radio still feels good when the novelty wears off. A lot of rigs are exciting for the first month, when you're learning every feature, and then you find out whether you actually like sitting in front of them. Receiver audio is a big part of that. Listening fatigue is real, and a radio with a slightly worse spec sheet but a smooth, easy-to-copy receiver can win in the long run. On overpriced gear, I'd nominate anything where the price is mostly collector hype. Some classic names command a premium that has little to do with how well the radio performs on the air today. If you want to operate, a well-kept mid-tier rig from the same era is often a better value, and you'll worry less about putting a scratch on it. If you want a display piece, that's a different budget conversation and a perfectly legitimate one.
  24. On the choke: both types work, but they behave differently. A coiled-coax choke (several turns of the feedline itself, close to the feedpoint) is cheap and easy, but its impedance peaks around a fairly narrow range set by the coil's inductance and stray capacitance. It's worth checking that the peak actually falls near 7 MHz and not somewhere else. A ferrite choke wound with coax through a stack of cores, usually a mix such as 31 for lower HF, has a broader response. Aim for a choking impedance of at least a few kilohms, mostly resistive. What you want is to suppress common-mode current on the outside of the coax shield, so the feedline doesn't become part of the antenna and the pattern and SWR readings don't depend on how the cable is draped. That ties directly to measuring. If you measure SWR at the radio end through a long, lossy coax, the loss flatters the reading. An analyzer connected at the feedpoint (or at the end of a short line) gives the truer picture of the antenna. Also note that if the reading changes when you move the coax or touch it, you probably have common-mode current, and the choke isn't doing its job. For trimming: find the frequency of minimum SWR (or zero reactance on an analyzer) and compare it to your target. If resonance is low, the wire is too long. As a rough guide, for a half-wave dipole, a 1% change in length moves the resonance by about 1%, so at 7 MHz, expect roughly 70 kHz per 1% of total wire. Shorten both legs equally, in small amounts, and re-measure each time. Don't trust a single sweep, and repeat it if the wire sways. On apex angle, a flatter inverted-V (closer to 120°) tends to raise the feedpoint impedance toward the dipole's free-space value, while a steeper V lowers it. Either is usually within what a typical transceiver tolerates with a decent match. The tradeoff is more about where the ends can be anchored safely, since the end wire shouldn't hang within reach of people or pets.
  25. On the combined-reference point, I'd double-check boundaries before you set up. A WWFF area and a POTA park can have the same name but not the same footprint, particularly for state forests, wildlife areas and conservation land. If your operating spot sits inside one boundary and just outside the other, you could only be eligible for one. Most databases give a map or boundary info, and the managing agency's page is the real authority on where you may be and whether you need a permit for antennas or vehicles. For operating tips, write the references on a card where you can see them: both numbers, your callsign, and a short exchange script. When the pileup comes, that saves you from fumbling. Keep the exchange short, repeat the reference now and then for people tuning in, and note anyone who says they are hunting only WWFF so you can confirm their callsign cleanly. Also put the log into the same format as you go, if you can. Fixing 44 contacts at the end of a long day is how typos creep in.

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.