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_Chrissy

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Chrissy

  1. One thing worth adding is repeater and satellite use, since the right antenna is almost the opposite for the two. For repeater access, a vertical omni or a vertical yagi pointed at the repeater is the usual approach. If you are weak into the repeater but can hear it fine, a small yagi (3 to 5 elements) may help more than a bigger omni, since it improves the transmit and receive link in one direction, and also reduces pickup from other directions. At a repeater site the antenna is typically a high-gain collinear fed with low-loss hardline, with a duplexer or separate antennas for transmit and receive. When separate antennas are used, vertical separation is much more effective than horizontal separation for isolation. Satellites are a different problem. Most amateur satellites transmit on 2 m and 70 cm with linear polarization from the satellite's point of view, but the polarization seen on the ground changes as the satellite tumbles and moves. That is why circular polarization (commonly a crossed yagi, with right-hand circular as the usual choice) is common for fixed tracking setups. Many people working FM LEO satellites use a handheld directional yagi and simply rotate the antenna as the signal fades. Doppler shift on 70 cm is also large enough that you need to retune during a pass, and full-duplex operation (hearing your own downlink while you transmit) helps with that. A simple J-pole or ground-plane antenna can work for the strongest passes at high elevation, but the low-elevation parts of a pass usually need gain and pointing. Also a reminder about safety. Keep any mast and antenna well clear of power lines, including when it is being raised, and be careful with the RF exposure limits of higher-power setups when an antenna is mounted close to living areas.
  2. 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. You do not have to ID at the start of a contact. People often assume you do, but the rule is the end of the exchange plus the 10-minute interval. The call sign must go out by a method that is legal on that channel: CW, phone in English, or the data or image mode you are actually using. Phonetics are encouraged but not required. A tactical call such as "Net Control" or "Aid Station 3" is fine for operational clarity, but it does not replace the FCC call sign. The ID is still required on the schedule above. Third-party traffic (§97.115). This is easy to over-apply. "Third party" means a message passed on behalf of someone who is not one of the two control operators. A friend sitting next to you is not a problem in itself. An unlicensed person can take part in a contact if a properly licensed control operator is present at the control point, can supervise, and can stop the transmission. The station licensee stays responsible. International third-party traffic is only allowed with countries that have a third-party agreement with the US, or where the third party is eligible to hold an amateur license. Look up the current list before you offer to pass a message abroad. Also, third-party traffic can't be used to get around the business restrictions below. Power (§97.313). The general ceiling is 1500 W PEP transmitter output, and you are also supposed to use the minimum power necessary for the communication. The limit applies to transmitter output, not to ERP, except in a few places such as the 60-meter channels, which have their own ERP-based limits. Some HF segments have lower limits, such as 200 W PEP on 30 meters and on the HF privileges that Technicians have. A few areas also have lower limits on 70 cm because of other users in the band. Check the section for your band and license class. Prohibited transmissions (§97.113). The main categories are: communications for pay or a business purpose on your own behalf or your employer's, with narrow exceptions such as a teacher in class and occasional sale of your own station gear; music; messages encoded to obscure their meaning; obscene or indecent language; false or deceptive signals; and broadcasting. Plain abbreviations and Q-signals are not encryption. Encryption is a different matter, and the main exceptions are control of space stations and model craft. Digital modes also need publicly documented protocols under §97.309, so you can't use a private code and call it a data mode. Emergency communications involving immediate safety of life or protection of property have their own provisions in §97.403.
  3. The Q-code ambiguity is the key to the whole system. Each code is a question when followed by a question mark and a statement or answer without one. QRL? means "Is this frequency in use?" A reply of QRL means "Yes, it's busy." QSY? asks "Shall I change frequency?" and QSY says "change frequency" or "I'm changing." Here are the ones you listed: QRM is man-made interference, such as another station on your frequency or a noisy device. QRN is natural noise, mostly static from storms. QRP is low power. By convention that is 5 W or less on CW and 10 W PEP on SSB, though the code itself just means "reduce power." QRO is the opposite, high power. QRT means stop transmitting, so "I'm QRT" means you're shutting down for now. QRZ? means "Who is calling me?" It's what you send when you heard a partial call or someone calling but couldn't get the full callsign. QSL means "I acknowledge receipt" and also names the confirmation card or electronic confirmation of a contact. QSO is a contact or conversation. QTH is your location. QSB is signal fading, where a signal swells and drops over seconds. On the other items: CQ is a general call to anyone, and DE means "from." A typical CW call is CQ CQ CQ DE W1ABC W1ABC K. 73 means best regards and 88 means love and kisses. 88 is used between friends or spouses, and sometimes jokingly. Many operators say "73" rather than "73s" because 73 is already plural in meaning, though you'll hear both. The same small family covers ending transmissions. K means "go ahead, anyone." KN means "go ahead, only the station I'm working, please." That's useful when a pileup is around. SK signals the end of a contact. AR marks the end of a message. On CW, prosigns like AR, SK and KN are sent run together as one character, not spaced as letters.
  4. On special events, I'd add a logging habit that saves a lot of headaches: record the exact special callsign as sent, not the sponsoring club's call, and note band and mode separately. Some certificate programs count each band or mode as a separate contact, and some only count one. If the event page has a QSL manager or an online log, check that your contact appears there before you send anything by mail. Also keep an eye on the dates. Special event stations are often active only for a limited window, and certificates may need to be requested by a certain deadline. If the page doesn't state a deadline, ask the operators rather than assuming. As for working them, make it easy on the operator. Listen first to learn whether they're running split or taking calls by area, give your callsign once or twice with phonetics, and let them finish the exchange. A calm, clean contact is quicker for everyone, and the person at the key is probably dealing with a lot of callers at once. One more net point that gets overlooked: many nets welcome listeners and new check-ins, but a few are restricted to members or served-agency volunteers. If the net's information page says who can check in, follow that, and if it's unclear, ask NCS or the net manager outside the net, not mid-session.
  5. On studying, you don't need to pick just one resource. The Technician exam is 35 multiple-choice questions drawn from a public question pool, and you need 26 correct to pass. Because the whole pool is published, practice exams are very effective. The pool is revised on a multi-year cycle, so make sure whatever you study matches the pool in effect on your exam date. A book or app tied to an expired pool can teach you questions that won't appear. HamStudy. It's good for daily repetition. It uses spaced repetition, shows explanations, and tracks which topics are weak. A few short sessions a day usually work better than one long cram. The ARRL Ham Radio License Manual. It's worth getting if you want to understand the material, not only pass. It explains why a 2 meter handheld behaves differently from an HF rig, what a repeater offset is, and how basic electricity and antennas work. A good approach is to read a chapter, then drill that chapter's questions in an app. Practice exams. Take full 35-question simulated exams. When you're scoring comfortably above passing, say in the high 80s or better, across several attempts, you have some margin for exam-day nerves. Review every miss and make sure you can explain the right answer. Answer order is often scrambled on the real exam, so memorizing "it's C" won't help. Exam-day tips. Read the whole question and every option before choosing. Watch for words like "not" and "except." Skip a question that stumps you, then come back to it. Don't change an answer unless you can say why the first one was wrong. First steps after passing. Check ULS for your call sign. Don't transmit until the license is granted and shows up there, so your call sign is on record. Then learn the basics of identifying with your call sign, and listen on local repeaters before you transmit. A repeater directory and your local club are good places to find frequencies, offsets and tones. A handheld is a common first radio, but listen first and ask club members before you buy. If you're interested in the General class later, you can often take that exam at the same session, so ask the VE team beforehand.
  6. On calendars: the WA7BNM Contest Calendar is the usual starting point because it lists the next eight days and a longer list by month, with links to the sponsor rules. The thing to avoid is trusting the pattern ("last full weekend of October") without checking the actual date, especially around month boundaries where "full weekend" can fool you. I'd put the contests you care about in your own calendar with the start time in UTC, since contest clocks run on UTC and local time zones and daylight saving will mess up your planning. For the Cabrillo check, I'd open the file in a text editor before uploading. Look at CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-POWER and CALLSIGN, then scan a few QSO lines to confirm the exchange fields landed in the right columns. Most sponsors will run a log checker, but if the header is wrong you may end up in the wrong category.
  7. I would add two cheap items to the list: an SWR bridge you build yourself and a simple keyer or at least a clean keying circuit. A resistive or Wheatstone-style return loss bridge is easy to build and teaches a lot. Just keep leads short, use matched resistors, and check it into the dummy load first (it should show a very good null), then into an open and a short, to confirm it responds the way it should. A tandem match or Bruene-style SWR meter is also nice for monitoring forward and reflected power, but calibrate it against something known before trusting the numbers. For keying, a transmitter that clicks badly is annoying to everyone on the band. A simple RC network or a slightly slower keying transistor to shape the rise and fall of the envelope helps a lot, and a scope will show you the result. Also be careful that keying the oscillator itself does not cause chirp. Often it is better to leave the oscillator running and key a later stage, though that needs good shielding or layout to avoid leakage into the receiver. Finally, if you are using a uBITX or similar, do not trust that the output is clean on every band just because it works. Check the low-pass filter board, confirm what is actually on each band, and look at the output on an attenuated SDR or spectrum analyzer before putting it on air.
  8. The SWR-versus-efficiency point can't be repeated enough. I'd add that for a small lot the real question is which antenna lets you get the most wire in the air at the highest point. A 130 ft doublet at 25 ft will often be a better all-band radiator than a loaded antenna at the same height, even though the doublet needs a tuner and the other one shows a flat match. If I were choosing for HOA stealth with a decent tree, I'd consider a doublet or an inverted V fed with ladder line. The ladder line is nearly invisible, the tuner takes care of the mismatch, and the losses stay low as long as the line is kept away from metal and routed with sensible spacing. The one thing to watch is common-mode current where the ladder line meets the tuner. Use a 4:1 current balun or a proper choke there, and don't let the feedline run in parallel with the wire for long. The EFHW is attractive for portable and quick installs because it needs no tuner on its resonant bands. But it's resonant on the fundamental and harmonics only, so a 40 m version covers 40, 20, 15 and 10 m, and 30, 17 and 12 m need a tuner and a little patience. Pay attention to the transformer too. A small core running 100 W on SSB is fine, but 100 W of FT8 at a high duty cycle can heat a marginal core. The core mix and size matter more than the ratio printed on the box.
  9. On the low bands I'd put receive noise first, because 2 m and 70 cm EME is often limited by how well you hear rather than how much power you run. Mount a low-noise preamp at the antenna or feedpoint, with a sequenced low-loss relay, and use a noise figure that is well under 1 dB. Every few tenths of a dB of loss ahead of that preamp counts directly against the weak echoes. A long run of ordinary coax with a relay at the shack end can cost you more than a bigger array would give you. Sequencing matters just as much on transmit. The relay should switch before the PA is keyed, and the PA should be unkeyed before the relay releases, otherwise you can damage the preamp or the relay. On polarization, the two effects get mixed up. Faraday rotation is rotation of linear polarization in the ionosphere. It is strongest on 144 MHz, fades with frequency, and varies over minutes and with the time of day. Spatial polarization offset is geometric and depends on where the two stations are relative to the Moon. It can be large when the stations are far apart in longitude. The practical fix on 2 m is an array that can change polarization, such as a rotatable boom, switchable crossed Yagis, or at least an ability to select horizontal, vertical or the two combined. Many stations simply wait for a better moment, and that is a legitimate option. At 1296 MHz and above, rotation is small enough that people usually switch to circular polarization. The reflection reverses circular sense, so the groups on those bands agree on a convention for which sense is sent and which is received. Confirm it with your sked partner before you blame the antenna. Before any contacts, measure the system. Sun noise and Moon noise measurements, plus your own echoes in WSJT-X, tell you more than a spec sheet does. If you cannot hear any of your own echoes, a contact with a similar station will not happen either.
  10. On the other half of your question: structure, head copy and confidence. Short daily sessions work better than long weekly ones. Fifteen to twenty minutes while you're fresh beats an hour when you're tired, because your brain consolidates the sounds between sessions. If a session starts feeling like a struggle, stop. CW Academy, run by CWops, is worth a look if you do better with other people. It offers free online classes with an advisor and a small group, and the beginner level is built for people starting from nothing. Class availability and format change, so check the CWops site for current sessions. The value is accountability and having someone to ask when you're stuck. You will still need daily practice between classes, and a class pairs well with LCWO or G4FON. For head copy, make the move from paper early rather than waiting until you feel fast. Some habits that help: Don't write down every letter while you're still learning a character. Write it only when you've recognized it. If you miss one, let it go and listen to the next. Dwelling on a missed letter makes you miss the next two. Practice with real words and common call signs, not just random groups. Once you know a handful of characters, short words and callsign-shaped strings help you hear patterns. Eventually you'll start recognizing whole words like 'THE', 'AND' and 'CQ' as single sounds. Listen without copying at all sometimes. Letting the code wash over you at a speed slightly above your comfort level, then just noting what you caught, is useful for ear training. On confidence, a typical path is to practice with a trainer until you can copy at a modest speed, then listen to real on-air CW. Look for slower operators, and for code practice transmissions if any are scheduled (the ARRL's W1AW is one source, but check their current schedule). Your first QSOs can be very short. Calling CQ and sending 'QRS' (please send slower) is normal and fine. Most operators will happily slow down if you ask. Keep a small card of standard exchanges (call, name, RST, QTH) so you aren't improvising everything at once. The plateau most people hit somewhere in the middle is normal. It usually passes if you keep the daily sessions going and don't switch methods every week.
  11. VHF FM is a sensible way to start, provided you check that someone is likely to hear you. In a populated area with active repeaters and simplex users, a handheld and a decent antenna can get you the four contacts. Out in remote country, the number of people within line of sight can be small, so an alert on SOTAwatch matters, and so does having a second option. HF takes away that dependence on local population because 40 m and 20 m can reach chasers hundreds of miles away. For a light HF kit, a common approach is a compact QRP rig, a linked or end-fed wire antenna on a lightweight pole, a small LiFePO4 or similar battery, a short coax run, and a paddle or a headset mic. CW gets a lot of weak-signal performance out of little power, but SSB is fine if you're more comfortable on voice. Whichever you choose, test the whole setup in a park or your yard first. Most failures come from small things like a missing connector, a battery that can't supply TX current, or an antenna you can't tune quickly with cold hands. Also, when you're on HF, announce the full summit reference clearly the first few times. Chasers will often copy the reference by ear and then check it against the spot.
  12. On partitioning, I'd split by consequence of failure. If a crashed Linux process could leave a transmitter keyed, a rotator driving into its stop, or an antenna relay in the wrong state, put the safety logic on a microcontroller. Give it a watchdog and a PTT timeout, and make sure the outputs fall to a safe state on reset. The Pi can then send requests like "select antenna 3" or "rotate to 270" over serial or MQTT, and the microcontroller decides whether to act. On levels, read the rig's CAT documentation before buying a cable. Some radios expose TTL-level serial, some use RS-232 voltage swings, and many modern ones present USB. Wiring 5 V TTL straight into a Pico pin is a quick way to damage the input, so use a level shifter or a resistor divider on the receive line. A MAX3232-style converter is the right part for true RS-232. The USB route avoids level problems, but it brings a long cable that can act as an antenna. For RF ingress, treat every cable leaving the box as a possible antenna. Common-mode chokes on USB cables, short leads inside the enclosure, and a small RC or ferrite bead on each sensor and relay line all help. Use a flyback diode across any relay coil you drive from a transistor or driver array. If the radio and the Pi are on different supplies, a USB isolator on the CAT link can break ground loops that otherwise inject hum or noise. The usual cause of random resets near a transmitter is RF on the supply or I/O lines, not a bad board, so put the ferrite on the cable first and only then suspect the firmware.
  13. For nets and emergency traffic, the priority is to be consistent and unambiguous. Some practical points: Use phonetics for anything that can't be checked from context: names, street names, unusual words, callsigns, and any part of a message that has to be exact. A common pattern is to say the word normally, then spell it: "Kowalczyk, I spell, Kilo Oscar Whiskey Alfa Lima Charlie Zulu Yankee Kilo." For number strings like a phone number or grid square, say the digits one at a time and pause between groups. Many people say "zero" rather than "oh" so that it isn't confused with the letter O. Saying "niner" for 9 is common because "nine" can be confused with "five" in noise, but if you're not sure everyone on the net knows it, normal digits are fine. The full ICAO number words (wun, too, tree, fower, fife, ait) are mostly an aviation habit and are rarely needed in ham nets. For traffic, plain language is generally preferred over 10-codes or other jargon, especially when different agencies and volunteers are on the same channel. Short prowords such as "say again," "break," "priority," "emergency traffic," "copy," and "clear" are fine. Don't use "Roger" as a vague acknowledgment of everything. Repeat back critical items instead, such as addresses and quantities. Prosigns are mainly a CW matter: AR, SK, BT, KN and so on. On voice you replace them with spoken equivalents like "over," "clear," and "stand by." It's worth knowing the CW versions if you handle formal message traffic, because the same structure carries over, for example when a radiogram's check count and spelled words must be read back exactly. In an actual emergency, follow whatever the net control station or served agency has set up. They will tell you the format, so don't improvise a new one mid-net.
  14. On the radio choice itself, I'd start with the network, not the specs. All three give you solid analog FM, which is what most mobile operating still depends on. The digital features only pay off if repeaters near you support them. If your area leans toward D-STAR, the ID-5100A is the logical fit. If System Fusion is common locally, look at the FTM-500D. If you want APRS beaconing and messaging from the same box, the TM-D710G is the one built around that. One caution for cross-band repeat: don't assume it works the same on every one of these. Read the manual section for your exact model and firmware, and test it on a simplex pair first, not through a live repeater. Also be careful with the power wiring advice. People often fuse the radio's own cable and think the job is finished, but if the run to the battery is long, the fuse at the battery end is what protects the wire. Keep that fuse near the source.
  15. If budget is tight, I'd put feedline and bonding ahead of almost any piece of radio hardware. Many "my rig has noise or RFI" problems turn out to be common-mode current on the coax, on USB cables, or on the mains wiring. A proper choke at the shack entry is cheap compared with replacing a radio, and it helps whichever rig you own. A good 13.8 V supply with low ripple is next, because a switcher that radiates hash into a sensitive receiver will undermine even a top-tier TS-890S or IC-7610. For the tuner, I'd separate two goals: making the rig see a safe SWR, and making the antenna system efficient. A tuner solves the first one. If a doublet or a long wire needs a tuner, it's usually better to put the tuner close to the feedpoint, or use ladder line to the shack, than to push a high-SWR coax run through it.
  16. On HF, the antenna and the noise environment usually decide the outcome more than the SDR's noise figure. Below roughly 20 to 30 MHz, external noise (atmospheric, and especially man-made noise from switch-mode supplies, LED lighting and powerline hardware) often sits well above the receiver's own noise. A very sensitive front end does not help you hear a weak signal if the antenna is picking up household noise. What matters is signal-to-noise ratio, plus enough dynamic range that strong broadcasters do not generate spurs. For an RTL-SDR, the options are direct sampling or an upconverter. Direct sampling on dongles that support it (the RTL-SDR Blog V3 uses the Q branch) is simple and cheap, but there is no proper preselection, so you get aliasing and the 8-bit converter must handle everything from LF through the shortwave broadcast bands. An upconverter mixes HF up to VHF. With a 125 MHz local oscillator, a 7.1 MHz signal appears at 132.1 MHz, and in SDR# or HDSDR you set a frequency offset (shift) so the displayed frequency matches the real one. Look for a low-pass filter ahead of the mixer, a stable oscillator, and good shielding. Cheap converters can add their own spurs and drift. If HF is your main interest, an Airspy HF+ type or an SDRplay RSP with its HF input is designed for the job, with better filtering and a lower chance of strong stations folding into your band. SDR software choices follow the platform: SDR# and HDSDR are common on Windows, SDRuno pairs naturally with SDRplay, and GQRX is a good Linux or macOS option through the osmosdr or Soapy driver layers. CubicSDR is useful when you want a Soapy-based cross-platform viewer that can work with several devices. For panadapter use, feed the SDR from a splitter or from a dedicated receive output or IF tap, never directly from the transmit path. Use a proper TX protection scheme such as a relay or attenuator chain, and make sure there is no DC on the coax from a bias tee into your transceiver. For frequency tracking, CAT control with OmniRig, hamlib or the vendor's own interface lets the SDR follow the radio, which is more reliable than eyeballing the spectrum. Finally, for portable setups, a common-mode choke on the feedline and a few metres of distance from the computer and power supplies can reduce noise more than any software setting.
  17. A way to make the run-versus-S&P decision less of a gut call is to figure out the multiplier value in advance. In a contest where score = QSO points × multipliers, a new multiplier is worth about the total QSO points divided by the current multiplier count. Compare that with what the same minutes of running would produce. In the first few hours the multiplier side tends to win. Later in the contest the same trip off the run frequency has to net you several multipliers to be worth it. One thing I'd add on N1MM: set up the bandmap and multiplier window so that needed stations stand out visually. If you have to read each callsign to decide whether it's worth chasing, you'll end up chasing the wrong ones. It also helps to decide beforehand which multipliers are worth a call on a pile-up and which aren't. A rare multiplier with a big pile-up may cost you more minutes than it pays back, while a moderate one with no queue is usually a fast gain. For band changes, I'd think of them as scheduled windows, not responses to a dip. Rate dips for lots of reasons, including a neighboring station, a short fade, or you've simply worked everyone who will answer. Look at the other bands before you decide, since a 10-minute lull on one band doesn't always mean the band is over.
  18. On kit, I'd resist buying a lot before you've done a couple of outings. A basic HF package is a QRP rig, a resonant wire antenna, and a small battery, and it works well if you have enough height for the wire. The common failure is not the radio but the feedline, connectors, or mast guying. A short length of spare coax or a spare connector adapter is cheap insurance. For VHF versus HF, remember that 2 m FM is limited by line of sight and who is listening. If nobody answers on FM, switching to a wire on 40 m or 20 m may be what gets you qualified. Whichever you choose, keep your frequency in the spot updated if you move, and pack up before the weather or daylight forces you to. For safety, also confirm access rules and any seasonal closures for your summit before you go, since those aren't always obvious from the database entry.
  19. Your order is right. Here are the details on each point. FRN: It's a free ID you get by registering in the FCC's CORES system. Do it before the session, because the VE team needs it to file your application, and registering at the table slows everyone down. Use your legal name exactly as it appears on your photo ID, and use an email address you'll keep, since the FCC sends license notices there. Never pay anyone for an FRN. If a site asks for money to create one, you're in the wrong place. ULS: This is the Universal Licensing System, the FCC database where your license record lives. After you pass, the VE team submits your paperwork through their coordinating organization (the VEC), and your call sign appears in ULS. That usually takes a few business days, though it varies. You can search by name or FRN. The electronic grant is your official license, and a paper copy is optional. Finding a session: The ARRL has an exam session search, and HamStudy has a session finder. Many local clubs also post their own dates. Some VE teams run remote exams over video, which is useful if no in-person session is nearby. Read each announcement for whether you need to pre-register, what the fee is, and what to bring. Fees are set by the team or VEC, so they differ between sessions. Also check whether the FCC itself is charging any application fee at the time you test, because that policy has been under discussion. Don't rely on a forum post, including this one, for a current number. What to bring: Photo ID, your FRN, a pen or pencil, and a simple calculator if you want one, since a few questions involve basic math. If you're upgrading, bring any credit certificates (CSCEs) too.
  20. Don't skip Part 97 just because it looks like the easy reading section. The questions are often about precise wording: who is the control operator, what counts as automatic versus remote control, what rules apply to spurious emissions, and when a station must identify. If you only skim it, it's easy to lose a handful of points there. Read the rule behind each question you miss instead of memorizing the answer letter. On the radio-design side, receiver specs are worth a little extra attention. Dynamic range, third-order intercept, noise figure, sensitivity and image rejection all describe different things, and the pool likes asking which one matters for a given problem, such as strong nearby signals overloading a front end. Think of it as a story: a strong signal causes intermodulation, so you care about the intercept point and dynamic range. For antennas, keep dBi and dBd straight (dBi is about 2.15 dB higher than dBd for the same antenna). Also know what changes with a Yagi when you adjust element spacing or length, and the basics of matching systems like gamma and beta matches. As for the privileges, the Extra gets you operating privileges on all amateur frequencies and all modes the rules allow. The practical difference from General is the small slices of the bands that General licensees can't use, such as some segments near the bottom of the HF bands and some phone segments. Whether that's worth it depends on how you operate, but if you like chasing DX or working in busy contest conditions, those extra segments can matter. Check the current band plan and FCC rules chart rather than relying on a forum summary, since the details can change.
  21. On linked systems, the biggest habit to build is leaving a gap between transmissions. Wait a second or two after the other station finishes before you key up. That gives anyone who wants to break in a chance, and it gives the link time to drop and reset. It also helps to key up, wait for the repeater to come up, and then start speaking. Otherwise the first word or two get cut off, and the fix is not to talk louder. Keep each transmission short, and remember the audience may be bigger than it sounds. A linked repeater can reach other cities or countries, and some nodes may be running a net or a scheduled event. If the system has a stated purpose, such as a regional net, an emergency-communications resource or a social chat, follow that. If you're just testing, say your callsign and that you're checking in. Saying "test" and then hanging on the key does nothing useful. You don't need to call CQ on a repeater either. Giving your callsign and saying you're listening is enough, and so is a general call like "anyone around for a chat". Identification rules depend on your country and licence, so check your own regulator's requirements. In many places you must identify at intervals and at the end of a contact. Also, a repeater's timeout timer is not a target. If you keep hitting it, you're probably talking too long. Finally, if the owner or control operator posts rules about courtesy tones, hang time, link behaviour or open versus closed access, follow those even if they differ from what you're used to elsewhere.
  22. I'd add that the 'stay or move' decision gets harder with SO2R, because a poor run frequency can look acceptable when radio 2 is producing multipliers. The total score might still go up, but the run is underperforming. It's worth checking the run-only rate occasionally. If it has fallen below what a different frequency or band might give, fix that first, because SO2R amplifies a good run and masks a weak one. On the question about exchange length: longer exchanges make SO2R harder, because the time you are committed on one radio is larger relative to the gap on the other. In a short-exchange contest, a quick call and number on radio 2 fits easily between CQs. With a long or irregular exchange, it's harder to fit anything in, and the gains drop. That doesn't make SO2R useless there, but it shifts the focus toward fewer, more selective radio 2 contacts, usually multipliers. The software side deserves practice, too. Keyboard focus, which radio is transmitting, which radio's audio is in which ear, and what the function keys send all need to be predictable. A mistaken transmit on the wrong radio costs more than a missed QSO. Setting up a short practice session with recorded or simulated contest traffic is a better way to build habits than learning the layout live in a contest.
  23. Students at Pinecrest Academy of Northern Nevada in Sparks, NV are scheduled to have an educational amateur radio contact with the ISS, using a telebridge via IK1SLD. The scheduled crewmember is Luke Delaney KJ5PPF. Downlink signals from the ISS should be audible on 145.800 MHz narrowband FM within the ISS footprint. The conversation will be in English and receive-only. A livestream is available on the school's YouTube channel, @pinecrestnnvSS.Location: Pinecrest Academy of Northern Nevada, 1150 Silent Sparrow Dr., Sparks, NV 89441, USA. The ISS Fan Club announcement gives only Sparks, NV, and the street address comes from the school's own site. The contact runs as a telebridge via IK1SLD, with a livestream on YouTube. Organizer: ARISS (Amateur Radio on the International Space Station), with Pinecrest Academy of Northern Nevada as host school. The announcement is published by ISS Fan Club. Source: Event information

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.