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

Admin_Lee

Administrators
  • Joined

  • Last visited

  1. I'd begin with the same shared-path logic, but I wouldn't condemn the finals just because TX is dead. Most failed finals have a cause upstream or downstream, and if you swap the transistors without finding it, the new ones usually follow the old. Before you power up a replacement, check these: Bias network. Look for a failed trimmer, an open resistor, or a bias supply that is too high. Excess bias on a FET stage can overheat it quickly.Gate or base protection. Look for shorted or leaky parts in the drive path and the gate protection.Parasitic oscillation. Failed decoupling capacitors or bad emitter/source bypassing can leave a stage oscillating outside the band. You often see this on a scope as spurious high-amplitude RF with the carrier barely moving, or as power that doesn't track drive.Output network and relays. A burnt low-pass filter relay contact or a cracked capacitor in the filter bank can reflect power back into the finals.The reason it failed. Reflected power from a bad antenna is one cause. A broken SWR fold-back circuit is another, because the radio no longer protects itself.When you do replace them, set bias to the manual's spec with a current meter in the supply line, into a dummy load, and with the supply current-limited. Bring drive up slowly. If current climbs by itself or the heat sink warms with no RF out, stop and look for oscillation or bias runaway.
  2. This lines up with how I'd think about it, and I'd push one point further: build two kits, not one. A small "leave now" bag holds the HT, a spare battery pack, a roll-up antenna, the printed frequency list, a headlamp, a notebook, and your license and ID copies. A larger "stay put" tote holds the 12 V battery, mobile rig, coax, mast, and solar gear. Trying to make a single kit do both usually produces something too heavy to grab or too thin to run a station from. On the family layer, keep it simple. If someone has to read a manual to change channels, the radio won't get used under stress. Pick one FRS/GMRS channel and one backup, tape a card to the radio with the schedule, and practice it on an ordinary weekend. A privacy code (a CTCSS or DCS tone) is not security, so don't rely on it for anything sensitive. All it does is reduce the chatter you hear from other users.
  3. I'd push back a little on dropping the pencil early. Writing is not what limits most people at 10 to 12 WPM. Their recognition is still letter by letter, and if you take the pencil away before that changes, you just lose characters faster. A middle step is to copy only the first letter of each word, or only digits and callsigns, while listening to the rest as words. That forces word-level listening without leaving you with nothing. On decoders, I'd use them as a feedback tool, not as a reference during the session. Record the QSO, copy it by ear first, then run the recording through the decoder and look at the differences. Where your copy and the decoder disagree, listen again. Sometimes you misheard, and sometimes the decoder choked on a bad fist or a fade, which is also useful to know. Just keep the screen out of sight while you are actually listening. For nets, listen before you transmit. Hearing how experienced operators handle fills, repeats and prosigns teaches you the rhythm of the exchange, and most people there are happy to slow down if you ask politely with QRS.
  4. On noise, change one thing at a time and write down the result. If you move the power cable, add a ferrite and re-seat the ground at once, you won't know which of them helped. Start with a baseline: engine off, accessories on, then engine running at idle, then with the throttle raised. If the noise changes with RPM, suspect the alternator or ignition system. If it changes when you turn on a certain device, such as a dash cam, charger or LED strip, that device is the likely culprit. Cheap USB chargers are often a worse source of noise than anything related to the engine. On cross-band repeat, the main thing to remember is that you are still the control operator. You need to be able to identify properly, and the repeat function should only be used where it's allowed by your license and local rules. Using it for long periods can also make the radio run warm, so consider your power setting and ventilation. If you're not sure your model supports it, look in the manual's function list. Don't assume all dual-band mobiles offer it. For etiquette, the easiest rule is to leave a gap between transmissions on a repeater, especially in a mobile where you may be listening with road noise and not hear someone trying to break in. Keep calls short, and if traffic gets busy or you need to concentrate on the road, wait until you've stopped to continue the conversation.
  5. If I had to carry one antenna, I would lean toward a simple resonant wire for the band you plan to use most. A 40 m EFHW is about 66 ft of wire and a 20 m one is about 33 ft. A dipole fed with coax needs a support in the middle, which can be a pain on a summit, while an EFHW can be an inverted L or sloper off one tree branch. The 49:1 transformer will have some loss, so build or buy a good one and keep the radiator reasonably high. For power, an additional point on LiFePO4: use a fuse near the battery, and do not depend on a balance-charged pack you have never measured. A cheap in-line voltmeter is a good safety net. If you plan to build your own pack, a battery management board with protection is worth the small extra cost. And if you are interested in QRP-ARCI, look at their current contest and award rules before you go out, since exact rules and sections can change from year to year.
  6. I'd add a few points about what happens on the contest side and with uploads. Dupe checking is only as good as the contest setup. In N1MM+ the dupe rules come from the contest you select when creating the database, and a new database is typically created for each contest. If you pick the wrong one, or edit the exchange fields incorrectly, both the dupe sheet and the multiplier counts can be wrong. Check the entry window for a few sample calls on different bands and modes. Mixed-mode contests are the usual trap: some treat CW, phone and digital as separate for dupes, others don't. Also keep the band map sources straight. Spots that appear in a different color for worked stations only help if the log and the contest are set up correctly. For the band map, a cluster feed and a skimmer feed behave differently. Cluster spots can be wrong or delayed, and skimmer spots depend on the receiver. Treat both as leads, not as guarantees of what's on the air. When a spot of yours looks wrong, check the frequency offset before concluding the other station is off. For rotators, make sure the logger's idea of the beam heading comes from the same controller you actually drive (PstRotator, a hardware controller, or rotctld). Two programs commanding the same rotator is a quick way to get strange headings. For uploads: after a contest, import the ADIF into your master log, de-duplicate, and then upload. QRZ Logbook uses an API key tied to a specific logbook, and Club Log uses your login or an application password, so store those in the logger settings and don't paste them into forum posts. LoTW is the fussy one, because TQSL signs each upload against a station location and certificate. If the QSO date or entity doesn't match, it can reject the record, so look at the TQSL log after each run instead of assuming everything went up. If you use DXKeeper or HRD Logbook as the master instead of Log4OM, the same principle holds. Pick one program as the source of truth, import ADIF into it, and run the confirmation uploads from there. Don't upload from several programs to the same service, because that is how duplicate QSOs and confusing confirmation states get created. Finally, back up the database and the raw ADIF files before any bulk import, and keep the WSJT-X wsjtx_log.adi as an independent copy.
  7. For a first season I'd pick events with simple exchanges and room to be casual. CQ WPX is a good one: RST plus serial number is easy to log, and you can pick any 12 hours or so without feeling you've wrecked a 48-hour effort. Add ARRL Field Day for the group-operating side, a state QSO party in your region for county-hunting practice, and one of the ARRL VHF contests if you have any 6 m or 2 m capability. A basic SSB or FM/SSB station can still make grid-square contacts in a VHF contest. One trap with Sweepstakes: the check is the last two digits of the year you were first licensed, not the current year, and the precedence letter depends on your power level and category (for example Q for low power, A for high power). Write the exchange on a cheat sheet before the first QSO. Also note that the ARRL DX contest flips the exchange depending on whether you're W/VE or DX, so a US station sends state and a DX station sends power. Mixing those up is the most common mistake I'd expect to see on a first log.
  8. On noise, it helps to classify it before chasing parts. Noise that follows the supply, such as whine that changes with load, points to ripple or a switching supply, and also to a failing filter capacitor inside the rig. Noise that changes when you touch controls points to dirty pots or switches. Noise that appears only on certain bands may be the radio picking up interference from a nearby switching power supply or LED lighting, so try the rig on a battery or a different supply and a different location before opening it up. For capacitor replacement, the caution I'd add is not to assume a bad capacitor just because it looks old. Measure ESR or capacitance if you have a meter that can, and check the circuit around it. A scope on a supply rail will show ripple that a DMM completely misses. And when you do replace electrolytics, clean up any leaked residue properly, and check that traces and nearby solder joints haven't been eaten away, or the fault will come back.
  9. I would push back slightly on treating the ID-52A and TH-D75 as simple upgrades. They are more capable, but the features come with a learning curve. D-STAR needs your callsign registered with the network for some functions, and APRS needs proper settings (path, beacon rate, position source) so you are not cluttering the network. A radio you cannot operate fluently under stress is not a good emergency radio, so learn the basics before relying on it. For emergency prep, I would rank things roughly like this: licence and basic training first, then simplex frequencies and a printed channel list, then spare power, then a real antenna, and only then fancier features. A high-gain antenna on a mast can beat a more expensive handheld with a rubber duck. Many handhelds also let you pick low, medium, or high power, and dropping to low saves battery during long standby or net monitoring. Remember that the antenna matters on receive too. For the cheap-radio camp, treat a budget HT as a learning tool or a loaner, and read the specs and independent test results before putting it in a grab bag.
  10. On the 44-QSO target, the practical approach is to split the activation into two goals. Get to 10 first, because that secures the POTA credit. Then keep going to 44 for WWFF. Calling that out loud is a good habit, because it stops you from packing up early when the rate slows. For band strategy, a single band usually runs dry before you reach 44, so plan to change. If your first band is 40 m, a move to 20 m or 30 m often brings a fresh group of hunters. If you operate both CW and SSB, switching mode on the same band can also pull in new callers. Whether duplicates across bands or modes count toward the 44 depends on the current WWFF rules, so read them before you rely on a strategy built around that. On logging, I'd keep a clean field-log workflow: one log with the right date, UTC time, band, mode, and callsign for every contact, and the reference entered in a way that exports properly for each program. Test the export before the trip, not in the parking lot afterward. Look at how your logger writes MY_SIG and MY_SIG_INFO, and confirm what the WWFF log-upload system and POTA each expect. One more tip: say the reference clearly and keep your exchange short. 'CQ WWFF, CQ POTA' is clear on phone, and on CW, adding both programs to the CQ helps hunters from either side find you. Include the KFF reference when you post spots so hunters can match it to the right entry.
  11. For a first build, an EFHW is easier to get working, in my view. One wire, one support, and you can change bands from the radio. A linked dipole will usually beat it on efficiency, but you have to be disciplined about band changes and carry the right number of links or clips. If you mostly work 40 and 20, a linked dipole is a great choice. On the EFHW, don't skip the counterpoise discussion. A lot of reported problems with these antennas come down to RF on the coax shield. Try a choke at the rig, and if SWR changes when you touch or move the coax, that's a clue. A short counterpoise wire cut to something like 0.05 wavelength of your lowest band is a common experiment, though results depend on the transformer and how you feed it. On the pole: collapse it in sections from the top down when you take it down. People tend to yank it, and that's how the thin end sections get cracked.
  12. Good framework. I'd stress the point about who actually authorizes you. Being a licensed ham with a good radio doesn't mean an agency has to accept you, and it shouldn't. Self-deploying to an incident without being asked can create a safety and accountability problem for the people running it. The practical fix is to build a relationship with the served agency before anything happens. Find out what they use you for: shelters, hospital backup, EOC support, weather reporting. Ask what credentials, background checks or training they require, because it varies a lot between counties. Then show up to their meetings and drills so they know your face. I'd also be careful with the Part 97 and RACES details. Check what your state emergency management office says about when and how RACES stations can operate, rather than relying on forum summaries, mine included. Local plans can change what is allowed in practice.
  13. For me the main rule is to log once and export many times. Keep a single master log in your logging program, then upload from that to LoTW, Club Log, and anything else you choose to use. That way you're not fixing the same typo in four places. Do a periodic check of the data too. A wrong band, an incorrect grid, or a time entered in local rather than UTC will quietly produce non-matches for months before anyone notices. On DXCC, the practical approach is to use LoTW as the default and keep paper cards for the entities where LoTW isn't available. Check the current ARRL DXCC rules before you submit paper cards, because requirements for card checking and for what's accepted can change. Also keep your certificate backup (the .p12 file) somewhere safe. Losing it when you change computers is a nuisance, and it's not that hard to avoid.
  14. To add to the above, the CW/phone split matters. RST is the report you give another station. R is readability (1-5), S is signal strength (1-9) and T is tone (1-9). Tone applies only to CW and digital modes with an audible tone, so phone reports use just RS. A great phone signal is "five nine" (59), and a great CW signal is "five nine nine" (599). In contests, cut numbers are common: 5NN means 599 and N stands for nine. Reports should reflect what you actually hear rather than always being 59 or 599. A solid 59 can drop to 57 or lower when conditions or noise worsen. On CW you'll also see run-together prosigns: AR (end of message), SK (end of contact), KN (go ahead, named station only), BT (pause or break between thoughts) and CL (closing station). Common CW shorthand includes: ES (and), UR (your), TNX or TU (thanks), FB (fine business, meaning good), OM (old man, a male ham), YL (young lady, a female operator), XYL (wife), WX (weather), ANT (antenna), RIG (radio), HW? (how copy?), PSE (please), AGN (again), GM/GA/GE (good morning/afternoon/evening) and HI (laughter). On phone, plain language is better for most things. Most operators prefer "This is W1ABC" to "de," and clear speech over Q codes in everyday chat. You will still hear QTH, QSL, QSY, QRM, QRZ and QRT on voice. Use the ITU phonetic alphabet for callsigns (Whiskey, Alpha, Bravo, Charlie, ...) rather than improvised words, especially when conditions are poor. "Over and out" is redundant, because "over" means you expect a reply and "out" means you don't. Just say "clear" or give your call. For logging and nets, a typical log entry includes date and time in UTC, callsign, frequency or band, mode, power, RST sent and received, the other operator's name and QTH, and notes. Many hams log electronically and upload to services such as Logbook of the World for confirmations. Net terms: the net control station (NCS) runs the net and decides who speaks. A check-in is a station reporting to the net, and a roll call is NCS working through the list. "Traffic" means message handling. "Short time" means a check-in with limited availability. "Liaison" is a station that passes information between nets or groups. Q signals used in nets include QNI (I am checking into the net), QNX (you are excused from the net) and QTC (I have messages to pass). QRV means ready, QRX means standby or wait, and QRS and QRQ mean send slower and faster in CW. If your net uses tactical call signs like "Shelter 1" or "Net Control," you still give your actual callsign at the intervals required by regulations.
  15. On the net side, a script is useful as a checklist, not a performance. A solid one covers the net opening (purpose, frequency, who is control), a clear way to call for emergency or priority traffic first, a routine for check-ins that doesn't take twenty minutes, a procedure for handing off net control, and closing instructions. The hand-off piece is worth testing explicitly. Many nets run smoothly right up to the moment the first net control operator is tired, and then discover that the log, the open-traffic list and the station roster are all in one person's head. For the after-action report, I'd keep the structure plain: objectives, what was planned, what actually happened, what worked, what didn't, and corrective actions with an owner for each. The owner part is what separates a report people read from one that sits in a folder. Try to describe problems as system issues rather than personal ones. "Net control had no way to track outstanding messages" leads to a fix; "operator X was slow" does not. As for what goes in the report versus a private note, one rule of thumb: if the problem could recur with a different operator in the chair, put it in the report. If it was a one-off, such as a dropped coax connector, fix it and log it briefly. One more inject worth trying is a deliberate loss of the primary frequency, repeater or power source partway through, with the alternate plan written down beforehand. It shows whether people know the fallback or only know that one exists.

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.