Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

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

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

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

Mod_Mike

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Mike

  1. I'd start with what the local repeaters actually run. If your area is mostly analog FM, a good analog dual bander covers nearly everything you'll hear. Extra digital features sit idle if nobody around you uses D-STAR or DMR. Look up the repeater directory for your area, see which modes are common, and buy for that. On the Baofeng question, the radio is fine for learning, but I'd put the saved money into a better antenna and a spare battery. Those two changes often improve the experience more than switching to a pricier radio. Just be aware of the receiver overload issue near strong transmitters, and consider a different model if you notice it. On CHIRP, I'd stress the habit of reading from the radio first and saving the image. It sounds boring, but it means that if a bad write messes something up, you can restore it.
  2. Start with the distinction you raised. The FCC rules (47 CFR 97.301 through 97.313, roughly) are the legal limits. They define which bands each class can use, which emission types are allowed in which segments, and the power limits. A band plan is a gentleman's agreement layered on top. If you call CQ on SSB in a spot the ARRL plan reserves for digital but the FCC allows phone there, you haven't broken a rule, but you'll probably get a lot of QRM and some unhappy FT8 operators. For the HF license privileges in the US, here is how I'd lay it out: Extra has everything. General has most of each band, but the bottom of each phone subband is held back. For example, on 80 m General phone starts at 3.800 (Extra at 3.600), on 40 m at 7.175 (Extra 7.125), on 20 m at 14.225 (Extra 14.150), and on 15 m at 21.275 (Extra 21.200). General CW and data start a few kHz up from the band edge, at 3.525, 7.025, 14.025 and 21.025. Technicians get CW on 80, 40 and 15 m in the 3.525-3.600, 7.025-7.125 and 21.025-21.200 segments. On 10 m they get 28.000-28.500, with SSB phone on 28.300-28.500 and a 200 W PEP limit. Technicians have no 160 m, 60 m, 30 m, 20 m, 17 m or 12 m privileges. On band edges, remember that the dial frequency is not the signal. In USB your signal sits above the displayed frequency, and in LSB it sits below. An SSB signal is about 2.5 to 3 kHz wide. A General on 80 m LSB parked at 3.800 is therefore transmitting partly below the General phone limit. Staying about 3 kHz inside the edge is a reasonable habit, and it also covers some dial calibration error. The same logic applies at the top of the band, where USB on 20 m at 14.349 would spill past 14.350. A few HF bands deserve their own note. 30 m (10.100-10.150) is CW and data only, no phone, with a 200 W PEP limit. 17 m and 12 m are the WARC bands, so contests stay off them by convention. For FT8, the common dial frequencies are 1.840, 3.573, 7.074, 10.136, 14.074, 18.100, 21.074, 24.915 and 28.074 MHz. Those are conventions, not regulations. Digital activity clusters there, so phone operators should stay off them. 60 m is not a band you can tune freely. The US has five channels, with USB dial frequencies of 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz. General and above can use them, with a 100 W PEP ERP limit referenced to a half-wave dipole. Phone, CW and bandwidth-compliant data are permitted. The channel centers are listed a bit differently in the rules (5332, 5348, 5358.5, 5373 and 5405), which is why people get confused. If your radio is set to a channel center rather than the USB dial frequency, you'll be 1.5 kHz off the intended spot. Amateurs are secondary users there, so listen before you transmit. Double-check the current rule text before you publish, since 60 m has been revised more than once.
  3. The MARS/CAP point deserves emphasis because it gets garbled a lot. A hardware or software mod makes the radio capable of using frequencies. It doesn't authorize you to use them. If you're a member of one of those organizations, follow the current guidance for approved equipment, frequencies, and programming. If you're not authorized, don't transmit there. Some people also forget that the rules for ham gear don't carry over to GMRS or FRS equipment, which is certified for a specific service. On power, I'd add one practical rule: treat the fuse and wiring as part of the mod. A high-capacity LiFePO4 battery can deliver a lot of fault current, so an unfused lead is a bigger risk than a weak battery would be. The same goes for a DC-DC converter you add to power a fan or accessory. Check it with an AM receiver for noise before assuming it's quiet, and put a ferrite or filter on the leads if it isn't. For firmware, my general approach is to read the release notes and make a backup before updating anything. Stable firmware you know works is better than the latest version with a feature you may never use.
  4. On study material: you don't have to choose between HamStudy and the ARRL manual. They work well together. HamStudy is built around flashcard-style spaced repetition and practice exams that use the actual question pool. The ARRL manual explains why the answers are what they are: how an antenna works, what a repeater does, how band plans and rules fit together. Many people read a chapter, then drill that chapter's questions in the app. If you only memorize answers, you'll pass, but you'll feel lost the first time you try to program a radio or pick a frequency. For practice exams, aim for consistent scores well above the 74% pass line, around the high 80s or better, across several different attempts. One lucky 80% doesn't tell you much. When you miss a question, read the explanation instead of just noting the right letter. Many questions in the pool have distractors that are obviously wrong once you understand the concept. On exam day, read every answer choice before picking, and don't change answers unless you can name a specific reason. Unanswered questions score as wrong, so guess if you're stuck. VEs generally grade your exam while you wait, so you'll know quickly. After you pass, the VE team submits your paperwork to the FCC through their coordinator. Your license becomes official when the FCC grants it and your call sign appears in the ULS, the Universal Licensing System. You can search the ULS by name or FRN, and the VEs will tell you when to expect the grant. Don't transmit until your call sign shows up there. The ULS record is also where you update your address and email later. For first steps after that, listen on a local repeater before you transmit, and look up your area's repeater listings. A local club is a good place to ask about nets. Technician privileges cover VHF and UHF and include some limited HF segments, so a handheld is a common first radio. Ask your club what works well in your area before buying one.
  5. On difficult conditions, the biggest improvement usually comes from slowing down and keeping a steady rhythm, not from fancier words. Say each phonetic clearly, with a very small pause between letters, and don't run the whole call together. With QSB, repeat the call at a measured pace rather than faster. In a pileup, give only your callsign, once or twice, and avoid adding extra chatter. If you're answering a call from a station that gave only a partial callsign, repeat back what you copied so they can correct it. Numbers: in callsigns, just say the digits. The ICAO-style pronunciations ("wun, too, tree, fower, fife, six, seven, ait, niner") are mainly an aviation convention, but "niner" is widely used by hams because plain "nine" can be mistaken for the German "nein" or confused with "five" on a weak signal. Say "zero" rather than "oh", so that it can't be confused with the letter O. For grid squares, treat them like a callsign, for example FN31 as "Foxtrot November three one". Names and locations: announce that you're about to spell, and the other operator knows to switch from listening for meaning to listening for letters. For example, "My name is Kari, I spell: Kilo, Alfa, Romeo, India." Do the same for town names and unusual words. Letters that are easiest to confuse by ear (B, D, P, T, V, M, N, F, S) are the ones to spell phonetically rather than by letter name. For portable or mobile operation, say "portable" or "mobile" and the slash or stroke explicitly, since the suffix can otherwise be lost. On nets and emergency traffic, discipline matters more than vocabulary. Check in with your callsign in phonetics, and only use a short suffix check-in if net control asks for it. Use plain procedure words: "over" when you hand over, "out" when you are finished, "say again" if you didn't copy, and avoid "over and out" because the two words contradict each other. Real distress and urgency calls use "Mayday" and "Pan-pan" on voice, and amateurs should follow any local emergency-net procedure and net control's instructions. For written message traffic such as radiograms, numbers and unusual words are usually spelled out and counted, so read the figures slowly and spell anything that matters. On CW the equivalents are prosigns such as AR (end of message), SK (end of contact), BT (break or pause) and KN (go ahead, specific station only), which are sent as a single run-together character rather than separate letters.
  6. Your framing of grounding is basically right. A ground rod that's a few feet long won't do much for the RF performance of most field antennas, but it can bleed off static and give you a reference for equipment bonding. The bigger things are a well-placed choke on the feedline and a counterpoise or radial set that suits the antenna. An end-fed or vertical with no counterpoise will use your coax shield as one, and that's how you end up with RF in the shack and a noisy receive. Chokes at both ends of the coax are cheap insurance. For lightning, no field ground setup is protection. The rule is to monitor the weather, disconnect the feedlines from the radios, and move people away from the mast when a storm gets close. A few safety items that belong on the setup list: pick the mast location by looking up first, and keep the whole mast, with guy lines and a margin for it falling, clear of any overhead power line. Put the generator at least 20 ft from the shelter with the exhaust pointing away from tents, and have a battery CO alarm inside. Don't connect the generator to the station wiring in any way that could backfeed anything. Check your generator's manual about neutral bonding if you ever run AC through a distribution strip, and leave the layout as 12 V only unless you have a reason otherwise. On the coax: at 2 m, RG-58 class cable loses roughly 4 dB per 100 ft and LMR-400 class about 1.4 dB, and the gap widens at 70 cm. For HF, loss is negligible over a short run, so RG-8X is fine. The real cost of coax on HF is the weight pulling on the mast, so use a strain relief and don't let the cable's weight hang on the feedpoint. For teardown, add these: photograph or note anything that failed or was awkward before packing it away, return the battery to a storage charge level rather than leaving it empty or full, check the fuses and connectors for heat discoloration, dry the guy lines and tent before bagging, count the stakes and the Powerpole pigtails, and log the final hours of generator runtime so the next deployment knows what the fuel plan really was.
  7. I'd treat it as a hardware problem first, because firmware can't fix a processor that's being fed RF. A very common failure path is common-mode current on the USB cable. The coax shield, station ground and cable shield all form loops, and the cable becomes part of the antenna system. Clamp-on ferrites help, but the most effective approach is usually a few turns of the USB cable through a mix 31 or similar HF-suitable core, close to the controller and again near the rig. Put the common-mode choke on the cable, not just a single snap-on bead. For CAT lines I'd add the usual protection at the connector: a 100 pF to 1 nF capacitor to ground on each signal line and a series resistor of a few hundred ohms where the protocol tolerates it. Don't add capacitance blindly on CI-V, because the bus is open-collector and extra capacitance slows the edges at higher baud rates. If a Pi is running rigctld, keep the Pi and the microcontroller on separate power or filtered supplies. Let them talk over Ethernet or Wi-Fi rather than a long serial run, so the RF-exposed cable is only the short one to the radio. One more point about rigctld: use the right Hamlib model number for the rig (rigctl -l lists them) and match the serial speed and stop bits to the rig's menu setting. A surprising number of CAT problems turn out to be baud-rate or handshake mismatches rather than RF. Rule those out before reaching for more ferrites.
  8. One design point that gets overlooked is the failure mode. If the link drops mid-transmission, what stops the transmitter? A solid remote station assumes the network will fail eventually. Useful safeguards are a watchdog that drops PTT if the control session goes silent, a transmit timeout, and an amplifier that defaults to standby when power returns. Switched power with a separate out-of-band path, such as a cellular-linked relay or a second ISP, lets you recover without driving to the site. That also fits the rule that you must be able to shut the station down. Camera and temperature or SWR alerts are cheap compared with a damaged PA or antenna tuner. On the Icom and Yaesu side, I would treat the LAN port as a trusted-network feature and put a VPN in front of it. Using the radio's own server through a tunnel is generally a safer plan than opening a range of UDP ports, and it keeps CGNAT from being a dealbreaker.
  9. The pool structure is the best planning tool. It is split into ten subelements (T1 through T0), and those are divided into 35 groups. Each exam pulls one question from each group, so you can't skip a whole topic and hope it doesn't appear. Passing is 26 of 35 correct, which is about 74 percent. Confirm the details and the effective dates of the current pool with the volunteer examiner coordinator running your session, because pools are replaced on a multi-year cycle and you want the one in use on your test date. Study group by group instead of reading cover to cover. Each group has several questions but only one gets asked, so learn the concept behind the whole group instead of one question's wording. For example, the group on Ohm's law is not about one problem. Know E = I × R and P = I × E, and practice rearranging them. If a 12 volt supply feeds a 6 ohm load, you get 2 amps, and 24 watts follows from that. On practice tests, use ones that randomize answer order and draw one question per group like the real exam. Missed questions are where the learning is. Read the explanation, then restate the concept in your own words. If you keep missing the same group, go back to the study guide section for it instead of retaking the test. Many people aim for consistent scores in the high 80s or better on fresh randomized tests before scheduling, since that leaves room for nerves and odd wording. Spend extra time on the groups where a calculation or a relationship does the work: wavelength and frequency, Ohm's law, and the basics of how components behave. Those are easy points once the pattern clicks.
  10. Building on the point about forecasts: I think VOACAP is most valuable when you use it for comparing, not for a yes/no answer. Run the same path for a couple of bands and times, and see where the reliability and signal-to-noise estimates peak. It helps you find the window, like the hour around the gray line when 40 m or 80 m might do something unusual, and then you confirm with live monitoring. The output depends heavily on your inputs: antenna gain, power, required SNR for the mode, and the man-made noise setting. If those are unrealistic, the result will look much better or worse than your station will actually deliver. On the NVIS point, it's also worth pairing a band choice with the time of day. When the critical frequency drops at night, a frequency that worked at midday for regional contacts can go long and skip over the people you want to reach. Moving down from 40 m to 80 m, or from 60 m to 80 m, is the usual adjustment. A beacon or a regional net on a known frequency gives you a quick sanity check. For the "closed versus empty" question, I'd look at whether you can hear the noise floor change. A band with a lot of atmospheric noise but no signals is different from one where the receiver is quiet and flat. But honestly, the clearest test is to listen on a few known beacons or active frequencies in several directions before concluding anything.
  11. Adding the activator-side and VHF/UHF tools, since those work a bit differently. For POTA and SOTA, the spot pages are the main way hunters and chasers find activators, and activators can generally post their own spot with reference, frequency and mode. That's the big difference from a DX cluster. The activator usually wants to be found, so self-spotting is normal. Two practical points: spots only help if the frequency and mode are right, and after you QSY you should update or retract the spot. Otherwise hunters keep calling on an empty frequency. Also keep the reference formats straight. POTA uses park references like K-1234, while SOTA uses association/region-number summit references. On propagation, a few numbers explain most of what the tools show. Solar flux, the A-index and the K-index give a quick feel for HF conditions, and a high K-index usually means disturbed high-latitude paths. Prediction tools based on models like VOACAP give averages, not guarantees. I'd use them to choose a band to try first, then confirm with RBN or PSK Reporter what is actually being heard. Grid maps are worth a bookmark for VHF contests and for POTA or SOTA logs. A 4-character Maidenhead grid is a big square, and a 6-character one is much more precise. When you exchange grids, make sure you're sending the character count the contest or award expects. RepeaterBook is convenient for finding offsets, tones and modes. It depends on user and coordinator submissions, so a listing can be out of date or wrong. Before you program one into a radio, check the frequency, offset, CTCSS or DCS tone and any access restrictions, and listen first. For exam study, Hamstudy gives you question-pool practice with spaced repetition. Its value is in repeating the questions you miss, and you should read the explanation instead of just memorizing the answer. HamCalc is better as a bench reference for quick calculations than as something you leave open all the time.
  12. On the handhelds, a few points that are easy to miss. The TH-D74 and TH-D75 have a built-in TNC and GPS, and both can be used as a KISS TNC for other software. The FT5D also has APRS with GPS built in. Menu structure and defaults differ between these radios, so check each manual for the packet speed, the beacon path (digipeater path) field, and whether the radio is using standard position format or Mic-E. Mic-E is worth understanding. Instead of the longer plain-text position format, it puts latitude in the destination address field and packs longitude, speed and course into the information field. The result is a shorter packet, which suits mobile use. It also carries a standard status code (In Service, En Route, Off Duty, Emergency and so on) that you choose on the radio. Many decoders show that status next to the track. For messaging, the format is the : data type, followed by the addressee padded to nine characters, then the text, with an optional message number after a {. Text is limited to 67 characters. The receiving station sends an ack with the same number, and the sender retries until it gets one or gives up. If you send messages to a callsign-SSID, the SSID must match exactly. Messaging to someone far away works through APRS-IS only if they were recently heard on RF at an iGate, so delivery is not guaranteed. Objects use the ; type with a nine-character name and a live (*) or killed (_) flag. They are handy for marking an event, a repeater or a checkpoint, but they repeat on whatever schedule you set. Put a realistic interval on them and kill the object when you are done, otherwise it lingers on the map. Test with a short path and low power first, and use a callsign-SSID scheme you will remember, such as one SSID for the handheld, another for the car and another for the home iGate.
  13. On interference, I'd stress documenting before reacting. Whether it's a power-line buzz, a switching power supply, or a repeated intentional jammer, the useful first steps are different. For local noise, a battery-powered portable radio can help trace where it's strongest, and checking with the main breaker off at your own house tells you whether it's coming from inside. For intentional interference on a repeater or net, the usual guidance is not to acknowledge it on the air. The NCS or repeater owner can decide whether to change frequency, use a different mode, or pass the information to the repeater coordinator or regulator. Another point for newer operators on digital modes: be careful with transmit audio levels. Overdriving the audio on FT8, PSK or similar modes produces a splattery signal that creates interference well beyond your own frequency. A clean signal with a reasonable power level is both better manners and usually better results.
  14. For modeling, it helps to run a few sanity checks so you can trust the results. First, put a plain dipole at your planned height and compare the resonant frequency with what you measure later. Whatever offset appears is a correction factor you can apply to other models of the same site. Second, check the segmentation: very short segments next to a junction or a much longer one can cause average-gain-test warnings, and in MMANA-GAL the average gain test is a quick way to see whether the model is reasonable. Aim for an average gain close to 1 (0 dB) with a lossless setup. Also check how the program treats ground, since radial-heavy verticals and low horizontal wires depend on it. For a vertical, run the model with different radial counts or ground types to see how much the efficiency and takeoff angle change. That gives you a sense of whether extra radials are worth the work before you cut anything. And for ladder-line setups, model the antenna alone for pattern and impedance, then handle the feedline loss and tuner matching as a separate calculation, because the SWR on the line and the loss in the line depend on the cable type, length and frequency.
  15. Start with the split. The FCC rules (Part 97, mainly 97.301 for which frequencies each class can use and 97.305 for which emission types are allowed where) are law. The ARRL band plan is a voluntary agreement about how to share the space inside those limits. Nobody can be cited for running SSB in a spot the band plan reserves for narrow digital, but you'll be unpopular and probably get little out of it. Run a mode where the regulations forbid it, or transmit outside your class's frequencies, and that is a violation. The HF structure is the same on almost every band. CW and narrow data modes sit at the bottom, a mixed or wider-data region follows, and phone sits at the top. Licence classes then carve that up. Roughly, under current US rules: Technicians get CW-only privileges on parts of 80, 40 and 15 m, plus 10 m from 28.000 to 28.500 MHz, with CW/data in the lower part and SSB phone above 28.300, all at 200 W PEP on HF. Generals get all of 160, 30, 17, 12 and 10 m, and large portions of 80, 40, 20 and 15 m. Extras get everything, including the segments at the very bottom of the phone and CW sections that Generals can't use. Typical General phone starting points are 3.800 on 75 m, 7.175 on 40 m, 14.225 on 20 m, and 21.275 on 15 m. Those are worth memorizing because they are where many new Generals accidentally step out of privileges. 30 m (10.100 to 10.150) is CW/data only and limited to 200 W. 17 m and 12 m have no Extra-only sections, so they are the easiest to get right. Legacy Novice and Advanced licenses are no longer issued, but existing holders keep the privileges they had, so you will occasionally hear operators in segments that no current new license class uses. On band edges, remember that your dial frequency is not where your signal sits. In SSB with the suppressed carrier, the signal occupies roughly 2.5 to 3 kHz beside the dial frequency. On LSB (conventional below 10 MHz), the audio extends below the dial, so if you sit at 3.800 on LSB, part of your signal is below 3.800 and out of General phone privileges. Put the dial at around 3.803 or higher to be safe. On USB (conventional above 10 MHz), the signal extends upward, so at the top edge, say 14.350, you want your dial at around 14.347 or lower. Rule of thumb: keep the whole occupied bandwidth inside the edge, not just the dial readout, and leave a bit more margin if your radio's display is not well calibrated or you use a wide filter or a processor. A few segment hints on the HF digital side. FT8 is a convention, not a regulation, and it clusters around well-known dial frequencies (USB): about 1.840 on 160 m, 3.573 on 80 m, 7.074 on 40 m, 10.136 on 30 m, 14.074 on 20 m, 18.100 on 17 m, 21.074 on 15 m, 24.915 on 12 m and 28.074 on 10 m. These sit inside the digital portions of the band plan. Stay off 14.100 on 20 m (beacons) and look for the narrow-mode areas before running anything that stays on the air for a long time. On 160 m, CW/digital tends to be at the bottom and phone starts around 1.843 and up, but check the current band plan for the DX window details.
  16. I like the point about using actual spots over forecasts. A flux number is more useful if you know how your own station works. A modest wire antenna on 15 meters might hear Europe fine when the beacons are strong, while someone with a better antenna may still be hearing nothing from the same path. Beacons are handy because everyone is hearing the same known signal, so you can compare your station honestly. For summer, I'd add that sporadic E can open 6 and 10 meters (and sometimes 2 meters) with little warning, and it doesn't track the solar cycle the way F2 propagation does. It's one reason to keep a spotting page open even when the flux looks mediocre. As for club news, a monthly meeting or a net is often where you hear about a repeater going down, a new award program, or a local special event station. Those items rarely make national headlines. I'd also say that if a club newsletter is posting a date, location or frequency, double-check it against the club's own page or the event organizer before driving anywhere.
  17. Agree on measuring supply voltage at the rig under TX load. A lot of "no transmit" or "resets on SSB peaks" complaints come down to voltage drop in the DC lead, a tired fuse holder or a supply that can't hold up on peaks. A scope on the supply rail while keying will show it straight away. On capacitors, I'd measure before replacing. An ESR meter or a scope looking at ripple on the rail tells you which ones are actually bad. Replacing everything on a hunch can introduce new problems, like a reversed polarity cap, a damaged pad or a wrong-value part in a timing or filter circuit. Targeted replacement of the ones that fail the test is usually safer, and you keep a record of what changed.
  18. Adding to the above, here is how I'd split the study time. Electrical principles and circuits scare people more than they should. The General pool uses fairly light math: Ohm's law, power calculations, the relationship between peak, RMS and PEP, and a bit of reactance, impedance and resonance. If you can rearrange E = I × R and P = E × I, you can handle most of it. The component and circuit questions (filters, amplifiers, mixers, oscillators, what a diode or transistor does) are mostly identification. A block diagram of a superhet receiver and a simple SSB transmitter is worth drawing once. Antennas are practical. Know that a half-wave dipole's length in feet is roughly 468 divided by the frequency in MHz, that a quarter-wave vertical relies on its radial system, what SWR does and does not tell you, and why feed line loss grows with frequency. Know the basic idea of a trap antenna, a loop, and a Yagi's gain and front-to-back ratio. Don't confuse high SWR with 'the antenna is radiating poorly.' The pool likes that distinction. Digital modes: expect questions on the difference between modes like RTTY, PSK31, FT8 and Winlink-style systems, what bandwidth and baud rate mean, and how to avoid overdriving your audio (watch ALC, keep audio levels low). Sound-card interfaces and USB-D or data mode settings are common practical topics. The popular FT8 and PSK31 watering holes on each band are good to know for real operation, but they aren't things to memorize for the test. Operating practices: know sideband convention (LSB below 10 MHz, USB above, with 60 meters being a USB special case), station identification timing, third-party traffic rules, and how to behave on a net or in a pileup. Learn the RF exposure and station safety material too, since it's quick points. A workable schedule for someone with a full-time job is three to four weeks. In week one, take a practice test cold to find your weak subelements. Then spend two weeks working the weak groups, reading the explanation behind each wrong answer rather than just memorizing it. In the last week, take timed full practice exams and aim for comfortably above passing, say 85 or higher, before you book the session. After you pass, the VEC reports your upgrade and it appears in the FCC's ULS database. Keep your Certificate of Successful Completion of Examination (CSCE) as proof until that happens. Check the current Part 97 rules on when you may operate with the new privileges and whether any on-air announcement is still required, since procedures have changed over time. Vanity calls are optional. You can keep your current call indefinitely, and a General is eligible for certain call sign groups. Apply through ULS and check the current fee on the FCC's site. Plenty of people upgrade and never change their call.
  19. On the Smith chart, I'd drop the idea that it's mysterious. Start with a few facts and a single worked example. The center of the chart is a perfect match, which is a normalized impedance of 1 + j0. Take a 50 ohm line with a 100 ohm resistive load. Normalized, that's 2. The reflection coefficient is (100 - 50) / (100 + 50) = 0.333, and SWR = (1 + 0.333) / (1 - 0.333) = 2:1. On the chart, a constant-SWR circle is centered on the middle and passes through that point on the real axis. Moving along a transmission line follows that circle. Moving toward the generator is clockwise, and one full revolution is a half wavelength. That last fact explains why a half-wave line repeats the load impedance. Most of the pool's chart questions only ask you to read a point, name its position, or identify what the chart is used for. They rarely ask for heavy plotting. Practice reading resistance and reactance from the circles and learn where open, short and matched conditions sit, then check yourself against the pool. For the antenna questions, keep the reference points straight. A gain figure in dBi is relative to an isotropic radiator, and dBd is relative to a dipole. A dipole is about 2.15 dB above isotropic, so dBi = dBd + 2.15. Many wrong answers come from mixing those two references or forgetting that ERP is calculated from the power at the antenna and the gain relative to a dipole, minus feed line loss. As for the privileges, the Extra-only segments are the visible payoff, but full access to all bands and modes is the real point. Confirm the exact current band-segment table from the FCC rules or the ARRL band chart when you're ready to operate there.
  20. A useful way to decide is to split tools into "what is happening now" and "what is true about this station." Spotting tools like a DX cluster, RBN, and the POTA or SOTA spot pages are for now. Callbook lookups are for "true," and even those can be out of date. For alerts, a service like HamAlert can notify you when a callsign, DXCC entity, or park matches your criteria, so you do not have to watch a spot list continuously. If you set up filters, keep them narrow. A broad filter on a busy band produces the same flood you were trying to escape. One caution on skimmer-sourced spots: a good SNR on RBN means the skimmer heard the station well, not that you will. Your local noise floor and antenna decide that, so use the spot as a prompt to listen, not a promise of a contact.
  21. On modeling, the biggest mistake is usually trusting the numbers beyond what the inputs support. A few things to check: first, run the model with the antenna in free space and compare it with the textbook value (about 73 ohms for a thin half-wave dipole), which verifies your segmentation. Second, vary the height above ground in steps, because the feedpoint impedance of a low horizontal dipole swings noticeably with height. Third, for an inverted-V, change the apex angle and see how the impedance and resonance move, since that tells you which way to trim in the field. For wire loss, make sure the model's conductor material and diameter match what you actually bought. For traps, EZNEC lets you include L and C loads, but the loss and Q of a real trap is hard to represent without measuring it. If you build a trap, the best approach is to measure the trap alone on the VNA with a small link, find its resonant frequency, then use those figures in the model. On supports, a catenary sag in a long span is not a failure of the build. The thing to avoid is a sag so slight that the tension is very high, because that is what breaks wire and insulators in wind and ice. A slight droop in the span, with the ends allowed to move, tends to last longer.
  22. I'd keep one master log and export from it, rather than splitting logs by program. The programs want different things from the same QSO. POTA expects an ADIF file uploaded to its own system, with the park reference in the right field. SOTA works through its own database, with a summit reference and its own rules for what counts as a valid activation. Neither of those feeds DXCC, so a QSO can be good for several programs at once but still needs to be exported and submitted separately for each. If you work from a park or summit, run the DX-award logging with the correct station location and keep the references in the log. CQ DX Marathon is different again. It runs on the calendar year, so each year starts from zero and the score is built from entities and CQ zones worked that year. It rewards steady operating more than a one-off big contact, and it is a decent way to track zones you still need for WAZ. For Challenge, I'd say work the slots you can actually reach. Band-entity credits need propagation to the right place on the right band, and some will only come through a DXpedition. A sensible approach is to build a want list by band, watch spots and cluster activity for those entries, and keep a note of which confirmations are still unmatched. For IOTA and for paper QSL submissions, read the sponsor's current rules on what confirmation they accept before you spend money on cards or postage.
  23. On the plateau: it is usually a recognition problem, not a speed problem. If you can copy 12 WPM at 95 percent on a good day but make mistakes at 14, check how you are listening. Are you still counting elements, or waiting for a character to finish before you decide what it was? If so, the fix is to practice a bit faster than your comfort level, with slightly longer gaps. Run at about 18 to 20 WPM character speed and set the effective speed to whatever you can handle. Then close the gap over weeks. Short sessions, 15 to 30 minutes every day, usually beat a single long weekend session because recognition builds with repeated brief exposure. If a session ends with you guessing, stop. Extended sloppy copy tends to reinforce bad habits. For drills, split the time instead of doing one thing. A reasonable weekly mix is some new-character or random-group work, some real words and common CW abbreviations, and a callsign drill. Callsigns are good practice because the letters and numbers come in random order, and you have to get them exactly right. Tools like RufzXP, which raises the speed as you succeed, are designed for this. Do not skip numbers and the punctuation used in exchanges (the slash, the question mark, and a few prosigns). They cause trouble later if you only practice letters. On head copy, try this progression. Copy everything on paper. Then copy words but only write down the first and last letters. Then listen to whole words and write nothing but callsigns, names, and numbers. If you drop a word, let it go and keep listening for the next one. Dwelling on the missed word means you lose the next three. That habit, letting go, is probably the hardest part of getting past 15 WPM.
  24. To add the planning side, a sked is mostly about overlap. Both stations need the Moon above a usable elevation at the same time, so use WSJT-X's Astronomical Data window or a tracking program to see azimuth, elevation, Doppler and sky-noise degradation for your own location and your partner's. The best windows usually have low sky temperature (away from the galactic plane and the Sun), the Moon near perigee, and a comfortable elevation for both stations. Agree the mode and submode, the frequency, which station transmits in the first period, polarization or circular sense, and how long you will keep trying. Also agree a fallback if one of you has a failure. Moon tracking can be low-tech on 2 m and 70 cm, since a wide beam forgives errors of a degree or so. On 10 GHz with a 3 m dish it is not forgiving, so a calibrated tracking setup, regular checks with sun noise, and mechanical stiffness matter more than raw power. Keep a log of your own echoes when you have them, since a drop in echo strength is the quickest warning of a failing preamp, relay or connector.
  25. On the Field Day side, the dupe sheet question is mostly about networking and clock sync. If you have multiple stations, use a shared logging database or a networked logging program, and set every computer's clock correctly before starting. Otherwise, merged logs will show confusing time stamps and can create dupes that were not real. Decide in advance who is responsible for the final merge and for submitting. Don't wait until Sunday evening to find out the logger on the GOTA station used a different callsign setting. One more point on exchanges: Field Day and Winter Field Day look alike, but the classes and bonus structures are not the same, so read each year's rules rather than assuming they carry over. The same goes for the power multiplier and whether things like emergency power, public information tables, or alternate classes apply. When in doubt, the sponsor's current rules and the latest summary page are the authority, not a forum post or last year's notes.

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.