Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

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

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

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

Mod_Mike

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Mike

  1. The scope formula is one of the most useful things a builder can have on a card taped above the bench. It is worth adding a caution that a typical x10 probe loads the circuit and has its own ground lead inductance, so on higher bands or at higher power the reading can be a bit off. For a quick check at 40 m or 20 m a short ground spring helps a lot. Always measure across the dummy load, not inside the circuit. One more tip: for a Pixie or Tuna Tin 2, where the output is only a fraction of a watt, a diode-detector RF probe on a multimeter can be a good rough indicator. Treat it as relative, because the diode drop makes low-level readings non-linear. It is great for tuning a pi network for maximum, less great for stating exact watts. On the Pixie specifically, expect lots of transmit-receive interaction. Its receiver is wide open, so don't be shocked if you hear several signals at once. That is the design, not necessarily a fault.
  2. Start with the split between rules and conventions. Part 97 is the law: which frequencies each license class may use, which emission types are allowed in which segments, and the power limits. The ARRL band plan is a voluntary set of recommendations, a gentlemen's agreement that keeps weak-signal CW, SSB, digital and FM from stepping on each other. Breaking Part 97 is a violation. Ignoring the band plan will mostly make you unpopular, though on a crowded band that can matter a lot. For HF privileges, the rough picture for General and Extra is as follows. Check the current FCC chart for exact numbers, because the edges were revised in the past and you don't want to rely on an old table. General has all of 160 m, and on 80 m it has CW/data from 3.525 to 3.600 and phone from 3.800 to 4.000. On 40 m the General CW/data segment is 7.025 to 7.125 and phone starts at 7.175. On 20 m phone starts at 14.225, on 15 m at 21.275, and 10 m phone runs from 28.300 up. Extra gets the full bands, with phone starting at 3.600 on 80 m, 7.125 on 40 m, 14.150 on 20 m and 21.200 on 15 m, plus the very bottom CW slices. The WARC bands (30, 17 and 12 m) are a separate case. They're open to General and above, with no contesting by convention. 30 m is CW and data only and limited to 200 W PEP, while 17 and 12 m split into a CW/data portion and a phone portion. Technicians have no phone on HF except SSB on 10 m (28.300 to 28.500). They also get CW-only slices of 80, 40 and 15 m and CW/data on the bottom of 10 m, with a 200 W PEP limit. From 6 m upward (50 MHz and up), Technicians have essentially the same operating privileges as the higher classes on most bands, which is why VHF/UHF is such a natural home for them. On band edges: remember where your signal actually sits. In LSB the audio extends below the dial frequency, and in USB it extends above. If you're a General on 75 m and set an LSB dial to exactly 3.800, part of your signal is below 3.800 and outside your phone segment. Leave a few kHz of margin: for LSB, tune comfortably above the lower edge, and for USB, comfortably below the upper edge. For example, on 20 m, don't park a USB dial at 14.350 with a 2.8 kHz-wide signal. Rig readouts also drift and can be off a little, so the margin covers that too. On 60 meters, operation is on discrete channels, not a continuous band. Phone is USB only, and CW and certain data modes are also permitted on the channels. It's open to General and above, and the power limit is stated as ERP relative to a half-wave dipole, so antenna gain counts. The channel centers are 5332, 5348, 5358.5, 5373 and 5405 kHz. With a USB radio you tune the dial 1.5 kHz lower: 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5. This is a classic way to get it wrong by 1.5 kHz, so read the rule's wording about channel center versus carrier frequency. Also check whether newer rules have added anything, since there was an international allocation change for a small segment of 5 MHz that national rules may or may not have followed.
  3. To add on linking: the digital modes have an extra layer of settings that analog users do not expect. On DMR, a repeater can have the right frequency and color code, but if your codeplug does not have the correct talkgroup on the right time slot, nobody will hear you, or you may end up on a busy network talkgroup by mistake. Check the repeater's documentation for which talkgroups are static and which are on demand, and do not key up on a wide-area talkgroup just to test. On D-STAR, it matters whether you are using local, routed or reflector traffic, so read the repeater's instructions before you set URCALL, and remember that your callsign must be entered correctly in the radio. For AllStar, EchoLink and IRLP, the same rule applies: ask whether the link is permanent or whether users can connect and disconnect. If users can change connections, do not link to another node or room while others are using the repeater. Announce what you are doing, wait for a gap, and disconnect when you are finished if the system's policy requires it. For a club, a one-page sheet near the repeater listing is probably the single most effective way to explain linking etiquette. It should cover the tone, the linked system, who the trustee is, and what to do for emergencies.
  4. I'll take items 1 to 4. Section numbers are from memory, so confirm them against the current eCFR before printing. Identification is in §97.119. You give your call sign at the end of a communication and at least every 10 minutes while the communication is in progress. You don't need to ID on every over. A tactical call such as 'Net Control' or 'Shelter 2' does not replace your FCC call sign. You can use tactical names, but the real call still has to go out on schedule. Phone IDs go out in English, and you can use the ITU phonetic alphabet to make the call easier to copy. CW and digital IDs go out in the mode in use or in another allowed identification mode. For FT8 and similar modes, the call signs in the exchange are what satisfy the rule. Repeater and auxiliary station identification has its own details, and the repeater ID is the trustee's responsibility. It doesn't excuse you from IDing your own transmissions through it. Third-party traffic is covered in §97.115. A third party is someone other than the two control operators at the ends of the contact. An unlicensed person can speak on the air if a properly licensed control operator is present at the control point and makes sure the rules are followed. The control operator has to be ready to take over the microphone or key and shut things down. The international piece is where people slip. Third-party communications with a foreign station are only allowed when the US has a third-party agreement with that country, or when the third party is themselves eligible to be a control operator. Check the current list of agreement countries. Don't assume that because you can talk to a ham in a country, a non-ham can too. §97.117 separately covers international communications, which must stay on amateur-appropriate content and avoid countries whose administrations have objected. On power, §97.313 says to use the minimum power necessary to carry out the desired communication. The general ceiling is 1500 W PEP. Exceptions to remember include 200 W PEP on 30 meters, 200 W PEP for Technician-class operators on the 10 meter HF segment they can use, and a different, ERP-based limit on 60 meters. Several small allocations have their own limits. Read the whole section for the bands you use rather than trusting the 1500 W headline. For prohibited transmissions, start with §97.113 and the surrounding rules in §97.101. It covers pay for operating, business communications on behalf of an employer, music, obscene or indecent language, false or deceptive signals, broadcasting, and codes meant to obscure meaning. On club nets, a control operator may tell others that amateur equipment is for sale or trade, but not on a regular basis. Regularly selling gear as a business is a different situation. Encryption to hide meaning is not allowed, with narrow exceptions such as certain space station control and remote model craft. Authentication-style methods that don't hide the message content are a different matter, and it's best to ask your coordinator or the FCC rather than guess. Separately, willful or malicious interference is prohibited under §97.101(d).
  5. Message handling deserves as much attention as the radio setup, because the link is the slow part. Keep messages small. Text is cheap, and large attachments can tie up a gateway and your own session for a long time. Winlink compresses traffic, but JPEGs and zip files are already compressed, so they gain little. If an image is truly needed, shrink it first, and consider whether a form or a few lines of text would do the job. For incoming mail from regular internet senders, Winlink has spam controls. Unknown external senders may be rejected, and the usual workaround is to have the sender start the subject line with //WL2K, or to add the sender to your whitelist. Sort that out before you need it. The ICS-213 form, and the other templates in Winlink Express, are filled in locally and sent as structured data attached to the message. The recipient then sees the formatted result, which is more reliable for served-agency traffic than free text. The recipient needs a client that can render the form, so confirm that with the other end ahead of time. Also remember that the form is only a container. A message that is clear, short, and signed with the right names, times, and locations is still what makes it useful. For practice, the weekly Winlink Wednesday routine is a low-pressure way to exercise the whole chain: account, modem, rig control, gateway choice, and form handling. Check the current Winlink Wednesday announcement for the specific instructions, because the details can change and I would rather not guess at them here. Finally, content rules still apply. Amateur-band Winlink traffic must not be encrypted or obscured, and it should stay within the rules for your license and band. The control operator is responsible for each transmission, so look at the session log when something goes wrong before blaming the gateway.
  6. until

    The USS Midway Museum's amateur radio station NI6IW will be on the air to honor veterans and mark the founding of the Continental Marines on November 10, 1775. Operation is on or near 7.250 MHz LSB, 14.320 MHz USB, 14.070 MHz PSK31 and various CW frequencies. The station will also be on PAPA System repeaters in the SoCal area. The ARRL listing gives the same window as 1700Z-2359Z on Nov 14, 2026. QSL cards are available by SASE to the museum's address.Location: USS Midway Museum, 910 N Harbor Drive, San Diego, CA 92101, USA Organizer: USS Midway Museum volunteer radio team (NI6IW), supported by the PAPA System Source: Event information
  7. For Direwolf as a digipeater plus iGate, keep the roles separate in your head. Digipeating is an RF-to-RF function, while iGating moves traffic between RF and APRS-IS. In the config you set the audio device, the channel, MYCALL and the modem speed. Then you add DIGIPEAT rules for what you will repeat, and IGSERVER, IGLOGIN and the filter or transmit settings for the iGate side. Check the Direwolf user guide for the current syntax, because those directives have options that are easy to get subtly wrong. Loop avoidance is mostly about not gating things that already came from the internet. Packets with TCPIP, TCPXX, NOGATE or RFONLY in the path should not be sent to APRS-IS, and the same applies in reverse. IS-to-RF traffic should be limited to messages for stations you have actually heard on RF recently. Gating everything from the internet onto 144.390 is how a local frequency gets clogged. If you transmit anything from the iGate, keep it minimal. Audio level matters more than people expect. Direwolf prints an audio level at decode time. If it is far out of range, either clipping or very weak, the decode rate suffers. Fix that before blaming the antenna. If you have a hardware TNC or a radio's KISS mode, Direwolf can talk to it over KISS, but the sound-card path is usually the simplest to start with. On the third question, when you appear on aprs.fi but can't receive messages, remember what a message is. It is an addressed packet of the form :ADDRESSEE:text{id, with the addressee padded to nine characters, and the sender expects an ack. To reach you via the internet, an iGate near you must have heard you on RF recently, and your radio's callsign-SSID must match exactly. Check the raw packets page on aprs.fi for your call and see whether the beacon arrived via an iGate or only as a direct RF hit. Also confirm that your radio is set to receive messages and is not stuck on a different SSID. For weather and objects: a weather packet uses the underscore symbol with fields such as wind direction, speed and gust, temperature in degrees Fahrenheit, rain, humidity and barometric pressure. Objects are a different thing. They represent something other than the sending station, such as an event, a net location or a storm, and they use a name field fixed at nine characters. They need to be refreshed periodically by the originator, and a killed object is marked with an underscore in place of the asterisk. If you plan to send objects, keep the interval sensible, since every refresh is airtime for everyone else.
  8. Good breakdown. One thing I'd add to the TCXO point: measure first, because a lot of people buy a TCXO to fix a problem that is really a calibration error. If the reference oscillator is simply off by a fixed amount, adjusting it may solve the problem for free. A TCXO is for drift over temperature, warm-up, and aging. If the rig drifts a lot in the first 20 minutes and then settles, a TCXO is the likely fix. If it's a constant offset, calibrate it first. On the legal side, I'd separate three questions: can the radio do it, am I authorized to do it, and is the signal clean when it does it. Menu or jumper access answers only the first. The second depends on your license and any program membership, and the third needs actual measurement. It's easy to modify a rig and assume it's fine because the display shows the right frequency.
  9. On exercises, the most useful ones tend to be those that force the radio side to work with the served agency's actual process instead of a ham-only scenario. For example, have the "shelter" send a resource request that must be turned into a formal message and passed through net control to someone playing the EOC. Then see what breaks: unclear callsigns, messages that need clarification, handwriting nobody can read, or a net that gets saturated when everyone calls at once. It is also worth deciding ahead of time what happens when your primary repeater is down. A plan that goes from repeater to simplex to HF, with named frequencies and who is responsible for relaying, is worth writing down and testing. Keep SKYWARN reporting in mind too: weather spotters and emergency nets can compete for the same frequency, so it helps to agree on how they coordinate when severe weather activates both.
  10. On what changes with the upgrade: a General gets access to portions of every HF amateur band, including 160, 80, 60, 40, 30, 20, 17, 15, 12 and 10 meters. Instead of small CW-only windows, you get meaningful phone and data segments. Some details matter on the exam: Most bands are split into a CW/data section at the bottom and a phone section above it. The 30 meter band is CW and data only, and 60 meters is channelized rather than a continuous band. 160 meters is shared with other services, so power and operating rules matter there. Your best approach is to memorize the pattern first (CW/data low, phone higher), then fill in exact edges from a chart. On the sideband convention, the usual practice is LSB below 10 MHz and USB above, with 60 meters being USB. That is a convention, not a license rule, but it shows up in operating questions and matters on the air. Digital modes are a good place to pick up easy points. Know the difference between modes like RTTY, PSK31, and FT8, the idea of weak-signal modes that depend on accurate computer time and narrow bandwidth, and that digital activity sits in the data portions of the bands. For FT8, it is worth knowing that operators gather around well-known calling frequencies, such as 14.074 MHz USB on 20 meters. For antennas, the half-wave dipole length formula (about 468 divided by the frequency in MHz, giving feet) and the quarter-wave version (about 234 divided by frequency) come up often. Also understand SWR as a measure of match, how feed line loss increases with frequency, and why a balun or choke is used to keep common-mode current off the coax. On vanity calls, your license class determines which call sign groups you can request. A General can apply for Group C (1x3 format) and Group D (2x3) calls if they're available. The shorter 1x2, 2x1, and 2x2 formats are reserved for Extra. Requests go through the FCC's ULS and carry a fee, so check the current amount. Many hams upgrade first, then decide whether they want a different call, since keeping the sequentially issued one is perfectly fine.
  11. The split makes sense, and the main thing is that anything that can cause damage should keep working when Wi-Fi, the Pi or MQTT is down. That puts relays, PTT interlock and rotator end-stops on the Pico, and the network nodes only make requests. On CAT: if the rig has USB, use it and keep it on the Pi. Hamlib is mature and rigctld lets several programs share one rig connection, so logging, digital modes and your own scripts don't fight over the serial port. If you must reach a TTL or CI-V port from a Pico, level-shift it properly. CI-V is an open-collector style bus with pull-up, so the transmit side usually needs a diode or transistor arrangement, and you can't just wire TX and RX together. An RS-232 port needs a real line driver, because RS-232 voltage swings will destroy a 3.3 V pin. For the antenna switch, boot state matters. Some ESP32 pins are strapping pins or float during reset, so a relay can click briefly at power-up. Use pull-down resistors on driver inputs and pick GPIOs with known boot behaviour. Flyback diodes on every relay coil are mandatory, and a separate relay supply with common ground is cleaner than powering coils from the logic regulator. Also decide what 'no power' means: for most setups it should be a defined antenna, or a grounded one if lightning protection is the aim. For the ESP32's ADC, I wouldn't trust it for anything that needs good accuracy. It is nonlinear near the ends of its range, and ADC2 pins conflict with Wi-Fi use on many boards. An ADS1115 over I²C is an easy improvement, although I²C wiring that runs far from the board needs care.
  12. My suggestion for anyone new is to pick two or three events and treat the rest as casual. A common mistake is to try to be competitive in everything and end up exhausted and underprepared. Choose one worldwide event, one domestic exchange-heavy event and one fun, low-pressure event such as a state QSO party, SOTA or Field Day. Before each one, make the logging-software preparation a checklist. Load the right contest module, confirm the exchange fields, test the CAT and keying interface, set up your function-key messages and check your Cabrillo header information such as category and operator. Doing a short practice session in a sprint or a small event helps find problems before the big weekend. On exchange accuracy, in Sweepstakes I would slow down and make sure the precedence, check and section are right rather than rushing. In exchanges like CQ WW's zone, many logs get penalized for busted zones, so confirm zones for stations you work often. Rate matters, but a clean log usually helps more than a few extra hurried QSOs.
  13. I'd start with software and listening only, because it costs nothing and tells you whether your site and expectations are reasonable. Set your location in Gpredict, enter your grid square properly, and update the TLEs. Then watch a handful of passes on the polar plot and note which ones go over about 30 degrees of elevation. Once you have a handheld receiver and an Arrow, try to hear an FM bird's downlink without transmitting. Hearing a pass tells you more about your antenna aiming and your Doppler habits than a transmitted contact would. For linear practice, RS-44 is useful because the passes are long and there is time to figure out what your radio is doing. Listen to CW beacons or SSB signals and tune the downlink until a station sounds natural. The inverting relationship takes a few passes before it becomes automatic. When you do transmit, use the lowest power that gets you a copyable signal. If you can hear your own downlink clearly at modest power, that is the right level.
  14. Adding a few details on the mobile and connector side. The 5/8 wave on a vehicle works best if the ground plane is a reasonable size. On a small roof or on a trunk lid mount, the pattern can tilt and the SWR can be less friendly than on a roof center install. With a quarter-wave, the sensitivity to mount location is smaller, so it's a good choice if you can't mount in the center. If you're making your own cable for an NMO mount, make sure the shield makes proper contact at the mount and that the center conductor isn't shorted when you solder or crimp. Many mounts come with the coax already attached; if you're replacing it, use a mount style that matches your coax size. I'd skip adapters wherever possible. Each extra connector adds a point of loss and a place for water to get in, so a PL-259 to N adapter on the roof is a weaker choice than a single N-type connection built into the cable. For satellite use, the easiest improvement to a handheld setup is a beam with a gain you can point. Keep the handheld's rubber duck for portable use, but when you point a yagi at a pass, you'll need to track the satellite and account for Doppler shift. For FM satellites, that means adjusting the receive and transmit frequencies in steps through the pass. The antenna choice makes less difference if you can't hear the satellite, so work out the pass times and elevation before spending money.
  15. On the EFHW versus linked dipole question, I'd say it depends on how you operate. If you are chasing a quick activation, an EFHW on a pole as a sloper is hard to beat because you can have it up in minutes and start calling. The thing people often overlook is the counterpoise and coax. Even though it's "just a wire," the match can shift depending on how the radiator and feedline run, so a short length of coax with a choke is a good idea. A little SWR checking before you commit to a spot saves time later. For the pole, it's worth checking the collapsed length and the wall thickness of the bottom sections. A longer pole sounds great, but if the lower sections are thin, a gust can bend the whole thing. A shorter, sturdier pole with the wire sloping off a tree or fence post is often more reliable than the tallest one you can find.
  16. Start with the topics where a small number of ideas unlock a lot of questions. Op amps are a good example. Know that an inverting amplifier has gain of minus Rf over Rin, and a non-inverting amplifier has gain of 1 plus Rf over Rin. Then learn the gain-bandwidth product: for a typical voltage-feedback op amp, closed-loop gain times usable bandwidth is roughly constant. If the GBW is 1 MHz and you set the gain to 10, expect about 100 kHz of bandwidth. Slew rate is a separate limit and mostly matters for large signals at higher frequencies. For oscillators, don't just memorize names. Colpitts uses a capacitive divider in the feedback network, Hartley uses a tapped inductor (or two inductors), and Pierce is the crystal-controlled one. Underneath all of them is the same idea: loop gain has to be at least 1, and the feedback has to come back in phase. A question that seems to be about a specific circuit is often just asking whether you can identify that structure. Filters work the same way. Butterworth is maximally flat in the passband, Chebyshev trades passband ripple for a steeper cutoff, and elliptic filters get steeper still by allowing ripple in both the passband and stopband. If you know the tradeoff, you can reason out most of the answer choices. For the Smith chart, learn five facts. The center is the matched point (normalized impedance of 1 + j0). The upper half is inductive reactance and the lower half is capacitive. Moving toward the generator is clockwise. One full trip around the chart is a half wavelength of line. Circles centered on the chart's center represent constant SWR. Most of the pool questions only need that, plus reading r and x values off the chart. Calculators are generally allowed at exam sessions, but it's worth asking the volunteer examiner team beforehand what their policy is, such as whether memory must be cleared or whether programmable models are restricted.
  17. I'd treat it as a funnel. Start with the broad prediction to decide which bands deserve attention at a given hour. Use the space weather numbers as a sanity check, mainly the K index and X-ray flux. Then go to live evidence for the final call. If VOACAP says 15 m should be decent toward a region but WSPR or PSKReporter shows nothing across several cycles, consider whether anyone is actually transmitting or receiving there before concluding the band is dead. One useful habit is comparing in both directions. If your own WSPR signal gets spotted in a region, that confirms one direction. If you can decode stations there, that confirms the other. Propagation is usually reciprocal in principle, but noise level, antenna pattern and power can make the practical result very asymmetric. A noisy receive location can make a path sound worse than the signal strength suggests. For the NCDXF beacons, I find the stepped power levels the most informative part. Hearing the 100 W transmission but not the 10 W one means something very different from hearing all four. That gives you a rough sense of the margin without needing any other tools.
  18. I'd add that exercises usually reveal more than classes do. A simple tabletop or a simulated EOC deployment will quickly show weak points: nobody can find the frequency sheet, the repeater has no backup plan, the message form is unfamiliar, or the net control operator has no way to track who is where. Those are easy to fix once you know about them. For net practice, rotate people through net control and logging roles so the group is not dependent on one or two operators. Practice writing and relaying messages verbatim, including when the message is awkward or has a number you are not sure about, and practice reading it back. Include a no-repeater scenario too, so the group has tried simplex and has an alternate plan on paper. Fancy gear matters less than repeating the basics until they are routine.
  19. For the forums and prizes, I'd say pick one or two talks that are outside your usual comfort zone. Antenna and propagation sessions are popular, but sessions on digital modes, satellite operating, emergency communications, or building a small kit can send you home with a project. If the hamfest has a prize drawing, check the rules, because some require you to be present or hold a ticket, and a few clubs do the drawing at a set time. It's easy to miss it while you're deep in a tailgate row. For clubs that want to make these events useful, a few things work well: a simple project table, such as a soldering practice kit, a tape-measure Yagi, or a Pi-based station demo, a list of upcoming meetings and Field Day plans, and someone on hand who can explain the VE session in plain terms. Newcomers are often more anxious about the test than about the radio side. One more tip: write down who you talked to and what they offered, whether it's an Elmer for a first HF antenna or a local net you should check in on. It's easy to say "I'll follow up" and forget by the time you're home and unloading the car.
  20. I'll take the first four. Treat this as a study guide and check the current text of 47 CFR Part 97 on eCFR before relying on any detail. Station ID (§97.119). You must identify at the end of a communication and at least every 10 minutes during it. You don't have to ID at the start, though many operators do. Each transmitting station is responsible for its own ID. Phone is identified in phone, CW in CW, and data in a data mode. On phone, the ITU phonetic alphabet is the accepted way to use phonetics. On FT8 and similar modes, the callsigns in the exchange normally satisfy the requirement, but you're still responsible for knowing your software is sending your own call. A tactical call or net name is fine only if you also give your FCC call sign at the required times. A repeater or other automatically controlled station has its own ID obligation, separate from the users'. Third-party traffic (§97.115). Generally, a non-licensed person can take part if a control operator is at the control point, monitoring and ready to stop the transmission. If the third party is themselves a licensed amateur who could be the control operator, the rule is more relaxed. International third-party traffic is different: it's allowed only with countries that have a third-party agreement with the US. Check the current list rather than assuming. There are also restrictions on who can be the third party, such as someone whose license was revoked. Also remember that third-party traffic can't turn into business communication. Power (§97.313). The ceiling is 1500 W PEP, and you must use the minimum power necessary to carry out the communication. Exceptions to know: 30 m is limited to 200 W PEP.Technician privileges on certain HF segments are limited to 200 W PEP.60 m has its own effective-radiated-power-based limits.Beacons have a lower limit.Some 70 cm areas near specific government radar sites carry additional restrictions.Pointing out that you're legal at 1500 W doesn't help if 100 W would have done the job. 'Minimum power' is a real rule, not a suggestion. Prohibited transmissions (§97.113, plus §97.101(d) on interference). The main categories: Communications in which you or your employer have a pecuniary interest. There's a narrow carve-out for teachers.Regular business use of the station.Music.Obscene or indecent language.False or deceptive signals.Messages encoded to obscure their meaning, with limited exceptions such as telecommand of certain space stations.Broadcasting, apart from permitted one-way transmissions such as bulletins, beacons and code practice.Occasional on-air notice of personal amateur gear for sale is allowed if it isn't a regular activity. Running a store through your ham station isn't. Also, 'password' protection on a link doesn't equal encryption of the over-the-air message, but you should be careful about anything on the RF side that hides meaning.
  21. On the repeater question, RepeaterBook is a good starting point, but the listings are only as current as the people submitting them. Before programming a radio, I'd check the offset direction, the tone for transmit versus receive, and whether the entry shows an off-air or unknown status. When it matters, confirm with the repeater owner's or club's own page, or with your local frequency coordinator. A repeater that shows up in a database can still be gone, moved or changed to digital-only. On the POTA and SOTA side, the basic etiquette for spotting is to confirm the frequency is clear, ask if it's in use, and then post the spot with accurate details. If you change frequency or mode, update or re-spot. As a hunter, check the comment field for the activator's mode and any split instructions before calling. For study and reference tools, HamStudy is built around the question pools, so it makes sense to start there and let a spaced-repetition approach do the work. HamCalc is better thought of as a reference toolbox for antenna lengths, impedance and similar calculations. It's worth cross-checking its results with a second calculator or a published formula, especially before cutting wire. For phone apps, I'd keep the list short. A repeater directory, a logger, a grid or locator converter and a spots viewer cover most needs. Anything beyond that is worth adding only if you use it regularly.
  22. Start by confirming which question pool your exam session will use. Pools are replaced on a multi-year cycle, and a study guide written for an older pool can include material that isn't tested or miss new questions. The NCVEC publishes the pool, and the volunteer examiner team running your session can tell you which version they'll use. Check the edition on any book, app, or website you pick. The exam is built from sections of the pool, with a set number of questions drawn from each. FCC rules get the largest share, so they deserve proportionally more time than their dry reputation suggests. Electrical principles, components, equipment, and modulation together make up a big block too. Antennas and safety have fewer questions each, but they're usually quick to learn, so they're good places to pick up points. For the math, you rarely need more than a few relationships: Ohm's law: E = I × R. With 12 volts across a 4 ohm resistor, the current is 3 amps. Power: P = E × I. That same circuit dissipates 36 watts. Wavelength in meters is roughly 300 divided by the frequency in MHz. A signal near 146 MHz is about 2 meters, which is where the band name "2 meters" comes from. Knowing this lets you work out many antenna-length and band-name questions instead of memorizing them. You don't need calculus or complex algebra. Rearranging a formula and doing simple arithmetic is enough, and you can use a basic calculator if the VE team allows it, so ask beforehand.
  23. I'd add a caution on the budget end. Cheap radios can be wideband and easy to program onto frequencies you shouldn't use, so limit yourself to your licensed allocations. If you're thinking of GMRS rather than amateur radio, that has its own licensing and equipment rules in the US, so don't assume an amateur HT is automatically legal there. On the IC-705 versus an HT question: they aren't really competitors. A handheld is for quick, grab-and-go local contacts. The IC-705 only makes sense if you want HF on the go, and then you also need to plan for an antenna, a tuner and power. For a first purchase, I'd get a solid dual-band HT, a better antenna, and a spare battery, then decide whether D-STAR or DMR is worth adding once you see what your local community uses.
  24. On safety, I'd put the weather and the turnaround time first, and the radio second. Decide before you leave the car what time you will turn around no matter how many QSOs you have, and leave that time and your route with someone. A summit with three contacts is still a perfectly good day if the sky is turning dark. Antennas make lightning a real consideration. A tall fiberglass pole and a wire on an exposed summit are bad in a storm. If thunder is possible, take the antenna down early or don't go up. Also check for power lines before putting up a pole, and keep the pole well clear of them. Add the usual layers, water, food, a headlamp, a map and compass or offline navigation, and a whistle. Check whether the summit requires permission, whether it is inside a restricted area, and what the rules are for operating there. For logging, write down each contact as you make it: callsign, time in UTC, band and mode, and the other station's summit reference if it is an S2S. It is much easier to type that up at home than to reconstruct it from memory. When you upload, match the summit reference exactly to the database, because a wrong digit or region code is the usual reason a log gets rejected or credited to the wrong summit. For chasers, a simple habit of noting the activator's reference as you work them makes it easy to check your totals toward the Shack Sloth.
  25. That rule is a good foundation. The alphabet most people call NATO is the same one the ITU and ICAO use: 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. The official spellings "Alfa" and "Juliett" exist so that speakers of other languages pronounce them correctly. Saying "Alpha" and "Juliet" on the air is common and rarely causes confusion. The main advantage of the standard set is that it was designed to survive different accents and poor audio. Many operators on a given band will recognize it, which matters most when you are talking to someone whose first language isn't yours. Creative phonetics like "Kilowatt" or "Texas" are widely used and often understood, especially among regulars. The risk is that they can be ambiguous or unfamiliar, so on a weak path or with a non-native listener they are a gamble. Mixing sets within one callsign (for example, standard for the first letters and something improvised for the suffix) is where problems start, so pick one approach per transmission. For callsigns in a pile-up or noisy conditions: give the full callsign phonetically once, clearly, at a steady pace, rather than repeating it five times in a rush. If the other station still gets it wrong, repeat only the part that was wrong, for example "the suffix is Kilo Echo Tango", and then confirm the whole call. Keep the exchange short and give the other station room to answer. Slow, clean, and consistent usually works better than loud and fast. If you are using a different phonetic for a letter that keeps being missed, switch to the standard word for that letter. Many people find that the letters that get confused (B/D/P/T, M/N, F/S) are fixed by using a distinctive standard word. One more habit: say the callsign phonetically, but don't make the phonetics the only way people hear it. On a good path, "W1ABC" said in plain letters is fine, and phonetics only need to appear when conditions or the listener's accent call for them.

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.