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.5
Wind 385.0 km/s
Aurora 1
Updated 13:00 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. For club meetings, a mix of formats tends to hold interest better than the same agenda every month. A short business section, then a program: a talk, a demo, or a hands-on build. Even a ten-minute "show and tell" of someone's station project can start useful conversations. If your club has newer hams who don't speak up much, assigning an Elmer to introduce them around is low-effort and effective. On Field Day, it helps to have a few jobs that don't require a license. Setup, logging, food, greeting visitors and taking photos all give non-operators something useful to do, and some may end up wanting to get licensed. If you're also hosting a VE session around then, put the schedule and any registration requirements in the announcement so people know what to bring. As for club projects, simple ones usually work best: a portable go-box, a J-pole antenna build, a shared Winlink or digital-mode demo, or a field-ready antenna kit. Pick something people can finish in a meeting or two. Which of those would your group be most likely to take on?
  2. For the VHF/UHF side, the same idea applies: Part 97 defines the band limits, and the band plan tells you how each part gets used. All Technician-and-above licensees have full privileges on 6 m, 2 m, 70 cm and 33 cm (with a CW-only restriction on 50.0–50.1 MHz and some power and geographic limits you should check). So the band plan is the main thing you need to follow. 6 m (50–54 MHz): the bottom of the band is for CW and beacons, then the weak-signal SSB region starts around 50.1 and includes the DX window. 50.125 is the common SSB calling frequency, and 50.313 is the FT8 dial frequency. The national FM simplex calling frequency is 52.525. Repeaters sit higher in the band. If you want to hear anything when the band is open, tune the bottom and the weak-signal end and not the FM end. 2 m (144–148 MHz): 144.200 USB is the SSB calling frequency, and the weak-signal segment is below about 144.275. 144.174 is the FT8 dial frequency and 144.390 is APRS in North America. The famous simplex calling frequency is 146.520 FM. The ARRL plan puts general simplex in 146.40–146.58 and 147.42–147.57. Repeaters use a standard 600 kHz offset: outputs from 146.61 to 146.97 transmit with the input 600 kHz lower, and outputs from 147.00 to 147.39 transmit with the input 600 kHz higher. Don't use a simplex frequency in the middle of a repeater block just because it sounds quiet. 145.800–146.000 is reserved for satellite use. 70 cm (420–450 MHz in the US): weak-signal work centers on 432.100, and 446.000 is the national FM simplex calling frequency. Repeaters typically use a 5 MHz offset. This band is secondary in the US and shared with other services, so you could see interference from radiolocation systems, and you should be aware of the geographic restrictions near some government sites. 33 cm (902–928 MHz): it's a Region 2-only allocation, so you won't find it on the band charts of other regions. It's shared with ISM devices, Part 15 gear and location monitoring systems, and the noise floor can be high. Weak-signal operation is near 902.1 and there's FM and repeater activity elsewhere in the band, but this is the one band where I'd check the ARRL band plan directly, and also ask local clubs, because use varies by area. For international operation, the ITU divides the world into three Regions and the allocations differ. 40 m is 7.000–7.300 in Region 2 but only 7.000–7.200 in Regions 1 and 3. 80 m is 3.500–4.000 in Region 2 but 3.500–3.800 in Region 1. 2 m is 144–148 in Regions 2 and 3 but 144–146 in Region 1. 70 cm is 430–440 in Region 1, with 420–450 in the US being a national situation. If you operate in another country, the rules of that country apply, and what your license class allows at home doesn't automatically carry over. Many countries have reciprocal licensing or CEPT arrangements, so look up the specific agreement and the power and band limits for that country before you transmit.
  3. One point worth adding about the spectrum display: FFT size and sample rate change what you see as well as what you hear. A wide span with a small FFT gives coarse resolution, so a weak narrowband signal can be hidden in a bin that also holds a lot of noise. Narrowing the span or increasing the FFT size reduces the resolution bandwidth, and the noise per bin falls, so weak carriers can pop out of the waterfall. Averaging helps too, though it slows the display. That is useful when comparing two antennas, because you want a fair test: the same span, FFT, averaging and gain on each antenna, and ideally a quick A/B switch rather than moving the cable around. On the overload test, it is worth also checking with a band-pass filter or a notch in place before touching gain. If the spurs vanish with a broadcast FM notch, you have found the cause immediately. That is a more informative test than just turning the gain down, because gain reduction also hides weak wanted signals.
  4. I'd put live evidence first and use predictions to explain it afterward. The indices are an overview, and a spot map is a measurement of one actual path. If a 20 m WSPR map shows copy into the target region at reasonable SNR, that settles the question for that moment, whatever the K index says. That said, the predictions earn their place in planning. A VOACAP chart can show that a path should open about an hour after local sunrise at your end, so you know when to start listening instead of sitting on a band all day. It also helps when you change antennas or power, because you can see how much of the gap is the circuit and how much is your station. One caution about WSPR and PSKReporter data: they show where stations are listening and transmitting. A lack of spots can mean nobody is there to hear you, particularly on a band with little activity. Look at how many receivers are active in the area before you decide it's closed. Beacons help with this because their schedule and power levels are known, and the NCDXF sequence of decreasing power steps gives a rough sense of how strong the opening is. If you hear the 100 W transmission but not the 10 W one, the path is marginal.
  5. until

    The 52nd Orange Hamfest is a two-day, ARRL-sanctioned event on Friday and Saturday, February 26–27, 2027, hosted by the Orange, Jefferson County and Beaumont amateur radio clubs. Hours are 1:00 PM to 6:30 PM on Feb. 26 and 7:00 AM to 2:00 PM on Feb. 27. Friday afternoon opens general admission, the flea market, dealers and tailgating. Saturday adds programs and forums.Location: Orange County Convention & Expo Center, 11475 FM 1442, Orange, Texas 77632, USA Organizer: Orange Amateur Radio Club, Jefferson County Amateur Radio Club and Beaumont Amateur Radio Club Source: Event information
  6. I'd lean toward keeping anything safety-related in hardware where you can. A relay antenna switch can have a simple hardware rule: if the PTT line is active, the relay drivers are blocked, regardless of what the firmware asks for. A diode and a transistor, or a small logic gate, can do that and it doesn't care if the Pico locks up. Pico versus ESP32 mostly comes down to whether you need Wi-Fi. The Pico's PIO is useful for odd timing jobs, like generating clean keying waveforms or reading a pulse-based rotator feedback. The ESP32 is attractive for a web UI, but its Wi-Fi radio makes supply decoupling and layout matter more, especially if the same board also reads a sensitive ADC for forward and reflected power. If it only needs to serve a status page, it can live in a separate box with a network link and be kept away from the metering electronics. On the ADC point, the ESP32's built-in ADC is known to be nonlinear and noisy, so for SWR work I'd use an external ADC like an ADS1115 over a short I2C run, or at least average a lot of samples and calibrate against a known dummy load and power meter.
  7. For special event stations, the main rule is to find the official details before you start calling. The event page will usually say which call sign or calls are in use, the bands and modes, the operating dates and any certificate rules. Some operators work split, so listen first to find where they're listening before calling on the transmit frequency. If a cluster or spotting network shows the station, use it as a hint, but confirm by ear that you're calling the right station. Special event call signs vary by country. In the United States, many event stations use short special event call signs (the 1x1 format) that are issued for temporary use. Elsewhere you may see a commemorative prefix or a special suffix tied to an anniversary or celebration. Either way, log the full call exactly as heard, not as you assume it should be, and note the band, mode and UTC date and time. That makes it far easier to claim a certificate or confirm a contact later. Certificates are handled in different ways. Some are free downloads after you request one online, some require a QSL or a specific number of contacts, and some ask for a self-addressed envelope or a fee. Don't assume an event will upload to LoTW or Club Log. Check the event page for the confirmation method and the deadline for requests, then keep your own log in case you need to show a contact. Finally, remember the operators are often running a tight rate and handling lots of callers. Short, clean exchanges (call sign, signal report, and anything the event asks for) keep the line moving and help everyone log the contact accurately.
  8. I'd add Club Log to the planning side. Its Most Wanted list gives a rough picture of which entities are scarce for the logs uploaded to it. It is not a measure of who is rare overall, but it helps when you are deciding which opportunities are worth the sleep you are about to lose. Many DXpeditions also publish a Club Log search page, so you can check whether your QSO made it into the log. If you do not see yourself, wait before you panic, because uploads can lag. If you still do not appear after a reasonable time, check the operation's QSL instructions for how to report a possible bust or missing QSO. On the planning side, it helps to remember that targets like Clipperton and Bouvet have a limited operating profile. Teams are working with permits, transport, weather and power constraints that most of us never see. If you want to give yourself the best odds, be ready for the band openings that are likely to favor your path, not just the ones with the most spots. Check your antenna, your rig's split settings and your logging software before the operation, not during it. On etiquette, the same few points come up every time. Do not call when the DX is not listening, do not tailend a QSO in progress, do not tell other stations to be quiet unless there is a real reason to, and do not keep calling after the DX has clearly moved on to a different region or band. Following the DX operator's instructions, including when they ask for a particular continent or call area, is part of the game and makes the pileup work better for everyone. How do others manage the trade-off between spotting and listening on the DX's frequency before they act on a spot?
  9. The most important distinction is that there are two layers. Your license privileges come from the FCC rules (Part 97 in the US) and are legally binding. Those cover which frequencies, which modes and how much power your class allows. The ARRL band plan is voluntary. It is a consensus on how to share the spectrum so CW, digital, SSB, beacons and satellite traffic don't trample each other. You won't get a notice for running SSB in the middle of the FT8 watering hole, but you'll be unpopular and probably unintelligible. Stepping outside your class privileges is a different matter. On HF, the pattern by class is roughly this. Technicians get CW privileges in segments of 80, 40 and 15 meters, plus 10 meters (CW/data in the bottom part, SSB in the upper part of the lower portion) with a 200 W PEP limit. Generals get most of each HF band, with phone segments that start higher than Extra's on 80, 40, 20 and 15 meters. Extras get everything, including the bottom slices of the phone bands. Because the exact edges differ band by band (and 30 meters is CW/data only with a lower power limit), don't memorize them from a forum post. Print the current FCC privileges chart or ARRL's band chart and check it when rules change. The band edge question is mostly about sidebands. The dial frequency on SSB is the suppressed carrier, not the edge of your signal. On LSB, the signal extends below the dial, so near the bottom of a phone segment you need to sit a few kHz inside it. On USB, the signal extends above the dial, so near the top of a segment you need to stay a few kHz below the edge. A voice signal commonly occupies around 2.4 to 3 kHz, and the dial readout may have some error, so leave extra margin. Digital modes are similar. The transmitted audio tone offset is added to the dial frequency, so your actual RF edge is the dial plus the highest tone in the passband. The 60 meter band is different in the US because it has historically been channelized rather than being a continuous band. General and Extra operators can use a handful of specific channels, and the rules call for USB for voice, a limited occupied bandwidth, and a low ERP limit relative to a dipole. The dial frequencies commonly cited are 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz. Check §97.303 and current ARRL guidance before relying on that list, since 60 meter rules have been revised over the years and may change again. Other countries often have different 60 meter allocations, so you can't assume the US channels exist elsewhere.
  10. Adding to the decoding side: a clean-looking waterfall is not the same as a decodable signal. For WSJT-X modes you need stable frequency and a sensible audio level in the decoder. Digital modes also have tight timing requirements, so a clock-synced PC matters as much as the radio. With pager or ADS-B tools, running the SDR at high gain makes false decodes and missed messages more likely, because intermod products and compression distort the signal. It's worth stepping through gain settings with a known strong signal, such as a local ADS-B stream, and keeping the one that gives the most valid messages rather than the highest peak on screen. On the panadapter point, one caveat: if you tap the IF of a transceiver, the span and centre frequency depend on that IF, so some software needs a configured offset or a dedicated plugin. Using an SDR in the receive path versus a bandscope view are different tasks, and it's worth being clear which one you're building before choosing the hardware.
  11. To add to that, I'd divide the study plan into three passes rather than reading the whole book once. First pass: take a full practice exam cold, without studying. It will show which topics are weak. Many Technicians find that electrical principles and antennas feel harder than the rules questions, because the Technician exam includes less math and less theory. Second pass: study by topic and keep an error log. For each missed question, write down why the right answer is right. For electrical principles, that means being comfortable with Ohm's law, power calculations, series and parallel resistance, and decibels. You'll also see basic filters, resonance, and impedance matching. You don't need advanced math, but you do need to be able to work through the simple formulas without hesitation. For antennas, learn the relationships that keep reappearing. A half-wave dipole's length depends on frequency (shorter at higher frequencies). A quarter-wave vertical depends on its radials or ground system. Feed line and SWR questions often ask what a high SWR means for loss or for transmitter protection, not just what the number is. Directivity, gain, and the effect of antenna height on takeoff angle also come up. For digital modes, know what separates the common ones (FT8, PSK31, RTTY, Winlink/Pactor-style modes) and which parts of the band they usually occupy. Understand terms like baud rate versus bandwidth, and what AFSK or FSK means for the signal you produce. Also review data-mode power limits on bands where they apply. For operating practices, expect questions on band plan etiquette, station identification, which sideband is conventional on which band, third-party traffic, and control operator responsibilities. These are often the easiest points on the exam because they're straightforward after one good read-through. Third pass: take several timed practice exams from the current pool and aim to score comfortably above 26 correct. Passing practice scores consistently in the high 20s or 30s is a better sign of readiness than one lucky pass. If your session scores keep landing near the line, go back to your error log, not to the textbook from page one.
  12. I'd start by sorting tools by what decision they support. If the question is "what should I call right now," use a spotting source. If it's "is my signal getting out," use PSK Reporter or RBN. If it's "who was that and where are they," use a callbook. Mixing those up is where people get misled. One common mistake is reading cluster spots as proof of an open path to you. A spot from a station in another country may reflect a path that doesn't exist at your end. Many cluster interfaces let you filter by the spotter's region or grid, so you only see spots from stations near you. That's a much better proxy for what you might actually hear. On lookups, QRZ.com and HamQTH both provide callsign data and logbook features, and both can be integrated with logging software. A free account will give you basic lookups, while some features such as XML data access need a paid QRZ subscription. HamQTH is free and has its own lookup interface. The practical thing is to keep your own address and grid data current on whichever you use, because other operators' logging software may pull from it. For POTA and SOTA, the main thing to remember is that spots are often posted by the activator or by hunters, so they can lag behind or be incorrect. A spot saying 14.285 MHz SSB doesn't guarantee they're still there. Tuning around the frequency, listening for the callsign and reference, and checking the latest comment on the spot is better than trusting the number alone.
  13. On the transmit side, I'd push the SWR bridge and dummy load step a little harder. A bridge is useful, but a homebrew one needs to be calibrated or at least sanity-checked. With a good dummy load it should show a very low reflected reading, and with the load open or shorted it should show a high one. If it doesn't do both, don't trust it for antenna tuning. Also, bridge readings at very low power can be misleading because diode detectors are not linear at low voltage, so test at the power you will actually use. For the uBITX and similar modular kits, I'd also separate the questions "is the radio working?" and "is the output clean?". Plenty of boards will make power and still need attention to filtering, drive level and spurs. Keep drive within a range where the final is not being compressed, check each band's low-pass filter setting, and look at the output with an SDR through a proper attenuator. A clean-looking waveform on a scope can still hide harmonics that a spectrum view makes obvious.
  14. For the 44 contacts, the biggest factor is usually where you spend your time on the band, not how much power you run. Pick a clear frequency, spot yourself, and keep your calls short and rhythmic. In a good run, give your callsign, the reference occasionally, and a quick signal report, then move on. Naming the reference every time slows things down. Doing it every few contacts is usually enough for hunters who are checking spots. If the band is slow, moving between modes helps. CW and FT8-style digital modes can reach hunters who would never hear a low-power SSB signal, and a mixed-mode log still counts toward the total. Ask on the thread or check the current rules to confirm how multiple modes and bands are treated. Also check whether the contacts must fall inside one UTC day or can be spread over several visits, because this is exactly the kind of detail that changes. On the hunter side, a few habits help. Keep a note of each reference you have worked, check spots before calling, and log the exact reference exactly as the activator gave it. Awards and diplomas rely on accurate logs, so small typos in the reference number can cost you credit. Then look at how the WWFF logger or log search shows your contacts. If something looks wrong, tell the activator promptly so they can fix the log before you submit an award claim.
  15. On filters, I'd test before buying. Modern rigs differ a lot in front-end design: some are direct-sampling, some use a roofing-filter superhet architecture, and some are hybrids. Local interference may come from a neighbor's transmitter or from a nearby switching supply, so a band-pass filter is not always the right answer. Check attenuator and preamp settings first, and use a dummy load and a short test antenna to see whether the noise comes from the shack itself. If you do add band-pass filters, check their power rating and what they do to the SWR the radio sees outside the passband. Watch the amplifier handshake too. Band data or a keying line that isn't wired correctly can send an amp to the wrong band and cause damage, so confirm the interface before applying full power. For layout, I'd keep the power cables, coax and USB/audio cables separated where possible, and cross them at right angles if they must meet. A ground bus behind the desk with short bonds to each chassis tidies up a shack, but it mainly serves safety and fault current. RF behavior depends mostly on what the antenna and feedline are doing.
  16. For the Direwolf box, the minimum is small. Define the audio device, set MYCALL to your callsign with an SSID, use MODEM 1200 on the channel, and add an IGSERVER entry with an IGLOGIN using your callsign and APRS-IS passcode. If it is also a digipeater, add a DIGIPEAT line, and only enable the aliases you actually want it to answer. A fixed station can beacon rarely. Every 30 minutes or so is plenty, because it is not moving. Check the Direwolf documentation for the exact PBEACON and IGTXVIA syntax, since the option names matter. An RX-only iGate is a perfectly good first step. Turn on RF-to-IS gateway behavior and confirm that packets reach the Internet before enabling any IS-to-RF gating. Gating internet traffic back to RF should be limited to messages for stations you have recently heard locally, so you don't push internet traffic onto the channel. Leaving it off is fine at first. aprs.fi's raw packet view is the best debugging tool. In the path you will see which iGate passed the packet to the internet, usually shown with a qAR or similar q-construct followed by its callsign. An asterisk on a digipeater callsign in the path means that digipeater actually repeated the packet. Together these tell you whether your packet was digipeated, gated, or both. For weather, the station sends a weather symbol with wind direction and speed, gust, temperature, rain, humidity and barometric pressure in the standard formats. Direwolf doesn't read the sensors itself. You need a separate program that produces the APRS weather data, and you must set the beacon interval sensibly, since every report is airtime. Objects start with a semicolon, a nine-character padded name, and a live marker (an asterisk). A killed object uses an underscore. Messages carry the addressee in a nine-character field, then the text, then an optional message number used for acknowledgements. Text is limited to 67 characters, so keep messages short. Retries are automatic until an ack arrives, which is another reason not to send long chatty messages over a busy RF channel. Test messaging between two radios of your own before relying on it, and note that different handhelds handle message acks and group messaging a little differently.
  17. On leaving a run, a rule of thumb that works for many people is to watch the trend, not the instant rate. If your 10-minute rate drops to roughly half of your 60-minute rate and you're getting no better response after changing your CQ speed or timing, start thinking about moving. The exception is when you're working a clean pileup of rare multipliers. That frequency is worth more than the rate window suggests, so stay. For multipliers, it helps to keep a short list of the ones still needed on each band. With the multiplier window in N1MM Logger+ and a band map, you can usually tell at a glance whether the next few minutes are better spent running or hunting. It also stops you from chasing a multiplier you already worked on that band when the rules count them per band. For SO2R, I'd put filtering and audio ahead of anything else. A cheap fix like a good headphone switch and consistent audio levels often improves your accuracy more than a fancier keyer setup. If you can hear radio 2 clearly while radio 1 is calling CQ, you'll find multipliers faster and make fewer mistakes when you switch.
  18. One thing worth adding to the power check is voltage drop. Measure from the supply terminals to the rig's input terminals while transmitting. Even a few tenths of a volt lost in a cigarette-lighter plug, a thin lead, or a worn Anderson-style contact can make a rig misbehave on transmit. Low voltage can cause low output, distortion, a resetting micro, or protection circuits tripping. It can look like a rig fault when the real problem is in the cable. For no-receive faults, I'd go stage by stage from the antenna jack toward the speaker, and the service manual's block diagram is the map for that. A signal generator at a known level into the antenna port, with a scope or an audio meter on the speaker output, lets you work out roughly where the signal disappears. If the manual has test points or expected voltages, use them. A DMM covers the DC side: supply rails, bias voltages, AGC or mute lines, and relay drive. A stuck mute or squelch line can look like a dead receiver. For cleaning contacts, use contact cleaner sparingly on switches and pots, and avoid soaking nearby plastics or trimmers. Isopropyl alcohol works for flux residue and dirt on boards. If a fault changes when you tap the board or wiggle a connector, look at connectors, ribbon cables, and cracked solder joints before touching any components.
  19. On CAT, the rule is that only one program can open a physical serial port. Everything else has to talk to that one program or to a splitter. Common patterns: Let a rig-control layer own the port (flrig, Hamlib's rigctld, OmniRig, or DXLab Commander if you use DXKeeper). Then point the logger and WSJT-X at it as clients. Alternatively, use a virtual serial port pair or splitter so each program gets its own virtual port. The rig-control layer approach is usually more stable, because a splitter adds one more thing to break when Windows renumbers ports. For PTT and keying, check whether you want it through CAT, a separate RTS/DTR line, or a hardware interface. Contest CW and digital modes often use different methods, so test each mode before the event, not during it. Also confirm baud rate, stop bits and the rig's CAT menu settings match on both ends. For rotators, treat it the same way. One program talks to the controller (for example PstRotator or the controller's own software), and the logger sends bearings to it. If the logger shows a beam heading but the rotor does not move, check whether another program is holding the port or whether the controller expects a different protocol. On the WSJT-X side, N1MM+ can receive logged-contact broadcasts from WSJT-X over UDP, and WSJT-X has a Reporting tab with options for logged-contact ADIF broadcast. The ports on both ends have to match, so read the current documentation for both programs before relying on it. Then pick one program as the receiver and leave the other logging paths off. Running JTAlert, GridTracker and a logger all auto-logging the same QSO is a classic source of duplicates.
  20. From the chaser side, a few things make life easier for people at home. First, keep SOTAwatch open and filter by band and mode if the interface allows it. Second, when you work an activator, log the summit reference as well as the call. Third, don't assume that because there's a pile-up you'll be heard first. Activators are usually trying to hit four contacts quickly, then work whoever's left, so short exchanges are appreciated. The Shack Sloth number is mostly a matter of persistence over time. There's no need to chase every spot. Working a mix of bands and modes keeps it more interesting, and it's worth checking whether your own stations can actually reach the summits you see spotted. Low-power CW with a decent antenna can do surprisingly well, but it's easier on some bands than others. On the activator side, spot yourself clearly, give your frequency, and keep your exchanges short and consistent. A common courtesy is to take a spot down or note QRT when you finish, so people aren't calling an empty frequency. Also, check the current rules for any restrictions on power sources and transport before you go, because they matter for whether your activation is valid. As for what to leave at home: heavy tuners and big batteries you won't use, and extra coax you don't need. Keep the radio cable short enough that you can sit in a sheltered spot rather than stand in the wind at the highest rock.
  21. On the ranked list: the order is everything, because the FCC grants the first choice that is both available and one you're eligible for. Check each call in ULS before you rank it. If a call shows as held by someone else, or it's in the waiting period after an expiration, it doesn't help to list it unless you expect it to clear before your application is processed. Spread the list across groups you're eligible for, with your top choice first. Also check that the call is actually allowed for your class. An Extra can reach for a Group A 1x2 or 2x1. A General or Technician can't, no matter how much they want it, so don't fill your list with those. As for keeping a sequential call, it's fine. The sequential assignment is a perfectly valid call sign and has no operating disadvantage. Vanity calls are about personal preference, such as initials, a short call for CW, or a call that is easy to say on phone.
  22. One thing I would add for newer operators is to write down your callsign and phonetics before you get on the air. When you are nervous, it is surprisingly easy to stumble over your own call, and the other station only gets one or two chances to hear it. Keeping a small note by the radio for your call, your grid or location, and your basic exchange takes the pressure off, and it makes your transmissions cleaner for the stations copying you. On the break-in question, I think simply saying your callsign in a gap is the most universally understood method, and it works on both HF and repeaters. Where "break" makes sense is when your local repeater group or net has a documented convention for emergency use. It is worth checking the repeater's rules page or net script, because some groups spell this out explicitly. Another habit that helps on nets is to wait a beat after the NCS finishes before you key up. That tiny pause avoids doubling, and it lets the repeater drop its carrier and reset if it uses a timer or courtesy tone.
  23. On the alphabet itself, the letters are the same list across NATO, ICAO and ITU use. The ITU form is the one the amateur service points to. The full list is Alfa, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu. These words were chosen because they stay distinguishable across many languages and through poor audio. In the US, Part 97 encourages a standard phonetic alphabet for station identification, but as I read it, it does not require one. Other countries' rules differ, so check yours. The practical trouble with improvised words is that they only work when both ends share the same mental list. "Nancy" for N is fine between two people who grew up with it. A listener who has never heard it, or who is copying in a second language, may hear nothing useful. Using the standard words keeps the other station from having to decode your choice as well as your callsign. Numbers work differently. The formal radiotelephony pronunciations (tree, fower, fife, niner) come from aviation and maritime use. On amateur voice, most people say the digits normally. "Niner" is the one that has spread widely, since "nine" can be mistaken for "five" in noise and sounds like the German "nein". If you are working a station that is struggling, switching to clear, separated digits helps more than any special pronunciation.
  24. I'd add that a rig can be a keeper simply because it's fun to operate, and that's a perfectly good reason. Ham radio is a hobby, and there's no rule that every piece of gear has to be the most efficient choice. Where it gets practical is the trade-off with noise. If a vintage radio has no good way to manage local interference, a modern DSP radio can make a noisy location workable, and that can matter more than nostalgia. A lot of people end up with both: a newer radio for the tough conditions and an older one for relaxed operating. The question I'd ask is which one you actually turn on most days, because that one is your real keeper.
  25. Here is the linking side. The important point is that "linked" can mean several different things, and each changes how you should operate. EchoLink, IRLP and AllStarLink are all voice-over-IP systems tied to analog FM repeaters or simplex nodes. EchoLink requires callsign validation and uses node numbers and conference servers. IRLP uses node numbers and reflectors, and commands are sent by DTMF. AllStarLink is built on Asterisk, uses node numbers, and lets one node connect to others or to hubs, again controlled by DTMF. Wires-X is Yaesu's system for System Fusion (C4FM) and uses a gateway node connected to "rooms." Each of these has its own control codes, and the owner may restrict who can connect or disconnect. Don't send commands unless you know the local rules, and ask on the air before dropping a link that someone else may be using. Linked systems have more delay than a standalone repeater, and the audio may be going to many places at once. Leave a longer gap between overs, avoid private side conversations over a wide-area link, and say clearly if you want a local-only QSO. Some repeaters announce the link status or have a courtesy tone that changes when a link is up. If you don't know what a given repeater does, listen for a few minutes. DMR and D-STAR repeaters work differently from analog FM. DMR uses two time slots on each 12.5 kHz channel, a color code that must match, talkgroups to select who hears you, and a DMR ID registered to your callsign. D-STAR uses callsign routing, with fields such as MYCALL, URCALL and RPT1/RPT2, and reflectors identified by a prefix, number and module letter. Because these need correct codeplug or radio settings, a sub-audible CTCSS tone is not the key detail on those systems. Whether a talkgroup is static or dynamic affects how much traffic lands on a repeater, so read the owner's notes before you start talking on an unfamiliar one. For finding repeaters, use more than one directory. RepeaterBook and printed or online band-plan listings are common starting points, and the club's own page is usually the most current source. For digital systems, check the network's own lists and the repeater's page for color codes, talkgroups, reflectors and rooms. Joining the club that maintains a repeater is a good way to learn its rules and help keep the system on the air.

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.