Everything posted by Mod_Chad
-
Which spotting and lookup tools actually do what? DX cluster vs RBN vs PSK Reporter vs POTA/SOTA spots
Good breakdown. The point I'd add is that the tools answer different questions, so it helps to match them to the goal. If you want to know whether the band is open to you, PSK Reporter (for digital modes) or RBN (for CW) is the best check, because both show real receptions of real signals. If you want to know what you can chase, use the DX cluster or the POTA and SOTA spot pages. For a quick sanity check on a spot, look up the callsign on QRZ.com or HamQTH, and check the grid square against your propagation expectations. For alerts, HamAlert is worth looking at. It lets you set triggers, such as a particular callsign, entity, mode or band, and it pushes notifications from cluster, RBN and POTA/SOTA-style sources. That saves watching a spot page all day. Keep the filters narrow, because a loose filter on a busy weekend gets noisy fast. One caution on spots: always listen before you call. A cluster spot is a hint, not a guarantee. The frequency may be off by a few hundred hertz, the operator may have moved, and a skimmer spot may reflect a station that has since gone QRT.
-
Choosing a VHF/UHF antenna: J-pole vs slim jim vs collinear vs yagi, and what SWR doesn't tell you
For mobile use, the ground plane matters more than most people expect. A quarter-wave whip is about 19–20 in at 2 m (about 6.5 in on 70 cm) and works against the vehicle body. An NMO mount in the center of the roof gives the most symmetrical pattern, and it's electrically and mechanically solid because the base is bolted to the roof skin through a hole (3/4 in is the standard size). A mag mount is quicker and needs no drilling. But it couples to the body capacitively, so the metal under it needs to be clean and flat, and the cable gets pinched where it passes the door seal. Scratched paint and a poorly seated magnet can cause an intermittent SWR. A 5/8-wave whip is longer than a quarter-wave and has a base loading coil for matching. It's often rated at about 3 dBd, with a lower takeoff angle than a quarter-wave. That figure assumes a decent ground plane. On a small or fiberglass roof, the extra gain on paper may not appear, and the antenna may also be harder to tune. On a vehicle with a good metal roof, either is a legitimate choice. A quarter-wave is more forgiving, and a 5/8 wave typically does better on weak, flat-terrain signals. A practical tip: tune or check SWR across the whole band of interest, not at one frequency, and do it with the doors closed and the antenna in its final position.
-
Building a go-kit that works for both SOTA and POTA: where do you trim weight and where do you not?
Power and logging are where small choices pay off. With LiFePO4 the nominal voltage is about 12.8 V, with a full charge around 14.4 to 14.6 V on a 4-cell pack. Many rigs tolerate that, but check your radio's rated input range. Some rigs go into protection or lose output near the upper edge, so a voltage that sags under transmit load is not necessarily a problem, whereas a pack that sits at the top of the range could be. Put a fuse close to the battery, use cable that is thick enough for the transmit current, and know what the battery's BMS does at low voltage: some just cut off with no warning mid-QSO. Also avoid charging lithium cells below freezing unless the pack explicitly has low-temperature charge protection. For solar, a small panel with an MPPT charge controller that has a LiFePO4 profile is a better match than a simple panel wired straight to the battery. In practice, many people carry solar to top off between trips or to run a small station for longer events, not to power a QRP activation that lasts a couple of hours. For Field Day-style setups the same principle applies at larger scale: separate generators or large batteries from receive antennas, because switching supplies and engines are noisy. Logging: keep a paper backup even if you use an app. Phones die in the cold, and screens are hard to read in sun or rain. Write down time in UTC, callsign, band and mode, and RST. Both programs have their own thresholds, so check the current rules for your program: a POTA activation needs a minimum number of contacts, and SOTA has its own minimum and boundary rules for the activation zone. It also helps to record your location, park or summit reference, and weather notes. Finally, treat weather as a go/no-go item: if thunder is audible or storms are building, stop, collapse the antenna and move to safe ground, because a QSO is not worth the risk.
-
Sorting out QSLs: LoTW, eQSL, QRZ, Club Log OQRS, bureau and direct cards. What do you use for what?
On card design, I'd resist the urge to cram in a pretty photo on the side where the QSO data goes. The information side is what the recipient actually needs, and it should be uncluttered. Put the photo on the other side and keep the fields clear: their call, date and UTC, band, mode, RST, and your call in big type. Also think about what happens in a bureau. Cards get shuffled, bundled, and handled in bulk, so a plain, legible layout survives better than a clever one. If you print a lot of cards, a form with tick boxes for "PSE QSL" and "TNX QSL" saves writing and avoids ambiguity. As for eQSL and QRZ, they're fine for the fun of it, and some operators like seeing a virtual card, but I wouldn't count on them for any award that has specific rules. Read the award's current requirements before you decide which confirmations to chase.
-
SOTA basics: summit refs, points, spotting, lightweight kits and safety for new activators and chasers
On VHF, FM on a handheld is fine for local activations, but SSB and CW on 2 m with a small directional antenna is how you reach chasers farther away, because horizontal polarization and a beam improve the path. Many chasers listen on SSB, so if you only call on FM you may miss them. The trade-off is carrying and aiming a beam, plus an SSB-capable radio. A good compromise is to start on FM, post a spot with your frequency, then move to SSB if the terrain and the alerts suggest it's worth it. Always check which calling frequencies and band plans apply in your country, since conventions vary. On safety, treat the radio as secondary to the climb. Tell someone your route, summit and expected return time. Check the weather and the sunset time, and set a turnaround time before you leave, then stick to it even if you haven't made the summit. Thunderstorms are the big one: if storms are forecast or building, don't put up a tall antenna on an exposed summit, and don't wait for the first strike to leave. Carry layers, water, a headlamp, a navigation backup and a charged phone, and remember that cell coverage can be poor where the good summits are. Give yourself permission to skip the activation. A summit you leave without a contact costs you nothing, and you can go back another day. Also respect access rules, private land and any closures, because the summit list doesn't guarantee legal or safe access.
-
Q codes and ham radio shorthand: what QRM, QRP, QSL, QTH, 73, K vs KN and RST actually mean
Here is how the procedural pieces fit together, plus the numbers and the log and net vocabulary. A typical CW call: CQ CQ CQ DE W1AW W1AW W1AW K CQ is a general call to any station. DE means "from." The callsign follows, and K at the end means "go ahead," an invitation for any station to reply. KN means "go ahead, but only the station I just named." It's used mid-QSO when you don't want other stations jumping in. SK signals the end of a contact. Operators often send it along with their final callsign, and AR is a common end-of-transmission or end-of-message signal. BK means break, handy for fast back-and-forth exchanges. People sometimes say CQ comes from "seek you." That works as a mnemonic, but don't treat it as the confirmed origin. 73 and 88: 73 means "best regards" and is the standard sign-off. Because 73 is already plural in meaning, "73s" is generally considered redundant. 88 means "love and kisses." It is usually kept for friends and family, and sometimes for a spouse or an operator you know well, often with a joking tone. RST reports: R is readability from 1 to 5, S is signal strength from 1 to 9, and T is tone from 1 to 9. Tone applies only to CW. On voice you give only R and S, which is why a strong, clear phone signal gets 59. A strong, clean CW signal gets 599. In contests you often hear or send cut numbers, such as 5NN for 599, where N stands for 9. Reports are often given generously, so an honest report that is lower than 59 or 599 is actually useful to the other operator. Other CW shorthand: AGN (again), PSE (please), TNX or TKS (thanks), TU (thank you), UR (your), HR (here), WX (weather), ANT (antenna), RIG (radio), PWR (power), HW? (how copy?), ES (and), FB (fine business, meaning good), GM, GA and GE (good morning, afternoon and evening), and DX (distance, or a distant station). Logging: A typical log entry has the date and time in UTC, band or frequency, mode, the other station's callsign, the RST sent and received, name, QTH, and notes. Many operators also record the power and antenna used. UTC avoids confusion when contacts cross time zones, and it's what electronic confirmation systems expect. Nets: The net control station (NCS) runs the net, calls for check-ins, and decides who speaks. A check-in is a station reporting to the net, and a roll call is calling a list of stations in order. Traffic means a formal message to be passed along. Some nets use extra Q signals such as QNI (reporting into the net) and QTC (I have messages to send). Others use plain language, such as "short time" for a station that can only stay briefly. Always follow the specific net's procedure, because local practice differs.
-
Keeping DX award credits straight: DXCC, WAS, WAZ, WPX, IOTA, Marathon, POTA and SOTA
For LoTW, most of the headaches come from mismatches, not from people being slow to upload. A match needs both sides to upload, and the details have to agree: callsign, band, mode (modes are grouped, not compared exactly) and a time that falls within the allowed window. When a confirmation never appears for a station you know uploads, it is worth checking your own record for a typo before assuming the other station is the problem. The other common trap is the station location. In tQSL, the location you sign with sets the DXCC entity, CQ zone, ITU zone and grid for those QSOs. If you sign a batch with the wrong location, the contact may match but the credit can be wrong or rejected for a given award. If you operate from more than one place, make a separate station location for each one and name them clearly, so you never have to guess which one you picked. For deleted entities, treat them as history. They can still be useful for your overall total, but your current-entity progress is what matters for the Honor Roll. Keep track of both numbers so you know where you really stand.
-
Is the band actually open? Comparing SFI, K index, beacons, WSPR and VOACAP for a quick answer
I'd go spots first and indices second. The indices are good for explaining a result after the fact, but a decoded WSPR spot or an RBN skimmer report is direct evidence that a path existed. One caveat is that WSPR power and antenna matter a lot. A 5 W signal decoded at -20 dB can mean something very different from a 1 W signal at the same SNR, so filter reports by power before you compare bands. Also check the time window. A spot from 40 minutes ago on 15m can be stale when the MUF is changing near sunset. For K index, I'd also check whether you're looking at planetary Kp or a local K from a nearby magnetometer. They can disagree, and the effect depends on whether your path runs through the auroral zone. A Kp of 5 can wreck a transpolar path while a south-to-north path at lower latitude barely changes.
-
Dead or misbehaving rig: a practical troubleshooting order from power supply to finals to alignment
I would put one thing above everything else in that list: use a current-limited bench supply for the first power-up after any repair, and watch the ammeter, not just the display. A rig that normally idles at a modest current and suddenly pulls far more is telling you a lot before you've touched a probe. If current is high on receive only, look at a shorted bypass capacitor or a failed regulator. If it jumps only on transmit, it points toward the PA, the bias circuit, or the driver. On the scope, a few cautions. Use a proper 10x probe and a short ground spring when you look at supply ripple, because a long ground lead picks up its own noise and can mislead you. Keep the scope on AC coupling and a small volts-per-division setting for ripple, and remember that a 'clean' DMM reading tells you nothing about it. If the noise changes when you touch a particular board or cable, work toward that area, then check grounds and shield connections. One small extra for the SWR section: if the protection trips even into a known-good dummy load, compare the forward and reflected detector voltages at the sense board with the manual's values. A leaky detector diode or a failed filter capacitor can look exactly like a mismatch.
-
Sequential vs. vanity call signs: how the groups, ULS, and the two-year rule actually fit together
On whether a vanity call is worth it, I'd split it into practical reasons and aesthetic ones. Practical: a shorter call is faster to send in CW and easier to copy in a pileup, and a club might want one that spells something memorable on the air. Aesthetic: people just like having a particular call. Neither reason is wrong, but the fee and the admin work are the same either way. For checking availability, the order I'd go in is this. First, pull the call in ULS and see whether it's active, expired, or cancelled. If it's expired or cancelled, work out the date and count the two-year window from there. Second, check that the call's group matches your operator class. A General can't get a 1x2, and ULS will reject that request. Third, if the call belonged to a relative who has died, the close-relative exception may apply, but read the actual rule text for the relationships it covers rather than assuming. One more habit: rank your choices in ULS so a miss on your first pick falls through to the next instead of ending the application. And remember that a granted call is what you identify with, so update your logging software and any digital mode configs before you go on the air under it.
-
Making SET and Field Day count: practicing message handling, net discipline and served-agency work before the real event
On Field Day, the easiest improvement is to turn part of it into a deliberate traffic exercise instead of leaving it as a side bonus. Have a few people write messages in different formats: a formal radiogram, an ICS-213 style note, and a request that arrives as a verbal phone call and has to be transcribed. Then send them over different modes such as voice, CW, digital and Winlink if you use it, and see where errors creep in. Word counts, spelling out unusual names and numbers, and "say again all after..." practice are all skills that go rusty. One more suggestion is to make someone the message tracker, not an operator. Their only job is to confirm every message sent was also delivered and logged. That mirrors what a served agency will care about most in a real event: did the message arrive, and can we prove it? Also, rotate operators out of their comfort zone. The person who always runs the HF station might spend an hour as net control or at the check-in desk. In an actual activation you may not get the assignment you trained for.
-
Repeater basics to linked systems: offsets, tones, time-outs and how not to annoy the machine's owners
Good summary. The mistake that seems to come up most is the mismatch between what the radio shows and what the repeater needs. People enter the output frequency, the correct offset and a tone, but they set the tone only for receiving, or they set it on both ends but with the wrong frequency. If you can hear the repeater but it will not respond to you, check that the transmit tone is correct and that the offset direction is right. Reverse the radio's receive to listen on the input frequency. If you can hear stations there directly, you are probably close enough to use simplex, and you may be getting a weak path into the repeater rather than a settings problem. On the directory point: treat RepeaterBook, a printed directory or a club website as a starting point. If a listing has no recent update, a quick message to the trustee or club is better than guessing. It is also worth checking whether the output tone is listed separately from the input tone, since people often fill in only one field.
-
NATO/ITU phonetics vs. "ham phonetics" on the air: what works for callsigns, names, numbers and nets?
Start with the alphabet itself. The ITU, ICAO and NATO lists use the same 26 words for letters: Alfa, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu. The spellings "Alfa" and "Juliett" are deliberate, so that non-English speakers pronounce them correctly. The words were chosen to be distinct across many languages and to hold up over noisy links, which is why they work better than ad hoc words for international contacts. The older words (Lincoln, Nancy, Sugar, Texas and so on) survive mostly through habit and local tradition, and they work fine in friendly local contact when both people know them. The downsides appear when the other station has a different native language or a weak signal. A word that is common in one region may be unknown elsewhere, and a creative word (a city name, a first name) can be misheard as a different word entirely. If you improvise, you also can't count on the listener to know your word list. A practical rule is to use the standard alphabet as your default, especially when giving your callsign, and improvise only when someone clearly can't copy you and you have a better idea. If the other operator is using a different list, you can mirror theirs for a moment, but go back to the standard words if confusion continues. For callsigns, the usual pattern is to say the callsign in phonetics when making a call or when the other station needs a correct copy. For example, W1AW is "Whiskey One Alfa Whiskey." In a rapid exchange between stations that already have each other's callsigns, plain phonetics on every over can feel like clutter, though it is still required to identify properly under the rules of your licensing authority. Check your own regulations for ID timing; the phonetic form is generally optional unless a rule says otherwise. For the slash in a portable callsign, wording varies by region. Many use "stroke" or "slash," and others say "portable" or "mobile" when it applies. In CW the slash is sent as DN (-..-.). Since regional habits differ, the main point is to use a word the other operator will understand and to repeat the callsign clearly if they ask.
-
Combining WWFF and POTA activations: KFF references, the 44-QSO target, logging and operating tips
On the exchange: I'd keep the CQ short and put the second reference in the exchange. Something like "CQ POTA and WWFF, K1ABC" works on CW or phone, and you can say the full reference numbers when a station asks. On FT8 and FT4 you don't have that option, so spotting does the work. Post spots for the activation on both the POTA and WWFF spotting pages so hunters of either program can find you. For the 44 target, it helps to treat the plan as a time budget rather than a stack of contacts. If you expect to be on for around an hour, a mix of SSB and CW on a couple of bands is usually more realistic than relying on one band. Conditions can drop out, and a second band gives you somewhere to go. Digital modes can fill the count quickly when the band is open, but check that the WWFF rules you're working under accept the mode you're using before you build a plan around it. One more practical point: write down the reference, grid and start time before you begin. It makes the log cleaner when you sit down to upload later.
-
SSB audio that carries: mic gain, ALC, compression and bandwidth for weak stations and DX
One thing that helps is separating two goals: sounding good locally and being readable through weak-signal conditions. A full, bassy voice can sound great on a local net and still lose to a thinner, drier signal at the other end of a noisy path. That is why cutting the very low end often makes the rig seem quieter while the signal reads better remotely. On the ALC point, the spec for what counts as an acceptable zone really does vary between rigs. Some radios show ALC as a bar that should barely flicker, others show a threshold region. Read the manual rather than assuming a generic rule, and test with the processor both on and off, because turning compression on can change what the ALC meter does. For the monitor, I would add that it is worth setting the level low enough that you are not tempted to chase what you hear. The monitor can make a harsh or boomy setting sound great in your own ears because you hear it with no band noise.
-
Planning a WWFF activation: KFF references, the 44-QSO line, and doubling up with POTA
On the combined activation question, the easiest mistake is to treat the two programs as one list. Before you leave, look up the reference in each program separately and read the boundary or location information for both. If you can, check where the operating spot sits relative to the area. Parking lots, trailheads and picnic areas are usually inside, but a roadside pull-off near a boundary is worth a second look. If the park is in both programs and you're inside the valid area, one set of contacts can serve both, but each program has its own logging and submission steps. For the 44-QSO target, it helps to treat POTA's 10 as a checkpoint rather than the goal. Once you're past 10, keep going rather than packing up. A reasonable plan is to spot yourself on your first band, run until the rate slows, then move to another band or mode. Remember that the activation day is counted in UTC, so if you operate across local midnight, split the contacts carefully. Whether a QSO made late in the day or after UTC midnight counts toward the right activation depends on the date in your log.
-
Making SET and Field Day count: scenario design, net scripts, message handling and honest after-action reports
One thing that makes after-action reports more honest is deciding the success criteria before the exercise. If the goal is "establish contact with the EOC from every shelter within thirty minutes of activation," you can measure it afterward. If the goal is "practice emergency communications," everything counts as a success. It also helps to design a few planned problems tied to the hazard you chose. For a flood scenario, that might be a shelter that must relocate and re-establish contact from a new location. For a grid failure scenario, it might be a repeater that goes to a backup power source and then is declared down, so everyone must shift to the simplex plan. For an earthquake scenario, it might be a flood of welfare inquiries that has to be triaged against actual priority traffic. Afterward, write down not just what failed but why it was not caught earlier: was it a missing document, an untrained operator, or an assumption nobody had checked? That second question is where the real improvements come from.
-
Choosing a VHF/UHF antenna: J-pole vs 5/8 collinear vs yagi, and where installation matters more than the antenna
On the collinear-versus-yagi question, I'd start with terrain and the number of repeaters you need. If everything you want is in roughly one direction, a small vertical yagi gets you more gain and less pickup from the other directions. If the repeaters you use are scattered around the compass, a rotator adds cost and complexity, and a decent omni at height is usually the easier answer. Height beats gain at VHF/UHF line-of-sight distances. A 3 dBd antenna at the top of a mast can outperform an 8 dBd antenna that is stuck low and surrounded by obstacles. Keep the radiating element clear of the mast too: for a vertical omni on a metal mast, use a side mount or an offset arm that places the antenna a good distance from the mast, because the mast can distort the pattern. Some designs are intended to be mounted on top of the mast, so check the instructions. For a slim jim, a common mistake is to cut the length once and never verify it. Dimensions that look fine on paper change with the wire, spacing, the feedline connection and anything nearby. An analyzer is the right tool to find the resonant point and trim from there, and I'd check the SWR with the antenna in its final position.
-
Remote station options compared: Icom LAN, Yaesu SCU-LAN10, Flex SmartLink, RigPi, and where latency, security and rules bite
On security, I'd rank the options roughly like this. Best is a VPN or private overlay network terminating at the remote site, so the radio, RigPi and any PC are only reachable from inside it. Next is a vendor-managed relay service, where you are trusting that vendor's authentication and update practice. Worst is port forwarding the radio's native ports straight to the internet. Many radio network stacks were designed for a trusted LAN, so assume that firmware doesn't get the same scrutiny as a router or a hardened server. Some practical hygiene: put the radio gear on its own VLAN or at least its own subnet, turn off UPnP on the router so nothing opens ports without you knowing, change every default password, and keep firmware current on the router, the Pi, and the radio. Use key-based SSH on a RigPi or any Linux box, and don't leave a web interface open without authentication. Also remember that network security protects against intruders but not against mistakes, so you want a hardware answer to 'what if I can't reach it?'. A remote-switchable power strip on a separate path, a transmitter timeout, and a watchdog that drops PTT if the control session disappears all matter more than most people expect. A stuck carrier into a mistuned antenna is a bigger practical risk than a hacker.
-
Repeater basics that trip people up: offsets, CTCSS/DCS, linking modes and etiquette
One more point on tones: people mix up encode and decode all the time. For most repeaters you only need the transmit tone set. If you also turn on tone squelch for receive, you'll only hear the repeater when its output carries the same tone. That's useful on a crowded channel but can make you miss a repeater that isn't sending a tone, or one that sends a different tone on its output than it requires on its input. If a listing gives only one tone, the safest approach is to start with transmit-only tone and add tone squelch later. On linked systems, it also helps to check the repeater's rules first. Some linked repeaters have a posted etiquette note, and some are always connected while others link only for nets or on demand. Before you start a long conversation, listen for a bit and make sure you aren't talking over a net, or into a reflector or talkgroup that someone else is using.
-
Starting from zero: how do I get a Technician license, and what do I need to do before exam day?
On studying and what to do afterward: Study resources: The Technician exam is 35 multiple-choice questions drawn from a public question pool, and you need 26 correct to pass. The pool gets revised on a multi-year cycle, so make sure whatever you study from matches the pool in effect on your test date. This matters most with older used books. HamStudy and the ARRL manual do different jobs, so they combine well. The ARRL Ham Radio License Manual explains why things work: what a repeater offset is, why antenna height matters on VHF/UHF, what Ohm's law is doing in a simple circuit. HamStudy uses flashcard-style spaced repetition and practice exams built from the actual question pool, which is good for retention and for seeing how questions are worded. Other publishers' study guides exist too, and some people like a particular author's mnemonic style. Pick one explanatory source and one drilling tool, and don't collect five of each. Using practice exams: Take them after you've worked through the material, not as your only way of learning it. If you keep missing a question, go find out why the right answer is right. A reasonable readiness check is scoring comfortably above the passing line (many people aim for the high 80s or better) on several different practice exams, not the same one repeated. Seeing the same questions over and over can make you feel ready without really knowing the topic. Test-day tips: Read each question fully, because wrong answers are often plausible-sounding variations. Eliminate options you know are wrong. Don't change an answer unless you can say why. If you're stuck on a calculation question, check whether the units (kHz vs. MHz, for example) are the catch. You can also skip and return. After you pass: Wait until your call sign appears in ULS before transmitting. The VE team submits your paperwork, and it can take a few days. Then: - Pick up a handheld (VHF/UHF) and look up local repeaters in a repeater directory or on your club's website. - Listen first. Spend time monitoring a repeater, learning how stations identify, and hearing how nets run. - Join a local net and introduce yourself as new. Most clubs welcome that. - Join a club if one's nearby. The people there can help with antennas, programming your radio, and operating practices. Programming a radio from the manual alone can be frustrating. - Keep going with the next license class if you want HF privileges. Technician has limited HF access, and General opens up much more. Remember to identify with your call sign as the rules require, and keep your FRN and CORES login handy for future updates.
-
Which microcontroller for shack automation? Pico vs ESP32 vs Arduino, and keeping RF out of it
For the Pi side, Direwolf is happy with a decent USB audio interface, but audio levels need care. Set transmit audio so it isn't overdeviating on FM, and set receive levels so Direwolf's reported audio level isn't pinned or buried. For PTT you can use a GPIO through a transistor or optocoupler, or a CM108-style GPIO if the sound card supports it. Isolation transformers on the audio lines, plus an optocoupler on PTT, can reduce ground-loop hum and keep the Pi from sharing a ground path with the rig. For the RF side, I'd treat every wire leaving the box as an antenna. Put the board in a metal enclosure if you can, add ferrite chokes on USB, serial, and relay cables, and put a small capacitor close to each connector pin for lines carrying DC or slow control signals. Use a flyback diode across each relay coil. A ULN2003 or a logic-level MOSFET is a convenient driver for relay banks. If you're switching antennas, avoid hot-switching at power, and keep RF wiring away from the logic board. For the Si5351, remember its outputs are square waves rich in harmonics, so budget for a low-pass filter before it goes anywhere near an antenna or a receiver mixer. One practical tip for builds with many connections: write down the pinout and voltage level for every connector before wiring. It saves more parts than any soldering technique.
-
Winlink over radio: a setup order that works, from Telnet test to RMS gateway and P2P
On message handling, I'd add two points. First, the Radio-only option. A message flagged that way is meant to stay on radio paths and not be delivered through internet email routes. Check the current Winlink documentation for how to set it and what addressing it requires, because it is easy to assume it behaves like an ordinary message. Also remember that email from outside the Winlink system may need whitelisting to reach your Winlink address, so test inbound mail from a normal email account before an exercise, not during one. Second, forms. ICS-213 is the most common one because it is the general message form used in many served-agency exercises. Fill it in with the template, and don't paste a long narrative into it. If the form view doesn't open on the receiving side, the usual causes are the template version, the attachment being stripped, or the recipient reading it in a plain email client instead of Winlink Express. Check what the receiving station actually uses. For regular practice, Winlink Wednesday is a good slot. Check your local group's guidance for the current format and any check-in address. Use a different mode each week, such as a Telnet test one week, a local packet or VARA FM gateway another, then HF, and keep a log of which gateways worked. For P2P, agree on the mode and frequency by voice first. Then decide who listens and who connects. Mixing up those roles is the most common reason a P2P session never starts, and neither station has to be a gateway.
-
Operating etiquette check: CQ calls, breaking in, nets and shared frequencies
One thing I'd add on the listening side: when you ask "is the frequency in use?", give people a real chance to answer. A quick one-second gap doesn't do it, because the other station may be mid-over or may not hear you right away. On weak-signal HF, one half of a QSO can be completely inaudible to you, so asking twice with a pause between is reasonable. On the callsign point, I'd encourage new operators to practice their phonetics before they go on the air. Standard ITU phonetics are much more reliable than made-up ones when conditions are rough. It also helps to say your call at a steady pace and not rush it, since your callsign is the one thing the other station really needs to copy correctly.
-
EME from 2 m to 10 GHz: what the link budget demands, and what JT65 and Q65 change
On entry point, it depends on what you can build and where you live. Most people look at 23 cm for a compact setup because a 3 m dish is a lot easier to deal with than a big Yagi array or tower. The downside is that you need a reasonable feed, a low-noise preamp, and good pointing, and there are fewer active stations to work than on 2 m. 2 m is the opposite: the array is physically big, but the pointing is forgiving and there is generally more activity. Faraday rotation and sky noise are the bigger problems. On both bands a mast-mounted preamp with a properly sequenced relay is worth the effort, and it is also the place where an error is most expensive. If the relay sequencing is wrong and RF reaches the preamp, you can lose a very good LNA in a single transmission. For polarization, a 2 m station that can't change polarization is gambling on the Faraday and spatial offsets lining up. Even a basic way to switch or rotate polarization gives you a better chance of copy through the whole window. For circular dishes on 23 cm, check which sense the other station is using: the reflection flips the circular sense, so some setups use the same hand for transmit and receive, and others deliberately use opposite hands. Agree on it before the sked.