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_Mike

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Mike

  1. From the hunter side of the procedure, the most useful habits are short and predictable. Give your callsign clearly, don't call over a QSO in progress, and give the activator a clean exchange. Also check the spot first so you know the frequency, mode and park reference before you call. If you can't hear the activator's end clearly, don't pile on with a weak call. Wait for a better moment or move on. For activators, a few things help: repeat the park reference every few contacts so new listeners know what they've found, call QRZ at intervals, and say when you're moving or finishing so hunters aren't left calling on a dead frequency. If you're doing a two-fer, say both references clearly. A hunter's log usually only reflects what the activator's file contains, so the accuracy of your upload matters long after the day is over.
  2. On Farnsworth, one practical split is to pick a character speed and leave it fixed, then only change the spacing. If the character speed keeps changing, the sound patterns never settle. Many learners choose something like 18 or 20 WPM for characters and bring the overall speed up gradually. Contests are good practice because the exchanges are predictable. In a typical CW contest you hear the same few words over and over: the call, 5NN, a serial number or zone, TU. Cut numbers like T for zero and N for nine are also common, so it pays to recognize them as part of the rhythm. Because the content is limited, you can concentrate on callsign copy. It is a good way to build confidence without needing full conversation skills. For the decoder question, some operators run a skimmer on a second receiver or window just to check calls and keep their own ears as the primary copy. That makes the decoder a backup rather than the main tool.
  3. On the net side, the thing that makes the biggest difference is a predictable structure. A good net control opens with the purpose of the net, the frequency or repeater, and how check-ins will be taken, for example by suffix or by region, or by category such as mobile, base or short-time. That way people know when to speak. Keeping a written list of callsigns as they come in saves a lot of "say again" later. For check-ins, the standard advice is to give your callsign once, clearly, with phonetics only if asked or if conditions are poor. If you have to leave early, say so as "short time" so net control can take you first. And when net control says to stand by, stand by. A pause usually means they're writing down calls or sorting out an overlap, not that the frequency is free. Where the etiquette gets tricky is on busy shared frequencies, like a repeater with a scheduled net followed by general chatter. The polite approach is to check whether a net is due, wait for the net to finish, and only then start a casual conversation. Many clubs publish their net schedules, so a quick look can save an awkward overlap.
  4. Good list. A couple of additions for the buying side. Take photos of the model and serial number tag before you commit, so you can look up service bulletins or known problems on your phone before paying. Cell service at big fairgrounds can be spotty, so it helps to save a few model-specific notes offline beforehand, like the typical failure points for the radios on your wish list. Also decide in advance what you're willing to repair. A rig with a bad display or a dead final may be a bargain for someone with a bench and the parts, and a trap for someone who just wants to get on the air this weekend. Being honest with yourself about that saves a lot of regret. On forums and prizes: keep your prize ticket stubs somewhere you won't lose them, and check how the drawing is run, because some events require you to be present to win. If you're short on time, it's worth sitting in on one forum even if it's on a topic you think you already know. There's usually a question in the Q&A that makes you realize a gap in your setup. One more thing for newcomers: if the VE session is running while you're there, you don't have to be testing to talk to the team. Asking about study resources and what to expect is a low-pressure way to get started, and teams are usually happy to point people to good practice materials.
  5. On batteries: LiFePO4 is a good match for 12 V portable gear, but check the voltage range against your rig's specs. A 4-cell pack runs a bit above 13 V under normal use and higher when freshly charged, which is fine for many 12-14 V rigs but not for something with a narrow input window. Know what the pack's built-in protection does when it hits the low-voltage cutoff, because some cut off abruptly in mid-QSO. A small inline fuse and a clearly marked connector polarity are cheap insurance. For capacity, don't oversize. A 5 W CW session at modest duty cycle draws well under what an SSB rig at 10 W PEP does, so a small pack goes a long way. The KX-series internal battery options are convenient but give you fewer hours than an external pack. On finding contacts: calling frequencies are a starting point, not a guarantee. Self-spotting through the usual spotting networks for park and summit activations, and answering other QRP stations, tend to work better than sitting on 14.060 and hoping. QRP-ARCI also runs operating events and has information on awards, which can give you a reason for people to be on the air. Check their current rules and calendar directly before planning around any specific event.
  6. On audio levels, the principle is that the digital signal should be clean before it ever reaches the final amplifier. These modes are mostly constant-envelope or at least tolerant of limited amplitude variation, but a transmitter driven into ALC compression or into nonlinearity splatters, and you get a wider signal than the mode was designed to produce. A reasonable procedure is to set the radio to a data or USB-D mode with speech processing and compression off, then raise the software's output level while watching ALC, and back it off until the ALC reads at or just above zero. Then set the power with the rig's power control, not the audio level. Several modes, FT8 included, work fine at low power, and a clean 20 W is better than a dirty 100 W. On the receive side, aim for a moderate level and keep the audio from clipping. In WSJT-X the receive level meter is a rough guide, and the documentation suggests something in the middle of the scale rather than pinned at either end. Also turn off any operating-system sound effects, enhancements or automatic gain on the audio device. They can quietly change levels or add processing you do not want. If you use a sound card interface with a separate audio path, galvanic isolation through transformers or an isolated USB interface can fix a lot of hum and RF feedback. Ferrite chokes on the USB and audio cables help too. If the software glitches or the PC drops its serial connection every time you key up, suspect RF getting into the cables before you suspect the software. For CAT, Hamlib is the usual backend in WSJT-X and several other programs. Make sure the baud rate, data bits, stop bits and handshake settings match the radio's menu, and that no two programs are trying to open the same COM port at once. For split, WSJT-X offers a mode where the radio itself is set up in split so the audio tone stays in a clean range, rather than letting the dial move around. That avoids audio harmonics landing inside the radio's passband filtering.
  7. On the logging side, here is a checklist that applies to almost every event. Check your category line, band and mode settings, power level, and operator or station info in the Cabrillo header, since mistakes there can move you into the wrong category or get the log treated as a check log. Make sure the callsign, grid or section, and zone in your station settings match the contest, and that the clock was accurate, since UTC time errors cause not-in-log penalties. For Field Day and Winter Field Day, the scoring is more about bonus points, class and documentation than a straight Cabrillo-style competition, so read the submission instructions for that specific event. For SOTA, log through the program's own system as well as your own record, and keep summit references accurate. And submit before the deadline rather than at it, because upload sites can be slow and some sponsors send confirmation that is worth keeping. A good habit for the calendar is to add the log deadline as a separate entry, not only the contest start time.
  8. I'll take the cross-band and power wiring questions, since they cause the most expensive mistakes. On cross-band repeat, don't rely on forum memory or spec-sheet summaries. Open the current manual for the exact model and version and search for "cross-band repeater" or "repeater function". Of the three, the TM-D710G is the one commonly described as having it, but check it against the manual you'll actually own. It's a feature that disappears from marketing pages and is easy to assume wrongly. Operationally, the mobile receives on one band and retransmits on the other, so your handheld is effectively using the mobile's antenna and power. You are still the control operator, so identify as your rules require, and pick frequencies that don't land on an active repeater input or output in your area. Duty cycle matters too: a 50 W radio retransmitting for long periods in a parked car can get hot, so make sure the heat sink has airflow. On power, the usual advice is a dedicated run from the battery, not the accessory socket. Take the positive lead straight to the battery with an inline fuse holder close to the battery terminal, within a few inches. The fuse protects the wire, so if the wire is damaged anywhere along its length, the fuse is what limits the fault current. Use the wire gauge and fuse rating given in the radio's manual, and don't substitute a bigger fuse because it keeps blowing. If it keeps blowing, something is wrong. A 50 W FM mobile can draw on the order of 10 to 12 A at full transmit, but the manual is what counts for your fuse and gauge. Use a grommet where the wire passes through the firewall so the insulation isn't chafed, and avoid running it next to ignition wiring or tight against sharp edges. The negative lead can go to the battery negative as well, which is the cleanest reference. A bolt on a random chassis point can work, but it is a common source of both noise and voltage drop.
  9. On shared frequencies, it may help to separate two things: the band plan, which tells you where certain modes and activities belong, and the informal local agreements, which tell you what actually happens on a given spot. A new operator can easily follow the band plan perfectly and still land on top of a regular daily net because they did not know about it. Listening for a while at different times of day gives you a feel for the regulars, and many clubs publish net schedules on their websites for exactly this reason. If you do find you have stepped on something, the best response is a quick apology and a move, not a long explanation on the air. Most people are happy to forgive a mistake that was handled politely. And when someone else makes the mistake, a short, calm "the frequency is in use" is usually enough. On interference, I would stress keeping notes. If a repeater coordinator or club officer is trying to track down a problem, a log with the date, time, frequency, mode and the nature of the signal is far more useful than "someone was jamming us last night." It also keeps you from reacting emotionally on the air, which is the thing most likely to make a bad situation worse.
  10. On submission: most big contests use a Cabrillo file uploaded to a web robot on the sponsor's site. The things that cause rejected or odd-looking logs are usually mundane: The callsign in the header doesn't match the callsign you operated with.The wrong category is selected. For example, the single-operator assisted category counts spotting aids, so check which category matches what you actually used.Time zone and clock errors. Log in UTC and sync your computer clock before you start.Sending the log after the deadline. Deadlines vary by contest, and some are only days after the weekend, so check the rules rather than assuming.Also look at the sponsor's "check log" or "claimed score" statements when the robot confirms receipt, and keep the file you submitted. For the others you mentioned, treat them separately. Winter Field Day is run by the Winter Field Day Association rather than the ARRL, so its rules, categories and submission process are its own. State QSO parties are run by individual clubs or state organizations, so exchanges and log addresses differ, and often the in-state exchange differs from the out-of-state one. The RTTY Roundup has its own exchange and needs a decoding setup such as fldigi or MMTTY, so test that well ahead of time. SOTA is different again. An activation needs a minimum number of contacts from the summit to earn points, and logs go to the SOTA database rather than a contest robot. Chasers and activators can also enter contest events from a summit, but follow the contest's own portable-operation rules. If you want a priority order for a casual setup, choose two or three contests where the exchange is simple and the activity is high, such as WPX or Field Day, and treat the rest as optional.
  11. Most operators treat the final minute of a contest as the finish line. The log is where the lessons are. A short review routine after Field Day, CQ WW, ARRL DX, or a state QSO party can improve next year's rate, clean up your submission, and push your DXCC, WAS, WPX, and IOTA records forward. None of it needs fancy software. Step 1: Check the log before you submit it Open your logging program and look for obvious problems before you export anything. Common ones include: Wrong contest settings. Check the category, power level, operator class, and exchange format. A misconfigured exchange can make an entire log harder to score. Time and band errors. Make sure the clock was right and that QSOs sit on the bands you actually used. If you use CAT control, confirm the logged frequency and mode matched the radio. Missing or odd exchanges. Scan for blank fields, suspicious zones or sections, and callsigns with unusual characters. Duplicate contacts. Read the rules for the event. Some contests count a repeat contact on the same band and mode as a dupe, and some have other rules. Do not assume. Then follow the sponsor's instructions for the log format. Many contests use Cabrillo, but the exact header fields and submission method come from the current rules, so read them each time rather than relying on memory. Step 2: Hunt for busted calls A busted call is a contact logged with a callsign that is slightly wrong. It costs you the QSO and may cost a penalty depending on the contest's checking. The fix is simple: scan for calls that appear only once and look unfamiliar, and compare them with what you remember hearing. A call-history or call-check feature in your logger can help, but treat it as a hint, not proof. When you spot a likely error, fix it only if you are confident from your own notes or audio. If you are unsure, leave the entry as logged or follow the contest's guidance on uncertain contacts. Never edit a log to make it look better than what actually happened. Step 3: Study rate and multipliers A raw QSO total hides the story. Break the weekend into hours and ask a few questions: When did my rate peak? If your best hours were on one band, note when it opened and whether you were on it. Where did I lose time? Long stretches of calling CQ with no replies, slow band changes, and hunting a single weak station are all worth noting. How did multipliers arrive? Look at when you picked up new zones, sections, states, or prefixes. Multipliers often come in bursts after a band change or a switch from calling CQ to search-and-pounce. What was my balance? Running a frequency tends to produce steady rate, while tuning around often finds multipliers. Most scores benefit from mixing the two. A one-page note with two or three changes for next time is more useful than a long spreadsheet. For example: "Move to 15 meters earlier," or "Set up a memory keyer for the exchange." Step 4: Turn the contest log into award progress Contests are efficient for award chasing because so many stations are on the air at once. After the event, check your log against what you need: DXCC: Look for new entities, and band or mode entries if you track those. The award is based on confirmed contacts with entities on the DXCC list, so a new-sounding prefix is not automatically a new entity. Verify it against the current list. WAS: State QSO parties and ARRL DX (where W/VE stations work DX) are strong hunting grounds, depending on your location and the event format. Mark states that still need confirmation. WPX: Prefix variety matters. Your contest log is a record of which prefixes you worked, but check the award rules for how the program counts and what documentation it needs. IOTA: Island stations can be sparse in ordinary operating but may appear in contests. Make sure the reference number was actually part of the exchange or confirmed some other way, because IOTA credit depends on proper identification. Each program has its own rules about which confirmations count. Review the current requirements before you decide how to chase a particular credit. Step 5: Handle confirmations Submitting a Cabrillo log to the contest sponsor is not the same as confirming contacts for awards. LoTW (Logbook of The World) is a separate system. To use it, you generally need a certificate, a signing tool (TQSL), and an upload of your station data. A confirmation appears only when the other station has also uploaded a matching QSO. Practical tips: Check that your station location in TQSL matches where you operated. Field Day or portable operation may need a separate location entry. Upload soon after the contest. Many stations upload quickly, so matches may arrive within days or weeks. Others never upload. For stations you really need and who are not on LoTW, a paper or electronic QSL card may be an option. Check the preferred method for that station and the rules of the award you are pursuing. Keep your logs backed up in ADIF form so you can re-import them if you change software. Step 6: Consider SO2R only when the basics are stable SO2R (single operator, two radios) means using two transceivers so that one can listen or call while the other is transmitting or searching. It can raise your rate, but it adds complexity: audio switching, interlock between radios, headphone routing, and software support. If your single-radio log still shows frequent exchange errors, a missed multiplier plan, or long dead stretches, solve those first. Many operators start by learning to run efficiently and search-and-pounce effectively before adding the second radio. A short checklist for beginners Read the rules and exchange format a week before the event. Test your logging software, including time sync and CAT control. Decide whether you want a casual or competitive approach. Both are legitimate. Even a few hours on the air teaches a lot. After the event, review busted calls, rate, and multipliers. Submit the log as required, then upload your QSOs to LoTW and check award needs. Write down two or three improvements to try next time. Treat each contest weekend as a cycle: operate, review, confirm, and improve. After a few cycles, you will see your rate grow and your award lists fill in without feeling like extra work.
  12. For the digital side, the decision mostly depends on what's active in your area. D-STAR helps if there are local D-STAR repeaters or you regularly use reflectors. DMR may be better if your area has a lot of DMR repeaters or a club hotspot. Look up the repeaters on a directory first, because a feature-rich radio that you can't use locally is an expensive paperweight. The ID-52A and TH-D75 are strong radios if you want the extras, such as GPS and Bluetooth, and APRS on the Kenwood, but they involve more setup than an FT-65R. Expect to spend time learning menus, callsign routing, and how your repeater handles DV traffic. For simple local calling, the analog FM modes on those radios work like any other HT. I'd also keep the IC-705 separate from the HT conversation. It's a different tool for portable HF. If you want a go-bag for emergencies, an HT with an upgraded antenna and a spare battery is where most people should start. If you want to work HF from a park or a hilltop, then the IC-705 makes sense, together with the antenna and power source that HF needs. And practice: set up a few memories for local repeaters and simplex, turn off the radio for a day, then see if you can still operate it from the manual and your own notes.
  13. On the after-action side, the hardest part is capturing information while it is happening. If you wait until the debrief, people remember the dramatic moments and forget the small friction points. Give net control and a couple of observers a simple log with times: when the scenario inject was delivered, when it was acknowledged, when the message was delivered to its destination, and anything that caused a delay. A short list of 'what went well, what did not, what we will change, who owns the change' is usually more useful than a long narrative. For net scripts, keep the script short enough that net control can actually use it under pressure. A workable skeleton might be: opening statement and purpose of the net, call for emergency or priority traffic, roll call by area or assignment, call for health-and-welfare or routine traffic, announcements, and closing with time and next check-in. Add a line at the top for the frequency plan and alternates, because that is the first thing people forget when the primary fails. Rehearse switching to the alternate during the drill instead of only listing it on paper. For Field Day as practice, try a few small additions: run part of the event on battery or generator only, check that go-kits have what the checklist claims, and rotate people into roles they do not usually fill, like net control, logger or message handler. The point is not to turn a contest weekend into a formal exercise, just to leave with a few concrete things to fix before the next real activation.
  14. On the plateau question, it helps to figure out what kind of plateau it is. If your copy is clean at 12 WPM but falls apart at 15, that is usually a processing-speed problem, not a character-knowledge problem. In that case, a useful pattern is a few short sprints at 2 to 4 WPM above your comfortable speed, followed by a return to your normal speed. Errors during the sprint are fine. The point is to train yourself to stop dwelling on a missed letter, because dwelling is what makes you miss the next two. If instead you are missing specific characters (the usual suspects are pairs like B/6, D/7, and the similar-sounding ones like F/L or Q/Y), then fix those directly. Koch-style trainers let you drill the weak characters in isolation, so you are not wasting time on ones you already know. For head copy, one common progression is: 1) write everything, 2) write only the callsign, name, and signal report, and 3) try to hold the first few words of a sentence in your head while the next ones arrive. Since the exchanges in typical rag chews and contacts are predictable (RST, name, QTH, rig, weather), you can train your brain to expect them. Expectation is a big part of how experienced operators appear to copy at "impossible" speeds. On schedule, short and frequent usually beats long and rare. Something like 20 to 30 minutes a day, with a mix of new material and review, tends to work better than a single two-hour session on the weekend, because fatigue degrades copy quickly. If you only have a longer window, break it into blocks with breaks in between. For callsign drills specifically, practice that simulates pileups and contest exchanges, whether through trainer software or recorded contest audio, builds the exact skill you need for fast callsign capture. Callsigns are random strings with no context to help, which is why they feel harder than plain text at the same speed.
  15. If the goal is the broadest band coverage with the fewest surprises, I'd rank the center-fed doublet on ladder line first, purely on loss physics. Open-wire line barely cares about a 10:1 or 20:1 mismatch, and coax does. The usual objection is routing, but the line doesn't need to be pretty. It needs to be kept a few inches off metal, avoid running parallel to gutters or siding for long distances, and cross other conductors at right angles. A wire you can feed at the center also gives a symmetrical pattern, which makes modeling easier to trust. The catch is the transition at the shack. A balanced tuner or a 4:1 voltage/current balun with a choke should be matched to what the line actually presents. A balun built for a 50-ohm resistive load doesn't necessarily behave when it sees a few hundred ohms of reactance. A tuner's internal balun can saturate or get hot on certain bands, so watch for that before blaming the antenna. A modeling program such as EZNEC or 4nec2, with a real ground model and your actual wire heights, will show which bands land at awkward impedances before you cut anything. On the G5RV, I'd call it a doublet with a particular length ratio, and I'd treat it like one. The 34 ft of ladder line is not special to every band. If you already own one, run it with a choke and a tuner and compare on-air reports across bands rather than relying on the tuner meter.
  16. Start with the rules-versus-plan split, because it answers a lot of the rest. Part 97 (mainly 97.301 through 97.305) is the law. It sets which bands each license class can use, which emission types are allowed in which segments, and power limits. The ARRL band plan is voluntary. It tells you where the community has agreed to put FT8, SSB, beacons, DX windows and so on. Nobody owns a frequency, and you are expected to share, but ignoring the plan makes you the person stepping on a weak-signal net. On HF in the US, the phone/CW divisions are mostly written into the rules for General and Technician, with Extra getting the widest slices. Rough General-class numbers: 80 m CW/data 3.525-3.600 and phone 3.800-4.000. 40 m CW/data 7.025-7.125 and phone 7.175-7.300. 20 m CW/data 14.025-14.150 and phone 14.225-14.350. 15 m CW/data 21.025-21.200 and phone 21.275-21.450. Extra opens up more at the bottom of each phone segment (for example 3.600, 7.125, 14.150, 21.200) and the bottom of the CW segments (3.500, 7.000, 14.000, 21.000). General also has all of 160 m, 30 m, 17 m, 12 m and 10 m, plus 60 m. 30 m is CW and data only, with a 200 W PEP limit and a requirement not to interfere with other services. Technicians are limited on HF to CW on 80, 40 and 15 m (the same bottom-end segments as General), plus 10 m: CW/data 28.000-28.300 and SSB 28.300-28.500, at 200 W PEP. That means FM at 29.600 MHz is General and up. Technicians have all privileges above 50 MHz. Novice and Advanced licenses are no longer issued, but existing holders keep their privileges, so you'll still see those on older charts. The common digital watering holes are conventions, not rules. FT8 dial frequencies are roughly 1.840, 3.573, 7.074, 10.136, 14.074, 18.100, 21.074, 24.915 and 28.074 MHz. Check the current plan for exact values, because FT4 and other modes sit nearby. CW tends to live in the bottom 50-100 kHz of each band, with the beacon sub-band on 10 m around 28.2 MHz. Many operators leave the top of the 80 m phone segment (about 3.790-3.800) as a DX window. On band edges, remember that the rule applies to your occupied bandwidth, not your dial readout. In USB, your signal extends upward from the dial frequency, so at the top of 20 m (14.350) you want the dial a few kHz below it. In LSB the signal extends downward, so at a lower edge like 3.800 for a General on 80 m, dial a few kHz above it. Aim for at least roughly 3 kHz of margin, and more if your audio is wide or your rig calibration is questionable. Check your dial against a known reference now and then. 60 m is the odd one out. It is channelized, not a continuous band. The US channel center frequencies are 5332, 5348, 5358.5, 5373 and 5405 kHz. For USB the dial frequency is 1.5 kHz lower: 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5. Privileges are General and above, power is limited to 100 W ERP referenced to a half-wave dipole, and the signal must stay within a 2.8 kHz channel. Allowed emissions are USB voice, CW and certain data modes. Other countries have allocated spectrum there differently, including a newer 5351.5-5366.5 kHz secondary allocation in many places. Verify the current US implementation before assuming you can use it.
  17. I'll take the first four. Station ID (§97.119): you identify with your FCC-issued call sign at the end of each communication and at least every 10 minutes during a communication. Tactical names like "Net Control" or "Shelter 2" are fine for operational clarity, but they never replace the call sign. Voice IDs have to be in English, and you can use the ITU phonetic alphabet. You can also ID in CW or in the digital mode you're using, as long as it's a mode the rules allow for ID. A repeater IDs under its own call sign, and that doesn't relieve the users of identifying themselves. Both the repeater and the users have to ID. Third-party traffic (§97.115): a third party is anyone other than the two licensed operators. A non-licensee can take part only while a licensed control operator is present at the control point, monitoring and ready to terminate the contact. The third-party rules also exclude certain people, such as someone whose license has been revoked or who is under a relevant cease-and-desist order. Internationally, it gets stricter. Third-party communications with foreign stations are allowed only where the US has an arrangement with that country, so check the FCC's current list before letting a guest talk. Contacts between two licensed hams are a different matter. This is mainly about handling traffic for people who aren't licensed. Power (§97.313): the headline is 1500 W PEP output, but the rule also says to use the minimum power necessary for the communication. Other limits sit on top of that. 30 m is limited to 200 W PEP, and the Technician HF privileges on 10 m are limited to 200 W PEP. 60 m has its own channel or segment structure and power limits in §97.303, so read that section directly. License class mainly determines where you can operate. It doesn't raise the power ceiling. Prohibited transmissions (§97.113 and §97.101): the big categories are communications for pay or in which you have a pecuniary interest, with a few narrow exceptions such as classroom teaching. You also can't use the service for communications that could reasonably be handled through other radio services on a regular basis. Music, obscene or indecent language, broadcasting, and messages encoded to obscure their meaning are prohibited. Deliberate interference is a separate rule. Occasional for-sale announcements of amateur equipment are allowed if they aren't a regular activity. Employer communications get a more nuanced treatment, so read the exact wording instead of relying on summaries.
  18. The mental model is right. One refinement on paths: the right choice depends on what digipeaters exist where you are. In an area with good wide-area digipeater coverage, a fixed station often needs only a single hop or none at all, and a mobile might use WIDE1-1,WIDE2-1 so that small fill-in digis and wide-area digis can both pick it up. In sparse areas, a longer path may be justified, but it should be a deliberate decision, not a default someone copied from a tutorial. Look at what your local APRS group recommends, because digipeater behaviour varies by region. On the handheld question, the same applies to the TH-D74/D75 and the FT5D. The radio is not the bottleneck, the antenna is. A rubber duck held against your body and used indoors can mean a perfectly configured radio never reaches a digipeater. If a position doesn't show up, check the radio's own APRS monitoring first. If you can hear the local digipeater and it hears you, the beacon should get through. If you hear nothing at all, the issue is coverage, not settings. One more tip on Mic-E: if your raw packet looks strange, decode it before blaming the radio. aprs.fi's raw view and Direwolf's own logs will both interpret it for you. The garbage-looking destination field is normal.
  19. On propagation, the habit that helped most is separating three timescales. Long-term cycle trend tells you whether 10 m and 12 m are worth watching at all. Day-to-day indices like SFI, A-index and K-index tell you whether today is likely to be disturbed. Real-time spots tell you what is open right now. People often mix these up and conclude the bands are dead because the numbers looked bad, when a quick check of spots would have shown a path open. For 6 m in particular, indices are a poor predictor, since sporadic-E openings can happen with unremarkable solar numbers. Leave a receiver or a decoder running on the calling frequency and watch spots from nearby stations. Setting up alerts in a logging program or a spot aggregator for the DXCC entities or grids you need also saves a lot of staring at a screen. For regulatory news, I'd add one more rule: if an article doesn't link to the FCC document or docket number, treat it as a pointer to look it up, not as the answer.
  20. The fifth SOTA Kentucky campout is planned for the weekend of April 17, 2027. People can come and go as they like, and a pancake breakfast is set for 8:00am ET on Sunday morning. Kingdom Come State Park has pencilled in the group for the weekend but won't take actual reservations until around February or March. The start time used here is the Sunday breakfast, April 18, 2027 at 8:00am ET. The announcement gives no other start time.Location: Kingdom Come State Park, Cumberland, KY, USA (the announcement gives no street address or postal code) Organizer: N4DCW (SOTA Kentucky Campout host, posted on the SOTA Reflector) Source: Event information
  21. Good thread idea. For anyone who has just passed the exam and is nervous about the first repeater call, here are a few practical points. Listen first. Leave the radio on the repeater for a while and get a feel for how people check in, how long they talk, and whether the repeater is busy. Check the repeater's listing for the output frequency, offset direction, and CTCSS/PL tone. If the radio is set up wrong, you may hear the repeater but not be able to key it up. When you call, keep it simple. Something like "(your callsign), monitoring" or "(your callsign), listening for a radio check" works. Phonetics help but are not mandatory. Many repeater users are glad to hear a new voice, and a radio check is a perfectly good reason to call. Test your setup before you depend on it. Try a simplex frequency with a friend or a club member. If you can get your hands on a second radio, you can try a short local test. Do not assume a handheld indoors will get into a repeater just because the signal bars look good. One more thing: avoid programming a long list of frequencies you do not understand. Start with a few local repeaters, the national calling frequency, and weather channels if your radio supports them. You can add more once you know what you will actually use.
  22. On copying on paper versus in your head, writing each character is a normal way to start because it gives you objective feedback: you can compare what you wrote with the source text. The trap is that writing can make you linger on a character and fall behind the next one. If you miss one, leave a dash or blank space and keep listening. Chasing the missed character is how people lose the whole word. Getting good at letting go is a skill in itself. To move toward head copy, begin by copying less. Try listening to short, familiar words or common call-sign formats and write only the answer afterwards. Then try recognising whole words, such as "the", "and", or the Q-signals and abbreviations you'll hear on the air, instead of individual letters. Words and common patterns start to sound like single units. When you can follow a slow transmission without writing, shift your attention to the content rather than the letters. It won't feel smooth at first, and you may want to go back to paper for new characters or higher speeds. That's normal. Expect a plateau somewhere in the middle of the speed range. It's common and usually means your brain is shifting from decoding letters to hearing words, which feels like going backwards before it improves. Rather than just pushing the speed, try varying the material: random characters, plain-text words, call signs, and callsign-and-number groups. Recorded QSOs and slow practice transmissions are useful too, because real operators have rhythm, mistakes and slightly odd spacing that computer-generated practice doesn't. For confidence, don't wait until you feel fast enough, because that day tends to keep receding. Prepare a few things you can send reliably: your callsign, name, location, signal report, and the standard exchange. Many CW operators are patient with beginners and will slow down if you tell them you're new, and a simple "QRS" request (please send slower) is perfectly acceptable. Listen first to a few real exchanges so the format is familiar, then make a short contact. Mistakes on the air are less dramatic than they feel in your head, and a clean, simple exchange is plenty to build on.
  23. The N/M rule is a good one and it's worth adding a correction for what the spot is worth. A multiplier on a spot that's already stale, or a station already being worked by a pileup, costs more time than an unspotted one you tune across yourself. So the break-even point is not fixed. You're comparing the QSOs you give up against the time to reach the mult, plus the probability that you will actually complete the contact. On SO2R: I'd stress the antenna side. Switching between radios is easy when each has its own antenna with good isolation. If both radios must share a tower or a stack, a lot of your "SO2R skill" becomes band-selection planning. Try to avoid pairing bands where harmonics or close-by fundamentals will desense the listening radio. Band-pass filters on each radio are a must-have rather than a luxury. After that, practice the audio and keying workflow until swapping focus is automatic. A footswitch or dedicated controller helps, but only if the software behavior matches what you expect, so test it with the radios disconnected from antennas before the contest. For fatigue, schedule your breaks around when the bands are producing the fewest multipliers, not around when you feel like stopping. Planning the rest gives you a much better chance of sticking to it.
  24. A few notes on phone versus CW, since that is where most mix-ups happen. On CW, shorthand saves time, so you'll see TNX (thanks), FB (fine business, meaning good or excellent), PSE (please), AGN (again), ES (and), WX (weather), RIG, ANT, UR (your), OM and YL (man and woman operators), GM/GA/GE (good morning, afternoon, evening), and TU (thank you). Prosigns like AR, SK, KN and BT are sent as one run-together character, not as separate letters. On voice, plain language is generally better. Q codes like QTH, QSL, QSY and QRZ are widely understood, but saying 'my location is' or 'what is your name?' is never wrong. QRM and QRN are fine, but 'there's interference here' is clearer for newcomers. Avoid CB-style ten-codes and slang, since they are not standard ham practice. For callsigns on voice, use standard phonetics when needed. The ITU alphabet (Alfa, Bravo, Charlie...) is the safest. A common beginner habit is saying 'CQ CQ CQ' with a callsign given only once, quickly. Giving it slowly, with phonetics, helps far more. Two small traps: 'QRZ' on voice is a question ('who is calling?'), not an answer, and 'QRZ.com' is the callsign lookup site, which is a separate thing.
  25. On the boundary question: treat the official reference list as the authority, not the park name. Look up the reference entry for the exact area, check its map or boundary information if one is available, and compare it with the POTA park page. Two programs can name the same place differently, and one park can sometimes contain several references or sit inside a larger one. If your operating spot is near an edge, set up well inside it. Don't rely on a GPS pin that might drift. It also helps to know the land manager's rules in advance. Permits, antenna restrictions, quiet hours and where you may park or put up a mast are separate from anything the award programs require. For the 44 versus 10 issue, the simplest approach is to plan for the larger number from the start. Once you have 10 contacts, POTA is satisfied, but you keep operating for WWFF. Calling CQ with both references in your exchange (something like "CQ WWFF and POTA") can reach both sets of hunters. Some hunters only chase one program, so mentioning both references at intervals avoids confusion. For logging, keep an ADIF file that records the reference fields correctly for each program, and check each program's upload instructions for which fields it reads. Don't assume one file will import cleanly everywhere without checking.

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.