Everything posted by Mod_Nancy
-
Which spotting and lookup tools actually earn a spot in your shack workflow? DX cluster, RBN, PSK Reporter, POTA/SOTA and more
For the POTA/SOTA side, a few practical points apply whichever app you use. As a hunter, check the mode and frequency on the spot and look at its age. A spot from forty minutes ago may be a finished activation. As an activator, put your reference, band and mode in the spot comment, and respot if you move. Short, accurate comments keep the page readable for everyone. For phone use, I'd pick one app or site as the main alert source and save the rest for lookups. Notifications from three different sources mostly just duplicate each other. If you travel, download or cache the repeater listings you need first, since cell coverage on a trail or in a rural park is often poor. RepeaterBook-style data is also a starting point rather than a guarantee. Offsets and tones change, and some systems are closed or have restricted access, so check the listing details before transmitting. And a quick tip on grids: when you're unsure of your own locator, take it from a map tool or your logging software rather than guessing. A wrong sixth character can mislead anyone using your grid for distance and bearing.
-
Run vs. S&P vs. chasing mults: how do you decide when to leave a good run frequency?
On the rate threshold, a fixed number is less useful than comparing the short-term and long-term rate displays in N1MM. If the last-10-minute rate is far below the last-hour rate, something has changed: the band is fading, a competitor has set up nearby, or your CQ timing is wrong. That's the point to take a mult excursion, because the cost of leaving is lowest when the frequency isn't producing anyway. This is where SO2R can pay off most directly, and it's often misunderstood. The usual model is to run on Radio 1 and use Radio 2 to look for mults on another band while your CQ repeats. The second radio is valuable mainly because it fills the gaps in your own CQ cycle, not because it doubles your rate. That means the CQ message length and gap time matter. A very short message with a short repeat gap gives you little time to look at the other radio, while an overly long gap gives up rate on the run. Many people tune this by trial and error until the cycle fits the way they listen. Practical SO2R points that get overlooked: Isolation first. Transmitting on one band while listening on another only works if your receiver isn't overloaded. Band-pass filters, stubs, or well-separated antennas are often the difference between SO2R working and merely being possible. Same-band operation on two radios is a much harder problem and needs very good separation.Transmit interlock. You want hardware or software that prevents both radios from transmitting at once. Test this on the bench, not during the contest.Audio. Stereo headphones with the option to put one radio in each ear, plus an easy way to swap or blend, reduce the mental effort of following two receivers. Switching that takes your hands off the keyboard slows you down, so a footswitch or a dedicated key is worth setting up.Don't S&P on Radio 2 while ignoring Radio 1. If a caller on the run frequency is waiting and you're deep in a pile-up elsewhere, the discipline is to finish quickly or return. Running slows the whole operation if you keep half-answering.For skimmer and packet spotting: unassisted vs. assisted categories exist precisely because spots change what an operator can do. Check the rules of the specific contest. Some allow a locally run skimmer feeding your own bandmap in unassisted classes, others treat any outside spot source (including the Reverse Beacon Network) as assistance. Don't assume the rule is the same from one contest to the next.
-
Technician to General: how should I split study time across the 35 questions on Element 3?
Your split is reasonable, but I'd change the order. Start with a full practice exam before you study anything. It shows which of your six areas actually need time, and for a Technician that's usually the HF privilege questions and the electrical-principles math, not the digital modes. Then study the weak areas and retake full exams until you're consistently above 26/35, with a cushion. Scoring around 80 to 85% on several different practice exams is safer than barely passing one. For band edges, learn the pattern first and the exact numbers second. CW and data segments sit at the low end of most bands, phone sits higher, and 30 meters is the odd one: CW and data only, with a lower power limit. If you've seen the pattern, the numbers stop being random and are easier to hold in your head. Then use flashcards or a printed band chart for the exact edges. Because those edges can change when the rules do, check the current FCC Part 97 rules or the ARRL band chart for the privileges you're actually tested on, and 60 meters especially, since it works differently from the other bands. For the math, do the calculations by hand a few times, even if the exam question is multiple choice. Ohm's law, power (P = E × I and its variants), and the resonance and reactance relationships show up in several forms, and the distractor answers are usually the results of a common mistake, like forgetting to square something or mixing up kilohms and ohms. If you can recompute the answer, you'll catch that.
-
Studying for the Amateur Extra (Element 4): what's worth the time, and what do you actually gain?
On what Extra gets you: Extra class has every frequency privilege on every amateur band. Where General holds back is in a few small segments near the low ends of the HF bands, such as parts of 80, 40, 20 and 15 meters. A General can't operate in those segments, and an Extra can. Those slices are often busy during contests and DX activity, so having them can be useful if you operate in those areas. Check the current band-plan chart from the ARRL or the text of Part 97 for the exact edges instead of relying on a forum post. Beyond frequencies, Extra also lets you serve as an accredited volunteer examiner for every element, subject to the VEC's rules. Some operators also care about access to the shorter call sign groups when picking a vanity call. For the Part 97 questions, I'd suggest reading the rules and not just the questions. The exam tends to ask about things like authorized emission types and the standards that go with them (97.305 and 97.307), power limits (97.313), station identification (97.119), and the rules for special operations like beacons, remote control, and auxiliary stations. If you understand why a rule exists, the answer choices are easier to separate. A lot of wrong answers look plausible but contradict the purpose of the rule, such as controlling interference, keeping control-operator responsibility clear, or keeping the station identifiable. One more tip for the design and modulation sections: for FM, modulation index is peak deviation divided by modulating frequency, and Carson's rule estimates bandwidth as about twice the sum of deviation and highest modulating frequency. A few of those formulas show up repeatedly in different wording.
-
Turning SET and Field Day into real disaster-comms practice: what are you testing, and how do you capture it?
I would add a point about message accuracy. When a group runs a drill, it is tempting to count messages passed. A better measure is whether the received text matches the original, and whether the right person got it in a reasonable time. A simple method is to have the originator keep a copy and compare it with the delivered copy afterward, marking each discrepancy as a dropped word, a changed number, a wrong name, or a missing signature. On net scripts, I like the idea of a separate short script for "net control lost" and for "switch to alternate frequency or mode," because those are the moments when people improvise. Also be careful about plain language with agencies. Ten-codes and ham shorthand can confuse non-radio partners, so many groups practice saying exactly what they mean in ordinary words. And for the served-agency side, ask the agency to critique the exercise as well. Their view of what was useful may differ from yours, and that belongs in the after-action report.
-
Setting up APRS properly on 144.390: Direwolf iGate, handheld trackers, Mic-E, SmartBeaconing and what to put on the channel
A few notes on the iGate side that save time. Start with the IGSERVER and login: if the passcode is wrong, Direwolf will connect but APRS-IS will treat you as receive-only, so your packets get no gating. Check the Direwolf output for the login result. On RF-to-internet traffic, it is normal for a well-run iGate to gate only packets it heard directly, or after a limited number of hops, and it should not forward packets that already came from the internet. Internet-to-RF gating is typically limited to messages, and only for stations heard locally on RF within a recent time window. If you enable it on a busy channel, keep it tight. It is easy to create loops or flood a shared frequency with traffic nobody needs. For the beacon, give the iGate an accurate position, a clear symbol and a short comment, and beacon rarely. Every 30 minutes is plenty for a fixed station. Longer comments mean longer packets and more collisions on 1200 baud. On the radio side, if you have a choice, use the data or discriminator audio connection rather than the speaker output. Speaker audio is shaped for voice and may lose volume or add distortion at the tones. If you run an RTL-SDR instead, the same Direwolf decoder applies, but you will not be able to transmit digipeated or beaconed packets without a separate transmitter.
-
Net schedules, check-ins and special event stations: what makes a net or on-air event worth joining?
One thing that helps new check-ins is a very predictable structure. If net control says the same few things in the same order every time (name, purpose, who can check in, how to call), a newcomer can listen for a minute and know exactly when to jump in. Nets that sound improvised can feel like a closed club even when everyone is friendly. For ARES and SKYWARN in particular, I'd also keep the script and the local plan side by side. The script should say what the net is for and who activates it, so nobody has to guess whether a check-in is a drill, a weather report or real traffic. Speaking clearly and slowly matters more than sounding polished, especially on noisy 75 meters. Another practical point: have a backup net control and a backup frequency decided in advance. If the primary operator drops out or the band goes bad, the net doesn't have to dissolve.
-
Getting started with LEO satellites: FM birds vs. linear transponders, Doppler handling, and which antenna setup to build first
On the linear side, RS-44 is a very different experience from the FM birds. The orbit is higher, so passes are longer and the footprint is larger, but the signals are weaker for the same power and antenna. Expect to need better pointing and probably a preamp on receive. The transponder is inverting, so if you do manual Doppler, keep that straight: when you move the uplink up, your downlink goes down. Many people get frustrated until they internalize that. A practical workflow for SSB/CW: find the beacon or a known station, set your downlink to the frequency where you want to listen, then adjust the uplink until you hear yourself on that same spot. In software, a tracking program with a Doppler-corrected tuning knob helps, but in the end you still need to listen and nudge. If you use SatPC32 or Gpredict with CAT, check whether it is tracking the uplink or downlink and which it treats as the "master" frequency, because the defaults can surprise you. For CW, a narrower filter and a bit of RIT helps. Keep your power moderate. If you overdrive the transponder you hurt everyone else, and you will also hear your own signal distorted, which tells you to back down. As for QO-100, it is worth a mention that the learning curve is not tracking but frequency stability. At 2.4 GHz uplink and 10 GHz downlink, a drifting local oscillator in your LNB can move your received frequency noticeably, so many people use a GPS-disciplined reference or a frequency-corrected LNB. It is a very different hobby from chasing LEO passes, and a good complement once you are comfortable with the basics.
-
Dead or sick rig: a sensible order of attack for no TX, no RX, protection faults and noise
Good order. One habit worth adding: before opening the case, look at what the rig does at power-up. Does the display come on? Do relays click? Does the current draw look sensible on a bench supply meter? A rig that draws no current at all points at the fuse, the power switch, the input protection diode or the connector. A rig that pulls too much current and gets warm points at a shorted part, and you can often find it by feeling for the hot component or by using freeze spray on a bench supply with the current limit set low. On the SWR protection question, a dummy load check is the quickest way to split the problem. If power output is normal into the load but cuts back on the antenna, you're looking at the feedline or antenna. If it's still limited into a known-good load, the detector or the protection reference voltage is more likely. Also compare the forward and reflected readings on the rig's own meter with an external meter if you have one, because a detector that has drifted can make a good antenna look bad.
-
Technician to General: how to study for Element 3 (35 questions) and what you actually gain on HF
Your plan is sound. The pool is public, so practice exams are the core of the work. The trap is memorizing answer letters instead of the reasoning. Try a first-pass test cold to find weak areas, then study those topics, then take timed 35-question sets. Consistently scoring in the high 80s or above gives you a margin over the 26-correct line. Most good practice sites report scores by topic, which tells you where to spend the next session. For electrical principles, you don't need heavy math, but a few relationships come up repeatedly. These are Ohm's law and the power formulas (P = I x E, P = I squared x R), RMS being about 0.707 of peak for a sine wave, and the dB rules of thumb: 3 dB is double the power, 6 dB is four times, 10 dB is ten times. Resonance is where inductive and capacitive reactance are equal. Know what impedance matching means and why SWR matters for the transmitter and feed line. Work a few examples by hand until the formulas stop being a blur. On the sub-bands, you do need to know them, because the pool asks things like which frequencies a General can use for phone on a given band. Use the ARRL band chart or the FCC rules (Part 97, the sections on authorized frequencies) as the authority rather than memory or a forum post. A useful memory trick is to learn the Extra-only slices at the bottom of 80, 40, 20 and 15 meters first, then the phone/data split on each band, and add 30 meters' 200 W PEP limit and the special case of 60 meters last. Vanity calls are separate from the upgrade. Technicians can apply too. What changes is that the call sign groups you're eligible to request depend on your license class. If you like your current call, there's no need to rush. If you want to change it, the application has a fee and the FCC's current process applies, so read their instructions before filing.
-
Band plan vs. FCC rules: where do I actually operate, and how close to the band edge is safe?
On 60 meters, the US operates by channels rather than a continuous segment. There are five channels, shared with federal users, and amateurs are secondary. The commonly published USB dial frequencies are 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5 kHz. USB is the standard phone sideband there, and CW and data are also permitted. General class and above can use it, with an ERP limit of 100 W relative to a half-wave dipole. The channel centers are 1.5 kHz above those dial settings, which is why people mix them up. Verify against the current FCC rules before relying on my numbers. On VHF and UHF, the main national FM simplex calling frequencies in the ARRL plan are 52.525 MHz on 6 m, 146.520 on 2 m and 446.000 on 70 cm. 223.500 serves the same role on 1.25 m. Call there, then move to another simplex channel to talk. Weak-signal SSB and CW use separate areas of the band. On 6 m, 50.125 is the common SSB calling frequency, and 50.313 is the usual FT8 spot. On 2 m, 144.200 is the SSB calling frequency and 144.174 is where FT8 usually lives. On 70 cm, 432.100 is the weak-signal calling frequency. Repeater inputs and outputs, satellite segments and beacon sub-bands are carved out separately, so look at the band plan for your area rather than guessing. Local frequency coordinators set repeater pairs, so regional practice varies. 33 cm (902-928 MHz) is the tricky one. It is shared with Part 15 devices and other services, so noise can be severe and amateurs are secondary. There are weak-signal and narrowband areas near the bottom of the band, but check the current band plan for specifics. For 70 cm, note that operation in some areas near military radar installations is restricted, and 420-450 MHz usage can be limited by location. Internationally, the ITU divides the world into three regions, and allocations differ. A few examples: 40 m is 7.0-7.3 MHz in Region 2 (the Americas) but 7.0-7.2 in Regions 1 and 3. 80 m is 3.5-4.0 in Region 2 but narrower elsewhere, and 160 m starts at 1.810 in Region 1. 2 m is 144-148 in Region 2 but 144-146 in Regions 1 and 3. 70 cm is 420-450 in Region 2 but 430-440 in Region 1. 6 m isn't available everywhere. Individual countries layer their own rules on top, including mode limits and power. If you operate abroad under reciprocal privileges, such as under CEPT arrangements, follow the host country's allocations and rules, not the ones you're used to at home. Always check the specifics for the country before transmitting.
-
Getting real performance out of an SDR: dynamic range, noise floor and where the dongle ends and the antenna begins
On direct sampling versus an upconverter, it depends on the target. For listening to broadcast stations and strong signals, direct sampling on an RTL-SDR v3 is often good enough. The limits are the 8-bit ADC and the lack of selective filtering, so it struggles when strong stations sit next to the weak signal you want. An upconverter changes the signal path and lets the tuner's own gain control work, but you accept the converter's spurs and the need to set the offset correctly. If you go that way, check the display against a known station before trusting any frequency readout. If the aim is serious HF listening, receivers designed for HF are a more direct fix than working around an RTL-SDR. They have better dynamic range and sensible input filtering, which matters most when the antenna is a long wire exposed to strong signals. For VHF and UHF work, an RTL-SDR with a bandpass filter and LNA at the antenna remains a good low-cost setup. A HackRF or LimeSDR makes more sense when you need transmit, wide bandwidth or experimentation, not when you only need a better receiver. For digital decoding, also check the sample rate and CPU load. Dropped samples at high sample rates can mimic a weak signal, and the decoder gets blamed for something the USB link caused.
-
Planning a 24-hour EMCOMM field station: power budget, antenna and coax choices, grounding, and noise control
Good starting point. I'd split the power plan into three layers. First, a critical-load bus: the primary radios, a handheld charging path, and one light. Second, a convenience bus: laptop, chargers, extra lighting. Third, generator or mains-powered loads such as a heater or fan. When the battery gets low, you shed from the bottom up and the net still works. On the generator-as-charger idea, I'd add that inverter generators are most efficient at moderate load, so running one at a trickle load all night wastes fuel. A better pattern is to charge hard for a defined window, then shut down. Keep fuel storage, refueling, and placement as part of the checklist, including letting the unit cool before refueling and keeping exhaust away from tents. Follow the manufacturer's instructions on neutral-ground bonding, and don't improvise backfeed connections. If you power anything from an AC outlet, GFCI protection is a sensible baseline outdoors. On LiFePO4: the flat voltage curve is nice for rigs but makes voltage a poor fuel gauge. A battery monitor that counts amp-hours or tracks state of charge is much more useful than watching a voltmeter, and it makes the 'when do we start the generator' decision objective.
-
Newly licensed? Let's talk first radios, first contacts, and what you wish you'd known sooner
For anyone deciding what to buy first, here's a checklist that tends to hold up. Start with the kind of operating you actually want to do. If it's local conversation and club nets, a dual-band handheld or small mobile rig is plenty. If it's emergency communications or public service events, check what your local group expects, since some use specific frequencies or modes. If it's HF, budget for the antenna, coax, a way to ground and protect the setup, and possibly a tuner, not just the transceiver. Programming a radio is another thing to learn early. Free software such as CHIRP supports many radios and makes entering repeaters much easier than using the keypad, though you should always verify frequencies, offsets, and tones against a current repeater directory or club listing before relying on them. One mistake to avoid is buying the cheapest radio you can find and assuming the experience will be the same as a higher-end one. Inexpensive handhelds can work fine for learning, but receivers, filtering, and spurious emissions vary a lot. Read reviews, talk to local hams, and don't be afraid to ask what the repeaters in your area actually need.
-
Planning a first SOTA activation: kit, spotting, logging, and what actually counts for points
For a first activation, I'd pick a summit with modest height and an easy trail, even if it is only worth one or two points. The goal is to learn the process: planning, setup, spotting, logging, and walking out in daylight. A very tall summit can add a lot of stress when you are also learning new radio gear. On VHF, remember that FM on 2 m is line-of-sight dominated. A summit helps a lot, but your contact count still depends on who is monitoring. Posting an alert on SOTAwatch in advance can help chasers know when to look for you. A spot after you are on the air helps even more, as long as you give the frequency, mode and reference correctly. If you move to HF, try 40 m or 30 m first, depending on your license privileges and what your antenna is cut for. Always check your band plan and local rules. Also practice your setup at home. A wire antenna that takes five minutes in the garden can take twenty minutes in wind. Rehearsing the setup is cheap and saves your battery and your patience.
-
Reading band conditions: how much do SFI, A and K tell you compared with WSPR, beacons and spots?
I'd add two points on VOACAP and on the low bands. First, treat VOACAP as a planning chart. Run it for the month using a smoothed sunspot number, enter realistic antennas and power, and look at the hours where reliability is highest. Then compare with real-time data to see whether today is running above or below the median. If real data is consistently better or worse, that may be your antenna or local noise, not the ionosphere. Second, on 80 and 160, the A and K indices are probably more useful than SFI. SFI matters little for the lowest bands, where D-layer absorption, local noise and geomagnetic disturbance dominate. Quiet geomagnetic conditions and a good noise floor often decide whether a gray-line path is workable. For NVIS, the useful number is the F2 critical frequency from a nearby ionosonde, if one is available, since it tells you roughly which band to pick for regional work. Does anyone have a preferred source for that near-real-time foF2 data?
-
Hamfest game plan: what to bring, what to test, and how to get more out of the day than a bag of cables
On finding a club, I'd say visit more than once before deciding. A club's character shows up in what they do at meetings. Some are mostly programs and talks, some are heavy on build projects, and some are really about a net or emergency communications. At a hamfest, the club table is a good place to ask what a typical meeting looks like, whether they run Elmer sessions for new hams, and whether they do VE sessions or Field Day. If you're newly licensed, ask whether they have a mentoring program or a loaner station. A lot of clubs will happily help you get a first antenna up or sort out a rig menu, but they won't know you need that unless you say so. Also ask how they communicate. Some clubs mostly use a mailing list, others a group chat or a repeater net, and it helps to know where the announcements actually go.
-
How do you separate real ham radio news from hype? Sources, firmware, new rigs and band-opening reports
On band openings, the useful skill is knowing which tool answers which question. If you want to know whether 10 or 12 meters are open right now, don't rely on the solar flux number alone. A high SFI helps, but a disturbed geomagnetic field (high K index, a stormy A index) can wreck the path anyway. Check the beacons. The NCDXF/IARU network on 14.100, 18.110, 21.150, 24.930 and 28.200 MHz lets you listen for a few minutes and see which paths are alive. Then use PSK Reporter on the FT8 calling frequencies, such as 28.074 or 50.313 for 6 meters, to see whether stations near you are being heard, and where. For sporadic E on 6 meters and up, the spot maps often tell you more than any forecast, because those openings are short and localized. A forecast tells you the odds. Spots tell you what is happening. For club news and awards, I'd treat club newsletters and net announcements as the best source for local events, and the sponsoring organization's page as the authority on award rules. Programs such as DXCC, WAS and special event certificates have specific requirements, and those can change, so check the issuer's current rules before chasing one.
-
Radio mods worth doing, and the ones that cause trouble: a practical order of operations
Good list. I'd move audio higher on it, because a lot of 'my signal sounds bad' reports come from level problems rather than hardware. On FM, over-deviation from too much mic gain causes splatter and distortion, and an EQ or compressor can't fix it. On SSB and digital modes, the usual mistake is overdriving the audio input. If the ALC is moving on a digital mode, you're already distorting. Set the drive so the ALC barely registers and control output power with the rig's power setting. For receive audio, a small external speaker with some DSP filtering often does more than any internal mod, especially in a noisy mobile. Cutting low-frequency rumble and trimming high-frequency hiss improves intelligibility without touching the radio's insides. I'd also add that power upgrades are mostly wiring: heavy gauge cable, a fuse close to the battery, solid Powerpole connections, and checking the voltage at the radio during transmit rather than at the supply. Voltage sag under load can cause more trouble than the radio itself.
-
Keeping DXCC, WAS, WAZ, WPX, IOTA and the activity awards straight: where do your confirmations actually count?
One caution on mixing the programs: do not assume a confirmation that counts for one sponsor counts for another. DXCC, WAS and the other ARRL awards use the ARRL's own LoTW and application system. CQ awards such as WAZ and WPX have their own rules about what they accept, and IOTA, POTA and SOTA each have separate databases and requirements. Read each sponsor's current rules page before you apply, because accepted confirmation types, fees and endorsement categories can change. It also helps to separate chasing for credit from chasing for activity. Marathon and the park and summit programs reward steady operating over a defined period, so a weak-signal evening matters. DXCC, WAS and WAZ are cumulative and reward patience over years, so the work is in filling gaps: the last few states, the last few zones, a band you have neglected. For the Honor Roll and Challenge, start with an audit. Export your current confirmed entities, compare them against the present entity list, and mark which ones are only credited through deleted entities. Then you will know whether you are missing a few common entities or a handful of rare ones. That decides whether you are chasing DXpeditions or just working the bands more.
-
Starting Morse code from zero: Koch vs. Farnsworth, which tools to use, and how to stop translating in your head?
Koch and Farnsworth answer different questions, so you can combine them. The Koch method is about the order in which you learn characters. You start with just two characters sent at a fairly fast character speed, commonly around 20 wpm. When you copy them at roughly 90% accuracy, you add the next character. The point is that you never learn the code as slow dots and dashes you have to count. You learn each character as a single sound pattern, a rhythm, from day one. Farnsworth is about timing. Characters are sent at a faster speed, but the gaps between characters and words are stretched, so the overall speed is lower. You get time to recognize each character without hearing it dragged out. Many people use Farnsworth spacing early on and then shrink the gaps until the spacing is standard. On tools, they overlap more than they compete: LCWO is a browser-based Koch trainer. It has its own character order, tracks your results, and lets you set character speed and effective speed. It's a convenient daily-practice tool because there's nothing to install. G4FON's Koch trainer is a desktop program that does much the same job: generate random groups at a chosen speed, add characters gradually. If you prefer an offline program, it's a reasonable option. CW Academy is a different kind of resource. It's a structured course run by CWops with volunteer advisors and live sessions, so you get feedback and accountability instead of just software. Check the CWops site for how the levels work and when classes are offered. Many people use a trainer for daily drilling alongside a class. For flashcards: avoid anything that shows you dots and dashes. If you memorize "A = dit dah" visually, you build the translation habit you're worried about. Audio-only drilling is better. Listen to the character, and write down the letter or say it. The rest of this is general advice rather than a rule. Pick a tone you find comfortable (many people like somewhere in the 500-700 Hz range), keep sessions short and frequent rather than long and rare, and don't stop to puzzle over a character you missed. Let it go and catch the next one. Dwelling on one miss makes you lose the next three.
-
EME from 2 m to 10 GHz: what each band asks of the station, and how to plan the schedules
On polarization: there are two separate effects, and people tend to mix them up. Faraday rotation comes from the ionosphere and is strongest on 144 MHz. It becomes less significant on 432 MHz and is basically negligible from 1296 MHz upward. It can make a signal fade in and out over minutes. The other effect is geometric or spatial polarization offset. That depends on where the two stations are relative to each other and to the Moon, and it applies on every band. This is why stations often have a way to rotate their polarization, or to switch between horizontal and vertical, at least on 2 m. Libration fading is a different thing again. The Moon's apparent motion makes echoes arrive with a spread of Doppler shifts, so the signal flutters rather than fading slowly. The spread grows roughly in proportion to frequency, so it is small on 2 m and much wider at 10 GHz. This is the reason Q65 has multiple submodes and why a mode that works well on 2 m may do worse on microwave. For skeds, a few practical points: Agree on the band, mode, submode, start time, and which of you transmits in the first period. Check that you both have the Moon above the horizon for the whole window, not just at the start. Look at the degradation figure for that date, because perigee and apogee differ by about 2 dB and sky noise varies with where the Moon sits. Have a fallback frequency and a way to coordinate, such as a chat page used by EME stations like ON4KST. Finally, allow time for the first few cycles before judging the result. Don't give up because the first few minutes are silent.
-
Making SET and Field Day count: what to test, how to script it, and what to put in the after-action report
One thing I'd add to the 'treat Field Day as setup practice' point is to give people a role they don't usually fill. If your regular net control always runs the net, have someone else do it, with the regular as backup. The same goes for message handling: rotate who is the originator, who is the relay, and who is the delivery point. Real events rarely run with the people you'd have chosen, and a team that depends on one or two strong operators finds this out at the worst time. For scenario injects, I like those that create a decision rather than just more traffic. For example, 'the primary repeater is down, switch to simplex or a backup,' or 'two shelters report the same supply request, who consolidates?' Those test your communications plan and your judgment, not just typing speed.
-
SOTA basics for new activators and chasers: references, points, spotting, kits and safety
For chasers, the entry cost is lower than people think. You do not need a big station, just a way to watch SOTAwatch and a decent receive setup. Listen first. Activators often work stations in a rhythm, so wait for a gap and give your callsign clearly rather than shouting over a pile-up. Use phonetics if conditions are poor, and keep the exchange short: callsign, signal report, then wait for the activator to finish. If you are on a summit yourself, S2S calls are worth making, and activators usually give them priority. On the awards, Shack Sloth is for chasers just as Mountain Goat is for activators, and both depend on accurate logs. Keep clean records so any later claim or correction is straightforward.
-
How do you decide if a band is really open: SFI/K-index, or WSPR and beacons first?
I treat the indices as a weather forecast and the spots as the radar. The indices tell you whether it's worth switching the rig on. WSPR, the beacons and PSK Reporter tell you what's actually happening right now. For a quick check on a DX band, listen to the NCDXF beacons. If you can hear the 100 W beacon from a region but not the 10 W one, the path is marginal. If the 1 W and 100 mW slots come through, the band is wide open. Each beacon transmits for 10 seconds on each frequency, so you can sweep all five bands in a few minutes. WSPR is great because it removes the human factor. A station running a watt or less into a modest antenna, heard at 10,000 km, tells you far more than a spot of someone running a kilowatt. Just remember that spots reflect where the stations and receivers are, not where the propagation could be. No spots doesn't prove a band is closed. There might simply be nobody listening in that direction. VOACAP is best used for planning. It's good for finding which band to try at which hour, and it uses a smoothed sunspot number, so it won't capture a short-lived Es opening or a sudden flare. If the prediction says a path is 10% reliable and WSPR shows it open, the live data wins for tonight.