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_Nancy

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Nancy

  1. One detail worth adding on D-STAR: it isn't just a different modulation. Calling through a repeater uses fields like MYCALL, URCALL, RPT1, and RPT2, and gateway use needs you to be registered. It is more involved than analog FM, so read the repeater trustee's instructions before you assume the radio will just work. The ID-52A and TH-D75 make it easier, but they don't remove the concepts. For emergency prep, I'd keep the setup simple. Put a few well-labeled memory channels at the front: local repeater, backup repeater, and simplex. Keep a printed copy of the frequency list with tones and offsets, because it's easy to lose a radio's memory if something goes wrong. Test it periodically on a net so the radio isn't a mystery when you need it. And the IC-705 comment above is right. It's a lovely radio, but it is a different category. If you want something for a pack or a go-bag, a dedicated HT plus a better antenna is a much simpler comparison.
  2. Agree with starting at power, and I'd add one thing: measure the rail at the point where it enters the board, not only at the connector. Contact resistance in the power plug or an internal fuse holder can drop a volt or more only when the transmitter is keyed. That gives you a rig that receives fine and seems to "lose power" on transmit, which looks like a weak PA but isn't one. On the SWR protection point, if it folds back into a dummy load, I'd compare the forward and reflected detector voltages with the manual's expected values before replacing anything. A detector diode that has gone leaky or a drifted trimmer in the bridge can produce a false high-SWR reading. A scope helps here too. If the reflected voltage is present when it shouldn't be, you may be looking at RF getting where it shouldn't, such as a parasitic oscillation, rather than a real mismatch.
  3. until

    ARRL-VEC license exam session run by the Troy Amateur Radio Association (N2TY) team, with a $15.00 test fee. Doors open at 9:30am, and no candidates are admitted after the 10:00am start time.Location: 1501 Broadway, Watervliet, NY 12189, USA Organizer: Troy Amateur Radio Association (N2TY) Source: Event information
  4. On the tools, these are roughly the roles they fill. LCWO (Learn CW Online) is a web-based trainer built around Koch-style lessons. You create a free account, it tracks your progress, and it adds characters in its own order. Its strengths are that it runs in a browser and keeps your place across devices. Besides the lessons it has text and callsign practice, which become useful once you know most of the alphabet. The G4FON trainer is a downloadable Koch-method program by Ray Goff, G4FON. It's a good choice if you prefer offline software. It also lets you tune character speed, spacing and the characters in the practice group. Check the author's site for current versions and platform support. Phone and tablet apps that call themselves Morse trainers vary a lot in quality and method, so I'd check a few things before trusting one. Does it let you set character speed separately from effective speed? Can you control which characters are in the practice set? Does it play the sound first, without showing dots and dashes? If an app can't do these things, it's better as a supplement than as your main method. CW Academy is different in kind. It's run by the CW Operators' Club (CWops) as free online classes taught by volunteer advisors. The levels run from complete beginner through fundamentals and intermediate to advanced. The value there is structure and a person who can tell you what you're actually doing wrong. You also practice with other students and get regular homework. Class availability and sign-up periods change, so check the CWops site for the current schedule. A sensible approach is to use a Koch trainer for your daily drilling and a class for guidance and accountability. For building confidence, a few things help. Listen to real CW even before you can copy it. You're training your ear to the rhythm and cadence of actual operating, and it makes the first real contacts less startling. Practice the standard exchange before you go on the air. Most casual contacts follow a predictable pattern: CQ, callsign, signal report, name, location, 73. If you can copy those pieces even when the rest is a mess, you can hold a basic QSO. Some operators write out their own callsign, name and location on a card so they can send them without thinking. Remember that slow operators are common and welcome. Sending 'PSE QRS' asks the other station to slow down, and most will oblige. Using a lower speed on the air than you practice at is also perfectly normal. Finally, expect to miss characters. Experienced operators do too, and they simply carry on or ask for a repeat with '?' or 'AGN'. A missed letter is not a failed contact. Getting comfortable with that is probably the biggest confidence step of all.
  5. For a first VHF kit, I'd keep it to a handheld, a decent antenna, a spare battery and a printed copy of your alert details. The antenna matters more than the radio. A rubber duck on a ridgeline often works, but a small directional antenna or a roll-up J-pole held up high makes the difference between calling into silence and getting answers. On a typical FM setup, announce yourself on the national simplex calling frequency or whatever frequency you listed in your alert, then move off it once someone answers so you don't tie it up. For the four-contact rule, send a clear alert and a spot, and keep calls short. Something like 'CQ SOTA, this is [call] on [summit reference]' is enough. The reference matters because chasers searching spots and logs need it exactly right. Also check the SOTAwatch alert page before you go for other activators nearby; S2S contacts on VHF are possible when two summits have line of sight.
  6. On the Smith chart, you do not need to master the whole thing. You need a handful of ideas, and the exam questions mostly test those. The center of the chart is the normalized impedance 1 + j0, so a perfect match to the system impedance sits right there. The horizontal axis is pure resistance. Points above it are inductive and points below it are capacitive. Moving toward the generator along a lossless line is a clockwise rotation, and one full trip around the chart is a half wavelength of line. Those facts alone answer a surprising share of the questions. The rest is usually reading off a normalized resistance or reactance, or recognizing that moving around a constant-SWR circle does not change the SWR. For antenna theory, get the dBi versus dBd relationship straight, since dBi = dBd + 2.15. Also know what front-to-back ratio, beamwidth and take-off angle describe, and how element lengths and spacing affect a Yagi's gain and feed impedance. For Part 97, read the actual rules alongside the question pool instead of relying on the answer key. The questions on control operators, station identification, third-party traffic and the allowed emission types are easier to retain when you see the context. As for the license itself, the Extra-only band segments are narrow, but the license does give full operating privileges on every amateur band and mode. Whether that is worth the effort depends on how much of that spectrum you want to use, and many people find the theory interesting in its own right.
  7. I'd choose by path, not by what's newest. If the nearest RMS is within VHF/UHF range and you have a radio with a good data port, VARA FM or packet is the first thing to test. It's fast, simple and uses a short, predictable airtime window. HF is for when the distance or the local damage means VHF paths aren't available. On HF the choices are usually VARA HF, ARDOP or Pactor, depending on what the nearby gateways actually offer. There's no point setting up a mode that none of the reachable gateways listen for. On gateway selection, don't just take the top of the list. Look at the distance, the band and time of day, and whether the path prediction is realistic. A closer station is not always easier on HF because of skip zones. Try two or three candidates and watch the session log. If the connection fails, check whether the failure is no answer, a handshake that starts and then dies, or a bad login. Those mean different things: path, level or audio problem, and account problem respectively. One setup habit that saves time is writing down the radio settings that work: USB or USB-D, filter width, audio level, PTT method and offset. When you need to move to a different band under pressure, you don't want to rediscover them.
  8. On the LiFePO4 cutoff: don't rely on the BMS as your low-battery warning. LiFePO4 has a very flat discharge curve, so the voltage looks fine until it suddenly isn't. A voltage reading is a poor fuel gauge for this chemistry. A shunt-based battery monitor that tracks amp-hours consumed gives you a real state of charge, and you can set an alarm at something like 20 to 30 percent remaining. Keep the voltage alarm as a second layer, but treat it as the last warning rather than the first. Also check the voltage under load, not just at rest. A healthy LiFePO4 pack runs about 13.2 to 13.3 V for much of its discharge and sits around 14.2 to 14.6 V when charging. Most modern HF rigs are happy anywhere in a 13.8 V ±15% window, but older rigs or ones with a tighter spec may complain at the top of the charging range. If your radio is picky, check its manual for the maximum input voltage before you wire it directly to a battery that's being charged. For noise, I'd plan the ferrites from the start. They're cheap and they take almost no space in the kit. Put clamp-on or toroid ferrites on the solar input, the controller output, and the DC leads to the radio. Then do a noise-floor test during setup: with the radio on a band you plan to use, switch the controller on and off, and the generator too, and note any change in S-meter reading. Keep that test as a line item on the checklist, because noise problems often depend on the specific band and on how the cables lie that day.
  9. For a first radio, the usual advice is to match the radio to what is on the air locally. If your area is mostly analog FM repeaters and simplex, a plain dual-band FM handheld like the FT-65R covers nearly everything. A multimode digital radio costs more and can sit idle if nobody nearby uses D-STAR or DMR. Digital handhelds pay off when your area has active repeaters or hotspot access. A hotspot lets you use D-STAR or DMR from home without a nearby repeater, but you then depend on an internet connection and the network's registration requirements. For D-STAR you register your callsign with the gateway and set MYCALL, URCALL, RPT1 and RPT2 correctly. For DMR you need a DMR ID and the right talkgroup and color code settings. On the antenna, the stock rubber duck is a compromise on both bands. A longer whip, or an external antenna on a mast or window mount, often improves range more than a more expensive radio. Check the connector first. SMA-female and SMA-male are easy to mix up, and adapters add loss and strain the radio's connector. If you buy an inexpensive radio, remember that the receiver can overload near strong signals such as pagers, broadcast stations and commercial transmitters. A radio that works fine in one location can be noisy in another, so test before relying on it.
  10. On the "translating in your head" problem: it fades naturally if you don't feed it. Never look at the character while it's being sent, and when you hear something you don't recognize, leave a blank and keep going. Stopping to work out one character means you miss the next two or three, and that's how people get stuck at the same speed for months. For daily practice, short and regular beats long and occasional. Fifteen to twenty minutes a day is usually better than one long session on the weekend, because your recognition improves between sessions. Stop when your accuracy starts dropping. Practicing while fatigued mostly reinforces errors. For flashcards and apps: audio-only drills are useful for the early characters, but a card that shows you the dit-dah pattern defeats the purpose. If you use spaced repetition (Anki or similar), make the prompt the sound and the answer the letter. Also, flashcards are a supplement. They don't replace listening to continuous code, because real copying involves groups of characters and words arriving at a steady pace. To move from pen and paper to head copy, there's a progression most people follow: 1. Write down every character, at a speed where you're mostly accurate. 2. Start recognizing whole words and common patterns (THE, AND, CQ, DE, 73), and write those as units. 3. Practice copying with a short lag, a word or two behind. Lag is deliberate: it lets your brain process the sound you just heard while you're still receiving. 4. Try listening without writing for a minute at a time, then check against a text file or a practice transmission. Software decoders can be handy for checking yourself, but don't rely on them. They struggle with noise, fading and irregular sending, and they won't teach you to copy. For confidence on the air, start with a standard exchange you can recite: callsign, signal report, name, location. Contests and POTA/SOTA activations are popular for beginners because the exchanges are short and predictable, and you can hear them repeated many times. It's also fine to send a slower CQ or say you're a new CW operator. Many operators are glad to slow down. If you freeze up, it's usually because you tried to copy everything. Aim for the callsign and report first and pick up the rest as you can. Expect plateaus, often somewhere in the low-to-mid teens of WPM. They're normal. Keep the routine going, mix in real on-air or recorded material, and your speed usually moves again without you doing anything special.
  11. My order is nearly the reverse of yours: live data first, forecasts second. If I can see WSPR spots from my area to where I want to work, or hear a beacon on the band, the prediction is mostly irrelevant. The indices become useful when you want to know why something is happening, or whether it's likely to last. One caution on WSPR: absence of spots is weak evidence. It requires someone to be transmitting and someone else to be decoding on that path. If a band looks dead on the map, check whether anyone is actually active in the direction you care about. Also remember that WSPR runs at very low power and decodes down to quite negative signal-to-noise ratios, so a spot doesn't mean you'll make an SSB contact with 100 W and a modest antenna. Treat the reported SNR as a margin, not a guarantee. For 6 m I do what you describe: watch for beacons and check spot maps for Es clouds, and only then bother calling. For the upper HF bands, I'd say a rising K index during an opening is a good reason to try a different path. Auroral paths can sound rough but be workable, and sometimes a southern route stays fine while the northern one collapses.
  12. The most useful distinction is between spots that say a station was heard and spots that say a station is worth calling. A DX cluster spot is usually a person saying they just worked or heard a station on a given frequency. It's great for finding rare or wanted stations, but it's only as good as the spotter. Busted callsigns, wrong frequencies and stale spots happen, so treat a spot as a lead and listen before you call. Check the time stamp, and look at how many independent spotters have reported it. RBN works differently. It's a network of automated skimmer receivers that decode CW and RTTY (and, as I understand it, some digital modes too) and report any CQ they hear, with signal-to-noise ratio and, for CW, speed in WPM. If you call CQ and then check RBN for your callsign, you get an objective list of which skimmers heard you and how strongly. That makes it handy for comparing two antennas or two power levels. It only covers stations that are calling CQ, and only where skimmers exist, so a blank result doesn't prove that nobody can hear you. PSK Reporter is the digital-mode equivalent. Software like WSJT-X can upload reception reports for every decoded station if you enable spotting, and the PSK Reporter map shows where your signal is being decoded. Because the reports come from many receivers, it's good for seeing real-time band openings on FT8 or FT4. Note that the map reflects where listeners happen to be, not where propagation exists. A lack of reports from a region may only mean no one is monitoring there. In short, use the cluster to find stations, and use RBN and PSK Reporter to measure your own signal.
  13. On mentors, clubs, and contests, because those are where a lot of new hams either get a big boost or quietly drift away. An Elmer doesn't have to be a formal teacher. It can be someone who answers questions on a net, helps you check your SWR, or lets you watch how they run a station. If you're not sure where to find one, go to a club meeting or a license exam session and ask. Most clubs have members who enjoy helping newcomers, though you may have to start the conversation. Saying "I'm new, and I'd like to learn how to do X" works better than a vague "I need help." Club meetings can feel cliquey at first, especially if the talk is about antennas, repeater controllers, or old rigs you've never heard of. Give it a couple of visits. Look for the club's net, its Field Day plans, or any demo nights where you can watch gear in use. Those are usually easier entry points than a business meeting. For first contests, don't think of them as a competition. A contest is a good, low-pressure way to practice. The exchanges are short, many operators send at a steady pace, and you'll quickly learn how to give your callsign, copy a callsign, and log accurately. Field Day, which many clubs run each summer, is especially welcoming because it's set up as an operating event and not just a scoring race. You can often sit with an experienced operator, log for them, or take a turn on the mic with someone beside you. If you do make an HF contact and the other station has trouble copying you, that's useful information, not failure. Try to figure out whether it was your antenna, your power, the band conditions, or just your callsign being hard to copy. Phonetics help a lot. Use standard ones, and say your call slowly and clearly.
  14. The exam is 35 questions and you need 26 correct (74%). That means you can miss 9, so you don't need to master every topic. You do need to avoid having one whole area go to zero. The question pool is revised on a multi-year cycle, so check the NCVEC or your VEC for which pool is current before you buy a book or an app. Using an outdated pool is the most common way to waste study time. On memorization versus concepts: do both, but handle them differently. For band privileges, don't try to memorize every frequency as a bare number. Learn the pattern. Each HF band has a bottom segment for CW and digital, with phone higher up. General gets more of the phone segments than Technician, and some segments are reserved for Extra. The exam usually asks things like "which of these frequencies is available to a General on this mode?" Knowing roughly where the CW/digital and phone portions sit on 80, 40, 20, 15, and 10 meters gets you most of the way, and you can then memorize the exact edges for the few bands that give you trouble. Learn the special cases separately: 60 meters is channelized, and 30 meters has no phone and a lower power limit. Verify any edge you memorize against Part 97 (§97.301 and §97.305) or the current ARRL band chart, because a study guide can have typos. For propagation, the questions mostly come down to a few ideas. The D layer absorbs lower HF during the day, which is why 160, 80, and 40 meters are better at night. The F layer does the long-distance refraction. MUF depends on ionization, which follows the solar cycle and time of day. Higher solar flux generally supports the higher bands. Disturbed geomagnetic conditions (high K or A index) can degrade paths. Once you can explain those, the questions become easy. For electrical principles, practice the math: Ohm's law, power (P = E × I), resonance, dB, and how reactance changes with frequency. A handful of formulas covers a lot of questions, and working problems on paper beats rereading. A workable plan for an hour a day: Weeks 1–2: Read one topic at a time and take a short quiz after each. Don't worry about scores yet. Weeks 3–4: Take full 35-question practice exams. For every miss, write down why the right answer is right. Final week: Go back to your weakest two topics, then take a couple of timed practice exams. If you're scoring in the low 30s consistently, you're likely ready.
  15. On the family side, the radio plan is only half of it. Set up an out-of-area contact everyone can reach, because during a regional outage it can be easier to send a text or call to someone far away than to reach someone across town. Agree on meeting points (home, neighborhood, and out of town), and on check-in times. Put it all on a wallet card with phone numbers, a frequency and channel plan, and a fallback if the first one fails. For license-free radios, remember what each service is. FRS radios are simple and need no license, but they have limited range. GMRS needs an FCC license, and as I understand it, one license covers the licensee's immediate family. It allows more power and repeater use. MURS has five VHF channels, runs at low power, and is also license-free. Use whatever your actual family members will carry and operate. A radio nobody understands is just weight. If you assign a channel, write it down, and don't count on privacy codes: they only filter what you hear and don't keep anyone from listening. A NOAA weather radio with SAME alerting and a battery backup is cheap and doesn't rely on cell service. Program in your county code and check it periodically. Many of them also run off AA cells, so they fit your battery plan. Many hams also carry a scanner or an HT that can listen to the weather channels. For first aid, a store-bought kit is a starting point. Add a tourniquet and gloves if you have trained on them, personal medications, copies of prescriptions, water purification tablets or a filter, and a few days of food and water. If you plan to support a served agency or net, find out whether they have their own requirements for ID, training and check-in before you show up with your kit.
  16. I'll take the first four. Identification (97.119): you must give your call sign at the end of each communication and at least every 10 minutes during one. There is no requirement to ID at the start of a transmission or at the start of a QSO. A 'communication' is a conversation with a station or group of stations, so if you finish a chat and go back to listening, ID at the end. During a long ragchew, ID inside the 10-minute window. On phone the ID must be in English, and phonetics are optional. Repeater users ID for themselves. The repeater's own timed ID identifies the repeater and does not stand in for the users. In a net, each station has to ID under the same rules, and a tactical call sign never replaces your FCC call sign. Third-party traffic (97.115): a third party is anyone other than the two licensed control operators in the contact, for example a family member who talks on the radio. The control operator has to be present at the control point and able to supervise and cut off the third party. Messages can't be a way of getting paid. For international contacts, third-party traffic is only allowed with countries that have an appropriate agreement with the US, or where the third party is themselves eligible to hold an amateur license. International traffic is also limited by 97.117 to remarks of a personal nature, so don't treat DX as a free-for-all message route. Third-party traffic generally can't be passed while a station is automatically controlled, with a narrow data-mode exception. Power (97.313): the general ceiling is 1500 W PEP, measured as power supplied to the antenna transmission line, not as ERP. Several limits sit below that. The 30 m band is limited to 200 W PEP, Technicians on the HF segments they have are limited to 200 W PEP, and 60 m is handled differently (ERP-based, channelized). Separately, 97.313(a) says to use the minimum power necessary to carry out the desired communication. The FCC doesn't hand you a number for that, but running full power into a local FM simplex contact or a strong-signal QSO is the sort of thing the rule is aimed at. Prohibited transmissions (97.113): the main ones are no pay-related communications where you or your control operator has a pecuniary interest, no business communications on behalf of an employer, no music, no obscene, indecent or profane language, no false or deceptive signals, and no codes or ciphers meant to obscure meaning. Exceptions are narrow. A teacher can be paid in connection with classroom use of the station. An occasional on-air sale of your own ham gear is fine, but a regular on-air swap business is not. Encryption is the one that confuses people. Publicly documented digital modes are fine, because the point of the rule is hiding the meaning of the message, not using a protocol the receiver has to decode.
  17. For injects, a few that tend to produce useful friction: the NCS has to hand off mid-exercise, a relay station can hear the net but can't be heard, a message arrives with a check that doesn't match the word count, and a served-agency contact asks for something nobody has a form for. None of these needs to be dramatic. They test whether people fall back on the plan or on habit. On the after-action side, I'd keep the report short enough that people read it. A format that works is a page or two with four headings: what we set out to test, what we observed, what to sustain, and what to fix, with names on the fixes. It also helps to separate observations from opinions. "Three stations couldn't hear the NCS on the primary frequency" is something you can act on. "Communications were rough" isn't. If you have a few people acting as evaluators who aren't also operating, they'll see timing gaps, unclear handoffs, and misheard calls that the operators themselves are too busy to note. As for what never gets fixed, power planning and message-form familiarity seem like safe bets in many groups. Both are tedious, and both are easy to put off until the next drill. If one corrective action gets an owner and a date after each exercise, that is probably better than a long list nobody tracks.
  18. On the master log: pick one program as the only place that talks to the online services, then keep it that way. Uploading the same QSO to LoTW, QRZ or Club Log from two programs is how duplicates and confusing status flags appear. QRZ and Club Log generally tolerate re-uploads of the same QSO. LoTW is different, because every upload is a signed file from TQSL, so it's worth keeping a note of which program handled which date range. For ADIF, the biggest trouble spots are mode and contest fields. FT4 is not a top-level mode in current ADIF. It's MODE=MFSK with SUBMODE=FT4. FT8 is its own mode. Older software or old export templates can mangle this, so check a few FT4 QSOs after any import.LoTW groups FT8, FT4 and similar modes under DATA when matching. A mode mismatch in your own log can look like a missing confirmation.Contest exchanges live in fields like STX, SRX, SRX_STRING and CONTEST_ID. Some programs keep them and some drop them on import. If you want the exchange kept for later, test with a small file first.Always check that date and time are UTC, and that band and frequency agree. A QSO with a wrong band is a common cause of rejected or unmatched uploads.For LoTW, the TQSL station location (callsign, grid, DXCC entity, CQ and ITU zones) must match where you actually operated. If you operate from more than one place, you need separate station locations, and the logger must select the right one. For QRZ, the Logbook API needs the key for that specific logbook, and it's separate from the lookup login. For Club Log, use an application password rather than your main password if the program supports it. When you import a contest ADIF into the master log, run any duplicate check the program offers first, and keep a backup of the log before the import. That is much easier than untangling an import afterwards.
  19. One planning habit that saves trouble is to work out both references before you go and write them in your notes: the POTA park number and the KFF number. Park and reserve boundaries aren't always drawn the same way in the two systems, so check each program's map or listing and don't assume they match. If you're near an edge, move well inside the boundary that applies to both. On the 44 count, the usual plan is to treat 10 as a checkpoint for POTA, not a stopping point. Once you pass 10, you have a valid POTA activation. Keep going and you may get the WWFF count in the same session. That means the log needs both references from the start. Fixing it afterward is tedious. Also read the rules on band and mode counting before assuming duplicates help or hurt. I'd rather check the program documentation than guess and find out at upload time.
  20. For the procedural pieces, here is a typical CW call and answer: CQ CQ CQ DE W1ABC W1ABC K CQ is a general call to any station. DE means "from." The K at the end means "go ahead, any station." An answer might look like this: W1ABC DE K2XYZ K2XYZ KN KN means go ahead, but only the named station. It tells everyone else not to jump in, which is useful in a one-on-one chat or when a pileup would be a mess. SK marks the end of a contact. It is sometimes sent before final call signs, as in "SK W1ABC DE K2XYZ." Be aware that "silent key" is also a term for a deceased ham. Context makes it clear, but it is a different usage from the prosign. AR (end of message) and BK (break, handing back and forth quickly) are also common on CW. RST is Readability, Signal strength and Tone. Readability runs 1 to 5, strength 1 to 9, and tone 1 to 9. Tone applies only to CW, because it describes the note quality. Phone uses just R and S, so a good signal is "five nine" rather than "five nine nine." Many contest exchanges send 59 or 599 regardless of conditions. That is a convention, but a more honest report is still more useful in casual QSOs. CW also has a lot of plain abbreviations beyond Q codes: TNX or TU (thanks), UR (your), ES (and), AGN (again), PSE (please), WX (weather), FB (fine business), GM/GA/GE (good morning/afternoon/evening), HW? (how copy?), DX (long distance) and CUL (see you later). They save keystrokes, but they aren't required, and new operators are better off keeping things clear than showing off. On phone, plain language is usually better. Q codes like QSY, QTH and QRM are still common, but most operators say "this is W1ABC" rather than "DE," and "over" or "go ahead" rather than K. Use the phonetic alphabet for call signs, especially in poor conditions. Avoid CB-style ten-codes, which aren't standard in amateur radio. For logs, record the date and time in UTC, band or frequency, mode, the other station's call sign, and the reports sent and received. Many people also note name, QTH or grid square, power, and QSL information. That is enough to confirm a contact later and to spot duplicates. On nets, the net control station (NCS) runs the session. Stations check in, which means announcing their call sign to be added to the list. Traffic means formal messages being passed. Net procedures vary by group, so listen first. You will often hear QNI (stations checking into the net) and QNX (net is excused or closing), and some nets use "short time" for stations that can only stay briefly. Always follow the net's script rather than assuming another net does it the same way.
  21. A practical order that works well: log accurately first, because everything downstream depends on it. Check that your UTC times, band, and mode are right, and that your station location in TQSL matches where you were actually operating. A mismatch there, or a portable operation under the wrong location, is one of the most common reasons a contact doesn't match or lands under the wrong entity. Then upload to LoTW regularly. After that, push the same log to eQSL and the QRZ logbook if you want those. Treat them as extras rather than the main plan if DXCC is your target. For the rare ones that never show up in LoTW, check Club Log to see whether the operator has an OQRS page, since that often tells you the preferred route and the cost. For timelines, there's no universal number. LoTW is as fast as the other station's uploads. A bureau can be so slow that you might want to stop waiting on it after a year or more. Direct depends on the country's postal service, the operator's habits, and whether they're actually active in the mail. If a QSL manager publishes a typical turnaround, trust that over a forum guess.
  22. For testing a new antenna or a power change, I would pair RBN and PSK Reporter and compare like for like. On CW, call CQ for a few minutes and note which skimmers heard you and at what SNR. On FT8 or FT4, do the same through PSK Reporter. Then change one thing and repeat. Conditions drift, so the comparison is only meaningful if the two runs are close together in time and on the same band. Remember that skimmer and reporter locations are not evenly spread around the world. A map full of spots into Europe says little about the Pacific if there are few receivers out that way. For travel, I would treat RepeaterBook as a starting point. If a repeater needs a tone or has restricted access, confirm with the owning club or local coordinator when you can. For exam prep, HamStudy's spaced repetition suits short daily sessions better than cramming, though it helps to read the explanations and not just memorize answers.
  23. I'd pull the goals apart. If the aim is DXCC credit, LoTW and approved paper cards are what matter. If the aim is simply a nice record of contacts, eQSL and a QRZ logbook are fine, and some people enjoy the cards themselves, which is a good reason to keep printing and mailing them. The mistake is treating all confirmations as interchangeable. On mailing, a few practical habits help. Put your callsign and the DX station's callsign on the card in large, clear characters, and match the band, mode and UTC time to your own log. Use a return envelope that fits the card flat, with sturdy cardboard or a stiff liner so it survives sorting machines. Some operators suggest keeping envelopes plain, with no radio-related markings, when mailing to countries where radio mail might attract attention; check local advice for the country you're writing to. For the bureau, don't expect fast results. Sort and send in batches, check the bureau's rules, and consider it a long-term pipeline rather than a way to get a confirmation this month. If a specific confirmation matters for an award deadline, use LoTW, OQRS direct, or another faster route.
  24. A current-limited bench supply is a good start, and I'd lean on it more than the first post does. Set the current limit conservatively, bring the voltage up and watch the standby current. If the rig draws almost nothing, you are probably looking at a missing rail, a failed power switch or a blown internal fuse. If it draws far more than the manual's standby figure, something is shorted or a regulator or capacitor has failed. That is much better than finding out with a big, unlimited supply that happily feeds a short until a track burns. On the SWR protection point: when a rig folds back power into a dummy load, I would check the dummy load itself and the coax jumper with a multimeter before opening the case. A cheap dummy load that is out of its range at higher frequencies, or a jumper with a bad center pin, can show high SWR on one band and look fine on another. If the same fault appears on every band into a known good load, then it is worth tracing the forward and reflected detector circuit. I'd also add that a DMM in the DC supply line is useful during bias setup, but check the meter's current range and fuse rating first. A 10 A meter range that is not actually fused for the 20 A the rig can draw is a bad surprise waiting to happen.
  25. I'd push back a bit on using a microcontroller for everything. For an APRS tracker, an ESP32 or Pico with a GPS module and a small AFSK modulator and radio module is a legitimate design, since the job is small, but for a fixed digipeater or iGate, Direwolf on a Pi is easier to tune and monitor. It handles multiple decoders, logs packets, and lets you adjust audio levels while you watch decode counts. The key is getting the audio levels right on both receive and transmit. Overdriven TX audio is one of the classic APRS problems, and a modest deviation setting on the radio keeps you from splattering the packet. On the RF side, an SWR meter built from a directional coupler and an AD8307 log detector gives a good dynamic range, but it needs calibration against a known load and a reference meter. Don't trust the displayed numbers just because the code produces a plausible-looking ratio. Diode detectors are nonlinear at low power, so apply a calibration table rather than a single scale factor. And for LCDs: an I2C backpack on a 16x2 or 20x4 character display is simple, but the long cables and RF in the shack can make them flicker. Keep the I2C runs short, add pull-ups of an appropriate value, and keep the wiring away from the feedline. If the display has to sit far from the controller, consider RS-485 or a differential link to the head unit rather than long raw I2C.

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.