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.5
Wind 385.0 km/s
Aurora 1
Updated 13:00 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_Terry

Administrators
  • Joined

  • Last visited

Everything posted by Admin_Terry

  1. On antennas, the main trap with an end-fed half-wave is assuming the transformer does all the work. The radiator length, the coax acting as part of the antenna, and the lack of a real counterpoise all change how well it behaves. A choke a little way down the feedline helps keep RF off the coax and out of your receiver. It is also worth carrying a short counterpoise wire if the SWR is odd. For SSB, a few dB of speech processing or compression, if your rig has it, does more than extra power would at the same price. A 5 W signal with good audio and a clean edge can be copied by operators who would miss a muddy one. CW is the more forgiving mode, which is why most kits and ultralight radios are built around it. Also test the whole setup at home first: rig, key, battery, antenna and logging method. Many of the failures people hit in the field are cabling, a bad connector or a dead battery rather than propagation.
  2. On SmartBeaconing, I'd treat any numbers as a starting point and adjust to your area's channel load. The structure is: slow rate when below the low speed (often a beacon every 20 to 30 minutes when stopped), fast rate at or above the high speed (often one to a few minutes), and in between the rate scales with speed. Corner pegging then triggers a beacon on turns. For walking or cycling, the high-speed threshold should be low. Using a car's numbers on foot means you'll almost never reach the fast rate. For a car, a high speed threshold around highway speeds and a fast rate of a minute or two is a typical shape, but check your local APRS group's recommendations since busy areas ask people to be conservative. On handhelds: the TH-D74 and TH-D75 have a built-in GPS and TNC, and APRS beaconing and SmartBeaconing are configured in the radio's menus. The FT5D also has built-in GPS and APRS. Read each manual for how the beacon type (automatic, SmartBeaconing, manual), position comment, and path are set, because menu names differ between radios and firmware. Also, handheld transmit power and antenna are usually the limiting factor, not the settings. A handheld at its own height may reach a digi in one place and not another, so a fill-in digi with WIDE1-1 matters a lot. Weather stations are worth mentioning too. A positional weather report carries wind direction and speed, gust, temperature, rainfall, humidity and pressure in a fixed-format string, and it's normally sent at a modest interval, like every 10 minutes or longer. There's no benefit to beaconing weather faster than the sensors change.
  3. My rule is to do one full lap without buying anything, then go back for the things that are still on my list. It's easy to overspend on the first table you see. Prices on similar items vary a lot, and a lap lets you compare. It also shows you who has the manuals and accessories, which can matter more than a small price difference. For the "is it a deal" question, I ask three things. Can I test it right there? Is the price clearly below what a working unit costs from a regular dealer or the used market? And what would it cost to fix if it's broken? An untested rig for a low price can be fine if you're comfortable repairing it, but a beginner should be careful. A dummy load and a wattmeter or a small power supply in your bag go a long way toward verifying things on the spot.
  4. On the log submission side, I'd make Cabrillo checking a habit, not a last-minute task. Open the generated file in a text editor and look at the header lines before you upload. Check that CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND, CATEGORY-POWER and CATEGORY-MODE are what you intended, because a wrong header can put your score in the wrong place. Then scan a handful of QSO lines for obvious problems: the wrong exchange field, a time zone slip, or a dupe sheet that doesn't match what you remember working. For events like Field Day, state QSO parties and SOTA, the rules are different from the big DX contests, so don't assume the same workflow. Field Day has bonus points and a class/section exchange, QSO parties often care about county or state multipliers, and SOTA activations are logged through their own system. Treat each one as its own set of rules, and keep the sponsor's page open while you prepare the log.
  5. On the power supply point, check what the amplifier needs before buying the supply for the rig. A 500 to 600 W class solid-state 13.8 V amp draws far more current than any 100 W transceiver, and most amplifiers in that class come with their own supply or a specific recommendation for one. Match the cable gauge and fusing to the amp's data sheet, not to the radio's. Also, the supply should be sized for continuous duty, not just SSB peaks. Digital modes and CW at full power are far kinder to the voltage regulation of a 30 A supply than a 20 A one at its limit. I'd also be careful with the idea that an internal ATU can substitute for fixing the antenna. The built-in tuners on the IC-7300, IC-7610, FT-991A, FTDX10 and TS-890S have limited match ranges, so they are best for small SWR bumps across a band. The G90's wider-range tuner can force a match on something awkward, but a match at the radio end does not recover power lost in the line. If the SWR is high at the antenna, put the tuner there or switch to a balanced feedline and a balanced tuner. Whichever tuner you use, retune at low power after any change, and avoid hot-switching an external tuner or antenna switch.
  6. For the VHF side, the usual indices matter much less. SFI and K have little to say about whether 6 m will open by sporadic E tomorrow, though a very high SFI and a strong F2 can also bring 6 m openings at the peak of a solar cycle. For E-skip, what helps is watching spots and the season. Look for 10 m and 28 MHz beacons opening, then 6 m. If you see 10 m sporadic E, it's worth checking 6 m too, because the MUF of the cloud can be higher than you think. Also, E-skip usually shows up as short-skip distances first, then multi-hop if the clouds are widespread. For tropo, forget SFI altogether and look at weather: high-pressure systems, temperature inversions, calm conditions, and coastal or over-water paths. Forecast maps for tropo ducting are published by several weather and amateur sources, and they're more useful than solar numbers for 2 m and 70 cm. On NVIS, one practical tip is to check foF2 from an ionosonde if one is near you. If you can see the critical frequency, you can choose between 80, 60 and 40 m instead of guessing. If the critical frequency is below your operating frequency, the signal goes through the layer instead of coming back, and you get a skip zone around you. That's a common cause of 'the band seems dead but I can hear distant stations.'
  7. A single master log is the least painful approach, with award tracking done as reports from that log rather than as separate files. The reason is that most credit problems come from inconsistent data. If the entity, CQ zone, ITU zone, state or grid is wrong in one copy and right in another, you end up chasing phantom problems. A few habits that help: Make sure the cty or entity data file in your logging program is current before you import contacts. Prefix rules and entity boundaries change, and old data can assign a contact to the wrong entity or zone. Be especially careful with special event calls, DXpeditions that operate from several locations, and stations with portable or maritime mobile suffixes. Treat the DXCC, WAZ and WPX fields differently. DXCC and WAZ depend on where the station was operating, while WPX depends on the prefix actually used in the callsign. A single QSO can be right for one award and a problem for another. For paper QSLs, a reasonable rule is to chase them when an entity or band slot is unlikely to appear on LoTW soon. That includes operators who aren't LoTW users and DXpeditions that don't upload quickly. Check whether the operation has a QSL manager or an online request system, and keep your request records, because replies can take a long time. Before submitting any application, run a duplicate-and-mismatch check. Look for contacts whose callsign appears in more than one entity, or whose entity is marked deleted. Those are the lines most likely to cause trouble.
  8. On safety, treat the hike as the main event and the radio as the bonus. Leave a route plan and a turnaround time with someone reliable, and tell them when you are expecting to be back. Check the forecast for the summit, not the town, because wind, temperature and visibility can change a lot with elevation. Carry the layers, water, food, light and navigation you would take for the hike without a radio. If the weather turns or you are behind schedule, abandon the activation. SOTA points are not worth an unsafe descent. Be careful with antennas near exposed ridges. Keep long wires and poles away from lightning risk, and do not set up on a summit if thunderstorms are developing. Also check access permissions and wildlife or seasonal closures. Being allowed to use a summit is not always the same as the summit being in the database. For logging, write down callsign, time, band, mode and any summit-to-summit reference as you go, even if you plan to use an app. A paper backup is useful if a phone fails. Afterwards, enter the log in the format required by the SOTA database, check the callsigns and summit references, and submit it. Chasers should keep their own logs of activator callsign and summit reference, since that is what the database matches against. Do the check while the day is fresh, and fix typos before you upload.
  9. Koch and Farnsworth are not really rivals. They solve different problems, and many trainers let you use both at once. Farnsworth is about timing. The characters are sent at a faster speed, but the gaps between characters and words are stretched, so the overall speed is lower. The point is that each letter still sounds like a single quick rhythm instead of a string of slow dits and dahs. If you learn at a slow character speed, you tend to count elements, and that habit is hard to unlearn later. Koch is about the order in which you learn characters. You start with just two characters at a fairly high character speed. When you can copy them reliably, usually taken as about 90% correct, you add a third, then a fourth, and so on. Your ear is always working on a small set of characters that you can already recognize, plus one new one that is still difficult. The usual combination is Koch for the character order, a character speed somewhere around 18 to 20 wpm, and extra spacing that you shorten over time. Different trainers handle this differently, so check the settings. One thing to watch is that some programs change the character speed as you go instead of keeping it fixed, and that can undermine the whole idea. On tools, LCWO.net and the G4FON Koch trainer both follow the Koch approach, so you don't need both on day one. LCWO runs in a browser and keeps your progress in an account. G4FON's is a downloadable program for Windows. Pick whichever you will actually open every day. CW Academy, run by CWops, is different because it's a structured class with a human advisor and a small group, and it's built around daily practice between sessions. Check the CWops site for current course levels and sign-up dates before planning around it. The two approaches fit together well: CW Academy for the structure and accountability, and a Koch trainer for the daily drilling. As for memorizing a chart, I'd skip it. If you only see dots and dashes on paper, you train your eyes, and your ear is what you need on the air. Treat each character as a sound, and the pattern on a chart becomes irrelevant.
  10. Adding the VHF/UHF part and the international side, since those answers are mostly about conventions. 6 m (50 to 54 MHz) has distinct sub-bands in the ARRL plan. The bottom is CW-only weak-signal work and beacons. The SSB calling frequency is 50.125 MHz, and 50.313 MHz is where FT8 is commonly found. The national FM simplex calling frequency is 52.525 MHz. The idea of a calling frequency is that you make contact there and then move off to another frequency to talk, so you don't tie it up with a long conversation. On 2 m (144 to 148 MHz), 146.520 MHz is the national FM simplex calling frequency, and the plan reserves the surrounding region for FM simplex. 144.200 MHz is the SSB calling frequency, and weak-signal work (CW, SSB, EME) is in the lower part of the band, with repeaters in the segments above that. APRS in North America is on 144.390 MHz. On 70 cm (420 to 450 MHz in the US), 446.000 MHz is the national FM simplex calling frequency, and 432.100 MHz is the usual weak-signal calling frequency. Repeater pairs are in the 442 to 445 and 447 to 450 MHz regions, subject to local coordination. Local frequency coordinators can make exceptions, so a regional repeater map might not match the national plan. Technician and above have access to all of these in the US. 33 cm (902 to 928 MHz) is a different kind of band. Amateur use there is secondary, shared with other services including unlicensed Part 15 devices, so local noise can be significant. It is also allocated to amateurs in ITU Region 2 only, so it isn't available in Europe or Africa. The ARRL plan puts weak-signal operation near 902 to 903 MHz, but I don't remember the exact calling frequencies reliably, so check the current plan rather than relying on a number from a forum post. Internationally, the ITU divides the world into three regions, and allocations differ. A few examples: 40 m is 7.0 to 7.3 MHz in Region 2 (the Americas) but 7.0 to 7.2 MHz in Region 1. 80 m runs 3.5 to 4.0 MHz in Region 2 and 3.5 to 3.8 MHz in much of Region 1. 70 cm is 430 to 440 MHz in Region 1 but 420 to 450 MHz in the US portion of Region 2. 6 m is not available in every country, and 60 m access varies widely by country and by license class. When you listen to a station abroad, they may be legally transmitting on a frequency your license wouldn't permit, and the reverse applies when you travel. If you plan to operate in another country, look into its reciprocal licensing arrangement and follow the local rules for bands, power and modes. Your US privileges don't go with you.
  11. Start with the wire antennas, because on a small lot they are usually the least painful. They all trade something away. An EFHW is a half-wave wire fed at the end, where the impedance is very high, often a few thousand ohms. That is why the matchbox is a transformer of roughly 49:1 or 64:1. A 40 m version is about 66 ft long and also works on 20, 15 and 10 m as a harmonic. It is easy to hide, because it is one thin wire and a short run of coax. The catch is the return path. With no real counterpoise, current wants to flow on the coax shield, so a good common-mode choke a short distance down the coax matters a lot. Some of the matchbox losses depend on the core material and how hard it is driven. A transformer that looks fine on 40 m can run warm, or lose noticeable power, on a band where the feedpoint impedance is far from the design value. Harmonic operation also means the pattern gets more lobes on the higher bands, and nothing guarantees a low SWR on the WARC bands. The OCFD is fed at about one-third of the way along, with a 4:1 current balun. The feedpoint impedance is lower than at the end, so the balun's job is easier. It covers 80/40/20/10 m with a reasonable match, and it is usually weaker on 15 and 12 m. The patterns are lopsided on some bands because the legs are unequal. Mechanically you need the full length, around 130 ft for 80 m, and you will not have that on a small lot unless you bend it, and bending costs performance. The G5RV is a 102 ft flat top fed with a 31 ft ladder-line section, then coax. It is a 3/2-wave on 20 m and needs a tuner elsewhere. It works, but it is not a magic multiband antenna. The coax section after the ladder line sees whatever SWR the tuner is hiding, so you want a choke at the ladder-line-to-coax junction. My own preference for a one-wire solution that has to cover many bands is a doublet fed with open-wire or window ladder line and a tuner with a balanced output or a good balun. Ladder line is low-loss even at high SWR. It does not care about the 'perfect' match, so the weakness is mostly in the tuner and the balun. Avoid a length that puts a very high impedance (thousands of ohms) on a band you really want, because that stresses the tuner and the balun. It is worth modeling a few lengths in a free modeling program (NEC-based) before cutting wire.
  12. On the analog side, the SWR meter and rotator position sensing are where the ADC choice shows up. For SWR, the usual designs use a directional coupler feeding either diode detectors or a log detector like the AD8307, and the microcontroller reads forward and reflected voltages. Two things are easy to overlook. First, calibrate across the bands you care about, because coupler response and detector behavior vary with frequency and power. Second, take readings only while there is enough forward power. At near-zero power the reflected/forward ratio is meaningless and the display will jump around. For noise, average multiple samples, keep the analog ground return separate from the relay and motor current path, and put an RC filter at the ADC input. A 16-bit I2C ADC like the ADS1115 is slow but quiet, and that is usually fine for a rotator pot or a slowly changing power reading. For a fast SWR sweep it may be too slow, and a Pico's internal ADC with good filtering, or a faster external ADC, makes more sense. For a rotator pot, a stable reference voltage matters more than resolution. If the reference is the 3.3 V rail shared with WiFi bursts on an ESP32, the reading will wander with load. Powering the pot from the ADC's own reference or a clean regulated supply, then calibrating end stops in software, gets better results than adding bits. Finally, on soldering: for fine-pitch parts like SMD ADCs, flux matters more than the iron. A decent flux pen, a small chisel tip, and cleaning the board afterwards will save a lot of intermittent problems that look like software bugs.
  13. The comparison depends on what you value. The TH-D75 and ID-52A both make sense for someone who wants GPS, APRS or D-STAR, though the price and the added menus are a real step up from a basic FM radio. If you're not going to use those features, you're paying for them. On the IC-705, I'd keep it in a separate category, as you said. It's good for portable HF and VHF/UHF operation with a larger battery and a proper antenna, but it's much bigger than a handheld and not a radio you would clip to a belt at an event. The two aren't really competitors. One thing I'd add on offsets: don't assume the offset from memory. Check the repeater directory and the sponsoring club's information, because some machines use nonstandard splits, a particular tone, or a different input than the usual plan would suggest. When a repeater won't respond, the common causes are the wrong offset direction, the wrong tone, or low power into a poor antenna, so check those in that order before blaming the radio. For emergency use, a cheap spare radio programmed identically to the main one is a better backup than a second expensive one. Keep a paper list of channels with it, and make sure someone else in your group can operate it.
  14. Q codes started as three-letter signals for CW. Each one can be a question or an answer depending on whether you add a question mark. Here is the usual set. QRM is interference from other stations, meaning man-made. QRN is natural noise such as static and thunderstorms. People mix these up all the time. A neighbor's switching power supply is not QRN, though plenty of people call it that. QSB is fading, where the signal rises and falls. QRP is low power. Many operators and contests treat 5 watts or less on CW and 10 watts on SSB as the QRP line. QRO is high power. QRT means "I'm stopping transmission" or shutting down the station. QRZ? means "who is calling me?" You hear it when several stations call at once and the operator missed a callsign. It's also the name of a well-known callsign lookup site. QSO is a contact or conversation. QSL means "I acknowledge receipt," and it's also the name for the confirmation card or electronic confirmation after a contact. QSY means change frequency. QTH is your location. QRL? means "is this frequency in use?" and QRL by itself says "it's busy." It's good practice to send QRL? before calling CQ on a frequency that sounds empty, because you might not hear a weak station on the other end. Related ones you'll hear: QRS (send slower), QRQ (send faster), QRX (wait or stand by), QRV (I'm ready), and QRU (I have nothing for you).
  15. Learn the math-light concepts properly, and don't try to memorize every question. The theory questions repeat the same ideas with different numbers or wording, so a mental model beats rote recall. Some models that carry a lot of questions: Op amps: Know the two gain formulas. Inverting gain is -Rf/Rin, so a 100k feedback resistor with a 10k input resistor gives -10 (a 180-degree phase flip). Non-inverting gain is 1 + Rf/Rin, which is never less than 1. The ideal assumptions (very high input impedance, very low output impedance, inputs at the same voltage under negative feedback) answer most of the rest. Transistors: Alpha is collector current over emitter current, so it's just under 1. Beta is collector current over base current. Amplifier classes are about conduction angle: Class A conducts the full cycle (linear, inefficient), Class B about half, Class C less than half (efficient, but needs a tuned circuit and isn't suited to linear modes like SSB). Filters: Q is center frequency divided by bandwidth. A 7.1 MHz circuit with a 100 kHz bandwidth has Q of 71. Know the difference between Butterworth (flat passband), Chebyshev (ripple, steeper skirts) and elliptical filters, and what shape factor means. Oscillators: Colpitts uses a capacitive divider in the feedback network. Hartley uses a tapped inductor. Pierce is a crystal oscillator. Once you tie each name to its signature component, those questions get easy. Modulation: Modulation index for FM is deviation divided by modulating frequency, so 3 kHz deviation with a 1 kHz tone gives an index of 3. That kind of question appears in several forms. Use the question pool for practice, but whenever you miss one, find out why the right answer is right. Otherwise you're memorizing letters.
  16. The alphabet is effectively one list with several names. ICAO, ITU and NATO all use the same 26 code words: Alfa, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu. The official spellings are "Alfa" and "Juliett", chosen so speakers of other languages pronounce them correctly. Most hams just say "Alpha" and "Juliet", which is fine. Amateur radio generally doesn't force one specific alphabet on you in everyday operating. Licensing rules differ by country, so check yours. In practice the standard list is the sensible default because it was designed and tested so each word stays distinct across accents and poor audio. Many operators who use it for callsigns are happy to improvise for names, but the standard words are the safer first choice. On numbers: the ICAO-style pronunciations ("tree", "fower", "fife", "niner") exist for international clarity. Most hams say normal English digits. "Niner" is the one that spread widely, because "nine" can be confused with the German "nein". You don't need the full set, but "zero" instead of "oh" is a good habit because it can't be mistaken for the letter O. Standard words are also useful for UTC. "Zulu" means UTC in much operating practice, so a time like "1830 Zulu" is unambiguous if both stations understand it. Whether you say "UTC" or "Zulu" is local culture.
  17. Your architecture is sound, and I'd add details on the generator side. Carbon monoxide is the hazard people underestimate with a tent or canopy. Put the generator well away from the shelter, downwind, with the exhaust pointed away from anywhere people sit or sleep, and run a battery CO alarm inside the shelter anyway. Don't refuel a hot or running unit, and keep the fuel storage away from the generator and the operating position. On grounding and bonding, read the generator manual rather than assuming. Many portable inverter generators have a floating neutral and a specific procedure if you're powering anything beyond direct plug-in loads. Don't improvise a backfeed into any building circuit. If it's powering extension cords, use a GFCI-protected arrangement and keep cords off the ground where water can pool. On noise, I'd test before the deployment rather than during it. Run the generator-powered charger and any switching supplies at the planned distance and watch the S-meter or a noise floor measurement on the bands you intend to use. Switch-mode supplies, MPPT solar controllers and cheap USB chargers are all common noise sources, and the fix is usually distance plus ferrites or chokes on the offending lead, not a new antenna. Also treat a generator as a scheduled source: define the fuel and runtime plan so it doesn't quit during a net. For lightning, there's no meaningful field grounding that makes an antenna safe in a thunderstorm. The plan should be a trigger: when a storm is approaching, stop transmitting, disconnect coax, and lower the mast if you can do it safely. A ground rod mostly helps with static and a reference point, not with protection from a strike.
  18. On propagation, treat the numbers as a weather forecast and the spotting networks as the radar. Solar flux and K-index tell you whether conditions are likely good or disturbed, but PSKReporter, RBN, and WSPR show who is actually hearing whom on a given band at that moment. If you hear nothing on 15 or 10 meters, a quick look at those maps tells you whether the band is dead or whether you just need a better antenna or more power. A good habit is to run a low-power digital mode or WSPR beacon for a while and compare your reports with a known-good station nearby. It tells you far more about your own setup than a headline about a great opening. For conventions and hamfests, I would pay attention to what is demonstrated on the floor versus what is just on a banner. Ask vendors about delivery dates, warranty, and software support. For club news, newsletters and net announcements are usually more reliable for local events than social media reposts, so check the club's own page or call-in net for time and location before you drive anywhere.
  19. On the antenna and noise side, it helps to measure before buying anything. Compare the noise floor on the same band with the antenna connected and with a 50-ohm terminator. If the difference is tiny on HF, the antenna is not delivering much external noise, so you are likely limited by receiver noise and may benefit from a more efficient antenna or a low-noise amplifier. If the floor jumps by 20 dB or more and the display is full of regularly spaced lines, you have local interference, and a better receiver will not fix that. Some quick steps for local noise: run the SDR from a laptop on battery to see whether the mains supply is the source, switch the USB 3 devices off, since USB 3 can radiate in the 2.4 GHz region and wider, and add ferrite chokes on the USB lead and the coax at the receiver end. Common-mode current on the shield of the feedline is a frequent reason why the noise floor changes when you touch or move the cable. A choke or a short length of coax wound through a ferrite core near the antenna feedpoint can reduce that. For panadapter use, keep an eye on the transmit path. Even a small amount of leakage from a 100 W transmitter at the SDR input will damage an unprotected front end. A proper TX-protected splitter, an attenuator, or taking the signal from the transceiver's dedicated IF or RX output are safer than just a T-piece on the antenna line.
  20. Here's the VHF/UHF side and the international piece. All US license classes get the privileges above 50 MHz in the usual amateur segments, so Technician is not limited there. What matters is band plan etiquette, because weak-signal, FM simplex, repeater, satellite and digital use are all packed together. On 6 m (50-54 MHz), the bottom 100 kHz is for CW and beacons, the SSB calling frequency is 50.125, and FT8 is at 50.313. FM simplex calling is 52.525, with FM mostly in the upper part of the band. On 2 m (144-148 MHz), the weak-signal segment is at the bottom: 144.200 is the SSB calling frequency and 144.174 is FT8. The national FM simplex calling frequency is 146.52, and APRS in North America is 144.390. Repeaters use pairs with a 600 kHz offset, but your local coordinator's plan decides which direction and which pairs, so check it before programming a radio. On 70 cm (420-450 MHz), 446.000 is the national FM simplex calling frequency and 432.100 is the usual SSB/CW weak-signal calling frequency. Repeater offsets are typically 5 MHz, again set locally. Part 97.303 also puts geographic limits on 70 cm near certain federal radar sites. On 33 cm (902-928 MHz), 902.1 is the weak-signal calling frequency. It is a shared band with ISM and Part 15 devices, amateur use is secondary, and noise can be a real problem. It is also only available in ITU Region 2 (the Americas). Simplex calling frequencies are for making contact, not for conversations. Call, answer, then move to another simplex channel in the plan. On 2 m FM that means something in the 146.40-146.58 range. Otherwise you tie up the one frequency everyone else is monitoring. Internationally, the ITU splits the world into three regions, and the allocations differ by band. The best-known examples are 40 m, which is 7.000-7.300 in Region 2 but 7.000-7.200 in Regions 1 and 3, and 80 m, which is 3.500-4.000 in Region 2 and 3.500-3.800 in Region 1. On 2 m, Region 1 is 144-146 rather than 144-148, and on 70 cm Region 1 is 430-440. 33 cm doesn't exist in Regions 1 and 3. The IARU region band plans also differ from the ARRL plan. The same FT8 frequency can sit in a digital segment in one place and next to phone in another. For 60 m, many countries now use the 5351.5-5366.5 kHz allocation, which doesn't line up with the US channels. A US station may hear signals it cannot legally answer. If you operate abroad, make sure you know which country's rules apply and what reciprocal arrangement covers you. Your privileges there are set by the host country, not by the US license class. For the cheat sheet, I'd label every frequency as either a legal limit or a convention, and I'd link the current ARRL band plan and the Part 97 text so readers can verify.
  21. On 23 cm and above, the dish becomes the natural choice. As a sanity check, a 3 m dish at 1296 MHz with a typical 55% efficiency gives about 30 dBi and a beamwidth around 5 degrees. A 1.8 m dish at 10 GHz is around 43 dBi, but with a beamwidth near 1 degree, so mount rigidity, backlash, and the tracking error budget are now serious engineering constraints. Position feedback and a tracking program that handles pointing corrections are not optional. Sun tracking is a convenient way to calibrate pointing offsets since the Sun is easy to find. Polarization also changes. On 23 cm many stations still use linear polarization with a rotatable feed to adjust for the spatial offset. Circular is common on 10 GHz. The reflection from the Moon reverses the sense of circular polarization, so stations on the microwave bands commonly transmit one sense and receive the opposite. Check the conventions your partner expects before assuming a mismatch is a hardware fault. Libration fading is the other big shift. The Moon's apparent motion relative to Earth spreads the reflected signal in frequency, and the spread grows with frequency. On 2 m it is slight, while on 23 cm it is wide enough to hurt narrow decoders, and on 10 GHz it is much wider still. This is why wider submodes make sense on higher bands. For Q65, choose the submode letter to match the expected spread, and for JT65 the same logic applies, with the B and C variants being the wider ones. Exact conventions vary, so check what the local EME group and the current software documentation recommend instead of assuming. Q65 also generally offers a modest sensitivity edge over JT65 in similar conditions, which is useful when your signal is near the edge. For skeds, plan around the Moon window. You need the Moon above the horizon at both ends with enough elevation for a clean path, and the path loss is about 2 dB better near perigee than at apogee. Agree on the band, mode, frequency, which minute starts first, and who is sending in which period. Keep clocks synced to within about a second, and use the standard message sequence of calls and grid, then reports, then RRR, then 73. Short signals like OOO and RO are common in this style of QSO. Whenever possible, schedule against stations that match your capability, since the best first contacts are the ones where both sides are within the decode threshold, not a station that is just barely audible to a big array.
  22. Agreed on net discipline. One thing that helps beginners is separating three situations that sound similar: a practice net, a directed net during an actual event, and an open emergency channel where someone just needs help. In a directed net, you don't transmit unless called, except for emergency traffic. Many new operators feel they are being helpful by chiming in, but it clogs the channel and makes net control's job harder. Also worth practicing: working without the repeater. If your plan depends on one machine and it loses power or the link goes down, can you move to simplex or to a backup frequency? Know your group's plan for that, and know your agency's plan for which channels are primary and alternate. Honestly, the best preparation is to run a few drills where net control deliberately announces that the repeater is down and everyone has to move. It's uncomfortable the first time, and that is the point. One more small suggestion for the ICS side: once you've completed the online courses, ask whether your county offers a hands-on EOC orientation. Reading about an EOC and sitting in one with a headset on are very different, and the orientation usually shows you who sits where and how requests flow.
  23. Adding the pieces that tend to get left out of run-vs-S&P discussions: category, antennas, and endurance. Category first. If you're in an assisted category, a skimmer feed and cluster spots let you build a mult list quickly. Since RBN-style spots can include spots for your own callsign, you can also see where your signal is being heard, which is useful for deciding whether to keep running or QSY. In unassisted categories none of that is available, so S&P takes longer and a good running frequency becomes more valuable. Overlay categories (like some Classic or Rookie-type categories in various contests) change the equation again, so read the rules for the specific contest rather than assuming. Antennas. Running rate depends heavily on how well you can be heard, and in contest conditions a modest gain advantage can mean a clearly different rate. For the higher bands, stacked yagis let you pick takeoff angles that suit the path, with the low stack for short skip and the high one for long haul. On the low bands, a separate receive antenna such as a Beverage or similar directional receive antenna can matter more than a bigger transmit antenna, because it lets you hear weak callers under the noise. Whatever you have, an antenna switch that lets you change quickly without thinking is worth more than a theoretical extra dB you can't use fast. Band changes and rules. Some contests restrict how often multi-operator stations can change bands (the 10-minute rule in some CQ WW categories is a typical example), but single operators generally have more freedom. Even so, constantly moving costs you your run frequency each time, so the best approach is often to commit to a band while it is productive and move when the rate really drops, rather than chasing each spot. Fatigue. In a 48-hour contest the biggest errors are usually late: logging the wrong callsign, sending the wrong exchange, missing a band that's opening. Plan your off-time in advance and put your breaks where the rate is poorest, such as the dead hours on your main band, rather than whenever you feel tired. Keep water and food within reach so you don't have to leave the chair. If you use SO2R, remember it is more mentally demanding than single-radio operating, and an operator who gets tired should be willing to drop back to one radio and keep the log clean.
  24. CHIRP is the standard tool for programming many analog radios, including a lot of Baofeng models and the FT-65R. Check the current supported-radio list before buying, since support varies by model and firmware, and the newer digital handhelds often need the manufacturer's software or a different workflow. Always download the radio's current configuration first and save it as a backup before uploading changes. On repeater offsets, the common US convention on 2 m is 600 kHz, and which direction depends on the output frequency and local band plan. On 70 cm it is usually 5 MHz, and on 222 MHz it is 1.6 MHz. Other countries and regions differ, and some repeaters need a CTCSS tone to open. RepeaterBook and local coordinator lists give the offset and tone for each machine, so confirm those instead of assuming. Use the radio's reverse function to listen on the repeater input and see whether you can hear the other station directly. If you can, use simplex. For batteries, carry a spare pack, charge before an event, and use low power when range allows. Some radios have an AA battery tray for alkaline backup, which is handy when you cannot charge. If you power a radio from external DC, check its input voltage range and use a proper cable rather than a makeshift one. For emergency use, don't depend on repeaters alone. Repeaters can lose power or linking, so program local simplex channels, such as 146.520 MHz in the US, and any frequencies your local club or emergency group uses. Keep a printed frequency list in your go-bag in case the radio loses its memory. Join practice nets before you need to, so your first operation under stress is not also your first time using the menu.
  25. On the gain procedure: I'd add that it's worth checking for overload with a test that doesn't depend on the waterfall alone. Change the gain by a few dB and see if weak signals move by the same amount. Real signals should move with gain. Intermod products and images will often move by a different amount, or appear and vanish. If a spur moves by more than the gain step, it was probably created inside the receiver rather than arriving from the antenna. Another quick check is to insert an attenuator ahead of the receiver. A real signal drops by the attenuator value, while a product from overload usually falls faster, because intermodulation products scale nonlinearly with input level. On filters versus a better receiver: it depends on which problem you have. If the problem is a strong nearby signal outside your band of interest, a filter (FM notch, bandpass, or a cavity for narrow bands) addresses the cause directly, and a higher-bit receiver only gives you more room. If the problem is a very wide spread of signal levels inside your band, which is common on HF in the evening, then you need the better ADC and front end. Often it's both.

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.