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_Tom

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Tom

  1. On antennas, an end-fed half-wave with a 49:1 transformer is a common starting point. It is light, resonant on one band, and fed with coax, which keeps losses and common-mode problems manageable. Its drawback is that each band needs its own wire length or a trap or link arrangement. A resonant inverted-V dipole on a light mast usually wins on efficiency when you can find a support, because it needs no matching network or counterpoise and the feedpoint is easy to understand. A random wire with a 9:1 unun and a counterpoise is more flexible, but the tuner has to do more work, and losses in the matching system come straight out of your 5 W. Whatever you choose, put a choke at the rig end if you see RF in the shack or strange SWR changes when you touch the equipment. Height and clear surroundings often matter more than the antenna type. One practical tip is to take a short, measured length of coax and a small SWR or antenna analyzer reading at the site. A few minutes spent confirming resonance saves a lot of calling into a mismatched antenna.
  2. On OQRS, the main thing is to follow the station's instructions to the letter. Some want the request submitted on the Club Log page, then payment by the method they list, while others only handle bureau cards. If your QSO doesn't appear in their log, check the time, band, and callsign for typos before sending the request. Also look for notes like "LoTW only" or "no direct cards" so you don't pay for something they won't fulfill. For mailing direct, keep it simple. Include a clearly printed SASE, the right return postage or dollars, and a card with your QSO details already filled in so there's nothing for them to work out. A plain envelope without call-sign markings on the outside is common for safety in some countries, but check whether the station has asked for something particular. As for cards, a clean layout with a big callsign and a blank-ish back beats a busy photo that hides the QSO data. Whoever handles hundreds of cards will thank you for that.
  3. On paddles versus practice, the equipment can matter if it is actively fighting you. Signs include contacts that bounce, a spring tension that tires your hand, or a base so light that it walks across the desk. Those are mechanical issues and a different paddle can fix them. If your sending is uneven because you are guessing at timing, a better paddle will not solve it. Recording yourself and listening back, or sending to a decoder as a rough check, will show whether the problem is spacing or the hardware. One caution on decoders: if yours reads your sending perfectly, that only means your timing is regular enough for software. A human at the other end tolerates a lot more variation than a decoder does, but it is still a useful test of character spacing. For bugs, expect a longer learning curve than with paddles. The dahs are fully manual, and the dit weight and spring need adjustment before the rhythm feels natural. If you are curious, a straight key is the better stepping stone because it teaches the same manual dah timing.
  4. The GMRS/FRS point deserves emphasis because there's a lot of confusion. Many blister-pack radios are FRS-only and need no license. Some combo radios cover both services, and using GMRS power or GMRS repeater channels needs a GMRS license. Check what your radio actually is before relying on it, and avoid assuming a ham license transfers. For family use, MURS can be a decent fallback to FRS because the antenna can be mounted higher, but you need radios that actually support it, and the options are fewer. Whatever you choose, test it in the places you'd actually use it: inside a house, across a neighborhood, between a car and a building. Advertised range figures on packaging are almost never what you'll get. On power, I'd suggest a simple practical test: run your radio setup for a few hours off the battery and solar panel you plan to use, and log the voltage. It will teach you more than any spec sheet, and it shows whether your wire gauge, fuse, and connectors behave well under real load.
  5. For phone and portable use, the main thing is to keep the setup simple. A callsign lookup app, the POTA or SOTA spotting page, and an offline repeater list cover most of it. With RepeaterBook, download or export what you need before leaving cell coverage, because live lookups don't help on a mountain or in a remote park. Also treat the data as a starting point: confirm the tone and offset on the repeater's own listing or by listening, since entries can be out of date. If you do POTA or SOTA hunting, filter the spots by band and mode so you aren't scrolling through everything. Many hunters keep the spot page open next to their logging software. When activating, spot yourself with accurate frequency and mode, and update the spot if you QSY. Stale spots frustrate hunters and can send people to an empty frequency. On grids: learn to read a six-character Maidenhead locator at a glance, and keep a map tool handy to convert a lat/long or address. It makes contest exchanges and portable logging much less error-prone. HamCalc is good for quick antenna or coax-loss checks when planning a field setup, though double-check the results for anything critical like power handling or safety.
  6. On charts and flashcards: it's best to avoid learning by looking at dots and dashes. If you memorize "A is dot-dash" visually and then have to decode it when you hear it, you build a translation step that slows you down later. Most beginner advice is to learn characters as sounds, where "di-dah" is the sound of A and not a picture to be converted. Flashcards are fine if the card is the sound and your answer is the letter. Many apps work this way, with audio played first and an answer typed in. Visual-only cards are the ones to skip. For moving from paper to head copy, there is no switch, but a common progression looks like this: First, copy on paper with no pressure to keep up. When you miss a character, let it go and write a dash or leave a gap. Chasing the one you missed makes you miss the next two. Second, once individual characters are automatic, practice with common words and callsigns. Callsigns are especially useful, since they are short, random, and what you will hear first on the air. Third, try just listening with no pen, and say the letters or words in your head, or out loud if you're alone. Starting with short words and gradually going longer works better than trying to hold a whole sentence at once. Many people find it helps to deliberately stay a character or two behind the sender. This keeps you listening to the current sound while the previous one finishes resolving. For confidence, two things help. One is sending. Learning to send with a straight key or paddle and a keyer, and recording and listening back to your own fist, gives you feedback on timing. The other is making the first contacts low-stakes. Slow CW QSOs, beginner-friendly nets, and scheduled practice sessions exist for exactly this reason, and operators generally are patient with newcomers. A simple script helps: callsign exchange, signal report, name, location, thanks. Having the structure memorized means you only need to copy a few variable items. If you lose it, sending "?" or asking for a repeat ("AGN" or "PSE QRS" to ask for slower sending) is normal practice and not an embarrassment. For sessions, short and daily beats long and occasional. Fifteen to thirty focused minutes is a common recommendation, and you will probably notice that things improve after a break or a night of sleep.
  7. On the Smith chart, you don't need to be able to design a matching network with it. The exam mostly asks you to read it. Learn these few facts and you'll cover most of the questions: The center of the chart is the normalized impedance 1 + j0, which is a perfect match to the reference impedance.The outer scale is marked in wavelengths, and one trip around the whole circle is a half wavelength of line.Moving toward the generator is clockwise.A circle centered on the chart represents a constant SWR. Move along the line and you trace that circle.The top half is inductive reactance and the bottom half is capacitive.Normalization trips people up. If a question gives you a 50-ohm reference and a 100-ohm load, you plot 2.0, not 100. For antenna theory, pay attention to units, since several questions turn on them. dBi is 2.15 dB higher than dBd for the same antenna. ERP is referenced to a dipole and EIRP to an isotropic radiator. As a quick example, 100 W with 3 dB of feedline loss leaves about 50 W at the antenna. A 6 dBd gain antenna roughly quadruples that, so the ERP is around 200 W. Walk through a few of those with a calculator and the question-pool versions get much easier. One caution on drilling: question pools get revised on a regular schedule. Make sure whatever practice tool you use matches the pool currently in effect, and confirm that with the volunteer examiner team or VEC running your session.
  8. One thing I'd add to the SWR section: separate a real mismatch from a false reading by testing with a known-good dummy load and an external wattmeter. If the external meter shows sensible forward power and almost no reflected power but the rig still complains, the problem is the rig's sensing circuit, not the load. If the external meter agrees with the rig, then look at filter relays, the antenna switch and the connector or jumper between the PA and the antenna socket. High reflected power can also come from a damaged low-pass filter, not only from the antenna. For noise, a little method helps. Note which bands it affects, whether it changes with supply voltage or the volume setting, and whether it follows the display or the backlight. A fixed spacing of birdies often points to a switching regulator or clock harmonic, while a rough buzz that moves with load suggests supply filtering. An SDR or a spectrum analyzer shows those patterns better than listening, but even a handheld AM radio held near the board can help you find the source. With electrolytics, an ESR meter beats a capacitance reading, because a part can measure close to its marked value and still be too high in ESR for a switching supply. And before you reflow a suspect joint, check whether the board has a hairline crack nearby. Reheating one joint can hide a mechanical fault for a while without fixing it.
  9. On the antenna types, I'd split them by what the pattern does rather than by name. A collinear is a stack of phased half-wave sections, usually vertical, so it is omnidirectional in azimuth with a flatter elevation pattern. A short one might give around 3 dBd, and longer ones more, but the longer the antenna, the narrower the vertical beam. That makes mounting height and mast plumbness matter more. If the mast leans or the antenna is mounted on a sloped roof, a high-gain collinear can point part of its beam away from where you need it. A yagi is the opposite approach: you trade coverage for directivity. A three- or four-element yagi has useful gain and front-to-back rejection, which can help with a noisy side or a weak repeater in one direction. Polarization is the catch. Most FM repeater and simplex work is vertical, so a yagi for that has to be mounted with its elements vertical. Weak-signal SSB/CW work on VHF and UHF is traditionally horizontal. Cross-polarized stations lose a lot of signal in theory, often well over 10 dB in practice, though reflections and local conditions can soften that. For mobile use, NMO is a good mount because it is mechanically solid and keeps the connection to the whip consistent. It needs a hole, so it is a commitment. A mag mount is quick and removable but depends on a flat metal surface under it, a clean contact, and a cable route that does not pinch the coax. Roof center usually gives the most symmetrical pattern. A trunk-lip mount can skew the pattern because the body blocks some directions. Dual-band mobile whips are often a compromise, with different effective gain on 2 m and 70 cm, so check the manufacturer's data for both bands.
  10. On the failure mode question, the answer needs to be layered, and the network software shouldn't be the only layer. A transmit timeout in the radio is the first one. Many rigs have a TOT setting, and it is worth setting even though it is crude. Next is a heartbeat or watchdog in the remote software, so that loss of the control connection drops PTT. Finally there is hardware you can reach out of band: a network-controlled power switch for the radio and amplifier, ideally on a different path than the main link, such as a cellular backup or a separate switch on the router. The amplifier is the item people forget. If your remote setup includes a linear, think about what it does when the exciter goes silent, when SWR rises, or when the antenna tuner is in an unknown state. I would also push back a little on the idea that a VPN settles the matter. It reduces exposure, but it does not fix weak passwords on the Pi or on the radio's own network login, and it does not fix a client PC that is already compromised. Treat the remote client like a key to the shack.
  11. On the 44-QSO target, I'd plan for two bands from the start rather than hoping one holds up. A common approach is to start on the band with the best expected propagation for the time of day, work the pileup until it thins out, then move and re-spot. Hunters who missed you on the first band often show up on the second. If the park allows it, CW and SSB together can also help, because it pulls in two different groups of hunters. FT8 or other digital modes can fill the gap if the rules allow them, but check that the WWFF program accepts that mode for the award or activation you're after. On dual-reference operating, I'd also say the reference twice in each exchange, one program at a time, so the hunter can log it without asking. Something like "KFF-1234 and K-5678" gets old fast, but it prevents repeats when the band is noisy.
  12. On question 3, treat safety grounding, lightning, and RF grounding as separate concerns. A ground rod at the station is fine for bonding equipment together and can help bleed off static, but it won't turn a dipole into a good antenna, and it won't make a field station safe in a thunderstorm. If lightning is nearby, the correct move is to take down the antenna, disconnect feedlines, and get people into a proper shelter, not to rely on a rod. Bond the radios, distribution block, and any metal mast or equipment frames together with short, heavy leads so there's no voltage difference between them. For most field antennas, the RF performance issue is common-mode current on the coax. A dipole or EFHW often works better and quieter with a good choke at the feedpoint. A common approach is a stack of ferrite beads or several turns of coax on a suitable core (mix 31 is common for HF). An EFHW also needs its matching unit and a counterpoise, and it's worth checking SWR and noise with the coax draped in different ways, since a feedline that's part of the antenna will also pick up noise from the shack. Coax losses are worth checking against your actual runs. At HF, even smaller cable like RG-8X is fine for short runs. At 2 m and 70 cm, loss climbs quickly with length. A long run of thin cable can eat a big chunk of a 50 W signal and hurt receive just as much, so put the VHF/UHF antenna as close to the radio as the situation allows, or use lower-loss cable if you need height. Add drip loops, strain relief at the mast and at the radio, weatherproofed connections, and a cable ramp where people walk. Label both ends of every cable. The mast needs its own checklist: check the wind rating, guy it at the points the manufacturer specifies, stake or ballast the base properly, flag the guy lines, and put the mast where its fall zone doesn't reach any power line or the tent. If there's any doubt about wind, plan to lower it. For the setup list, I'd add the items people tend to forget: a written power plan and fuse map taped inside the tent, spare fuses and Powerpole contacts with a crimper, a multimeter, an antenna analyzer, a battery-powered receiver for noise checks, and a printed frequency plan that matches whatever the served agency expects. For teardown: shut down in order (transmit gear off, then distribution, then battery), photograph or note the connections before disassembly, coil coax loosely, check for damaged connectors before they go back in storage, recharge and cycle batteries soon after, and refill or label the fuel. After the event, jot down what failed or got noisy so the next deployment improves on it.
  13. On HF sub-bands: you do need the General class privileges, but learn the structure rather than every digit. HF bands are split into CW/digital segments and phone segments, with phone typically at the upper end of each band. 60 meters is a special case with its own channelized rules, and 30 meters has a lower power limit and no phone. A band chart from the ARRL or a similar source is worth printing and keeping nearby. Use it to check frequencies, since exam questions sometimes ask for a specific edge, and verify against Part 97.305 if you're unsure about a detail. Beyond the exam, remember that Technician privileges on 80, 40, and 15 meters are CW only, and 10 meters allows some phone and data. Learning what General adds helps you remember it: more phone segments on 75/40/20/15 meters, plus access to 160, 30, 17, and 12 meters. Propagation: the usual mistake is memorizing layers without understanding why they matter. The D layer absorbs lower frequencies in daylight, which is why 80 and 40 meters work better at night for longer distances. The F layer refracts higher frequencies, so 20 meters and above depend heavily on ionization levels. Know what MUF means, and the difference between solar flux and the K and A indices. Higher solar flux generally helps higher-band propagation, while a disturbed geomagnetic field often degrades it. Gray-line propagation is also tested, so understand what happens around sunrise and sunset. Antennas: know the basics of a half-wave dipole, its approximate length formula (468 divided by frequency in MHz gives feet), and what SWR means and what it doesn't. A low SWR doesn't prove the antenna is efficient, and feed line loss increases with frequency. Also be familiar with verticals, Yagis, ground radials, and what happens to the radiation pattern at different heights. Draw a few patterns by hand if you can. Digital: understand how modes like FT8, PSK31, and RTTY are used on HF, why a data mode needs enough bandwidth for its signal, and that regulatory limits are written in terms of symbol rate in baud for certain bands. Know the station identification rules and who counts as the control operator, because those come up often. Sound-card interfaces, audio levels, and avoiding overdriving the transmitter also show up in questions about clean signals.
  14. I'll take the first four. Identification (§97.119). You must give your call sign at the end of each communication and at least every 10 minutes during one. You don't have to ID on every transmission, and a long ragchew only needs the 10-minute ID plus the final one. Identify in the mode you're using: English phone, CW, or the appropriate data or image method. On phone you may use the standard ITU phonetics. Tactical names like "Net Control" or "Shelter 2" are fine during exercises and public service events, but the FCC-assigned call sign still has to go out on the same schedule. On a repeater, the repeater has its own ID obligation, separate from the users. Third-party traffic (§97.115). A control operator has to be present at the control point and is responsible for the communication. Domestic third-party messages are generally fine, and unlicensed people can talk on the air under your supervision. The limits are that the traffic can't be prohibited business-type traffic, and the third party can't be someone barred from being a control operator, for example because their license was revoked. Internationally it is much narrower. Third-party traffic is generally allowed only with countries that have a third-party agreement with the US, and emergency situations are handled separately. If a station isn't in an agreement country, don't pass third-party messages. A foreign ham simply handing the mic to a family member is a common trap. Prohibited transmissions (§97.113 and §97.101). The main ones: Communications in which you or your employer have a pecuniary interest. There are narrow exceptions, such as a teacher using amateur radio as part of classroom instruction, or occasionally selling your own station equipment.Music, except as incidental to certain space operations.Obscene or indecent language.False or deceptive signals.Messages in codes or ciphers intended to obscure their meaning. This is why encrypted voice or data on the amateur bands is a problem. Protecting a control link is a separate matter from obscuring the content of communications, and the rules treat the two differently.Broadcasting and rebroadcasting commercial broadcasts.Willful or malicious interference (§97.101(d)).Power (§97.313). The general ceiling is 1500 W PEP output, and you must use the minimum power necessary to carry out the communication. That limit applies to transmitter output, not DC input. There are lower limits in some places. 30 meters is 200 W PEP, and the Technician HF phone and data privileges on 10 meters (28.3–28.5 MHz) have a 200 W PEP limit. 60 meters has separate channel and effective radiated power rules, so check the current text. License classes (§97.301 and following). Technician, General, and Amateur Extra are the classes currently issued. Novice and Advanced licenses are no longer issued, but existing ones can still be renewed. Technicians have all amateur privileges above 30 MHz plus limited HF segments. Generals have most HF privileges, and Extras have all of them. The class defines your frequency privileges, and it also limits what you can do as a control operator at someone else's station.
  15. On antennas, the best choice depends heavily on band. For VHF and UHF listening, a discone or a simple ground-plane cut for the band of interest is a reasonable start. Remember a wideband antenna passes everything, including strong broadcast and paging signals, so filtering matters more. For 1090 MHz ADS-B, a tuned antenna and short, low-loss coax usually matter more than the dongle. If an LNA is used, putting it at the antenna end overcomes feedline loss, but it also reduces the headroom for strong signals, so it can be counterproductive in a crowded environment. At HF, external noise usually dominates, so a very low receiver noise figure is often not the bottleneck. A small magnetic loop, an active loop or a random wire with a matching transformer can all work, and the deciding factor is often how quiet the location is. A common-mode choke at the feedpoint and another near the receiver is cheap and often reduces noise pickup on the coax. A panadapter setup is a separate case. It taps the transceiver's IF, so a buffered, high-impedance tap is important to avoid loading the radio. In software, CAT control (for example via OmniRig in HDSDR) keeps the display frequency in step with the rig. Check the manual for your rig's IF frequency before wiring anything.
  16. I'd start with the digital stack, because it's the cheapest way to get a lot of confirmations and it sets up everything else. For LoTW, the certificate request is the part that trips people up. The callsign certificate is tied to a specific callsign and DXCC entity, and you have to complete the verification step before you can upload anything. If you hold a US call, ARRL has typically mailed a postcard with a code to the address on your license record. Plan for that delay instead of discovering it right after a big contest weekend. Once the certificate is installed, back up the certificate file (the .p12) somewhere safe. Certificates expire, and a dead laptop with no backup means redoing the request. Also make sure the QSO dates in your log fall inside the date range your certificate covers, or the uploads will be rejected. Log hygiene matters more than people expect. LoTW matches on band, mode group (CW, phone, data) and time, so a QSO logged in local time instead of UTC, or logged as SSB when it was FT8, will quietly fail to match. Set your logging program to UTC, and let it fill in mode and band from the rig where possible. Upload regularly rather than in one giant batch every year. Your confirmations arrive when the other station uploads, not when you do, so frequent uploads keep your side current. For the rest, I'd treat them this way. eQSL is fine if the people you work use it, and it's good for general collecting, but it won't count toward DXCC. QRZ's logbook is handy as a master log, and it can send records on to LoTW and Club Log through its tools, though some of the API features may need a paid subscription, so check what yours includes. Club Log is worth uploading to even if you never request a card. It gives you an entity-by-entity view of what's confirmed and what isn't, and many DXpeditions use it for their logs and for OQRS. A reasonable approach is to keep one master log, push it to LoTW and Club Log automatically, and then use the 'needed' lists to decide where paper is worth chasing.
  17. On going from letters to copying in your head, there are a few habits to build deliberately. First, stop trying to keep up with every character. Beginners usually fall behind because they dwell on a letter they missed, and then miss the next three. If you miss one, drop it, write a dash or leave a gap, and pick up with the next character. A missed letter costs you one character; chasing it costs you the whole word. Second, learn to copy slightly behind the sender. Let a character finish before you process it, then keep a short lag of a letter or two. That lag is what eventually lets you hear words rather than letters. Once you recognize common words and endings (THE, AND, ING, and so on) as single sounds, writing becomes optional. Many people find it helps to move from writing everything, to writing only call signs, names and numbers, to writing nothing during an easy exchange. Third, change your practice material as your skill grows. Random characters are good early on, but they don't teach word shapes. Mix in call signs, common words, and plain text, which most of the trainers mentioned above can generate. Call signs are especially worth the time, since they're the one thing you must copy accurately on the air and they can't be guessed from context. For confidence, the biggest step is shrinking the gap between practice and real operating. A few suggestions: Listen to real CW on the bands before you transmit anything. Standard exchanges (calls, signal report, name, location) are very predictable, and recognizing the pattern makes copying much easier. Your first contacts will go better if you can already anticipate what comes next. Practice sending as well. Send what you've just copied, or send to yourself and listen to your own timing. Clean spacing matters more than raw speed, and you'll be copied better for it. When you're ready to make contacts, look for slower CW, and don't be shy about saying you're a beginner. Plenty of operators will slow down for you. Slip-ups are normal, and a request to repeat something (a single question mark or AGN, for example) is a routine part of CW, not an admission of failure. Finally, expect plateaus. Progress is rarely smooth, and a week or two of feeling stuck usually precedes a jump. The usual advice is to keep the daily habit going and not to slow your character speed down in response.
  18. On CAT, pick one owner for the radio and make everything else a client. With a single physical serial port, the usual choices are a rig-sharing layer such as OmniRig, FLRig or Hamlib's rigctld, or a logger like DXLab's Commander that other DXLab apps share. A virtual COM splitter can work, but it adds one more thing to break at 0000Z when you're busy. Many modern radios also expose separate USB CAT and audio devices, which makes this easier. Whichever route you take, keep the baud rate, the data/stop bits and the radio's CI-V or CAT settings consistent between programs. Most 'frequency randomly jumps' reports trace back to two programs polling or writing at once. On where the logs live, I'd keep contest logs in the contest logger. N1MM+ builds its dupe sheet, multiplier tracking, score summary and Cabrillo header around its own database, and the contest definition holds the exchange fields. Importing contest QSOs straight into a general-purpose log works for archiving, but you lose the contest-specific fields unless the ADIF carries them. After the contest, export ADIF from N1MM+ and import it into your master log. Check that CONTEST_ID, STX/SRX or the exchange strings, and the frequency survived. Then confirm that the import's duplicate detection doesn't throw away QSOs that are legitimate repeats on a different band or mode. For Cabrillo, the file is plain text, so open it before submitting. Check the CALLSIGN, CATEGORY lines, the operator list and the claimed score against what the sponsor expects. Sponsors differ on which categories and overlays they accept, so read that contest's rules rather than assuming last year's header is still right.
  19. On the CAT side, the question I would ask first is whether the radio or its driver exposes more than one control path. Some radios present multiple virtual serial ports over USB, but how they are used differs between models and drivers, so check the manual. If you only get one CAT port, rigctld or flrig as a broker is usually less fragile than splitting the serial port at the OS level. WSJT-X can talk to Hamlib's network rig control, and N1MM Logger+ has its own rig options, so check what your version supports before committing to a design. For band maps and dupe checking, remember that N1MM's band map is only as good as the frequency it reads and the spots feeding it. If you also have a digital program changing the VFO, you can end up with the band map jumping around, or QSOs logged with the wrong frequency. In a contest weekend I would close or pause the other programs that can retune the radio, unless you deliberately want them both in the chain. For the rotator, N1MM can send a bearing from the entry window or from a band map spot, but a conflict with other rotator software is the same story as the radio port: one owner for the hardware. If DXKeeper, Log4OM or HRD is also configured to command the rotator, turn that off while the contest logger is running. One last point on submission: after you generate Cabrillo, open the text file and look at the first few QSO lines before you upload. Check callsign, frequency, mode code, date and time in UTC, and the sent and received exchange. A quick look catches most problems that otherwise show up as a rejected or heavily penalized log.
  20. On the security side I'd go a step further than "use a VPN." Decide what your remote client actually needs to reach, and write that down. With an IC-7610 and RS-BA1 or wfview, that is the radio's control, serial and audio ports, which are commonly documented as UDP 50001 to 50003. Check your own manual, though, because ports can be changed and I wouldn't trust a forum post over the documentation. Once the VPN is up, a firewall rule that allows only your VPN subnet to those ports is much safer than relying on obscurity. A cheap managed switch or a router with VLAN support is worth it. Radios, Pis and cameras tend to run old firmware and are poor candidates to share a flat network with your laptop and NAS. If something on the radio VLAN gets compromised, it can't easily reach the rest of the house. On the legal side, I'd add that the person logging in is the control operator at the remote control point, so you need to be sure that only licensed, authorized people can ever key the station. Shared passwords on a family PC are a bad idea for that reason alone.
  21. The way to keep this manageable is to decide what each system is for. For DXCC, LoTW is the efficient path, so the habit is to log accurately, export or sync ADIF from your logging program, and upload on a regular schedule rather than in big dumps. The most common reason LoTW matches fail is sloppy data: wrong band, wrong mode, a time entered in local rather than UTC, or a callsign with a portable suffix that doesn't match the other operator's log. If you run mixed modes, remember that LoTW compares mode groups (CW, phone, data), not every individual mode name, but check it against your own award category. Paper is still worth it in a few situations. Some DX stations or DXpeditions never upload to LoTW, so a direct or OQRS card is the only route. Some people also simply enjoy cards, and a card from a rare entity is more satisfying than a green dot in a database. For those, I'd pick direct only when the operator or manager's instructions say direct is preferred or when the bureau is known to be impractical for that location. Otherwise, bureau is the economical default for stations that handle it properly. One practical point on direct requests: read the exact instructions. Some managers want a specific amount in cash, some want a card for each QSO, some want an OQRS request first. Following those details usually matters more than adding extras.
  22. On RST, it's a three-digit report. R is readability from 1 to 5, S is signal strength from 1 to 9, and T is tone from 1 to 9. Tone is only used on CW, so phone uses just two digits, RS. A solid voice signal is "five nine." A CW signal that is perfect is 599, which is also the default in contests whatever the signal actually sounds like. In casual QSOs an honest report is more useful. If the signal is weak and fading, give a lower strength number and mention QSB. Phone versus CW is mostly a question of what's natural. CW leans heavily on abbreviations because every character costs time. Common ones include PSE (please), TNX or TKS (thanks), UR (your), RIG, ANT (antenna), WX (weather), AGN (again), ES (and), FB (fine business, meaning good), OM (old man, a friendly term for a male operator), GL (good luck), and R (received). TU (thank you) is used constantly in contests, and BK means break, used for quick back-and-forth exchanges. On phone, plain language usually sounds better. People do still say QTH, QSL, QSY, QRM and QRZ on voice because they are quick and widely understood, but nobody needs "QRU" in a casual chat. For callsigns, use standard phonetics when conditions are poor, such as "Whiskey One Alpha Bravo Charlie." Avoid CB-style 10-codes on amateur bands. They aren't standard ham practice and tend to make you stand out for the wrong reasons. For logs and nets, a basic log entry has date and time in UTC, callsign, band or frequency, mode, RST sent and received, and often name and QTH. Contest and award logs add grid squares or park and summit references. QSL confirmations come in different forms, such as paper cards direct or through a bureau, or electronic systems like LoTW and eQSL. Net terms include net control (NCS), who runs the net, check-in, traffic (formal messages being passed), relay, and roll call. Some nets use QNI for stations checking in and QTC for "I have traffic." Follow the net's own script, because each net sets its own procedures. One extra tip: QRZ the Q code and QRZ.com the callsign lookup site are different things. The site just borrowed the name.
  23. I'd begin with Telnet and put off RF until the account side is solid. The Winlink account password is case-sensitive, and it's the thing people most often get wrong. Register the callsign, log in over Telnet, send a message to yourself and one to a second Winlink address, and make sure you set a password-recovery email address in case you lose the password. Don't write the password on a shared sheet or in a group document. Each operator should have their own account, and peer-to-peer sessions don't need the password because they don't involve the CMS. On gateway selection, Winlink Express lets you download a channel list from the internet, so do that while you still have a connection and keep the list current. Enter your location or grid square so it can sort by distance and, for HF, show propagation estimates. Treat those as guides, not guarantees. The listed HF frequency is generally the center frequency, and if rig control is configured, the software works out the dial setting for you. If you tune manually, you have to account for that offset yourself. Listen before you transmit. If the channel is busy, wait or choose another one, because a gateway can only serve one connection at a time on a frequency. Regarding messages, the format over RF should be small. Compression helps text, but images and large attachments will be slow on HF and may be refused or time out at some gateways. Keep forms and text short. For people sending from ordinary internet email to a Winlink address, spam controls mean they might need to be on your whitelist, or they can put //WL2K at the start of the subject line. Test that path before you rely on it. ICS-213 and other forms are in the standard templates in Winlink Express. The form opens in a browser, and the message carries the data as a small attachment with a readable version in the body. The receiving person needs a client that can display the form, so confirm that before using forms with outside agencies. Update the templates periodically so everyone is on the same version. For Winlink Wednesday, check the current instructions from whoever is running the exercise, because the check-in format and addressing can change. It's a good low-stakes way to practice sending a message through a real gateway. On your last question: a normal gateway session uses an RMS to reach the CMS, so it depends on that gateway having its own internet link. Radio-only messaging is for traffic that should stay on the radio side and not go out to the internet, so read the current Winlink documentation for exactly how it's flagged and routed. A P2P session is a direct connection between two stations, such as VARA FM, packet, or ARDOP, with no gateway involved. One station listens and the other calls, and you need compatible modem settings on both ends. When the internet is down, P2P is the dependable fallback, but it only moves messages between those two stations. It doesn't deliver anything to the wider system until one of you can reach a gateway.
  24. For the math, the Technician pool keeps the calculations simple. You mostly need three relationships: Ohm's law: E = I × R, so 12 volts across 4 ohms gives 3 amps. Power: P = I × E, so 2 amps at 12 volts is 24 watts. Wavelength: roughly 300 divided by the frequency in MHz gives meters, so 146 MHz is a bit over 2 meters, which is where the "2-meter band" name comes from. Two related decibel facts also come up: +3 dB is about double the power, and +10 dB is ten times the power. Write the formula, plug in the numbers, and you can usually eliminate wrong answers quickly, even on a day when you can't recall a memory trick. As for where people lose points, the repeater items are a common trouble spot because they're easy to confuse. The standard offset on 2 meters is 600 kHz, and on 70 cm it's 5 MHz. The offset direction depends on where you are in the band. A repeater input and output are different frequencies, and many repeaters need a CTCSS (PL) tone on your transmitted signal to open them. Simplex means transmitting and receiving on the same frequency. Learn those as a set of connected ideas, and also learn the ID rule: give your call sign at the end of a communication and at least every 10 minutes during it. RF exposure questions are easier once you see the pattern. The factors that determine exposure are power, frequency, distance from the antenna, antenna gain and pattern, and duty cycle or transmit time. Questions often hinge on one of these: more power or closer distance means more exposure, and a mode with a lower duty cycle means less average exposure. For license terms, know that an amateur license is for ten years, and that there is a grace period after expiration during which you can still renew. The exact rules are in the FCC Part 97 text, so verify any detail you're unsure about there.
  25. The answer depends on what the person wants to learn. A Pixie-type transceiver is cheap and teaches a lot about how a transmitter final can double as a mixer, but it is a very rough receiver: wide, no real selectivity, and lots of out-of-band signals, so it can feel disappointing on a busy band. A crystal-controlled one-band transmitter like the Tuna Tin 2 is better for learning about oscillators, keying, matching, and output filtering, and it pairs well with a simple direct conversion receiver. A BITX is a bigger step because you are dealing with SSB generation, a crystal filter, bidirectional amplifier stages, and alignment. It is very rewarding but less forgiving without a signal source and a way to see what you are doing. On the instrument question, I would say a frequency counter or an inexpensive SDR used as a receiver for monitoring your own oscillator, before a scope. Many first-time problems are simply that the oscillator is not where you think it is, or it is running on a harmonic or overtone of the crystal.

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.