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 cross-band repeat, treat it as a feature you configure deliberately and test on a quiet frequency before relying on it. Two things cause most of the trouble: the antenna on the vehicle picking up its own transmission, and someone forgetting it is enabled. With a handheld talking into the mobile there is also the question of who is the control operator and how ID is handled, so check your licence rules instead of assuming. For noise, I'd add one step to the checklist: if the whine is on your transmitted audio but not on receive, look at the microphone cable routing and the power feed to the radio, not the antenna. If the noise is on receive only, go through the vehicle's electronics one by one. A cheap phone charger can be responsible for an alarming amount of hash on VHF. On etiquette, one thing that gets overlooked is the volume at the speaker. Mobile ops often run the audio loud over road noise, then key up in a quiet parking lot and blast anyone nearby. A small external speaker mounted closer to you helps with that.
  2. I'd treat real-time reports as the main evidence and the prediction tools as a planning aid. Solar flux and the K-index tell you the general conditions, but PSK Reporter or RBN tells you whether your signal is reaching a particular region right now. If a path looks open on a forecast but nobody is hearing you, believe the receivers. For cluster spots, a few habits cut down on bad chases. Tune to the frequency and listen before you call. Check whether the spot is recent, and whether more than one independent spotter agrees with the callsign. A single spot with an odd comment can be wrong. If the callsign looks unusual, a quick lookup on QRZ or HamQTH can show whether the operation is real or a spotting typo. Most clusters and web front ends let you filter by band, mode, or spotter region, which keeps the list readable. For alerts, a notification service such as HamAlert (which works with spot feeds and can push to a phone) is better than refreshing a page. You can set it for a specific callsign, a DXCC entity, or a POTA/SOTA reference, so you only hear about what you want.
  3. On studying, I'd combine a few things rather than pick one. The ARRL license manual is a good way to learn the material. It explains why things work, such as what a repeater offset is, why antenna height matters, and what the basic safety rules are. Understanding that makes the questions much easier than memorizing letters. HamStudy and similar apps are good for repetition. They drill the actual question pool and track which questions you keep missing. Use the practice exams as a check on your readiness rather than the whole plan. Know which question pool your session uses. The Technician pool is revised on a multi-year cycle, so confirm the effective dates and make sure your study material matches. If you use an older book with a newer pool, or the reverse, you may find some topics don't line up. The Technician exam is 35 multiple-choice questions, and passing is 26 correct. A sensible target is consistently scoring well above that on fresh practice exams, around the high 80s or better, rather than barely clearing it. Then you have margin for a couple of oddly worded questions. For freezing up: read every answer choice before picking, since the distractors in this pool are often built from real terms used the wrong way. Skip anything you're unsure of and come back. Don't change an answer unless you can articulate why the first one was wrong. After you pass. Watch ULS for your call sign, then listen before you transmit. Look up local repeaters (RepeaterBook is a common directory), find out which ones have open access or require a tone, and monitor a local net to hear how people check in. Identify with your call sign at the end of a transmission and at least every 10 minutes during a longer conversation. A handheld on 2 meters and 70 centimeters is a typical first radio. Joining a local club is probably the quickest way to get help with programming it and picking an antenna.
  4. On the Direwolf side, I'd separate three roles, because they get mixed up. Decoding and KISS output let other software use the TNC. Digipeating repeats RF packets according to rules you configure. iGating moves packets between RF and APRS-IS. You can run only the first, or the first and third, without ever digipeating, which is often the right choice for a home station that just wants to improve coverage for the area's data on aprs.fi. For a handheld like the TH-D74, TH-D75 or FT5D, remember that its built-in TNC is not a Direwolf replacement. It handles beaconing and messaging, but it does not give you the audio-level reporting, logging or iGate functions that a PC or Raspberry Pi running Direwolf does. Many operators use the radio as the mobile tracker and keep a separate receiver and Direwolf instance at home as the iGate. One last caution on weather: a wrong callsign or SSID on a weather station will make the data look like it comes from a different or nonexistent station. Give the weather station its own SSID, and keep the position and symbol consistent so it displays as a weather station and not as an unknown object.
  5. One check I'd add for equipment: compare the manufacturer's spec sheet against independent lab numbers where they exist. ARRL Lab test reports have long been a common reference for receiver measurements like blocking dynamic range and third-order intermodulation. Because they use a consistent method across radios, they're easier to compare than anecdotes. Marketing pages usually stick to features and leave out numbers that look unflattering. For antennas, be wary of gain claims on compact or multiband designs. Ask whether the figure is in dBi or dBd, what ground assumption was used, and whether efficiency is stated at the lowest band. A small loop or a short vertical can work well in the right situation, but the physics around size and efficiency doesn't change because the product page is glossy. Independent SWR sweeps and on-air reports from several locations tell you more than a single demo video. Also check what the update path looks like. A rig with an active firmware history and a clear support channel is a different purchase from one with a great launch and no follow-up.
  6. For nets, I'd say the biggest difference is between a casual net and a formal or emergency-style net. A casual weekly net can be relaxed, with chat and announcements. A formal net uses a tighter structure, such as a script, a defined check-in order and strict brevity, because the same format needs to work when people are stressed. If you're unsure which type a net is, listen to a session before checking in and read any published net script or guidelines the group offers. Some practical tips: have pen and paper ready, speak at a steady pace and use phonetics for your callsign, since net control may be copying a dozen stations. Keep your signal report or location short, and avoid long pauses after pressing PTT, so the first syllable of your callsign isn't clipped. If you're on a repeater, also leave a second of space before you key up so that others can get in with urgent traffic. And if you disagree with how the net is being run, don't argue about it on the frequency. Contact the net manager or organiser afterwards. Net control has enough to do without a dispute playing out live.
  7. On test gear, I'd split it into must-have and nice-to-have. The must-haves are a DMM, a dummy load, an RF probe (which is simple to build) and some way to see your own signal, either a scope or a receiver. A NanoVNA is useful for checking filters, measuring antenna impedance and sweeping crystal filters, though it doesn't replace a scope. If you're comparing the two, a scope shows you waveform problems such as clipping, oscillation and hum, while a VNA shows how a network behaves across frequency. A direct conversion receiver has its own quirks. There is no image rejection, so you hear both sides of zero beat. Strong AM broadcast stations can get into the audio chain, which is why a bandpass filter ahead of the mixer helps. Hum and microphonics are common, so look at your power supply decoupling, ground routing and any loose toroids or coax. Audio gain stages with an LM386 or similar chip can oscillate if you skimp on bypassing and layout. A Pixie-style rig is a good learning project, but remember that the single transistor doing double duty as mixer and transmitter finishes with poor receive performance and a transmit signal that needs a proper filter. With any transmitter built around a simple crystal oscillator and final stage, such as the Tuna Tin 2, check the output for harmonics, ideally with a spectrum analyzer or a known-good receiver tuned across the harmonic frequencies. Add a low-pass filter for the band, using the right toroid cores and winding counts from a design you trust. Spurious emission limits depend on your licensing authority, so check the requirements that apply to you. For SWR bridges, calibrate on a known load: a good dummy load should read close to 1:1, and an open or shorted terminal should give a very high reading. If the bridge disagrees with that, don't trust it with an antenna. Also remember that bridge sensitivity changes with power level, so a QRP-level reading may be less accurate than the same bridge at higher power.
  8. The split sounds sensible. I'd add one rule: anything that can damage something if it hangs should not depend on Linux. Keep the Pico (or a simple hardware path) in charge of PTT lines, relay states and any amplifier or antenna safety interlock. If the Pi is rebooting or a service crashes, the outputs should fall back to a safe state, which usually means receive and antenna grounded or selected by default. A watchdog on the Pico helps a lot here, and so does a pull-down or pull-up on each output so the relay doesn't chatter while the board boots. For the RF issue, I'd treat the cables as antennas. Common-mode chokes on USB and control leads, short runs to the rig, and a single-point ground at the operating position cover most cases. If you have a long USB run between the Pi and the rig, a USB isolator can also keep ground-loop hum out of Direwolf audio. For an SWR meter, put the detector right at the coupler and send a low-impedance DC voltage down the cable, not RF. Then filter it at the ADC input.
  9. On the FRS/GMRS/MURS side, I'd treat them as a family and neighborhood layer rather than a replacement for ham gear. The practical advantage is that anyone can pick up a radio and use it without a ham license. FRS works well for a household within a few blocks. If you want more reach, GMRS with a proper license and a better antenna is worth looking at, but terrain and buildings still limit range a lot. MURS is handy because it's unlicensed and VHF, though fewer people own those radios, so it's mostly useful if you buy them yourself and set them up in advance. The biggest issue with all three is a lack of plan. Pick a primary channel and an alternate, write them on the radio, and agree on a check-in time. Whatever you choose, keep a weather radio in the kit too. It's a one-way receiver, but warnings from NOAA don't depend on cell service or the internet, and that can matter when the weather is what caused the outage in the first place.
  10. One thing I'd add on mobile installs: the ground plane matters more than whip length. An NMO mount in the center of a metal roof gives the antenna a symmetrical ground plane and a clean pattern. A mount near the edge or on a trunk lip pushes the pattern off to one side and raises the takeoff angle. That is where a 5/8 whip can behave unlike its spec sheet. A quarter-wave is often a decent answer when the ground plane is mediocre. For mag mounts, the coupling is capacitive through the paint, so the surface must be clean and flat. Any dirt, grit or a thick film can cause SWR changes and scratch the finish. Also watch the cable: the thin coax on most mag mounts has noticeable loss at 70 cm, and routing it through a door seal can crimp it. A permanent NMO with a proper cable through a grommet is usually more reliable than a magnet for daily driving.
  11. For DXCC I would start with LoTW and treat everything else as a backup for the entities that don't show up there. LoTW needs no postage, there is no card to get lost, and you can see the result quickly. The usual reasons a QSO doesn't match are small: the log has the wrong band or mode, the time is off (a local-time entry that should have been UTC is a classic), or the other station just hasn't uploaded. Before you chase anyone, compare your own log against the QSL record. Also check which callsign and which date range your certificate covers. If you've held more than one call, or operated from a different DXCC entity, each needs its own certificate, and tQSL will refuse to sign QSOs that fall outside the certificate's dates. Old QSOs that sit in a log but never get uploaded because of that are a common source of confusion. For cards, I'd decide per station. If the operator uses Club Log OQRS and their page says bureau is fine, take the slow, cheap route unless you need the credit soon. If it's a rare entity and the QSO is one you may never repeat, a direct request is a reasonable cost. The one thing I'd avoid is sending several rounds of requests, because that just creates duplicate paperwork for a volunteer QSL manager.
  12. Good baseline. On the EQ question, I would treat any curve as a starting point for your voice and mic, not a universal recipe. A lift that makes a deep voice clearer can make a naturally bright voice harsh. A practical method is to make short recordings of yourself with one change at a time, such as cutting below 300 Hz, adding a bit around 2 kHz, or reducing compression. Then compare them, ideally listening through small speakers or an SDR the way a distant station would hear you. For DX, the other half is receive discipline. A narrower filter helps only if you tune accurately. Many weak signals disappear because the filter is centered a few hundred hertz off, so try shifting the passband before blaming the band. If the station you are chasing is very weak, drop the noise reduction a notch, use a slower AGC if it stops the band noise from pumping, and listen for several exchanges before calling so you know whether the operator wants a callsign only or a full report. And if a station tells you that you are splattering or sound distorted, do not go straight for more compression. Lower the mic gain and drive first, then rebuild the audio chain stage by stage.
  13. Good list. I'd add one more: how easy is it to sell later? That sounds boring, but it affects what I'm willing to buy. Mainstream models with lots of users tend to be easy to move if you change your mind. A rare or heavily modified radio might be wonderful, but it may take a while to find the right buyer, and the people who know what they're looking at will want documentation. For classifieds, a few things make a listing a lot more trustworthy: clear photos from all sides, a note on whether it's been tested on all bands and modes, a mention of any known faults, and a description of what's included, such as the manual, mic, power cable and original box. If a seller can't answer basic questions, that usually tells you something. As for the keeper question, I think the best radio is whichever one makes you want to get on the air. If a plain modern transceiver gets used every evening and a gorgeous vintage station sits cold, the plain one is the keeper. Nothing wrong with having both, though, if you have room on the desk and a power strip with enough outlets.
  14. On the rules: in the US, the FCC's station identification rule allows a phonetic alphabet but doesn't mandate one specific list. The wording is about using an easily understood phonetic alphabet, so the regulation doesn't force NATO words. Other countries differ, so check your own regulator. The practical standard is the ITU/ICAO/NATO list. Its words were chosen and tested to stay distinguishable across languages and noisy channels. The official spellings are Alfa and Juliett, and Whiskey, X-ray and Yankee round out the tricky ones. Improvised words are fine in a good-signal ragchew, and plenty of operators like a personalized suffix. The problem is that a station copying you through noise or an accent has to guess whether your word is meant as a letter. Words like "Lima" and "Mexico" are well known, but novelty words can be misheard as a different letter. For your callsign, especially when working DX or a pileup, the standard words win because the listener expects them. In difficult conditions the usual advice is to slow down rather than change the words. Say the callsign at an even pace, give it once or twice, and don't run the letters together. If the other station keeps getting one letter wrong, repeat only that letter with its standard word. The most commonly confused letters are B, D, P, T, V and E, plus M and N and F and S, so those are the ones where phonetics matter most. If the other operator suggests a different word for the letter, switch to it. The goal is that they copy it, not that you stick to a pet word. Older sets like "Able, Baker, Charlie" (a WWII-era list) or local police-style lists still turn up. Each has its own words, so mixing two systems in one callsign can confuse a listener. Pick one list per transmission.
  15. Here's the rest, plus the phone-versus-CW question. CQ is a general call to any station: "CQ CQ CQ de W1ABC W1ABC K". DE means "from" or "this is". K means "go ahead, any station." KN means "go ahead, but only the station I just named", so use it when you don't want other stations jumping in. SK ends a contact. AR ends a message or transmission. Prosigns like AR, SK and KN are sent as a single run-together character rather than as separate letters. BK means break, handy for fast back-and-forth exchanges. 73 means best regards. Many operators avoid "73s" because 73 is already plural, though you'll still hear it. 88 means love and kisses, and it's used between friends or in a lighthearted way, not as a standard sign-off to a stranger. RST stands for Readability (1 to 5), Strength (1 to 9) and Tone (1 to 9). Tone applies only to CW, so phone reports use just RS, for example "5 by 9" or "5 and 7." A CW report of 599 is the usual contest default, and many operators send it whatever they really heard, so a plain-language comment is often more useful on voice. Treat a report as an honest estimate if you want it to be useful. On phone, Q codes are used but less than on CW, and plain English is generally preferred because it's quicker to say and impossible to misunderstand. "QRZ?" and "QSY" are common on SSB, while saying "DE" is rarer than just saying "this is." Use the standard phonetic alphabet for callsigns on voice. On CW, abbreviations save keystrokes, so Q codes and prosigns are standard. For logs, record the date and time in UTC, band or frequency, mode, callsign, reports sent and received, and optionally name and QTH. Confirmations usually come through LoTW, eQSL, direct mail or a QSL bureau. On nets, the net control station (NCS) runs the session. Check-in is when you announce your callsign to join, and traffic means formal messages being passed. Some net-specific Q signals exist: QNI means a station is checking in or reporting to the net, QTC means you have messages to send, and QNX means a station is excused from the net. Nets may also use their own procedures, so listen first and follow what the NCS says.
  16. On the key question, there is no single winner. A straight key makes you think about timing for every element, and that can improve your sense of spacing. Paddles with an electronic keyer give consistent dits and dahs, which makes high speeds easier on the hand. A bug like a Vibroplex gives automatic dits and manual dahs, and it has its own swing and rhythm that takes time to learn. Newcomers often find a bug harder to send cleanly than either other option. If you use paddles, be careful about setting the keyer speed above what you can copy. It is tempting to send faster than you can receive, and then the replies come back at that speed. Keeping the sending speed close to your copying speed makes the exchange easier and avoids calling CQ at a pace that only gets answers you cannot read. For QSK, it helps to check the rig manual for the recommended settings. Some rigs and amplifiers handle full break-in without trouble, while others click or chatter. If the relays are noisy or the amp cannot keep up, semi break-in with a slightly longer hang time is a fine compromise.
  17. On 2 m and 70 cm, the array design usually decides how much you can do. Four reasonably long Yagis give a beam that is wide enough to be forgiving but still gives usable gain. Going to eight or more helps, but it brings tighter pointing requirements, a heavier mechanical load and a much more demanding feed and phasing network. Stacking distances and phasing line lengths matter more than people expect, because a mismatch in the harness wastes the gain you built the array to get. Receive performance usually matters as much as transmit power. A good mast-mounted preamp with a low noise figure helps only if you keep the loss ahead of it small, so the TX/RX relay and any filtering need to be thought through carefully. The preamp, relays and PA also need proper sequencing, so the amplifier never keys before the relay has switched and nothing is hot-switched. Sky noise matters too: on 2 m, when the Moon is in or near a hot part of the sky, the background noise may hide signals you could otherwise copy. Planning around that can save a lot of wasted time. For polarization on 2 m, being able to switch or rotate between orientations is far better than a single fixed linear. A common approach is two sets of antennas or cross-polarized elements with a switching or phasing arrangement. Some stations use polarization diversity on receive, which means two polarization channels decoded with software that can combine or pick between them. Even without Faraday rotation, two stations at different locations see the Moon's geometry differently, so there is always a spatial offset between their polarizations. A fixed polarization can therefore be a poor match even in the absence of ionospheric effects. On the software side, the main thing is to let WSJT-X do the Doppler correction and keep the rig frequency dial accurate. If the dial is a bit off, you will see it immediately in your own echoes, which is why Echo mode is a good routine check.
  18. They aren't really competing. Koch and Farnsworth answer different questions, and most modern trainers let you use both. The Koch method is about the order in which you learn characters. You start with just two characters sent at a fairly high character speed (commonly 18 to 20 WPM), so you never learn to count dits and dahs. Each character is a sound with its own rhythm. When you reach roughly 90% accuracy on the current set, you add one new character. The key point is that the speed of the individual characters never gets slowed down to make them easier. Farnsworth is about timing. Characters are sent at a faster speed, but the gaps between characters and words are stretched, so the overall speed is lower. This gives you time to recognize each character before the next one arrives. As you improve, you shrink the gaps until the spacing is standard. Used with Koch, you'd keep the characters fast and give yourself generous spacing at first. So the practical answer to your first question is to use Koch for the order of characters and Farnsworth-style spacing for how it's sent. Avoid the old approach of memorizing the whole alphabet from a chart at 5 WPM, because the characters then sound wrong once you speed up and you end up with a plateau. On resources: LCWO (Learn CW Online) is a browser-based trainer built around the Koch method. It tracks your lessons and has other exercises such as callsigns, abbreviations and plain text. G4FON's Koch trainer is a downloadable program that does the same core job and lets you customize settings like pitch and spacing. Either is fine; pick one and stay with it for a few weeks before switching. Check each site for its current features, as these things change. A sensible routine is two short sessions a day, around 10 to 20 minutes each, rather than one long one. Short and frequent beats long and rare, and fatigue makes your accuracy numbers meaningless. Set the tone somewhere comfortable, often 500 to 700 Hz, and keep it consistent so your ear isn't relearning pitch.
  19. Power and noise are where I would put money first. People often chase receiver mods when the real issue is a noisy DC supply, a bad ground, or a long coax run with no common-mode choke. Putting a choke at the radio end and, where practical, at the feedpoint is cheap and easy to test. Try the change in isolation and compare the noise floor before and after, so you know what actually helped. On batteries, I would be especially cautious with generic packs and unprotected cells. A proper pack with protection, correct charging and a fuse where required is a safe mod. A pack with unknown cells wired into a radio that can pull high current on transmit is a risk to the radio and to the person using it. For 12 V LiFePO4 setups, remember that the voltage curve and cutoff behavior differ from lead-acid, so check what your radio does at the low end. On TCXO and firmware, I would add one note: write down what you changed. Keep the original codeplug, the firmware version, the oscillator part number and the calibration offset. If audio or frequency accuracy goes wrong later, you will know whether it was the mod, a firmware change or a setting that got reset. Documentation also helps if an agency or club asks what has been done to a radio before it is approved for use.
  20. For a mixed bag of parks and the occasional hike, the EFHW usually wins on convenience, mainly because you can move around the band and chase spots without touching the antenna. Where it goes wrong is a poor setup, not the design itself. Wire tangled in brush, a transformer sitting on wet ground, or a tuning that was done at home with the wire at a different height can all push SWR around. It's worth checking the final SWR with the antenna deployed the way you'll really use it, then marking the wire or noting the settings so you can repeat it. If you go EFHW, I'd add a choke at the radio end and carry a short spare counterpoise wire. That's lighter than most people expect and it can fix a lot of odd behavior. Put the feedpoint up off the ground rather than lying in grass if you can, and keep the coax run short so the shield isn't doing the counterpoise job by accident.
  21. On the RF side, WIDE1-1,WIDE2-1 is the usual compromise for a mobile. Fill-in digipeaters answer to WIDE1-1, and wide-area digipeaters pick up WIDE2-1 after that. If the area is dense with digipeaters, a single hop such as WIDE1-1 alone is kinder to the channel. Long paths like WIDE3-3 or more multiply every packet across a large area, so they are best avoided on a shared 1200 baud frequency. SmartBeaconing is worth using on a moving station. The key parameters are the fast speed with its fast rate, the slow speed with its slow rate, minimum turn time, minimum turn angle, and turn slope. The idea is frequent beacons at speed and on corners, and sparse ones when slow or stopped. Parked at a trailhead, a fixed-interval tracker sends the same position again and again, and SmartBeaconing avoids that. The defaults are a reasonable starting point, but tune them to how you actually move. Walking, cycling and highway driving want quite different values. Mic-E packs the latitude into the destination address field and puts longitude, speed and course in the information field, along with a symbol and a standard status code (such as In Service or Emergency). The result is a short packet, which matters at 1200 baud where every extra byte adds airtime. The receiving side decodes it into an ordinary position, so it should look normal on aprs.fi. If you open the raw packet you will see an odd-looking destination callsign, and that is the encoded latitude, not a mistake. For handhelds, keep the transmit side realistic. A small rubber duck at body height with 5 W or less is a weak APRS station next to a mobile with a roof antenna. Check that the unit is set to 1200 baud for 144.390 and not a 9600 mode, and that the GPS has a fix before blaming the path. Also set the beacon comment and status text to something short. Long comments make longer packets, and that load adds up.
  22. My advice is to keep one master log with fields for everything you might need later, and treat each award as a report, not a separate record. Store the DXCC entity, CQ zone, ITU zone, state or province, IOTA reference and POTA/SOTA reference on every QSO that has them. Then you can run the same data through the ADIF export for LoTW, the Marathon, WPX and so on without retyping anything. The big trap is that country and zone fields are often filled in automatically by a lookup against a prefix list. That works until you hit an exception, such as a station operating from a different entity than its callsign suggests, a special event call, or a DXpedition. Anything unusual deserves a manual check. Compare the entity in your log with what the operator actually signed or what the DXpedition's own page says. For Challenge, I'd separate 'worked' from 'confirmed' clearly. Keep a status field per QSO (not confirmed, LoTW, card, or other) so you can filter easily. Otherwise you end up guessing what's missing when you want to push for the next 100 points.
  23. Adding a few related points on lookups, clubs, special events, and keeping the call, since those usually get missed. For lookup, the authoritative source is the FCC's ULS license search. You can search by call, name, or FRN. Third-party sites like QRZ-type directories are convenient for checking a call quickly, but they mix FCC data with whatever users submit and may lag behind. If you're checking vanity availability, confirm the status in ULS itself: look at the license status, the expiration or cancellation date, and whether anything is pending. A call that looks open may still be in its two-year waiting period or tied up in another pending application. Club stations work a little differently. A club license is held through a trustee, who is a licensed individual responsible for the station, and the license is a separate record with its own call. Clubs can pursue vanity calls too, but the eligibility rules for club stations are laid out in Part 97, so read the current wording of the rule and the FCC instructions before filing. Don't assume the trustee's own class settles it. Make sure the trustee's contact info and the club's records stay current, since a lapsed club license goes through the same expiration and waiting-period process as an individual one. One-by-one special event calls (the 1x1 type, such as K1A through W9Z) are not obtained through the vanity process. They are coordinated through a separate volunteer-run special event program, usually tied to a short operating period. They also have to be requested through the sponsoring coordinator, so look up who currently runs it and what the application window is. Don't assume ULS will handle it. For holding a call, the practical rules are straightforward. The license term is ten years. You can renew within the window before expiration. If you miss it, there is a grace period after expiry during which you can still renew but cannot transmit. Keep your mailing address and email current with the FCC, because that is where notices go. Identify with your call at least every ten minutes during a contact and at the end, as Part 97 requires. If you want a different call without pursuing vanity, ULS also has an option to request a sequential change, which gives you the next one in the sequence for your region. Be sure that's what you want, because it replaces the call you have now.
  24. For gear and convention coverage, I'd separate three things: what was announced, what's actually shipping, and what real-world reports say. Hamvention and other big shows are good for hands-on time, comparing front-end behavior side by side, and talking to manufacturers about support. But booth enthusiasm isn't a review. Ask about firmware update policy, whether there's a published roadmap, and how long a product line typically gets supported. Dates and exact venues vary, so check the official show site before planning a trip. With firmware, one cheap precaution is to wait a bit after a release and see whether owner groups report problems with CAT control, CW keying, or SDR panadapter behavior. When you do update, save your configuration and download the file only from the manufacturer's own page. For club news and awards, I think local sources are underrated. Club newsletters, net announcements and Field Day or special-event station pages often cover things the national outlets never mention. DXCC, WAS and contest award rules do get revised, so check the sponsor's current rules page instead of relying on a forum summary, even a good one like this thread. As for trends, it's hard to measure them reliably. License-exam volumes, club membership, and what shows up in the used-gear market give some signals, but I'd treat any single anecdote as just that.
  25. One thing worth adding is that ALC behaviour varies between radios, so "ALC just flickering" is not a universal rule. Some rigs show it as a bar graph, some have a defined acceptable zone, and some work differently when the processor is on. Check the manual for your model, then verify with an independent receiver or SDR. A meter reading alone does not tell you whether the signal is clean. For the processor, a useful test is to record a minute of normal talking with it off, then with a low setting, then a high setting. Play them back at the same volume. The high setting may sound louder, but you will often hear more noise, breath and room reflections. That is a good reminder of what the person at the other end gets when the band is already noisy.

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.