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_Dan

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Dan

  1. On tracking schedules: keep everything in UTC and let your calendar app convert it for your local time. Net announcements that say "7 PM Eastern" are the ones that cause confusion twice a year, and some nets keep a fixed local time while others stay on UTC. Whenever a net changes its time, note in your calendar entry where you found the information and when you last checked it. A short note such as "confirmed on net page" saves you from relying on an old schedule. For special event stations, I'd add one more habit: save a copy or screenshot of the station's certificate instructions when you work them. Pages get taken down once the event is over, and the request deadline may be shorter than you expect. Also check whether the certificate requires a specific band or mode, since some give separate awards for different ones.
  2. On voice, a handful of Q signals are common and understood: QTH, QSL, QSO, QSY, QRM, QRN, QRT and QRZ. You will often hear "What's your QTH?" or "I'm going to QSY up a few kilohertz." Others, such as QRS or QRQ, make little sense when speaking, because you can simply say "please speak slower." A good rule is to use a Q code on phone when it is shorter and everyone understands it, and to use plain language when you're talking to someone who might not know it. Clarity matters more than sounding like a veteran. The misuse I see most often is the question-versus-statement distinction. "QRZ" and "QRZ?" are not interchangeable, and "QRL?" is a question while "QRL" is an answer. Another common mix-up is QRP, which people sometimes use to mean "quiet" rather than low power. Also, QRZ.com is a callsign lookup website, which is a different thing from the Q signal, even though people say "I looked you up on QRZ" all the time.
  3. On the first question, I would pick the band based on what you can build and maintain, not on theoretical performance. On 2 m, you can add Yagis one at a time and keep improving. A dish for 23 cm has a lower tolerance for error. If the surface, the feed or the pointing is off, there is not much to tune. Whatever band you pick, receive noise is the first thing to fix. A mast-mounted LNA with a very low noise figure, a relay with sequencing, and short, low-loss feed line matter more than a few extra watts. Even 0.1 dB of loss ahead of the preamp adds noticeable noise. Gain on the antenna side helps both transmit and receive, but the preamp is where cheap improvements usually are. For tracking, you do need accurate azimuth and elevation, and the beamwidth sets how accurate. A large 2 m array has a beamwidth of a few degrees, so it is forgiving. A 3 m dish on 10 GHz is not. Doppler is the other part. Shifts reach several hundred Hz on 2 m and scale up with frequency, so on microwave bands they are in the kHz or tens of kHz range. WSJT-X has Doppler control and an Echo mode so you can measure your own echo. Use it, because a working echo is the best proof that the whole chain is functioning. A calculator such as the VK3UM EME planning tool is useful for estimating what the path should allow before buying anything. Treat the output as a budget, not a promise.
  4. On picking between sequential and vanity: a sequential call is fine unless you have a specific reason to change it. Typical reasons are wanting a shorter call for contesting or DXing, wanting a call that spells something or matches initials, wanting the old call of a family member, or wanting a particular digit after a move. If none of those apply, a vanity filing is just extra work and cost. If you do file, a few habits help. List a lot of choices, ordered from most to least wanted, rather than just two or three. Look up each one in ULS before you list it, including the license status. A call showing as expired may still be in its grace period, and a call of a silent key is held for two years after the death. Also confirm each choice is a format your class allows. The FCC works down your list in order, so a long list with a couple of realistic fallbacks at the bottom beats a short list of one-in-a-hundred picks. Don't assume that a call you saw on-air is the one you'll get. Calls change hands, and you can't see from a quick lookup whether someone is about to renew.
  5. One thing I would add to the leave-the-run rule is to look at the quality of the rate, not just the number. A rate of 90 per hour made up of callers you already have on other bands, or of dupes, is worth less than 70 per hour of new stations. Most logging programs show rate and multiplier counts side by side, so compare the multiplier gain per hour against what you would expect from S&P before you decide to move. On SO2R, the most common mistake is hunting multipliers on the second radio while the first is calling CQ into silence. It can help to set a simple rule: if the run radio has had no answer for a few CQs, check the band map on radio 2, but do not tune around freely. Only go after spots that are already on your needed list. That keeps the second radio productive rather than just busy.
  6. I would start with height and feedline rather than antenna type. A horizontal wire at 25 to 30 ft is about 0.18 to 0.22 wavelength on 40 m, so it radiates mostly at high angles. That is fine for regional contacts and NVIS-style paths, but it is weaker for DX. On 20 m and up the same wire is a higher fraction of a wavelength and the pattern lowers nicely. Moving a dipole from 20 ft to 35 ft often does more than switching between two wire designs. The EFHW is attractive here because you need only one feed point, thin wire and a short run of coax. A 40 m half-wave is roughly 65 to 66 ft after end effect. It resonates on 40, 20, 15 and 10 because those are harmonics, but 30, 17 and 12 m are not, so expect to lean on the tuner there. The transformer presents a few thousand ohms at the end of the wire. On a half-wave that end-point impedance is high, so any loss in the transformer, such as core heating or stray capacitance, shows up directly as lost power. The EFHW also has no real counterpoise except the outside of your coax, so a common-mode choke a short distance from the transformer is not optional. It decides whether the coax shield becomes part of the antenna. A doublet fed with ladder line and a tuner can be more efficient overall because the ladder line is low-loss even at high SWR. A 4:1 current balun or a proper balanced tuner at the shack end keeps the system balanced. Matched-loss figures vary by cable, so check the manufacturer's attenuation tables. RG-58 at 14 MHz loses on the order of 1 dB per 100 ft even when matched, and it gets worse quickly as SWR rises and frequency goes up. Short coax runs are far kinder than long ones.
  7. For a first station I'd keep it simple and separate the problems. First, learn to hear a pass. An HT and an Arrow-style antenna are enough for FM birds, and you can listen for a while before you try to transmit. That tells you where the satellite is, how Doppler sounds, and whether your horizon is clear. Then add a second receiver or a full-duplex rig so you can monitor your own downlink. Not being able to hear yourself is a more common cause of failed attempts than power or antenna choice. On the Doppler question: for FM satellites, doing it by hand is entirely workable if you keep the downlink fixed and step the uplink. Work out a rhythm, such as a small step at acquisition, another near closest approach, and another near loss of signal, and let the 5 kHz channel steps help you. For linear birds like RS-44 the manual habit gets tiring, and a rig-control setup via Gpredict or SatPC32 pays off quickly. Test your control chain on a pass you don't intend to operate. Get the CAT cable, the radio's VFO tracking and the rotator working before you need them. And always check keps before a session, because stale elements waste whole passes.
  8. Here's the logistics side, in the order it usually works. Finding a session. The ARRL and HamStudy both have searchable session finders where you enter your ZIP code. Local clubs often post their own schedules too. Each listing should say whether the session is in person or remote, whether you need to pre-register, and which VE team runs it. Plenty of teams want an email or a sign-up form in advance so they have enough examiners and paperwork, so don't assume you can just show up. Some teams also run remote exams over video, which can be useful if nothing is nearby. FRN and ULS. Your FCC Registration Number (FRN) is the ID the FCC uses to track you. You get it by registering in the FCC's CORES system, and for an individual that normally involves your Social Security number. Do this before exam day and write the FRN down, because the VE team puts it on your application. ULS (the Universal Licensing System) is the FCC database where your license is stored. After you pass, the VE team submits your paperwork through a coordinator, and your new call sign eventually shows up in a ULS search. You can generally begin operating once your call sign appears there, so don't transmit just because you passed. Fees. They vary. The VE team or its coordinating organization sets the exam fee, and some teams charge little or nothing. FCC fee rules for amateur licensing have been under discussion, so I won't quote a number. The session listing or the team contact should tell you the current amount and which payment methods they take. Ask that before you go. What to bring. Government photo ID, your FRN, the fee in whatever form they accept, a couple of pens or pencils, and a basic calculator in case they allow one (ask the team, since some want it cleared or non-programmable). If you hold any other license or CSCE, tell them in advance.
  9. I'd add a safety layer to the list, because the kit is only useful if you can pack up and leave quickly. For weather, check the forecast for thunderstorm potential before committing to a summit or an exposed park spot, and decide your bail-out trigger in advance, such as thunder or visible build-up, rather than making that call mid-pileup. A tall pole with a wire on it, held up in an open area, is the last thing you want to be standing next to in a storm. Lower the antenna and move to lower, sheltered ground early. Cold and wind matter too: fingers lose dexterity before you notice it, so keep gloves you can still log in. For Field Day style setups the priorities flip a little. You usually have a vehicle, more people, and often a fixed location, so the weight limit disappears and reliability and logging discipline take over. A shared log with a clear way to detect duplicates is worth more than a nicer antenna. Keep power redundancy simple: two smaller batteries, a fused distribution block, and clearly labeled connectors, so a loose Anderson Powerpole doesn't take down the whole station. As for sharing gear between the kits, the pole, the choke, the coax, and the logging notebook can be the same everywhere. The radio and battery are where people usually split, since a rig that makes sense at 5 W on a ridge may not be what you'd want for a long operating session at a group site. One question for the thread: does anyone carry a small tarp or bivy as part of the station, not just the personal kit, so the radio and log stay dry if the weather turns?
  10. I'd question the plan for the ESP32. It's useful, but it's easy to overuse. A Wi-Fi-connected antenna switch is convenient, though you're then putting network access on something that switches antennas. At minimum, keep it on a separate VLAN or use a local-only protocol, and don't expose it to the internet. For a remote switch, a wired Ethernet-to-serial or a Pico with an isolated serial link may be more robust than Wi-Fi at the far end of a yard. For the rig side, Hamlib is worth using even for small projects. Let rigctld own the serial port and have everything else (logger, dashboard, band decoder) talk to it over TCP. That avoids two programs fighting over one CAT port. The same goes for rotators: Hamlib's rotctld can sit between your software and a controller that speaks a common protocol such as GS-232, so you can swap hardware later without rewriting your software. On Si5351 and APRS trackers, remember the Si5351 outputs a square wave, so any transmit use needs proper low-pass filtering and a check of harmonics. Don't run it into an antenna directly. For a tracker, be sure you know the rules for your license and for power output before you transmit anything.
  11. For copy practice, send-and-receive balance matters less than how you copy. If you write down every letter, you'll tend to fall behind as speed rises. Try copying in your head in short bursts: callsigns, then short words, then common phrases like CQ, DE, UR, RST, QTH, NAME, 73. Because abbreviations and prosigns repeat so often, recognizing them as units instead of letter strings frees up attention. It also helps to separate prosigns from similar-sounding characters. AR ends a message, SK ends a contact, BT is a pause or separator, and KN means go ahead, only the named station. They're sent as a single run without letter spacing, which sounds different from the same two letters sent normally. On Farnsworth: many people use it while learning new characters and then reduce the extra spacing as recognition becomes automatic. If a character is still being counted, slow the spacing, not the character speed.
  12. I'd move message handling up the list. Plenty of people can talk comfortably on a repeater, but the real work in an EOC or a shelter is often moving accurate written information from one place to another. Get comfortable with the ICS-213 and with radiogram structure: number, precedence, handling instructions, station of origin, check, place of origin, time and date filed, addressee, text, signature. The precedences are Routine, Welfare, Priority and Emergency, and knowing the difference is useful even if your served agency only uses a plain form. One habit worth building early is reading the message back and having the receiving operator repeat the critical parts, especially numbers, names and addresses. Phonetics for anything that could be misheard. And under NIMS the expectation is plain language, so skip 10-codes and radio slang when talking to agency staff, even though hams love them. Also, tactical callsigns like "Shelter One" or "EOC" are fine for clarity, but you still need to identify with your FCC callsign at the end of communications and at the required intervals. That is something that gets forgotten when things get busy.
  13. On the setup side, these are the usual failure points. First, the password. The Winlink account password is case-sensitive and is separate from your computer or email logins. Test it with a Telnet session before blaming the radio. If the CMS rejects it, fix the account first. A "secure login" failure over RF is often the same wrong password rather than a modem problem. Second, audio levels. Set the transmit drive so the radio's ALC barely moves or stays off, and don't run the radio at full power with the interface turned all the way up. Overdriven sound card modes splatter and decode badly at the other end. Receive level needs to be high enough to decode but not clipping. For PTT, choose one method and make sure Winlink Express and the modem agree on it: CAT, serial RTS/DTR, or the interface's own VOX. Windows also loves to reassign COM port and audio device numbers when a USB interface is moved to another port, so label the port each device should use. Third, message handling. Keep traffic small, because every kilobyte costs airtime, especially on HF. Text is better than attachments, and images should be avoided over radio unless there is a clear need. Forms such as ICS-213 General Message from the Standard Templates are filled out in a viewer and sent as small attachments with a text body. A recipient without Winlink Express and the matching forms can still read the text, but the form data will not display properly. Agree beforehand which form versions and templates the team uses, and update templates before an exercise, not during one. Fourth, radio-only and P2P. A Radio-only message type exists for traffic that should travel only over radio paths and not be released onto the internet. Use it when you need to control how a message is routed, and verify how your recipient will receive it. P2P connects two Winlink Express stations directly, one initiating and one listening, using a P2P session type for the matching mode (packet, VARA, ARDOP). It is a good way to practice when no gateway is available, and it doesn't depend on a CMS connection, so it suits a local incident or a gateway outage. For Winlink Wednesday, check the current instructions from the organizers rather than relying on memory, since the check-in format and addresses can change. Treat it as a regular scheduled exercise: pick a gateway, send a short test message, confirm that it posted, and record the session log, because the log tells you what went wrong when a connect fails.
  14. On the CAT side, I would start by drawing the control chain on paper: radio, then one program that owns the port, then everything else connecting through that. Most of the intermittent problems come from two programs fighting over the same COM port, or from a virtual port pair that was set up with different baud rates on each end. The rig and the software need the same baud rate, data bits, stop bits and handshake setting, so check those against the radio menu before blaming the program. For Cabrillo, the habit that saves the most trouble is reading the generated file before upload. Look at the header, then spot-check a few QSO: lines against what you remember working. Common problems are the wrong category, a missing or extra operator callsign, a power class that does not match the entry, and exchange fields that are blank because a QSO was entered without the required report or serial number. Some sponsors have a log checker or acknowledgement page, so after upload see whether your log was accepted before the deadline instead of assuming it was. For club-level logs, such as a club station or a multi-operator entry, agree beforehand on how logs are merged. Everyone should be on the same contest and category, the same UTC clock, and the same naming conventions for operators and stations. Merging several ADIF files after the fact is where duplicate and out-of-order QSOs show up. If you run multiple stations on a network, check the contest program's networking features and test the multi-op setup before the contest starts.
  15. One thing worth adding is a regular test routine. A bag that sits in a closet for a year is a risk. A simple schedule helps: twice a year, pull everything out, charge and cycle batteries, check connectors, confirm your frequency list is current, and run a short radio check on the local net or a simplex frequency. Make a one-page inventory that you tick off. Also separate "must work" from "nice to have." If the HT, spare power, and a working antenna are solid, you can improvise the rest. If the base item fails, the extras don't matter. For power, label each battery with its charge date and chemistry, and don't assume a power bank that charges your phone can also drive a 12 V radio. Check its output voltage and current rating before relying on it.
  16. Here are some places where the pool commonly catches people, with the concepts behind them. Privileges and bands. Technicians get all amateur frequencies above 30 MHz, plus limited HF privileges: CW on parts of 80, 40, and 15 meters, and voice/data on a segment of 10 meters. Learn the common VHF/UHF band names (2 m, 1.25 m, 70 cm) and their rough frequency ranges. The wavelength rule of thumb is wavelength in meters ≈ 300 divided by frequency in MHz, so 146 MHz is about 2 meters. Electronics. Memorize Ohm's law (E = I × R) and the power formula (P = I × E), then practice rearranging them. Know the basic units (volts, amps, ohms, watts, hertz) and metric prefixes like kilo, mega, milli, and micro. Only a handful of questions involve calculation, but they're easy points once you've drilled the formulas. Also learn the schematic symbols and what common components do. RF exposure and safety. The pool is interested in the factors that determine exposure: transmitter power, frequency, how close the antenna is, duty cycle, and antenna gain. Safety questions also cover grounding, lightning, working near power lines, and tower and antenna installation hazards. License terms and operating. Know the license term, the grace period for renewal, station identification rules, and what a control operator is. For repeaters, learn the typical offset on each band, what a CTCSS (PL) tone does, and the difference between simplex and repeater operation. Practice questions on these are quick wins because they repeat in similar forms. Check the exact numbers against your current study material, since you should use the figures from the pool you're tested on.
  17. I'd start by getting in touch with the local EC or the emergency management office before buying anything. Ask what they actually need: shelter support, EOC staffing, hospital links, weather spotting, or backup communications for a event. Then take the free ICS courses and sit in on a few nets as a listener. Once you've heard how a decent net control operator works, you can pick up a lot about pacing and checking in stations. One caution on go-bags: build around the assignment type. A shelter position wants a different kit than a field spotting role. For a shelter or EOC you might need a table-top setup, extension cords, and a logbook. For a mobile role you need a safe way to mount an antenna and a plan for staying hydrated and fed for several hours.
  18. On the propagation side, I think the biggest trap is treating solar numbers as a forecast for your own path. A high flux value generally helps the higher bands, but whether you work anyone depends on your location, the time of day, the season, and geomagnetic conditions. A rising K-index can wipe out a path that looked great an hour earlier. The most useful habit is to check what's being decoded now. Open PSKReporter for FT8 on a band, or look at the RBN for CW, and see whether your region is being heard. Then compare that with the indices so you start to learn how the numbers map to what you hear. It also keeps you from calling the band dead when it's really just quiet at your end. For club news and awards, I'd just add that the club's own site or newsletter beats social media reposts. Deadlines, award rules, and special event callsign details change, and the original page is where corrections show up first.
  19. One addition on ALC: a lot of people set it once and never revisit it after changing mics or turning the processor on. Processing changes how much average level reaches the modulator, so the mic gain that looked right with the processor off can overdrive the chain with it on. Redo the ALC check with processing engaged, saying the same test phrases at the same distance from the mic. Also check the ALC reading on each band if you run an amplifier. A little ALC action from the radio is usually acceptable on many rigs, but if the amp is feeding back its own ALC voltage, the audio will sound compressed and mushy even though the radio's settings look fine. In that case reduce drive until the amp's output stops growing faster than the distortion. For sideband, remember that tuning the band edge on LSB or USB shifts where your signal actually sits. Keep your suppressed carrier frequency and the whole audio bandwidth inside the allowed segment, not just the dial reading.
  20. On the sound card and TNC side, most failures I see described fall into four buckets: wrong audio device, wrong PTT method, overdriven audio, and a software TNC that is not actually running. For packet with a software TNC, the chain is: radio audio into the sound card, a software modem that does the AFSK and AX.25 work, then a KISS connection to Winlink Express, and finally a PTT method that the modem or the program is allowed to control. The common mistake is two programs trying to key the radio, or the modem expecting a different COM port than Winlink Express does. Pick one owner for PTT and one owner for the audio device. If you use a virtual COM port pair or a TCP KISS connection, check the exact option your Winlink Express version offers, because the supported choices have changed over the years. For VARA HF and VARA FM, the VARA modem is a separate program that Winlink Express talks to. It has its own audio device, PTT, and sometimes CAT settings. If you set up Winlink Express but never opened the VARA settings, you will get a session that starts and then does not key or does not decode. Set the soundcard input and output in VARA, then use its tuning display and level indicators to set receive audio so it is neither buried nor clipping. On transmit, raise drive until you see power on the meter, then back down. A clean 100 W signal is not the target for a 2300 Hz wide data mode on a typical transceiver. Look at ALC and keep it from moving. For HF, use USB, and keep the rig's noise reduction, compressor, and wide filtering features out of the way. For ARDOP, the bandwidth you select should match what the gateway is configured for. A mismatched bandwidth is a common reason for connection attempts that go nowhere. One more detail that gets overlooked: if the gateway list shows a frequency for the station you want, confirm whether it is a dial or center frequency and how your software handles it. A 1.5 kHz offset error is the kind of mistake that looks like a dead band. If a connection fails, change one thing at a time. First prove the radio chain with a known-good test, then the modem, then the gateway, then the path. Trying a different gateway or a different time of day often tells you more than changing settings.
  21. For me the tiebreaker is usually the receiver audio and the noise floor, with the filters right behind. A rig can have a fancy display and a long feature list, but if the AGC pumps on a crowded band or the audio is fatiguing, I'd rather not sit in front of it for two hours. I do think the "old gear sounds warmer" thing is partly the audio chain and partly the bandwidth. A lot of vintage radios have a speaker and audio stage that roll off the highs, which sounds pleasant on AM and SSB. A modern rig can sound just as nice if you give it a decent external speaker and tweak the receive audio settings. It's worth trying before deciding that only a tube radio will do. On your point 3, I'd add that a boat anchor is much more fun if you go in expecting some tinkering. If you want to turn it on and operate with zero fuss, a well-sorted modern rig is a better choice. If you like the idea of a project, an old Heathkit or a Kenwood from the 1980s can be a rewarding bench exercise.
  22. Start with the format. Element 3 is 35 questions and you need 26 correct. That leaves room for a few misses, but not for skipping an entire topic. The questions are drawn from a published pool, so use the current pool for your exam date. Question pools are replaced on a schedule, and a study guide for an older pool can leave gaps. For sub-bands, don't try to memorize every frequency edge as a raw list. Learn the pattern first. Technician HF privileges are limited (CW on parts of 80, 40, and 15 meters, plus limited 10 meter privileges). General opens up much more of every HF band, with the CW/data portions generally lower in each band and phone higher. On the exam you'll see questions like "which band segment is available to a General but not a Technician" or "is this frequency inside a General phone segment". Make a one-page chart for 160, 80, 60, 40, 30, 20, 17, 15, 12, and 10 meters. Then drill it with practice questions until you can quickly say whether a frequency is CW/data, phone, or outside your privileges. Take the exact edges from the current ARRL band chart or the FCC rules rather than from a forum post, including the special 60 meter channel rules and the 30 meter power limit. Spend time on understanding rather than rote memory in the other areas. Propagation questions reward knowing why things happen. The D layer absorbs lower HF frequencies during the day, which is why 80 and 40 meters are better at night. Higher bands depend on solar activity and ionospheric refraction. Know MUF, LUF, critical frequency, skip zone, and gray-line propagation, and what solar flux, A-index, and K-index suggest about conditions. For vanity calls, you don't need to decide before the exam. After you upgrade, you keep your current call unless you apply for a different one. A vanity application is optional and depends on which callsign groups are open to your license class, and whether the call you want is available. Check the FCC's current rules and fee information before applying, since fees and procedures can change.
  23. On checking a choke on the bench: a NanoVNA can read it in a few ways. One is to put the wound choke in series between two ports and read S21, though that tends to flatter a choke at low impedance. Another is to wire the choke as a shunt with the coax shield and read the impedance directly in the shunt-through arrangement. The main thing is to look across all the bands you plan to use, because a toroid that performs on 40 m can be weak on 10 m, where self-capacitance in the winding starts to matter. Some builders stack several chokes, one for the low bands and one for the high bands, to cover the range. Before trusting any measurement, check that the dipole is balanced. Run the VNA with the choke at the feedpoint and again with the feedline touching or draped across something different. If the readings change noticeably, there is still common-mode current on the shield. A choke is also only useful if the feedline leaves the antenna at a sensible angle. Dropping coax along one leg of the dipole invites currents onto the braid. Power matters too. A choke working into a high-SWR load heats the core, so for a doublet driven through a tuner the core size and mix need to match the power and the worst-case mismatch, not just the average.
  24. On SO2R, I'd stress that audio discipline matters as much as the hardware. Most people put one radio in each ear, and some find it easier to keep a different pitch or level on each. The point is to know instantly which radio a signal is on. If you can't, the second radio becomes a distraction. Timing the CQ gap also matters. Short gaps between CQs leave little time for the second radio, while long gaps cost rate on the first. Start with a gap long enough to hear a call from the other radio, then tune it to the band. On the hardware side, a station that can't keep the radios from hearing each other will find SO2R frustrating however good the software is. If you are building toward it, sort out filtering and antenna separation first, then the switching, and only then the fancier macros. On categories: decide before the contest whether you want to be unassisted or assisted, and configure the software to match. It is easy to leave a cluster connection running by mistake, and the entry then lands in the wrong category.
  25. Think of grounding as two separate jobs. One is bonding the equipment together so there are no voltage differences between the radio, power supply and metal chassis. The other is lightning protection, and a single driven rod doesn't provide that. For a temporary station, bond your equipment together, and if you drive a rod, treat it as a static-bleed point, not protection. The real lightning plan is to watch the weather, lower the antenna, disconnect the coax and stop operating when thunderstorms get close. Nothing you can carry in a go-kit will make operating in a storm safe. With a generator, check the manual to see whether the neutral is bonded to the frame or floating. Many portable inverter generators have a floating neutral and say so. That matters if you ever plug into a GFCI or a transfer device. Never backfeed a building circuit. Keep the generator at least 20 feet from the tent, downwind, with the exhaust pointed away. Put a battery-powered CO alarm in the shelter anyway, because wind shifts and tent walls change airflow. For noise, turn things on one at a time and watch the S-meter on a quiet band, 40 m at night if you can. Cheap USB chargers, LED lights, MPPT charge controllers and laptop supplies are frequent offenders. A noisy device often can be fixed by moving it, shortening or rerouting its cable, or adding a snap-on ferrite. Don't wrap AC and DC cords alongside the coax. Run them at right angles where they cross.

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.