Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

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

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

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

Admin_Lee

Administrators
  • Joined

  • Last visited

Everything posted by Admin_Lee

  1. One thing worth adding about the monitor function: it is useful, but know what your rig is feeding it. On some radios the monitor takes audio before the processor, and on others it is tapped after it. If you tune the sound in your headphones without knowing which, you may be judging a signal that is not what goes out on the air. Wear headphones so the monitor does not feed back into the mic, and compare against a recording, a remote SDR or an on-air report when you can. Microphone technique matters as much as any menu. Keep a consistent distance from the mic, and use a pop filter or foam windscreen to tame plosives. Be aware of proximity effect: close up, a directional mic boosts the low end, so an EQ low cut that sounds right at one distance may sound thin at another. A stable position, usually a few inches off-axis, gives a more predictable signal than constant EQ changes. Also reduce room reflections and fan noise before turning up the processor, because compression will amplify them.
  2. On the vertical question, the honest answer is "it depends on the radials." A quarter-wave vertical over a poor ground system can lose a large share of its power as heat in the soil. That loss shows up as a nice, low SWR because the ground resistance is added to the feedpoint resistance, so the SWR actually improves when the antenna gets less efficient. There are two ways to deal with that. One is many ground-level radials, on the order of dozens if you want the loss low, buried or laid on the surface. The other is an elevated system, where a few resonant radials a few feet above ground (four is common, more is better) can do well because the fields are not heavily coupled into lossy soil. Elevated radials need to be cut for each band, which means a multiband vertical gets complicated fast. That is why people use a trap vertical or a vertical with a tuner and a loaded radial set, and accept some compromises. For HOA use, the vertical has a good property: it can be thin, and if it is a pole or a flagpole it is often visually accepted. If you can fit a short vertical dipole or a vertical with a feed-line choke, it will also be easy to move. Its downside is that it is vertically polarized and tends to pick up local noise more than a horizontal wire, especially in a suburban setting with a lot of switching power supplies. An inverted V is a very good compromise on a lot like this. Put the apex as high as you can, with an included angle of about 90 to 120 degrees. The resonant frequency will drop compared with a flat dipole, so cut it a little long and trim. The impedance near the feedpoint tends to be close to 50 ohms for a wide angle, so a 1:1 current choke and coax are enough on its design band. Remember that the ends are low and carry high voltage, so keep them out of reach. Finally, a magnetic loop belongs in this thread as a last-resort option. Small loops are narrow-band and need retuning when you move more than a few kHz, and their efficiency depends heavily on the quality of the conductor, the capacitor and every joint. On 40 m and below, a small loop can be very inefficient, though it can be quiet on receive and fit where nothing else will. For 20 m and up it becomes much more attractive. If you can hang a wire, the wire will usually beat the loop on 40 m and 80 m.
  3. For net control, the best ones are predictable. They open with the same preamble every time: the net's name, its purpose, and who may check in. They run the roll call in a clear order and repeat what they heard before moving on. Good net control also asks for breaks and emergency or priority traffic first, handles it, then goes back to the list. If the band is noisy or the signal is weak, a relay station can help, and the net control can ask for one by name. For special event stations, keep a simple log of your own. Write down the call sign, date, UTC time, band, mode and the exchange you received. That helps when a certificate requires proof, a QSL request needs details, or you want to check the event rules against what you actually worked. Many events have a deadline for requesting certificates, so check the event page rather than assuming it's open-ended. Also check whether the event uses a log upload service, a direct request, or both. If you're working a pileup, the usual technique is to listen for how the operator is handling it. Are they taking numbers by call area, working by suffix, or just taking whoever is loudest? Call once your pattern is clear, and give your call sign exactly. A good habit is to send your call, wait, and only repeat if you aren't acknowledged. That works better than hammering the frequency.
  4. I'd also think about how the programs treat the same QSO differently, because that is what trips people up when they use one log for everything. A contact with an island station on a spare band could be a new band-entity for the Challenge, a new reference for IOTA, a new prefix for WPX and a new CQ zone for the Marathon, or none of those. Filtering by program is easier if your logging software stores entity, CQ zone, IOTA reference, and POTA or SOTA references as separate fields instead of free text in the comment. For POTA and SOTA, the key difference is that nobody checks a QSL card. Credit depends on the activator's upload and on meeting the activation threshold. It is worth confirming the threshold and any logging rules on the program's own site, because they are updated separately from the DX award rules. I wouldn't carry assumptions from one program into another. A paper QSL that is good for DXCC does nothing for a POTA hunter award, and the reverse is also true. On paper cards: it generally makes sense when the station doesn't use LoTW or when the entity is rare enough that you don't want to depend on an upload that may never happen. Check the current card-checking and submission rules first, since the process has changed over the years.
  5. One point on the paper side that's easy to miss: the instructions on the QRZ page, the Club Log OQRS page, or the manager's site beat any general rule of thumb. Some operators say "no green stamps," some only take bureau, some want a specific number of dollars, and some only handle cards through OQRS. Following the stated rules makes a reply far more likely. For a direct envelope, keep it plain and simple: your card (or cards, filled out if the operator asks you to), a return envelope with their address already printed or written clearly, and the postage they ask for. If you're sending several cards to the same manager, check whether they want one request per envelope, and don't assume. Also, if you're planning to use any card as proof for an award, confirm that your card shows the details the award rules require, such as both call signs, date and time, band, and mode. On design, I'd err on the plain side. A clean layout with a big, easy-to-read QSO box is more useful in the long run than a busy design, especially if the card gets crumpled in bureau sorting.
  6. On the HT-plus-Arrow question: it is a very cheap way to find out whether you enjoy this, but the main limit is half-duplex. If your radio can't transmit and receive at the same time, you won't hear yourself on the downlink. That makes it harder to confirm you are getting into the satellite, and it makes tuning for Doppler on the fly more awkward. Two radios, or one satellite-capable dual receiver, make FM passes much more comfortable. Headphones help avoid feedback when you can hear your own signal coming back. Before the pass, I'd do three things: confirm the satellite is currently active, load the correct uplink tone, and check max elevation. Low passes under about 10 to 15 degrees are often more frustrating than useful. When elevation is high, the pass is longer and the signal is stronger, so your first contacts are easier. For grids, 4 characters is generally enough on a short FM pass (for example, two letters and two digits). Give the 6-character version if the other station asks or if you are in a rare spot.
  7. Here is a different angle on the on-air side and the equipment. For first QSOs, standard contacts are the best preparation because they are predictable: callsigns, signal report, name, location, rig and power, then 73. If you have practiced those exchanges, you can fill in the blanks from the expected structure even when you miss letters. Practice software that simulates a contest or a ragchew helps, and so does recording a real QSO off the air and copying it later at your own pace. Slow-speed CW nets and special-event stations are good places to start, because many operators will slow down on request. The specific nets, times, and frequencies change, so check current listings from a club or organization instead of relying on old information. In contests, a good plan is to start by listening and copying callsigns without transmitting, then make a few calls once the rhythm of the exchange is familiar. Short, fixed-format exchanges make contests surprisingly friendly for building speed. On keyers, there is no universal setting, but some starting points are reasonable. A sidetone between about 500 and 700 Hz is comfortable for most people, and matching it to the pitch you listen to in the receiver reduces fatigue. Keep standard spacing, with a dah three times the length of a dit and normal weight, before experimenting. The paddle gap should be small but not so small that you get accidental double contacts, and the tension should let you rest your fingers without the paddle triggering. For mode, iambic A and B differ mainly in whether a final element is added when you release both paddles. Try both and keep the one that gives you fewer extra dits. If your sending is cleaner than your copy, that is normal, but listen to recordings of yourself because sloppy spacing is hard to hear while you are sending. As for software decoders, they are fine for checking an answer after you have tried to copy, or for confirming a callsign you are unsure of. The problem is using them in real time. They struggle with fading, noise, and irregular timing, and watching the screen stops you from training your ear. A good compromise is to copy first and look afterward. Software also cannot help you in a pileup or on a weak band, which is where ear-trained recognition pays off.
  8. I'd put weather ahead of the gear discussion, because it's the failure you can't fix with a spare. A rough decision rule is to settle your turn-around criteria before you leave the trailhead, including a time and a sky condition, and stick to them. Towering cumulus building, a darkening sky, a sudden wind shift or distant thunder are reasons to pack the antenna and go down. A wire and a fiberglass pole don't make you safe from lightning, and a summit is the worst place to find that out. The common rule of thumb is that if you can hear thunder, you are close enough to be at risk, but check a reliable source for current guidance. For park operating the risk is lower, but tents, picnic shelters and cars each carry different tradeoffs, and a pole at a picnic table is still the tallest object around. Keep the antenna down when a storm is close, and keep cables and operator away from the feedpoint if you can. Back to the kit: a rain cover for the radio and a zip bag for the logbook cost almost nothing and prevent most wet-weather headaches. Cold is the other quiet problem. Batteries lose usable capacity in the cold, so keep the pack inside a jacket until you need it, and don't count on charging a LiFePO4 cell below freezing unless the pack is designed for it. Many aren't, so check the manufacturer's notes on low-temperature charging before relying on solar in winter.
  9. On study materials, it comes down to how you learn. The Technician exam (Element 2) is 35 multiple-choice questions drawn from a public pool of a few hundred questions, and the usual passing score is 26 correct. The pool is revised on a multi-year cycle, so check that your book or app covers the pool in effect on your exam date. A used manual from a few years back may be out of date. HamStudy: It's built around the question pool, with flashcard-style review and practice exams. It tracks which questions you keep missing, which makes it good for the last stretch of studying. Pair it with something that explains concepts, or you'll end up memorizing answers without really understanding Ohm's law, band plans or antenna basics. ARRL Ham Radio License Manual: This one is more of a textbook. It explains why things work, which helps if you're new to radio and electronics. Reading a chapter first and then drilling that chapter's questions in an app works well for a lot of people. Many local clubs also run Technician classes if you'd rather study with other people. Test-day habits: Bring a photo ID, your FRN, a couple of pencils or pens, and a basic calculator in case the VE team allows it. They may ask you to clear its memory. Take practice exams until you're passing comfortably, not just barely. Read each question twice, because the wrong answers are often plausible-sounding distractors. Skip and return to anything that stumps you. If you fail, many sessions let you retake it, sometimes for another fee, so ask the team about their policy. After you pass: Check ULS for your call sign. Then program a few local repeaters into a handheld, with offsets and CTCSS tones from a repeater directory. Listen for a while, then join a club net, where new hams are usually welcome. Your first few transmissions will be easier on a net with people who expect new callers.
  10. On the LoTW mismatches, the TQSL station location is the first thing to check. If the DXCC entity, CQ zone or ITU zone in it is wrong, your upload can look fine and still not match, or it can credit the wrong entity. This matters most if you operate from more than one place. Make a separate station location for each one, and for each callsign if you hold more than one. After that, check mode and timing. LoTW matches by mode group (CW, phone, data) rather than exact mode, so a phone QSO logged as a digital mode will not match. The time also has to fall within the allowed tolerance, so a log kept in local time or with a bad clock offset will fail quietly. A QSO that is unmatched after a few weeks is usually worth checking against the other station's log if you can see it. For deleted entities, I'd keep a separate view or report in your logging program that flags which entities are current and which are deleted. DXCC credit depends on the entity as it existed at the date of the QSO. The Honor Roll question is a separate thing, since it looks only at current entities. A QSO with a deleted entity is not wasted for the basic award, but it won't move you toward Honor Roll.
  11. I'd do concepts first for the math and theory sections and use repetition for the rules sections. The calculation questions look intimidating, but they come in a small number of patterns. Ohm's law is E = I × R. Power is P = I × E. For wavelength in meters, divide 300 by the frequency in MHz, which is why 146 MHz is roughly the 2 meter band. If you can rearrange those three relationships, you'll cover a lot of the electrical principles questions. Writing the formula triangle out by hand a few times is worth the time. The rules section is where rote recall pays off. Know the privileges: Technicians have all amateur modes on frequencies above 30 MHz, plus limited HF access (some CW segments, and phone and data on parts of 10 meters). Know the license term (10 years) and the grace period after expiration, during which you can renew but cannot transmit. Know the ID requirement: give your call sign at the end of a communication and at least every 10 minutes during it. Those facts come up as straightforward questions, so flash cards are good for them. On readiness, I'd treat a few consecutive practice scores in the low 80s or better as a decent buffer, since the real pass line is 74%. But the more useful check is to find the subelement where you keep missing questions and fix that one, rather than only looking at the overall score.
  12. Good framework. I would add one thing to the net control point: write your net script down and keep it in the same binder as your frequency plan. When you are tired or the room is noisy, a script saves you from forgetting to ask for emergency or priority traffic first. A simple order helps: opening, emergency traffic call, check-ins by group, announcements, then traffic. Also practice with a mixed-skill group, because a net with only experienced operators hides a lot of weaknesses. On forms, it is worth asking your served agency early what they actually use. Some use ICS-213 for everything, others have their own message sheet, and a few just want a phone call relayed. If you show up with the wrong form, you lose time at exactly the wrong moment.
  13. On 2 m, I'd put polarization management ahead of an extra Yagi, because a lot of lost minutes come from mismatch. Faraday rotation changes the polarization angle of the returning signal, sometimes over tens of minutes, and a purely linear station can fade deeply when the two ends are crossed. There is also spatial polarization, a geometric offset between two stations in different places that has nothing to do with the ionosphere. Fixes include a rotatable feed or boom, switchable horizontal and vertical sets, or a crossed array with a phasing/switching box. Even simple H/V switching is a big help. Libration fading is a different problem. It is the rapid flutter in amplitude from the Moon's apparent motion, and it gets faster with frequency. A weak signal that comes and goes at that rate is exactly what averaging in Q65 and deep decoding are designed for. If decodes are patchy, check pointing and polarization before blaming the mode.
  14. For most builders the first extra instrument worth buying is a way to see the spectrum, not a better scope. A scope tells you the waveform looks bad, but it will not tell you whether the second harmonic is 25 dB or 45 dB down. Many amateur regulators expect spurious emissions to be suppressed by something like 40 dB or more below the fundamental, depending on power and band, so check the actual rule in your own country rather than trusting a forum number. A tinySA or similar inexpensive analyzer with a 20 dB attenuator on the input makes that measurement possible. Remember that those cheap analyzers can have their own internal spurs, so confirm a suspicious peak by changing the input attenuation. If the spur level changes by the wrong amount, it is probably the analyzer, not your transmitter. An SWR bridge is useful, but it is mostly an antenna tool. On the bench into a dummy load it will show a very low reflected reading, and that tells you little about harmonic content. A bridge also reads misleadingly if the transmitter is putting out harmonics, because a mismatch at harmonic frequencies can make the meter reading odd. I would treat it as a check on the antenna system after the transmitter is already proven clean. One more bench habit that helps: run the transmitter from a supply with a current limit set a little above the expected draw. If a PA transistor goes into self-oscillation or a bias resistor is wrong, the limit gives you a chance to catch it before a part gets hot enough to fail.
  15. Koch and Farnsworth answer different questions, so you can use both together. Farnsworth is about timing: characters are sent at a faster speed, but the gaps between characters and words are stretched so the overall speed is slow. Koch is about the order and pace of learning characters: you start with just two characters sent at a fairly fast character speed, and add a new one only when you can copy the current set accurately. The usual benchmark is around 90% correct. The reason both are popular is that they discourage counting. If characters are sent slowly, with long dahs and long gaps, your brain has time to think "dit dah dit, that's R." That habit has to be unlearned later. When each character goes by as a quick, single rhythm, you learn to hear it as a sound, like a short word, rather than as a pattern to decode. Many people choose a character speed somewhere around 18 to 20 wpm and then adjust the spacing to suit them. On the flashcard question, it's the visual route that causes trouble. Looking at a chart or a card with dots and dashes trains you to recognize something on paper, and that isn't the skill you need on the air. The skill is sound to letter. If you use cards or an app at all, make sure it plays the audio first and shows the answer afterwards. A mnemonic that turns a character into a word can also slow you down, because you end up doing an extra step every time you hear it. For head copy, the standard advice is to get away from writing every letter as soon as you can. At first, writing each character as it arrives is fine and helps you check yourself. As the characters become automatic, try to hold a few in your head and write only whole words, or just listen and don't write at all. You'll be a character or two behind what you're hearing, and that lag is normal. If a character slips by, let it go. Dwelling on it makes you miss the next two. Ear training is mostly repetition at a level where you're getting most of it right, so short, regular sessions of maybe 10 to 20 minutes tend to work better than one long weekend marathon.
  16. On the sending side, start with the key type and what it forces you to do. A straight key gives you full control over timing, which is good for learning rhythm and bad for fatigue at higher speeds. A single-lever or dual-lever paddle with an electronic keyer makes the elements for you, so your spacing tends to be more consistent, but the keyer will faithfully send whatever sloppy timing you feed it. Iambic keying means that squeezing both paddles alternates dits and dahs. In Mode B, if you release the squeeze during an element, the keyer sends one more opposite element. In Mode A it stops when you release. Many people who learned on one mode find the other produces odd extra dits or missing ones, so check which mode your keyer is set to before blaming your hands. Some keyers also offer Ultimatic or bug-style modes. It's worth trying them, but pick one and stay with it long enough to build muscle memory. Paddle adjustments matter more than people expect. Contact spacing that is too wide makes you slow and heavy-handed, and too narrow gives accidental doubles. Tension should be light enough that you aren't fighting the spring but firm enough that your hand can rest without triggering. If you buy a well-regarded paddle from N3ZN or Vibroplex, you still need to set it to your hand. Check current availability and specs from the makers, since I don't want to quote anything that has changed. A bug is a semi-automatic key. The vibrating pendulum makes dits automatically, and you make dahs by hand. It has a distinctive swing that many operators enjoy, but it takes practice and careful weight and spring adjustment. It's a nice thing to learn, not a shortcut to speed. For QSK, full break-in lets you hear between elements, so you can tell when someone is trying to break you. It depends on fast transmit-receive switching in the rig, and if you run an amplifier, it has to keep up as well. Semi break-in with a hang time is quieter on the relays and fine for most casual operating. Use whichever mode doesn't chop off your first dit or clip the end of your last character. Finally, record yourself. Listening to your own sending back is the quickest way to catch weight problems, uneven character spacing and word gaps that are too short.
  17. My rule of thumb is to split the question into "what do I operate" and "what do I enjoy owning." Those can overlap, but they don't have to. A modern transceiver with good filtering makes sense as the daily driver if you chase DX or contest, because crowded bands punish weak receivers. A vintage rig can still be the one you fire up for a relaxed AM net or a casual SSB chat. One thing people sometimes overlook with older transceivers is how they behave next to a modern station. Drift, no built-in noise blanker worth the name, and limited filter options are all manageable, but they change how you operate. It's less about better or worse and more about adjusting your habits. If you go in expecting that, the old radio is much more fun.
  18. Adding to the math and equipment side, because that is where people tend to either overstudy or skip it. The General pool does not require advanced math. You need Ohm's law (E = I × R), power (P = E × I, and combinations such as P = I² × R), basic series and parallel resistance, and a feel for reactance and resonance. Learn which direction each goes: inductive reactance rises with frequency, capacitive reactance falls with frequency. At resonance, inductive and capacitive reactance cancel. SWR questions are mostly conceptual: a mismatch between the feed line and antenna impedance causes reflected power, and a tuner or matching network at the radio mostly protects the transmitter rather than fixing the antenna itself. Be able to explain why a balun or choke is used with a dipole on coax. For antennas, know the half-wave dipole length formula (about 468 divided by the frequency in MHz gives the length in feet). Practice a few calculations, since the pool tends to ask for them. Learn the difference between horizontal and vertical polarization, the idea of takeoff angle for DX versus NVIS, and what end-fed, off-center-fed and loop antennas are good for. On digital modes, the exam is about identification and practice rather than operating skill. Know that FT8 is a weak-signal mode with timed transmit slots (so accurate computer time matters), that PSK31 and RTTY are narrow-bandwidth keyboard modes, and that digital activity clusters in the CW/data portions of each band. Check the current pool and rules for the details of bandwidth and baud rate limits, since regulations here have changed over time. On vanity calls: a General can apply for one, but the shortest sequential formats are reserved for higher classes, so check the FCC's call sign groups to see what your license class is eligible for. Upgrading does not require a new call sign. Your existing call stays on the license unless you choose to change it. Before test day, read the current question pool's effective dates, because pools are replaced on a multi-year cycle and study guides can lag behind.
  19. On the direct conversion side, I'd split the checklist into audio first, RF second. Get the audio amplifier working before the mixer goes in: a finger touched to the input should produce hum, and the gain should be stable without motorboating. Many DC receivers go wrong because the supply isn't decoupled enough between the high-gain audio stages and the LO, and a bit of extra capacitance and a series resistor on the supply line fixes a lot. Then bring in the product detector and the VFO. Common problems are LO leakage radiating from the antenna, AM broadcast breakthrough because there is no front-end filter, and hum or microphonics caused by a drifting or poorly shielded VFO. A bandpass filter at the input and a bit of buffering after the oscillator help a lot. If it is a single-signal build, check opposite-sideband rejection with a signal generator, or with a nearby transmitter into a dummy load, by tuning on each side of zero beat and comparing the levels. For the BITX/uBITX crowd, the same discipline applies. Don't rely on the factory output filters being correct just because the board is assembled. Check the output on a scope and an analyzer on each band, and be cautious about running it at its highest drive level into a real antenna until you've seen the spectrum.
  20. The biggest time saver is treating your own log as the master record and every award site as a downstream check. Export ADIF periodically and keep the original fields intact: station callsign, band, mode, UTC date and time, and the DXCC entity if your logger fills it in. When something is missing in LoTW, the cause is usually in one of those fields. The station callsign field matters if you operate from more than one location or under different calls. LoTW ties a QSO to a specific callsign certificate and location, so a log uploaded under the wrong location can make a valid contact look like a mismatch. The same goes for grid squares and zones on portable operation. Set the right station location before you sign and upload, not afterward. Mode is the other common trap. LoTW groups modes for matching, so a digital contact logged under a different digital mode label generally still matches, but a phone QSO logged as CW will not. Cleaning that up in the log before uploading is much easier than untangling it later.
  21. The step I'd underline is measuring the supply at the rig during transmit. A DMM on the supply terminals can look fine while a poor DC lead or a tired inline fuse holder drops enough voltage to make the rig misbehave. Measure at the radio's own connector while someone keys it into a dummy load, and the problem often shows up immediately. On the protection faults, it's worth separating "the rig is protecting itself correctly from a real fault" from "the sensing circuit is lying." A dummy load check is the fast way to tell. If the reflected-power reading is not zero into a good dummy load, look at the detector diodes and the bridge balance before suspecting the finals. If SWR reads fine but power output collapses, then the fault is probably in the drive, bias, or power-control path rather than the sensing. For blown finals, one extra caution: in-circuit resistance checks on a final transistor can mislead you because of the low-impedance windings and bias parts around it. A dead short is informative. A mildly low reading often isn't. Check the bias components and the driver stage before you fit a new pair, or you may just end up buying another pair.
  22. The TCXO point needs one caution: a better reference only helps if the radio is calibrated against something reliable afterward. Dropping a TCXO into an older HF or VHF rig and skipping the calibration can leave you with a more stable error. A frequency counter, a known WWV or GPS-disciplined reference, or a well-characterized signal can all serve. Check against a second source if you can. On filters, I'd add that adding a filter often moves the problem. A narrow roofing or IF filter helps with adjacent-channel signals but does nothing for front-end overload from a strong broadband signal. If a handheld gets swamped near a broadcast tower, an external notch or bandpass filter on the antenna port is likelier to help than anything inside the radio. If the problem comes and goes with the antenna or location, suspect overload before you suspect the receiver's selectivity.
  23. Two things belong on the checklist that the post only touched: P2P and forms. P2P (peer-to-peer) sessions connect station to station with no gateway and no internet. One station must be listening in a P2P session type for the same mode (packet, VARA, ARDOP or Pactor) while the other initiates the connection, and then queued messages move in both directions. This is the mode that still works when the internet is down and no gateway is reachable, for example between a served agency's shelter and an EOC. It's also good for practice because two operators can test audio and settings without depending on propagation to a remote gateway. The related Radio-only option keeps messages on radio paths rather than letting them out onto the internet. It's a message-handling choice for sensitive or isolated scenarios, so read the current Winlink documentation on how it's configured before relying on it. For forms, Winlink Express includes a library of templates, and ICS-213 General Message is the one most emergency groups practice first. The form is filled out in a viewer, and the data travels as a small attachment, so it stays compact over HF. The receiving operator sees it properly only if their Winlink Express has the matching form viewer, so test that with the agency or recipient station before an event. A recipient reading through a plain email client may just see the raw data. Keep the text brief, because every extra paragraph is airtime. For training, Winlink Wednesday is a recurring weekly practice event, and it gives a regular reason to open the program, check passwords and send a test message through a real session. Check the current Winlink Wednesday instructions for how to participate, as formats can change.
  24. My rule of thumb is to put anything with a hard timing or safety requirement on a microcontroller and keep Linux out of that path. A CW keyer or a PTT sequencer should still behave if the Pi is rebooting or an SD card has gone read-only. So the Pico or ESP32 does the keying and relay sequencing, and the Pi just sends it commands over serial or the network. On the PTT side, it's worth adding a hardware timeout so a stuck-high line can't hold the transmitter keyed forever. A simple watchdog or a monostable that must be retriggered will do that. It also means a crashed script doesn't end up with a carrier on the air. For the CAT bridge, rigctld on the Pi is hard to beat if everything on the network can already talk Hamlib. It lets logging software, digital mode software and a rotator or band-decoder app share one serial connection. Just check that the baud rate and CI-V or CAT address settings match the rig, and avoid two programs polling the radio directly at the same time.
  25. For CAT, the rule is one owner per port, and everything else connects through a sharing layer. With a Hamlib rigctld, FLrig or Omni-Rig setup, the logger and WSJT-X both talk to the sharing layer and neither opens the COM port directly. WSJT-X can use Hamlib, and also supports Omni-Rig, DX Lab Commander and HRD as rig control options. N1MM+ can use its own radio interface or Omni-Rig. It is usually easier to pick one method and use it for both than to mix several. Set baud rate, stop bits and handshake to match the radio's menu. If the radio has a built-in USB audio codec, check the Windows sound devices too, because a changed default device or an input level change will stop decodes or push the wrong power into the rig. For FT8 specifically, clock accuracy decides whether you decode or not. Keep the PC clock synced with an NTP tool, and keep the logger's UTC settings consistent, otherwise the time_on values in the log will disagree with what the other station logs. LoTW matches on date and time within a window, so a clock that's several minutes off can cost you confirmations. For WSJT-X in a contest, the UDP route is worth setting up if your logger supports it. N1MM+ and Log4OM both have ways of accepting WSJT-X UDP traffic. This is easy to get wrong with two programs listening on the same port, so check which one is meant to own the UDP port and whether the other needs a different setting or a forwarder. If you instead import wsjtx_log.adi later, keep the file backed up and note the time you started so you don't import the same session twice. Dupe checking depends on the contest rules. Some contests count a station once per band, some once per band and mode group, and a few have special exchanges. Set the contest in N1MM+ before the first QSO and make sure the operating category you choose is what you'll submit in the Cabrillo header. For band maps, spot sources give you a lot of data and little context. A spot is a hint. Filter by band, mode and age, and let the logger flag spots for stations you've already worked on that band, so a stale spot doesn't pull you off frequency. Rotator control from the band map usually works through a rotor program or Hamlib rotctld. The logger needs to know the bearing source, so check that your grid or home coordinates are correct. A wrong grid gives you wrong beam headings even though everything appears to be working. For submission, read the contest's current rules and their log checking instructions rather than relying on memory. In general: use the Cabrillo header fields exactly as the sponsor's log robot expects, check that the category and band lines match what you actually did, confirm your callsign is as you transmitted it, and look at a few QSO: lines before upload. Frequencies in Cabrillo QSO lines are normally in kHz, with the time in UTC. Keep the original log, and watch the deadline, which differs by contest.

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.