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_Terry

Administrators
  • Joined

  • Last visited

Everything posted by Admin_Terry

  1. I'd push back slightly on making the general logger the master for everything. It depends on what you care about. If your main goal is awards and confirmations, then yes, a master log in Log4OM, DXKeeper or similar is where it all ends up. But if you contest seriously, the N1MM+ database is the record of the contest and it should be archived as is, with the original .s3db file or equivalent, plus the exported ADIF and the submitted Cabrillo. If a sponsor asks a question or a robot reports a mismatch, you want the exact data you submitted. For uploads, the cleanest approach is probably to let the master log handle LoTW, QRZ and Club Log, and have N1MM+ do none of them. With LoTW especially, check the TQSL station location before the first batch from a contest. Operating from a different grid, a club station or a portable location needs its own location entry. If those QSOs get signed against your home location, they usually just don't match, and it's annoying to fix later. For FT8/FT4, the UDP route into the master log is good, but watch the time. If the PC clock is off, you'll see it in decodes first and in your ADIF timestamps second. Logging in UTC with a synced clock is what makes the confirmations match up on the other end.
  2. On antennas, I'd split the choice by how you plan to operate. If you'll be at a picnic table or in a park, a linked dipole or an inverted-V on a lightweight mast is hard to beat, because it's resonant, simple, and you can see exactly what the SWR is doing. If you're trying to climb and be set up in minutes, an end-fed half-wave on a fishing pole is quicker, but it's more sensitive to counterpoise length and how the coax is dressed. A few minutes with an antenna analyzer at home will save a lot of frustration in the field. A small point on the 5 W figure: when you're calling CQ on a QRP frequency, patience matters more than anything. Many successful QRP contacts happen because the other station is also listening carefully, not because of any clever trick. Keep your exchange short and clean, repeat your callsign clearly, and slow your CW down if the band is noisy.
  3. SWR is mostly a feedline and tuner question; efficiency is a separate question, and the two get conflated constantly. Coax loss is the bridge between them. Loss per 100 ft rises with frequency, and roughly speaking RG-58 loses a few times as much as RG-213 or LMR-400 on the same run at 14 MHz. When the SWR is high, the reflected power makes the line carry extra current, so the loss goes up, sometimes by several dB on a thin cable at 10 m. A 200 ft run of thin coax into a mismatched wire can quietly eat a large part of your power. That is the main argument for a doublet fed with ladder line. A tuner at the shack end matches whatever impedance arrives, and the line loss stays small even when the SWR on the line is 6:1 or higher. If you want to avoid a tuner, the EFHW or OCFD trade a little simplicity for fixed-ratio transformers that are good on their design bands and mediocre elsewhere. For any of the transformer designs, the choke matters more than people expect. If common-mode current flows on the coax shield, the coax radiates, you pick up household noise, and the SWR readings change when you move the cable. A rough test is to touch the coax or move it and see whether the SWR reading shifts. A choke of 10 or so turns of coax on a mix 31 core (or a stack of clamp-on beads) is a typical starting point, but check the manufacturer's data for the band you care about, since 80 m and 10 m behave differently.
  4. On the buying side, I'd add a rule about priorities: test what you can, and price what you can't. A transceiver you can power up and check for receive audio, a working display, and a keying response is worth more than the same model "untested." For anything that's untested, assume it needs repair and offer accordingly. A few practical items: bring an SWR meter or antenna analyzer if you want to check an old tuner or coax, bring spare fuses, and look at connectors (PL-259s and SO-239s, BNCs, Anderson Powerpoles) because mismatched or damaged ones are common in used-gear boxes. Cables and adapters are great bargains, but only if the ends are solid. For handhelds, check the battery pack condition, since replacement packs can cost a lot, and ask whether the charger is included. For anything with a microphone or a proprietary cable, make sure it's actually in the box. It's easy to discover at home that the one missing cable is the expensive part. Finally, take a few minutes to walk the whole flea market before buying. You'll see the going price on common items, and you won't spend your budget in the first row.
  5. For operating tips, the practical points are mostly about being easy to copy. Give the reference clearly and don't rush it. On SSB, something like "CQ World Wide Flora and Fauna, CQ WWFF" followed by your callsign and the reference, phonetically, is much easier to work than a fast, clipped call. Some hunters are chasing the reference, others just the contact, so repeat the reference periodically. On CW, send it a few times per CQ sequence, not only at the start. If you're working POTA hunters at the same time, say both programs in your CQ so nobody is confused about what you're calling. It's also worth thinking about band conditions before you pick the spot. If you need 44 QSOs and only have a short window, it's better to pick the band you expect to be open and have an antenna that works well there than to start with the one you like most. Digital modes can add contacts, but don't plan on them alone unless you know hunters are available on that mode. Finally, check the park's own rules, including quiet hours, access limits, and restrictions on antenna supports or on setting up away from designated areas. A great reference is no use if you've set up somewhere you shouldn't be.
  6. On the family side, it helps to keep things as simple as possible for the non-ham members. A pair of FRS/GMRS radios with fresh batteries, one preset channel, and a laminated card with three lines of instructions (turn on, press and hold to talk, release to listen) is more useful than a fancy radio nobody understands. If you go the GMRS route, get the license sorted out and know which channels are shared with FRS and what their power limits are. It's also worth thinking about how often you check in. Scheduled windows, like a few minutes at the top of the hour, save batteries and avoid the problem of everyone listening and nobody transmitting. Write the schedule on the same card as the instructions. For the grab bag itself, a small waterproof pouch for the paper items (channel list, contact numbers, a copy of your license, a pencil rather than a pen) is a cheap upgrade. Pencils still write when wet or cold.
  7. On the formal-versus-plain question, it helps to treat the format as a tool for the path rather than a rule for its own sake. If a message is going to cross several relays, or sit in a queue before delivery, the radiogram structure protects it: the check catches dropped words, and the numbering lets people refer to it unambiguously. If it is a short request inside a single shelter-to-EOC link, a clean ICS 213 read out in plain language with a readback is often faster and less error-prone. What I'd drill is the readback habit regardless of format. Names, numbers, street addresses and quantities should be repeated back, and phonetics should be used for anything that could be misheard. Plain language also means avoiding Q-signals and ham shorthand when talking to non-hams on the other end. A good exercise injects a deliberately messy message, such as one with a long street name, a medication list or a count of cots, and sees how many stations get it right the first time.
  8. SO2R can make the run-or-pounce question easier, because the second radio becomes your search tool while the first keeps running. The main skill is listening. You can't search effectively on radio 2 if you're half-listening to radio 1. Many operators use headphones with stereo split, so radio 1 is in one ear and radio 2 in the other, and learn to focus on one at a time. The hardware matters too. An SO2R box or controller that handles transmit inhibit, headphone switching and PTT interlock prevents you from keying both radios into the wrong antenna. Interference between the two radios is the next hurdle. If both are on nearby bands, front-end overload and harmonic or noise problems from the other transmitter can wreck the receive side. Band-pass filters, stubs and physical antenna separation all help, and so does picking band pairs that interfere less. It often makes sense to put your best antenna on the radio that's running and use something smaller on the search radio, though that depends on what you have. Antennas decide a lot of this. Stacked Yagis let you choose a takeoff angle for the opening, and on 160 and 80 the receiving antenna can matter as much as the transmitting one, because a Beverage or small loop lets you hear stations you'd otherwise miss. If you can't hear well, S&P won't work no matter how clever your logging software is. For fatigue, plan your off-times before the contest starts rather than deciding when you're tired. The best time to rest is when rate is low on your best bands, and that depends on propagation. Late-night hours on a higher band may produce almost nothing anyway, so you lose little by sleeping then. Poor decisions, missed callsigns and slower exchanges are the early signs that you've been at it too long, and they cost you more QSOs than a planned break would.
  9. The split you describe is sensible, and the biggest risk is the merge step. I'd back up the master log before importing contest ADIF, and import only after checking a sample. Some loggers treat an incoming record as a duplicate if call, band, mode and time are close, while others just import everything. If you're unsure how your logger behaves, run the import into a test database first. Also decide in advance whether contest QSOs should be uploaded from N1MM or only from the master log. Uploading the same QSOs from both places can create duplicate entries on QRZ or Club Log. On CAT, the right choice depends on the radio. If the radio's CAT is serial over USB, a single program owning the port is simplest, with the others reading through a Hamlib or flrig layer. For rotators, N1MM can control one directly, but if the same controller also serves another program, use a shared interface rather than letting two programs fight over the port. One more item for the plan: keep the ADIF export from the contest log untouched. If the master log import goes wrong, you can redo it without regenerating anything.
  10. For a brand-new ham, I'd start by showing up to a local ARES or RACES meeting and asking what the group's actual commitments are. The free FEMA courses are worth doing no matter what, since IS-100 and IS-700 take little time and teach the vocabulary people will be using. But the local group can tell you which served agencies it supports, whether it needs a background check or agency credential, and what its net schedule looks like. That keeps you from collecting certificates that do not match what your county expects. On the ARES versus RACES paperwork question, I'd keep the distinction clear in every document: who can activate you, under whose authority you operate, and what frequencies and modes are in the plan. The rules for drills and operating authority under Part 97 are not something to guess at, so read the current text and ask your emergency management contact how they interpret it locally.
  11. On Q65 versus JT65, the safest way to answer is to check what the stations you want to work are running, because a better mode does you no good if nobody is using it. Q65 was designed for paths with spread and fading, and the submode choice should reflect your band. If the echo is wide because of libration, a narrower submode will smear and lose sensitivity, so test with your own echoes or use whatever the active stations agree on. On the single Yagi question, it can work, mostly with big stations and in good conditions, but you should expect many failed attempts, because many things have to line up: moon distance, low sky noise, favorable polarization, and a station at the other end with plenty of gain and power. Hearing your own echo is a useful benchmark, and WSJT-X's Echo mode helps with that. If you can't see one, you probably can't expect much from a QSO either. For microwaves, the point that gets underestimated is tracking. A dish with a beamwidth under one degree needs pointing that is a fraction of that, and calibration is worth doing on the sun and then the moon. Refraction near the horizon, mechanical backlash, and wind loading all show up as signal loss. The other big item is frequency stability, since a small drift in the oscillator is a huge error at 10 GHz.
  12. On the check-in point, I'd add that it helps to treat a net's published script as part of the schedule. Some nets are open and just want a callsign. Some want a name and location. Others ask whether you have traffic or are mobile, and a few want a signal report. If you don't know the format, check the net's website or ask the NCS at the end, instead of guessing in the middle of a roll call. For SKYWANN-style nets and ARES nets in particular, the biggest etiquette rule is to stay off the frequency unless you have something useful or are asked to speak. A callsign alone is often enough. Those nets exist for a purpose, and it's easy for casual chatter to get in the way when activity picks up. For special event stations, keep your exchange short when there's a pileup. A callsign, a signal report, and a thank-you is often all they need. Save longer conversation for stations that clearly have time for it.
  13. Adding to that, with a focus on names, numbers and nets. For names and places, spell only the part that is likely to be misheard, and announce it: "The name is Moira, I spell: Mike Oscar India Romeo Alfa." For a place, give the whole word first, then spell the unusual portion. If it's a long location, break it into chunks and pause between them so the listener can write. When copying, repeat it back and let the other station confirm. This matters more than which phonetic words you use. For numbers, the common voice convention is to say each digit separately, with "zero" instead of "oh" in callsigns and messages, and "niner" for nine if there is any chance of confusion with the German "nein" or with five. Aviation uses "tree," "fower," "fife" and "niner," but in ham radio most people just say the numbers normally unless conditions are poor. The ITU also defines a special set of number words (Nadazero, Unaone, Bissotwo and so on) but they are essentially never used on amateur bands, so you can skip them in a guide. For a callsign with a slash, "stroke" or "slash" works, and "portable" or "mobile" can be used for the suffix when appropriate. Prosigns are different on CW and voice. On CW, prosigns like AR (end of message), SK (end of contact), BT (break), KN (go ahead, specific station) and AS (wait) are sent as run-together characters. On voice you use procedure words instead: "over," "go ahead," "say again," "standing by," "clear" or "out." Avoid saying "over and out" because they contradict each other, as "over" invites a reply and "out" ends the exchange. Many hams just skip "over" on a repeater with a clear turnaround, but on HF with a weak path it can be useful. On nets, the net control station (NCS) sets the procedure and you follow it. Many nets ask for check-ins using just the suffix of the callsign, said phonetically, for example "Kilo Echo Tango." NCS then calls back with the full callsign. Wait to be called, give your callsign once, and don't hold the frequency for conversation. Emergency and priority traffic is typically signalled with words such as "emergency" or "priority" and often "break" to interrupt, depending on the net's rules. Communication in organized emergency work usually favors plain language rather than 10-codes or slang, because served agencies and operators may not share the same code meanings. For message traffic, read digits slowly and separately, spell anything unusual, and ask for a readback of critical items such as addresses, names, quantities and times. Follow your local group's or served agency's written procedures where they exist, as those take priority over general advice.
  14. For me the dividing line is whether a radio invites you to turn it on. Specs matter less than whether you actually reach for it. A rig with a good receiver but fiddly controls can sit idle, while a simpler one with a nice tuning knob and a clear filter control gets used every week. On the vintage side, the keepers tend to be gear with good documentation and a big user community. Popular classic transceivers from Collins, Drake, Heathkit, Kenwood and Yaesu have schematics, manuals and known failure points that are well covered. That support matters more than the brand name when something eventually breaks. One caution for anyone buying an older tube or early solid-state rig: don't assume it's fine just because it powers up. Aging electrolytic capacitors in the power supply are a common trouble spot, and checking or replacing them before extended use is generally a good idea. It's much cheaper than finding out the hard way.
  15. On the 'antenna system first' question, I'd put the antenna and feedline ahead of any radio upgrade. A rig with a better dynamic range figure can't recover signal you never captured, and a 100 W radio into a poor antenna is a 100 W heater for the coax. That said, the order of spending does depend on what is actually limiting the station. If the noise floor is high and you can't hear weak signals, the fix may be locating or filtering the local noise source, not buying a new receiver. A point about the tuner: it's worth separating 'the radio is happy' from 'the system is efficient'. An ATU that shows 1:1 at the rig can be hiding a very high SWR on the line. With a short run of good coax on a moderate mismatch, the extra loss is small. On a high-SWR multiband wire with long thin coax, it can become significant. Open-wire or ladder line with a balanced tuner is often better for that kind of antenna, and the choke at the transition matters.
  16. For a first pass, the best weight savings usually come from the support gear, not the radio. A 10 m pole is often the heaviest single item, and a lot of operators carry more pole than the wire needs. An inverted-V EFHW needs the feedpoint high and the far end can slope down to a stake or a tree branch, so you don't always need the full height. For the EFHW, a short coax feed with a choke at the rig end is worth the few grams. If SWR is fine on the bench but shifts when you touch the coax or move the radio, common-mode current is the usual suspect. Trim the wire for the band you care about most and re-check after each setup. Wire height, ground type and how the end is routed can all move the resonance. On the power side, many people size the battery to the mode. CW or SSB at 5 to 10 W is very forgiving. FT8 or other digital modes at a steady duty cycle will drain a small pack faster than you'd guess, because the transmit time adds up. Write down your actual consumption once so you aren't guessing at the trailhead.
  17. One thing to add is that if the goal is a fixed station for repeater access, work out the path first and the antenna second. If the repeater is within line-of-sight and decently strong, a plain vertical is usually enough, and the coax and connector quality will have more effect than 2 dB of extra antenna gain. If the repeater is marginal, a small vertically polarized yagi aimed at it can turn a noisy signal into a quiet one, and it will often reduce interference from other directions too. The tradeoff is that you have to aim it, and if the repeater's coverage is wide and you only occasionally use another one, you may regret the narrower beam. On J-poles specifically: the feedline question is the one most builds skip. If the pattern looks lopsided or the SWR shifts when you touch or move the coax, the shield is probably carrying current. A choke near the feedpoint is cheap to add and easy to test.
  18. Picking up the rest. Section numbers are in parentheses so you can check them. RF exposure (97.13(c) and the FCC's general exposure rules in Part 1): you are responsible for exposure limits around your station. If your power and band are above the thresholds in the FCC's table, you must do a routine evaluation. Below the thresholds you are categorically excluded from that step, but the limits still apply. Evaluation methods include the FCC's OET Bulletin 65 Supplement B, antenna modeling, calculators, and measurement. Mode matters because the limits are time-averaged (6 minutes for controlled exposure, 30 for uncontrolled). SSB and CW have a much lower average power than a full-carrier digital mode, so use a realistic duty cycle. Keep the antenna as far from people as practical. Many problems come from antennas near neighbors, rooftop installs, and loop or vertical antennas near living space. Spurious emissions (97.307): for HF, the mean power of any spurious emission must be at least 43 dB below the fundamental and not exceed 50 mW. For 30-225 MHz, above 25 W the requirement is 60 dB down. Spurious emissions must also not cause harmful interference, and good engineering practice (97.307(a)) applies throughout. Overdriving a linear amp is the usual culprit: splatter, harmonics, and a dirty signal. A properly sized low-pass filter and correct drive level go a long way. The certification rules for amplifiers (97.315) matter if you sell or build amps, so check them before building more than one unit of a model. License classes: Technician has all amateur privileges above 50 MHz plus limited HF segments (CW on 80, 40 and 15 m, and CW/data/phone on parts of 10 m). General adds large parts of all the HF bands. Amateur Extra has all privileges. Novice and Advanced are no longer issued, but existing licenses can be renewed. You can only transmit where your class allows, so a control operator must hold privileges that cover that frequency and mode. Control operation (97.109): local control means someone is at the transmitter. Remote control means a control operator is at a control point connected to the station, which must have a way to shut down if the link fails (97.213 uses a three-minute limit for control-link failure). Automatic control, where nobody is at a control point, is limited to specific station types such as repeaters, beacons, auxiliary links and certain digital stations, and in some cases to specific segments. Auxiliary stations (97.201) are link stations for repeaters or remote-control and are limited to certain bands, mostly 2 m and up with some portions excluded. A repeater still needs an accountable licensee and a valid control operator. Enforcement: the FCC Enforcement Bureau can issue a Notice of Violation, and for serious or repeated problems, a Notice of Apparent Liability for a monetary forfeiture, or revocation proceedings. Volunteer programs such as the ARRL's Volunteer Monitor can document issues but they do not have enforcement authority. Real-world cases are typically deliberate interference, unlicensed operation, or ignoring warnings. Term and renewal (97.21, 97.25): licenses are valid for 10 years. You can renew up to 90 days before expiration through the FCC's ULS, with no new exam. After expiration there is a 2-year grace period in which you can still renew without retesting, but you can't transmit until the renewal is granted. After that you'd have to re-qualify. You need an FRN in CORES, and your ULS record must carry a valid mailing address and email address (97.23), so keep them current or you could miss an FCC letter.
  19. Good breakdown. I'd add that the order of operations matters. Before buying a TCXO or filter, measure what you have. A cheap SDR dongle with a known reference or a frequency counter will tell you if the radio is actually off frequency. A dummy load, wattmeter, and a second receiver will tell you a lot about power, deviation, and spurs. A lot of "upgrades" are solving a problem the radio never had. On noise, I'd put it ahead of almost every internal mod. If the S-meter is sitting at S5 from a bad wall-wart or LED driver, a new filter will not fix it. Walk the house with a battery AM radio, unplug things one at a time, and watch what changes. Then look at ferrites and grounding. It's cheap and usually gives the biggest improvement. One caution on fans: if the noise floor rises when you power one up, it's the fan or its supply. Try a different fan, a separate filtered feed, or a small choke on the leads before blaming the radio.
  20. One thing I'd add for newcomers: before buying anything beyond a first handheld, spend a week just listening. Scan the local repeaters, tune around a scanner-style band plan, and see what's actually active in your area. That tells you more about what you'll use than any "best beginner radio" list. Also, whatever radio you choose, learn how to program it by hand at least once, even if you plan to use software later. Knowing what frequency, offset, tone, and power setting you've entered makes troubleshooting a lot easier. If you can't get into a repeater, the usual suspects are a wrong offset, a missing or incorrect tone, low power or a poor antenna location, or simply being out of range. Ask someone nearby to do a radio check. A short "Can anyone give me a signal report?" is a perfectly normal request. And please bring your questions to a club meeting. Many clubs enjoy helping newcomers, and a ten-minute look at your antenna setup can save weeks of frustration.
  21. I'd add something for people who want to try contesting without the full commitment. Field Day, Winter Field Day and the QSO parties are the friendliest entry points because there's a built-in social element: clubs, portable setups, generators, and so on. Just remember that Winter Field Day and ARRL Field Day are different events with different sponsors, so read each rule set rather than relying on what you know about the other. SOTA fits in differently. It has its own system for activators and chasers, with summit references and a database for logs, rather than a contest-style Cabrillo submission. If you plan a summit activation on a contest weekend, think about whether you want to work contest stations from the summit or run a normal SOTA setup. Those two goals can compete for time and battery power, and contest-level pileups on a portable QRP station can be a handful. For VHF, don't overlook how much the grid-square exchange depends on knowing your locator accurately. Verify your grid before the event and write it somewhere visible. Quick tip: if you plan to operate from a hilltop or park, check the grid there rather than assuming it matches your home grid. Finally, treat any "upcoming events" list as provisional until you've cross-checked the sponsor's own page. Schedules and rule tweaks do change, and the official rules always win over a forum summary like the one above.
  22. I'd push back a little on starting callsign drills before word drills, or at least on treating it as an either/or. Callsigns are a closed, high-value set of patterns, and they're the part of a QSO where you can't guess from context. Missing a letter in a word is forgiving, but missing one in a callsign means you can't reply. So even at modest speeds, a short daily callsign block is worth it. Word and text practice can fill the rest of the session. On decoders: a reasonable middle ground is to copy first, by ear, and only then check with software if you want to verify. Doing it in that order keeps your ear in charge. If you glance at the screen mid-copy, you'll start waiting for it to confirm each character, and that dependence is hard to break. Also keep in mind that decoders tend to struggle with fists that have uneven timing, so a garbled screen doesn't necessarily mean you missed anything. It may just mean the software can't handle that sender. For nets and QSO practice, slow nets are a good place to rehearse the standard exchange when nerves are the main obstacle. Having the structure memorized frees up attention to copy the one or two items that actually change, such as name and location.
  23. On firmware, the habit I'd recommend is to treat it like any other station change. Read the release notes, save your configuration, and if the radio is part of a contest or net setup, don't update the night before. Check whether the manufacturer provides a way to revert to the previous version, because not all radios do. Also check whether your logging software, rig-control program or digital-mode setup depends on specific CAT behavior, since some updates change command responses or audio routing options. For FCC and ARRL news, go to the primary source when you can. For FCC items, that means the actual docket or public notice, not a paraphrase of it. For ARRL, it means the official bulletin, board minutes, or website article. Forum summaries often mix what was proposed with what was adopted, and those are very different things. As for Hamvention and other conventions, the best coverage often comes from forum and club posts that describe what was actually on the floor: which products were available to touch, which were only displays, and which forums or talks had useful content. Still, confirm schedules and venue details on the official site before you plan travel.
  24. On the handhelds, treat the built-in TNC as a convenience and not as a replacement for planning your path. On a TH-D74 or TH-D75 the APRS settings (beacon type, interval, path, comment, status text) are separate from the voice settings, so it's easy to leave a default path on that's far too aggressive for a dense area. Check what the radio is actually sending, not just what the menu implies. A Mic-E packet decoded on aprs.fi or on another radio's display will show the path, so you can verify it. For SmartBeaconing, tune it to how you move. A car can use a fast speed in the highway range with a rate of a minute or two, and a slow rate of 10 to 30 minutes when stopped. Walking at 3 to 5 km/h will probably never reach those thresholds, so the radio stays on the slow rate and you lose track detail. Lowering the speed thresholds, or using a fixed interval of a few minutes for hiking, gives a cleaner track. Also be careful with corner pegging. A small minimum turn angle or short turn time on a twisty road produces a lot of packets that add little. On the FT5D side, check the manual for its APRS beacon and data-band behavior. It matters which band is set to transmit data and whether the radio will still receive voice on the other band while beaconing, since that differs between radio models and can surprise you in a car.
  25. A few notes on the pieces you asked about, plus a way to check your materials. Repeaters and operating practices: learn the vocabulary as a set. Input and output frequencies, offset (the difference between the two), CTCSS or "PL" tone (a subaudible tone your radio sends so the repeater will open), and simplex (talking directly, with no repeater). A common point of confusion is that the offset direction (plus or minus) depends on the band and on local convention. On the exam you'll mostly be asked what the terms mean and what typical offsets are on 2 meters and 70 cm. In real life, check your local repeater directory for the exact settings. Station identification and good practice are also testable. Know when you must give your call sign and what it takes to be a legal control operator, and know the basics of courtesy, such as listening before transmitting and keeping calls on a repeater short. RF exposure and safety: it helps to understand what drives exposure. Power, frequency, how long you transmit (duty cycle), and how close people are to the antenna all matter. The questions generally ask which factors affect exposure and when an evaluation is needed, not for complicated calculations. For general safety, think about commonsense hazards like working near power lines, using a safe ladder, grounding and bonding, and staying off the roof when there's lightning. Checking that your materials are current: look at the question pool published by the volunteer examiner coordinator organization (the NCVEC maintains it), and note the validity dates printed on the pool. Then compare them against the edition named on your study guide or practice-test site. If a site doesn't say which pool it uses, find another one. You can also ask the VE team running your session which pool they're using, since they'll certainly know.

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.