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_Chrissy

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Chrissy

  1. One I'd add for VHF/UHF is to drop the CB-style habits. Ten-codes and handles aren't standard in amateur radio, and plain language is better, especially in emergency communication where different agencies and groups may be involved. Likewise, on CW the Q-signals and abbreviations are useful, but don't force them into voice contacts. "QSL" on phone is fine occasionally but "I copy" is clearer to a newcomer. Also worth saying for new operators: nobody expects perfect procedure, but they do expect you to listen first. A mistake like a wrong ID format or a clumsy check-in is easy to forgive. Stepping on a net or ignoring a request to clear the frequency is what annoys people. If you're nervous, write out your callsign phonetically on a card beside the radio and just read it.
  2. One thing I'd add is to read the actual award rules again before applying, even if you did it the last time. Programs update their rules, entity lists change, and application procedures move online. What counted two years ago may not match what the administrator wants now. I wouldn't trust anything on a forum, mine included, over the current official rules page. For the TQSL problem, my approach would be to set up a separate station location for every distinct operating situation (home, each portable site, each different callsign) and give each a clear name. Never reuse one location and edit it afterwards. Before you sign and upload a batch, check that the location shown matches where the QSOs were made. If something is off, fix it before uploading, because trying to undo a bad upload is much harder. Also keep in mind that not every award recognises every mode or band. WAS and DXCC have mode categories, and some programs treat digital modes differently from phone or CW. If you're chasing a specific endorsement, check that the mode in your log maps to the category you want. A QSO logged as one digital mode might not match a counterpart logged as another in LoTW, and that can look like a missing confirmation when the real issue is mode matching.
  3. One thing that helps me think about this: compare the rate you're getting with the rate you could get elsewhere, not just the rate you want. If the last-10 rate is falling but the last-100 is still high, it might just be a lull. If both are down and the multiplier window shows needed stations across the band, that's a stronger sign to go hunting. A tip for S&P: work the stations that are easy first. If a needed mult is running a pileup you can't break, mark it and come back later instead of burning minutes on it. N1MM's bandmap lets you keep those spots on screen, so you can return when the pileup has thinned. On band changes, check the other bands before you leave. A quick sweep of each band for activity, or a look at what the skimmer is decoding, tells you whether the next band is actually open. Moving blind to a band that is not ready is one of the most expensive mistakes.
  4. Go to a club meeting, even if the topic sounds boring or you feel like you don't know enough. A club is often the quickest way to find an Elmer, borrow test gear, get a look at someone's real station, and hear which repeaters are worth programming into your radio. A good question to bring: "Could someone help me check my radio's programming and my first antenna setup?" That's specific, easy to answer, and usually leads to someone saying, "Sure, bring it over." Another good one is to ask which repeaters have nets and when. Check-ins are a low-pressure way to get a first contact, since the net control operator will guide you through what to say. On the first-QSO nerves, a useful trick is to write your callsign, your name, and your location on a card next to the radio. Everything else is just a normal conversation. You can use the phonetic alphabet if the signal is weak, but nobody expects perfection on day one. For the HF crowd: what bands and modes did you start with, and was it SSB, CW, or a digital mode like FT8? I'd like to hear what made the first contact easier or harder.
  5. On bandwidth, I would separate casual ragchewing from DX and contest operating. A wider TX setting can make voices sound more natural on a quiet band when you are not crowding anyone, but in a pileup or contest it makes sense to keep the occupied bandwidth tight, around 2.4 kHz or a bit more. It reduces interference to neighbours, and narrow audio puts more of the power into the part of the spectrum that carries intelligibility. Also check your PC or digital audio chain if you use a USB interface. Settings in the operating system, a voice-processing app or the rig's own menu can stack on top of each other, giving you double compression or low-cut filters you did not intend. Reset everything to a flat, known setting first, then add processing one step at a time.
  6. One practical tip for FM passes is to prepare the radio before AOS, not during it. Program memories for the satellite you plan to work, with the uplink tone set and the downlink in a separate memory or VFO. Write the pass times, maximum elevation and direction on a card. If the pass is under about 15 degrees maximum elevation, treat it as a bonus rather than a main target, because the path is long and horizon obstructions will hurt you. Also remember that you cannot hear another station while transmitting on a half-duplex radio, so listen first, find the gap, and keep your over short, just your call and grid. If you can use a second receiver or a duplex radio, you can hear your own downlink and spot problems with your Doppler correction.
  7. One more thing about band changes is that antennas shape the decision as much as propagation does. A band where you have a strong antenna toward the major population areas may be better than a band that is theoretically more open but where your antenna is weak. A stack, a high Yagi or a good low-band receive antenna can change which band you prefer at a given hour, so factor your station's real strengths into the plan. On the skimmer question, it's mostly a category decision. If you plan to enter an unassisted class, practice without spots, because S&P without them feels different: you tune more, you decide faster, and you have to read a band map from your own receiver instead of from the network. If you enter an assisted class, spots are a tool for both finding multipliers and checking whether a band has opened to a region, but treat them as hints, not truth. Spots can be wrong, and a busted spot can send you chasing a callsign that isn't there. For endurance, I'd plan the off-time before the contest starts. Decide which hours you're most willing to give up based on likely band conditions, then protect that rest. People who make that decision when they're already tired tend to make a worse one.
  8. One practical suggestion is to make a short cheat sheet for each contest before the weekend starts. Write down the exchange you send, the exchange you expect to receive, and what counts as a multiplier. Then you are not reading rules at 0300 UTC when a station sends something you did not expect. For example, in a contest where DX stations send a serial number, and one where they send power, the logger field you tab through is different, and a mismatch is an easy way to get busted QSOs. Also confirm that your software version has the current rule set for that event. Some programs handle contests by plugin or template, and an old one can mis-score or export the wrong header. Test with a few dummy QSOs and export a trial Cabrillo file the week before, rather than the night you need to submit.
  9. Here's a study order that fits most people moving up from Technician. Start with the rules and operating practices chapters, since they overlap with what you already know and build confidence quickly. Then do band privileges and emissions. Save electrical principles and propagation for the middle, when you're warmed up. Leave digital modes and the odds and ends for last. A four to six week schedule of short daily sessions beats cramming, especially if you're also working through the math. For the electrical section, the General pool leans on Ohm's law, power calculations, decibels, and basic filter and circuit behavior. Remember the dB anchors: 3 dB is about double the power, 10 dB is ten times, and 6 dB is a quarter-wave step in voltage terms. Anchors like these let you do the arithmetic in your head. Know the difference between PEP and average power, since power limits are written in PEP. Practice working each formula in both directions, since the exam will present the unknown in different positions. For digital modes, learn the categories more than the software: what FT8 timing requires (accurate computer clock sync), how PSK31 and RTTY differ, what Winlink does (email over radio), and the difference between baud rate and bandwidth. Most questions are conceptual. Take practice exams in timed mode and review every miss by reading the explanation, not just the correct letter. When you're consistently scoring in the mid-80s or better, you have a margin over the 26-correct line. Plan for the real session by bringing ID and your FRN, and expect the VE team to handle the paperwork. On vanity calls, you keep your current call when you upgrade, and nothing forces a change. Vanity is optional and carries an application fee, so check the FCC's current rules before applying. General operators can generally pick from the sequential-format groups that Technicians can, so upgrading doesn't change much about vanity eligibility. If you want a shorter or more memorable call, you can do it any time after you hold a license. There's no need to rush it around the exam.
  10. On the served-agency side, I'd push for getting someone from the agency to take part in the exercise, even if it's just an hour at a table with a radio operator. Often the biggest gap is that we think in radiogram format while they think in ICS forms or in plain questions like "how many cots do you need and where?" If your operators can restate a request in one clear sentence, then format it, the message usually survives better. For Field Day, a low-pressure way to add practice is a dedicated "traffic table" with a small stack of pre-written sample messages, some radiogram and some ICS-213 style. Rotate people through as sender, relay and receiver. Include a couple of messy ones with numbers, unusual place names and a few abbreviations to expand, since those are what trip people up. It doesn't take much logging time away from contacts, and it shows right away who needs more practice with the forms and the phonetics.
  11. For a first activation, I'd pick the mode you can operate most comfortably when the band is imperfect. SSB is usually easiest to get started with, since hunters tend to gather there, but it can get crowded and needs decent audio. CW can be very efficient with low power and simple antennas if you're comfortable copying call signs at speed. FT8 can fill a log, but remember that it's a different workflow, and spots and logging need extra care so contacts don't get mixed up. A few practical points: Pick a frequency, listen long enough to confirm it's clear, then post a spot with the correct park reference and mode.Update your spot if you change frequency, and don't leave a stale spot up after QRT.Keep a paper backup of calls in case your logging software or phone dies.Verify the UTC date before you start so you don't accidentally split an activation across a date boundary.Reaching 10 QSOs is the minimum, not the goal. Having a few extras gives you a safety margin for busted calls or contacts you can't confirm.
  12. Your split is sensible. Keep anything that can damage hardware, like relay sequencing and PTT, in firmware that can't be stalled by an OS update or a Wi-Fi reconnect. The Pi can send commands, but the microcontroller should have the final say. For example, it should refuse to switch an antenna relay while PTT is asserted. For the SWR sensing, a diode-detector bridge is fine for a rough indication, but the diodes are very nonlinear at low power. Don't compute SWR from raw ADC counts. Take a few calibration points at known power levels into a dummy load, build a lookup table or curve fit, then compute reflection coefficient as sqrt(Vrefl/Vfwd) after correcting for the diode drop. SWR is then (1+ρ)/(1−ρ). Expect the numbers to be least trustworthy below a few watts. If you want to test the relay logic safely, do it on the bench with the transmitter off and a dummy load on the output.
  13. On head copy, the main thing is to stop translating. If you hear the sound, think "dit dah dit," and then look up R, you're doing a lookup, and a lookup can't keep up with speed. The goal is for the sound itself to mean R. Koch-style training helps because the sound is never slowed enough to analyze. A few habits help: Don't dwell on a miss. If you miss a character, let it go and pick up the next one. Stopping to puzzle over the one you missed makes you lose the next two or three. Leave a blank on the paper and keep going.Write less over time. Early on, copying to paper is useful because you get an honest score. Later, try copying only part of the time, or listening to short words and calls without writing, then checking against a transcript.Move from letters to words. After a while, you start hearing common words and prefixes as units, such as THE, AND, and CQ. Practicing with real words and callsigns, not only random groups, speeds this up.Keep sessions short. Ten to fifteen focused minutes once or twice a day tends to work better than one long session. Stop while you still feel sharp.For the plateau, the usual advice is to move on. Accuracy often stalls around a certain speed because your brain is shifting from copying single characters to recognizing words. Dropping the speed slightly for a day or two, then pushing it up, is normal. Don't read a plateau as a sign of failure. Flashcards and mnemonic charts are fine for a quick first look at a character. They are a weak way to learn the sound. Whatever you use, make sure the character is paired with the actual audio, not the visual pattern. Confidence mostly comes from the gap between drilling and real signals. Decoding clean, computer-generated code is easier than copying a real station with fading, noise, and a different fist. Add some variety, such as contest-simulator software or recordings of real operators, once you're comfortable with the basics. When you're ready to go on the air, listen first and answer a slow CQ. Most operators are patient with a beginner who says so, and a short, simple exchange (call signs, signal report, name, location) is enough for a first contact. You don't have to be fast to start. You only have to be able to copy the basic exchange reliably.
  14. Do both, but in a specific order. Start with the concept, then memorize the one or two formulas that go with it. A lot of Element 4 can be answered by knowing which direction something moves, so you often don't need a full calculation. Some examples that come up in different forms: Op amps: an inverting stage has gain of minus Rf divided by Rin. A non-inverting stage has gain of 1 plus Rf over Rin. With a 47k feedback resistor and a 4.7k input resistor, that's -10 inverting and 11 non-inverting. A common slip is forgetting the "plus 1" or the sign inversion. Filters: an RC cutoff is 1 divided by 2πRC. For band-pass circuits, Q is center frequency divided by bandwidth. At 7.1 MHz with a 100 kHz bandwidth, Q is about 71. The pool also asks about shape factor, which compares the bandwidth at two attenuation points. A lower shape factor means a steeper skirt and a better filter. Modulation: modulation index for FM is deviation divided by modulating frequency. Carson's rule estimates bandwidth as twice the sum of deviation and highest modulating frequency. With 5 kHz deviation and a 3 kHz tone, the index is about 1.67 and the bandwidth is about 16 kHz. Receiver design: understand the difference between sensitivity (how weak a signal you can hear) and dynamic range (how strong a signal you can tolerate before blocking or intermod). Third-order intercept and noise floor questions tend to reward that distinction more than the math. For the rules, treat Part 97 as its own category and do short, repeated review sessions. The questions are often wording-based, and you can lose points by mixing up similar-sounding rules. When you miss one, read the actual rule section rather than only the explanation in the study guide.
  15. For anyone nervous about a first repeater call: listen first. Spend a few evenings just monitoring so you know how the local users operate. Many areas have regular nets, and a net is one of the easiest places to check in because the net control station tells you exactly when to speak. When you're ready, keep it simple. Wait for a gap, key up, and say something like, "This is [your call sign], listening." If someone replies, give your call, your name, and your general location, and ask how their day's going. That's a perfectly good first QSO. Using phonetics for your call sign can help, but you don't need to sound like a pro. Some other habits worth building early: - Pause for a second after keying up so you don't clip your first word. - Leave a short gap between transmissions. On many repeaters, that lets others break in, especially in an emergency. - Keep contacts short on busy machines, and move to simplex if you want a long chat and the other station can hear you. - Identify as your rules require. Check your regulator's requirements instead of relying on someone's memory. For HF, the first QSO is often a bigger jump because of antennas, propagation, and the pace of operators. Special-event stations, Parks on the Air activators, and contest stations are good targets. They run short, structured exchanges and are used to answering newcomers. In a contest you can often make a contact with just a call sign and a simple exchange, so it's a low-pressure way to learn. Just don't feel like you need to compete for a score. Finally, find an Elmer. That can be a formal mentor from a club or just a friendly person at a meeting. Ask them to look at your station, listen to how you sound on the air, or help you put up your first antenna. Most clubs are happy to help new members, especially if you show up and tell them what you're trying to do.
  16. I'd split it by how far you carry it. For a drive-up POTA spot, weight barely matters, so you can bring the heavier battery, a bigger pole and a proper table and chair, and spend your effort on operating comfort and logging. For a SOTA climb, every item has to earn its place. A common approach is a 5 W radio, a small LiFePO4 pack, an EFHW on a lightweight pole or tied into a tree, and paper and pencil. People who like the EFHW for summits usually point to speed: you can be on the air in a few minutes, which matters when the weather turns or the daylight window is short. One practical point on the EFHW is to test it at home on each band before you hike with it. If the SWR is high on one band, adjust the wire length or the way you lay it out, rather than discovering that on a summit. It also tells you whether your coax and choke arrangement is behaving the way you expect.
  17. On picking modes, a few distinctions help. FT8 and FT4 are for quick confirmed contacts. A standard FT8 exchange is a grid square and a signal report, so the grid itself carries the "where are you" information. Maidenhead locators are worth understanding rather than copying blindly. A 4-character grid (for example, two letters and two digits) is a square of 2 degrees of longitude by 1 degree of latitude. A 6-character locator adds a subsquare that is 5 minutes of longitude by 2.5 minutes of latitude, which is much better for VHF distance calculations. Many weak-signal setups send only 4 characters, which is enough for HF and for most awards but coarse for VHF and up. Q65 and MSK144 are more specialised. MSK144 is for meteor scatter, where the signal appears as very short bursts, so its frames are fast and the decoder is tuned for pings rather than long integration. Q65 is aimed at difficult paths such as EME, ionospheric scatter and rain scatter on the higher bands, and it offers multiple sub-mode choices and period lengths, so you pick based on how much frequency spread the path imposes. Using these on a normal HF band is possible, but it is not what they were designed for. WSPR is useful when the question is "where can I be heard?" rather than "who can I work?". It is a beacon mode with two minute transmissions and very low power requirements, and spots go to a shared database, which makes it a handy antenna comparison tool. Just remember that spot counts depend on how many receivers happen to be listening on that band at that time. For messaging, Winlink and JS8Call fill different roles. Winlink is email over radio via gateways, with modems such as VARA, ARDOP or Pactor, and is the usual choice for emergency communications where you need to move a real message. VARA is a proprietary modem, and its free version is rate-limited while the registered version is faster. JS8Call is more of a conversational, keyboard-to-keyboard mode with relay capability, and its throughput is low. Olivia and other MFSK modes in FLDIGI sit in between, as a way to hold a slow ragchew on a noisy band where PSK31 would fall apart. One last point is that decode thresholds are usually quoted in dB relative to a 2500 Hz noise bandwidth. That makes comparisons fair across modes, but it does not account for QRM, fading or timing issues, so treat the numbers as ideal-condition references and not as a guarantee on your own receiver.
  18. For band maps, treat the WSJT-X waterfall and the contest band map as separate tools. The band map in N1MM+ is useful for CW and SSB, where you're hunting multipliers and marking stations you've already worked. Putting FT8 on the same band map can clutter it, because many stations occupy a few narrow slices of spectrum. If the radio is in data mode and CAT is shared, it's easy for the band map to follow a frequency the digital program has moved. On the submission side, give yourself a checklist: confirm callsign and category in the header, check that band and mode counts look right, run the sponsor's checker if one is available, and save the Cabrillo as a plain text file with the exact filename the rules require. Then export a separate ADIF for the master log and for LoTW signing. For rotators, I'd test the setup before the contest by sending a bearing from the logger, then from the rotator software, and confirming both display the same heading. Offsets and wrap-around at 180 or 360 degrees tend to show up only once you actually use the controls in the middle of a run.
  19. I agree with the dummy-load step, and I'd add a reminder that a rig's SWR meter or protection circuit is only as good as its directional coupler. If the forward and reflected detector diodes have drifted, or a connector inside the rig has a poor joint, the rig can report high SWR into a perfectly good load. Test that with a known-good dummy load and, if possible, an external wattmeter that you trust. If the external meter shows sensible power and low reflected power but the rig still cuts back, the fault is likely inside the protection or sensing circuit. Also watch the order of the checks you mention in step 2. A relay that clicks is not necessarily making good contact. A multimeter on continuity or resistance across the relay contacts, with the rig powered down and the antenna disconnected, can show whether a path is actually closing. For RF voltage measurements, remember that a standard DMM can read incorrectly in the presence of RF, so an RF probe or a scope is the better tool there.
  20. One practical point on zones. If you're building WAZ from DXCC-oriented data, don't assume entity equals zone. Large countries can straddle several zones, so you need the zone that applies to the station's actual location. If your logger fills the zone from the callsign prefix alone, it can get it wrong for those cases. I'd recheck any zone you're counting on for a last-needed credit before applying. For the CQ DX Marathon, keep the calendar-year logic in mind. Contacts from last year don't carry over, so some people maintain a separate view filtered by year. That's also a good reason to export your log in ADIF regularly and keep a backup, because LoTW can be slow to confirm and you may want to audit your own records before a deadline. For POTA and SOTA, check the activation requirements and how the sponsor matches logs. Callsign errors, wrong dates, or a missing reference in your own record are the usual reasons a chaser or hunter credit doesn't show up. Compare your log against the database record before assuming the activator made a mistake.
  21. One angle that's easy to miss: the noise isn't always in the radio or the antenna, it can come from the computer. USB 3 ports and cables are known to radiate broadband hash that lands on HF and VHF. Moving the dongle to the end of a USB 2 extension, adding ferrites at both ends, and powering the computer from a different supply can change the noise floor noticeably. Put the receiver at the antenna, if you can, and send the data back over a long USB or network link, instead of running a long coax into a noisy room. The software side is useful for diagnosis too. In a waterfall, a noise source from a switching supply tends to show up as evenly spaced lines. You can also compare with a dummy load connected to the input. If the noise floor with the dummy load is well below the floor with the antenna, the noise is arriving through the antenna system. If the two are almost the same, the receiver or the computer is generating it, and no antenna change will fix that. And before you try to decode digital modes with WSJT-X, fldigi or multimon-ng, check your audio levels and the virtual audio cable. Overloaded audio is a far more common problem than a bad decoder.
  22. For receiving, the biggest shift is to stop writing each letter as it arrives and start copying in your head, a little behind the signal. Once you're writing every character you hit a speed ceiling, because the pencil can't keep up. Farnsworth or Koch practice helps because you learn to recognize a character as a unit instead of counting elements. If you use Farnsworth, shrink the extra spacing over time rather than leaving it stretched permanently, or the contest speeds will still feel like a jump. On filters, a bandwidth around a few hundred hertz is a common starting point, then narrower if the band is crowded. If you hear a ringing or hollow quality on the signal, widen it a bit. Setting your receive pitch so the signal sits in the middle of the passband also matters. Tuning off to one side and compensating with the filter can leave you with more noise than necessary. Decoders are useful when you treat them as a cross-check. A skimmer-style display is great for seeing who's on the band and what they're sending. In a pileup or a contest it can help you verify a callsign you only partly heard. But a decoder won't copy through deep QSB, and it can mislead you on bad timing, so it's no substitute for ears. A good contest practice rule is to send the callsign cleanly, repeat what's needed, and use a question mark when you're unsure instead of guessing. Slowing down a notch for a partial call often gets the QSO done faster than blasting at full speed and getting repeats.
  23. On logs and nets, the vocabulary is a bit different from the Q codes, so here it is. Logging. A typical log entry includes date and time in UTC, callsign, frequency or band, mode, RST sent and received, the other operator's name and QTH, and notes. In contests, you also record the exchange (serial number, state, zone and so on). 'Dupe' means you already worked that station on that band and mode in the contest. 'NIL' means 'not in log', which a station may say when the other side's report doesn't match their log. 'QSL via' tells someone how to confirm: direct, a bureau, or an electronic service such as LoTW or eQSL. 'Run' means calling CQ and letting others come to you. 'Search and pounce' (S&P) means tuning around and calling other stations. 'Pileup' means many stations calling one at once. 'Split' means transmitting on one frequency and listening on another. Nets. The net control station (NCS) runs the net. A directed net means stations only speak when NCS calls them, while an open net lets people join in more freely. 'Check-in' means announcing your callsign to be counted. 'Traffic' means formal messages being passed. 'Break' means you have something urgent to add, and a priority or emergency break should be used only when appropriate. 'Clear' or 'out' means you are leaving the net. 'Standing by' means you are available but not transmitting. ID rules vary by country, but in the US, for example, you must identify with your callsign at the end of communication and at least every 10 minutes during it. 'This is [callsign], clear' is a common way to sign off and meet that rule at once. If you operate elsewhere, check your own licensing authority's rules.
  24. On the "where to call" question: the usual advice is to find where the DX operator is currently listening and then work out how he moves. Some operators sweep slowly up the spread and then drop back down. Others stay on a narrow segment and pick the strongest. If it's a sweep, calling about one or two kHz above his current pickup point, so that he reaches you in a few seconds, tends to work better than burying yourself at the top of the range. Calling at the very top, out where nobody is reaching, can leave you stuck for a long time. On phonetics, I'd say avoid inventing creative ones. Standard ITU phonetics are what a tired operator is most likely to copy, and on a marginal path the distinctive consonant sounds survive better than vowels. If the DX gets part of your call, repeat the full call once, not just the missing letters, unless he explicitly asks for a partial. On CW the same logic applies: send your whole call at a speed he can copy, not faster. Matching or slightly slowing to his sending speed is usually better than blasting at 30 wpm. Tailending also depends on the mode. On CW with a fast operator who is using short exchanges, calling right on the last character of the previous QSO is standard behaviour. On SSB, where the exchange is longer and the operator listens to the whole thing, it's much more disruptive. Pileup etiquette also covers things not directly about transmitting: don't tune up on the DX frequency or the listening range, don't tell others to "QRZ" or comment on whether he's split, and don't call again after he has logged you. Confirm the QSO by logging what you heard, not by making a second call to be sure. A dupe QSO costs everyone else time.
  25. I'll take the first four. ID (§97.119). You must give your FCC call sign at the end of each communication and at least every 10 minutes during one. On phone it has to be in English, and standard phonetics are fine. The call sign has to be yours, not the repeater's. A tactical name like "Net Control" or "Shelter 2" is fine for operating, but it never replaces your call sign at the required intervals. For data modes the ID has to be sent in the mode you're using, or by a permitted method. On FT8 and similar modes, the exchanged messages carry call signs, which in normal use takes care of it. Keyed or automatic IDs on a repeater controller are the repeater licensee's responsibility, and users still have to ID themselves. Third-party traffic (§97.115 and §97.117). Between U.S. stations, a third party can speak over your station as long as you are the control operator, you are present, and you are monitoring and supervising the contact. If the third party is a licensed amateur who could act as control operator of that station, the restrictions mostly fall away. For international contacts, third-party traffic is only allowed with countries that have a third-party agreement with the U.S. Otherwise you are limited to remarks of a personal character and technical matters. Check the agreement list for the specific country before putting a guest on the mic. Also, third-party traffic can't go out over an automatically controlled station, with a narrow exception for automatically controlled digital stations (§97.115(c)). Emergencies are a separate matter. §97.403 lets an amateur station use any means of radiocommunication when life or property is in immediate danger, but that is for real situations, not drills. Power (§97.313). The general ceiling is 1500 W PEP output, and you must use the minimum power necessary for the communication. Several limits sit below that: 200 W PEP on 30 meters.200 W PEP for Technicians on their HF phone segment on 10 meters.Beacons: 100 W.Spread spectrum: 100 W.60 meters has its own channel and ERP-style limits, so read the current text rather than relying on a number from memory.Remember these are limits on transmitter output. Antenna gain doesn't count against the 1500 W limit on most bands, but it still counts toward your RF exposure picture. Prohibited transmissions (§97.113). Here are the most common ones: Communications for compensation or business purposes, with limited exceptions such as a teacher's classroom use, plus some narrow employer-related allowances that depend on your duties.Music.Obscene, indecent or profane language.Messages encoded to obscure their meaning. This is the encryption rule, and it has narrow exceptions for control of space stations and radio-control models.Broadcasting and one-way transmissions, apart from beacons, code practice, bulletins and similar permitted types.Deliberate interference is a separate matter under §97.101(d).

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.