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. Adding to the above: club calls, special event calls, lookups and changes. Club callsigns. A club station license is issued to a trustee, who is a licensed amateur designated to act for the club. The call is held in the club's name, but the trustee is the named contact. Club license applications generally go through a Club Station Call Sign Administrator, which is a VEC-related service, and not through a regular individual application. Vanity rules for clubs are similar to individual ones, with the trustee's license class mattering for what the club can request. If the trustee changes, the license record needs to be updated, and a club shouldn't rely on one person remembering to do that. Special event calls. These are the 1x1 format calls, such as K, N or W followed by a digit and one letter. They're temporary and are assigned for a short operating period. Coordination isn't done by the FCC directly. A volunteer organization runs the Special Event Call Sign System, and you request one by submitting dates and the event details. You still operate under your own license privileges, and you still have to identify per Part 97. Station ID. Identify with your callsign at the end of a communication and at least every ten minutes during one. That applies the same way whether you have a sequential call, a vanity call, a club call or a special event call. Lookup. The authoritative source is the FCC's ULS license search, where you can see the class, grant and expiration dates, and the address on file. Third-party databases such as QRZ and others are convenient and often have more details, but they depend on what operators enter, so treat the ULS as the official record. Changes. If you move, update your address in ULS and keep your old call unless you want a different one. A change to a new callsign can be a sequential change or a vanity request. A sequential change gives you the next call in the system. A vanity request lets you choose. Which one is right depends on whether you care what the call is, and whether you care about the exact letters. Once you move to a new call, your old one goes into the waiting period before others can request it. Prefix and suffix practice also deserves a mention. Domestic US operating doesn't require adding a portable or mobile suffix to your callsign. When operating abroad, the rules of the country you're in and any reciprocal arrangements decide what prefix you use, so check those before you go.
  2. On names and locations, the simplest approach is to say the word first, then spell the part that might be misheard. That way the listener gets the likely sound and then the letters to confirm it. For example, say the town name normally, then "I spell" and the letters, using standard phonetics. Don't spell every word in a sentence, only the ones that carry the information: names, street names, unusual places, call signs and anything non-obvious. When conditions are rough, slow down and keep a steady rhythm instead of shouting. Pronounce each phonetic word fully and leave a very short gap between letters. Group long strings into small chunks, such as callsign prefix, number, suffix. If the other station says "say again," repeat only the part they missed rather than the whole message. "Say again" is the usual request, and "I say again" signals that you are repeating yourself. Avoid saying "repeat" in settings where it could be read as an instruction to repeat a message or fire, though that is more common in military procedure than ham use. Numbers can be spoken plainly in most casual ham contact. The ICAO aviation numeral pronunciations ("niner," "fife," "tree" and so on) exist to prevent confusion in poor audio. Hams often use just "niner" for 9, since "nine" can be confused with "five" or with German "nein." Using the full aviation set is optional, but clear digit-by-digit reading matters. Say numbers one digit at a time: "one two three," not "a hundred twenty-three," unless you mean a quantity. Regarding prosigns and procedure words, the true prosigns (AR, SK, BT, KN and so on) are mostly a CW matter, where they are sent as a single run-together character. On voice you use procedure words: "over" to hand the transmission back, "clear" or "out" to end the contact. Avoid saying "over and out" together because the two meanings contradict each other.
  3. For two-fers, the activation is for each reference, so you need 10 valid contacts counted for each park, not 10 split between them. Operationally that usually means spotting both references and announcing both in your CQ. Then make sure your logging software or the upload tool can attach both references to each QSO. Where the tool allows, check the reference field format before the trip, and keep to the format the POTA site wants, because mistakes there are the usual reason an upload gets rejected. Roving is the same idea stretched over several parks: you move from reference to reference and complete an activation at each one. The practical points are to plan each stop in advance, note the UTC time you start and finish, and keep each park's log separate. That makes the upload clean and saves untangling it later. If you roam across a UTC date change, those QSOs fall into different days, so plan the 10-QSO count around that. For logging in general, whether you use the POTA app, a paper log or logging software on a laptop, record the callsign, band, mode, UTC time and park reference at the moment of contact. Hunters can help here by logging park-to-park (P2P) contacts when they have them. Check the current award pages on the POTA site for the activator and hunter milestones. I wouldn't rely on remembered numbers, since awards and thresholds are updated.
  4. Here is the usual order of events, with the terms explained. Volunteer Examiners (VEs) are licensed amateurs accredited through a Volunteer Examiner Coordinator (VEC), and they run the exam sessions. The FCC doesn't give the test itself. A VE team checks your ID, hands you the exam, grades it, and submits your paperwork to a coordinator who files it with the FCC. Because each team and coordinator sets its own logistics, the exam fee and the payment methods can differ from one session to the next. Don't trust a number from a forum post, including this one. The session listing or the contact person for the team will tell you what to bring and in what form to pay. To find a session, search the listings that the VECs publish. The ARRL and some other coordinators have search tools by ZIP code or state, and many local clubs post their own exam dates. Some sessions are walk-in and many want you to register in advance so the team knows how many exams to bring. Remote sessions run over video also exist, but check that the team is accredited and read their technology requirements before you commit. On the FRN: it's your FCC Registration Number, and you get it by registering with the FCC's CORES system. The FRN is tied to you personally, and your license record in the FCC's Universal Licensing System (ULS) will be attached to it. Many VE teams ask that you already have it when you arrive, so get it a few days before the session. Make sure the name and address you register match your photo ID and where you want your license mailed or emailed. What to bring is usually: a photo ID, your FRN, payment, a couple of pencils, and a simple calculator if you want one. Ask the team about calculator rules. Some sessions ask that it be cleared of stored formulas. Treat the session announcement as the final word on what to bring.
  5. One more category worth adding: the weekend QSO parties. They often have a more relaxed atmosphere than the big DX contests, and if you live in a state that has one, in-state stations are usually in high demand, so even a small signal gets answered. Read the rules for your state and for any you want to chase, because county abbreviations and mode rules vary. On Field Day and Winter Field Day, check who runs each event and read that organizer's rules, since the classes and bonus structures aren't interchangeable. And for any contest, do a test export of your Cabrillo file before the event so you aren't troubleshooting a header field at the submission deadline.
  6. The best advice I can give is to read your county's emergency operations plan, or at least the communications annex, before you do anything else. It tells you who can request amateur support, which agencies you would be supporting, and whether the plan references ARES, RACES or both. Plans vary a lot from one county or state to the next, and the person who activates you may not be the person you assume. Also, don't self-deploy. Showing up at a scene or an EOC because there is a disaster is a good way to become a problem instead of a resource. Wait for a request through your Emergency Coordinator or the agency, check in with the net, and follow the assignment you are given. Most groups also expect you to log your time and keep a copy of your traffic. On the training side, ICS forms and structure make a lot more sense once you sit in an exercise. Even a simple tabletop or a drill with a simulated shelter and hospital will show you where messages get stuck.
  7. I would add that VOACAP is easiest to misuse by treating it like a forecast. It gives you a probability-style picture for a typical day in the month at a given smoothed sunspot number, so use it to plan windows, not to decide that a band is dead. For example, run your location to a target region, compare 20, 17 and 15 m by hour, and then confirm with spots. For NVIS, the question to ask is whether the frequency is below the critical frequency at the time, not whether the band is "good for DX." A good setup is a low horizontal antenna and a lower band for night operation, with a move up to 40 m or 60 m as the day brings the critical frequency up. If the contact fails, check whether you were above the critical frequency, because the signal will just pass through to space. WSPR can be useful for that regional check too. Even a few watts can show whether a short path is working, as long as there are enough receivers around. The limitation is the sparse station coverage in some areas, so no spots does not always mean no propagation. For sporadic E and ducting, I would say indices are almost irrelevant. Use cluster spots, beacons on 6 m and 2 m, and weather charts. If a beacon you normally cannot hear suddenly appears, that is a stronger signal than any forecast.
  8. On difficult conditions: the standard words are usually better than improvised ones, but only if you actually use them cleanly. A few habits that help more than switching alphabets: Say the callsign slowly and in a steady rhythm, with a small gap between letters and digits. Don't run the phonetics together. If the other station asks for a repeat, repeat the whole thing the same way first, because many repeat requests come from one dropped syllable rather than the callsign being unclear. If a particular letter keeps getting missed, that's when a swap makes sense. Some operators use alternative words for letters that get confused, such as Lima against another word for L, or Mike and November, which both end in similar sounds. Say "my callsign is... I say again... " and spell it out, but if you improvise, make the word obvious and common. Avoid obscure names or words that sound like another letter's word. For names and locations, spell only what's necessary. If a name is common, give it once and spell only the tricky part: "Name is Marek, M-A-R-E-K" using phonetics on the letters that might be mistaken. For a town, it's often quicker to give the town and the state or region, then spell it only if asked. Words like "Quebec" or "Kilo" inside the spelling of a name can themselves confuse listeners if they don't realise you've switched to phonetics, so signal it with something like "spelling:" or "I spell". Prosigns are mainly a CW thing. AR, SK, BT, KN and similar are sent as run-together characters. On voice you use words and procedure words instead: "over", "clear", "break", "say again", "roger" (many nets prefer plain "copy" or "received"). Don't say prosign letters on phone as if they were procedure words. In nets and emergency traffic, clarity and discipline matter more than style. Phonetics are used for callsigns, unusual names, and anything where a single wrong character could cause a problem, such as addresses, serial numbers, or medical item names. Many served-agency and net procedures ask for numbers to be given clearly and often repeated, and written messages such as ARRL radiograms spell out digits and use a check count so the receiving end can verify the message length. For actual emergency or priority calls, follow your net's script and the local emergency plan. The correct voice distress and urgency words are "Mayday" and "Pan-Pan", which have formal meanings and should only be used for those situations. So a sensible approach is to treat the ITU alphabet as your default, keep it brisk when conditions are good, and slow down and spell more when they're bad. Improvise only as a targeted fix for one confusing letter, not as a replacement for the whole system.
  9. On question 2, I'd lean toward not enabling digipeating until you've watched the channel for a while. Run Direwolf as an RX iGate first and look at aprs.fi to see what you're hearing and what path the packets arrive with. If a good wide-area digi already covers the area, a second one mostly adds duplicates and collisions. If the local terrain leaves gaps for handhelds and low-power mobiles, a WIDE1-1 fill-in is the more useful job than a big wide-area digi. For Direwolf, the iGate part comes down to a few directives in direwolf.conf: your MYCALL, the audio device and modem settings, and the APRS-IS connection. It looks roughly like this: ADEVICE plughw:1,0 CHANNEL 0 MYCALL N0CALL-10 MODEM 1200 IGSERVER noam.aprs2.net IGLOGIN N0CALL-10 12345 Use your real callsign and your own APRS-IS passcode, and check the current Direwolf documentation for the exact syntax, because directives and examples change between versions. If you enable the TX iGate side, be careful. A proper TX iGate only sends internet-to-RF packets for stations it has recently heard directly on RF, and mostly for messages. It should not dump general internet traffic onto the channel. Packets whose path contains TCPIP, TCPXX, NOGATE or RFONLY must not be gated to APRS-IS at all. If you do digipeat, the Direwolf docs include a standard example using the WIDEn-N paradigm with a filter that keeps hop counts sane. Copy from the docs rather than writing the pattern yourself. Most bad digi behavior comes from ad hoc regexes. Don't skip audio levels. An overdriven receive level or a hot transmit level will cause more lost packets than any path choice. Set the receive level so Direwolf's audio-level numbers sit in a comfortable range, and keep TX deviation reasonable. Too much deviation makes packets less decodable at the other end.
  10. On sending, a lot of plateaus are really sending problems. If you can copy 18 WPM but can't send cleanly above 12, you will hesitate at the moment of your first QSO. Some basics: Paddle and keyer: Use an electronic keyer if you want to send at speed. Iambic mode A and mode B differ in what happens when you release the paddles while squeezing. Try both and see which one stops you from adding a stray dot or dash. A standard weighting of about 3:1 (dash to dot) is a good starting point; change it only if your sending sounds off.Sidetone: Many operators prefer something in the 500 to 700 Hz range. Pick a pitch that doesn't tire your ears, and use the same one for practice and on the air.Paddle feel: Contact spacing and tension matter. Too light and you get double characters; too stiff and your hand tires. Adjust them in small steps.Practice habit: Send slowly and cleanly before sending quickly. Record yourself and listen back to find uneven spacing between letters and words.For the first QSOs, an easy route is to listen to a few exchanges first, since the standard patterns repeat: CQ, call, signal report, name, QTH, 73. Slow-speed CW nets, where they exist near you, can be a friendly place to start. Check with local clubs, and ask on a CW learners' group for current schedules rather than trusting old listings. Contests are a good source of fast, structured repetition because the exchange is predictable. Start by tuning around and answering stations (search and pounce) instead of calling CQ. Most contest operators will repeat a call or exchange if you ask, and a few contacts at a pace you can copy are worth more than struggling through a big pileup.
  11. Adding to the 23 cm and microwave side: pointing and polarization behave differently there. A 3 m dish at 1296 MHz has a beamwidth of roughly 5 degrees, while a 1.8 m dish at 10 GHz is closer to 1 degree. The Moon itself is about half a degree wide. Tracking therefore needs to be good to a small fraction of beamwidth, and any backlash or encoder error will show up as lost signal. Moon and Sun noise measurements are a common way to calibrate pointing and system performance on the higher bands, because they give you a repeatable reference. Always point the dish and set limits so that the Sun is never in the feed path, to protect both the feed and any equipment. Polarization is simpler than on 2 m, but not free. A reflection reverses the sense of circular polarization, so check the convention your sked partner uses for transmit and receive senses before assuming a mismatch is a fault. Linear stations on 23 cm still see some Faraday effects and spatial offset, so rotatable feeds are useful if you do not use circular. Libration fading is the other point. The Moon's apparent rocking spreads the echo in frequency, and the spread grows with frequency. At 2 m it appears as slow flutter, while at 23 cm and above it produces a much wider smear that interferes with narrow modes. That is the main reason for choosing a wider Q65 submode on higher bands. The tradeoff is sensitivity, so it is not worth jumping to a wide submode unless you actually see the spread on your partner's echoes or signals. For sked planning, the minimum agreed items are band, mode and submode, frequency, start time and who transmits in which period, plus a fallback time. Check your own Moon window with software and look at Moon declination, elevation at both ends, and the degradation figure for that date. Avoid dates where the Moon sits close to the Sun on microwave bands, since Sun noise can ruin receive performance. Exchange callsigns and short reports and leave rigging details to a later chat. A first sked with a known large station is usually more informative than waiting on random calling.
  12. Picking up the rest. Power (§97.313). The ceiling is 1500 W PEP output from the transmitter, and the rule that matters in daily operation is to use the minimum power necessary to carry out the communication. Some segments have lower caps. 30 meters is 200 W PEP, and the Technician HF segment on 10 meters is also limited to 200 W PEP. Certain bands and sharing arrangements, like 60 meters, are specified in ERP or EIRP terms and have been revised over time. Read §97.303 and §97.313 as they stand today rather than going from memory. A big amplifier doesn't give you a license to run full power at a local contact. Spurious emissions (§97.307). Your signal must not cause harmful interference outside your intended bandwidth. The rule sets attenuation standards that differ by frequency range and power level. The real-world causes are usually overdriven amplifiers, missing or damaged harmonic filters, and poorly adjusted audio or ALC. The fix is to keep drive levels clean, use proper low-pass filtering, and check your signal with a second receiver or an SDR. Note that the FCC also has certification requirements for amplifiers sold on the market (§97.315). RF safety (§97.13(c)). Licensees must evaluate their stations for RF exposure unless they fall under the exemption thresholds. Those thresholds depend on band and power, and the table has been updated, so look up the current one. If you're not exempt, you do a routine evaluation using the methods in FCC OET Bulletin 65 Supplement B or similar. Antenna placement, duty cycle, and proximity to neighbors all matter. Control operation, auxiliary stations, automatic control (§97.201 and following). Every transmission needs a control operator. The licensee is responsible unless the licensee designates someone else. Repeaters can run under automatic control. Auxiliary stations, such as links and remote bases, are restricted to certain bands, so check §97.201. Automatically controlled digital stations are only allowed in specific segments (§97.221). Local, remote and automatic control each carry different obligations, and the control operator must be able to turn the station off. License classes. New licenses are Technician, General and Amateur Extra. Novice and Advanced are no longer issued, but those licenses can still be renewed and keep their existing privileges. The details of which frequencies and modes each class gets are in §97.301 and §97.305, and they're worth reading directly. Enforcement. The FCC's Enforcement Bureau handles this. The usual escalation is a warning or Notice of Violation, and in more serious cases a monetary forfeiture or license revocation. Volunteer monitoring programs can document problems, but the FCC makes the enforcement decisions. In practice, deliberate interference and unlicensed operation draw the most attention. Term and renewal. Licenses are valid for 10 years. You can renew within 90 days before expiration. After expiration there is a grace period of two years during which you can still renew, but you can't transmit until it's granted. After the grace period, you have to take exams again. Keep your mailing and email addresses current in the FCC's Universal Licensing System, because that's where notices are sent.
  13. until

    The Arizona ScQRPions' FYBO QRP contest runs on Saturday 6 February 2027 from 1400Z to 2400Z. It is an on-air QRP event open to operators worldwide. The organizer's contest page links to the rules and an autolog tool.Location: On the air (amateur radio bands, worldwide); no physical venue stated Organizer: Arizona ScQRPions (AzScQRPions) Source: Event information
  14. For a first contest, the usual advice is to start where the exchange is short and the activity is high. CQ WPX is a good example: RST plus a serial number is easy to log, and there's plenty of traffic. CQ WW is similar if you know your CQ zone. Sweepstakes is a great event but the five-part exchange catches people out, so it works better as a second or third contest once the routine is comfortable. Field Day and the state QSO parties are the friendliest on-ramps. They are designed for lots of casual operators, and you don't need a big antenna to make contacts. It also helps to pick one band and one mode for your first weekend instead of trying to cover everything. On setup, get the logger working before the event. Configure the contest template, test the Cabrillo export with a few dummy QSOs, and set up your function-key messages. Most first-time frustration comes from a program that is not set up for the right contest, not from the radio.
  15. On channel layout for emergencies, I'd keep it boring. Put the most important local repeaters in the first few memory slots with names that make sense at a glance, such as the repeater callsign or net name. Add a few simplex channels next, then everything else further back. If your radio supports memory banks or groups, use them: one for local repeaters, one for simplex, one for events or nets. Also keep a paper sheet with the same information in the same order. Screens fail, batteries die, and someone else may need to pick up your radio. List frequency, offset direction, tone, and what the channel is used for. And test the radio on the air occasionally instead of just checking that it powers on. It's the only way to find out your tone, offset or antenna connection is wrong before you need it. One more point on batteries: if a radio supports both a Li-ion pack and an alkaline AA case, the AA case is usually lower power, so treat it as a backup rather than a normal operating mode.
  16. On interference, it helps to check your own station before blaming someone else. A noisy power supply, LED lighting or a poor connection can look like "interference from the band" when it is really something in your own house. Turning off devices one at a time at the breaker is a reasonable way to find it. If it comes from a neighbor's equipment, a polite conversation with the neighbor often works better than a complaint. On the rag chew point, it is worth saying that a short break in the middle of a long QSO is more than politeness. A pause lets a station with a weak signal slip in and say they would like a turn. It also helps the other operator, who may be waiting to say something about the topic. If someone breaks in, acknowledge them, even if it is only to say you will finish your thought and then give them the next turn.
  17. On studying, the biggest point is to make sure your material matches the question pool currently in use. Question pools are revised on a multi-year cycle, so an old used book can have outdated questions. Check the effective dates printed on the book or on the app. A workable plan is to read a reference such as the ARRL license manual for the concepts, then use HamStudy or another practice-exam app for repetition. Apps are good at spaced repetition and show you which topics you keep missing. The manual is better when you need the reasoning behind an answer, like why a repeater uses an offset, or what a 1/4-wave antenna actually is. Free alternatives exist too if you don't want to buy a book, but the same warning about the pool version applies. The Technician exam is 35 multiple-choice questions, and you need 26 correct. Practice exams will tell you if you're close. Don't stop at the score. Read the explanation for every miss, because the real exam draws from the same pool but shuffles the wording and answer order. Pure memorization of letter positions fails for that reason. Focus on the areas that fill the pool: FCC Part 97 rules, station identification, operating practices, basic electrical safety, simple Ohm's law and power math, antenna and propagation basics, and the VHF/UHF bands. Learn the 2 m and 70 cm calling frequencies and the usual repeater offsets. After you pass, the VEs submit your results to the FCC. Your call sign will appear in the ULS (Universal Licensing System) once the grant is processed, and you can look yourself up by name or FRN. Your license is electronic, so keep the email address on your FCC record current. Once the grant shows in ULS you can transmit. Printing the ULS page or an official copy for your records is wise. For first steps, get an inexpensive handheld (HT) and program a few local repeaters from a source like RepeaterBook. Listen for a while before you transmit, join a club net, and say your call sign clearly. Technician privileges include all amateur bands above 50 MHz plus limited HF segments, so there's plenty to try. If you want more, a General upgrade can come later, and some sessions allow you to take it in the same sitting.
  18. On tailending, my view is that it depends on the mode and on the speed of the operator. On a fast CW operation where the DX sends his callsign and a report and then goes straight to the next call, the gap is only a fraction of a second, and stations who wait for a full QRZ will often be too late. But the technique only works if you can actually hear the end of the exchange cleanly. In practice that means a good receive audio chain and a transmit-receive switchover that is fast enough, with no relay delay. If your rig or amplifier needs time to switch, you will land on top of the last part of the QSO and annoy everyone. For SSB, I would be more conservative. The pauses are longer and the DX is more likely to be affected by overlapping speech. A short, clear call right after the QRZ usually works better than a clever tail-end call. One more point on split: it is also worth checking your transmit filter and audio bandwidth. If you are transmitting a wide SSB signal while the DX is listening up, you could splatter into neighbouring callers. Keeping processing moderate and bandwidth narrow is a real courtesy at a time when many people are calling inside a few kilohertz.
  19. For HF I'd flip the order and check observations first, then use the indices to explain what you see. A quick pass could be: listen to the NCDXF beacons on 20 and 15 m and note which ones are audible and at which power steps. Then look at WSPR or PSK Reporter for your own area to see which paths are active. Only then check K and the flare/radio blackout reports if something looks odd. The reason is that SFI is a single global number, while propagation depends on your path: the latitude it crosses, whether it is in daylight or darkness, and the geometry of the gray line. A decent SFI says nothing about whether the D layer is absorbing at your end this minute. One caution on WSPR: it is a great band-opening detector, but remember it runs at very low power and decodes at a very low SNR. If your station is hearing spots at -25 dB, that does not give you the margin for a casual SSB QSO. I'd treat it as a yes/no for the path, and the beacon power steps as a better guide to the margin you have.
  20. Adding to the mode-selection side, plus grids and Winlink, since those catch people out. For weak-signal work beyond HF FT8, the WSJT-X family has specialised modes. MSK144 is meant for meteor scatter, usually on 6 m and 2 m, where a useful signal might exist for only a fraction of a second. Q65 is aimed at difficult paths like EME and tropo/ionospheric scatter, and it has several submodes and selectable period lengths, so you pick a combination suited to the path and frequency. That's a different workflow from FT8. You often need to agree on the submode, period and frequency in advance, usually through a coordination chat or a calling frequency set by convention. For grid squares, WSJT-X uses the Maidenhead locator. The four-character form, like FN31, identifies a rectangle 2 degrees of longitude by 1 degree of latitude. The six-character form adds a subsquare for finer location. For FT8 and FT4, four characters are normally all that's sent. Make sure your configured grid is correct, because it ends up in your CQ and in logs and reporting sites. A wrong grid makes distance awards and propagation maps unreliable. On VHF and up, where grids drive awards and contest scoring, accuracy matters even more. For Winlink, treat it separately from the chat-style modes. It's an email system over radio, and the software (Winlink Express) talks to a modem or TNC rather than just using your sound card as an FT8 decoder. VARA is a popular modem for it. It's proprietary, and unlicensed versions limit throughput, so check the author's current terms and licensing before relying on it. Whatever the modem, listen first, because Winlink and similar modes use channels that others may be using. Use frequencies and gateways appropriate to your band plan and license, and don't assume a gateway's availability from old lists. If you want something to sanity-check your station, WSPR is a good tool. Set a modest power level, let it run for a while, and compare what the network reports against what you'd expect. That helps confirm that your frequency, clock and antenna are working, without needing a QSO partner.
  21. Here are the pieces in the order you'll meet them. Study: the exam is drawn from a published question pool, and the pools are replaced on a multi-year schedule. Whatever you study from has to match the pool in effect on your test date. Check the edition on the cover of any book, and check the pool dates listed in the app. A used book from a few years back may cover an expired pool. HamStudy and the ARRL manual do different jobs, so they combine well. The manual explains the material in prose, which helps if terms like frequency, wavelength, or the relationship between voltage, current and resistance are new to you. HamStudy is practice: flash-card style questions with spaced repetition, plus practice exams that mimic the real one. Reading a chapter and then drilling that chapter's questions works better than trying to memorize the whole pool cold. If you hit a question you keep missing, work out why the right answer is right. Many questions are variations on the same idea. The Technician exam is 35 multiple-choice questions, and you need 26 correct to pass. A reasonable readiness check is scoring comfortably above that on several full practice exams, not just once. Some people use a 85 to 90 percent average as their personal bar, since nerves cost a question or two. FRN: that's your FCC Registration Number. It's a 10-digit ID you get by registering in the FCC's CORES system, and it's free. Get it before test day, because the volunteer examiners will ask for it when they file your paperwork. Don't pay anyone for an FRN. Keep the login details somewhere safe, since you'll need them later for address changes and renewals. ULS is the FCC's Universal Licensing System, where the license database lives. After you pass, the VE team submits your results through their coordinator. Your license is granted in ULS, and you can look it up by name or FRN to see your call sign.
  22. On the radio choice, I'd start by deciding which network or mode you'll actually use. If most of your local activity is analog FM repeaters, any of the three will work, and the deciding factors become the menu layout, display readability while driving and how well the microphone and speaker suit your vehicle. If your local group is active on C4FM or D-STAR, that should drive the decision more than the spec sheet. A radio can be perfectly good and still be the wrong one if nobody around you uses its digital mode. For the TM-D710G, the APRS and TNC features are the main attraction, but a few extra items matter too, such as a GPS source, correct beacon settings and sensible beacon intervals. Don't set up a mobile APRS station and leave it chattering at an excessive rate.
  23. I'd put filtering and noise hunting ahead of almost everything else. A lot of "my receiver is deaf" complaints turn out to be a noisy supply or an overloaded front end, and a mod inside the radio won't fix either. A good test is to run the rig from a battery for a short time, with the house breakers or the suspect devices switched off one at a time. If the noise floor drops, you found the source. If a broadcast station or pager system is hitting you on VHF, an inline notch or band-pass filter is cheaper and less risky than opening the radio. On the MARS and CAP side, I'd keep the radio capability and the authorization separate in your mind. Having a radio that can be programmed to the frequencies doesn't mean you may transmit there. Those programs normally have rules on who can operate, when, on which channels, and sometimes with which equipment. The safest approach is to ask your program coordinator what is approved and get it in writing, then keep a record of how each radio is configured. A separate radio for those duties, or at least a clearly labeled and backed-up codeplug, keeps you from accidentally transmitting on the wrong service.
  24. On the tools, here is how they differ in practice. Check each site for its current features and schedules, since these change. LCWO (Learn CW Online) is a browser-based Koch trainer. It handles the lesson progression for you, sends random groups, and you type what you hear and get scored. Typing instead of writing by hand is quick and works well for early drills. It has other exercises too, such as words, callsigns and plain text, which are useful once you know the full alphabet. G4FON's trainer is software you run locally, and it's also built around Koch-style learning. It's a good choice if you'd rather not depend on a website, and it gives you fine control over pitch, speed and spacing. The tradeoff is that it's less hand-holding than a site that tracks your progress. CW Academy, run by the CWops group, is different in kind. It's a structured class with volunteer advisors, a set curriculum and a group of fellow students. The main benefit is accountability and a human who can tell you what you're doing wrong. If you tend to drift away from solo practice, that structure is worth a lot. Classes run in sessions, so check their site for sign-up times. Many people use more than one: a class for structure and an online trainer for the daily drill. On head copy: once you know the characters, start by writing everything down, then gradually stop. A good first step is to copy the letters on paper but listen for whole words as they come in. Next, try just listening to short common words and callsigns without writing them. The usual trap is falling behind while you decode the previous letter. If you notice that, drop the speed. Don't try to push through it. For confidence, the best step before a real contact is to listen. Tune around the CW portions of a band and just follow along, even if you only catch a few characters. Learn the standard exchange (CQ, callsign, signal report, name, location, 73) so that the content is predictable and you only have to catch the variables. Many operators are happy to slow down for someone who says they're a beginner. Also, avoid leaning on a decoder program while learning. It does the work your ear needs to do.
  25. For sending, I'd say record yourself before changing any gear. Most 'my keyer is bad' problems turn out to be spacing problems: letters running together, or gaps between words that are too short. Listen to a recording with the sidetone off if you can, or run it through a decoder as a rough check. If the decoder consistently splits a letter, your character spacing is probably off even if each element sounds fine. On Mode A versus Mode B, the best test is to send a few letters that need alternating elements, like C, K, R and Q, and see which mode gives you the output you meant. If you keep getting an extra dit or dah on the end of a character, try the other mode, or adjust how early you release the paddle. A lot of people find it's just a timing habit rather than anything wrong with the keyer. For receiving, I'd keep Farnsworth at a character speed you can't comfortably count out. If you drop the character speed to match your overall speed, you end up counting dits and dahs and that habit is hard to break later.

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.