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 412.9 km/s
Aurora 1
Updated 14:00 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. On flashcards and apps: anything that shows you a letter next to a dot-dash diagram trains your eyes, and CW is an audio skill. If you use cards at all, make them sound-first, where you hear the character, say it, and only then check the answer. For a Koch approach you don't really need them, since the trainer is the flashcard deck. Phone apps are fine as a way to get in extra reps while you wait for something, as long as they play at real character speed and don't make you read a visual chart. Don't say 'dit dah' in your head while you listen to learn a character. Try to attach the sound to the letter directly. If you catch yourself counting elements, that's a sign the speed is too slow for your character recognition, and you should raise the character speed and widen the spacing instead. Going from writing to head copy is largely a matter of deliberately letting go. Early on you copy on paper because it's reliable. When your accuracy is solid, try a session where you only write every other word, or where you only write when you get lost. Then try letting characters go by without writing them, and just hear the word forming. You'll miss things. That's normal. The common trap is chasing a character you missed and losing the next three, so when you miss one, let it go and pick up at the next. Over time you'll find you recognize whole words, common ones like 'the', 'and' and your callsign first, rather than individual letters. You'll probably hit plateaus, usually in the middle of the speed range where you're no longer counting but haven't yet got whole-word recognition. It's common to feel stuck for a while and then jump ahead. Mixing in different practice material helps: random groups, then real words, then callsigns, then actual text. Listening to on-air code, even if you only catch fragments, helps too. ARRL's W1AW sends code practice at set speeds on a published schedule, so check their site for the current times and frequencies. For confidence, don't wait until you feel perfect. Work up a few predictable exchanges you can handle: your callsign, a signal report, your name and location, and a polite sign-off. Those are repetitive enough that you'll recognize them even at a modest copy speed. Answer a station that is calling CQ slower than you can copy at full speed. Many CW operators will slow down if you ask with QRS, and it's perfectly acceptable to say you're a new CW operator. A first contact or two with a patient operator does more for your nerves than another month of practice alone. Keep the key or paddles feeling easy too, because struggling with sending adds pressure to the receiving side. Practice sending at the same time as you practice copying, and record yourself so you can check your spacing.
  2. Adding the operating-procedure side, plus phone, RST and logging. CQ is a general call to any station. "CQ CQ CQ DE N0CALL N0CALL K" means "calling any station, this is N0CALL, go ahead". N0CALL is a placeholder, not a real callsign. DE just means "from". On phone you'd say "CQ, this is..." instead. Variants like "CQ DX", "CQ POTA" or "CQ TEST" limit who you want to hear from. K means "over, any station go ahead". KN means "go ahead, but only the station I'm talking to", so others should not break in. People use KN when they don't want other stations calling in. SK is the end-of-contact prosign. Don't confuse it with "silent key", which is a separate use of the same letters meaning a deceased amateur. Other prosigns you'll hear are AR (end of message), BK (break, back to you) and CL (closing the station). On CW these are sent run together as one character. 73 means best regards and is the standard sign-off. 88 means love and kisses. It's friendly and used among close friends or spouses, so most people won't use it with a stranger. RST is Readability (1 to 5), Strength (1 to 9) and Tone (1 to 9). Tone is only used for CW, so phone reports are just RS, such as "5 by 9". A CW report of 599 is perfect on everything. In contests 599 is often sent regardless of conditions, so don't treat it as a measured value in a casual QSO. A real report is more useful. If a signal is weak with QSB and QRN, give your honest numbers and say so. On phone, plain language is generally preferred. Q codes like QTH, QSL, QSY, QRM and QRZ are widely understood and used, but many operators just say "location", "confirmed" or "change frequency". Avoid CB-style ten-codes. They aren't ham convention. For logs and nets, a basic log line usually has date and time in UTC, callsign, frequency or band, mode, RS or RST sent and received, name, QTH, and notes. Net terms you will hear include NCS (net control station), check-in, roll call, late check-in, traffic, relay and liaison. "Break" is normally reserved for urgent or emergency traffic. In a directed net you wait for NCS to call you instead of just transmitting. On a casual net, listen first, then give your callsign and say "checking in".
  3. On receive, I would separate two ideas: filter width and passband position. When the signal is weak but there is nothing next to it, a width of about 2.4 kHz often sounds natural and keeps the speech intelligible. When there is a strong signal on one side, shifting the passband can help more than shrinking the width, because you get rid of the interference without cutting out as much of the wanted voice. Narrowing the filter also cuts noise, but it affects tone, so use your ears and judge by readability rather than by how much quieter it sounds. Also be careful with noise reduction. It can make weak speech sound smooth, but it can also add watery artifacts and hide the consonants that carry the callsign. For DX, try the filter and AGC adjustments first, then add NR only if it improves the copy. If a station is on the edge of the noise, copying the callsign matters more than making the audio pleasant, so a plain, slightly noisy receive signal may be better than a heavily processed one. For transmit, the same logic applies. Under pileup conditions, a clean 2.4 kHz-ish signal with moderate compression and a clear callsign usually beats a wide, bass-heavy signal. The other station only needs to decode the information, not enjoy a broadcast-quality sound.
  4. A tip that saves trouble: keep one master log and treat every upload as an export from it. If you correct a callsign or a time in one place but not another, you end up with a QSO that matches on LoTW but not on Club Log, and then you waste time figuring out why. Before any big LoTW upload I check the station location settings. If you operate portable or from another DXCC entity, make a separate TQSL station location instead of editing your home one. That keeps the grid, zones and entity correct for each batch of QSOs. Also note that the certificate has a date range, so QSOs outside it won't sign. That matters if you're loading old logs. For paper, I'd only send direct when the QSL info says it's needed or when the card has real value to you. If the operator uploads to LoTW or accepts Club Log OQRS, that is usually easier than hunting for the right address and postage.
  5. The split makes sense, and the rule I'd keep is that anything that can damage hardware must be safe when the Pi is dead. A Pi hangs, an SD card gets corrupted, a script throws an exception halfway through a sequence. The microcontroller should boot into a known state, ideally with all relays in a default position that grounds or parks the antennas. It should also have a watchdog, so if the Pi stops sending heartbeats for a few seconds it goes back to that state. For the PTT interlock, it's best to bring a PTT sense line into the controller (an opto-isolated input from the rig's PTT or from the keying line) and refuse to switch while it's active. Doing this in firmware gives you a real guarantee that software on the Pi can't violate. Hot switching is hard on relay contacts, and with an amplifier in the chain it can also destroy things downstream. A short delay (a few tens of milliseconds, chosen from the relay's datasheet) between dropping TX and switching is cheap insurance. For relay drive, put a flyback diode across every coil, use a driver such as a ULN2003 or discrete MOSFETs, and keep the relay supply and its return routed separately from the logic supply. With latching relays, store the last state in non-volatile memory, but also treat the stored state as a hint and re-drive the relays on boot rather than trusting it.
  6. Start with the logistics, because they shape the plan. Element 3 is 35 questions drawn from the current General pool, and the pass mark is 26 correct. That leaves room for about nine misses, so you don't need perfection, but you can't skip a whole topic either. Pool editions rotate on a multi-year cycle, so check which pool is in effect on your exam date and make sure your practice tool matches it. Since you already passed Element 2, you only need Element 3. On HF, think of Technician privileges as a few narrow slices and General as most of the HF spectrum. Technicians have limited CW privileges on 80, 40 and 15 meters, plus 10 meters, where phone is allowed in the upper part of the band at reduced power. General adds phone and data segments on 160, 80, 40, 20, 17, 15, 12 and 10 meters, plus CW/data on 30 meters and access to the 60 meter channels. Don't just memorize frequency numbers. Draw each band as a bar, mark where CW/digital ends and phone begins, and note the exceptions: 30 meters has no phone and a 200 watt PEP limit, and 60 meters is channelized with its own rules. The exam often asks whether a given frequency, mode and license class combination is legal, so practice that format. Then check your notes against the current ARRL or FCC band chart, since you should not rely on any forum post for band edges. For study weighting, I'd split it roughly like this: Heavy: band privileges and operating rules, propagation, and antennas/feed lines. The rules questions are the most memorization-driven, while propagation and antennas reward understanding. Medium: electrical principles (Ohm's law, power, dB, reactance and impedance basics) and digital modes. If you are shaky on math, learn the dB shortcuts: 3 dB is roughly double the power, 6 dB is four times, 10 dB is ten times. Light but easy points: safety, RF exposure, and general operating courtesy.
  7. On SSB, automation helps most with the details that are tedious to do by hand. With an inverting bird like RS-44, you have to move the uplink opposite to the downlink, and also correct both for Doppler. Software that does both lets you tune the downlink dial and have your transmit frequency follow it, so you can hear a station calling CQ, answer on the right frequency and stay in the passband. If you tune by ear without automation, it is workable, but you will tend to chase your own signal around during the first few minutes of a pass, which is where the shift is largest. One practical tip about Gpredict and SatPC32: set up the radio's mode and offset in the tracker. Many beginner problems come from uplink and downlink drifting because the radio's RIT/XIT, split or sideband was set wrong, not from the software. Listen to your own signal on a second receiver, or an SDR, before you assume anything is broken. For a mixed station, a common step up from handheld Yagi is a small az/el rotator with two Yagis on a short boom. Make sure the controller's elevation limits and the cable strain relief are right before the first live pass. And keep power low on the uplink: with a good antenna, a few watts is often enough, and a nearly full-power signal on a linear transponder will wipe out the weaker stations.
  8. Start with the clock. FT8, FT4, WSPR and Q65 all depend on both stations being within a fraction of a second of true time. In WSJT-X the DT column tells you how far off you are. If your decodes cluster at +0.8 or -0.6 instead of near zero, fix the clock before touching anything else. The default Windows time service syncs infrequently, so a dedicated NTP client or a GPS-disciplined source is the usual fix. Make sure the correction is actually being applied and not only displayed. Second, audio level. The rig's ALC should show little or none on a data mode. If the ALC is moving, the audio drive is too high. The result is splatter and a signal that looks fine on your own waterfall but is wider than it should be. Turn the PC output down and set power with the rig's own power control. Also disable system sounds and any audio "enhancements" on the interface's sound device, because a notification chime going out over the air is a very real failure. Third, CAT. The usual culprits are mismatched baud rate, stop bits or rig address (on CI-V radios), a USB virtual COM port that renumbered after a reconnect, and two programs fighting for the same port. If WSJT-X reports a rig control error, confirm that nothing else (a logger, a rig control program) holds the port. In the Radio settings, "Split Operation" with Rig or Fake It keeps the audio tones in a clean part of the passband. It does this by shifting the dial frequency, not by pushing the audio offset around. On PTT: CAT PTT works well when the rig supports it cleanly. RTS/DTR through a serial line is fine, but some USB chips toggle those lines at port open, which can key the transmitter momentarily. VOX on a data mode is the most fragile of the three.
  9. until

    In-person amateur radio license testing at the Ames Public Library on Oct 17, 2027, from 2:00 to 4:30pm CDT. The test fee is listed as free. The team requires pre-registration. Computer-based in-person testing will be offered.Location: Ames Public Library, 515 Douglas Ave, Ames, IA 50010, USA Organizer: AMESIA: Story County ARC VE Team Source: Event information
  10. I'd separate three questions that get mixed up: how do I reach the station, how do I authenticate, and what can an attacker do if they get in? Port forwarding the radio's control port to the internet answers the first question and fails the other two. A VPN into the LAN (WireGuard works well for this) means a single, well-understood entry point. If you use SmartLink or a hosted service instead, check how accounts, keys and permissions are handled, and keep those credentials unique. For latency, I'd measure rather than guess. Run a continuous ping and look at the variation, not just the average, and test under real conditions such as evening home-network load or a mobile hotspot as the client. Jitter buffers can hide some problems on SSB, but they add delay, and that makes CW and rapid exchanges harder. For CW, local keying at the station is a sensible design. For digital modes, run the decoder on the station side or at least confirm your time source is good. On licensing, don't assume your home privileges travel with you. The rules usually care about where the transmitter is and which licence you hold for that country, and a contest or an award may add its own requirements. Check each one before you plan a weekend around a remote station.
  11. I would keep that order, with one addition: look before you measure. A quick visual pass with a magnifier will often show a burnt resistor, a leaking electrolytic, a cracked joint near a heavy connector or a loose ribbon cable. Also look at anything that has been modified, because an earlier fix may be the real cause of the current fault. Photograph the board before you remove anything. On the SWR point, an easy trap is to test the rig on an antenna and then draw conclusions. A dummy load takes the antenna, the coax and the tuner out of the picture. If the fault follows the rig onto the dummy load, the problem is in the radio. If it vanishes, stop opening the case. On the finals, I would add the cautionary note that a quick replacement without checking bias is how people kill a second set. Measure the idle current at low supply voltage first, and do not trust that it is right just because the transistor is new.
  12. Your math is sound. The usual mistake is budgeting only transmit current when receive and ancillary loads are what drain the battery over a long deployment. A 100 Ah LiFePO4 battery is roughly 1,280 Wh nominal, and you shouldn't plan to use every watt-hour of it. For a true 24-hour run at your numbers you either want about 200 Ah, or you accept scheduled generator charging. Cutting the laptop's draw (screen dimming, a more efficient machine) is often the cheapest saving. For the generator question, I'd lean toward running it in blocks rather than continuously. Inverter generators tend to be more fuel-efficient under a moderate load than at idle, so a decent DC charger pulling a steady load for a few hours is a better use of fuel than keeping it running for a 150 W station. You also get long quiet stretches for weak-signal work and for people sleeping. Pick a charger rated for LiFePO4 (typically around 14.2 to 14.6 V absorption), and don't assume an old lead-acid charger with an equalize or desulfation mode is safe for the bank. A few practical points on distribution. Fuse close to the battery, then run everything through a fused distribution block with Anderson Powerpole-style connectors so polarity and pin orientation are standardized across the whole team. Check what your battery's BMS does at low voltage. Many simply disconnect, which drops the radios without warning, so a voltmeter on the bus helps you act before that happens. Also check low-temperature charge protection if there's any chance of near-freezing nights, because charging LiFePO4 below freezing damages the cells unless the battery has heating or a low-temperature cutoff. For the generator itself: keep it well away from the shelter and downwind, never inside or under the canopy, and keep fuel stored and handled away from the operating area. Carbon monoxide is the real hazard here, and an enclosed or partly enclosed tent makes it worse. Treat it as a safety item on the checklist, not an afterthought.
  13. On tracking software: both work. Gpredict is fine for pass prediction, mapping, and driving a radio through Hamlib's rigctld and a rotator through rotctld. SatPC32 has been a long-time favourite on Windows for people who want tight CAT and rotator control from one program, and it works well with older rigs. The most important thing with either is fresh Keplerian elements (TLEs). Stale elements mean the predicted time and direction slip, and your Doppler correction drifts with them. Update before each session. RS-44 behaves differently from the FM birds. It's a linear transponder, and it's inverting, which means that when you tune your uplink higher, the downlink moves lower. The usual convention is to transmit LSB on 2 m and receive USB on 70 cm, so your signal appears with the correct sideband in the downlink. CW stays CW. Since the transponder passband is wide (tens of kHz), you can hear many stations at once, and you can find your own signal in the downlink. The standard technique is to pick a downlink frequency, correct for Doppler, and then adjust your uplink so your own signal lands where you want. If your radio can't be tuned while keeping the downlink fixed, software-controlled Doppler becomes close to essential. A practical setup question is full duplex. Hearing yourself in the downlink while you transmit is what makes linear operation easy, so you'll want either a radio that can transmit and receive on different bands at the same time, or two radios (for example a transceiver plus an SDR or a second receiver). With FM satellites you can be half-duplex and still do fine, so you can postpone that purchase. Rotators: you don't need them until holding an antenna by hand starts to compromise the contact. Hand-aiming works well for FM and for ISS passes. A pair of rotators, one for azimuth and one for elevation, becomes valuable when you want a larger Yagi, more gain on low-elevation passes, or both hands free for logging and tuning. Remember that on higher passes the elevation and the azimuth sweep happen quickly, so a rotator with slow movement can lag. Grid squares: for most contacts, 4 characters is enough (for example FN31). Learn yours, and learn how to look up your partner's. Some operators, and many award programs, care about worked grids, so it's worth logging them from day one. QO-100 is a different world. It's geostationary, so there's no Doppler to correct and no passes to schedule. You need a fixed dish setup, with an uplink in the 2.4 GHz range and a downlink around 10.489 GHz. It's usually a better fit once you've done LEO and want a steady station. Check the transponder plan and the satellite's coverage before you buy any gear.
  14. One thing worth adding about exercises is that they are most valuable when they test the boring parts. Everyone wants to practice the dramatic scenario, but the weak points usually show up in unglamorous places: nobody knows which frequency is the backup, the net control operator has no relief scheduled, or a message gets copied three different ways because nobody read it back. If your group runs drills, try assigning someone to just observe and note what slowed things down. A simple after-action review covering what worked, what did not and what to change is more useful than another round of check-ins. Also try practicing with a primary mode down. If your plan relies on a repeater, run part of the exercise on simplex. If your plan relies on voice, try a few written messages through a digital mode your group supports. You want to find out in practice, not in an activation, that half the team cannot program the backup channel. For the credentialing question, the answer varies a lot by jurisdiction, so I would ask the emergency management office directly instead of relying on what another county does.
  15. On HF the biggest improvement usually comes from treating the audio chain as part of the transmitter. If the rig has a data mode with a flat audio path, use it. Otherwise USB with the processor off is the next best option. Then set the drive from the software's tuning or test tone and watch the ALC. If the ALC is moving, back off the audio before you touch the power control. A cleaner signal at lower power connects more reliably than a strong, distorted one. For gateway choice, don't connect to only the closest station. On HF, a gateway a few hundred miles away on a band that is open at that hour can work better than a nearby one on a band with a skip zone. Try two or three from the channel list and note which ones answer. If a gateway never answers, the usual reasons are band conditions, a busy channel, wrong frequency offset, or a rig set to the wrong sideband. Check those before you change the modem settings. One caution on VARA HF: the free unregistered mode is slower, and what you get depends on the registration state. If you plan to use it in an exercise, test it ahead of time instead of finding out on the day. ARDOP is a good fallback because it has no license cost and works well on weak or noisy paths, even though it is slower.
  16. For a first activation I would lean towards VHF if there are local chasers and the summit has a clear path to populated areas. A handheld with a decent antenna and a few spare batteries keeps the pack light and the setup quick, so you can reach four contacts early and then decide whether to try more. Check that your region has activity on 2 m FM and use the SOTAwatch alert to tell people which frequency to expect. Remember that VHF depends on line of sight, so a valley summit may be tougher than the numbers suggest. HF gives more reach, but it also means an antenna, a feedline, and more things to get wrong in wind and cold. You can add it on a second trip once the routine of climbing, setting up and logging feels easy.
  17. Good framework. One thing I'd add on reading the operator: the way the DX picks callers often reveals more than what he says. If he is consistently picking out stations calling at the low end of the range, move there. If he picks the strongest signal every time, calling more often won't help, but a better antenna or a different band might. If he picks stations with a particular letter or number in the call, don't keep calling when it isn't yours, as it only adds to the noise. On split specifically, I'd stress checking your transmit frequency with the 'A/B' or 'TX monitor' function before you call, and making sure your radio really is transmitting where you think. It is easy to find you've been calling on the DX's own frequency or on a different mode setting. Also remember that wide pileups drift: stations spread out and the cluster of callers moves up. Re-check where the operator is listening every so often. He may change the range without announcing it clearly. On tailending, I'd treat it as something to use sparingly. If the pileup is large and orderly, the better approach is to call in the natural gap after he sends his call or 'QRZ'. If you must try to catch the end of a QSO, make sure you aren't stepping on the other station's final exchange. And if you're called by someone else calling over you ('QRM from the pileup'), don't respond by calling louder, just wait. For SSB, short and clean beats clever. Standard phonetics, your call once, then stop. On FT8, if the DX is using the Fox/Hound mode in WSJT-X, follow the instructions for Hound operation: call above the limit specified by the Fox and let the software handle the frequency shifts, rather than calling on the Fox's own frequency.
  18. Boundaries are the thing I would check first. A KFF reference and a POTA park can share a name but still not cover exactly the same ground, and some areas have special zones or restrictions. Look at the official maps for each program, and check the land manager's rules on equipment, antennas, vehicles, quiet hours and where you may set up. A nature reserve can be stricter than a typical recreation park, so supports, wire antennas and generators may be restricted. Always follow the site's rules first, and the program's rules second. For logging, I'd keep one master log and export the program-specific files from it, with the correct reference on each. Then open the exported files and read a few records before uploading. A wrong or missing MY_SIG_INFO is an easy mistake and can mean the activation isn't credited properly. If your software can't do dual-reference exports cleanly, a short script or a manual edit is fine as long as you keep the original log intact. For hunters, the useful habit is to log the reference exactly as the activator gives it, and to check later whether the contact appears in your WWFF record. If something is missing, it is usually either a typo in the callsign, a mismatched reference or the activator not having uploaded their log yet. For awards and diploma details, go to the official WWFF site and your national coordinator, since class levels and application procedures are managed there.
  19. For propagation, I'd split it into forecast and evidence. NOAA's Space Weather Prediction Center is the place for flare, geomagnetic and solar wind alerts. Solar flux gives a rough idea of how well the higher bands might support F2 propagation, but it doesn't tell you whether a path is open to your target region at this moment. For that, use live spotting. PSKReporter shows who is hearing digital signals on a band, RBN shows CW and RTTY skimmer spots, and WSPRnet gives you a steady record of low-power path data. If 10 meters shows FT8 spots from several stations toward Europe, that's an opening. A good solar number alone is not. Also keep in mind that a spot only means that a receiver somewhere heard a signal. Your path, local noise floor and antenna may give a different result. A geomagnetic storm can also help on some paths, such as higher-latitude ones, and wreck others, so it's worth watching the K index before you give up on a band.
  20. For special event stations, the best approach is the same as in a DX pileup: listen first. Work out whether the operator is calling by call area, taking any caller, or running split. If the station says "up" or "split", don't call on its transmit frequency. Once you know the pattern, give your call sign once or twice and wait. Repeating it ten times rarely helps. The exchange is usually minimal: call signs, a signal report and sometimes your state or section. Keep your reply short so the operator can keep the rate up. Write down the date, time (UTC is easiest for later matching), band, mode and call sign as you work the station. If the event has a certificate, check whether the sponsor requires you to request it through a web form, a log search or by mail. Operators sometimes use several bands and modes, and a few awards only count contacts from certain days or bands. Also look for a QSL option, which may be paper, electronic or both. One more point: a commemorative call sign is part of the event's identity, but the legal ID still matters. Operators should identify properly and follow their license terms. If you are thinking of running one yourself, set a schedule, tell people where to find the details, and assign a logger so the contacts are recorded cleanly for the certificate requests that follow.
  21. I'd add something about identification, because that's where callsign rules affect daily operating. You ID at the end of a communication and at least every ten minutes during one, using your assigned call. Using "portable" or region designators, like W1ABC/5, is optional under current US rules. It's often used for clarity, but it isn't a requirement, and it doesn't alter what your license authorizes. For clubs, the trustee matters more than people expect. The trustee is the licensee of record, so if the trustee moves away or leaves the club, someone has to take over properly through the administrator, not informally. A club call is easy to lose track of if the paperwork isn't kept current. For special events, the 1x1 call is temporary and tied to the event dates, so announce your normal call too if the net or QSL arrangement calls for it. And for lookup, use ULS for anything official. If QRZ and ULS disagree about an address or class, ULS is the legal record.
  22. On names and places: spell what can't be guessed, and be explicit about when you're spelling. Something like "My name is Sean, I spell that Sierra Hotel Echo Alfa November. QTH is Tallahassee, I'll spell that." Announcing the spelling gives the other operator time to get pen and paper ready. Spell only the part that's ambiguous. Common words like "Paul" or "Chicago" usually don't need it, but unusual place names, surnames and anything with silent or doubled letters do. After spelling, give the word again at normal speed so it lands as a word rather than just a string of letters. In nets and traffic handling, discipline matters more than style. Net control wants short, standard exchanges. A check-in is typically just your callsign, with the suffix in phonetics and maybe your name and location if the net asks for them. Don't pad it with extra chatter. Wait for net control to acknowledge you, and use "over" or a clear pause when you hand back. Avoid "over and out" because it contradicts itself. "Out" or "clear" is the end of the exchange, while "over" invites a reply. For emergency and priority traffic, plain language is the rule. Don't invent codes, and don't use Q-signals or ten-codes unless everyone involved knows them. Say clearly what the traffic is (emergency, priority, welfare, routine), who it's for and what's needed. For formal message handling such as ARRL radiograms, numbers and text have their own conventions. For example, "X" can stand for a period in the text, and groups are read out clearly with spelling when needed. Follow whatever your served agency or net uses. When conditions are poor, speed isn't your friend: Slow down slightly and keep your rhythm even. Rushing clips syllables and makes phonetic words run together. Keep your audio moderate. Over-driving the mic or shouting adds distortion and doesn't help copy. Lean on the words that carry the most distinction. If M and N are getting confused (Mike and November), say them with an emphasis on the first syllable. B, D, P, T and V are classic problem letters, and phonetics resolve them well. If the other station asks for "fill" or says "say again," repeat just the part they missed, in phonetics, instead of re-sending everything. On CW the equivalent habits apply. Prosigns like AR (end of message), SK (end of contact), BT (break) and KN (go ahead, specific station only) are sent as single run-together characters. They have no voice counterpart beyond words like "over" and "clear." Getting the spacing right is the CW version of speaking clearly.
  23. Here are the analog basics. A repeater receives on its input frequency and retransmits on its output frequency. Your radio transmits on the repeater's input, so "offset" means the difference between the two. In the US, 2 m is commonly 600 kHz and 70 cm is commonly 5 MHz, but the direction (plus or minus) depends on where in the band the output sits. Other regions use different numbers, for example 600 kHz on 2 m but 7.6 MHz on 70 cm in much of IARU Region 1. Always check the local bandplan rather than relying on your radio's auto-offset feature. The tone confusion usually comes from the fact that CTCSS is used in two directions. The tone your radio sends to open the repeater is the access tone, which is usually what a listing means by "PL" (a Motorola trade name for CTCSS). Some repeaters also transmit a tone on their output. If your radio is set for tone squelch (often called TSQL), it stays silent until it hears a matching tone on the received signal. That is handy for cutting down on noise and on other users on a shared frequency, but it can hide the fact that you are being received weakly or that someone else is on the channel. For a first setup, it is usually simpler to transmit the access tone and leave receive tone squelch off until you know what the repeater sends. DCS is the digital counterpart to CTCSS: a continuous low-speed data stream with a three-digit octal code. Not all radios treat polarity the same way, so if a DCS repeater won't open, check the normal/inverted setting. Neither CTCSS nor DCS provides privacy or security. They only control which signals open a squelch. A few etiquette points apply on almost any repeater. Listen first, since you may be about to step on a net or a conversation. Pause for a second or two between transmissions so someone with an urgent need can break in. Keep transmissions short, because the time-out timer is typically a few minutes but is set by the owner and may be much shorter. Identify according to your local rules (in the US, at least every ten minutes and at the end of a communication). And skip the repeated kerchunking to "test" the repeater, which just keys it up with nothing to say. If you want to check that you are getting in, say your callsign and ask for a signal report.
  24. One point that gets overlooked: confirmations are only as good as the logs behind them. If your own log has a wrong date, an off-by-one UTC day, or a typo in the other station's callsign, none of the methods will fix it. Cards come back marked "not in log", and LoTW simply never matches. Cross-check against what the other station logged, particularly after contests or pileups where a call can be copied incorrectly. For OQRS and direct requests, give the operator what they need to find you quickly: your callsign, date, time, band and mode, all matching your log. For card design, keep a layout that leaves room for the QSO details. A beautiful picture on the front is fine, but a crowded back makes it harder for the other operator to verify the contact, and a card that's hard to read may not get a reply. And if you handle bureau cards, learn your own society's sorting and envelope rules, because mistakes there can delay everything.
  25. I'd treat the forecast as a hypothesis and the beacons as the test. A common routine is to look at SFI and K to decide which band to try, then tune to the NCDXF frequency for that band and listen through one full 3-minute cycle. Because each beacon steps down from 100 W to 100 mW, you can see how much margin the path has. If you only hear the 100 W transmissions, the band is marginal and it may not support a normal CQ. If you hear the 1 W or 0.1 W slots, there is a lot of signal to spare. The caveat is geography. The beacons only cover the paths from where they are, so a quiet frequency might just mean none of them have a path to you, not that the band is shut. That's where WSPR or PSKReporter help, because you can see your own transmitted signal being decoded at distant stations, which is the direct answer to "can they hear me?"

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.