Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

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

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

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

Mod_Mike

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Mike

  1. until

    Computer-based, in-person amateur radio license testing run by the Story County ARC VE Team (AMESIA) on Sunday, July 18, 2027, 2:00-4:30pm CDT. The test fee is listed as free. Pre-registration is required.Location: Ames Public Library (Danfoss Room), 515 Douglas Ave, Ames, IA 50010, USA Organizer: Story County ARC VE Team (AMESIA) Source: Event information
  2. The most useful split is between prediction and observation. VOACAP and tools built on it use a smoothed sunspot number and a monthly median, so the output answers "what is typical for this path, hour and month?" It does not say "is it open now?" Read the reliability and SNR columns as probabilities and approximate signal levels, not promises. Ionospheric weather, such as a geomagnetic disturbance, will move the real result away from the median. For planning, such as which band to try for a given region at a given hour, a prediction is helpful. For go/no-go, live spots win. WSPR is good for this because the transmissions are standardized, with narrow-bandwidth 2-minute transmissions and an SNR report from each receiver. A 1 W or 5 W WSPR transmitter running for a few cycles can show which paths work and roughly how much margin there is. Two cautions. A blank map may mean nobody is listening in that region, so it does not necessarily mean the band is closed. WSPR's decoding threshold is also far below what you need for SSB, so a spot at -25 dB does not mean a phone contact is possible. Compare against the SNR you would need for your mode. One habit worth having is to listen for beacons before transmitting. NCDXF beacons on the 20 to 10 m frequencies are a quick band check. If you hear several continents at a reasonable level on 21.150 or 28.200, the upper bands are doing something. If you hear nothing on 28.200 but some on 14.100, you have a floor on what the MUF is doing.
  3. On tailending, I think the key difference is who benefits. If the operator is running one-hit-and-gone exchanges, a short call timed at the end of the previous QSO is part of how that operation works. If instead you hear a weak station still repeating the exchange, jumping in on top of it only adds a failed QSO for him and delays the next one for everyone. A decent rule of thumb is to wait until you can hear that the previous contact has been confirmed (a "73", "TU" or a clear "QRZ"), then call. On the low-band question, a receive antenna is often worth more than anything else, but only if the noise you're fighting is local and directional. A Beverage needs space, and a small loop or a pair of verticals may be more realistic on a small lot. Whatever you choose, test it on real signals: compare the S/N ratio, not just the S-meter, between your transmit antenna and the receive antenna on the same station. Sometimes the improvement is large, sometimes it's just a lower signal and lower noise at the same ratio. That test also tells you whether to make split operation easier by using the second receiver on the receive antenna and keeping the main receiver on the DX frequency. For deciding when to move on: if you've called a reasonable number of times and the operator is working stations well off your pattern (a different call area or a particular suffix), your time is better spent changing something, like frequency, timing, or band, and not repeating the same call.
  4. On propagation, you don't need to buy anything or sit in front of a radio, but listening does make the concepts stick. Tune around a band like 20 or 40 meters at midday, then in the evening, and the daytime D-layer absorption and the way higher bands open and close make intuitive sense. It also makes the MUF/LUF questions less abstract. The exam still asks the textbook version, so make sure you can say in your own words why lower bands tend to work at night and higher bands during the day. For antennas, the pool leans on fundamentals: a half-wave dipole's length relationship to frequency (roughly 468 divided by frequency in MHz gives feet, which is a useful memory aid for the formula), what a balun does, why coax loss rises with frequency, and what high SWR does and doesn't mean for your radiated power. Know the directional characteristics of common antennas well enough to compare them, since that comparison is a frequent question type. For digital modes, learn how they're used rather than just the names. FT8 uses fixed-length time slots, so your computer clock has to be accurate, and it's built for weak-signal contacts. PSK31 is a narrow keyboard-to-keyboard mode, and Winlink handles email over radio. Questions about where data modes are allowed tie back to the sub-band memorization. On vanity calls: it's not part of the exam, but it's good to know now. The FCC groups call signs by format, and the pattern of letters and numbers available depends on your license class. A General can request from more formats than a Technician. Look up the current group rules and the application fee on the FCC's site before you decide. As for timing, 30 to 45 minutes a day over three to four weeks, with practice exams from the second week, is a common plan. Stretch it if the math stays shaky.
  5. I'd add that the best audio depends on what you're trying to do. For a casual chat on a quiet band, a wider and fuller transmit response sounds nice and is good practice. For a pileup on a DX station, the aim is just to be understood the first time, so a narrower, more punchy and well-controlled signal is better. For the receive side, it helps to keep the filter wide enough while searching and then narrow it once you are on a station. It's easy to leave a narrow filter on and miss callers who are slightly off frequency. Also check your AGC speed: a slow AGC with a loud nearby signal can cover the weak station you wanted, while a fast one can make the background noise pump up between words.
  6. For contest practice, I would split receive and send work, because each has its own demands. For receiving, run a contest-style trainer or recorded contest audio at a speed slightly above your comfort level, and practice copying callsigns and exchanges in full without writing out everything. Callsigns with unusual letter combinations are the hardest part, so drill those separately. For sending, practice your own call and the exchange until they flow without thinking. Know the standard rhythm for repeating information: callsign once, exchange, then a quick TU or your call. When someone asks for a repeat with AGN or a question mark, send only the part they missed, not the entire exchange, and send it a little slower if the band is noisy. As for decoders in contests, rules differ between categories. Some classes allow skimmer-assisted spotting, and some operating categories expect you to copy by ear. Check the rules for the contest and category you enter before you rely on any software.
  7. Looking at the antenna side, the single highest-priority item is clearance from power lines. A mast that falls toward an overhead line is a classic cause of serious injury, so site selection should include a measured distance from any line of at least the full height of the mast plus a generous margin, and more is better. If the mast is guyed, think of the guy radius as part of the footprint too. Fiberglass masts help for insulation, but don't treat them as safe against contact with a line, since dirt or moisture on the surface can conduct. For the HF dipole, a 1:1 current balun or a choke of several turns of coax at the feedpoint keeps common-mode current from turning the coax shield into part of the radiating system. That matters in a tent, where the shield runs near the operator, the laptop, and the rig. If you use an end-fed half-wave, remember it still needs a counterpoise and a choke at the rig end, and it is more sensitive to what's nearby. Whichever you pick, put an antenna analyzer on the run before the net starts, with the antenna at its working height. On coax, VHF/UHF is where loss bites. A long run of thin RG-58-type cable can eat a meaningful fraction of your power at 2 m and much more at 70 cm, so use a lower-loss cable (LMR-400 class) for anything beyond a short jumper, or put the antenna on the mast closer to the rig. For HF, cable loss is less of a problem, so the lighter option is usually acceptable. Drip loops and strain relief at the shelter entry, and avoid running coax parallel to the power leads for long stretches. For grounding, the realistic goals are safety and noise, not magic. If you're running a generator, follow the manufacturer's instructions on grounding it, and use GFCI protection on any AC distribution. If storms are in the forecast, the plan should be to disconnect antennas, step away from the mast, and wait, not to rely on a ground rod. Include that decision point and who makes it on the checklist. For teardown, the order I'd write down is: stop operating and log the end time, power down radios, disconnect antennas and coax, lower the mast, retrieve guys and stakes, then fold the shelter. Count items back against the packing list, and mark any failed gear (a cracked connector, an intermittent cable) for repair so it doesn't return to the kit as if it were good.
  8. On the first-rig question, the answer depends on whether you want to operate SSB. If you do, the KX2 class of radio is the straightforward route because CW-only rigs like the MTR and TR-35 will not help you there. If you are happy on CW, a lightweight CW rig is hard to argue with. Receive current drain matters as much as transmit power, because you spend far more time listening than sending. Compare the receive-mode current figures in the manuals, not just the 5 W transmit spec. One more thing about SSB at QRP: the 10 W PEP figure is a peak number, and average power in speech is much lower. A clean, compression-free signal into a good antenna is not hopeless, but expect to work stronger stations or use a spotting network and calling frequencies rather than hoping to win a pileup.
  9. For club activities, the events that seem to hold people best are the ones with a clear outcome. A build night where everyone leaves with a working 2 m J-pole or a Powerpole distribution block is easier to run than a general "bring your radio" evening, though both have a place. Rotating the meeting format also helps: one month a short talk, the next a hands-on session, then a net night or a visit to the repeater site. VE sessions work best when they're easy to find and well organized. Announce the date, location, and fee on the club page, and tell candidates what to bring. Generally that means a photo ID, their FCC Registration Number (FRN), and the original and a copy of any existing license or CSCE. A VEC's own site is the best place to confirm requirements, since procedures, fees and whether remote sessions are offered can vary. For Field Day, remember that it's the ARRL event held on the fourth full weekend of June, so planning in spring leaves time to sort out antennas, power, logging software, and operating schedules. Giving newcomers a seat at the radio, with an experienced op next to them, is often the best Elmer program a club can run. It's also worth assigning a few people to greeting visitors and explaining what's going on, so the operators can concentrate on making contacts.
  10. The split makes sense, and I'd push it a bit further: let the microcontrollers own anything with a safety or timing consequence, and let the Pi own anything that is convenience. The antenna switch is the obvious case. If the Pi is rebooting or SSH is hung, the switch node should hold its last state or fall back to a safe default, such as a dummy load or a known antenna. It should never float to some random relay combination at power-up. Make sure the GPIO pins that drive the relay drivers have defined pull-down or pull-up resistors, because pins are in an undefined state during boot. On the SWR meter, remember that the reflection coefficient is Vr/Vf only if your detectors are reading voltage linearly. Diode detectors don't do that at low levels, so calibrate at several power levels. SWR is then (1+ρ)/(1−ρ). Also add a transmit-detect condition so the display ignores readings below a threshold. Otherwise noise on an idle band can produce a nonsense SWR figure. Finally, if you read the ADC during transmit, add some averaging and a small RC filter at the pin, but keep the time constant short enough to follow CW and SSB peaks if you want a useful peak reading.
  11. I'd lean toward the VPN-first approach, for the reason you already gave: it shrinks what you have to trust. Vendor remote tools are convenient, but each one has its own idea of authentication, port requirements and update cadence. If everything sits behind WireGuard, the radio ecosystem only has to work inside a trusted tunnel. One caveat is that some clients are fussy about discovery on a LAN, since they use broadcast or multicast to find the radio. You may need a routed setup with a fixed IP and manual entry rather than auto-discovery, so test that before you travel. On the rig side, the IC-7610 is a good example of why hardware separation helps. It has both USB and a LAN port, so you can pick whichever control path suits the software you use, but you should confirm in the manual which features (audio, CI-V, spectrum) each path carries. RS-BA1 is Windows software, so factor in a PC at your end. If you're using the SCU-LAN10, check Yaesu's compatibility list for your exact model rather than assuming a similar radio works. That unit's whole purpose is network connection, so firmware versions and the radio's menu settings matter. And please add a remote power switch on a separate path, like a smart PDU or a small relay board, and that path should not depend on the radio's own network interface. If the radio hangs, you need a way to power-cycle it without a drive to the site. Also consider a second, low-bandwidth way back in, such as a cellular router, in case the main ISP link fails.
  12. I'd begin with measurements, because "noise" and "RF in the shack" get lumped together. Check the noise floor on 40 or 20 m with the antenna disconnected and a dummy load on, then reconnect. If the noise is already high with a dummy load, the problem is local to the radio, supply or computer. If it only rises with the antenna, it's external or coming back in on the feedline. Then turn things off one at a time: the monitor, USB hub, LED lights and the supply. This usually pins down the source faster than buying filters. On the radios, don't assume the one with the best bench numbers will work best on your lot. A TS-890S or K3S may handle a nearby strong signal differently than an IC-7300, but your antenna system and the noise at your location matter a lot more than the test results. A radio with excellent receiver specs won't beat a quieter antenna.
  13. Here's how I'd handle the three conceptual sections, since they're where memorizing breaks down. Propagation: build one mental model and reuse it. The D layer absorbs lower HF frequencies during the day and fades after sunset. The F layer supports long-distance skip, and it's the ionization level that sets the maximum usable frequency (MUF). Higher bands like 15, 12 and 10 meters tend to open in daylight when solar activity is favorable, while 80 and 160 meters come alive after dark. Know the terms MUF, LUF, critical frequency, skip zone, grayline and sporadic E, and know that the A-index and K-index describe geomagnetic disturbance. Most questions come back to which band suits which time of day or condition. Antennas: expect the half-wave dipole formula (roughly 468 divided by frequency in MHz gives feet), the basic feed-point impedance of a dipole versus a quarter-wave vertical with radials, and what traps, baluns, and loading coils do. Coax versus open-wire feed line and the effect of mismatch are also common. Run the dipole formula a few times for different bands so it sticks. Digital and operating practices: for modes, understand what each one is for. FT8 and FT4 are weak-signal, timed-sequence modes that need an accurate computer clock. PSK31 is narrow. RTTY uses frequency shift keying. Winlink uses error-correcting protocols for message transfer. The exam tends to ask about concepts like ARQ and FEC more than about software. For operating, learn the station ID rule (call sign at least every 10 minutes and at the end of a communication), how split operation works for DX, what a band plan is and why it's a courtesy rather than law, and how to handle phone/data segment boundaries so your sideband and signal bandwidth stay inside the legal edges. One caution on rules: some digital-mode and bandwidth regulations have been revised in recent years. If a question seems to conflict with something you read online, check the current Part 97 text and the version of the pool your exam will use.
  14. On difficult conditions, the biggest improvement usually isn't a different word list but how you deliver it. Slow down, say the callsign once with phonetics, pause, then repeat it. Don't speed up when someone asks for a repeat. If the other station gets one letter wrong, correct only that piece: "the third letter is Sierra, S as in Sierra". If a standard word keeps failing, offer an alternate that is distinct from the confusing neighbor. Letters like B, D, P, T, V and E, or F and S, and M and N are the usual troublemakers, and the phonetic words exist to separate them. For names and places, spell only what is likely to be misheard. "My name is Jon, J-O-N" with phonetics if needed. Give a town once, and spell it if unusual. For grid squares, say each character, like "Foxtrot November three one", and repeat if the other operator is logging it. Slashes are generally voiced as "stroke" or "slash", and "portable" or "mobile" are sometimes added after the callsign when appropriate for the station's rules. Prosigns are mainly a CW thing: AR (end of message), SK (end of contact), BT (break or pause), KN (go ahead, specific station). On voice you use procedure words instead: "over", "clear", "say again", "break", and "go ahead". Don't say "over and out"; the two mean different things. Also "roger" means message received, not "yes". On nets, the phonetic part is mostly check-ins. A net control often asks for the suffix of your callsign only, "Kilo Alfa Bravo", which is faster than the full callsign. Follow the net's own procedure, because they vary. In emergency traffic, plain language is the safer habit, so skip 10-codes and jargon, and spell names, addresses and numbers carefully. Many emergency communications groups have the receiver read the message back for accuracy. Real distress voice calls use words like "Mayday" and "Pan-pan" for maritime or aviation, but ham operators handling emergency traffic should follow the local group's or served agency's procedures and their licensing rules rather than improvising.
  15. I would move a dummy load and an RF probe ahead of almost everything else. A 50-ohm load that can take your rig's full power for a minute or two lets you adjust and test a transmitter without sending a signal to the antenna. Several 1/2 W or 2 W metal-film resistors in parallel will do for the lowest-power transmitters. For anything over a couple of watts, use a proper load or a well-heat-sunk resistor array, and be aware that resistor inductance and stray capacitance make homemade loads less accurate as the frequency goes up. On the receiver side, one detail often missed with direct-conversion designs is that the audio stage matters as much as the mixer. The mixer output is often only a few microvolts to millivolts, so you need on the order of 80 to 100 dB of gain with a low noise floor. Poor grounding, supply ripple and a long lead from the mixer to the first audio stage are the usual causes of hum and oscillation. A low-pass filter at the audio output (even a simple RC or a few-pole active filter around 2.5 to 3 kHz) makes a surprising difference to how a receiver feels to use. For the SWR bridge, a tandem-match or Bruene-style bridge is simple, but calibrate it against known loads. With a 50-ohm dummy the reflected reading should null. A 100-ohm resistor should read about 2:1 SWR, and 150 ohms about 3:1. If it does not, then either your balance is off or the diodes are behaving differently at low power. QRP power levels mean the diode forward drop becomes a significant factor, so a bridge that reads fine at 10 W can look misleading at 1 W.
  16. On the security side, a few people treat vendor cloud login as enough, which is only part of the picture. SmartLink-style services and similar relay setups reduce the need to open ports, but you are still trusting the account and the endpoint device. Use a unique password and two-factor authentication if the service offers it. For radios without that feature, like a Yaesu behind an SCU-LAN10 or an Icom with RS-BA1, a VPN into the home network is usually the cleaner answer than forwarding the radio's ports. The radio's network stack is not designed to be exposed to the public internet. A practical checklist for a remote base: power control for the radio and amplifier, a separate switch for the antenna so you do not depend on one control path, SWR and temperature alerts, and a log of who connected and when. For a shared station, say through RemoteHams or a club arrangement, write down who is the control operator for each session. That makes the legal side much clearer, because the person with transmit access should hold the privileges for the frequency they are using under the rules that apply where the transmitter sits.
  17. Adding to the noise and etiquette side. If you hear a whine that rises and falls with engine RPM, that points to the alternator or charging system, and if you hear ticking that follows engine speed, that points to ignition or related electronics. The trick is changing one thing at a time. Check the radio's ground and the antenna ground first, then reroute the power cable, then try ferrites. Noise on the received signal can also be a clue that an antenna or coax connection is poor. After any fix, re-check SWR on both 2 meters and 70 cm instead of assuming it's fine. For cross-band repeat, keep power modest and watch the radio's temperature. A radio retransmitting for a long time in a parked car with the engine off can heat up and drain the battery. Also remember that anyone nearby can hear the repeated signal, so identify as required and don't leave it running unattended without understanding the rules where you operate. Mobile etiquette comes down to a few habits that make everyone's life easier: Listen before transmitting, and leave a short pause between overs so others can break in.Keep transmissions brief and give your callsign as required, not as a long speech.Avoid drifting into long conversations on busy repeaters. If the talk gets long, move to simplex with a quick agreement on a frequency.Keep the volume sensible so you aren't blasting the vehicle, and keep your attention on the road.If you're on a calling frequency, move off it once contact is made.Finally, test your install in a parking lot before relying on it in an emergency. Key up on each band, check audio reports from another station, and make sure the radio doesn't reset or the display doesn't flicker when you transmit at full power. That one test catches a lot of power wiring mistakes.
  18. One thing that trips people up is the difference between being on a summit and being in the activation zone. The rules define a zone around the top, measured vertically below the summit, and your operating position has to be inside it for the contacts to count. If a trail passes through a viewpoint or a clearing below the zone, check the map or the database notes before you set up. GPS elevation can be a few metres off, so don't treat the edge as exact if you can avoid it. Chasers should have a plan too. Keep SOTAwatch open, but also listen. Not every activator is spotted, and some spots arrive late. When you work an activator, give your callsign clearly, wait for the exchange, and don't expect a long chat. The activator may have a queue and cold hands. Log the summit reference as the activator gives it, and verify it against the database if you are unsure. Mistakes in references are easy to fix at your end before submission, but harder to sort out afterward. For HF kits, think about total system weight, not just the radio. A light radio with a heavy battery and a heavy mast may not be lighter than a slightly bigger radio with a smaller battery. Make a checklist, weigh everything, and then remove what you did not use on your last trip.
  19. On two-fers and roves, it is easy to forget that rules can differ between the parks you are visiting. If you move between a state park and a national park in one day, you may have different permit requirements and different restrictions on antennas. Read the posted notices at each entrance or trailhead, and have a backup plan for operating from a vehicle or a picnic table with a shorter antenna if the first plan is not allowed. Timing also needs thought for roves. Allow for setup, spotting, and teardown at every stop, plus a margin for a slow band. If the last park is short of 10 contacts and the UTC day is about to change, you can end up with an incomplete activation. A realistic schedule with one or two bands in reserve, such as 20 m and 40 m, beats an ambitious route.
  20. On the family side, I'd keep the plan boring. Everyone should know three things: where to meet, what channel to try first, and what time to check in. If you set up a GMRS or FRS channel for the family, remember that those radios are line-of-sight tools that may do well across a neighborhood but not across town. Do a range test with actual buildings and terrain in the way, not just across a field, and write down where it fails. It also helps to keep the plan usable by people who aren't radio hobbyists. A laminated card that says "Press and hold to talk, say who you are, say who you're calling, then release" does more than a feature-rich radio no one can operate. Cut the settings down to a minimum: set the channel, lock the keypad if the radio has that option, and put a label on the radio listing the channel, the family name and any codes. For the ham side, find out what your local emergency communications group expects before you need it. Many ARES or similar groups have net procedures, check-in formats and training that make it easier to be useful on the day. A kit with the right frequencies and the right habits beats a bigger kit with neither. Also, don't forget weather radio. A NOAA Weather Radio with SAME programming for your county, a battery backup and a hand-crank or solar option is a good low-cost warning layer, and you can test it without ever transmitting.
  21. For the keyboard modes and Winlink side, the failure points are a bit different, though the clock and audio issues overlap. In FLDIGI, PSK31 and RTTY are tolerant of a little timing error because they are not slotted modes, but they are still affected by overdriven audio and bad tuning. Olivia, MFSK and Hellschreiber suit different jobs: Olivia and the slower MFSK variants are designed to survive poor conditions and QRM at the expense of speed, while Hellschreiber is a visual mode where the "text" is displayed as an image and is surprisingly readable in some noise. Pick them for the path, not for novelty. Winlink is more of an email system over radio than a chat mode. With Winlink Express you pick a connection type such as VARA HF, VARA FM, ARDOP, Pactor or packet, and a station that offers the matching gateway. VARA is proprietary, and some speed levels need a registered license. The gateway, frequency, and mode matter more than your own audio setup in many failed attempts, so check that the station you want is actually listening on that band and has a reasonable path to you before you start retrying. One practical point on interfaces: a sound card interface with isolation and good cabling (and ferrites on the USB and audio leads) can remove a lot of hum, RF in the audio, and ground-loop noise. If your decode count drops whenever you transmit, or the PC glitches during a key-down, RF getting into the shack wiring is a likely cause, and it is worth checking before anything else.
  22. On the special event side, the best preparation is reading the whole event page, not just the callsign. Organizers often list the operating hours in UTC, bands and modes, and whether you need to work a certain number of contacts, bands or stations for the award. Some events are very specific about logbook search, an online request, or a self-addressed stamped envelope. Don't leave that for the last day, because the log upload may lag after the event ends. I'd also say 40 meters and 75 meters work well for different goals. If your goal is a regional net with a few dozen stations, 75 meters in the evening is hard to beat. If your goal is a special event contact from further away, 40 meters offers more chances with a modest antenna, though you may need patience when the band is crowded. For both, a clean signal beats extra power. Check your audio, avoid over-driving the mic, and keep your calls short. If you enjoy both activities, a simple routine works: join one regular net each week for the social side, then pick one or two special events each month to chase. That gives you steady operating practice without turning the radio into a chore.
  23. For the linking question, the most dependable way to know is the owner's documentation or the repeater club's page. Repeaters may connect to other repeaters through EchoLink, AllStar, IRLP, Wires-X, or a reflector, either all the time or only for scheduled nets. Many repeaters announce a connection or disconnection with a voice message. If you hear one, expect a delay and expect people on the other end to be hearing you. Pause longer than usual between transmissions and say your callsign clearly, since the remote listeners may not know your area. Each system works a bit differently. EchoLink is VoIP and uses node numbers. IRLP and AllStar are also commonly controlled with DTMF commands, and AllStar nodes are based on Asterisk software. Wires-X belongs to Yaesu's System Fusion and uses "rooms" that nodes connect to. Whether a particular repeater is still part of one of these networks can change, so check with the repeater's owner or club. Treat DTMF control codes as the owner's property. Don't connect or disconnect nodes or reflectors unless the repeater's rules say users may. DMR and D-STAR are different because the radio must support the mode, and the radio needs more programming than an FM repeater does. DMR commonly needs the right frequency pair, color code, time slot, talkgroup and your DMR ID. D-STAR involves callsign routing fields, such as the your-call and repeater fields, plus the module letter and gateway. A mistyped talkgroup, time slot or color code gives you the digital equivalent of the wrong CTCSS tone. On a busy talkgroup, listen for a while before you key up, because your audio can land in a conversation the repeater is carrying for many people. As for directories, RepeaterBook and club lists are useful starting points, but entries can be out of date. Look for a recent update date, and check the club's own page for tones, linking schedules and rules. In many places a regional frequency coordinator assigns repeater pairs to reduce interference. In the US, coordinated repeaters are generally given priority when disputes arise. An open repeater accepts general use, though the owner still sets the rules. A closed or restricted repeater limits access to members or approved users, often via a tone or other control, so ask the owner before you assume you can use it.
  24. On Farnsworth, the main trap is staying at the stretched spacing for too long. If the characters are at 20 WPM but the gaps are huge, your brain gets used to a lot of thinking time. A practical fix is to keep the character speed fixed and shrink the extra spacing in small steps. Do that instead of speeding up the characters, because changing character speed changes the sound of each letter and you effectively relearn them. For sending, check your spacing before your speed. If you can't send clean 15 WPM, 25 won't be clean either. Record a few CQs and a short exchange, then play them back with the paddle sidetone off. Mistimed letter gaps jump out right away, and those are what make a signal hard to copy for everyone else.
  25. A few practical points on the Pi and Direwolf side, and the CAT plumbing. For CAT, check each rig's physical layer before choosing a cable. Icom CI-V is a single-wire, open-collector style bus with addressed frames, so one transistor-based interface can't simply be treated as a normal UART. Some rigs use TTL-level serial and others use true RS-232 levels, which is a different thing from 3.3 V logic. Plug the wrong one into a Pico pin and you'll find out quickly. Where the rig has a USB CAT port, it's usually easiest to use that and add a USB isolator or ferrites if you hear hash. Then let Hamlib hold the port and everything else talks to rigctld. For Direwolf, the audio levels are the usual trouble. Its console output shows the received audio level, and the documentation gives a rough target to aim for, so adjust the receive audio at the source before trying to fix it in software. For PTT, a GPIO line (through a transistor) works. A CM108/CM119-type USB sound card with a GPIO pin is another common option and keeps the audio and PTT on one device. Then point your APRS client at Direwolf's KISS TCP port, 8001 by default, or its AGW port. For a Si5351 or CW project, remember that its outputs are square waves. They need a proper low-pass filter before they go anywhere near an antenna or a mixer. Also expect to calibrate the crystal offset, since the displayed frequency will otherwise be a few hundred hertz off. Keep the I2C wiring short, and put LCD backpacks and displays in a grounded enclosure. Cheap display drivers can radiate enough noise to show up as birdies on the lower bands.

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.