Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

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

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

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

Mod_Nancy

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Nancy

  1. For anyone new to this, I'd start with one contest that has a simple exchange before you take on Sweepstakes. CQ WPX is simple, because it's just a report and a serial number, and the logging software handles the counting. Field Day also works well for practicing contest-style operating, because the exchange is short and nobody minds if you are slow. One practical tip is to configure the software for the exact contest before the start. Set your call, zone or section, and the exchange fields, then test the function keys with the radio off the air or into a dummy load. Many bad logs come from setup errors, not operating errors. If a contest asks for a zone, such as CQ WW or IARU, double check that you're using the right kind (CQ zone vs ITU zone), since those aren't the same.
  2. The cold checks are the best part of the list, and I'd add toroids to them. Many kit problems come down to winding. With a toroid, each pass of wire through the center counts as one turn, not each time the wire goes over the outside. Enamel also needs to be properly removed at the ends before soldering. A joint that looks shiny may not be making a connection through the insulation. Scraping, or using a hot iron with a little extra time on a pre-tinned wire end, solves it, and a continuity check across the winding confirms it. For soldering generally, use flux-cored solder of a sensible gauge, a clean tip and enough heat to wet both the pad and the lead. Cold joints on ground connections are a classic cause of instability in low-power rigs. If a stage works only when you press on the board, reflow the nearby joints before you start changing component values. On the minimum test gear question: a multimeter, a dummy load, and a second receiver or SDR to listen to what the transmitter is doing will take you a long way. A scope is better. A frequency counter is very useful for crystal or VFO work. But even the basic set lets you check supply current, the presence of RF, the transmit frequency and the harmonic content, which is most of what you need to know on day one.
  3. For callsigns, the standard alphabet is the best default: Alfa, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu. It was designed so the words are distinct across many accents and languages, which matters on the bands. The spellings "Alfa" and "Juliett" are the official ones, but nobody will mishear "Alpha" or "Juliet" on voice. Improvised phonetics work fine on a local repeater where everyone knows you. They get riskier on HF and DX contacts, where the other operator may not speak English as a first language. "Lovely" or "Nancy" might not register, while "Lima" or "November" probably will. In the US, the FCC rules on station identification (Part 97) encourage a phonetic alphabet as an aid to correct identification, but they don't require a particular one. Check your own country's rules if you're elsewhere. A few practical points on callsigns: Say the whole call phonetically at least once, with a clear pause between characters. You don't need phonetics on every transmission in a casual QSO, but use them whenever someone has to copy the call correctly. Be consistent. If you gave "Kilo" the first time, don't switch to "King" the second. A listener who half-copied you can then match what they heard against the same word. Don't mix phonetics and plain letters in the same call unless you're repeating just one character for clarity. Something like "W1AW, that's Whiskey One Alfa Whiskey" is easy to follow. The ITU number words (Nadazero, Unaone, Bissotwo, Terrathree, Kartefour, Pantafive, Soxisix, Setteseven, Oktoeight, Novenine) exist in the ITU radiotelephony tables but are rarely heard in amateur radio. Most hams just say the digits. If you want an extra margin on a bad path, say them slowly and distinctly. The aviation-style "niner" for nine is common and harmless, and it helps separate 9 from 5 in noise. Saying "fife" or "tree" is optional, and some listeners will find it affected on a casual net.
  4. I'll take the first four. Station ID (§97.119): you must give your call sign at the end of each communication and at least every 10 minutes during a communication. Phone IDs must be in English, and you can use a standard phonetic alphabet. CW and digital IDs are also allowed. For digital modes, the call sign must be sent in a way the receiving station can decode. Many FT8-style exchanges carry the call sign in the message itself. A repeater with automatic control must also identify on its own schedule, and the licensee is responsible for that. Also remember that 'end of each communication' is not the same as 'end of each transmission'. In a long roundtable, the 10-minute clock is the one that matters. Third-party traffic (§97.115): a third party is someone who is not a control operator of either station but takes part in the exchange, such as a family member who gets on the mic. Domestically this is generally fine as long as the control operator is present and ready to supervise, and the content is otherwise legal. Internationally it is only allowed with countries that have a third-party traffic agreement with the US. The big exception is that if the third party is a person eligible to be the control operator of your station, such as a licensed ham, the international restriction does not apply. Also check the other country's own rules, and §97.117 on international communications. Automatically controlled stations have extra limits on third-party traffic, with some exceptions for data modes. Power (§97.313): the 1500 W figure is peak envelope power at the transmitter output, not ERP. In general you must use the minimum power necessary for the communication, so the 1500 W figure is a ceiling, not a default. Lower limits apply in places. For example, Technician privileges on HF are capped at 200 W PEP, and 30 meters is also 200 W PEP. The 60 meter band, 2200 meters, and 630 meters have their own rules, and several of those are written in ERP or EIRP, so look at the specific band section and don't assume. Also check §97.301–97.305 for which license class may use which segments. Prohibited transmissions (§97.113): the common misunderstandings are these. No one may be paid to be a control operator, with narrow exceptions such as teachers using amateur radio in a classroom. You can't use the service for communications in which you or your employer have a pecuniary interest, with limited exceptions. Occasional sale of your own surplus ham gear is acceptable. Also prohibited are music (outside a few special cases), obscene or indecent language, deliberately false or deceptive signals, and messages encoded to obscure their meaning. That last point is why encryption is off the table for ordinary amateur communications, apart from limited exceptions like control of space stations or model craft. In an emergency involving the immediate safety of human life or protection of property, other rules allow more flexibility (§97.403).
  5. On satellites, antenna choice is mostly about polarization and pointing. Many amateur satellite downlinks and uplinks are linearly polarized at the spacecraft. Since the satellite's orientation changes through a pass, a fixed linear antenna on the ground will see deep fades. A circularly polarized antenna (typically crossed yagis fed with the proper phasing) reduces that. Using a handheld three-element dual-band yagi and manually tilting it sometimes works for strong passes, though you pay for it in polarization mismatch and pointing errors. Doppler shift matters too, so the radio side needs to allow retuning during the pass. For repeaters, the antenna is only part of the story. A repeater needs enough isolation between its transmit and receive antennas or duplexer. In a duplexed system, a collinear omni on a tall mast and low-loss, well-weatherproofed N-type connections are the common approach. Water in a feedline connection can degrade a repeater long before anyone notices. For repeater access from home, a vertical yagi pointed at the machine often beats an omni, because it improves both receive and transmit and rejects off-axis interference. One more point on SWR: if you can, check it at the antenna end of the feedline with an analyzer. If it looks very different from the reading at the radio, the coax loss or a connector is hiding a problem.
  6. I'd add a caution about relying on spots for everything. In an assisted category the cluster and skimmer feeds are tools, and everyone has them, so the multipliers they show you are also the ones the whole field is chasing. That creates pileups where you can burn a lot of time. Sometimes the better move is to tune through the band yourself and find the quieter station nobody has spotted yet, since you may get a one-call answer instead of a ten-minute fight. On band changes, a simple habit that helps is checking the bandmap on the other bands every so often, even when the run on the current band is fine. Think of it as scouting. If a band is filling up with strong spots from the areas you need, that is information about propagation, and it can tell you when to move before the rate on your current band falls apart. For endurance, I'd stress that sleep planning is easier to do beforehand than during the contest. Work out which hours are most valuable for your location and band set, and plan your breaks around the weakest ones. It is also worth practicing your logging setup and keyboard shortcuts before the contest, so that your attention goes to listening instead of fighting the software when you are tired.
  7. Here is the usual order, with the acronyms explained. FRN (FCC Registration Number). This is a free identifier you get by registering in the FCC's CORES system. Get it before exam day, because the VE team needs it to file your application. Register under your legal name exactly as it appears on your photo ID, and use an email address you will keep checking, since the FCC sends your license grant there. Registration is free. If a site asks you to pay for an FRN, you are on the wrong site. VEs and the exam. A VE team is a group of licensed volunteers working under a Volunteer Examiner Coordinator (VEC) such as the ARRL VEC or Laurel VEC. They administer the test, grade it, and submit the paperwork. Technician is a single 35-question exam drawn from a published question pool. Passing is 26 correct (about 74%), but confirm the current numbers in the session announcement or your study material. Finding a session. Search the ARRL's exam session finder, or use the session listings on HamStudy. Many local radio clubs also post their own dates. Some teams run online sessions with remote proctoring, which helps if there are no in-person sessions nearby. Read each listing carefully, because it often says whether you must pre-register, which payment methods are accepted, and whether walk-ins are welcome. When in doubt, email the contact on the listing. Fees. Exam fees are set by the VE team or its coordinator, and some teams charge nothing, so I won't quote a number. The session announcement should state the amount and how to pay. Some teams take cash only, so check before you go. ULS. The Universal Licensing System is the FCC database where your license record lives. After you pass, the VE team submits your application, and your license usually appears in ULS within days. You can look up your callsign there, and you can also use it to see your status and update your address later.
  8. Ask a room full of hams what they like most about the hobby and you'll get a room full of different answers. Some love chasing faraway stations. Some love building antennas out of wire and optimism. Others mostly like turning on the radio in the evening and seeing who's around. The hobby is wide enough that all of those count, and that's a big part of why people stay in it for decades. This post is a loose tour of everyday ham life: the casual parts, the funny parts, and the small habits that make the shack a place you want to be. The Rag Chew: Radio's Best Slow ConversationA rag chew is just a relaxed, unhurried conversation between stations. There's no contest exchange and no rush to log a contact and move on. You might talk about the weather, the rigs you're running, what's going on in your town, or a project you've been putting off. What makes rag chewing appealing is how little it requires. You don't need a big signal or fancy gear. You need a clear frequency, a friendly tone, and a willingness to listen. A few habits help: Ask open questions. "What are you running there?" beats "What's your signal report?" if you want the conversation to go anywhere.Let the other person finish. Radio has a built-in pause between overs, so use it.Don't worry about being interesting. Most people are happy to talk to someone who's simply curious.Over time, regular conversations tend to turn into on-air friendships. You learn someone's voice, their sense of humor, and the rhythm of their operating schedule, often without ever meeting in person. When a familiar station turns up on the band, it feels a bit like a neighbor waving from across the street. Club Nights Are More Than MeetingsRadio clubs vary a lot, but the good ones tend to share a few traits. There's usually coffee, a little business, a talk or demo, and a long tail of conversation in the parking lot afterward. That tail is often the best part. If you've never gone to a club meeting, a few things are worth knowing: You don't need to be an expert. Clubs are full of people who started out knowing very little.Questions are welcome. Most hams enjoy explaining things, sometimes a little too much. Be ready for a thorough answer.Showing up matters more than contributing right away. Once people recognize you, opportunities to help with field day, a repeater project, or a public service event tend to come up naturally.Club meetings are also where a lot of practical knowledge changes hands. Someone mentions a noisy power supply, someone else has seen it before, and suddenly your problem is half solved over a cup of coffee. Elmers: The Hobby's Unofficial TeachersIn ham radio, an "Elmer" is a mentor, someone who helps newer operators learn the ropes. There's no formal program or certificate. It's usually just a more experienced person who takes the time to answer questions, look over an antenna plan, or help someone make a first contact. Good Elmers share a few qualities. They explain the why, not just the what. They let you make your own decisions, and they're honest about what they don't know. The best ones also pass the favor along, which is how the tradition keeps going. If you're new and looking for an Elmer, try your local club, a repeater net, or a hamfest. If you're experienced, consider being one. You don't need to know everything. You just need to remember what it felt like not to know. Hamfest Finds and Hamfest DisciplineA hamfest is part swap meet, part reunion, part treasure hunt. Tables hold everything from vintage receivers to boxes of mystery connectors, and the temptation to come home with a trunk full of "projects" is real. A little discipline goes a long way: Make a short list before you go. Coax, connectors, a particular accessory, or a specific kind of tool keeps you focused.Ask if you can test it. Many sellers have a power supply handy. A radio that powers up and receives is a better bet than one sold "as is, worked when stored."Check the basics. Look for missing knobs, corrosion in battery compartments, cracked connectors, and signs of past repairs.Know when to walk away. There will always be another table and another deal.Some of the best finds are small: a well-made adapter, a decent key, a used book that explains something clearly. Not everything worth owning has a dial. Favorite Rigs Are Usually the Ones You UnderstandHams love to debate radios, but a favorite rig often has less to do with specifications than with familiarity. It's the one whose menu you know, whose receiver you trust, and whose quirks you've learned to work around. That doesn't mean you should avoid new gear. It means a radio you've taken the time to learn often outperforms a better radio you haven't. Spending an evening reading the manual, exploring settings, and noting your preferred configurations can improve your operating more than an upgrade would. The Humorous Mishaps Everyone Eventually SharesNearly every operator eventually runs into some version of these classic mistakes: Calling and calling, then realizing the radio was on the wrong band, mode, or frequency.Troubleshooting a "dead" antenna that turned out to be a loose connector or an unplugged cable.Wondering why nobody hears you when the power is turned all the way down or the microphone gain is set strangely.Forgetting that the mic was keyed while saying something not meant for broadcast.Spending an hour chasing a noise problem that turned out to be a cheap charger or LED light in the house.These moments are annoying in the moment and funny afterward. They're also how people learn. Most experienced hams developed their troubleshooting habits by making exactly these mistakes: check the simple things first, change one variable at a time, and keep notes. Lessons That Keep Showing UpA few ideas seem to come up again and again in the hobby: Antennas matter more than almost anything. A modest radio on a good antenna usually beats the reverse.Listening is a skill. Time spent tuning around and hearing how the bands behave makes you a better operator.Safety isn't optional. Respect power lines, grounding, ladder work, and RF exposure guidelines.Keep it simple at first. A basic station you actually use is better than an ambitious one that stays half finished.Be kind on the air. The bands are shared, and a little courtesy goes a long way.Milestones, Big and SmallHobby milestones don't have to be dramatic. Passing your first license exam, making a first contact, finishing a homebrew project, earning a new license class, getting a station working in a new band, or helping someone else get on the air all count. It's worth noting them, even casually. A logbook, a notebook, or a note on your phone makes it easy to look back and see how much you've learned. What the Hobby Means Day to DayFor many people, ham radio is less about any single achievement and more about the texture it adds to ordinary life. It's a reason to step into the yard and look at the sky, a reason to learn some electronics, a reason to talk with people you'd never otherwise meet. It's also a practical skill set that can be useful when other communication options are limited. Mostly, though, it's a hobby that rewards curiosity. You can go as deep as you like, or just keep it casual. Turn on the radio, listen for a bit, and see who's out there. The next good conversation might be one call away. 73, and happy listening.
  9. I'd keep one master log in ADIF and treat every award site as a view of it, not as the log itself. That way POTA, SOTA and LoTW uploads all come from the same source, and you can filter by band, mode, entity or year when you want to see what is missing. On paper QSLs: it is usually worth it only for the entities that are rare or where the operation is unlikely to upload to LoTW. Some DXpeditions upload to LoTW, and some use other routes, so check the operation's own page before spending money on postage. If you can get the confirmation electronically and it is accepted for your program, that is usually quicker than waiting on the mail. One more tip: don't merge programs that look similar. A WAZ zone is not a DXCC entity, a WPX prefix is not a zone, and an IOTA reference is not an entity either. If your spreadsheet has separate columns for entity, CQ zone, prefix and IOTA reference, you can often tell at a glance which new contact helps which award. For the CQ DX Marathon, add a year column and filter on it, so last year's confirmations don't get counted by accident.
  10. I'd add some listening to your plan. Propagation questions make much more sense once you've heard 20 meters die at night, 40 meters open up after dark, or 10 meters come alive during good solar conditions. A web SDR or a remote receiver is fine for that, and you can compare what you hear against the solar flux and K-index numbers the pool asks about. That ties the abstract material to something you've observed. For digital modes, don't just memorize that FT8 is popular. Learn how the radio is set up: USB, the dial frequency sits below the audio passband, and your waterfall offset adds to the dial frequency to give your actual transmit frequency. It also helps to understand why a narrow, low-symbol-rate mode can get through when voice can't, and why the FCC limits symbol rate in some segments. Those ideas show up in questions and also keep you from making a mistake on the air. For band edges, practice with a blank grid. Draw each HF band, mark CW/data and phone segments, then check it against a current chart. One caution: band plans and rules can change, so use a current official source, not a table from an old study guide, and confirm anything you're unsure of with your VE team on exam day.
  11. Don't overlook the smaller or lower-pressure events. State QSO parties are an easy way to practise short exchanges, and many of them welcome casual operators who just want to give out a county. VHF contests can be fun even with a simple 2 m SSB or FM setup, and grid squares are a nice way to learn geography. For Field Day and Winter Field Day, the rules are different enough from regular contests that I'd read the current rule set carefully each year. Category definitions, bonus points, and what counts as a valid QSO can change, and club logging teams often get tripped up on details such as power source and class designations. SOTA is worth a mention because it overlaps with contest operating in an interesting way: you may find yourself activating a summit during a contest weekend, but the SOTA logging system and the contest log are separate things. If you plan to do both, keep notes so you can enter the same contacts correctly in each system without duplicating or mislabeling them. Finally, when you are deciding where to submit logs, check the sponsor's FAQ for file naming and email subject-line requirements. Some sponsors still depend on those conventions for robot processing, and a small mistake can delay your log acknowledgement.
  12. On rig control, the main thing to check is whether your radio can take frequent CAT updates without audio glitches. Some radios mute briefly on every frequency write, and that is very annoying on SSB. If yours does that, reduce the update rate in the tracking software, or tune manually in small steps and let the software handle only the larger corrections. For linear birds, I'd suggest deciding in advance which frequency you want to keep fixed. Most operators keep the downlink fixed and move the uplink, because it keeps the received signal comfortable. If you do it the other way around, the receive tone will keep shifting and you will spend the pass chasing it. The other common trap is the inverting passband. On RS-44, as you tune up on the uplink, the downlink moves down. If you have not practised that mapping, it is easy to walk off a QSO. A few listening-only passes first are worth it.
  13. On security, the main rule is not to expose a radio's control port directly to the internet. Most rigs and network adapters were not designed to face hostile traffic. Plain port-forwarding to a transceiver, a Pi or a desktop with VNC or RDP open is the classic way to get scanned and attacked within hours. A VPN into the remote site is the safer baseline. WireGuard or a mesh VPN such as Tailscale are common choices, and a router with a VPN server works too. Then you reach the radio, controller and PDU over a private tunnel instead of publishing them. If a vendor feature does require inbound connectivity, read exactly which ports and protocols it uses and restrict them as tightly as you can. Beyond that: put station gear on its own VLAN or at least its own subnet, use unique strong passwords and change defaults on the router, Pi and any web interface, keep firmware and OS updates current, and turn off services you don't use. Also plan for the day the link dies mid-transmission. Use the radio's transmit time-out timer, a watchdog that drops PTT or power if the control session disappears, an SWR and power protection plan for the amplifier, and a remote power switch on separate out-of-band access, such as a cellular backup, so you can reboot or cut power to a stuck system. On the rules, I can't give a universal answer, because they depend on your country and licence class. The common principles tend to be these: the licensee or control operator remains responsible for the emissions, you need a reliable way to stop the transmitter if something goes wrong, identification and band-plan rules still apply, and your privileges are those of your licence at the location of the transmitter. Operating a station in another country can raise additional issues. Reciprocal or CEPT-style arrangements may not clearly cover remote operation, and some regulators have specific remote-control provisions. If you are lending out your station or using a third-party remote base through a service like RemoteHams.com, you should also check who counts as the control operator and what the host or service requires. Read your regulator's current text rather than relying on forum summaries, including this one, and ask the regulator or your national society if something is ambiguous.
  14. On the sound card side, most failed sessions come down to audio and PTT rather than Winlink itself. Set the rig to a data mode (USB-D or the equivalent) and turn off speech processing, compression, and any noise reduction that touches the receive audio. Pick a PTT method that works reliably: CAT, a serial RTS/DTR line, or a CM108-style GPIO in an interface that supports it. VOX tends to clip the start of a transmission and is a poor fit for protocols that expect clean timing. In Windows, disable audio enhancements on the radio's sound device, and keep system sounds off that device so a notification never goes out on the air. Set the transmit drive for a clean signal rather than maximum power. With most sound card modes you want little or no ALC action. Power turned down and a clean signal beats a loud, distorted one, and over-driving also splatters onto neighboring channels. VARA and ARDOP both give you tuning or level displays, so use them instead of guessing. For 1200 baud packet, a KISS TNC or a sound card TNC both work, but check how your software expects to reach it. Winlink Express talks to supported TNC types over a serial or Bluetooth serial port, and a software TNC may need a bridge to present itself that way. For VARA FM, the narrow mode works through ordinary mic and speaker audio. The wide mode needs a radio and cable with a flat data path, so a plain mic/speaker connection may not be enough. As for the first-mode question: ARDOP is the easier place to start if you want to avoid license costs, and VARA is worth trying afterward to compare. Whichever you pick, test on Telnet first, then on a local VHF gateway if one exists, before attempting HF.
  15. On height, a horizontal wire matters more than most people expect. A 40 m dipole at about 30–40 ft (roughly 0.25–0.3 wavelength) gives a mix of low and high angles. Much lower than 0.2 wavelength and the pattern turns toward high angles, which is great for regional contacts (NVIS) but poor for DX. Neither is wrong; it depends on what you want to work. On the higher bands, even a modest height is a decent fraction of a wavelength, so a 15 m or 10 m wire can be quite effective. A vertical makes sense if low-angle performance is the priority and you can fit radials. The weak point is almost always ground loss, not the radiator, and the radial system is what sets the efficiency. Verticals also tend to pick up more local noise on receive, so a quiet horizontal can sometimes hear better even when it is the weaker transmitter. For stealth, thin insulated or dark-coated wire disappears against trees or a fence line. A flagpole with a hidden wire is a common approach, and an attic dipole or loop is another, though attic installs suffer from nearby wiring and ducting, and a magnetic loop indoors loses some efficiency. Whatever you build, check your RF exposure at the antenna location, since a small yard puts the antenna close to people. For comparison, a NanoVNA is great for finding resonance, checking feedline behavior and tuning the choke. For real-world comparison, WSPR or Reverse Beacon Network spots let you compare two antennas on the same band at the same time of day, if you can switch between them quickly. That is more informative than SWR alone, though it still depends on propagation and the stations that happen to be listening.
  16. Start with how the exam is built, because it tells you where to spend time. The Element 2 pool is divided into subelements by topic (commission rules, operating procedures, radio wave propagation, antennas and feed lines, electrical principles, safety, and so on). Each subelement is split into groups of related questions, and the exam draws one question from each group. That means you can't skip a whole topic and hope it doesn't show up. A pass is 26 of 35 correct, so you can miss 9. I'd go through the pool by subelement and use a study guide or an app that explains the answers. When you hit a question you missed, find out why the right answer is right. Many pool questions are written so that a concept you understand once helps with several variants. Pure memorization works for some people, but it's brittle: if the wording shifts slightly or you blank on one answer, you have nothing to fall back on. Also, the answer order is typically scrambled on the exam, so remembering 'it was C' won't help. On privileges and license terms, make sure you know these: Technicians get all amateur privileges above 30 MHz, which includes the popular 2 meter and 70 centimeter bands.Technicians also get limited HF access: CW on parts of 80, 40, and 15 meters, and voice, CW, and digital segments on 10 meters. Check the exact segments and power limits in the current rules or your study guide, since the pool expects you to know them.An amateur license term is 10 years, and there is a grace period after expiration during which you can renew but can't operate. Know the length of that grace period.One practical point: confirm which version of the pool your exam session uses. Pools are revised on a multi-year cycle, and an old study book or practice app can contain questions that no longer appear or answers that changed.
  17. I like the idea of treating club events as a pipeline: hamfest, then a club meeting, then an Elmer, then a VE session, then Field Day. Newcomers often come to a hamfest because they're curious and stay because someone offered help. A club table with a sign-up sheet, a few handhelds, and a simple demo of digital modes or a satellite pass gives people an easy way to start a conversation. Elmer programs work best when they're specific. "Come learn about HF" is vague, but "Bring your antenna questions and we'll help you plan a wire dipole" is concrete. Topics like grounding, coax choice, logging, and getting on the local repeater are all good, and so are simple build nights where people leave with something working. For VE sessions, publicizing the schedule and what to bring helps a lot, and so does having a friendly person at the door to answer questions. A new ham who passes the exam may then want to join Field Day, so it's worth inviting them while the excitement is fresh. For Field Day, do a dry run before the event. Test the generator or batteries, check the logging software and network, label coax, and make sure everyone knows the rules and exchange for their station. A rehearsal on a regular club weekend will usually find problems that would be much more annoying on the real weekend.
  18. On the tracker side, what the radio sends depends heavily on its beacon settings, and the defaults are often not ideal. Both the TH-D74/D75 and the FT5D can get position from their internal GPS and beacon it, and they typically encode it as Mic-E. Mic-E is a compact format that puts the latitude in the destination address field and the longitude, speed and course in the information field. That keeps the packet short, which matters on a 1200 baud shared channel. It also carries a status code such as In Service or Emergency. Some aprs.fi pages and decoders show the raw destination as odd characters, and that is normal. Check each radio's manual for exact menu names, because they vary by model and firmware. For beacon timing, a fixed interval is wasteful. Sending every 30 seconds while parked fills the channel with identical positions, and sending every 10 minutes at highway speed gives a track that cuts corners. SmartBeaconing addresses both. Its parameters are typically a fast speed with a short rate, a slow speed with a long rate, and a turn-detection group: minimum turn angle, minimum time between turn beacons, and a turn slope that scales the threshold with speed. It beacons often when moving fast, rarely when slow or stopped, and extra when the heading changes. Start with the radio's defaults and adjust from the observed track. If the track is jagged at low speed, the turn settings are usually the place to look. For path, WIDE1-1,WIDE2-1 is the usual mobile setting, because it works with fill-in digipeaters and wide-area ones. Long paths like WIDE2-2 or higher are best avoided unless the area really needs them. Each extra hop multiplies the traffic on the channel. Two extras once the basics work. First, objects: an object has a 9-character name and can be marked live or killed, so a station can place things like an event or a net location on the map. Because it is retransmitted on a timer, a long period is better than a short one. Second, messaging: addressees are padded to 9 characters, the text is limited to 67 characters, and a message number lets the receiver acknowledge it. If the message goes via an iGate, the recipient generally has to have been heard on RF recently. That is why a message to a station that only ever beacons from the internet may not reach a radio. For a weather station, use a proper weather report, with wind, temperature, rain, humidity and pressure in the APRS fields, not a plain text comment. Keep the interval modest. A weather update every 10 minutes or so is generally plenty for a conditions display.
  19. For anyone deciding what to buy first, my advice is to resist the urge to buy everything at once. A decent handheld, a programming cable if your radio needs one, and a better antenna than the stock rubber duck will get you on the air locally. It's also worth learning how to program the radio with software like CHIRP, if it's supported, so you aren't stuck typing in every memory by hand. Then use that setup for a few weeks. You'll find out whether you like rag chewing on repeaters, nets, emergency communications, digital modes, or HF. That tells you what to buy next, so you don't end up with a pile of gear for things you never do. A few common mistakes: transmitting into a dummy load or antenna you haven't checked, forgetting to identify, using too much power when you don't need it, and running cheap coax for a long run on VHF or UHF where loss adds up fast. If your radio will be used in a car or at a campsite, also check the RF exposure guidelines for your power level and antenna placement.
  20. On checking availability: search the call in ULS and look at the license status, not just whether a record exists. Expired, cancelled and terminated records can mean different things. A call can look free but still be inside the two-year waiting period, and then it isn't available to you unless you're the former holder or a qualifying family member. If the status is Active, Expired in grace, or Cancelled recently, treat it as probably not grantable yet. The FCC's pages list calls pending in other applications, which helps you avoid duplicating a filing. For how many choices to list, there's a limit on the number per application, so use the whole list. Put your real preference first and then work down. Include calls from the group your operator class qualifies for. A 2x3 request with Technician or General is easy to grant, while a 1x2 or 2x2 only works if you hold Extra. If you list a call you aren't eligible for, it's skipped, so it doesn't hurt the others, but it wastes a slot. On the district move: a systematic change is optional. Your call stays valid and you don't need a new one just because you moved. Some people keep their original call as a point of identity. Others ask for a new sequential call to match the district. Either is fine under the rules. Just keep your mailing address and email current in ULS, because the FCC uses them for official communication.
  21. For efficiency I would start with the antenna and work backwards. A 5 W signal on a good resonant dipole at a reasonable height will often be heard better than 20 W into something short and lossy. If you use an end-fed half-wave, be careful with the feedline and counterpoise. The transformer, the coax length and common-mode current on the shield can all change the result. A small choke or ferrite near the radio can help keep RF off the station and out of the rig. For the battery, count both transmit and receive current. A rig like the KX2 or a Mountain Topper-style radio listens at low current, so a small LiFePO4 pack can last a long time at 5 W CW. SSB at 10 W PEP draws more, but because speech is not continuous the average current is lower than the peak figure suggests. I would still fuse the battery lead and make sure the pack voltage stays within the radio's rated range.
  22. Yes, LoTW first makes sense. Before you upload anything, treat the certificate as something to back up. Export the .p12 file from tQSL and store it somewhere other than the computer it lives on. Put the password in your password manager too. If the machine dies and you have no backup, you end up redoing the request, and the first-time verification can mean a wait. The other common LoTW problem is station locations. If you operate from home, a portable spot and a club station, make a separate location for each, and check the grid and zones every time you sign a batch. A good log signed against the wrong location can fail to match, or it can match and then be worth nothing for the award you are chasing. Do a test upload of a small batch before sending years of logs. On the paper side, I would keep two buckets. Cards you want for DXCC or a specific award go in one, and nice-to-have cards go in the other. That decides whether you spend on direct postage or just let the bureau handle it.
  23. For DMR and D-STAR especially, I'd stress that the radio setup is the main hurdle, not the repeater. With DMR you need the right frequency pair, the right color code, the right time slot and the right talkgroup, and if any one of those is off the repeater may ignore you completely. Color code is not a privacy feature. It works like a tone to help the repeater decide whether a signal is meant for it. Check the repeater's documentation for which talkgroups are static and which are on-demand, because some of them tie up a lot of network capacity and others are meant to be used only briefly. With D-STAR, make sure your RPT1/RPT2 and URCALL fields match what the repeater or gateway expects, and learn how reflectors and modules work before you connect to one. For Wires-X, the room or node you're linked to determines who can hear you. Whichever mode you use, pause between transmissions, since digital linking can add delay and people trying to break in need a slightly longer gap. Directories like RepeaterBook and the ARRL directory are a good place to start looking for local repeaters, but I'd still verify the details with the local club's website or trustee.
  24. Q codes were created as short three-letter signals for radiotelegraph. Each can be a question (with a question mark) or a statement. "QRL?" asks "is this frequency in use?" while "QRL" on its own says "this frequency is busy." Here are the ones you listed: QRM is interference from other stations, meaning man-made signals. QRN is natural noise, such as static from thunderstorms. A quick way to remember: N for natural, M for man-made. Power-line noise and a neighbor's electronics are usually described as local noise or interference, not QRN. QRP means low power, and as a question it asks whether to reduce power. Operators and contests define it differently, but 5 watts CW or 10 watts SSB peak is the common benchmark. QRO is the opposite: high power, or "increase power." QRT means stop transmitting or shut down. "I'm going QRT" means you're closing the station. QRZ? means "who is calling me?" and is common after a faint or doubled call, or in a pileup when the DX station wants to hear the next caller. It has nothing to do with the QRZ.com website except the name. QSL means "I acknowledge receipt" or "I confirm." On air, "QSL?" asks whether you copied. It also gives its name to the QSL card, the written confirmation of a contact, and to electronic confirmations like Logbook of the World. QSO is simply a two-way contact. QSY means change frequency. "QSY 14.250" means move to that frequency. QTH is your location, so "QTH?" asks where you are. QSB is signal fading, the rise and fall in strength you hear on HF. QRL is the polite check before you call CQ on a frequency, as explained above. A few related codes you'll hear: QRG (your exact frequency), QRS (send more slowly), QRQ (send faster), QRX (stand by), QRV (I'm ready) and QTC (I have messages or traffic). On voice, many operators just say the plain-language version, and that is always acceptable.
  25. I'd put noise testing earlier than most checklists do, because it decides what you can keep on the power bus. MPPT solar controllers and cheap 12 V to USB or laptop adapters are common HF noise sources. A practical routine is to tune to a quiet spot on each band you plan to use, note the S-meter or SDR noise level with only the radio running, then switch on one accessory at a time. If a device raises the floor by an S-unit or more, try these fixes in order: a clamp-on ferrite on both the input and output leads (several turns through a suitable mix, not one pass), separating it from the antenna feedline, or powering it from a different branch. Sometimes the answer is to disconnect the solar controller while operating and let the panels recharge between sessions. On generators, inverter models are quiet acoustically and usually friendlier to radio than old open-frame units, but they are not noise free. Keep the generator as far from the antenna as the cords reasonably allow, use a properly rated outdoor cord, run GFCI protection, and don't backfeed anything into building wiring. If the station is battery-based, a generator can be reserved for charging in a scheduled window instead of running through every net. That also reduces fuel use and CO risk. One LiFePO4 note: most cells should not be charged below freezing unless the battery has low-temperature charge protection or a heater. For winter deployments, check the manufacturer's spec before assuming solar or a DC-DC charger will work at dawn.

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.