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. One thing I'd add on digital: D-STAR and DMR are very different to set up. D-STAR is mostly about registering your callsign with the network and setting up routing for the repeater or hotspot. DMR is about talkgroups, color codes and timeslots, and the codeplug can get big and fiddly. A hotspot at home can be a way to try either mode before committing, but check what the mode covers in your area first. For emergency use, I'd say digital is less of a first priority than analog simplex. Analog FM works with almost any radio, so in a pinch you can talk to a stranger's HT. A digital radio is only helpful if everyone around you has the same mode and the same configuration. The TH-D75 and ID-52A have nice features, but a laminated card with local repeaters, offsets, tones and a few simplex frequencies is worth more than any menu option. I'd also treat the IC-705 as its own decision. It's great for portable HF and VHF/UHF operation, but it's a different category from a radio you clip to a backpack. If you want HF capability, compare it to other portable HF rigs, not to HTs.
  2. For antennas, I'd split the plan into a primary and a fast fallback. The primary might be a 40/80 m inverted V on a fiberglass mast. The fallback should be something one person can deploy in a few minutes, such as an end-fed wire or a vertical with radials, so you can get on the air before the full system is up. For NVIS, height matters less than you'd think. A dipole at 0.1-0.25 wavelength up on a quiet band often performs fine, and it is easier to keep out of the way of people and vehicles. Also separate the radio area from the noise sources physically. Keep the generator, charger and solar controller on one side, the antenna feedlines on the other, and run the coax straight out of the shelter, not parallel to AC and DC cables. If something is noisy, change one thing at a time and write down what you changed. That log is also useful afterward, because a deployment note like "MPPT controller raised the noise floor on 20 m, fixed with ferrites on the PV lead" is exactly what the next team needs. For the shelter, plan for rain, wind and condensation. A tarp or tent with a defined cable entry point, a place for the laptop away from drips, and red or low-level lighting for the operating position all cost very little and prevent a lot of problems on a long night.
  3. The family plan deserves just as much attention as the radio gear. A ham-only plan leaves out the people you most want to hear from. A GMRS or FRS radio in each vehicle or at the neighbor's house can fill the gap, as long as everyone knows the channel and any privacy code settings, and that privacy codes don't actually make a conversation private. Another practical tip is to decide who monitors what and when. If every radio is left on all night, batteries die by morning. A scheduled check-in, with a backup time and a backup channel, works better. Keep messages short: name, location, status, need. If you're serving with a net, practice formal message handling and writing things down, because a clear log is often more useful than a fast reply. Finally, test the weather radio's alert mode and make sure the batteries are fresh. A device that is supposed to wake you for a warning is no use if it has been sitting dead in a drawer.
  4. One thing I'd add on finals: do not apply drive or full voltage after replacing the devices until you've verified the bias circuit. A common mistake is to replace a blown transistor or MOSFET and then power the rig with the bias circuit still faulty, which kills the new part within seconds. Check the bias voltage range, make sure the adjustment pot isn't open or noisy, and check that the voltage actually reaches the gate or base. Use a series lamp or a current-limited supply if you can. Also check the output filter relays, low-pass filter capacitors and inductors, and the antenna changeover relay. A relay with burned contacts can present a bad load, and the finals pay for it. A multimeter diode check will catch a shorted junction, but it can't tell you whether the device has lost gain or that a MOSFET is leaky. The SWR protection circuit might still be perfectly healthy and doing its job. It may be telling you the output filter or the relay is wrong. On manuals, I'd treat the voltage chart and block diagram as the most useful pages. They let you decide where to measure before you open the radio. If there is a service bulletin or known-failure list for that model, read it first, because some models have repeat failures that aren't obvious from the schematic alone.
  5. Digital ham radio can feel like alphabet soup. Many of these modes use the same sound card, the same computer, and sometimes the same radio, but they solve very different problems. Choosing the right one first saves hours of fiddling with settings for a mode that was never going to do what you wanted. This guide groups the common tools by what they are good at, then covers the shared plumbing that makes almost all of them work: audio, timing, rig control, and logging. Start with the goal, not the modeAsk what you are trying to accomplish: Make contacts with weak signals and a modest station: FT8 (or its relatives in the WSJT-X family).Have a slower, keyboard-style conversation with weak-signal tolerance: JS8Call.Share position, weather, or short messages on a map: APRS.Send real email or formatted forms over radio: Winlink.Move data between stations over VHF/UHF links: packet radio.Talk by voice through a digital network: DMR, D-STAR, or System Fusion.See what the bands are doing: an SDR, plus PSK Reporter and the Reverse Beacon Network.FT8 and the WSJT-X familyFT8 uses fixed 15-second transmit/receive cycles and a highly structured, compact message format. That structure is why it can decode signals well below the noise floor, and why it needs accurate clocks. Your computer time should be within about a second of true time, and a network time sync tool or a reliable GPS-based source is worth setting up before you blame anything else. The settings that matter most in WSJT-X: Audio input and output: select the right device for your radio interface, not the computer's built-in microphone.Receive level: aim for a moderate reading on the WSJT-X level meter rather than pinning it at either end.Transmit level: set the output so the radio shows little or no ALC action. A clean, lower-power signal beats a splattery strong one. Overdriven digital signals are wider than they should be and bother neighbors.Rig control: choose CAT, or PTT through a serial line or VOX if that is what your interface supports. CAT lets the software read and set frequency and mode.Split operation: using the rig's split mode or the software's fake-it option helps keep audio tones in a clean part of the passband.If a decode problem persists, check the basics in order: time, audio device, radio mode (typically USB with data options if your radio has them), filters, and then CAT. JS8Call: a different feelJS8Call builds on FT8's modulation but is designed for keyboard-style messaging, directed calls, relay between stations, and heartbeat-style presence. It is slower than FT8 and rewards patience. Setup is similar: accurate time, correct audio, and sensible levels. It suits casual conversation and low-power experimentation. It is not a replacement for a formal emergency communication system, though it can be a useful tool in a larger plan. APRS and packetAPRS runs on AX.25 packet. In North America, the common VHF frequency is 144.390 MHz, using 1200 baud AFSK. Stations send beacons, positions, weather data, and short messages, and digipeaters or internet gateways carry them farther. A basic setup might be a handheld or mobile radio with a tracker, or a software TNC on a computer using the sound card. Beyond APRS, general packet radio lets you build point-to-point links, bulletin boards, and node networks. It is a good place to learn how addressing, retries, and acknowledgments work. Many hams find a Raspberry Pi is a handy small host for these projects, since it can run a software TNC, a digipeater, or a monitoring station in a small, low-power box. Winlink for email over radioWinlink lets you send and receive email-style messages through radio gateways, with a client such as Winlink Express on the computer. It can use several transport methods, including packet, and HF modes like VARA, ARDOP, or Pactor, depending on your hardware. Before you rely on it, practice: Set up your account and confirm the client works over a normal internet connection first.Move to a radio connection and test with a nearby gateway.Learn which gateways are reachable at your location and which bands propagate to them at different times of day.Keep messages short, since bandwidth over radio is limited.The advantage is a familiar email workflow even when the internet is unavailable. The cost is more setup than weak-signal modes. DMR, D-STAR, System Fusion, and hotspotsThese are digital voice systems, and they are not interoperable with each other without a gateway or bridge. Each has its own radios, codec, and network approach. Many people join them using a hotspot, a small personal low-power access point connected to the internet, often built around a Raspberry Pi or similar board with a modem board. When setting one up: Confirm the hotspot's mode and frequency on a clear spot, away from repeater channels you use locally.Align the frequency offset between hotspot and radio. A small error can cause garbled audio or no connection.For DMR, you generally need a registered ID and correct color code and talkgroup settings. For D-STAR and Fusion, the callsign routing and reflector or room settings matter.Keep the hotspot's power low, as it is meant for local coverage.SDR, PSK Reporter, and RBNA software-defined radio gives you a waterfall view of what is actually on the band. That is excellent for diagnosing a weak signal, seeing interference, or checking your own transmitted bandwidth with a second receiver. PSK Reporter and the Reverse Beacon Network collect reception reports from many stations. They answer a simple question: who heard me, and where? If you call CQ on FT8 and nobody answers, a quick look at PSK Reporter tells you whether your signal is being heard. Zero spots from a busy band might point to antenna, power, or timing issues, while a good spread of spots suggests propagation or a crowded frequency. RBN does a similar job for CW and RTTY, which is useful for checking your signal during contests. Logging and rig controlLogging software ties the operating tools together. Log4OM is a general logger with strong support for digital modes and award tracking, and it can receive logged contacts from WSJT-X automatically. N1MM Logger+ is a staple for contesting, with fast entry, rate displays, and integrated radio control. Whatever you choose, think through three things: One source of truth: decide which program holds the master log and which ones only forward contacts.One owner for the CAT port: a serial port can usually be opened by only one program at a time. If two programs fight over it, use a rig control sharing tool or a virtual serial port pair.Consistent frequency and mode data: mismatches here can cause confirmation problems later with online logbooks.Common interface and sound card pitfallsOperating system audio enhancements or auto-gain settings can distort digital tones. Turn them off.System sounds mixed into the transmit audio can cause an accidental noisy transmission. Use a dedicated sound device or mute alerts.Ground loops cause hum and RF feedback into audio. Ferrite chokes and good grounding practice often help.USB devices can change port numbers after a reboot, so recheck COM or device paths when CAT suddenly fails.Baud rate, stop bits, and handshake settings must match between software and radio.A sensible learning orderIf you are building out a digital station, a gradual path works well: begin with FT8 to get audio, time, and CAT working, add a logger, then explore PSK Reporter to evaluate your signal. From there, pick the next mode based on interest, whether messaging with JS8Call, mapping with APRS, email with Winlink, or voice with a hotspot. Each step reuses skills from the last, and the same discipline applies throughout: clean audio, accurate timing, one program per control port, and a log you trust.
  6. On sending and live practice, a few points. If you use iambic paddles, check the squeeze behavior in your keyer. Mode A and mode B differ in whether an extra element is added when you release both paddles, so the same hand movement can send a different character. A slightly tighter contact gap and light tension help reduce accidental doubled dits, but it's personal, so adjust one thing at a time. Slow QSO practice is worth doing even if it feels awkward. A standard exchange (CQ, callsign, RST, name, QTH, 73) is predictable, so you can use context to fill gaps, which is exactly what you'll rely on at 20 wpm. A slow net or a code practice session lets you do this without the pressure of a pileup. Contests are good for callsign copying and for hearing a lot of exchanges quickly, but they can be discouraging early on because the speed is high and the exchanges are rigid. Running Morse Runner or listening to a contest weekend before entering is a way to test the water. Many contests also have slower-speed or low-power categories where beginners won't feel out of place.
  7. I'd add some thoughts on how chasing differs from activating. Chasers do not need to hike, but they do need patience and a sense of timing. SOTAwatch alerts help you plan when to be at the radio. An activator on a cold summit may only have a short window, so being ready when the spot appears gives you the best chance of a quick contact. Listen first, then call with your callsign once, and give a clear exchange when asked. For the awards, the two paths are very different. A Mountain Goat is mostly about legwork and weather, while a Shack Sloth is about steady chasing over a long period, and propagation and a good home antenna do much of the work. Keep an eye on how the database counts chaser points, because the rules on repeat contacts with the same summit are worth reading before you assume anything. One more safety point for activators: a spot saying you are on the summit is not a safety plan. Leave your route and a return time with someone who is not on the radio.
  8. For a quick propagation check, I'd combine three things instead of relying on one number. First, the current solar flux and K-index from NOAA's Space Weather Prediction Center, which tells you the general state of the ionosphere and whether a geomagnetic disturbance is likely to hurt HF. Second, a live spotting map for the band you care about. If FT8 or CW stations are being heard in your target region, that beats any forecast. Third, a beacon or WSPR check on your own antenna, since local noise and your take-off angle can make a big difference. For 6m and sometimes 10m, keep an ear on sporadic E season. It tends to be short-lived and patchy, so a DX cluster or a regional chat group helps if you want to catch it. Don't assume a quiet band means a dead band. Sometimes nobody is calling because nobody has checked. As for conventions, they're useful for things you can't get from a spec sheet, like how a handheld's menu feels, how heavy a portable antenna is when packed, or what the people who've built a project say about its weak points. Take notes and compare against the published specs afterward.
  9. On clubs: a club station license is issued to a named trustee, and the club call goes through a Club Station Call Sign Administrator approved by a VEC, not through the same path as an individual's application. The trustee has to hold their own amateur license and must be at least 18. The trustee is also the one who gets the call if there's a problem with the station. The club still needs to meet the FCC's description of a club, with a name, a defined purpose and its own officers. Check Part 97 for the precise wording of what qualifies. Clubs can pursue vanity calls too, and there are specific provisions about requesting a call tied to a deceased holder, so don't assume the individual rules map one-to-one. Special event calls are a separate thing. They are the 1x1 formats, a K, N or W prefix with a digit and one letter, for short-term operations tied to an event or anniversary. They are coordinated by volunteer organizations, not through the normal vanity filing, and each assignment is short-lived. Whoever is operating still uses their own license privileges, so a special event call doesn't give anyone extra band access. Anyone planning an event station should ask the coordinating organization for current eligibility, timing and reporting expectations. For lookups, the FCC's ULS license search is the authoritative source, because it is the licensing database itself. QRZ-style sites and other third-party directories pull from it or from user submissions, so they can lag or contain stale details. If a record looks wrong, fix it at the source, since the FCC requires you to keep your mailing address current (97.23), and changes are filed through ULS. Changing a call is a different matter from changing an address. Moving doesn't force a new call. If you want the sequential call that matches your new region or your new class after an upgrade, you can request a systematic call sign change through ULS, and the system will assign the next available one. Prefix and suffix talk gets tangled with identification rules. Within the US, adding a portable or mobile designator is optional, but you must still ID every ten minutes and at the end of a communication. Operating abroad is different, because reciprocal arrangements often require a specific prefix or format, so check the host country's rules before packing the HT.
  10. Your chain is correct. On staying receive-only first: yes, that's a sensible way to begin. An RX-only iGate (RF to Internet) already helps coverage, and you can watch Direwolf's log for what you decode before adding any transmit function. Internet-to-RF gating is a separate decision. Well-run iGates only send messages to RF for stations they have recently heard directly on RF, and they don't gate everything, because that would swamp 1200 baud. Gating rules also drop packets with TCPIP, TCPXX, NOGATE or RFONLY in the path, so don't be surprised if some traffic never reaches the internet. For checking your packets on aprs.fi, search for your callsign-SSID and look at the raw packets view. It shows the path and which station (the iGate) injected the frame. If you see your handheld's packet there with a q construct like qAR followed by an iGate callsign, it went over RF and was gated. If nothing shows, check these in order: is the iGate actually connected to APRS-IS (look for a login success in the Direwolf output), is your beacon path reaching a digi or iGate at all, and is the radio on the right frequency with APRS actually enabled? Many people forget that a handheld's APRS band may be set separately from the voice band. One audio detail: level matters more than people expect. If Direwolf's receive audio is clipped or too low, decodes drop badly. It prints audio level hints in its log, so use those to set the sound card input gain before blaming the radio.
  11. I would sort out the RF path before touching code. Start by running the rig into a dummy load. If the glitches vanish, you are dealing with RF getting into the system via the antenna or feedline, not a power supply or firmware fault. Then go back to the antenna and add one change at a time so you can tell which one helped. The usual order is a proper common-mode choke on the coax at the shack entry, ferrites on the USB and CAT cables (several turns through a suitable mix for the band, not a single pass), and then bypassing on the board itself. A 100 nF capacitor plus a small value like 1 nF to ground on each exposed I/O line, with a series resistor, helps a lot on slow signals such as PTT sense or a sensor input. Keep the leads short, because a capacitor with long leads stops working as a bypass at HF/VHF. A grounded metal enclosure also matters more than most people expect. A bare ESP32 dev board in a plastic box with a 1 m sensor lead is nearly an ideal pickup. Feed cables through bulkhead connectors, bond the shield at the entry point, and avoid ground loops from multiple USB connections where possible. For a rotator controller that reads a pot, the ESP32 ADC is also nonlinear and noisy even without RF, so averaging in software or using an external ADC like an ADS1115 is worth doing in any case. With Wi-Fi active on the ESP32, ADC2 pins are not usable, so plan the pin assignment around that.
  12. On the equalizer, I would treat 'flat' as a starting point rather than a rule. Voices differ, and so do microphones. A cut in the low end often helps with a desk mic that picks up table thumps and boomy room sound. A headset mic may already be thin, so extra low-cut could leave the voice sounding tinny. Record a short test with your radio's built-in recorder, if it has one, or listen through a monitor receiver, then adjust one control at a time. It is easy to fix several things at once and not know which change helped. For weak-signal and DX work, I would separate two goals: sounding natural and being easy to copy through noise. For a pileup or poor path, a slightly narrower TX bandwidth with modest compression often works better than a full-range, nicely shaped voice. When conditions are good and you are not competing with others, go back to wider, lower-compression audio. Rather than keeping one profile for everything, store a 'DX' and a 'ragchew' memory if your radio supports it.
  13. I'd go spots first, indices second. Spots tell you whether a path is open right now, and the indices explain why or help you guess what happens next. If the WSPR map shows signals on 20 m into the region you want, it doesn't matter much that the SFI looks mediocre. The reverse also happens. A decent SFI doesn't help if there's a geomagnetic storm or a flare-related blackout. Two caveats on the spot data. First, WSPR and RBN show where stations are active, not just where propagation exists. An empty area on the map can mean nobody is transmitting or listening there. Second, a path that shows at -25 dB in WSPR may be far too weak for SSB. Compare the report with what your mode needs. WSPR decodes signals far below the level at which a voice contact is workable. I'd use VOACAP-type predictions to decide when to be at the radio, and live spots to decide what to do once you're there. For the low bands, also check the sunrise and sunset times at both ends. The gray-line window can be short, and the indices won't tell you when it is.
  14. On the SO2R point, the second radio should be treated as a tool for finding multipliers while the first radio keeps its CQ going, not as a second run position. The simplest way to start is to run on radio 1 and use the CQ repeat gap on radio 2. Set the gap long enough to tune a few spots, call one station, and still get back to the run radio. If the S&P station doesn't answer in a couple of tries, drop it and return to the run frequency. Chasing one stubborn multiplier is one of the quickest ways to lose the rate you were protecting. Hardware matters more than people expect. You need a way to switch headphone audio (one radio in each ear, or a stereo/mono blend), a way to switch the key or keyboard CW and PTT, and some transmit interlock so both radios can't key at the same time. If the radios are on nearby bands, you also need bandpass filtering or stubs, because the transmitter on one radio can overload the receiver on the other. Many stations avoid the problem by keeping the radios on different bands, with the run radio on the better one and the second radio on a band with a lot of open multipliers. In N1MM, the bandmap is the main S&P tool for the second radio. Configure it so needed multipliers are visually distinct from needed QSOs and dupes, and set the spot filters so you aren't scrolling through noise. If you use skimmer spots, be aware that busy contests produce a lot of busted calls. I'd treat a spot as a lead, not a confirmed callsign, and I'd copy the call on the air before logging it.
  15. On mode selection, the key distinction is between modes designed for a fixed exchange and modes designed for conversation. FT8, FT4, WSPR and MSK144 all use synchronized slots and a strict message format. That is why they are so sensitive. PSK31 and RTTY are continuous-stream modes, so there is no sync requirement and no fixed message structure. Fldigi also lets you switch between PSK, RTTY, Olivia, MFSK and Hellschreiber without changing the radio setup, so it is a good tool for trying them on the same audio path. For weak-signal work, WSPR is more of a propagation tool than a QSO mode. Transmit-only beacons and receive-only spotting let you see where your signal is heard without needing a partner. That can tell you whether the antenna is working before you spend time on a contact mode. For VHF and above, Q65 and MSK144 are worth reading about because they target specific propagation mechanisms (EME, tropospheric scatter, meteor scatter), and the settings, such as T/R period and sub-mode, matter much more than for FT8. For Winlink, remember that it is a different workflow. You need a callsign registered with the system, a station configured with the correct gateway, and a decent understanding of how to pick a frequency and listen first to avoid interfering with an existing connection.
  16. I'd add one point about testing. A kit isn't ready just because every item is in the bag. Do a full power-up of the whole setup now and then: charge the batteries, key the radio into a dummy load or a known antenna, check the SWR, run the radio from the battery for a while, and confirm the cables and adapters still fit. Many kit failures come down to a missing adapter, a dead battery or a connector that doesn't match, and none of those show up on a packing list. Also, label things. A strip of tape on each cable with its purpose, plus a laminated sheet inside the lid with frequencies and tones, saves time when you're tired or someone else has to use the kit.
  17. That order is about right. I'd add one thing to the power step: measure the voltage drop across the power cable and connectors while the rig is transmitting, with the DMM probes on each end of the lead. If you see more than a few tenths of a volt lost, fix that before anything else. A rig that works on receive and shuts down or distorts on transmit is very often a voltage drop, not a failed stage. On the dummy load check for SWR faults, I'd also test the load itself with the DMM, since a damaged one gives misleading results. After that, if the protection trips with the dummy load connected, it's worth comparing the forward and reflected detector voltages against the service manual's expected values. Those detectors are simple diode circuits, so a leaky diode or a drifted trimmer is easy to spot once you're measuring at the right points. For finals, I'd stress setting the bias with the drive removed and the supply current-limited. It's tempting to just key up and look at the power meter, but that hides a stage that is oscillating or running far above its idle current. The bias current is a quick health check that tells you the transistor is happy before it has to deliver RF.
  18. A few extra things to check before you go: the boundaries, the park rules, and the logging format. First, boundaries. A WWFF reference can be a different shape from a POTA park even if the names look alike. Some include only part of an area, and some stretch across multiple land units. If you are near an edge, use a map overlay on your phone and make sure your antenna and operating position are inside the reference. Second, rules. State parks, wildlife refuges and nature reserves can differ on things like vehicle access, antenna supports and quiet hours. Read the local rules rather than relying on a general assumption about what is allowed. Third, logs. Before uploading, open the ADIF in a text editor and confirm that MY_SIG and MY_SIG_INFO contain what the target program expects. A small field mistake is the most common reason an upload fails or credit does not appear, and it is much easier to fix before you send than after.
  19. On the plateau, one thing worth checking is whether the problem is copy or recall. If you can recognize characters fine in isolation but fall apart in running text, the issue is usually lag: you are still processing the previous character when the next arrives. Dropping the speed won't fix that. A better test is to copy at a speed where you miss about one in ten characters, and just let the missed ones go. Skipping a character without chasing it is what trains you to stay current with the stream. For callsigns, it helps to work them in two passes. First, pure recognition: letters and numbers at full speed with plenty of spacing. Second, in context: callsign embedded in a short exchange like 'CQ CQ DE' or 'UR RST 599'. The context pass teaches you where callsigns start and end, which is half the battle on a busy band. As for software, a middle path is to copy by ear first and only afterward compare against a decoder or a recording. That gives immediate feedback without letting the screen do your listening for you.
  20. A good rule is to measure before you modify. A lot of mod threads skip that step. If you do not know your baseline, such as the frequency error, the transmit power, the receive sensitivity or the noise floor, you cannot tell whether a change helped or whether you just changed something. With any transmit-side change, the harmonic and spurious output matters as much as the power. A radio's low-pass filtering is designed for its intended bands. If you run it outside that range, the filters may not be doing their job, even if the radio makes plenty of power there. That is a good reason not to treat "it transmits" as proof that it is fine. If you can't check the output with a spectrum analyzer or a service monitor, borrow the use of one or ask a local club. On the MARS/CAP side, it is also worth asking whether you need a mod at all. Some radios can be programmed for authorized channels without opening the case. Your program may also have specific guidance about equipment and how it should be set up, so ask the program before changing anything.
  21. On repeaters, yes, learn the basics now, because they show up in the operating practices questions and they're what you'll actually use with a handheld. Make sure you understand these ideas: A repeater listens on one frequency (its input) and retransmits on another (its output). The difference is the offset, and the offset direction and size depend on the band. A CTCSS (PL) tone is a sub-audible tone your radio sends so the repeater will open its squelch for you, and it's not the same as a voice password. Simplex means talking directly radio to radio on a single frequency, which is good practice when the other station is close enough to hear you. If a repeater isn't needed, it's courteous to move off it so others can use it. Operating practice is also testable: listen before you transmit, identify with your call sign at the required intervals and at the end of communications, keep transmissions short, and know how to make an emergency call. The question pool often tests the reasonable, courteous answer, so common sense plus a read-through of the pool usually works. For RF exposure and safety, ask what changes the risk. Exposure depends on transmitter power, frequency, how close you are to the antenna, how much of the time you're transmitting (duty cycle), and the antenna type. The FCC sets maximum permissible exposure limits and requires you to make sure your station complies. Safety questions generally come down to a few themes: stay clear of power lines when installing antennas, ground and bond your equipment properly, use fuses or breakers correctly, take care around batteries and high-voltage supplies, and don't work on towers without proper precautions. Group the questions by those themes and the pattern becomes easier to remember. For license terms, learn the length of the license term and the grace period for renewal as stated in the current rules and pool, and make sure your information with the FCC is up to date. Test yourself with timed 35-question practice tests near the end of your study. Once you're consistently scoring comfortably above the 26 required, you're probably ready.
  22. On Direwolf, the two things I'd watch for are audio levels and gating rules. If the receive audio is clipped, packets that should decode will be dropped, and then the iGate seems 'quiet' even though the radio is hearing fine. Adjust the receive level until Direwolf's own level readout is healthy, and avoid auto-gain or processing on the sound card. On transmit, a Direwolf iGate that also beacons is a different job from a receive-only iGate. If you don't need RF transmit, a receive-only iGate is simpler and puts less load on the channel. If you do enable RF gating of messages, keep in mind that it should only send messages to stations that were recently heard directly on RF, and that you are responsible for what goes out under your callsign. Also, don't copy a config from a web page without changing the callsign, passcode and coordinates. A duplicate login or wrong position on APRS-IS makes you look like someone else. For handhelds, SmartBeaconing is worth setting up, but check the defaults before you drive. A walking pace and a highway pace need different thresholds. If the radio beacons too often at low speed, raise the slow rate. If it's too sparse on turns, check the turn angle and minimum turn time.
  23. The Telnet-first order is the one worth insisting on, because it separates account problems from RF problems. One addition: after Telnet works, run a Telnet P2P or a local P2P test between two machines before touching a gateway. A gateway can fail for reasons you cannot see, such as the station being busy, a poor path, or a mismatch in bandwidth settings. A P2P link to a second station you control tells you quickly whether your sound card levels, PTT and modem setup are good. On packet, check the TNC side separately. If you use Direwolf or another software TNC with KISS, confirm the KISS port settings and the callsign/SSID before blaming Express. Many packet problems turn out to be a wrong SSID, a digipeater path that does not exist, or audio levels that are too hot for 1200 baud AFSK. Also keep your packet path short. A gateway reached directly is far more reliable than one that needs digipeaters you cannot verify. For the password question: keep the account password and the recovery email details in a documented place the club trustee can reach, and avoid putting passwords into message bodies. The password and secure-login options for gateways and P2P are separate from the Winlink account itself, so write down which one a given station is using.
  24. For special event stations, a few habits can save you a lot of frustration. Search the call sign online before the event so you can see the dates, bands, modes and certificate instructions. Operators may change plans with propagation, so treat the posted schedule as a guide rather than a promise. If the station is working a pileup, listen long enough to learn whether it is working split and how it is picking callers. Then give your call sign once or twice, using phonetics, and wait for a reply. After the contact, confirm the log method. Some stations upload to a log search page, while others rely on the operator's regular QSL route. If your contact doesn't show up within a reasonable time, check your call sign for typos before you write to them. A transposed letter is a common reason for a missing contact. With certificates, read the criteria for each award. Some require a specific number of contacts, a particular band or mode, or contacts on separate days, and these rules are usually printed in the event notice. Treat any rules about commemorative call signs as local, since each country has its own policy. If you plan to operate a special event station yourself, read your national regulator's rules and ask your national society or local coordinators about the application process.
  25. On frequency selection, the usual advice is to follow the DX rather than guess. Many operators tune slowly through their listening range, so the stations they answer drift across it. If you call on a spot and get nothing after a couple of tries, move a little instead of staying put, especially when a crowd is stacked on the same offset. A quiet spot a few hundred hertz away from the main cluster can work better than the loudest part of the pile. On CW it also helps to listen to which frequency the DX operator answers. If he is replying to stations he hears clearly, a matching pitch tends to stand out from a wall of overlapping signals. Timing is where opinions differ. Tailending means starting your call just as the previous QSO is finishing. Done cleanly, it can speed things up, and some operators work fast enough that waiting for a long gap would mean never getting in. Done badly, you step on the last exchange, the previous station has to repeat his report, and you add to the rate loss. A safer version is to wait for the DX to finish his own transmission and then call as he goes back to listening, rather than talking over the end of the QSO. You can also try calling a beat later than the first rush after a 'QRZ?' Big pileups often thin out a little after the opening blast. One caution on etiquette: don't tune up on the DX frequency or inside his listening range. Use a dummy load or a free frequency. And keep your exchange short. If he asks for 'five nine', give the report and the call, nothing more.

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.