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_Nancy

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Nancy

  1. On nets, I'd stress that the NCS is managing a limited resource, which is time on the frequency. Check-ins are easiest when you follow the format the net announces. Some nets want callsign only, some want a name and location, and some ask for a short comment. If you're unsure, just listen for a round or two first. Most nets explain their format at the start. It also helps to know the difference between directed and open nets. In a directed net, you talk through the NCS. In an open net, stations can talk directly to each other. Don't assume it's open. If you have emergency or priority traffic, say so clearly and briefly so the NCS can handle it first. For interference, I'd add that keeping notes helps a lot. If you ever need to report a repeater problem or a persistent noise source, time, frequency, mode, signal strength and how long it lasted are much more useful than "someone was causing trouble."
  2. One thing I would add to step 4 is an indicator for how long the dummy load was keyed. Resistors of 0.25 W each do not survive continuous carrier at 1 to 2 W, and a load that is slowly changing value gives you false SWR readings. A pulse of key-down at a time is fine for checking, and a metal oxide or a proper dummy load is better for longer tuning. For a first build, I would also separate the question of kit versus scratch build. With a kit like the uBITX, the main risks are solder bridges on the small parts and untested modules, and the bring-up order above still applies. For a Pixie or a Tuna Tin 2 style circuit, the circuit is simple enough that the problems are usually the crystal, the toroid winding or a wrong component value. Is the OP planning a kit or a design from an article?
  3. One practical tip on certificates and special event operations: keep a simple log of your own, whatever the event offers. Record the date and time in UTC, the callsign, band, mode, and any details the event asks for. Many events have a limited window for claiming a certificate or checking an online log, and a clean record of your contact makes it much easier to claim a certificate or sort out a mismatch later. It also pays to read the event's rules for what counts. Some events require a specific mode or band, a particular number of contacts, or a contact with a particular station. Sometimes a special event station is also operating under a different callsign on a different band, which catches people out. For nets, I'd say the best way to get comfortable is to start as a listener. Hearing how the NCS handles check-ins, late arrivals, and relays teaches you more than reading any guide. When you do check in, keep it short and clear, and the net will welcome you.
  4. On the two-fer announcement question: keep it short and say both references at least once, like "CQ POTA, this is [call], in K-XXXX and K-YYYY." Then use the full reference in your spot comment too, so hunters can see it before they tune in. People who need only one of the parks will still know they get credit, and it saves you from answering the same question repeatedly. One tip for logging: if you are not sure how the QSOs get attributed to each park, test with a small log or read the current POTA upload guidance before the trip. It is much easier to fix the log format before you have a full day's contacts in it.
  5. I'll take the VHF/UHF side, plus 60 m and the international bit. Same caveat as above: check the current Part 97 text and the band plan, because I'm giving the commonly used frequencies, not an authoritative table. 6 m (50-54 MHz): this is the "magic band" with a clear weak-signal section at the bottom. CW and beacons live around the lowest 100 kHz. SSB weak-signal activity follows, with 50.125 as the SSB calling frequency and the intercontinental DX window around 50.100 to 50.130. The common FT8 frequency is 50.313. The national FM simplex calling frequency is 52.525. Technician and above all have full privileges on 6 m, so class isn't the limit here. 2 m (144-148 MHz): 146.520 is the national FM simplex calling frequency. It's a calling frequency, not a hangout, so make contact and then move to another simplex channel. Other widely used simplex spots are around 146.40 to 146.60 and 147.42 to 147.57. Typical repeater outputs run roughly 146.61 to 146.97 with a negative offset, and 147.00 to 147.39 with a positive offset, usually 600 kHz, though local coordination decides what's really used. Weak-signal SSB and CW are at the bottom of the band, and 144.200 is the usual SSB calling spot. APRS in North America is on 144.390. 70 cm (420-450 MHz in the US): 446.000 is the national FM simplex calling frequency. SSB and CW weak-signal work is around 432, with 432.100 as the calling frequency. Repeaters commonly use a 5 MHz offset, and the exact sub-bands depend on your region's frequency coordination. There are geographic restrictions on parts of 70 cm because of other services, so check the footnotes in Part 97 for your area. 33 cm (902-928 MHz): this is the awkward one. It's allocated to amateurs only in ITU Region 2, and it's shared with other users, including unlicensed Part 15 devices, so noise and interference are common. 902.1 is often used as a weak-signal calling frequency, and FM simplex and repeater use is up to local plans, so look at what your area coordinator publishes. 60 m is channelized in the US rather than a continuous band. As I understand it, there are five channels, and General class and above can use them. Voice goes out on USB. The channel center frequencies are 5332, 5348, 5358.5, 5373 and 5405 kHz, which correspond to USB dial settings of 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz. The power limit is 100 W PEP ERP relative to a half-wave dipole, the bandwidth limit is 2.8 kHz, and CW and some digital modes are also allowed on the channels. We share it with other users, so I'd double-check the current rule text. Internationally, the 'ITU Region' idea matters. Region 1 covers Europe, Africa and the Middle East, Region 2 the Americas, and Region 3 most of Asia and the Pacific. For example, 40 m is 7.000 to 7.200 in Regions 1 and 3 and 7.000 to 7.300 in Region 2. 80 m is 3.5 to 3.8 in Region 1 and 3.5 to 4.0 in Region 2, and 2 m is 144 to 146 in Region 1 versus 144 to 148 in Regions 2 and 3. That's why you hear Europeans working split or listening in odd spots around the band edges. When you operate abroad under a reciprocal arrangement, the local allocation and the local license terms apply, not your home privileges.
  6. A single master log with good fields is the approach that makes the most sense to me. The main reason is that most of the awards you list draw on the same few pieces of data: call, date and time in UTC, band, mode, and then program-specific extras. For IOTA that means the island reference, for POTA and SOTA the park or summit reference, and for WAZ the CQ zone. Many logging programs can store these in ADIF fields, so you can export for each program without retyping. Check that your software populates the DXCC entity field using the date of the QSO, since entity status depends on when the contact happened. For deleted entities, I would record them as normal contacts and never worry about them for the Honor Roll or Challenge, since those use the current list only. The one trap is assuming that an old confirmation can be moved onto a successor entity. It cannot, because the successor is a separate entity and needs its own contact. Paper cards are still worth keeping for a few things. Some operators and expeditions do not use LoTW, and a card can be the only route to credit for a rare one. For routine contacts, uploading to LoTW and checking the matches regularly is much less work.
  7. On the family side, I'd treat licensed services and unlicensed ones as separate layers. FRS is fine for the kids to talk between houses or around a campsite, but the range is short, especially in buildings and hilly terrain, so test it before you rely on it. If you want repeater access or more range, GMRS is worth looking at, and the license covers your immediate family. Just make sure the radio is actually certified for GMRS, because many cheap dual-band ham radios are not. MURS is a nice option for simple point-to-point setups, and you can use it for things like a property or a small neighborhood, but with low power limits you shouldn't expect miles. Whatever you pick, write the channel plan on paper and keep one copy in each bag and one on the fridge. And keep the weather radio on a shelf with fresh batteries, so you get the alert even when nobody is looking at a phone.
  8. A tiered approach saves time and money. Upload everything to LoTW, and do it regularly, because a match can't happen if your side of the log is missing. Then look up whether the station you worked is active on LoTW. If so, wait for the match. If not, check their QRZ page for QSL instructions before deciding on anything else. For rare entities, I'd check Club Log for an OQRS option and whether the operator says "LoTW preferred." If they are on LoTW, a paid direct request is mostly wasted money unless you really want the paper card as a keepsake. Paper is mostly worth it for nostalgia, for stations not on LoTW, or for a card checked toward an award that needs paper. And for DXCC, check ARRL's current rules on submitting cards, since the requirements for paper confirmations are different from LoTW. One more tip on the bureau: write your callsign clearly on the front, and don't send cards to the bureau for stations that already confirmed electronically. It clogs the system and wastes everybody's time.
  9. For the lowest-complexity route, I would separate FM from linear. For FM, a dual-band handheld, an Arrow-style antenna, and a pass predictor are enough to make contacts, as long as you can hear the downlink and are willing to move the receive frequency during the pass. Before you transmit, listen to a few passes to learn the pass timing, how crowded the channel gets, and how much Doppler affects you. Your elevation also matters: low passes below roughly 10 degrees can be dominated by terrain and noise, while higher passes are cleaner but shorter. Linear is where I would add CAT control sooner. With an inverting bird like RS-44, once you have a rig that supports split operation and a program that tracks both VFOs, the passband is much easier to work. A handheld Arrow can work for linear in good conditions, but the pointing needs to be steady and the polarization mismatch can show up as fading. If you're limited to one radio, keep in mind that many HTs and basic mobile rigs are half-duplex, which makes it hard to hear your own downlink. Two receivers, or a rig with true satellite mode, makes a big difference.
  10. On kit weight, the usual trade-off is antenna versus radio. A tiny rig with a good antenna often beats a bigger rig with a compromised one. A linked dipole or end-fed half-wave on a lightweight pole is a common choice, and a short throw-line helps if there are trees. Test everything at home first, including how long it takes to set up in gloves. For logging, paper is robust and doesn't care about cold batteries, but then you have to transcribe into the CSV later. If you use a phone app, make sure it works offline and keep the phone warm. Either way, record UTC times and the summit reference for every QSO. On the awards, it's worth noting that Mountain Goat and Shack Sloth progress is tracked in the database. Keep your uploads tidy and use consistent callsigns, especially if you operate under portable or alternate callsigns, so the points go where you expect.
  11. Numbers, prosigns and nets each have their own conventions, so here are some thoughts on each. Numbers: say digits individually, and use "zero" rather than "oh" in callsigns and grid squares so there's no confusion with the letter O. "Niner" for 9 is widely used because "nine" can be mistaken for "five" or "nein" on a bad channel. The full ITU number words (Nadazero, Unaone, Bissotwo and so on) are rarely heard on ham bands, and most operators would be puzzled by them. Grid squares are handled as letters and digits, so FN31 is Foxtrot November three one. Names and locations: say the word naturally first, then spell it, because the word gives the listener context for the letters. For a place, say the town, then the state or country, and spell only the unusual part. Don't phonetically spell "Smith" every time, but do spell a surname with an ambiguous spelling or a name the other op will likely have to log. Prosigns and procedure: on CW, prosigns like AR (end of message), SK (end of contact), BT (break), KN (go ahead, named station only) and K (go ahead) carry procedural meaning. On voice, use plain words: "over" or "go ahead", "clear" or "this is [call] clear", and "break" for interrupting. Avoid saying "over and out" together, since the two have opposite meanings (expecting a reply vs. finished). Nets: many nets ask for check-ins by suffix or last two or three letters, then the net control repeats the full call phonetically to confirm. Wait for net control to finish before transmitting, and answer only to your own call. For emergency traffic, use plain language, say exactly what you need, give the key details (who, what, where, how many), and spell only critical or unusual items. Voice nets generally discourage Q-signals and 10-codes because plain English leaves no room for mismatched meanings. Always follow the net's or served agency's own procedures if they differ from this.
  12. For choosing a club, it helps to visit a meeting or two before joining and notice what the group actually does. Some clubs are mostly about operating: nets, Field Day, contests, and POTA or SOTA outings. Others lean toward emergency communications, a repeater, or technical builds. None of these is better, but the fit matters. Ask how new hams are welcomed, whether there's an Elmer or mentoring program, and how meeting information gets out (email list, website, group chat, repeater net). As for projects that last, the ones that seem to work best are small and have a clear finish line. A portable station kit that members can borrow, an antenna build night, a Raspberry Pi packet or digital-mode demo, or a basic soldering workshop all give people something to do with their hands and a reason to come back. Big long-term projects, like a repeater site upgrade, can work too, but they usually need a few dependable volunteers and a plan for documenting what's been done. One more tip: if your club hosts VE sessions, helping out as a volunteer is a good way to meet newcomers. Check with the VEC the team works through about requirements for becoming an examiner.
  13. Antennas, coax and grounding, since that's the other half of this. The mast: a fiberglass telescoping pole is fine for an inverted-V or EFHW if you guy it properly. Use at least three guy points at the upper section and the base, with stakes or weights sized to the wind forecast and the soil. Ballast like water jugs or sandbags helps on pavement. Don't raise a mast anywhere it could fall into power lines, and treat that as a hard rule. Keep the guy lines marked so people don't trip on them, and keep the antenna away from where the public or volunteers walk. For your end-fed, give some thought to the transformer's power rating and to the counterpoise or coax shield acting as part of the antenna. A common-mode choke at the feedpoint and another near the shack can reduce RF on the coax and the noise coming down it. Coax loss matters most on VHF/UHF. Thin RG-58 style cable can eat a lot of power at 146 or 440 MHz over a 50 ft run, so check the manufacturer's loss tables and consider a lower-loss cable like an LMR-400 type for that run. HF at these lengths is far more forgiving, so use thinner cable there if weight matters. Whatever you use, make connectors weatherproof and keep coax from lying in water, and put a drip loop where it enters the tent. Run coax away from power cords where you can, and cross them at right angles rather than in parallel. Grounding is where field operators often have mixed ideas. A ground rod at a temporary site will not protect you from a lightning strike. The safety plan for thunderstorms is to stop operating, disconnect antennas and stay away from masts, and shelter appropriately. What bonding does give you is a common reference: tie equipment chassis together with a short, heavy bond, keep DC negative and equipment grounds consistent, and follow the generator's manual for its neutral-ground configuration. An RF ground at HF is often more about choosing the right antenna and choke than about driving rods. If you see RF in the mic or the logging computer, the fix is usually a choke, ferrite, shorter cable runs, or antenna placement, not just another rod. For the shelter, weight the tent or canopy for wind from the start, keep sidewalls available, and put the power and antenna entries on the leeward side. Use cable covers or flags in walkways. Lighting should be low glare and low noise, and red or dimmable lights help when someone is working a radio at night. Keep a paper log and spare pens even if you log on the laptop. Checklists I'd build in: a pre-departure list (batteries charged, fuses, spare Powerpoles and crimper, adapters, spare coax jumpers, chokes, tools, printed frequency plan and net info, forms, and ID), a setup order (site survey, shelter, power, antennas, feedline, radios, then a noise and SWR check before you declare ready), an operating list (check-in times, operator rotation, battery voltage log, fuel log), and a teardown list in reverse. On teardown, count the stakes and guy lines, coil coax loosely, recover all small hardware, label any damaged items for repair, and recharge and inspect the batteries before storage. The usual misses are tent stakes, cable ties, a missing short jumper, and a half-charged battery that gets stored that way. For EMCOMM use specifically, write down the communications plan before you leave: who you serve, primary and alternate frequencies, net control, message format, and when you report status. A well-powered station with a vague plan is less useful than a modest station with a clear one.
  14. On fatigue, the most useful habit is planning breaks before you need them. Rate drops during the worst propagation hours for your station, and that is the cheapest time to sleep. A tired operator makes more copy errors, forgets to check the bandmap, and tends to stay on a dead band too long. Hydration, food that does not cause a crash, a chair and headset you can tolerate for hours, and sensible audio level all affect how long you keep a clean log. Deciding in advance when you will take your off-time, and what the minimum rate threshold is for staying on a band, takes some of the emotion out of the choice. For antennas, think about what is limiting you: transmit gain, receive ability, or the ability to switch quickly. On the low bands, receive antennas such as Beverages or small loops can matter as much as the TX antenna, because you cannot work what you cannot hear. On the high bands, a Yagi with a rotator or a stack lets you use both low and high takeoff angles as conditions change. Compromise stations often do better by being honest about their strong band or two and building the strategy around them, rather than evenly spreading effort across all bands. Finally, check your category. Single-op, assisted or unassisted, low or high power, QRP, single-band or all-band, and multi-operator classes all have different rules, so the same strategy does not always apply. Checking rule details such as time limits, band-change limits for multi-ops, and spot use before the contest avoids a disqualification or a wrong class.
  15. For noise and power problems, I'd separate rig noise from supply and station noise. Run the rig from a clean linear supply or a battery if you can. If the noise vanishes, look at the switching supply, the DC cabling and the grounding. If it stays, check the rig's internal rails for ripple with a scope, using a short ground spring rather than a long ground lead so you don't add pickup of your own. Excess ripple on a regulator output often points to a failing electrolytic, a regulator problem or a bad solder joint. On capacitor replacement, a multimeter alone won't tell you much about an electrolytic. A capacitance reading helps, but ESR matters more in supply and decoupling stages, so an ESR meter is a very good addition. Don't shotgun every capacitor, though. Compare the voltage, temperature rating and ripple-current rating with the original, mind the polarity, and clean up any electrolyte residue properly. On surface-mount boards, leaked electrolyte can eat traces and pads, so inspect around the capacitor and not just the part itself. Also check for shorted tantalums on low-voltage rails. Contact cleaning helps with intermittent faults, scratchy controls and relay-switched paths, but use it carefully. Use a cleaner suited to the component, and avoid soaking parts that can be damaged by solvents or lubricants, such as some trimmers, filters and plastic parts. After cleaning, work the control or connector repeatedly and re-test. If the fault returns quickly, look for a cracked solder joint, a worn contact or a corroded connector. For basic gear, I'd list a DMM, a current-limited bench supply, a dummy load, an RF power meter, a scope, and the service manual or schematic. A scope makes the PLL, oscillator, ripple and keying checks far easier. An RF probe for the DMM is a cheap way to trace signal flow, and a NanoVNA helps with filters and antenna checks. For tube or older mains-powered gear, add an isolation transformer or a bulb limiter, and discharge high-voltage capacitors before working inside.
  16. Adding to that, the Smith chart scares people more than it should. The pool questions are mostly about reading it, not plotting complicated networks. The center of the chart is a perfect match, meaning the normalized impedance is 1 + j0. Circles centered on the chart are constant-SWR circles, so the farther from center, the higher the SWR. Moving toward the generator is clockwise, and one full trip around the chart is a half wavelength of line. Know that the left edge of the horizontal axis is a short circuit and the right edge is an open circuit, and that you normalize impedances to the characteristic impedance of the line. That covers most of what you'll see. For antennas, keep the reference straight. dBi is relative to an isotropic radiator, and dBd is relative to a half-wave dipole, with dBi = dBd + 2.15. Also review how element length and spacing affect Yagi gain, front-to-back ratio, and feed impedance, and the idea of radiation resistance versus loss resistance in determining efficiency. The Part 97 section is the most memorizable chunk. Group related rules together: station control types, third-party traffic, identification, spurious emission standards, power limits, and the Volunteer Examiner system. Read the actual wording of the rules for the topics you find vague, because the pool phrases things closely to the regulation. On the privilege question: Extra gives you access to every amateur band segment and mode. The exclusive segments are small slices at the low ends of 80, 40, 20, and 15 meters, along with the wider phone allocation on 75 meters compared to General. For a lot of operators the practical gain is a few extra DX-friendly slots when pileups get crowded, plus eligibility to serve as a VE for all exam elements. It's a good goal on its own merits, but whether the privileges change your daily operating depends on how you use the bands.
  17. On duplicates, it helps to separate two kinds. There are contest dupes, where the same station is worked again on the same band and mode under the contest rules. Then there are database duplicates, where the same QSO record gets imported twice. The first is a rules matter and the logger handles it live. The second is a data-hygiene matter, and you only avoid it with a consistent import path. Most logging programs match on callsign, date and time (within some tolerance), band and mode, but the details vary. A mode mismatch such as MFSK/FT4 versus a plain digital mode, or a time zone error in the import, is enough to defeat the matching. For LoTW, check the station location before you sign a big batch. If the grid, DXCC entity or zones are wrong, you can end up with a perfectly signed upload that never matches. Re-signing the whole batch takes time, and a mistake might even create duplicate-looking records on the LoTW side. DXKeeper, Log4OM, HRD and Logger32 all have some way to set or confirm this, but the field names differ, so compare the exported ADIF against a record you know is correct. For Cabrillo submission, the most common errors I'd look for are a wrong category line, a callsign in the header that doesn't match the one used on the air, and exchange fields shifted by a column. Open the file in a text editor before you upload it. If the sponsor's site gives a log-checking report, use it to make sure your own logging setup is right for next time.
  18. The split architecture is the sensible one, and the dividing line is basically "what must be safe if the Pi crashes?" Anything that can damage equipment, such as relay sequencing, PTT timeout, and not hot-switching an antenna relay, should live in microcontroller firmware with a simple serial or network command interface. The Pi just asks for a state and the microcontroller decides whether it is allowed. A hardware PTT timeout is cheap insurance against a stuck transmitter. On CAT levels, don't generalize between rigs. Check the manual's pinout and signal description for each radio. A TTL-level port can usually go to a 3.3 V device through a resistor divider or a proper level shifter, but an RS-232-level port needs a MAX3232-type converter, and connecting it straight to a Pico can destroy the pin. For CI-V, the bus is shared and open-collector, so a transistor or a purpose-designed interface is the safer approach. If it's feasible, using the rig's USB CAT port directly with Hamlib avoids most of this, though you then have to deal with USB noise and ground paths. For relay drivers, use a ULN2003 or a logic-level MOSFET with a flyback diode, and power the coils from a separate supply from the logic rail. Relay coil kickback is a classic cause of random resets that get blamed on RF. For an antenna switch, break-before-make behavior, a sensible relay rating for the band and power, and some interlock against switching under power matter more than which brand of board you use.
  19. For the power side, I'd treat the fuse and wire as one system rather than separate decisions. The fuse protects the wire, not the radio. If the cable ever shorts, you want it to open close to the battery, before the long run of copper can overheat. That is why the fuse goes at the battery end of the positive lead, not at the radio. Also check how the battery connection is made. A ring terminal on a clean, tight connection is better than a loose clamp. If you're using the supplied cable, don't shorten it carelessly or replace the fuse holders with something less capable. If you need a longer run, step up the wire gauge and keep the connections solid. For noise diagnosis, a handheld or a second receiver is a handy test tool. Run the engine, switch accessories on and off, and watch the S-meter or noise level. If the noise changes with RPM, suspect alternator or ignition. If it comes and goes with one device, such as a dash cam, phone charger or LED light bar, that device is the culprit. Fix the source before adding filters around the radio.
  20. Your group-by-group plan is a good fit for how the exam is built. Since each exam question comes from a different group, a weak spot in one group costs you about one question, and you have nine questions of slack (26 of 35 to pass). The practical reading is that you don't have to be perfect, but you shouldn't skip entire groups. On what to understand versus memorize, a few things are worth actually learning: Ohm's law and the power formula (E = I × R, P = I × E). Be comfortable rearranging them, because questions can give you any two values and ask for the third. Also learn the metric prefixes (milli, micro, kilo, mega), since unit conversion trips up many people more than the algebra does. Frequency and wavelength. The shortcut is wavelength in meters ≈ 300 divided by frequency in MHz. It explains where the band names come from: 144 MHz is roughly 2 meters, and 440 MHz is roughly 70 centimeters. Once that clicks, a lot of band-related questions become easier to reason through. The rest, like license term, ID requirements and who can be a control operator, is mostly rule recall. Flashcards work well for that. As a reminder, the license term is 10 years and there's a grace period after expiration, but check the current FCC rules for the details rather than relying on a forum post. For the practice-test question, the shuffled-answer concern is valid. If you miss a question, write down why the right answer is right, not just which option it was. Then, when you see the question again with the choices reordered, you'll still get it.
  21. For BITX and uBITX builds I'd put the filters and the output stage at the top of the checklist. These are fun, capable designs, but the transmitter chain is fairly broad, and the stock low-pass filters are only as good as the toroids and capacitors you actually built. If you wind the toroids yourself, check the inductance with a meter if you have one. If not, count turns carefully and compare with the instructions for your exact kit revision. Different kit versions have changed over time, so use the documentation that matches your board. It's also worth looking at the output on an SDR or analyzer if you can reach one, rather than just trusting the power meter. Check each band you plan to use, because a filter that looks fine on one band can leave strong harmonics on another. Don't drive the final stage harder than it needs. A cleaner 5 W is better than a dirtier 10 W. On accessories, a basic iambic keyer is a good first project because it is small, forgiving and testable on the bench. Use a pull-up on each paddle input, debounce in software or with a small capacitor, and check that the keying line only switches the transmitter's key input and doesn't carry RF back into the keyer. A small ferrite bead on the cable often cures odd keyer behaviour on transmit.
  22. One thing that has helped a lot of groups is separating "net skills" from "station skills" when you evaluate. A net can run beautifully while individual stations struggle with their own setup, or the other way round. If you score them separately, the fixes become obvious: net skills usually need scripts, training and net control rotation, while station skills point to go-kits, power, antennas and checklists. On message handling, I'd also add a rule that the receiving station reads back the message in full on at least some of the traffic. It's slower, but it shows exactly where errors creep in. Numbers, similar-sounding names and street addresses are the usual culprits. If you run it as a timed drill and then as an accuracy drill, people see the trade-off between speed and correctness and learn when each matters. For served agencies, a short joint tabletop before the on-air exercise can save a lot of confusion. Even a one-page sheet listing who sends what, in what format and to whom gives everyone something concrete to test.
  23. On picking nets: choose by purpose rather than only by band. If you want to practice emergency skills, a local ARES or SKYWARN training net teaches you the format and gets you used to the people running it. If you're newer to HF, a ragchew net on 75 or 40 meters is more forgiving, because stations generally welcome newcomers and the pace is slower. For traffic, look for the NTS section net in your area and ask the net manager how a new station can start handling radiograms. The ARRL message format has specific parts (number, precedence, station of origin, check, place of origin, filing time and date, addressee, text, signature), and it helps to practice on paper before you try it live. One caution on schedules: net times, frequencies, and even whether a net still meets are easy to get wrong from old lists. Check the net's own page or ask the sponsoring club or section before you plan around it. Also note whether times are given in local time or UTC, especially around daylight saving changes.
  24. On the RACES vs. ARES question, I'd suggest checking with your local emergency management office and your Emergency Coordinator rather than assuming. Registration, ID requirements, and who has activation authority can differ by county and state. Some places run the two as one combined group, and others keep them separate with different rosters. The part that tends to matter on a deployment is that you know who tasked you and who you report to. If you're working for a served agency, check in with the person in charge on arrival, find out what they need, and avoid freelancing on the air. Keep chatter off the net, keep transmissions short, and use tactical call signs where the net calls for them, while still giving your FCC call at the required intervals. For SKYWARN, I'd treat it as its own training track. Your local NWS office sets the class schedule and reporting criteria, so use those and not generic advice. Knowing what to report, such as hail size, wind damage or flooding, and how to describe location and time, is a skill separate from emergency net work, though both reward clear, brief reporting.
  25. I'd treat it as a decision based on what you want out of the contact. If the goal is DXCC, LoTW is the first thing I'd check. Look at the station's QRZ page or the DXpedition's website to see whether they upload there, and if so, upload your own log and wait. Spending money on a direct card for something that will show up in LoTW is usually unnecessary. If they don't use LoTW and you want credit, then a paper QSL is the way to go, and it has to meet the award rules. The card should look professional and hold every required piece of information. For a card you just want for the wall, the bureau is fine as long as you can wait. One more tip for LoTW: if matches aren't showing up, double-check your station location in tQSL. A wrong DXCC entity, grid, or zone setting can cause problems, and fixing it later may mean re-signing and resending the affected QSOs.

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.