Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.5
Wind 385.0 km/s
Aurora 1
Updated 13:00 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Mod_Dan

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Dan

  1. A good way to organise these is by what question you're asking. "Is the band open to where I want to work?" is best answered by PSK Reporter and RBN, because those are real receivers reporting real signals. "Who is on the air that I need?" is a cluster or alert question. "Who is this person?" is a callbook question. Mixing those up is what causes most confusion. With a cluster, spot filters matter more than anything else. Most nodes let you filter by band, mode, DXCC entity or spotter, and a few minutes of setup stops the feed from becoming unreadable. Skimmer spots are worth keeping separate from human spots, since an automated spot only says the signal was heard, not that the operator is actually working stations or listening up. One caution on PSK Reporter: it shows where your signal was heard, so a good map doesn't guarantee a two-way contact. The other station may have a noisy receive location or no transmit capability. Treat it as a measure of your transmit signal and the path, not a promise of a QSO.
  2. Contact your local EC or group leader first, because that tells you what your area actually requires. Some counties want ICS certificates, a background check or a registration form before you're listed on a roster, and some ask you to be known to the emergency management office before you can staff an EOC. Doing the FEMA courses at the same time is easy since they're self-paced, so get IS-100 and IS-700 done early and keep the certificates handy. On nets, listen before you check in. Pay attention to how net control calls for traffic, how stations give their call signs, and how short the transmissions are. Then volunteer for a simple role like logging. Net control is mostly discipline: keep a clear list of who's checked in, take priority and emergency traffic first, and don't let side conversations creep in. Learning that from the logger's chair is a gentle way in. For message handling, practice writing things down in a standard format. ARRL radiogram form is a useful starting point, but your served agency may use its own form, such as an ICS-213 General Message. Get a sample of what your agency uses and practice sending it by voice, phonetically spelling the unusual words and reading numbers clearly. The goal is for the receiving station to copy the message without needing to ask you to repeat it.
  3. Koch and Farnsworth aren't really competing. They answer different questions. Farnsworth is about timing. Each character is sent at a faster speed, such as 18 to 20 WPM, but the gaps between characters and words are stretched so the overall speed is slower. You still hear each letter as one fast sound, and you get extra time to think between letters. Koch is about how you introduce material. You start at your target character speed with just two characters. When you copy them accurately, usually around 90%, you add one more. Because you only ever hear whole-character rhythms and never a slow, drawn-out version of a letter, the habit of counting dits and dahs never forms. Many people combine them: Koch ordering for the character set, plus extra spacing at first that gets tightened as copy improves. LCWO and G4FON both support this kind of Koch-based practice. LCWO is browser-based, so your progress follows you from device to device. G4FON is downloadable software, which suits people who like a local program. Check each site for its current features, since they change. On question 3, the main rule is never to write or say "dit dah" while learning. Say the sound as a whole, like "di-dah" for A, or don't verbalise it at all. Don't look at a chart of dots and dashes either. Visual flashcards can undermine you because they train sight-to-symbol recall rather than sound-to-letter recall. If you want flashcards, use audio ones where you hear the character and then check the answer. For a plan, short daily sessions of about 15 to 20 minutes usually beat one long weekly session. Stop when your accuracy starts to fall off.
  4. I'll take the operating-rule half: ID, third-party traffic, power and prohibited transmissions. Station ID (§97.119). You must identify at the end of a communication and at least every 10 minutes during one. It is not every transmission. In a 40-minute rag chew you need your call sign at least every 10 minutes and again when you finish. Phone IDs must be in English, and the ITU phonetic alphabet is explicitly allowed. On digital modes, the ID has to use a method the rules allow, with publicly documented codes. Modes like FT8 and PSK31 carry call signs inside the protocol, but you are still responsible for making sure the ID requirement is met. Tactical calls ('Net Control', 'Water Stop 3') are fine as long as your FCC call sign goes out on the required schedule. Repeaters and auxiliary stations normally identify with the station's own call sign, usually via an automatic ID. Third-party traffic (§97.115). Here the licensed control operator is in charge. An unlicensed person can talk over your station only while you are present, monitoring and supervising, and you must be able to cut the transmission if needed. A person whose amateur license was revoked or suspended cannot be a third party at all. For stations outside the US, third-party traffic is only legal with countries that have a third-party agreement with the US. The FCC and the ARRL publish lists, so check before letting a visitor talk to a DX station. Emergency situations get special treatment elsewhere in Part 97, but don't treat that as a general loophole. Power (§97.313). The general rule is to use the minimum power necessary to carry out the communication. The ceiling is 1500 W PEP output for most privileges. Some segments have lower limits, such as 200 W PEP on 30 m, and HF-privileged Technicians are limited to 200 W PEP. The 60 m channels have their own ERP-based limits. Read §97.303 and §97.313 for the band you're operating on, because the lower limits catch people moving between bands. Prohibited transmissions (§97.113). The main prohibitions are: • Compensation to the control operator, or communications in which the control operator or their employer has a pecuniary interest. There are carve-outs, such as an occasional personal equipment sale and certain teaching situations. • Music, with narrow exceptions. • Obscene or indecent language. • False or deceptive signals. • Messages encoded to obscure their meaning. Space station telecommand and radio control of models have limited exceptions. This is why 'amateur-legal' digital modes use published protocols that anyone can decode. • Broadcasting, meaning one-way transmissions intended for the general public. There are exceptions for bulletins, code practice and similar content. A weekly net script read to net participants is a different animal from music or entertainment. The edge cases usually turn on who benefits and whether the content really is amateur communication. If you can't explain why it is an amateur-service communication, stop and read §97.113 again.
  5. Adding to the handheld and content side. If your message doesn't get acknowledged, check three things: the addressee, the message number and the path. Messages use the format :ADDRESSEE:text{msgno, with the addressee padded to nine characters. The receiver should reply with an ack carrying the same number, and the sender retries until it sees one. If the recipient is only reachable through an iGate, remember that the internet-to-RF gate only works if that iGate heard the recipient recently on RF. Objects and weather are useful but easy to overdo. An object has a nine-character name and is marked live or killed. A repeater, an event or a storm cell can be sent as an object by someone other than the thing's location. Send it at a sensible interval and kill it when it's no longer valid, otherwise it hangs around on maps. A weather station sends a position packet with the weather symbol and then wind direction, speed, gust, temperature, rain and humidity in a fixed format. In most cases, once every ten minutes or less often is enough. For SmartBeaconing on a mobile, keep the slow rate really slow when you stop. Many unneeded packets come from a parked vehicle beaconing as if it were moving. On handhelds in particular, expect the GPS fix and your antenna to limit things more than the settings. A rubber-duck antenna inside a vehicle is a weak signal to a digipeater. An external antenna and a decent path matter more than tuning the beacon parameters any further.
  6. On linking, the biggest etiquette change is time. Pause longer between overs, because a linked system adds delay and a short gap can mean two people are talking at once on opposite ends. Listen for a full cycle of transmissions before announcing anything. If the system is linked, name the node or room in your call if that is how people on the link identify themselves, and do not assume everyone listening is local to you. Also check the owner's rules for the link. Some systems keep the link up all the time, some bring it up for scheduled nets, and some use DTMF commands to bring it up or drop it. Do not issue link commands on someone else's machine unless the owner has said that is allowed. Dropping a link in the middle of a net is one of the fastest ways to annoy a club. With digital modes, the same idea applies in a different form. On DMR, a talkgroup can carry traffic from far outside your area, so listen on it before calling. On D-STAR, a misconfigured URCALL or reflector command can route your audio somewhere you did not mean. Read the system's usage page first.
  7. On the exam structure, the numbers you quoted are right: 50 questions, 37 to pass. One caution is that the question pool is revised on a multi-year cycle. Before you buy a study guide or start a practice-test app, confirm that it matches the pool your volunteer examiner team will use. The rules and band plans don't change much between pools, but individual questions and numbering do. For the electronics, a handful of relationships cover a surprising number of questions. For op-amps, know inverting gain as -Rf/Rin and non-inverting gain as 1 + Rf/Rin, and know what a virtual ground means at the inverting input. For bipolar transistors, know beta as collector current over base current, and be able to tell common-emitter, common-base and common-collector (emitter follower) apart by input and output impedance and by phase inversion. For resonant circuits, Q is reactance over resistance, and bandwidth is center frequency divided by Q. That lets you reason out answers instead of memorizing them. For oscillators, learn how to recognize them from the schematic. A tapped coil points to a Hartley, a capacitive divider in the feedback path points to a Colpitts, and a crystal in the feedback path points to a Pierce. For filters, know that Butterworth is maximally flat in the passband, Chebyshev trades passband ripple for a steeper skirt, and the shape factor is the ratio of the bandwidth at a deep attenuation point to the bandwidth at the 6 dB point. For the Smith chart, you don't need to be an expert, but you should know what the chart represents. The center is a normalized match (1 + j0, or SWR 1:1). The upper half is inductive reactance and the lower half is capacitive. Moving along the line toward the generator rotates you clockwise, and one full rotation is a half wavelength. Once you know that, most of the chart questions become reading exercises.
  8. For direct cards, the details matter more than the postage amount. Read the DX station's instructions first. Some want one card per envelope, some accept several QSOs, some want donations only through a manager's website, and some say not to send cash. If the station uses Club Log OQRS, using it can save you from sending a card for a QSO that isn't in the log at all. Also keep a note of when you mailed the request and what you enclosed. If you need to follow up, that helps you tell whether the card is just slow or you missed something in the instructions. On the design side, I'd push back a little on fancy cards. A simple card with a legible callsign, UTC date and time, band, mode and RST that fits on one side is more useful to a busy QSL manager than a glossy photo with tiny print. If you want something decorative, put it on the front and keep the info side practical.
  9. On logs: submit early and read the checklist. Before uploading, confirm your category (single-op vs. assisted, low vs. high power, band and mode selections) matches what you actually did, because a wrong header can put you in the wrong results table. Make sure your clock and time zone were correct, since logging in local time instead of UTC causes lots of problems. Most sponsors want Cabrillo, and many send you a confirmation email or show a log-received page. Keep that, and if nothing arrives, contact the log checkers rather than waiting for results. Also keep Winter Field Day and ARRL Field Day separate in your head. They share a name and some of the spirit, but different organizations run them with different class codes, scoring and submission systems. And since SOTA isn't a contest, activations during a contest weekend are usually logged under SOTA's own database as well as in whatever contest log applies. If you want to combine them, read both rule sets first.
  10. On the feedline question, think about what each option is solving. A 40 m dipole used on 20 m is a full-wavelength-long wire, and it presents a very different impedance, often a few thousand ohms at the feedpoint depending on length and height. Real 40 m dipoles don't land exactly on a 3x harmonic either. Coax can feed that, but the SWR will be high and the tuner has to cope with it. Open-wire or window ladder line handles this much better, because its loss stays low even at high SWR. The trade-off is that ladder line wants a balanced tuner or a tuner plus a 4:1 current balun. It also needs to be kept away from gutters, metal masts, and other conductors, and it should hang off the antenna symmetrically with as few twists as possible. For a choke on coax, the key number is common-mode impedance at the frequencies you use, not how many turns it has. A coil of coax gives a modest impedance that is band-dependent, and it can work well for one band and badly for another. Several ferrite cores (type 31 is the usual choice for lower HF, type 43 higher) threaded onto the coax give a broader, more predictable result. If you want to check it, use an analyzer to measure the impedance across the choke while it is disconnected from the antenna. A larger real-part impedance is better. Don't judge it by the SWR. If the ladder-line approach gets the nod, a single dipole fed with ladder line would also cover 80 and 15 m. At that point a fan dipole or traps are not needed, though you pay for it with a tuner and a more careful feedline routing plan. On traps, they let one wire cover several bands, but each trap adds loss, narrows bandwidth, and has to be weatherproofed. A fan dipole avoids the loss. Its drawback is that the elements interact, so you tune the shorter one first, then the longer one, then recheck.
  11. On studying, you don't need to buy everything. The Technician exam is 35 multiple-choice questions drawn from a public question pool, and the passing score is 26 correct. The pool gets revised on a multi-year cycle, so make sure whatever you study matches the pool in effect on your exam date. A book or app that's a cycle behind can have outdated questions. A workable combination: read the ARRL Ham Radio License Manual (or another current guide) once for understanding, then use HamStudy for repetition. The app tracks which questions you miss and brings them back, and it shows explanations. Take full practice exams once you've been through the material. Many people schedule the real test when they're scoring comfortably above passing, around the high 80s or better, rather than barely clearing 74%. Practice exam results are only a rough guide, but a safety margin helps on test day. Resist memorizing the position of the right answer. Test versions can shuffle choices. Instead, learn the idea behind each one: Ohm's law, the relationship between frequency and wavelength, basic repeater operation, what you must do when you identify, and RF safety. If you miss a question, read why, and don't just note the answer. For first steps after you pass: listen before you transmit. Scan the local repeaters, find a club or a weekly net, and ask members about their gear. A handheld (HT) is a common first radio for Technician, but check what repeaters are in your area before you pick one. Programming it is easier if you can see a local repeater list. Once your call sign is in ULS, introduce yourself on a net and ask questions. Most nets welcome new hams.
  12. Clubs and special event calls are separate paths with their own rules, so I'll cover them separately. Club stations. A club station license is issued to a trustee, who must hold a valid amateur license, on behalf of the club. The club needs its own FRN, and the license is tied to that trustee's information in ULS. Club licenses are typically filed through a club station call sign administrator, which is an arrangement through a VEC. If the trustee changes, the license record needs an update, because an out-of-date trustee is a common reason a club's callsign lapses unnoticed. A club can also request a vanity call, but the process goes through the administrator. Check Part 97 for what's allowed for your club's situation. Special event calls. The 1x1 calls are not part of the ordinary vanity process. They are meant for short-term, event-specific operation and are coordinated through a designated group rather than the standard vanity application. They're generally assigned for a brief window, often described as about 15 days, so confirm the current rules and application process with the ARRL or whichever coordinating group is currently handling them. Don't assume you can reserve one the way you'd request a vanity call. Applying for a vanity call. Prepare a list of acceptable calls in preference order. Check each one in ULS to confirm it's available and see whether it was recently held. The fee is paid through the FCC system, and the FCC publishes the current amount. Once granted, the new call replaces the old one, and you should update everything that carries your call: club rosters, logbook software, QSL services, repeater registrations, and so on. Your old call will not be reserved for you in any special way, so decide before you file whether you're sure about the switch.
  13. On the low bands, I'd stress that the receive side can decide the whole contact. A DXpedition on 160 might be running a few stations in an area with high noise levels. If their receiver can only hear the strongest signals, a wall of callers makes it worse. Often the most effective approach is to call once, listen for the response, and avoid long strings of calls. It also helps to be patient in the grey-line window and be ready to switch to another band if conditions change. For Club Log, the thing I'd point out is that it is a record-keeping and information tool and not a way to guarantee a contact. A DXpedition's log search can confirm whether your contact made it into the log, but a missing entry might just mean the upload hasn't happened yet. Keep your own timestamps (in UTC), frequency and mode so that if there is a mismatch you can check it. Also, before sending an OQRS request, check whether the operation is accepting them and whether LoTW is used. The last thing worth saying is about spots. Posting a spot is helpful when you've verified the callsign and listening frequency, and a good spot comment mentions things like 'up 2' or 'listening 5-10 up'. A spot that just says 'DX' with a rough frequency often sends people to the wrong place. Spot only what you've actually confirmed, and don't repeat a spot that is already on the cluster.
  14. For me the first thing is to separate "rate" from "rate that matters." A run at 100 Q/hr where half the calls are on a band whose mults you've mostly worked is different from a 70 Q/hr run that includes new zones and countries. Some operators keep a mental threshold: stay as long as the run is producing a new multiplier at least every N minutes or the rate is well above what S&P would give you. Pick N before the contest and don't relitigate it every ten minutes. On skimmer spots, a decent habit is to verify before committing. A spot for a rare mult is worth a quick listen for the callsign before you call, and on SO2R you can do that on the second radio with the run radio still calling CQ. If the call looks like a partial or a likely bust, wait for a second skimmer spot or hear it yourself first. Calling a busted spot wastes time on the target and may add to the problem for others. One more point about band changes: not every band change is the same. Moving from 20 to 15 when 15 is open and loud is a different decision than moving from 40 to 80 at dusk when the whole band is filling up with QRM. In the second case you may lose rate, but you gain access to a pool of stations that wasn't there an hour earlier. Writing a simple band plan before the contest, with rough times when each band should be productive for your location, makes these calls less emotional on the day.
  15. The "NATO" alphabet, the ICAO alphabet and the ITU radiotelephony alphabet are for practical purposes the same list of 26 words: Alfa, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu. The official spellings are "Alfa" and "Juliett" so that non-English speakers pronounce them correctly. On the air, almost everyone says and writes "Alpha" and "Juliet", and that is fine. The list was designed and tested so the words are distinct across many native languages, not just English. That is why it works well for international contacts. Making up your own words has no legal penalty in most places (check your own regulator's rules, as I wouldn't assume every country is identical), but a non-native listener who has memorized the standard list may not recognize "Kentucky" for K or "Radio" for R. Words like "Lima" and "Mike" are well known, whereas a personal word may need a second to decode, and in weak signals that second matters. My practical rule is to use the standard words by default, especially on DX, in contests, or with anyone whose first language may not be yours. On a local FM repeater with friends, nobody will care much. Just don't rely on a clever word you've used for years being understood by a stranger. On numbers, the ITU list also defines special number words (Nadazero, Unaone, Bissotwo and so on), but they are almost never used by hams. What you do hear in aviation-influenced speech is "niner" for 9, which keeps 9 from being confused with "five" or "nein", plus sometimes "tree" and "fife". For ham use, saying each digit clearly and separately is normally enough, with "niner" as an option if 9 keeps getting lost. Say callsign digits individually, so "W1AW" is "W, one, A, W", not "W-eighteen".
  16. I would put ICS and net discipline ahead of buying more gear. Radios are the easy part. What causes trouble is usually people transmitting without listening, or the message arriving garbled because nobody used a form. One thing I'd add to the go-bag list is a printed copy of everything you rely on a phone for: frequency plan, contact roster, and the agency's address and check-in procedure. If cell service is down or your phone dies, you still need to know where you are going and who to call. Also write down your own callsign and tactical assignment on a card you can hold up. It sounds minor, but it helps when someone at a shelter needs to know who you are. For exercises, ask the organizers to include at least one message that is deliberately awkward, like a long list of numbers or an unusual spelling. People get better at phonetics and read-back quickly when they hit something that doesn't fit the easy pattern.
  17. On the radio choice, I'd decide on mode and menu workflow first. If your area has active D-STAR, the ID-5100A makes sense. If it's Fusion, the FTM-500D is the matching option. If it's mostly analog FM, the TM-D710G's strength is its mature feature set, with APRS and cross-band repeat built in. Whichever you choose, check the manual for the specifics you care about instead of relying on forum memory, including mine. Feature lists differ by model and revision, and cross-band repeat in particular isn't something to assume. One practical tip for any of them: program your most-used memories before you drive. A touchscreen or a dense menu is fine when parked, but fiddling with it at speed is how people get into trouble, and many places have laws about handling devices while driving. Set up memory banks so the radio is nearly one-knob operation, and stick to listening and short, simple transmissions while the vehicle is moving. For fusing, it's worth stating the reason: the fuse at the battery protects the wire, not the radio. If the cable shorts to the body anywhere along its length, the fuse near the battery is what stops it from heating up. That's why the fuse belongs close to the source, and why you shouldn't tap into an existing circuit or replace the fuse with a higher rating just because it blew. If it blows repeatedly, find the cause: a pinched cable, a bad connector or a wiring mistake.
  18. One suggestion on workflow: model first only to pick a target length and see how sensitive the design is to height, then build with extra wire at the ends. A model will tell you things like "the resonance moves by X kHz per foot of height change," which helps you decide how much trimming margin to leave. It will not tell you your actual resonance, because soil, nearby metal and sag are not in it. For checking the final result, I would keep two measurements separate. Measure resonance and impedance with a VNA at the antenna feedpoint, ideally with a short jumper. Then measure again at the end of the actual feedline in the shack. If the two differ much, you are seeing feedline loss or common-mode current. That difference is itself a useful diagnostic. A good test is to touch or move the coax and see whether the reading changes. If it does, the choke is not doing enough. On traps versus fans: if you only need two or three bands and have space for the extra wires, a fan is usually less work. Traps make more sense when you have a fixed length limit and cannot spread the wires out.
  19. On the DX side, I would stress that the best audio is not the same as the loudest. In a pileup the station you are calling is using a narrow receive filter, often not far from 2.4 kHz or less, and may be listening through QRN and fading. The signal that gets through is usually the one with clean, consistent modulation and a clear callsign, not the one with the heaviest processing. Overprocessed audio can also hurt copy when the band is noisy, because the compressor lifts the noise between words and makes the speech harder to follow. Another practical point is split operation. When the DX is listening up, make sure you have actually set your transmit frequency correctly and are not drifting while you adjust gain. Also keep an eye on your own splatter, since a signal that is slightly overdriven in a pileup will annoy nearby stations as well as hurting your own chances. If you can, ask someone a few kilohertz away how you sound. A quick report on whether you are splattering tells you more than another change at the EQ.
  20. Start with the mode, because it decides most of the rest. If you only plan to work CW, a Mountain Topper or TR-35 gives you the best weight and current drain per contact. If SSB matters even occasionally, the KX2 or KX3 make more sense, since a CW-only rig can't do it at all. Note that a Pixie-style rig is closer to a build-and-learn project than a practical field radio. Its receive selectivity is very wide and its output is low, so it is best used as a bench project or for experiments on a quiet band. On power, 5 W versus 100 W is a 13 dB difference. At roughly 6 dB per S-unit, that is a bit over two S-units at the receiving end. So a QRP signal is not hopeless. It just needs a decent antenna and a good choice of band and time. The antenna is where most of your effort pays off. Height, a clean feedpoint and low-loss coax matter more than squeezing a little more power out of the rig. On calling frequencies, these are the commonly used QRP spots. Check the band plan for your region, because they can differ: CW: about 1.843, 3.560, 7.030, 10.106, 14.060, 18.096, 21.060, 24.906 and 28.060 MHz. On 40 m, 7.040 is also used in some regions.SSB: about 3.985, 7.285, 14.285, 21.385 and 28.885 MHz.These are meeting points, not reserved frequencies. If someone is already there, move up or down a few kHz. Many QRP-ARCI contests count 5 W CW and 10 W PEP SSB as QRP output, but read the current rules for any event before you operate, since the exact categories change.
  21. My suggestion for someone starting out is to pick one primary award and let the others come along as side effects. WAS and WAC fall out of regular operating, and a WPX tally grows without much planning. DXCC takes longer, so give it a clean base: one master log, with the confirmation status of each QSO recorded in its own field. On LoTW, a match depends on both stations uploading signed logs with consistent data. That means call, band, mode and time need to agree within the matching tolerance. The usual reasons for a missing confirmation are a wrong mode (for example, logging FT8 as plain DATA in one place and something else in another), a portable or alternate callsign that was never added to your certificate setup, or a QSO date that fell on the wrong side of UTC midnight. If a QSO should be there and isn't, check those before assuming the other station never uploaded. For entity credit, remember that DXCC is based on the entity list in effect and on the callsign and date of the contact. A QSO with a station operating from a location that was a different entity at that time counts for that entity, not today's. Deleted entities still sit in your overall total but not in the Honor Roll calculation, which is worth knowing before you spend time chasing old paper QSLs.
  22. One angle that gets skipped is repairability. A lot of older rigs came with schematics and were designed so a hobbyist with a decent meter and a soldering iron could fix them. Modern surface-mount radios are far more capable, but when something fails it can be a service-center job or a parts-unavailable situation. That's a real factor when you decide what to keep for the long haul. The flip side is that vintage gear has its own risks: parts that are no longer made, wiring that's been modified by previous owners, and lethal voltages inside tube equipment. If you're new to working on it, read up on discharging capacitors and use proper precautions before you open anything up. A radio you can't safely work on isn't much of a keeper. For the classifieds question, I'd always ask whether the seller will let you see it powered up, or at least provide a video showing receive and transmit on a couple of bands. A vague "works fine" doesn't tell you much. Also, factor in packing: a 40-pound radio in the wrong box will arrive in pieces, and the shipping cost can change what a fair price is.
  23. On rigs, the choice mostly comes down to what you want to do. If you plan to operate CW only and want the lowest possible weight and current draw, the Mountain Topper or TR-35 fit that goal well, because they're built around that single job. The KX2 or KX3 make more sense if you want SSB or digital modes without carrying a second radio, and if you value having a good filter and a full set of controls on the hill. The trade-off is cost and a more complex menu system. Don't overlook the build-it-yourself route. Kits such as the Pixie are a useful way to learn how a transmitter and receiver work, even if you wouldn't choose one as your main station. If you're interested in building, a simple direct-conversion receiver is a good first project, and QRP-ARCI is a good community to ask about construction and about contest and award activity. On the air, call CQ on or near the QRP spots and listen for replies, since a tight CW signal often does better than expected.
  24. For a modest station I'd pick one event from each of three groups. Take a DX event where you only have to learn one exchange, like CQ WPX or CQ WW. Take a short-duration event with a simple exchange, such as a state QSO party or a VHF contest. Then take one event that teaches you something new, like Sweepstakes or a digital contest. On Sweepstakes: the exchange looks scary, but it is the same four elements every time. Serial number, precedence (Q, A, B, U, M, S), check (the last two digits of the year you were first licensed), and section. Put a template in your logging software and the fear mostly goes away. A common mistake is copying the call and serial wrong, so ask for fills sooner than you think you need to. On Field Day versus Winter Field Day, read the category definitions in each ruleset separately. The exchange formats look alike, but the class letters and what they mean differ between the two, and it's easy to mix them up if you do both. For logs, I'd set up the Cabrillo header (category, operator, power, bands) once in your logging program before the contest starts. Fixing it afterward is where most submission errors come from. Check the rules for the deadline, since it varies by sponsor and some are only a few days after the contest ends.
  25. On direct cards, the biggest time-waster is incomplete paperwork. Before sending anything, check the QSL route listed for the DX station. Some want an SAE plus one or more US dollars, others use a manager, and others strongly prefer LoTW or OQRS only. Sending a card to the wrong address, or to a station that doesn't answer direct mail, is the usual way to end up waiting for nothing. A practical package is: your card filled in with the contact details, a self-addressed envelope sized to fit it, and the postage or funds they asked for. Many operators put the card inside a folded sheet of paper with the cash so it isn't visible through the envelope. If you send via the bureau instead, sort cards by prefix and follow your national society's rules for outgoing envelopes, since they differ. As for design, a printed back-side space for notes like "TNX QSO, 73" or "PSE QSL" is useful, but the more important thing is that the date and time are in UTC and clearly labeled. A card with local time and no zone can be rejected by a manager who can't match it to the log. And on timelines, I wouldn't quote a fixed number for bureau or direct. It depends on the manager, the country, and the postal system, so treat any figure as a rough guess and check recent reports for that specific route.

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.