Everything posted by Mod_Dan
-
NATO/ITU phonetics vs. "ham phonetics" on the air: what works for callsigns, names, numbers and nets?
On difficult conditions, think about what the listener is missing. Noise and fading remove pieces of a word, so the aim is to give the receiver more distinct pieces to latch onto. Speak at a measured pace with clear breaks between letters, and avoid raising your pitch or shouting, which often distorts audio and doesn't help copy. Give the callsign once clearly in standard phonetics, then repeat it once. If the other station gets only part of it, they can ask for the missing portion, such as "say again the last two letters." Standard words matter more here than anywhere else, because the listener is relying on familiar patterns to fill gaps. Common letter confusions are B, D, E, G, P, T, V and Z, and M and N. Phonetics resolve most of these. For example, "Delta" and "Bravo" differ in both rhythm and vowels, while "Golf" and "Gulf" are unlikely to be misheard if you use the standard word consistently. Avoid adding extra chatter around the callsign when conditions are marginal, since extra words can bury the information that matters. For names, give the name normally first and spell it only if the other operator didn't catch it, or if it is unusual. For example, "Name is Siobhan, spelled Sierra India Oscar Bravo Hotel Alfa November." For places, spell the unusual part, not the whole sentence. Grid locators are well suited to phonetics because they mix letters and digits: FN31 is "Foxtrot November three one," and a six-character grid adds the lowercase subsquare letters in phonetics too. On numbers, the ICAO form is zero, one, two, tree, fower, fife, six, seven, eight, niner. Most amateur voice operators don't use the exaggerated pronunciations ("tree," "fife") in casual contact, but "niner" is widely used to keep nine from being confused with "five" or with the German "nein." Use whichever version is clearest to the person you are talking to, and slow down on digits rather than changing the words. Prosigns such as AR, SK and BT are CW procedural signals, not voice words. On phone, the equivalents are plain procedural words like "over," "clear," or a short pause. One common mistake is saying "over and out," which is contradictory, because "over" invites a reply and "out" ends the contact. On nets and emergency traffic, the priorities are discipline and accuracy. Net control directs who speaks, so check in with your callsign in standard phonetics when asked. Keep transmissions short. For traffic that matters, such as names, addresses, quantities or medical details, read the information slowly, use phonetics for ambiguous letters, and ask the receiving station to read it back. Use "say again" rather than "repeat." Reserve urgent signaling like "break" or "emergency" for actual need, and follow your net's or served agency's procedure. Real distress and urgency calls on voice (Mayday, Pan-pan) have defined meanings in international procedures, so don't use them casually.
-
APRS on 144.390: sorting out paths, iGates, Mic-E and SmartBeaconing across a handheld, Direwolf and aprs.fi
On SmartBeaconing, the logic is easier to tune once you see what each parameter does. The beacon rate scales between a slow rate when you are below the slow speed and a fast rate when you are above the fast speed. In between it interpolates. Separately, corner pegging sends an extra beacon when your heading changes by more than a threshold that depends on speed, with a minimum time between turn-triggered beacons so you don't spam during a roundabout or a winding road. The usual mistake is a fast rate that is too fast. Beaconing every 60 seconds on a highway gives a decent breadcrumb trail. Going much shorter mostly adds collisions on 144.390 without making the map noticeably better. Also set the slow rate to something long, like 20 to 30 minutes, so a parked vehicle is not chattering away all day. The other thing to check is the path, not just the timing. If the handheld sends WIDE1-1,WIDE2-1 and you are already in range of a wide-area digi, the extra hop only adds duplicate traffic. Many people use the same path everywhere and that is fine for a mobile, but be conservative at home. For a fixed station with decent coverage, a single WIDE2-1, or nothing, is usually plenty. On the TH-D74/D75 and the FT5D, use the radio's own SmartBeaconing menu. The names and ranges differ between brands, so copy the logic, not just the numbers. One caution: a radio in the car with the GPS on a dashboard may report poor course and speed at low speeds. If you see the position jittering while stopped, a longer slow rate and a higher slow-speed threshold help.
-
One station, several loggers: how do you keep N1MM+, WSJT-X, Log4OM and the LoTW/QRZ/Club Log uploads from becoming a mess?
The single-owner rule is the part that matters most. I'd extend it to anything that touches the rig: the logger, the digital program, the rotator controller, and even the tool that does band-map spotting. Draw it on paper. Rig, CAT port, who owns it, who talks to it through a server. Most "it worked last week" problems are two programs fighting over one port after an update or a USB re-enumeration changed the COM number. On the dupe side, I'd keep your contest logger and master log philosophies separate. In N1MM+ a dupe is defined by the contest rules: per band, per band and mode, or once ever, depending on the contest. In a general log, the same callsign on the same band and mode on the same day is a different question. So don't import contest QSOs into the master log and expect its dupe check to behave the same way. Import them with the contest ID kept, so you can filter them later. One more thing on ADIF: always do a small test import first, maybe 20 QSOs, and look at what landed in the fields. Compare frequency, band, mode/submode, RST, grid and the exchange fields against the original. It takes five minutes and saves a mass cleanup.
-
Splitting shack automation between a Pi, a Pico and an ESP32: where should CAT, relays and rotator control live?
I'd add that RF immunity is mostly layout and cabling, not which microcontroller you picked. Common failure patterns are: RF on the USB cable, RF on the sensor wiring, or RF on a long relay-control line, any of which can end up as a detected signal inside a chip. So treat every cable leaving an enclosure as an antenna. Practical measures: a metal or at least shielded enclosure; a ferrite choke or a few turns through a suitable core on USB and power leads; a small capacitor to ground (for example 100 pF to 10 nF depending on band and signal speed) plus a series resistor on analog and slow digital lines; and a good common-mode choke on the feedline, so you aren't pushing RF current onto the shack wiring in the first place. For low-speed sensor lines, a series resistor and a bypass cap are cheap, but on I²C they limit speed and rise time, so check the bus still works. For the rotator, putting the control loop on the Pico is reasonable. With a pot-based feedback, filter the voltage, take several samples and median or average them, and add a deadband so the motor isn't hunting around the target. If your rotator controller speaks the common Yaesu GS-232-style serial commands, you can expose that interface and let rotctld or logging software drive it without custom software. If you later add an Si5351 or an SWR meter, keep the Si5351's square-wave outputs well away from the receive chain and filter them, since a square wave has lots of harmonics. For an SWR meter with a log detector like an AD8307, calibrate against a known dummy load and watch that your ADC sampling catches peaks under SSB or CW keying, otherwise the displayed reading can lag or jump.
-
Cheap SDR chain for HF and VHF: where dynamic range, noise and antenna choice actually limit you
For HF, I would first decide whether the problem is sensitivity or noise. Below about 20 MHz, man-made noise at most locations is far higher than the receiver's own noise, so a more sensitive radio doesn't help much. What helps is an antenna that gives good signal-to-noise ratio, and that is not always the one with the most gain. A small receive loop can null a local noise source by orientation. A long wire picks up more signal and more noise, and common-mode current on the coax can bring in noise from inside the house. A common-mode choke at the feedpoint and another at the receiver end are cheap and often worth trying before anything else. The computer is another source. Switch-mode supplies, USB 3 ports and cheap hubs can all put hash on HF. Try a USB 2 port, a short USB cable with ferrites, or a powered hub, and compare with the antenna disconnected. If the birdies stay with the antenna removed, the source is local to the receiver chain. For digital modes, the software chain is simple but the details matter. On Windows, a virtual audio cable carries demodulated audio from SDR#, SDRuno or HDSDR into WSJT-X or fldigi. Use USB demodulation, keep audio levels below clipping, and make sure the PC clock is accurate for FT8. Frequency error is a separate issue. A dongle with a TCXO makes ppm correction far less of a chore, and it matters more at VHF/UHF and when using an upconverter, where oscillator error is multiplied into the tuned frequency. If you want a panadapter on a transceiver, check how you split the antenna. Never connect an SDR input directly to a transmit path. Use an IF output on radios that have one, or a properly protected splitter or relay system. Then use CAT or rigctld to keep the SDR dial following the radio.
-
Good on-air habits: CQ calls, breaking in, nets and sharing frequencies
I'd add a few things about nets, because that's where nervousness shows up most. A directed net really does depend on discipline. If the NCS says "check-ins, stations east of the river only" and everyone calls at once, no one gets logged, and the NCS has to start over. Listening to how the NCS runs the net for a few sessions before checking in is the best preparation, and it's completely acceptable to just listen. If you are checking in, keep it to the format. Callsign phonetically, name, location, and any traffic. Then stop and wait. Don't tack on a weather report or a story about your antenna. The same rule applies if you volunteer as NCS. Give a brief opening statement, say what kind of net it is, ask for check-ins in a clear order, and acknowledge each station so people know they've been heard. Having a backup or relay station helps a lot when conditions are poor, especially on HF where the NCS may not hear everyone equally. One more thing: say who you are even if you've checked in before. Operators have different hearing and propagation conditions, and a clean callsign makes the logger's job much easier.
-
Getting clean, effective SSB audio: mic gain, ALC, compression, EQ and bandwidth for weak-signal and DX work
One check I'd add is a recording test. Record a few seconds of your transmit audio, ideally through a dummy load or at low power, and listen back with the processor off, then on. Hum, a hard "S", mouth noise and room reflections are much easier to hear on playback than live. I'd also treat "no ALC" as a starting point rather than a rule. Radios differ: some show ALC activity even when clean, others have separate compression meters and ALC behavior that the manual explains. The thing to avoid is ALC held hard against the limit during normal speech, because that usually means distortion, splatter or both. If you run an amplifier, make sure the radio's drive is set so the amp is not being flat-topped. That kind of problem can sound fine in the monitor but awful on the air.
-
Technician to General: how should I study for Element 3 and what do I actually get on HF?
Your numbers are right: 35 questions, 26 correct to pass. Confirm the current pool and your local VE team's rules before test day, since pools are revised on a multi-year cycle and you want to study the one that is in effect. For study order, I'd split the pool into three kinds of material. Understand it, don't memorize it. This covers electrical principles and propagation. For the electrical questions, know Ohm's law and the power formulas (P = E × I, and the variants), plus the decibel rules of thumb: 3 dB is about double power, 6 dB is about four times, and 10 dB is ten times. If you grasp these, the numerical questions become quick. For propagation, learn why the D layer absorbs lower HF frequencies during the day, why the F layer supports long-distance contacts, and what MUF means. Questions on solar flux and the K and A indices become much easier once you see what each one says about conditions. Memorize with a chart. This is the frequency and privilege material. Print a General band chart and trace the CW/data and phone segments for each band until the pattern sticks. Then practice recognizing which sub-band a given frequency falls in. Check any specific edge against the current Part 97 rules or an ARRL chart instead of trusting a forum post, mine included. Learn by association. Operating practices, Q-signals, and rules questions respond well to repeated practice tests. Take timed sets, and for each miss, read the explanation and write one sentence about why the right answer is right. A 4 to 6 week plan at 30 to 45 minutes a day is workable. A simple split is two weeks on theory (electrical, propagation, antennas), one week on regulations and band plans, one week on digital modes and operating practices, then a final stretch of full practice exams until you are consistently well above the pass line. Aim for roughly 85% or better on practice tests, because the real exam wording can differ slightly.
-
How do you filter ham radio news? New rigs, firmware notes, band-opening reports and FCC/ARRL items
For FCC and ARRL items, I'd keep a clear line between 'announced', 'proposed' and 'in effect'. Many headlines compress those into one. If a story mentions a docket or a rule, open the actual document or the issuing body's notice and read the effective date and any compliance language. Things that affect licensing, power limits or band privileges are the ones worth confirming at the source. For club news and awards, I'd suggest finding out what your local club or section already publishes: a newsletter, net announcements, a calendar for Field Day planning, VE sessions, and hamfests. That information is more actionable than the national news, and it's often where you'll hear about swap-meet gear, antenna work parties and operating-award deadlines. For awards like DXCC, WAS or POTA-related recognition, check the sponsor's current rules page before spending effort on a QSO or confirmation method, because acceptance rules can change.
-
SSB audio that carries: mic gain, ALC, compression and bandwidth for weak stations and DX
Good write-up. I would add a caution on the receive side: a narrower filter is not automatically better. If you go too narrow, speech becomes harder to follow, and a weak station with an off-frequency or drifting carrier can slip out of the passband. For a weak SSB signal, I would try the 2.4 kHz filter first, then use the shift control to move the passband away from the interference before shrinking the width. If the problem is a heterodyne, the notch might do more than the narrow filter. On DX pileups, the biggest improvement is often discipline rather than gear. Listen long enough to know who the DX is working, whether they are splitting, and how they like callsigns sent. Then call once, clearly and briefly, rather than repeating your call five times. A moderate, clean signal with a clear callsign usually beats a heavily processed signal that is wider than the rest. Question for the thread: for people with a built-in equalizer, do you keep separate profiles for DX and rag chewing, or one compromise setting?
-
Getting started with satellite work: FM birds vs. linear transponders, Doppler handling, and tracking setup
On the question of antennas vs. rotators: if you are on a handheld Arrow, the thing that limits you is usually how consistently you can point it, not the gain. Take the pass table from Gpredict with the AOS azimuth and max elevation, and aim slightly ahead of where the satellite will appear instead of chasing it. Also watch your feedline and duplexer losses. A small amount of extra loss on the 70 cm receive side has a bigger effect than most people expect. For a fixed station with a rotator, there is one practical trap to watch for: the pass that goes close to overhead. Azimuth can swing very quickly near zenith, and some rotators cannot keep up. Many operators prefer a slightly lower-elevation pass for that reason, or set up the controller to avoid it. SatPC32 and Gpredict both let you tune how often they send commands, and it is worth testing with the rotator disconnected from the antennas first. For QO-100, forget all that and put the effort into mechanical stability of the dish and the LNB, because even small wind movement matters at 10 GHz.
-
Run vs. S&P, mult timing, and SO2R: how do you decide when to leave a good run frequency?
The Q/M figure is a good rule of thumb, but it only works if multipliers are counted the way you assume. In some contests a prefix or section counts once for the whole contest. In others, like CQ WW, zones and countries count again on every band. That changes how you plan. With per-band mults, the second pass on a new band can be worth far more than the first. One workable approach is to keep the run as your base and go hunting only when a specific station is worth the trip. If a spot shows a rare multiplier on a band where you haven't worked it, jump on it quickly, log it, and go straight back. That's usually cheaper than a long S&P sweep. If you're running low power or have a modest antenna, you might also run less and spend more time pouncing, because a weak run frequency may not give you enough QSOs to justify holding it. On spotting, rules differ by category. In unassisted classes, many sponsors treat packet spots and Reverse Beacon Network spots as outside assistance. Some also count a local decoder such as CW Skimmer as assistance, and others word it differently. Read the sponsor's definition for that contest. If you enter assisted, set up a spot filter in N1MM for your band and mode and for needed mults, so a busy cluster doesn't bury what you actually want.
-
Predictions vs. proof: how do you decide whether a band is actually open?
I'd add some caution on SFI thresholds. Rules of thumb like "above X means 10 m is open" are fine as a rough guide, but they hide a lot. The same flux value can give very different results depending on the season, because the F2 layer behaves differently in winter and summer at the same latitude. Local time and the geomagnetic state matter just as much. A decent SFI with an elevated K can feel worse than a modest SFI on a quiet day. On sporadic E, the indices are close to useless. It isn't well predicted by SFI or K, and you mostly catch it by monitoring. Beacons and spot networks on 10 m and 6 m are the best option, and the clustering of spots can show how the cloud is moving. The same goes for tropo ducting: look at weather maps and pressure patterns, and watch for beacons on 144 MHz and above. For NVIS, the question isn't the MUF for a long path but whether your chosen frequency stays below foF2 and above the point where absorption is a problem. That's why 40 m often works in daytime and 80 m tends to take over after dark. Antenna height matters too: a low horizontal dipole, roughly a tenth to a quarter wavelength above ground, favors high angles. I wouldn't use VOACAP's long-path logic for that, though it can still give useful regional predictions if you set the distance and antenna parameters sensibly.
-
Learning Morse code from scratch: how do Koch, Farnsworth, LCWO, G4FON and CW Academy fit together?
On flashcards, the format decides whether they help. Cards that show a letter on one side and dots and dashes on the other teach a visual code, and that's the thing you're trying to avoid. In real CW you never see anything, you hear a rhythm. If you want cards, make them audio-first: hear the character, say or write it, then check. Software like LCWO or G4FON is already doing that for you, so a separate flashcard app is optional. On head copy, the shift is gradual. A few things help: Stop dwelling on misses. If you miss a character, drop it (write a dash or leave a gap) and pick up the next one. Chasing the one you missed makes you miss the next three.Lag behind the sender. Beginners tend to want to identify each letter the instant it ends. As you improve, you'll naturally stay a letter or two behind, and that gives your brain room to start hearing chunks.Move from characters to words. Once you know most of the alphabet, practice common short words and then callsigns and short phrases. Words stop sounding like strings of letters and start sounding like units. Common ham abbreviations and Q-codes (like QTH, QSL, QRS) also become single units quickly.Try copying without writing. Try this in short bursts at first. Write everything while learning characters, then gradually write less as words start to register.Plateaus are normal, and many learners notice them once they're no longer reading each letter separately and have to start recognizing words. It's usually a sign that the skill is changing, not that you've stopped improving. When this happens, mix up the material: plain text instead of random groups, callsign drills (RufzXP is a well-known callsign trainer), or contest-style practice with Morse Runner once you're comfortable with callsigns and exchanges. On confidence, you don't need to be fluent to get on the air. Slow CW contacts are a normal part of the hobby, and QRS ("please send slower") is a perfectly acceptable request. A good first step is to listen to real signals and copy whatever you can, then work up to answering a CQ at a speed you can handle. Prepare the standard exchange (callsign, signal report, name, location) so the routine parts are automatic. Mistakes happen to everyone, and operators generally understand that. The best time to try your first contact is when you can copy those basic exchanges reliably, not when you feel perfect.
-
Planning a from-scratch HF wire antenna: where the real compromises are (wire, choke, radials, modeling)
For choke verification, an analyzer helps. Connect it at the shack end with the antenna attached and watch whether the reading changes when you move the coax or touch it. A stable reading is a good sign, though not a guarantee. A clamp-on RF current probe is better if you have one. Compare the current on the shield on each side of the choke. If you only have an SWR meter, the same test still applies. Move the coax, add or remove a choke, and see if the numbers change. One point on modeling the choke: NEC models a perfectly balanced dipole, so the model won't show common-mode problems unless you include the feedline as wires. If you want to see how a bad choke changes the pattern, model the coax as a vertical wire below the feedpoint. It's a rough approximation, but it shows why the choke matters. On verticals, a quick check is the feedpoint resistance. A quarter-wave with a few elevated radials at a downward slope often reads close to 50 ohms. If you see 30 to 36 ohms, the radials are probably horizontal or the ground loss is lower than expected. That tells you something before you spend time on matching.
-
Building a solid CW setup and habits: paddles vs. bug vs. straight key, filters, QSK, and when decoders help
For keys, I'd separate the question of what is good for learning from what is fun to use. A straight key teaches you what correct spacing feels like. Paddles are better for sustained sending, and a decent keyer lets you adjust weighting and speed without fiddling with the key itself. A bug is a rewarding choice if you like the mechanical side, but its feel is quite different from paddles, so expect an adjustment period. One practical thing about decoders: they are best used for confirmation. If your decoder prints something odd, listen again before assuming the sender made a mistake. And in a contest, don't let the screen replace your ear. The operators who copy calls most reliably are usually the ones who learned to listen for the pattern, then used the logger to check the result.
-
Which radio mods are actually worth doing, and where does a modified rig stop being legal to use?
Start with the symptom before picking a mod. A lot of "my receiver is deaf" reports turn out to be local noise, not the radio. Switch-mode supplies, USB chargers, LED drivers, powerline adapters and badly shielded computer gear can all raise the noise floor. A battery-powered receiver away from the house wiring is a good test. If the noise disappears there, a filter inside the radio won't help. You need to find the source, then use ferrites, common-mode chokes on the DC and USB leads, better bonding, or a different supply. On the power side, voltage drop is the usual culprit on transmit. A rig that behaves on the bench and sags in the car is often limited by thin wire, a poor fuse holder or a marginal connector. Size the cable for the full transmit current, put the fuse close to the battery, and measure voltage at the radio during a keyed transmission, not at idle. If you move to LiFePO4, check the charge voltage and the battery's low-voltage cutoff. Don't assume it's a drop-in replacement for lead-acid in every setup. Lithium packs should have protection circuitry, and you shouldn't bypass it to squeeze out more runtime. For fans, a modest airflow improvement helps most on digital modes and other high-duty-cycle operation. Put the fan where it moves air across the heatsink, don't just stir the air in the enclosure, and watch for motor or PWM noise showing up on receive. A temperature-controlled fan is usually quieter in every sense than one that always runs. On the TCXO, check whether your radio's reference stage and the replacement part are actually compatible. Frequency, output level and mounting all matter, and an incorrect reference can leave the radio worse than before. Re-check calibration afterward with a frequency counter or a known-accurate signal.
-
Planning a dual-band mobile install: FTM-500D vs ID-5100A vs TM-D710G, and how to wire it so it stays quiet
On mounting, the first rule is that nothing goes where it could become a hazard in a crash or where it interferes with airbag deployment. Look at your vehicle's airbag markings and keep the radio body and bracket out of the knee area. Under the seat or on the transmission tunnel with a proper bracket can work, as can a mount on the dash with the control head separated from the body. Whichever you pick, the body needs some air movement around it. A radio running 50 W in a hot parked vehicle already has a heat problem before you add cross-band repeat. Use the mounting hardware that comes with the radio, or a sturdy bracket, and don't depend on sticky pads for something that weighs this much. For the antenna, the usual approach is an NMO mount in the center of the roof, which gives the best ground plane and a fairly even pattern. A dual-band antenna is a compromise, so measure SWR on both bands, not just one. A good SWR on 2 m with a poor one on 70 cm tells you something about the mount or the antenna, and a poor match on both usually points at the coax connector or the ground. Keep the coax run short and avoid kinks. UHF loses more in thin coax than VHF does, so a low-loss cable is worth the money on anything but a very short run. Never transmit without an antenna connected. For noise, work out where it comes from before you buy any filters. Compare the receiver noise with the engine off, then with it running, then with the accessories on one by one. Alternator whine that changes with RPM points to the power path or charging system. Ticking or hash can come from ignition, fuel pumps or aftermarket LED lighting. Dash cameras, USB chargers and DC-DC converters are frequent offenders as well. Keep the radio's power cable away from other wiring, check that the ground connection is clean and tight, and add ferrites where it makes sense. Fix the cause before you reach for squelch as a bandage. For cross-band repeat, treat it as a station you are operating, not a convenience feature. Check how your radio implements it, which band is the input and which is the output, and how station identification is handled, since you're responsible for ID under your local rules. Use the lowest power that works because the radio may run for long stretches. Be careful about the frequencies you choose so you don't interfere with existing repeaters, and keep the HT's power low if it sits close to the vehicle. As for etiquette, listen first, keep calls short, and identify properly. Announce that you are mobile if it helps other operators understand if you drop out. Driving comes first, so stay off the radio in heavy traffic, use a hands-free arrangement where the law permits, and check your local rules on handheld microphones. A mobile that is easy to ignore on a busy repeater is usually one that is polite and brief.
-
Bring-up order for a first homebrew QRP transmitter: what to check before you key it into an antenna
The order is good. I would move the harmonic check earlier for anything with a Si5351. Those outputs are square waves, so the unfiltered output is full of odd harmonics, and the amount depends on the stages after the clock. A rig can look fine on a power meter and still be loud on three times the frequency. If you only have one instrument for that stage, an SDR with a proper attenuator is more useful than a scope. On the first piece of test gear: a NanoVNA is good value, but it will not replace a dummy load. Check the load itself on the VNA, too. A homemade resistor load can look fine at 7 MHz and drift badly on 20 or 15 m because of lead inductance.
-
Winlink over radio: a setup order that works, from Telnet test to RMS gateway and P2P
On sound card setups, the usual culprit is audio level, not the software. Most problems come from too much drive. With VARA HF, ARDOP, or VARA FM, use the software's tuning display to set receive level, then set transmit drive so the radio's ALC barely moves. Overdriven audio makes splatter and lowers decode success for the other station, and the symptom is often repeated retries, not an obvious error. A few other practical points. Make sure the sound device used for the radio is not also your Windows system sound device, or notifications can go out over the air. Turn off audio enhancements on that device. On HF, set the power below the radio's maximum, because these modes have a high duty cycle and many rigs run hot in continuous transmit. PTT can come from CAT, a serial RTS/DTR line, VOX, or an interface's own PTT. Pick the one that gives the least delay and stays stable. If you run VARA HF and VARA FM on one PC, check their TCP command and data ports so they don't collide. The defaults are commonly 8300 and 8301, so you may need to change one. In Winlink Express, the VARA settings and the program's configured ports must match. For gateway choice on HF, try a couple of different gateways and bands instead of retrying one that fails. A clear propagation prediction is nice, but noise at the gateway's end can still ruin the connection.
-
Which microcontroller for shack automation? Pico vs ESP32 vs Arduino, and keeping RF out of it
I'd split it by failure mode. If a crash or glitch is merely annoying, like a display or a logging node, the ESP32 is fine. If a glitch could damage something, such as a relay switching under power, a PTT line, or an amplifier band-switch input, I'd keep that logic on a simple wired microcontroller and make the safe state the default. Pull PTT lines low through a resistor, and make sure relays de-energize if the controller resets. A watchdog timer helps, but don't rely on it as the only protection. On the ESP32 specifically, two details are worth knowing. The ADC is noticeably non-linear and noisy, so it's not ideal for a precise SWR or power meter unless you calibrate it or use an external ADC such as an ADS1115 over I2C. Also, ADC2 pins can't be used while Wi-Fi is active on many ESP32 variants, which catches people out. For an SWR meter built around a log detector like the AD8307, you also need to think about the detector's nonlinearity near the noise floor, the coupler's frequency response and a calibration table. The microcontroller is the easy part. For CAT on Icom, remember CI-V is half-duplex on one wire, so everything you send is echoed back to you. Your code must either discard its own echo or handle it as part of the frame parsing.
-
Small-yard HF antenna choices: what SWR hides, and where the losses actually are
It's also worth separating bands by what you actually want to do. If most operation is on 40 and 20 m, a simple dipole or inverted V cut for the main band, with a second wire for the other, will often beat a single compromise antenna covering everything. Multiband convenience costs something in loss, pattern, or setup effort, so decide how many bands you really need. On the vertical question: a ground-mounted vertical in a small yard can work, but it is only as good as its ground system. A few dozen short radials do a lot more than three long ones, and a loaded vertical with a poor ground is usually the one that sounds deaf and makes few contacts. If the yard allows elevated radials, four tuned radials per band beat a sparse buried system. If it doesn't, expect a weak transmitter and a noisy receiver compared with a horizontal wire up in the trees. For the HOA side, remember that visibility matters more than the electrical details. A thin dark wire is almost invisible against branches, and it's often the simplest solution. The tricky part is feeding it neatly. The feedline can usually be tucked along a fence line or buried in conduit, and a lightning arrestor and a ground are worth having whichever antenna goes up. Keep RF safety in mind for anything that comes near people or pets, particularly the ends of an EFHW.
-
Band plan vs. FCC rules: how do you work out where to operate from 160 m to 33 cm, and where the band edges really are?
Start with the split between law and convention. The FCC rules in Part 97 are the law: which bands your license class can use, which emission types are allowed in which segments, power limits, and so on. The ARRL band plan is voluntary. It says where the community has agreed to put SSB, narrowband digital, beacons, SSTV, calling frequencies and so on. You can be perfectly legal and still be a nuisance if you park a wide signal in the middle of the weak-signal segment, and you can follow the band plan and still be illegal if you're outside your privileges. On HF, think in three layers. The bottom of each band is CW and narrowband data. Phone sits in the upper part. Inside the CW/data area, the digital modes tend to cluster at conventional spots. The popular FT8 dial frequencies are roughly 1.840 on 160 m, 3.573 on 80, 7.074 on 40, 10.136 on 30, 14.074 on 20, 18.100 on 17, 21.074 on 15, 24.915 on 12 and 28.074 on 10. These are conventions, not rules, and they shift a little between sources, so cross-check with the software's own list or the current band plan. For privileges, the big picture is this. Technicians get limited HF: CW on segments of 80, 40 and 15 m, and on 10 m CW and data from 28.000 to 28.300 plus CW and SSB from 28.300 to 28.500, with a 200 W PEP limit. Generals get all the amateur HF bands, but not all the segments. The Extra-only slices sit at the low end of the 80, 40, 20 and 15 m phone and CW areas, so General phone starts around 3.800, 7.175, 14.225 and 21.275. Extras get everything. Always read the exact edges from the FCC table, because the numbers above are the ones people commonly remember. The special cases are worth memorizing. 30 m is CW and data only, with a 200 W PEP limit, and no phone. The 30, 17 and 12 m bands are the WARC bands, so by convention there are no contests there. On 20 m, the NCDXF/IARU beacons transmit around 14.100, with similar beacon spots near 18.110, 21.150, 24.930 and 28.200. Don't transmit right on top of those. Band edges are where sidebands bite. The rule is that your whole occupied bandwidth has to be inside your privileges, not just the dial reading. On LSB the signal extends below the dial frequency. If your General phone segment starts at 3.800 and you sit at 3.800 LSB, the lower part of your signal is outside the segment. Back off by the width of your signal plus some margin. On USB it's the reverse: at the top of the band or at the top of your privilege segment, you need that margin above the dial. With digital modes, the signal sits at dial frequency plus the audio offset, so something at a 2.5 kHz audio tone is actually 2.5 kHz above the dial, and the same margin logic applies. When in doubt, move away from the edge by a couple of kilohertz rather than test how well your radio's filter and your math agree. Finally, 160 m is shared in a way that matters for etiquette. CW and narrow digital are conventionally at the bottom, and phone and wider modes are higher. If you listen for a minute, you'll learn where people actually sit.
-
Keeping your award credits straight: DXCC, WAS, WAZ, WPX, IOTA, POTA and SOTA, and where LoTW fits in
On the POTA and SOTA side, people often assume the contact works like a DXCC QSO, and it doesn't. For hunters, the credit usually depends on what the activator uploads, so a typo in your call on their end can cost you a contact. If a park or summit contact is missing from your stats, contact the activator or check the program's own rules for log corrections, because LoTW is irrelevant to that credit. If you are also working toward WPX, WAZ or WAS with the same operations, keep everything in a single ADIF master log and export from it for each program. The CQ programs have their own application rules, fees and checking processes, and they won't necessarily accept the same confirmations the ARRL does. A rule that applies to one award can fail on another, so read each sponsor's current instructions every time you apply, and don't rely on memory from the last submission. For the CQ DX Marathon, remember that it is calendar-year based. A lot of operators plan ahead for January, because the zone and country totals start from zero when the year rolls over.
-
Good operating habits: CQ calls, breaking in, nets and what to do when someone is on your frequency
On interference, the boring answer is often the best one: don't engage. If someone is deliberately jamming, arguing back only gives them what they want. Identify yourself normally, note the time, frequency, mode and what you heard, and move if you can. Most of the time, though, it isn't malicious. It may be someone who didn't hear you, a station who didn't ask if the frequency was in use, or noise from a neighbour's equipment or your own shack. Check which it is before assuming the worst. There are a few practical steps. A narrower filter, notch, or noise blanker helps with a lot of problems on the receive side. If you're the source of the problem, for example an overdriven audio chain, a splatter signal from too much ALC, or digital transmissions that are too wide, fix it as soon as someone mentions it. If a signal is persistent and harmful, document it and report it to your local repeater coordinator, national society or regulator, depending on the case. Avoid public call-outs on the air. For digital modes like FT8, a similar principle applies. Look at the waterfall before transmitting, avoid sitting on top of an existing signal, and keep audio levels low enough that your signal stays clean. Using the same slot as someone else's CQ is not a good way to start a contact.