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. Here is the non-Q side, plus how it differs on CW and voice. CQ is a general call meaning any station may answer. DE means "from." A typical CW call is "CQ CQ CQ DE W1ABC W1ABC K" (placeholder call). K means "go ahead," any station. KN means "go ahead, but only the station I'm talking to," which is used to discourage others from breaking in. SK signals the end of a contact, usually followed by your call. Separately, "Silent Key" is the term for a deceased amateur. Related prosigns are AR (end of message), BK (break), and BT (pause or separator). Prosigns are sent as one run-together character, with no gap between the letters. 73 means best regards, and it's already plural, so "73s" is technically redundant even though you'll hear it. 88 means love and kisses. It's traditionally used between close friends or spouses, and sometimes jokingly, so most people stick with 73. RST stands for Readability (1 to 5), Strength (1 to 9) and Tone (1 to 9). Tone is used for CW only, so voice reports are just RS, like "59." A CW report of 599 is the usual default in contests. A good report is honest and based on what you hear, so tell a weak station when they are weak. In CW, common abbreviations include TNX or TU (thanks), PSE (please), AGN (again), ES (and), UR (your), WX (weather), RIG, ANT, FB (fine business), GM/GA/GE, CUL (see you later) and HW? (how copy?). On voice, avoid most of these and use plain language and standard phonetics for callsigns. For nets and emergency work especially, plain language is recommended over CB-style codes. For logs, record the date and time in UTC, frequency or band, mode, the other station's callsign, the RS(T) sent and received, and optional details like name, QTH or grid square. Contests add their own exchange, and a "dupe" is a repeat contact with the same station. On nets, the net control station (NCS) runs the roll call and directs who speaks. Check-in means announcing your call to join. Traffic is a message to be relayed, and a tactical call is a role-based identifier used in drills and emergencies. Some nets use QNI for check-ins and QTC for traffic, but local conventions differ, so listen to a net a few times before you check in.
  2. On privileges: an Amateur Extra can operate on all frequencies allocated to the Amateur Radio Service, in all authorized modes, within the power limits and other rules in Part 97. Segments that used to be reserved for Advanced and Extra are now effectively Extra-only for new licensees, and some sub-band edges that look odd on a band chart are just the dividing lines between license classes. Don't rely on a memorized chart. The authoritative sources are §97.301 through §97.305 for frequency and mode allocations, along with the ARRL or other current band charts for a quick visual. Extra also opens up some operating options beyond the band edges. You can request a Group A call sign, including the shorter formats (such as 1x2 and 2x1) that are reserved for the top class. You can also serve as a volunteer examiner for any exam element, which is a way to give back once you pass. For Part 97 study in general, use the section numbers as anchors. §97.3 is the definitions section, and many questions are just vocabulary from it. Station identification, third-party communications, prohibited transmissions, and control-operator rules each have their own sections, and the exam likes to test the exceptions to the general rule. On the design-theory side, a few receiver concepts show up repeatedly and are worth working through with real numbers: sensitivity vs. dynamic range, why strong nearby signals cause blocking or intermodulation, and why phase noise in a local oscillator limits close-in selectivity. For modulation, remember that FM modulation index equals frequency deviation divided by the modulating frequency. Also check which pool revision is currently in use, because the question pool is updated on a multi-year cycle and older study guides may have outdated questions.
  3. On traps, the main trade-off is loss and weatherproofing against convenience. A trap is a parallel LC circuit resonant on the upper band, so it isolates the outer wire there. On lower bands it acts as a loading inductor and shortens the antenna. That shortening is the reason traps cost bandwidth and some efficiency. A homebrew trap also has to be built and tuned with a dip meter or analyzer before it goes up, and the capacitor's voltage rating and tolerance matter. Moisture changes the L and C values, so sealing counts. A fan dipole or linked dipole is easier to build and troubleshoot. A fan dipole has parallel wires from a common feedpoint, but wire spacing causes interaction, so each element needs trimming in sequence, starting with the highest band. If you only want two or three bands, I'd start there. Run each design through MMANA or EZNEC first so you know how much the interaction shifts the lengths.
  4. On the legal side, keep three things apart: what the radio can do, what the license allows, and what the equipment rules say. In the US, amateur operators have more freedom to modify their own equipment than users of other services, but that freedom covers amateur-band use, not other services. Equipment for services such as FRS, GMRS, CB and business or public-safety channels is generally expected to be certified for that service, and modifying it can invalidate that status. Other countries have their own rules, so check your national regulator and don't assume the US approach applies. For MARS, CAP and similar programs, the rule is simple: no authorization, no transmitting on those channels. A radio that can be unlocked is not an authorization. If you're a member, follow your program's guidance on approved radios, programming files and frequency use. If an organization has issued rules for its own equipment, a personal modification may not be acceptable even if it's technically fine. Third-party firmware needs extra care because it can change power levels, deviation, filtering and transmit limits. Before using it on the air, check the output on a dummy load and a spectrum display or a second receiver. Look for harmonics, spurs, overdeviation and splatter. Back up the original configuration, confirm the exact model and hardware revision, use a stable power source during flashing, and be prepared for the radio to need recovery if the update fails. For audio changes, don't turn up mic gain until the radio sounds loud. On FM, excess deviation causes distortion and adjacent-channel interference. On SSB, overdriving the audio chain or ALC causes splatter. Compare your transmit audio against a monitor receiver, and run a few test transmissions with a local operator who can give a report. A modified radio that sounds good to you but is splattering across the band is not an improvement.
  5. If sending feels fine but receiving lags, the usual fix is to stop practicing in ways that let you cheat. Writing everything down letter by letter is fine early on, but eventually you want to copy in your head, a word or two behind the sender. Short daily sessions with a character speed that's a little uncomfortable tend to beat one long weekend session. Keep the character speed fixed and only change the spacing, so the sounds of the letters stay consistent. On the filter question, try this test: tune across a crowded part of the band with the filter at about 400 Hz, then open it to 250 Hz or so. If the narrower setting makes the dits blur together, it's too tight for the signals you're copying. A slightly wider filter plus a comfortable pitch is often easier on the ears than an extremely narrow one.
  6. Here's the logistics side, since that's where most people get tangled. VE, VEC, and who runs the test: Amateur exams are given by Volunteer Examiners (VEs), who are licensed hams accredited through a Volunteer Examiner Coordinator (VEC). The VEC is the umbrella organization (the ARRL VEC is one, and there are others). A local VE team runs the session, grades your paper, and submits the results. You can usually take the test with any team, regardless of which VEC they're under. Finding a session: The ARRL has an exam session search on its website, and HamStudy has a session finder too. Local radio clubs often post their own dates. Many VE teams also offer remote exams over video, with a webcam and ID checks. Rules and scheduling differ from team to team, so read the session listing carefully. Some require advance registration and some take walk-ins, and the listing should tell you which. FRN and ULS: The FRN is a ten-digit number you get by registering in the FCC's CORES system, and it's free. Register before exam day, because teams typically ask for it and the application can't go through without it. ULS (the Universal Licensing System) is the FCC database where your license record lives. After you pass, your call sign and record show up there, and you can look yourself up by name or call sign. Keep your CORES login details somewhere safe, because you'll need them later for address changes and renewals. Rules around this have been updated over the years, so check the FCC's current instructions rather than relying on a forum post, mine included. Fees: The exam fee is set by the VE team or its VEC, and it varies a bit between teams. It covers the cost of running the session. I'm not going to quote a number because it changes and differs by session, so look at the listing or ask the contact person. Don't assume the FCC itself charges anything. Confirm the current FCC fee situation on its site before you pay anyone. What to bring: Photo ID, your FRN, the exam fee in whatever form the team accepts (ask in advance), two pencils and a pen, and a basic calculator if you want one. Some teams have rules about calculators, such as clearing the memory, so ask. If you've held a license before, bring a copy.
  7. One thing to add on the noise side is that the SDR's own display can mislead you. The waterfall and spectrum scaling, FFT size, averaging, and window function all change how the noise floor looks. A larger FFT lowers the noise per bin, so weak narrowband signals show up more clearly, while a short FFT with heavy averaging can hide intermittent signals. So compare noise floor levels using the same settings. For digital modes, also remember that decoding failures are not always RF problems. Sample rate mismatches, audio device routing, clock drift on cheap dongles, and AGC pumping can all cause bad decodes. For WSJT-X style modes, getting the dial frequency and time sync right is critical, so an upconverter offset error can look like a reception problem. Setting a ppm correction, or calibrating against a known signal, is worth doing, especially on cheaper dongles whose oscillators drift as they warm up.
  8. I'd put one thing ahead of most of that: look at the radio before powering it. Check for a cracked solder joint at the DC jack, corroded battery or fuse contacts, heat-discoloured resistors, bulging caps and any previous repair work. It takes a couple of minutes and spares you from applying power to something with an obvious short. On test gear, a decent DMM with a diode range and a current clamp or in-line current measurement covers a surprising number of faults. A scope becomes valuable when you need to see something change over time: PLL control voltage, oscillator startup, supply ripple, audio clipping or a PTT line chattering. Keep the ground lead short. Long probe grounds on RF circuits can mislead you badly. If the unit has an off-line power supply, don't connect a grounded scope to it without an isolation transformer or a clear understanding of what the chassis is tied to. For intermittent faults, tapping with a plastic tool and gentle flexing of the board while monitoring a key voltage is often more productive than reaching for the soldering iron.
  9. I'd add that "keeper" often depends on what else is in the shack. A radio can be redundant next to your main rig, but it earns a place if it fills a different role, like a portable QRP rig for the park, a dedicated CW radio, or a backup for when the main one is down. The classifieds angle matters too. Radios with strong resale value are easier to try without commitment, because you know you can recover most of the money. Niche or unusual gear is harder to sell, so people tend to hold onto it longer, whether or not they use it. A decent filter for deciding is to ask whether you'd buy the radio again today at the going price. If the answer is yes, it's probably a keeper. If you're mostly keeping it because selling feels like a hassle, it might be time to list it and let someone else enjoy it.
  10. I'd add a note on bonding and amplifiers, since the thread covers both. When you add an amp, the chassis bonding and the RF return path matter more because higher power makes any common-mode problem more obvious. Symptoms such as a tingle on the microphone, erratic SWR readings, or the radio's display glitching on transmit generally mean RF is on the shield or the control cables. Chokes on the coax, the amp keying line, and the USB or CAT cable are the first things to look at. On band-pass filters, there's a difference between using them on the receive path and in-line on the transmit path. A BPF rated for transmit power sits between the radio and the amp, or after the amp, and has to handle the power and the SWR. A receive-only preselector is a separate device with different ratings. It is worth checking the manufacturer's specified power handling, insertion loss on the band you care about, and what happens to the filter when the SWR is poor. A filter that is fine at 100 W into a 1:1 load may not be fine into a mismatch. What bands and antennas are people planning to use? That will change the advice quite a bit.
  11. On kit: a VHF handheld with a decent antenna is the lowest-effort start, but it depends on the area. Where there are plenty of FM operators and a local calling frequency, a handheld and a roll-up J-pole or a good whip can get you the four QSOs. Where VHF activity is thin, you can sit on a good summit and call into silence. In that case a compact HF setup is more dependable. A typical lightweight HF kit is a QRP transceiver, a 10 m or similar fiberglass pole, and either an end-fed half-wave with a matching unit or a linked dipole cut for two or three bands. The linked dipole is a bit more fiddly to set up but needs no tuner and is easy to reason about. Whatever you choose, assemble it in the garden first. You don't want to find a missing connector at the summit. For power, a small LiFePO4 pack covers a short activation easily. The thing most people underestimate is the cold. Batteries sag and fingers stop working, so key and logging arrangements matter more than a few grams saved. Carry a spare pencil, because pens fail in the cold.
  12. On matching references: start from the reference lists, not from memory. The WWFF site has a searchable directory of references, and POTA has its own park pages. Many sites appear in both programs, but the names, boundaries and numbering are independent. One POTA park can overlap a single KFF reference, several, or none. A large protected area might be split differently in each program, and a small local reserve may exist in only one. Look at the map for each and confirm where you will physically set up. If the boundary is unclear, ask the land manager or check the official boundary data, because operating just outside the line does not count for either program. For a double activation, the usual idea is that the same QSOs can count for both if you are inside both areas and each program's own requirements are met. That means the park must be valid in both, you must reach the higher WWFF count if you want a WWFF credit, and your log must carry the right reference for each program. Check current rules on any restriction about combining programs or reusing contacts, since that is the kind of detail that gets updated. On logging: keep the reference data in separate fields so nothing gets mangled on export. ADIF has MY_SIG and MY_SIG_INFO for your own program and reference, and many loggers let you add a second reference or export separate files. The safest habit is to export a clean ADIF for each program and look at the files before uploading, rather than trusting one file to satisfy both. Also confirm in the current WWFF instructions how they want logs submitted (upload, a specific format, or a particular logger), since I won't state a specific submission procedure from memory.
  13. A good rule of thumb is to match the tool to the question you're asking. If it's "can anyone hear me right now?", use PSK Reporter for FT8 or similar modes, or RBN if you're calling CQ on CW. If it's "is that rare one on the air?", you want cluster spots, and you'll want filters. Most cluster clients let you limit by band, mode, spotter continent or DXCC entity, and without that the stream is mostly noise. Notification services like HamAlert are the other half of that. Instead of staring at a spot list, you define triggers (a callsign, an entity, a POTA or SOTA reference, a band/mode combo) and get a push or email when a matching spot appears. The trade-off is that you have to be disciplined about the triggers. Too broad and you'll mute it within a day. One caution on skimmer data: RBN and PSK Reporter tell you about reception at specific receiver locations. A strong report at a skimmer in one region doesn't mean the path is open to you. Look at where the reports are coming from, not just the best SNR number.
  14. On the card design question, readability beats art. A beautiful photo is nice, but if the QSO details are in tiny script on a dark background, the card can be hard to read. Many people put the photo on the front and keep the entire back as a plain, high-contrast box with the QSO data. That makes it easy for the recipient, and it helps if a card checker needs to verify the details. Also double-check the little things that cause rejections. Make sure the callsign is the one actually used in the contact (portable or special-event calls can differ from the base call). Make sure the time is UTC, not local. Include the mode that was actually used. If the other station's callsign is written wrong on your card, the confirmation can be useless for awards. A quick check against your log before printing or mailing a batch can prevent a lot of re-sends. For direct requests, keep the package light. A card, SASE, and postage in a plain envelope is usually enough. Add a short note only if the station asks for something extra, and check whether they want a certain number of stamps or dollars, since requirements vary by country and station.
  15. One habit that helps is separating worked from confirmed from credited. Those are three different states, and each program counts a different one. A contact is worked when it is in your log. It is confirmed when LoTW matches it or a QSL card arrives. It is credited only after the award manager has accepted it, so you need a status column for each step. For DXCC, keep your log tied to the entity as it is defined at the contact date, because operations from entities that were later deleted or split still count in their own category. Don't trust a prefix lookup alone. Some prefixes cover more than one entity, and special event or portable calls can point to a different place than the call suggests. When a QSO fails to match, look at the other station's callsign suffix and your own entity assignment before assuming they never uploaded. For the Honor Roll, a simple check is to compare your confirmed count against the total number of current entities on the official list. Only current entities count there, so deleted ones won't help close that gap.
  16. Koch and Farnsworth solve different problems, so you can combine them. Koch is about how you introduce characters. You start with just two characters sent at your target speed, commonly somewhere around 18 to 20 WPM. Once you can copy them with high accuracy (90% is the usual benchmark), you add one more character. You keep going until you have the whole set. The idea is that you never learn a slow, countable version of a letter. You learn its sound at the speed it will actually be sent, so there's no habit of counting dits and dahs to unlearn later. Farnsworth is about timing. The characters are sent at a faster speed, but the gaps between characters and words are stretched. That gives your brain time to recognize each character as a single sound pattern. The risk is that you get comfortable with the long gaps and then struggle when the spacing tightens. If you use it, shrink the extra spacing over time. Many people use a Koch-style trainer with fast characters and generous spacing at first. LCWO and G4FON's trainer both support this approach. LCWO is browser-based, so you can practice on any device with an account and keep your progress. G4FON's trainer is software you install, which some people prefer for offline use and for tweaking settings. Pick one and stick with it for a while rather than rotating tools every few days. For sessions, short and regular beats long and occasional. Fifteen to thirty minutes a day is a common recommendation, and you can split it into two sittings. Move on to the next character when your accuracy is solid, not just because you feel impatient. Moving too fast leaves you with shaky characters that fall apart on the air. On flashcards, visual dit-dah charts are fine for a quick look at what a character is, but they're a poor way to learn it, because you end up associating a letter with a picture of dots and dashes. Any card system should be audio-first: you hear the character and recall the letter. Learn it as a sound pattern, like a short word you recognize by ear.
  17. On nets, I'd say the most helpful thing a new operator can do is listen to the net control's opening before checking in. Most nets announce how they want check-ins: by list, by region, by suffix, short-time, or only if you have traffic. Following that matters more than anything else. Give your callsign once, clearly, in phonetics, and add your name and location only if the net asks for them. Don't give a long update or start a side conversation while the net is working through a list. Net control is a job with its own etiquette. Keep the net moving, acknowledge each station, and keep a log of who has checked in. If you're running the net, state the purpose, frequency, and mode at the start and repeat them periodically so late arrivals know what's going on. Priority or emergency traffic always goes first. Tell stations to stand by if you can't handle them yet instead of ignoring them. When closing, thank participants, announce the time of the next net, and give the net's callsign if it has one. For emergency or training nets, brevity and discipline are the point. Say what you need, say it once, and listen for the answer. Don't transmit unless you're sure you have something useful to add.
  18. For 23 cm and the microwave bands, the usual recommendation is to put effort into the feed and the pointing before adding amplifier power. A good illumination of the dish, minimal loss between the feed and preamp, and an accurate pointing model often give more than a larger amplifier. At 10 GHz, Moon noise and sun noise are standard ways to check performance, and a mount that holds position through wind and temperature changes is more important than people expect. Libration fading becomes the main mode issue. Narrow-tone modes can lose decodes from the Doppler spread even when the average signal level is enough. This is where Q65's wider submodes and its tolerance of spread help. Whatever you pick, agree on the exact submode, period and frequency with your partner before the sked, and check the current WSJT-X documentation for the recommended settings on your band. For sked planning, don't just compare Moon windows. Compare each side's elevation, because low-elevation Moon paths pick up ground noise and local obstructions, and check whether the Moon is in a noisy sky region, though that matters less at microwaves. Agree on who transmits in which minute, a backup time, and the signal-report convention before you start. Having all that written down avoids losing time while the Moon window is open.
  19. On the compression question, a useful way to think about it is that the benefit is limited and the cost is cumulative. Compression doesn't create signal. It reduces the gap between your loud and quiet syllables, so the quiet parts sit higher against the noise at the far end. A few dB of compression usually helps. Beyond that, you mostly raise the noise floor of your own transmit audio, including fan noise, room echo and keyboard clatter, and intelligibility can get worse even while the signal looks stronger. For testing, the most reliable approach is a recording from outside your shack. A remote SDR within range, or a friendly station who can record you with their radio set to a normal 2.4 kHz filter, is much more informative than an S-meter reading. Compare three versions: processor off, light processing, and your usual setting. Listen for pumping, harsh sibilance, a boxy sound and any background build-up between words. One more thing to check is RF in the shack. If your audio gets raspy only on certain bands or at higher power, the cause may be RF getting into the mic cable or audio gear rather than any processor setting. Ferrites, better grounding and a shorter or better-shielded mic cable can fix problems no menu adjustment will. On the bandwidth question, my view is that a clean 2.4 to 2.6 kHz signal with good low-cut is a sensible default for crowded bands. Wider settings are fine for a casual contact on a quiet frequency, provided you're not splattering and nobody is squeezed next to you.
  20. On message handling, I'd push for practicing the paper side as much as the voice side. In a real event, served agencies often want written messages with a clear "from, to, time, message" structure, and the ICS-213 is a common form for that. Formal radiogram format is worth knowing too, especially for longer-haul traffic, but the form your served agency actually uses is the one to drill on. Practice reading a message back verbatim, with no paraphrasing or added opinions, because accuracy matters more than speed. For exercises, a drill that forces a few things tends to pay off: a simulated loss of the primary repeater so people have to switch to simplex or a backup, a net control handoff partway through, and a few messages that need relaying between stations that can't hear each other. Those show where the plan is thin much faster than a simple roll-call net does. For the go-bag, I'd split it in two. One part is the radio kit: HT or mobile, spare batteries, a better antenna than the stock rubber duck, coax, adapters, a headset or earpiece, and a power source. The other is personal sustainment: water, food, medications, weather-appropriate clothing, ID and any agency credentials. A deployment can last longer than expected, and an operator who isn't looking after themselves doesn't last long on the net.
  21. For the path question, it helps to separate propagation types. On HF, FT8 is the default because so many stations are on it, and it is usually decoded before you can finish a sentence in the log. WSPR is more useful as a measurement tool. You can run low power on a band, and the reports on the public spot database give you a map of where your signal landed. That tells you more about an antenna change than a handful of QSOs would. On 6 m and up, mode choice depends on the mechanism. Meteor scatter calls for MSK144, with accurate time and a fixed schedule or calling frequency. Q65 is the one to learn if you are looking at tropo, scatter or EME, because the sub-mode letter and period have to match between stations, and a mismatch looks exactly like no signal. For something like emergency or off-grid messaging, JS8Call and Winlink serve different jobs. JS8Call is good for informal keyboard contact and relaying short messages between stations, whereas Winlink is for formatted email that has to reach an internet gateway. Neither replaces proper training or a local net plan, and it is wise to test them on a quiet band before they are needed. One last point on CAT: if you also run a logger or another program on the same radio, use a shared CAT arrangement or a rig-control server (rigctld, for example) so two programs do not fight over the serial port. This is a common reason that frequency readouts freeze or PTT drops partway through a transmission.
  22. On the band plan: stop trying to memorize every frequency and learn the pattern. On 80, 40, 20, and 15 meters the General CW/data segment sits at the bottom of the band, and the General phone segment sits near the top. The Extra-only slices fall between them or at the very bottom edge. Once you can sketch that layout for a band, the numbers are easier to recall. For reference, General phone starts at roughly 3.800 MHz on 75 meters, 7.175 on 40, 14.225 on 20, and 21.275 on 15. Check those against the current FCC Part 97 tables before you rely on them. Questions are usually worded like "which of these frequencies is available to a General on USB?", so what you need is a picture of where each band is open to you. Know the special cases separately, because they are the usual trick questions. 30 meters is CW and digital only, with a lower power limit than the other HF bands. 60 meters has its own rules, so read the current rule text rather than an old study guide. 160, 17, and 12 meters are the awkward ones because they do not follow the pattern of the other bands. 10 meters has a larger phone segment than a Technician has had. For power, remember the general rule of 1500 W PEP, and that the band-specific limits override it. Also keep operating privileges separate from emission types. Many wrong answers in this section come from mixing those up. For the digital questions, they tend to be conceptual: FT8 and similar weak-signal modes need an accurate computer clock and use fixed time slots, PSK31 is narrow, RTTY uses frequency shift, and the questions ask about bandwidth, sound card interfacing, and where such signals are typically found. Knowing why a mode behaves the way it does is more useful than memorizing frequency lists.
  23. Good list. I'd add a point about handoffs, because that's where exercises tend to expose real weaknesses. Test shift changes at stations and at net control: does the incoming operator know which messages are pending, which stations are assigned where, which frequencies are in use and what's been promised to the agency? A simple handoff sheet or log summary makes a big difference. If your exercise runs only an hour or two, you may never see this problem, so consider a longer scenario or at least a forced mid-exercise swap of operators. Another suggestion for after-action reports: record both the technical problems and the human ones, such as unclear roles, people not knowing whom to ask, or fatigue. Include what went right as well, so the group knows which practices to keep. And when an item is fixed, retest it in the next drill rather than assuming it's solved. Finally, for Field Day, try designating one station as an "agency desk" where someone plays the role of the served agency and hands operators messages in the agency's own format. It makes the contest feel a bit more like the real job.
  24. Another point on CHIRP: the first thing to do is a clean download from the radio, then save that file as your backup. After that, import repeaters for your area from a current source and spot-check a few against the repeater's own listing. Directory data can be stale, and a wrong offset or tone is the most common reason "the radio hears but can't open the repeater." If you can receive the repeater output but can't access it, check three things: duplex direction (+ or −), the offset size, and whether it needs a CTCSS tone on transmit. Some repeaters also need a tone on receive for tone squelch, but that's usually optional on your side. Also test on simplex with another ham before blaming the radio. It separates a programming problem from a coverage problem. For emergency channels, I'd keep a separate memory bank with simple names, such as local simplex, the primary repeater, a backup repeater and weather, and not mix them with a hundred other entries. In a stressful moment, fewer choices are better. Also carry a printed copy of your channel list in case the radio gets reset.
  25. For band conditions, I'd treat solar numbers as a weather forecast and spotting networks as the radar. A high SFI suggests the higher bands can support propagation, but it doesn't guarantee a path from your location to the place you want. Open PSK Reporter, filter by band and mode, and look at where your own signal or nearby stations are being received. If FT8 on 12 meters shows spots in your target region, that's better evidence than any index. The Reverse Beacon Network does the same job for CW and RTTY. Keep an eye on the K-index too: a geomagnetic disturbance can wipe out an otherwise good day, especially on paths near the poles. For gear announcements, my rule is to separate three stages: teaser, preorder, and shipping. Only the last one tells you how the product actually behaves. Even then, the first batch of owner reports is more useful than a polished launch video, particularly for receiver performance, menu quirks, and firmware stability.

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.