Everything posted by Admin_Terry
-
Field comms power and antenna planning: where do 24-hour deployments usually fall apart?
One addition on power distribution: build it so a single failure doesn't take down the whole station. A common layout is a main fused feed from the battery to a distribution block, then separately fused branches for each radio, one for the computer and accessories, and one for lighting. That way a shorted light fixture can't drop your HF rig. Label each branch with its fuse rating and what's connected, because during a busy deployment nobody wants to trace wires. Also check the BMS limits on the LiFePO4 battery. Some drop out on over-current or low voltage with no warning, and a transmit surge into a marginal cable can trigger that. If your main battery has a continuous discharge limit, compare it against the worst case of all connected loads, not just the radio. A multimeter and a clamp meter are worth carrying so you can see real current rather than guessing.
-
Planning a first SOTA activation: summit refs, points, kit choices, VHF vs HF, and logging
On logging, I'd keep the field log boring and the cleanup log careful. On the summit, write down UTC time, callsign, band, mode, and any summit ref the other station gives you. Don't try to do everything in a logging app with gloves on. At home, enter it into whatever program you use and then export it for the SOTA database. Check that your own summit ref, the date, and the callsign you used are correct before submitting, as errors are easy to make and annoying to fix. For chasers, it helps to remember that you can also log summit-to-summit contacts when you are the one on a summit. Also, a quick spot check on SOTAwatch before you call helps avoid pileup confusion, especially when an activator has moved band or mode. If someone is chasing toward the Shack Sloth, it is mostly a matter of keeping a clean record over time, and the same is true for the Mountain Goat on the activator side.
-
Band plans vs. FCC rules: how to find where you can legally operate, and where you should, from 160 m to 33 cm
For VHF and UHF, the band plan matters more than the license class, because the whole band is shared and the plan is the only thing separating weak-signal work from repeaters. The rough rule is that weak-signal CW and SSB live at the bottom of each band, FM and repeaters are higher up, and simplex calling frequencies are fixed spots where you make contact and then move. On 6 m (50 to 54 MHz) the bottom 100 kHz or so is CW and beacons, with SSB and CW DX above that. The SSB calling frequency is 50.125 MHz, and FT8 is normally on 50.313. FM simplex calling is 52.525 MHz, with repeaters in the upper portion of the band. On 2 m (144 to 148 MHz) the weak-signal area is at the bottom, with 144.200 MHz as the SSB calling frequency. The national FM simplex calling frequency is 146.520, and standard repeater offsets are 600 kHz, with repeater outputs generally in the 146.6 to 147.4 range. APRS in North America is on 144.390. On 70 cm (420 to 450 MHz) the national FM simplex calling frequency is 446.000. The weak-signal SSB calling frequency is 432.100 MHz. Repeaters are usually 5 MHz apart, around 442 to 445 and 447 to 450, depending on local coordination. On 10 m there is also an FM simplex calling frequency at 29.600 MHz. For 33 cm (902 to 928 MHz) the allocation is secondary and shared with ISM and unlicensed devices, so noise can be a problem. Weak-signal activity is concentrated near the bottom, and FM and repeater use varies by region. The band is also only available in ITU Region 2, so it's not a worldwide band. I'd check the current ARRL band plan and your local frequency coordinator for this one rather than rely on remembered numbers. The same applies to repeater offsets and input and output pairs everywhere else on VHF and UHF. Local coordination bodies decide what's actually in use, and they sometimes differ from the national plan. A calling frequency is only for making contact. Call, get an answer, then agree on another simplex frequency and move, so the calling channel stays free for others. On international allocations, ITU divides the world into three regions, and the US is in Region 2. National regulators then decide how to implement each region's allocation. Examples: 40 m is 7.000 to 7.300 MHz in Region 2 but only 7.000 to 7.200 in Regions 1 and 3. 80 m is 3.500 to 4.000 in Region 2, but narrower in Region 1 and Region 3. 2 m is 144 to 148 MHz in Regions 2 and 3 but only 144 to 146 MHz in Region 1. The 70 cm band is 430 to 440 in Region 1. The 60 m band varies widely by country, and some countries have no access or use a different layout from the US channels. When you work DX, a station may be in a segment that you can't legally use, so always check your own privileges, not theirs. If you travel and operate abroad, check whether the country has a reciprocal operating agreement or CEPT arrangement with the US, and follow that country's rules, which include its band edges and power limits.
-
Newly licensed? Let's swap first-radio advice, first-QSO stories and "wish I'd known" mistakes
For a first radio, I'd say don't spend much until you know what kind of operating appeals to you. A basic dual-band handheld is enough for local repeaters, simplex and nets. The biggest practical hurdle is programming. Many budget handhelds are easy to program with free software like CHIRP and a correct cable, but the manual menus can be painful. Get the frequency, offset direction, and CTCSS/PL tone right for each repeater. If you can hear a repeater but nobody hears you, the usual causes are a missing tone, the wrong offset, or being too far from the machine for a handheld's power. Before your first transmission, listen for a while. Learn how people identify, how nets run, and whether the repeater is busy. Then say your callsign and that you're listening or checking in. You don't need a speech. One upgrade that's often worth more than a fancier radio is a better antenna, such as a decent magnetic-mount or outdoor antenna in place of the stock rubber duck. Also keep in mind that cheap radios can be fine for learning, but spurious emissions and poor receiver selectivity are real downsides in busy RF environments. Check reviews and compare before buying.
-
Choosing a handheld: budget FM, D-STAR, DMR, or something like the IC-705? Features, batteries, antennas and CHIRP tips
I'd split it into two questions: which mode, and how much control do you want over the radio. If the answer is local nets, simplex and basic repeaters, analog FM is enough, and a radio like the FT-65R is easy to understand. Spend the savings on a spare battery, a better antenna and a programming cable. If you go with CHIRP, do things in this order. First download the existing configuration from the radio and save that image before changing anything. Then import your local repeaters from a source such as RepeaterBook, and check each entry by hand. Pay attention to offset direction, tone mode and tone frequency, because a repeater with the right frequency but the wrong tone can sound dead. Also confirm in CHIRP's supported-models list that your exact model and cable are covered, since not every radio works with it. DMR radios usually need the vendor's customer programming software instead.
-
Getting from 5 to 20 WPM: what actually moves the needle, and how do you get past the plateaus?
On schedule: the usual advice, which matches how skill learning works generally, is that frequent short sessions beat occasional long ones. Fifteen to thirty focused minutes a day, ideally split from other sessions, is easier to keep up than a two-hour block on Sunday. Fatigue also matters. When your copy starts falling apart halfway through a session, extra minutes after that point mostly practice mistakes. For plateaus, one common approach is to work slightly above your comfortable speed. If you copy 100 percent at 15 WPM, spend part of the session at 18 or 20, accepting that you'll miss characters. Don't chase the missed character. If you stop to puzzle over it, you lose the next three. Let it go and stay with the stream. Then drop back to your comfortable speed and it will feel easier. Some people also alternate between a character-speed push and a spacing push, so they aren't always raising the same variable. On head copy, it helps to stop writing before you feel ready. A practical way is to copy only every few words on paper, then fewer, and eventually just listen and keep a sentence in your head. The first stage of that will feel worse, and that's normal. Your brain is trading letter-by-letter certainty for word-level recognition. As for decoding by software: decoders can be handy for confirming a callsign you weren't sure of, but they are unreliable when there is fading, static crashes, hand-sent timing that drifts, or two signals close together. Relying on one for training also gets in the way of building your own ear. A reasonable use is to copy by ear first, then check against the decoder afterward, not the reverse.
-
Technician to General: how should I structure study for Element 3 and what changes on HF?
On the vanity question, there's no real reason to wait or to rush. Vanity applications are separate from the exam, so it's mostly a matter of preference. One thing to understand first is that the call sign groups you can request depend on your operator class, so a new General may have more choices than a Technician. Check the current FCC fee and the list of available calls before deciding, and make sure you can handle your preferred call's phonetics and CW rhythm if you plan to use it on the air a lot. For the study plan, here is one way to spread the work over about five weeks: Week 1: Band plan and privileges. Make flash cards or a hand-drawn chart of each HF band's CW/data and phone sub-bands. Add the power limits and the special cases (30 m, 60 m). Week 2: Propagation. Learn the layers, why D-layer absorption matters on lower bands in daytime, what MUF and critical frequency mean, why 10 and 15 meters open and close with the solar cycle, and how solar flux, A-index and K-index relate to band conditions. Grayline and skip zone questions are common. Week 3: Antennas and feed lines. Know dipole length from the 468/f formula, the typical feed-point impedance of a half-wave dipole versus a quarter-wave vertical, what SWR does and doesn't tell you, coax loss versus frequency, and how baluns and traps work. Sketch each antenna type and its radiation pattern instead of just reading the answer. Week 4: Electrical principles and digital modes. Work through Ohm's law and power problems by hand until they are automatic. For digital, understand what separates modes like FT8, PSK31 and RTTY: bandwidth, weak-signal capability, how they are timed, and the role of the sound card and rig interface. Week 5: Timed practice exams. Take full 35-question sets, review every miss by reading the explanation, and aim to score comfortably above 26 for a few sessions in a row before booking. Questions you answer correctly by guessing should count as misses in your review. The biggest trap is memorizing answer letters from one site's practice test. Shuffle questions and use more than one source, since the exam presents the same questions with the answers in different order.
-
Stuck at 10-12 wpm on the way to 20: what actually breaks the plateau?
On the keyer side, two things are worth checking before you blame yourself. First, make sure your sending speed isn't well above your receiving speed. It is tempting to set the keyer fast because it feels good, but sloppy 20 wpm sending sounds worse than clean 14 wpm. Second, adjust spacing, not only speed: a slightly longer inter-character gap makes your own fist easier to copy and easier for others to read. For paddle setup, start with a light touch and a small contact gap, then loosen only if you get accidental double dits. If you're unsure whether you want mode A or B, try both for a week each. Mode B adds an extra element when you release the squeeze at the wrong moment, which trips some people up and suits others fine. Neither is better in the abstract. For nets and contests, listening before you transmit is underrated. Copy a few exchanges from a contest at your comfortable speed before calling anyone. Many contests also have a slow-speed or low-power class, and a few CW clubs run short, informal timed events aimed at newer operators. Check the current rules and schedules directly from the organizer, since formats and dates change.
-
Rig dead, no TX or no RX, or stuck in protection: what is your order of checks before you touch alignment?
For me the PLL check comes early whenever a synthesised rig is silent on both receive and transmit. If the first local oscillator is not locked, nothing else will behave, and you can waste an hour in the IF while the actual fault is a VCO or reference problem. A counter or scope on the reference oscillator, plus a look at the VCO control voltage, settles it quickly. If I had to choose a single instrument, it would be the bench supply with a current limit, followed by the dummy load and wattmeter. A supply that shows you the current as the rig powers up tells you a lot before you pick up any other tool. A big jump to the limit points to a short. A tiny draw means the rig is not powering up properly. A draw that creeps up points toward a failing part getting hot. A scope is great, but it is easy to misread. A long ground clip on a 10x probe will make a clean oscillator look messy. Keep the ground short, know whether you are AC or DC coupled, and compare against the service manual waveforms where they are given.
-
Cheap SDR vs. dynamic range: how to tell overload from a weak signal (RTL-SDR, HackRF, SDRplay, Airspy)
Worth separating two different goals, because the right kit differs. If you want to listen across a wide span and see what is out there, a wideband receiver with a big waterfall is fine, and the 8-bit limits only bite when something strong is close. If you want to work weak signals next to strong ones on HF, then preselection and a good front end matter more than the sample rate or the number of bits. On software: SDR# and HDSDR are Windows-oriented, GQRX is mainly Linux and macOS, CubicSDR is cross-platform, and SDRuno is built for SDRplay hardware only. Which one is best is mostly down to which hardware you have and which plugins or decoders you need. HDSDR is popular for HF with ExtIO support and CAT control. GQRX is a nice quick tool for VHF/UHF on Linux, and it plays well with command-line decoders. It is also easy to try more than one on the same hardware, which tells you quickly whether a problem is in the radio or the software. On noise: it is worth keeping a note of the noise floor with the antenna connected and disconnected, at a few frequencies. A before-and-after record makes it easy to see whether a ferrite, a different power supply or a new antenna position really helped, rather than relying on how it seems by ear.
-
One log, many tools: keeping N1MM+, WSJT-X, Log4OM and the LoTW/QRZ/Club Log uploads from fighting each other
I'd add that time is the quiet dependency across the whole chain. FT8 and FT4 decoding depend on an accurate PC clock, and LoTW matching depends on QSO times being close enough between both logs. So whatever sync method you use, confirm it is actually running before a contest. A clock that has drifted can make a perfectly good log mismatch on the other end. For the post-contest flow, I'd do it in this order. First, generate Cabrillo and submit it, since that has a deadline. Second, export ADIF from the contest program and look at it in a text editor or a viewer before importing. Check mode, submode, the exchange fields and the station fields. Third, import into the permanent log and run its own duplicate detection on the import. Only after that, upload to LoTW, QRZ and Club Log, so a bad import does not propagate to three services you then have to clean up. For multi-operator or club events, also decide up front which callsign goes in STATION_CALLSIGN and which goes in OPERATOR. That affects how the QSOs look in Club Log and LoTW, and it is much harder to fix after the upload.
-
Getting from licensed to useful: ARES, RACES, SKYWARN, CERT and what activation actually asks of you
On the question of what new members get wrong, I would say it is usually scope. Radio operators are there to move information, not to make decisions for the agency they serve. If a hospital, shelter or EOC asks for a message to be sent, send it accurately as written. Do not edit it for clarity, and do not add your own interpretation of what you think they meant. If something is unclear, ask them to restate it. A related point is discipline on the net. Listen before you transmit, wait to be called, and give your call sign and location when asked. When you check in, include only what net control needs: call sign, location, availability and any equipment limits. It is tempting to talk through your whole setup, but during a busy net that costs everyone airtime. For the SKYWARN side, the same principle applies. Report what you actually observed, where and when, using the reporting criteria your local NWS office gives in training. Fewer, accurate reports are more valuable than speculation.
-
How do you separate real ham radio news from hype? Gear launches, firmware, FCC items and band-opening reports
On gear news, I'd add a checklist for anything announced at a convention or in a first-look video. Is there a manual to download? Is a shipping date stated by the manufacturer? Are there independent measurements, such as ARRL Lab results or other test data, rather than only the maker's spec sheet? Early reviews often cover ergonomics and features but not receiver performance under strong-signal conditions. Convention coverage is useful for hands-on impressions and for seeing new antennas, accessories and club or vendor booths. But a demo unit may be a prototype, and prices, features and firmware can change before release. If the vendor says a feature is coming in a later update, I'd count it as unavailable until it is in the release notes. For regulatory items, a good habit is to keep the original document link in your club's newsletter or chat when you share news. That lets others read the actual text, and it keeps the discussion from drifting into rumor.
-
Technician to General: how should I split study time across the 35 Element 3 questions?
I'd add a few things on antennas, digital modes, and the upgrade logistics, since those are the areas people tend to under-prepare for. Antennas: know the half-wave dipole length formula, about 468 divided by the frequency in MHz gives the length in feet, and be able to reason about what happens when you change frequency. Know the basics of feed lines (coax loss rises with frequency), what SWR tells you and doesn't tell you, why a balun or choke matters on a dipole, and how a quarter-wave vertical depends on its radials or ground system. Understand traps and loading at a conceptual level. The questions are mostly conceptual, but they do expect you to pick the right relationship. Digital modes: expect questions about RTTY, PSK31, packet, and general sound card interface practice. Know the basics of why you keep audio levels low to avoid ALC action and a distorted signal, why you stay in the digital portion of the band, and what common modes are best suited for. Be careful about treating any one dial frequency as a rule. Calling frequencies for modes like FT8 are conventions, not regulations, and the band plan portions you operate in are what the exam cares about. Operating practices: this is where the rules and common sense overlap. Review control operator responsibilities, station identification, third-party traffic basics, and courteous practices like listening before calling, using split operation properly in a pileup, and not calling CQ on top of an existing QSO. These are often the easiest points if you read the explanations rather than just memorizing the answer letters. Upgrade logistics: your call sign stays the same when you upgrade. A vanity call sign is optional, and the available groups depend on your operator class. As I understand it, Technician and General can request many of the same formats, but check the FCC's current rules and fees before assuming it is worth doing. Also ask your VE team what proof you will receive after passing and whether any temporary identification requirements apply while the FCC database updates. As for scheduling, one reasonable approach for a few weeks is to take a practice exam first to find your weak subelements. Then spend most of your time there while doing short daily review of the sub-band chart. Finish with two or three full-length timed practice exams, and don't take the real one until you're consistently scoring well above 26 out of 35.
-
Planning a 100 W HF shack: signal chain order, power, and grounding vs. bonding
One distinction to keep clear is that a ground rod doesn't make a shack safer from lightning on its own. What matters is bonding. The rods at the antenna entry, the mains ground and the shack bus should all be tied together, so that a surge raises everything to a similar potential, not just one cable. A bus bar at the entry panel with surge protectors on the coax lines is the usual way to do it. Disconnecting antennas during storms is still the only dependable protection. For noise and RF in the shack, think common-mode current first. If you get hum, RF feedback on audio, or a USB CAT link that drops when you transmit, put a choke on the coax at the feed point and at the radio, and ferrites on the USB and audio leads. A short bonding strap between chassis helps but won't fix a feedline that's radiating. For the noise-floor question, compare the S-meter or a noise reading on a quiet band with the supply on and then unplugged from the mains (running from a battery), so you can see what the supply is adding.
-
Planning a dual-band mobile install: FTM-500D vs ID-5100A vs TM-D710G, wiring, noise and etiquette
I'd rank them by local repeater activity first, then by control layout. A radio that can't access the repeaters people actually use in your area is a poor fit, however good the specs look. Check which modes your local repeaters run and whether they need CTCSS tones, a DCS code, or a digital access setting. Then think about how you'll actually operate the radio. Touchscreens can be convenient when parked but harder to use at a glance while driving, so physical knobs and buttons matter more than they seem to on a spec sheet. For the install checklist, I'd add one item: before you drill anything, temporarily lay out the head, mic and cables inside the cabin and check that nothing interferes with the steering, pedals, seat travel, or airbag deployment. It's much easier to move things at that stage.
-
Starting Morse code from zero: Koch vs. Farnsworth, which trainers to use, and how do you get past the plateaus?
The most useful thing to know is that every method that works is trying to get you to hear a character as a single sound, like a word, and not as a count of dits and dahs. If you hear "dit dah dit dit" and translate it, you'll top out at a low speed. If you hear the rhythm of L, you can keep going. That's why the chart-first approach has a bad reputation. A chart isn't harmful in itself, but it invites you to think of the code visually, and that habit is hard to shake. Learn by ear from the first session. Koch and Farnsworth both address this, in different ways. In the Koch method you send the characters at a real speed from the start. The usual figure is around 20 wpm character speed, and some people go a bit lower. You begin with just two characters, copy until you're about 90% accurate, then add a third, and so on. Speed never has to catch up later, because it's already there. The only thing that grows is the character set. Farnsworth keeps the characters at a fast speed and stretches the spacing between characters and words. Overall speed might be 10 wpm while each letter sounds like 18 or 20. Many courses use this idea, and you can combine it with Koch: the Koch trainers let you set a character speed and an effective speed, so you can start with generous spacing and tighten it as you improve. For tools, LCWO.net is free in a browser and built around Koch lessons. It also has callsign and text-copy exercises, so you can use it for months. G4FON's Koch trainer is a downloadable program for the same method, with some differences in character order and settings. The character orders in the different trainers aren't identical, but this doesn't matter. Pick one tool and stay with it for the first lessons so you aren't resetting your progress. On the 90% rule: it can feel slow around the middle of the set, where similar-sounding characters show up together. That's normal, and it's useful. The characters you keep mixing up are the ones you most need to hear more of. Short sessions of 15 to 30 minutes, once or twice a day, usually beat one long session because the learning seems to consolidate between sessions. Two practical settings: use a sidetone pitch you find comfortable (many people settle somewhere in the 500 to 700 Hz range), and don't write down dits and dahs. Write the letter you heard, and if you miss one, let it go and catch the next one instead of dwelling on it. Dwelling on a missed character makes you miss the next two.
-
Confirming contacts: how do you split your QSL workflow between LoTW, eQSL, Club Log OQRS and paper?
A useful split is by goal. If a contact is meant to count for DXCC or WAS, LoTW should come first, because it is the one with the least friction and no postage or waiting on mail. Upload regularly, and don't wait for a big batch, since mismatched times or modes are easier to fix while the details are fresh. Check your logging software's export too: if it writes the wrong mode (for example FT8 labelled as plain DATA, or the reverse), TQSL may not match it the way you expect. Paper cards fit contacts where you want the card itself, or where the other station doesn't use LoTW. Before you spend on postage, check the station's QRZ page, its website or Club Log for how it prefers to be contacted. A few minutes of reading often tells you whether bureau, direct or OQRS is the right route. If you ask for direct and the station says LoTW only, you can save yourself and them a stamp.
-
Radio mods that are worth doing, and where the legal line sits (MARS/CAP, expanded RX, TCXO, filters, power, noise)
I'd stress the power and noise side, because they interact. A radio with sagging supply voltage can show distorted audio, reduced power or odd digital-mode behavior, and a cheap switching supply can raise the noise floor enough to wipe out what a filter upgrade gained. Check the wiring from the supply to the radio before blaming the radio: gauge, crimps, fuse holders and connector contact resistance all count. For fans, consider whether you actually need one. If you're running data modes at full power on a radio rated for intermittent duty, turning down the power is the first thing to try. If you still need a fan, mount it so it pushes air across the fins instead of recirculating hot air, and watch for noise from the fan's own motor or controller. For firmware and mods in general, make the change reversible whenever you can. Save the config, photograph the board before disassembly, change one thing at a time, and test after each step. That makes troubleshooting much simpler.
-
When do you leave a good run frequency to chase multipliers? Rate vs. mults, band changes and SO2R
A rate threshold works for me as a framework, but I'd tie it to the mult value rather than a fixed number. If the new multiplier is worth, say, 1% of your score and your rate is high enough that two minutes away costs less than 1%, go get it. If the mult is a per-band one and you have few on that band, the threshold shifts further in favor of leaving. The point is to compare the cost and the payoff instead of using a feeling. On SO2R, the biggest practical gain I'd point to is not hardware but discipline: decide ahead of time what radio 2 is for. If it is only for mult hunting, don't let it turn into a second run. The moment you start calling CQ on both radios, you are probably making each one worse unless you have the experience and the ergonomics for true two-run operation. Keep radio 2 in S&P mode, log the contact quickly, and return to radio 1. One more detail about skimmer spots: set filters so you only see spots that multiple skimmers have confirmed, if your software allows it. It cuts down the clutter and reduces the number of busted-call spots that waste your time.
-
Starting EME: what really limits 2 m, 70 cm, 23 cm and 10 GHz moonbounce stations?
For 2 m and 70 cm, the usual argument is that the receive side is where small stations lose most. Every tenth of a dB between antenna and preamp is noise added directly to a signal that may already be around the decoding threshold. That is why mast- or feed-point LNAs, low-loss sequenced relays and short runs of good coax or hardline matter so much. Put the preamp where it sees the antenna with as little loss in front of it as practical, and make sure the TX/RX sequencer cannot hot-switch the relays. A bad switch-over can destroy a very expensive preamp. On the antenna side, there is no magic number. A single long Yagi can sometimes hear and work the biggest stations, but you depend on their capability. More gain widens the pool of stations you can work. Four long Yagis of similar design are a common step up. Stacking and bay spacing should be chosen to match the Yagi's pattern, and the array needs to be steerable in both azimuth and elevation. If the array is fixed on the horizon, you get only a moonrise or moonset window. Polarization is where 2 m differs most from higher bands. Faraday rotation in the ionosphere can rotate the received polarization sense, so a fixed horizontal Yagi array can see deep fades for a while and then good signal. The rotation scales about 1/f², so it's roughly nine times smaller at 432 MHz and about 80 times smaller at 1296 MHz. Two approaches are common. One is a switchable or phased cross-polarized array, either with relays or with a dual-polarization receive system. The other is simply to accept the fades and plan skeds with that in mind, perhaps using longer sequences to get the necessary information through. WSJT-X's dual-polarization sibling MAP65 is built to exploit dual polarization on receive. Separately from Faraday rotation, there is a purely geometric (spatial) polarization offset between two stations at different locations. It's visible in the software's polarization readout and can be corrected by rotating the feed or antenna. For sked planning, look at three things: the window where both stations have the moon above a usable elevation, the declination (high declination gives longer windows in the northern hemisphere), and the sky temperature at the moon's position. On 2 m, the moon near the galactic centre can cost a lot of sensitivity even with identical hardware. On the other end of the cost scale, moon-free periods around the new moon are usually unusable because the moon is in the sun-side sky, and the sun's noise adds up. Agree on a mode, sub-mode, frequency, who transmits first, and who calls whom. Many failures are simple confusion over those details.
-
Building a ham go-kit in tiers: what goes in the pocket, the grab-and-go bag, the car and the home station?
The tier split makes sense. One addition for the grab-and-go bag: set up a "cold start" test. Pack it as if you'll leave, then unpack it on the back porch or at a park and try to make a contact with only what's in the bag. That quickly exposes missing adapters, dead batteries, and an antenna you can't actually deploy one-handed. Do it on a schedule, maybe when you change the clocks, and replace anything that has aged. On frequencies, I'd be careful not to rely only on repeaters. Put several simplex channels and a few of your local repeaters with their offsets and tones in the radio, and put the same list on paper. If your group uses a specific net or tactical frequencies, confirm them with the net control or emergency coordinator so you aren't relying on a forum post. A radio with a dead screen and no paper backup is a good lesson to avoid.
-
Building a wire antenna from scratch: where do you spend effort first, and what do you verify before trusting the SWR?
One thing worth adding about traps and verticals: both can look fine on an analyzer and still underperform, so it's worth thinking about efficiency separately from match. On a vertical, the radial field is where most of the loss lives. A short ground-mounted vertical with few radials can show a perfectly usable SWR while turning a lot of power into heat in the soil. On a trap dipole, trap Q and the wire between traps affect both bandwidth and loss. A model that includes realistic loading or loss values will show the difference between an antenna that is merely matched and one that radiates well. For modeling, it helps to run the same antenna in both EZNEC and MMANA and see where they disagree. If the two programs disagree wildly, it usually points to a segmentation problem or ground model issue rather than a real effect. Also try varying height and ground conductivity a bit to see how sensitive the design is. If a small change in assumed ground wrecks the result, the real antenna may be fragile too.
-
From FM birds to linear transponders: building a Doppler and tracking workflow that actually works
For the antenna question, I'd treat the Arrow or another handheld Yagi as a very good learning tool for FM satellites, and then decide what you actually want next. If it is linear work with a fixed station, a pair of small Yagis, one for 2 m and one for 70 cm, with az/el rotators is the more comfortable option. You get repeatable pointing, and you can watch the pass on the screen rather than keeping the antenna aimed by hand. Don't overlook the cabling and preamp. On 70 cm, a long run of poor coax can cost you more than you gain from a bigger antenna. If you add a mast-mounted preamp, make sure the sequencing is correct for transmit so you don't damage it. Polarization is worth thinking about too. Linear polarization is simple, but fading as the satellite rotates is common, and circular antennas smooth it out at the cost of a little gain. For grid squares, I'd log both your own locator and the other station's, and confirm the format for any awards you plan to chase. Some programs require six characters and some accept four.
-
Matching the digital mode to the path: decode thresholds, time sync, CAT and audio setup
For the Winlink side: Winlink is the messaging system, not a mode. Winlink Express can use VARA HF, VARA FM, ARDOP, Pactor and packet. VARA is proprietary, and the free version is speed-limited. ARDOP is the open option, although performance differs between the two. The usual ARDOP and VARA problems are audio level and PTT timing. Before transmitting into a gateway, make sure the modem's drive level is set so the rig isn't compressing or hitting ALC. On fldigi: PSK31 and RTTY are easy to set up, but poor tuning is very visible. Click the signal on the waterfall and use AFC cautiously, since on a crowded band it can chase the wrong signal. Olivia and the MFSK modes are slower but tolerant of fading. Hellschreiber is different again, because you read the text visually off the screen. It is not a good match for the weak-signal digital modes. For the sound card, make sure Windows isn't resampling or applying enhancements. Also keep fldigi and WSJT-X from opening the same audio device at the same time, as one will usually block the other.