Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

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

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

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

Mod_Dan

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Dan

  1. On the MARS/CAP point, it helps to separate three things: what the hardware can do, what the software lets you do, and what you are authorized to do. A menu unlock or jumper only changes the second. Without membership and authorization in the relevant program, using those frequencies is not covered by an amateur license, and the rules differ again outside the US. Even for authorized use, check that the radio's specs are valid where you are operating. Output power, filtering, and spurious emissions may not be characterized outside the ham bands, so test it instead of assuming. Also keep in mind that if a modified radio is used in a service that needs certified equipment, the modification itself can be the problem. For firmware, I'd avoid flashing anything unless you can identify the exact hardware revision and have a way to restore the original. Wrong-variant flashes are a common way to turn a good handheld into a brick. If a build changes band limits or power tables, treat it as a different radio and re-verify it on a dummy load before putting it on the air.
  2. For mobile, the usual practical order is: location of the mount first, then cable routing, then antenna type. A roof-center NMO with a quarter-wave or 5/8 whip is a sensible baseline. A trunk-lip or fender mount makes the pattern lopsided, because the metal around the antenna isn't symmetrical. Magnets are fine for temporary use but check the paint and keep the surface clean, and use a short, round coax path rather than flat cable pinched in a door. Whatever you choose, check the SWR across the band you use, not just at one frequency, because mounting position changes the resonance. A 5/8 whip also isn't guaranteed to beat a quarter-wave in real life if the ground plane is poor. On connectors: PL-259 is acceptable for a mobile VHF setup with a short run, but if you also run UHF or the connection will be outside and exposed, N-type with proper sealing is a better long-term choice. The more frequently you swap antennas, the more a repeatable, well-made connection matters, because a half-soldered center pin looks like an antenna problem when it is really a connector fault.
  3. Your split between rules and band plan is the right one. The legal question is: does Part 97 allow my license class, this emission, and this power on this frequency? The band plan question is whether I'm using the space the way everyone else expects. Whenever you're unsure, check the current FCC text for the band, since privilege tables on old charts can be out of date. On band edges, think about where the energy actually is. In USB the carrier is suppressed and the signal sits above the dial frequency by roughly 300 Hz to 2.7 kHz or so, depending on your audio filtering. So at the top of a segment, say a phone limit at 14.350, you want the dial low enough that the whole sideband stays below the limit. In LSB the signal sits below the dial, so near a lower edge such as 3.600 or 3.800 you need to keep the dial a few kHz above it. A reasonable margin is a kilohertz or more beyond the bandwidth, because dial readouts aren't always perfectly accurate and a wide transmit audio setting can spread your signal. The same applies to digital modes. With FT8 or similar, the signal is at dial frequency plus the audio offset, so a high offset near an edge can push you out. Staying away from edges with the audio tones in the middle of your passband avoids the problem. Calling frequencies are for making contact and then moving. On 2 m FM, 146.52 is for finding someone, then you QSY to another simplex frequency so the channel stays open. Weak-signal SSB and CW sit in the lower portions of 6 m, 2 m, and 70 cm, away from the FM sections. If you're listening on 6 m for an opening, that's where you'll hear it, not on the FM calling channel.
  4. Start with the power budget, because everything else follows from it. A 100 Ah LiFePO4 battery is about 1,280 Wh nominal. Usable energy is somewhat less once you account for inverter losses (if you use one), cable drop, and a reserve you don't want to cross. Treat roughly 1,000 Wh as a planning number and adjust from there. Then look at your rig's spec sheet instead of guessing. A 100 W HF transceiver can draw around 20 A on key-down at full power, but SSB voice and typical net traffic average far lower. Receive current is usually 1 to 2 A, and a laptop, lights and chargers add to that. Build a table with a receive load, a transmit load and an assumed duty cycle, then add a safety margin. Digital modes at high duty cycle change the picture a lot, so run FT8-style or Winlink sessions at reduced power if you can. Many stations only need 25 to 50 W for regional work. On solar, a 200 W panel rarely delivers 200 W. Angle, temperature, haze, shade from tents and trees, and season all cut it down. It's good for offsetting the draw during the day, but I wouldn't count it as your only recharge plan for a 48-hour deployment. Keep the controller away from your HF antenna and receiver, and put ferrites on the panel lead and the load lead. Some MPPT controllers are noisy on HF, so test yours before the deployment, not at the site. For LiFePO4 in general: fuse close to the battery positive terminal, size the wire for the fuse rather than the other way around, and avoid undersized Powerpole crimps. Check the BMS specs, since many cells shouldn't be charged below freezing unless the battery has low-temperature protection or heating. A fully charged LiFePO4 can sit near 13.4 to 13.6 V under light load and sag toward 12.8 V as it discharges, so confirm your gear is happy across that range and that your charger or solar controller has a proper LiFePO4 profile. On the generator: using it only for recharging is a sensible approach. An inverter generator is quieter than a conventional unit, but its output can still produce RFI from the engine ignition and the inverter electronics, and the noise from the charger or power supply you plug into it can be worse. The safest pattern is to run the generator some distance away, charge the battery, then shut it off during critical HF operating. If the generator must stay on, keep it downwind and well away from the shelter, put a CO alarm in the tent, never run it inside or near openings, and use a GFCI-protected cord. Let it cool before refueling, and store fuel away from the operating area. If you backfeed or tie into a building circuit, do it only through a properly installed transfer arrangement, never with a male-to-male cord. One more noise point: switching supplies and cheap USB chargers are some of the biggest field noise sources. Keep an identical 'quiet' test: with the battery alone, note the HF noise floor, then add one device at a time and watch the S-meter or waterfall.
  5. The St. Louis & Suburban Radio Club's November general meeting is a hands-on antenna build. Pete Nowikow KFØOQA leads members in building an End Fed Half Wave (EFHW) wire antenna, including winding the matching transformer. The club also plans a short talk on how the antenna works and on build techniques. A short business meeting starts at 7 PM, followed by the build. Attendees who want to take an antenna home buy a kit from the club store.Location: St. Luke's North Medical Office Building, Lower level Rooms 1&2, 222 S Woods Mill Rd, Chesterfield, MO 63017, USA Organizer: St. Louis & Suburban Radio Club (SLSRC, W0SRC) Source: Event information
  6. On radio choice and filtering, it helps to ask what the strong-signal problem actually is before buying a filter. If the issue is overload from a local broadcast station or a neighbor on a close band, a high-pass or band-reject filter at the antenna input may do more than a full BPF set. If it's a second transmitter on the same site, the BPF on each radio, or at least a stub or filter on the harmonics, is the usual solution. Filter specs for insertion loss, power rating, and rejection on the adjacent band should be checked against the actual use case. The comparison between radios is more nuanced than direct-sampling versus superhet. The IC-7610's dual receivers and the roofing filter options on the TS-890S and K3S are advantages when conditions are crowded. The G90 and KX3 have fewer controls for dealing with overload, but at 20 W or 10 W they often work in less demanding environments, and the amplifier and external tuner arrangement can matter more than the radio. I'd check each radio's measured performance from independent lab tests and not rely only on the brochure specs. For amplifiers, I would also verify that the radio's ALC and output power settings match what the amp needs. A rig set to full power into an amp that needs 50 W can produce splatter even when the SWR looks fine, and that is easy to miss without a monitor scope or a second receiver.
  7. On 2 m and 70 cm, I'd think about the system in two parts: how many dB you can add cheaply, and how many you can only get by building something larger. The cheap ones come first. Move the preamp to the antenna, replace lossy relays and coax, and make sure the receive side is not being degraded by your own transmit chain. After that, the next dB of gain usually means more Yagis or a bigger dish, and each doubling of the antenna area is worth about 3 dB. Polarization is easy to underestimate on 2 m. Even with a decent array, a fixed horizontal antenna may leave you with a very uneven picture of who is hearable. If the budget allows, a way to switch or rotate polarization is worth planning for from the start rather than adding later. Also, for early skeds, it is more useful to pick stations with large arrays than to wait for stations about your own size. That gives you a better chance of confirming that your transmit, receive and tracking all work before you try weak-to-weak contacts. On 70 cm, the narrower beam means a mount that tracks well matters. Sun noise measurements are a useful way to check pointing and receive performance without waiting for a partner.
  8. One practical point on measuring: calibrate at the analyzer port or at the end of the cable, and know what you are measuring. If you measure through a long coax run without a choke, the shield can carry current and change the reading, so the number may drift when you move the cable or touch the analyzer. Fix that first, then trim the antenna. In EZNEC and MMANA, two settings catch people out: segmentation and ground. Too few segments, or very different segment lengths where wires join, can give unreliable impedance. A low horizontal wire or a vertical with radials near the ground is also sensitive to the ground model. MMANA's treatment of real ground is simpler than NEC-based programs, so for low antennas compare a couple of ground assumptions, such as average and poor soil, rather than trusting one number. If the resonant frequency predicted by the model is within a few percent of what you measure, that is usually a good result. What matters is that the model predicts which way and roughly how much each trim will move the resonance.
  9. On the audio chain, the quickest check is to watch your own transmitted signal on a second receiver or an SDR. A clean FT8 or PSK31 signal should look like a few tidy tones with nothing around them. If you see a skirt of spurs on either side, the level is too high somewhere, whether in the PC mixer, the interface gain, or the radio's data input. Windows is notorious for enhancements, system sounds and automatic gain getting in the way, so the sound card should be set to a fixed level with all effects disabled. Many rigs also behave differently on the rear data connector compared with the USB codec, so check which input your menu is routing to and which gain setting applies to it. A related habit: don't judge power by the wattmeter alone on a mode with a constant envelope like FT8. A steady carrier-like output with a tiny bit of ALC action is usually a good place to be. If you run a linear amplifier, low drive and low duty cycle are even more important, because the amp and the radio are heated continuously over the whole 12.6 seconds of an FT8 transmission.
  10. One thing people often get wrong is how vanity eligibility works. Your operator class decides which groups you can request from. A General can ask for a Group C 1x3 or a Group D 2x3 call, but not a 1x2 or a 2x2. If you upgrade to Extra later, you then become eligible for Group A and B calls, so some people wait to apply until after the upgrade. Another point is the order of your choices on the form. The system works down your list and grants the first one that is available and valid, so put your real favorite at the top, then fill in realistic alternatives. A long list of callsigns that are all likely to be taken doesn't help much. Also check the call's history before applying. Some calls look open but are still inside a waiting period, or are blocked for a reason that is not obvious from the format. ULS will reject the application, and the fee and the time are lost.
  11. until

    The club's regular meeting is held on the fourth Saturday (except some November and December meetings) at 10am at the Paris Municipal Court. Visitors are welcome to join.Location: Paris Municipal Court (listed in the event's venue data as Paris Police Department), 2910 Clarksville St, Paris, TX 75460, United States Organizer: Red River Valley Amateur Radio Club (RRVARC Officers; listed organizers Mark Johnson (W5PTX) and Phillip Beall (W5EBC)) Source: Event information
  12. One thing to add on the EFHW: the "no tuner, no radials" pitch is only partly true. The transformer needs something to push against, and in many installs that something is the coax shield. If the coax run is an odd fraction of a wavelength on some band, the common-mode current changes and so does the SWR, and RF can show up in the shack. A choke near the feedpoint or near the radio, or a purpose-made counterpoise wire, usually makes the antenna behave more predictably. Also check how the transformer is rated. A 49:1 unit handling 100 W SSB is a different job from the same unit handling 100 W of FT8 or RTTY, and some compact cores can get warm. For verticals, if you cannot lay many radials, elevated tuned radials are worth considering over a handful of short ground wires. Four radials raised a few feet can outperform a few buried ones, and they are easier to hide at the edge of the lawn than a field of surface wires.
  13. Good thread idea. For anyone deciding what to buy first, I'd suggest starting with the question "what do I want to do in the next month?" rather than "what's the best radio?" If the answer is local repeaters and nets, a handheld plus a better antenna is a sensible, low-cost path. If it's HF, budget for the antenna, coax, and some way to deal with noise and common-mode current, not just the transceiver. A few common mistakes worth avoiding: transmitting before you know your radio's settings, buying several cheap items you'll replace later, putting up an antenna anywhere near power lines, and assuming a high SWR reading is the whole story about how well an antenna works. Also, read your local rules on identification and permitted operation before you get on the air. When in doubt, ask a licensed local operator or your club.
  14. Start with the legal/voluntary split. Part 97 (mainly 97.301 to 97.313) sets which frequencies each license class may use, which emission types are allowed in which segments, and the power limits. Those are rules. The ARRL band plan is a voluntary agreement about how to share the space inside those limits. It's why FT8 clusters at 14.074 and SSB doesn't sit on top of the RTTY/data segment. Ignoring it won't usually draw FCC attention, but you'll get QRM and some pointed comments. On privileges, the HF picture for a US licensee looks like this. Extra has all amateur frequencies. General has all of 160 m, 30 m, 12 m and 10 m (30 m is CW/data only, 200 W PEP). On 80, 40, 20 and 15 m, General is limited to parts of each band, and the Extra-only portions sit at the bottom of the phone and CW/data segments. For example, General phone on 20 m starts at 14.225 MHz and on 15 m at 21.275 MHz. On 80 m, General phone is 3.800 to 4.000, and on 40 m it's 7.175 to 7.300. Technicians get CW on parts of 80, 40 and 15 m, plus 10 m from 28.000 to 28.500 MHz (28.300 to 28.500 includes SSB phone), with a 200 W PEP limit on those HF segments. Above 50 MHz, Technician and General have essentially the same privileges as Extra. Advanced licenses are no longer issued, but existing holders keep their slightly larger sub-bands. Verify exact numbers against the current rules. On band edges, the number that matters is the edge of your emission, not your dial. In USB, the signal extends upward from the displayed carrier frequency, by roughly 2.5 to 3 kHz for a normal voice signal. In LSB, it extends downward. So at the General phone edge on 75 m at 3.800 MHz, an LSB dial at 3.800 puts part of your signal in the Extra-only segment. Moving to about 3.803 or higher keeps the whole signal inside. At the top edge, such as 14.350 MHz, USB needs the dial a few kHz below that. Digital modes work the same way. FT8 dial frequencies like 14.074 are in USB with the audio tones adding a few kHz on top, so check where the actual signal lands. Leave a margin, because dial calibration isn't perfect either. For HF convention, LSB is normally used below 10 MHz and USB above, with 60 m being a special case, covered in the next reply. Digital activity concentrates near calling frequencies (FT8 at 1.840, 3.573, 7.074, 10.136, 14.074, 18.100, 21.074, 24.915, 28.074), and PSK31 and RTTY use their own subsegments. On 160 m, the DX window is traditionally around 1.830 to 1.840 MHz, and phone sits higher in the band. Check the current ARRL band plan for exact boundaries, because they get revised.
  15. For the vertical, a quarter-wave on 40 m is about 33 ft (roughly 234/f in MHz, in feet), which is why a fiberglass pole is popular: it's a non-conductive support, and the wire is taped or clipped along its length. The radial system is what decides how well the antenna works. Ground-mounted verticals need many radials. Quantity beats precise length, and 16 or more is a reasonable minimum, with more being better. Elevated verticals can work with fewer, tuned radials, and sloping them downward raises the feedpoint resistance toward 50 ohms. A common-mode choke at the base is useful here too, since the coax shield can otherwise act as an extra radial. Trap antennas are a trade-off. A parallel LC trap isolates the outer part of the wire on the higher band, which gives you multiband operation on one wire, but the traps add loss, narrow the bandwidth and need weatherproofing and voltage ratings suitable for the power level. For a first build, separate dipoles in a fan arrangement, or a single-band dipole with a tuner and ladder line, are usually easier to adjust than traps. Fan dipoles interact, so expect to trim in more than one pass. For modeling, EZNEC (NEC-based) and MMANA-GAL (MININEC-based) are good for checking the idea before building. Pay attention to segmentation, particularly where wires join and near the feedpoint. Model the real height, ground type and wire loss, and use EZNEC's average gain test to check the model is sound. Neither tool will tell you about common-mode current unless you model the feedline too. Real ground effects for radials near or on the ground are better handled by a NEC-based program than by MMANA. Treat the model as a guide to trends, such as how much a change in height or droop moves the resonance, rather than as a precise answer. Then build it, measure it, and trim.
  16. On HF I would make gateway selection the main decision. VARA HF and ARDOP are both usable, but the listing only tells you who exists, not who you can reach today. Pick a few candidate gateways at different distances, use the propagation estimates as a guide only, and try them in sequence. If your first attempt fails, check whether it was a connect failure (no handshake, a path or tuning problem) or a transfer failure (a link that dropped partway through, usually a power, noise or bandwidth problem). For forms, keep the sender and receiver in mind. An ICS-213 sent to someone who cannot render the form is just a block of XML-derived text. For served-agency work, agree beforehand on which forms and templates will be used and who has the viewer. P2P is a good fallback when you know the other station and can pre-agree a frequency and mode, but treat it as planned, not improvised, because there is no gateway to tell you the other station is listening.
  17. I'd put the order as antenna, then noise and common-mode control, then power, then the rig. A K3S or TS-890S won't beat a decent antenna system on a noisy band, and a lot of 'my receiver is deaf' problems come down to noise at the antenna, not the radio. On power, a quiet 25-30 A supply with fuses, short heavy leads and a ferrite on the DC cable is cheap insurance. If the noise floor changes when you switch the supply off and run from a battery, you've found the noise source. A simple test that costs nothing is to move the supply and the computer power bricks away from the radio and compare the S-meter on a dead band. For bonding, I'd separate the jobs the way you did. The AC safety ground and the lightning bond belong to the building's electrical system and need to follow local code, so it's worth asking a qualified electrician. The RF part is mostly about keeping the feedline from carrying common-mode current into the shack. A choke at the feedpoint and another near the entry point, plus keeping the coax from running parallel to AC cables, usually does more than adding ground rods. A test is to see whether touching or moving the coax changes the noise or the SWR, which suggests current on the outside of the shield.
  18. One thing worth adding on the Flex and Icom comparison is where the trust sits. With SmartLink, authentication goes through a vendor-run service, so you are depending on that service and on how you configure NAT or UPnP. With RS-BA1 or wfview you are usually on your own for how traffic reaches the radio, which is more work but also more control, and it fits neatly with the VPN approach. Neither is automatically better. It depends on whether you want to maintain a VPN or prefer the vendor's account model. On latency, I would measure before assuming. Ping time to the shack is only part of it, because audio codec settings, buffer sizes and jitter all add to the round trip you perceive. A link that shows a modest ping can still feel sluggish for a net or a pileup if the audio buffer is large. Try different codec and buffer settings, and test with the kind of operating you actually do. A DX pileup, a casual SSB rag chew and a CW contest each stress the link differently. As for rules, the practical step is to write down where the transmitter, the antenna and the control operator each are, and then check that against your licence terms and any award or contest you care about. Those three locations are what the rules usually ask about, and the answer isn't the same everywhere.
  19. On the first few QSOs: spot early, but only after you have actually found a clear frequency. Listen for a minute or two first, ask "is the frequency in use?", and only then call CQ POTA. If you spot first and then discover a net or a contest on top of you, you've sent hunters to the wrong place. Remember too that a spot is a tool for hunters, not a replacement for a good CQ. For cleaner logs while roving, many operators keep one file per park per UTC day instead of one big file for the whole trip. That avoids mixing up references at upload time. If a spot has a two-fer, log the same QSO with each park reference in the way the upload tool expects, rather than editing the file by hand afterwards. A quick check of the ADIF before upload is worth it for catching a typo in a call sign or a missing park field.
  20. One master log is the better choice, with a small number of fields you review regularly: DXCC entity, CQ zone, state or province, IOTA reference, POTA reference, SOTA reference, confirmation source (LoTW, paper card, other) and a note on whether you've applied. If those fields are blank or wrong, you can't tell which award a QSO supports. For paper QSLs, treat the request as its own workflow. Track the date sent, the route (direct, bureau, or a manager) and what return postage or fees the QSL manager asks for. Many operators in rare places take direct requests only through a specific manager, so check the QSL information on the operation's own page rather than guessing the address. Also remember that a card from a deleted entity or an old callsign is still valid for the award if the QSO is, but the entity and dates have to line up.
  21. The pool is divided into subelements (T0 through T9), and those are divided into groups. The exam draws one question from each group, which is how you get 35 questions. That means every group matters. You can't skip a whole topic and hope the draw goes your way, but you also don't have to master everything in extreme depth. Aim for a solid grasp of each group. I'd skip memorizing letter positions, because answer order is shuffled on the real exam and on most good practice tools. Memorize the idea behind the answer instead. Many wrong answers are built to look plausible, so if you know why the right one is right, the distractors get easy to spot. On math, it's lighter than people fear. You need Ohm's law (E = I × R) and the power formula (P = I × E), and you should be able to rearrange them. For example, 12 volts across a 24 ohm resistor gives 0.5 amps. A radio drawing 2 amps at 13.8 volts is using about 27.6 watts. You should also know the rule of thumb that wavelength in meters is roughly 300 divided by frequency in MHz, so 146 MHz is about 2 meters. That's where the "2 meter band" name comes from. For decibels, you mostly need to know that +3 dB is about double the power, +10 dB is ten times, and −3 dB is half. For privileges, the big idea is that Technicians get all amateur privileges above 30 MHz, which includes 2 meters, 1.25 meters, and 70 centimeters, plus limited HF privileges. Learn the specific limited HF segments and modes from your study guide, since the exam can ask where you're allowed to operate and what modes you can use there.
  22. Here is how the pieces fit. VEs and VECs. Amateur exams are given by Volunteer Examiners (VEs), who are licensed hams accredited through a Volunteer Examiner Coordinator (VEC). A session needs at least three VEs. The VEC is the umbrella organization, and ARRL VEC and Laurel VEC are two examples. The VEs are the local people in the room, often from a radio club. Finding a session. The ARRL has an exam session search by ZIP code, and HamStudy has a session finder too. Local radio clubs often post their schedules, and some VE teams hold remote sessions over video. Some sessions are walk-in. Others want you to register ahead, so read the listing and contact the team if the details are vague. Sessions can be cancelled or moved, so confirm a few days before you go. FRN and ULS. The FRN is a ten-digit ID you get by registering in the FCC's CORES system. It's free. Register before exam day and bring the number, because the VEs need it to file your application and many teams ask for it up front. The ULS (Universal Licensing System) is the FCC database where your license record appears. After you pass, your call sign is assigned and shows up in a ULS license search. Wait until you see yourself listed before you transmit. Make sure the email address in your FCC record is one you actually check, because the license is delivered electronically. Fees. The exam fee goes to the VE team or its VEC to cover costs and varies by team, so check the session listing. Fee rules can change, so verify the current FCC charge for a new license on the FCC's site or with the VE team instead of trusting a forum post, mine included. What to bring. Bring a photo ID, your FRN, a couple of pens or pencils, and a simple calculator if you want one (ask the team about their calculator rules). If you already hold a license, bring the original and a copy.
  23. On the plateau: it is often not one problem but two, and they need different fixes. One is character recognition that is still not automatic for the less common letters (Q, J, X, Z, numbers, punctuation). The other is word-level processing. A quick test is to take a plain text file with the 100 or so most common English words and have a trainer send it at your usual speed with normal spacing. If you copy it fine but struggle on real QSOs, the issue is probably the lack of context and noise tolerance, not the characters. A practice schedule that holds up for most people is short and regular, not long and occasional. Fifteen to thirty minutes a day beats a two-hour weekend session, because the recognition skill consolidates with repetition and sleep. A simple split for a half hour: ten minutes of new or weak characters, ten minutes of word or callsign drills just above your comfortable speed, and ten minutes of ordinary text at a speed where you get roughly 90 percent without strain. Keep the fast material as a stretch, not the main diet. For callsign drills, look at tools built for them, such as RufzXP, which sends callsigns and adapts speed to your accuracy, or Morse Runner, which simulates a contest pileup with noise and QSB. Callsigns are good practice because there is no context to guess from. You either got the characters or you did not. A simple method is to type the callsign, check it, and repeat the ones you missed. Also, don't switch to full-speed everything too early. Dropping the speed of the whole session to mimic on-air conditions can reinforce counting. Keeping the characters fast while stretching the spacing preserves the sound shape of each letter.
  24. On sound card setup, most problems come from audio levels, not from the software. Set the transmit drive so the radio's ALC is barely moving, since overdriving a sound card mode splatters and lowers throughput. Turn off processing, speech compression and any audio enhancement on the radio and in the operating system. Make sure the sound card and the PTT method are really the ones you intend. PTT might come from CAT control, a serial RTS or DTR line, VOX or a CM108-style GPIO interface. Run a test transmission into a dummy load or at low power before you go on the air. For packet with a software TNC, confirm how the client connects to the TNC. Typically that is KISS over a serial or virtual port, but check what your Winlink Express version and your TNC software support, because menus and options vary. P2P is worth practicing separately from gateways. Both stations must choose the matching P2P session type, one side listens and the other connects, and the messages need to be waiting in the Outbox first. P2P messages stay between the two stations and are not relayed through the Winlink system, which is what you want when no gateway or internet is available. Winlink Wednesday is a community practice session for sending test messages. The details are set by its organizers, so check the current instructions from official Winlink sources before joining. Use it to test your Telnet account, one RF mode, and an ICS-213 form, and keep attachments small. Radio-only messages are another feature to test, because they are meant to stay on RF paths and not be forwarded over the internet, which limits who can receive them. Read the current Winlink documentation for the exact restrictions.
  25. On NVIS, the number to watch is foF2, the critical frequency, not the SFI itself. For a steep-angle path, a signal goes through the ionosphere if its frequency is above foF2, and you get a skip zone. In practice that means 40 m may serve regional coverage by day, and 80 m or even 60 m takes over at night when foF2 falls. In a low-activity part of the sunspot cycle, 40 m at night can already start to skip over nearby stations. A horizontal antenna fairly low (roughly a tenth to a quarter wavelength up) helps keep the radiation angle high. The D layer matters here too: the lower you go in frequency, the more daytime absorption you get, so 80 m NVIS can be poor at noon even when the ionosphere would refract it. That's a reason to have a choice of bands, not a single favorite one. For the original question about predicted versus actual openings, I'd say a prediction is a prompt to go and check. A beacon on 28.200 MHz, or a 6 m beacon, costs nothing to listen to for a few minutes. If you hear the beacon and nothing else, that is useful: the path is there and people are just not on. Sporadic E especially can open and close within minutes, so no model will give you more than "this is the season to listen."

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.