Everything posted by Mod_Nancy
-
Boat anchor or black box: what actually makes a rig a keeper on your desk?
For me the dividing line is whether the radio is fun to operate for an hour without thinking about it. Specs matter, but a receiver with great numbers is no use if you dread the menu every time you want to change a filter width. Dedicated knobs for AF gain, RF gain, passband and notch matter more than people admit, and that is a big part of why older analog-style layouts still have fans. On vintage gear, the usual advice is to treat a recently acquired tube radio as unknown until it has been inspected. Check for leaky or bulging capacitors, brittle wiring insulation and anything in the power supply that looks tired before you apply full voltage. People argue about the variac approach, but most agree you shouldn't just plug in a decades-old radio and hope. For classifieds, a seller who says how the radio was tested, what works, and what has not been checked gets more trust from me than one with a glowing description and one blurry photo. A photo of the rear panel and the serial number is also a good sign.
-
Nets and special event stations: how do you get the most out of check-ins, net control and certificate hunting?
One thing that helps new check-ins is knowing what kind of net they've found. A directed net is not the same as a round-table. In a directed net, you wait for net control to call you and you don't talk to other stations unless told to. In a round-table, you pass the transmission to the next station in order. If you break the pattern, even with good intentions, the net slows down. So listen for the opening statement and any announcement about how check-ins will be taken. For traffic nets, it's also worth reading the standard radiogram format before you try to pass or receive anything. Count the words in the text accurately, because the check number is there so the receiving station can confirm nothing was dropped. Slow, clear delivery with phonetics for anything ambiguous will do more for a message than speed.
-
Building an HF shack around a 100 W rig: where should the money and effort go first?
On the rigs, the useful questions are how you operate and what band conditions you have, not which model is 'best'. The IC-7610 and K3S make sense if you work split, chase DX or contest and benefit from two receive paths. The IC-7300, FTDX10 and TS-590SG fit a single-operator station well. The FT-991A is attractive if you also want VHF/UHF in the same box, though it's a compromise at the extremes of dynamic range. The G90 and KX3 are for portable use or low power, where weight and current draw matter more than a big front panel. On band-pass filters, I'd say they solve a specific problem: strong out-of-band energy hitting a receiver, typically from another transmitter at the same site. They won't fix noise from LED lighting or a switching supply, and they won't cure common-mode current on the coax. If you're running one rig and one antenna, I'd diagnose the noise and the bonding first. If you're running two stations near each other, a BPF per radio is worth the cost, provided it's rated for the power through it. One more point on amplifiers. Set the drive so the ALC isn't doing the work. Check the amp's input SWR rather than assuming the rig's tuner has made it a perfect load, and keep an external tuner after the amp if the antenna needs one. A clean 100 W signal into an amp usually sounds better than a pushed 100 W with the ALC in the red.
-
POTA activation checklist: park references, 10 QSOs, spotting, logging and two-fers
For modes: CW and digital are often efficient with low power, and SSB tends to give more casual hunters a chance to call. If your signal is modest, a mode you're comfortable with beats a mode that looks theoretically better. Bring a backup, like a second antenna, spare coax, or a simple dipole, since a connector or feedline fault can end an activation faster than propagation does. For hunters, remember that a short exchange is fine. Give your call sign, the activator confirms it, and you're done. Don't hold up the line with a long chat while others are waiting. If you want credit for park-to-park, make sure you are clearly signing from your own park and giving the reference, and that the other station has copied it correctly. And if the activator is only a few QSOs short of the 10, a quick, clean call can help more than another long conversation.
-
Run vs. S&P, SO2R, and rate: how do you decide when to leave a frequency?
On SO2R, I'd focus on making the switching boring before making it clever. Keep the CQ message length and cadence consistent so you know when you have time to check the other radio. Use the second radio to look for a single clear target, not to scan the whole band. Then return to the first radio before the gap becomes obvious to callers. Equipment matters for this. A proper SO2R interface or controller with transmit lockout, plus band-pass filters and stub filters where needed, helps prevent receiver desense and the dreaded double-key. Antenna separation and band choice also decide how well it works. Running two radios on adjacent bands with antennas close together is a harder problem than using widely separated bands. Antenna choice for contesting is usually about getting a reliable signal on the bands that matter most. A few well-matched antennas with good switching often beat a large number of marginal ones. As for fatigue, an SO2R operator should probably plan more breaks, not fewer, because the mental load is higher than with one radio. Dropping back to a simpler single-radio approach late in the event is perfectly reasonable if your accuracy starts to slip.
-
On-air habits that make a band easier to share: CQ calls, breaking in, nets and handling interference
On nets, the biggest difference between a smooth one and a chaotic one is how well net control sets expectations at the start. A good opening states the net name, the purpose, the frequency or repeater, the type of net (directed, where net control calls on everyone, or open), and how check-ins will be taken. Then it tells people when to speak. For example, "Priority or emergency traffic first, then check-ins by callsign suffix." If you are checking in, listen to that opening first. Do not transmit just because you heard a pause. When you check in, give only what net control asked for. Many nets accept the suffix of the callsign, using phonetics, and then the full call if requested. Others may want a name and location. If you have traffic or a question, say so briefly and let net control decide when to take it. Wait to be recognized, keep your transmissions short, and do not hold the mic for a long story. A net is a shared tool, and a busy net with fifty check-ins cannot afford several minutes of chat from one station. If you are net control, keep a log, repeat callsigns back so everyone knows they were heard, and use a consistent routine. Acknowledge late check-ins, then close the net by stating when it ended and thanking participants. Do not assume a new operator knows the procedures. A short, friendly reminder of how the net works can go a long way and may keep them coming back. One more point on shared frequencies: no one owns a frequency, even if a net meets there every week. If a net is running, the courteous move is to be aware and avoid stepping on it. If you find a net on a frequency where you were planning to operate, move rather than argue. That works in both directions: nets should also be willing to yield when they are not the only users, or to ask others to adjust if there is a legitimate reason.
-
Standard NATO/ITU phonetics or "ham phonetics" on the air? How do you handle callsigns, names, numbers and nets?
On the practical side, a few points for your guide: Callsigns. Give your call phonetically at least once per exchange, and in a busy or weak-signal situation, every time. Pace matters more than speed: say each element cleanly and don't run them together. If the other station gets one character wrong, correct only that character instead of respelling the whole call: "the second letter is Sierra, S-I-E-R-R-A." Partial repeats help, but don't send half a call and assume the other person knows the rest. Names and places. Spell the unusual part, not the whole word. "Name is Joe, Juliett Oscar Echo" is useful. Spelling "Boston" probably isn't, but a small town or an odd surname deserves it. For grid squares, treat them like characters: FN31 is Foxtrot November three one. Mixing letters and digits quickly is where mistakes creep in. Numbers. Amateurs normally say digits individually and plainly. "Niner" for nine is common because it can't be confused with the German "nein" or with "five" at a distance. The formal ITU numerals (Nadazero, Unaone, Bissotwo and so on) exist in the Radio Regulations but are very rarely used on ham bands. Say "zero" rather than "oh" if there might be confusion with the letter O. For a slash in a callsign, you'll hear "stroke" or "slash", and "portable" or "mobile" for the suffix meaning. Prosigns. On CW these are real prosigns: AR (end of message), SK (end of contact), BT (break or pause), KN (go ahead, named station only). On phone they don't exist as such; you use prowords like "over", "clear", "break" and "say again". One small tip: "over and out" is contradictory. "Over" means you expect a reply, and "out" means you don't, so pick one. Difficult conditions. Slow down, don't shout, keep your voice steady, and use phonetics only where it's ambiguous. Letters like B, D, P, T, V and M, N, S, F sound alike through noise, and those are the ones to spell out first. Don't speak faster when the band is crowded; that makes it worse.
-
How do you separate real ham radio news from hype? A practical checklist for rigs, firmware, band openings and rule changes
For gear, I'd split it into three tiers: announced, shipping, and proven. A radio that's announced only has a price and a promise. Once it's shipping, you start seeing real-world quirks like menu oddities, fan noise, or a buggy first firmware. Proven comes after enough owners have run it through contests, digital modes and portable use that the problems have surfaced and been patched. On firmware, the biggest practical tip is to read what the update doesn't mention. If a release changes CAT behavior, WSJT-X, N1MM+ or your rig-control software might need a configuration tweak. Also save your settings to a card or file if the radio supports it. Some radios reset menus or memories during major updates, and a recent backup turns that from a mess into a minor annoyance. For antennas, be skeptical of gain claims with no pattern plot or no stated ground assumptions. Compact multiband verticals and loops can work fine, but a number like 'covers 160 to 6 meters' says nothing about efficiency on each band. Look for modeling, field-strength comparisons, or at least a clear description of how the numbers were obtained.
-
Making SET and Field Day Count: Scenario Ideas, Net Scripts, Message Handling and Served-Agency Lessons
On message handling, I'd argue the most valuable drill is also the plainest: have several people originate formal messages from scratch, pass them by voice to a relay station, and then compare the delivered text against the original word for word. The errors are usually predictable. Numbers get transposed, names get misspelled, and operators "clean up" the text without realizing they changed the meaning. The check count catches some of these, but not all of them. One suggestion for net scripts is to build in a deliberate pause after the call for priority or emergency traffic, long enough that a station with a weak signal or a slow microphone can get in. Net control operators who rush through that part can easily miss someone. I'd also keep a separate, simple scratch format for tracking who has checked in, who has traffic, and who is tasked where. Even a basic table on paper beats trying to remember it all, especially when the net runs for hours and control rotates. For Field Day, a traffic table that handles a few formal messages and a few plain-language welfare messages is a good addition because it exercises both forms. It teaches operators to match the format to the situation instead of using one style for everything.
-
Getting from 5 wpm to 20 wpm: plateaus, head copy, drills, and what's worth practicing
On decoding by ear versus software: they are useful for different things. Decoders like fldigi's CW mode or those built into some rigs and apps do reasonably well on clean, steady, machine-sent code. They fall apart on fading, noise, irregular spacing, and hand-sent code with variable weighting. Many operators use them as a cross-check on callsigns they are unsure of, but if you lean on the screen while learning, you tend to look instead of listen, which defeats the point. A reasonable rule is to copy first, then check. For sending, a few settings are worth thinking about. Standard timing is a dah three times a dit, with one dit of space inside characters, three between characters, and seven between words. Most keyers default to that, and heavy weighting makes your code harder for others to read. Set the keyer speed to about the speed you can comfortably copy, so you do not end up sending faster than you receive. Otherwise the person answering will probably send back at your speed and you will be lost. On paddles, iambic mode A versus B is mostly a matter of what you learned on. Mode B adds an extra element when you release the paddles after squeezing, and mode A does not. If you notice stray dits or dahs at the end of letters like C or K, check the mode and paddle tension before blaming your fingers. Contact spacing and tension that are too tight or too loose are common causes of sloppy sending. Adjust gradually and give yourself a few sessions to adapt. For on-air practice, slow-speed nets and CW practice sessions are a good step between drills and real contacts, since the exchanges are predictable and the other operators expect beginners. After that, relaxed contest exchanges (short, formulaic, repeated) are a good bridge. You hear the same structure over and over, so it builds confidence faster than rag-chewing does. Check each event's own rules and current schedule from its sponsor, because those change.
-
Getting my first ham license: how do I find a test session, what does the FRN do, and what should I study?
On studying and what to do after you pass: Study resources. The Technician exam has 35 multiple-choice questions drawn from a public question pool, and you need 26 correct to pass. One thing to check is that the pool is revised on a cycle of roughly four years. Whatever book or app you use, confirm that it matches the pool in effect on your exam date. Old books are cheap for a reason. HamStudy is a good fit for the questions themselves. It uses spaced repetition, tracks which topics you keep missing, and has a practice-exam mode laid out like the real test. The ARRL Ham Radio License Manual is a better fit if you want the reasoning behind the answers, such as why a 2 m repeater has an offset or what a dummy load is for. Many people use both: the book for understanding and the app for repetition. Free options exist too, including online practice exam sites and other study guides. Test tips. Don't just memorize letters. The pool is public, but understanding the concepts helps when a question is worded differently than you expect. Keep taking practice exams until you pass consistently with some margin, not just barely. Read each question fully, because wrong answers are often close to the right one. Review the topics that cost you points, usually electrical basics, Part 97 rules, and station safety. After you pass. Don't rush into a big purchase. A cheap handheld (HT) is a common first radio. Look up local repeaters in a directory like RepeaterBook, and note the frequency, offset, and CTCSS/PL tone for each one. Listen before you transmit. Check whether your local club runs a weekly net, since nets are a friendly way to make a first contact. Identify with your call sign as required. If you buy a radio you can program, CHIRP is free software that helps load repeater data. Club members will often help a new licensee set up their first radio, so ask around.
-
Keeping RF out of shack automation: ESP32/Pico nodes, CAT, antenna switches and SWR sensing
I'd emphasize the power supply as much as the cables. A cheap switching wall adapter can inject noise that gets blamed on the Pico or the sensor board. Try powering the node from a linear regulator or a well-filtered 12 V source, add bulk capacitance plus ceramic decoupling at each board, and keep the Si5351 and any RF detector on a quiet, locally filtered rail. For the ESP32 specifically, Wi-Fi transmit bursts cause current spikes that can disturb nearby analog circuitry. If the SWR readout is jumpy, test with Wi-Fi off, or move the ADC job to an external converter such as an ADS1115 over I2C, and keep that I2C run short. If the sensor is at the antenna tuner, think about sending digital data over a shielded cable rather than a long analog line.
-
Technician heading for General: how would you split up study time for Element 3?
Start by looking at how the pool is divided into subelements. Each exam is built from a fixed number of questions per subelement, so you can see which sections give the most points. Check the current pool's counts on the NCVEC site or in whichever study guide you use, because the pool gets revised on a multi-year cycle and you want the one in effect on your exam date. Commission's rules, operating procedures, and amateur practices make up a big share. Those are the most learnable points, so don't put them off. A workable split for a few hours a week over about eight weeks: Weeks 1-2: rules and operating procedures. This covers privileges by class, control operator responsibilities, third-party traffic, station identification, power limits, and which emissions are permitted where. It is mostly memorization, but if you learn the reasoning, like why certain segments are CW/digital only, you will retain it better than with flash cards alone. Weeks 3-4: electrical principles and components. Ohm's law, power calculations, resonance, reactance, decibels, and basic circuit behavior. Do the calculations by hand instead of memorizing answer letters. Roughly: 3 dB is double the power, 6 dB is about four times, and 10 dB is ten times. Questions get reworded, and if you understand the formulas, a changed number won't throw you off. Weeks 5-6: propagation and antennas (see below), plus signals and emissions. Weeks 7-8: practice exams, timed, and a focused review of weak topics. Take a new practice exam each session and keep a log of which subelements you miss. Don't keep retaking the same one until you've memorized it, because that tells you nothing. On question 5: any licensee can apply for a vanity call, and the available call formats depend on your license class. The rules on this change occasionally, so read the current FCC vanity call sign guidance and the question-pool material on call sign formats. It isn't a reason to delay the exam. Upgrading itself doesn't require a new call, and your existing one stays unless you apply for a new one.
-
Go-kit sanity check: what's in your grab-and-go, and what have you stopped carrying?
Good breakdown. One thing I'd add to the power section is to label everything with its role and test it as a system, not as individual parts. A battery, a charge controller, a fuse block, and a rig can all test fine on the bench, then fail when you connect them because of a bad crimp, an undersized wire, or a polarity mix-up. Using Powerpole connectors with the same orientation everywhere helps, and so does a short pigtail with an inline fuse on each device. Keep a simple voltmeter or a power meter in the kit so you can see what's actually happening instead of guessing. On the license-free side, I'd treat FRS and MURS as the family channel and keep ham for the people who are licensed. For non-hams, a printed card with the channel number, any privacy code settings, and a check-in time is more useful than a lecture on how the radio works. Whatever radios you choose, make sure they're set up the same way, because mismatched tones or channel numbers are a common reason for "it doesn't work."
-
Where do you draw the line between Pico, ESP32 and a Raspberry Pi in a shack automation setup?
On the audio question, ground loops and RF pickup are the most common reason a Direwolf setup decodes poorly or sends distorted audio. A cheap USB sound card plugged straight into the rig's data port with a long unshielded lead will often hum or pick up RF. Things that usually help are a 1:1 audio isolation transformer on both the RX and TX audio lines, a ferrite on the USB cable, and keeping the TX audio level low enough that the rig isn't overdriven. Many TNC problems are really level problems, since too much audio into a rig's mic or data input produces splatter and bad packets, even though the software is working correctly. If you use a CM108-style adapter for PTT, check which GPIO pin your particular adapter exposes, because the pin numbering and wiring differ between boards. And Wi-Fi or Bluetooth radios on the Pi can be disabled in software if you don't need them, which removes one more source of interference near sensitive receive audio.
-
Callsigns 101: sequential assignment vs. vanity, groups, club and special event calls, and what the FCC expects once you hold one
On club and special event calls, I'd add that people often assume a club call is a shared personal call. It isn't. The trustee is the named responsible party, so a club should think about who holds that role and what happens if the trustee moves away or becomes inactive. Having a succession plan written into the club's records is worth the effort. For special events, a 1x1 call sounds great, but the short-term nature means the planning matters: dates, operators, and QSL handling should all be settled before the grant arrives. Read the coordinator's current instructions instead of relying on a past event's write-up. Also, lookup tools are great for a quick check, but if a license status ever matters, like confirming an expiration or a trustee, use the ULS record as the source of truth.
-
APRS end to end: handheld beacons, Mic-E, digipeaters, a Direwolf iGate and what shows up on aprs.fi
Good overview. I'd add one thing about the iGate side that trips people up: gating is not "repeat everything." iGates are supposed to skip packets that already have TCPIP, TCPXX, NOGATE or RFONLY in the path, which avoids loops and respects stations that don't want internet exposure. On the internet-to-RF side, the common practice is to send only messages addressed to stations recently heard directly on RF at that iGate, not the whole feed. If your Direwolf config sends everything to RF, you're adding load for no benefit. For a first iGate I'd run receive-only for a week and compare against what aprs.fi shows for your callsign. If you hear stations that never appear on the map, check the login, the passcode and whether the server accepts you. If they appear but with weird positions, that's a decoding or source-station problem, not an iGate problem. The raw packet view on aprs.fi is the quickest way to tell. It shows the path, so you can see which digipeater or iGate handled the packet. Be aware that Direwolf's own logs show what your station heard, while aprs.fi shows what APRS-IS received, and those can differ. On the path question: I'd say keep it short and test with the minimum before extending. In sparse areas WIDE1-1,WIDE2-1 is reasonable. In dense areas, ask local operators what the digipeaters are set up for. Some regions have their own recommendations, and the generic guidance isn't always the best fit.
-
Keeping DXCC, WAS, WAZ and the rest straight: what counts, what doesn't, and where credits go missing
The most common LoTW problem is a mismatch in the details, not the other station refusing to upload. LoTW needs both sides to match on band, mode group and time, and the time tolerance is only about 30 minutes. A bad clock, a wrong date near 0000Z, or a mode logged as SSB when the other side logged it as a digital mode can leave a QSO showing as unmatched. On your own side, check the station location in TQSL. If the DXCC entity, CQ zone, ITU zone, grid or state or county data is wrong, the signed upload will carry those values forever. That matters for WAS and WAZ credits especially, because the awards read the location data, not just the callsign. For deleted entities, remember that the QSO date is what counts. Those contacts should be treated as historical. I would keep them in the log with their original entity names and not rewrite them to match today's list, since that is what lets the QSO keep its basic-award value.
-
Remote station design: control paths, latency, security and the rules (IC-7610/RS-BA1, SCU-LAN10, Flex, RigPi, Kiwi/WebSDR)
On latency, it helps to split the problem into the radio's response and the human feedback loop. Tuning feels sluggish when the panadapter or waterfall data takes a long path, even if the audio is fine. A Flex-style SDR, where the client does the DSP, can feel snappier on tuning than a CAT-polled traditional rig, but only if the bandwidth for the panadapter stream is there. If your upstream at the station is thin, drop the panadapter rate and the audio bit rate before blaming the VPN. For CW, the local-keyer approach in the opening post is the right one. If you must stream keying, expect to slow the speed down and accept sloppy weighting, or use a keyer at the station with a text interface. For a remote Pi-based setup, I'd run the logging and digital software there as well. A single remote-desktop session into the Pi also gives you fewer moving parts to troubleshoot than separate audio, CAT and PTT streams. One useful test is to have a KiwiSDR or WebSDR near your station, or at a distance, receive your remote signal and compare it to what you monitor. That catches overdriven audio, a stuck compressor setting and a mis-set TX bandwidth, which are easy to miss when you only hear a processed return stream. Just remember that the Kiwi's own delay means you can't use it to judge round-trip timing.
-
Combining POTA and WWFF: KFF references, the 44-QSO target and keeping the logs straight
On the air, I would keep the calling simple. On phone, something like "CQ POTA and WWFF" followed by your callsign and both references, repeated now and then, is easy for hunters to copy. On CW, alternating "CQ POTA" and "CQ WWFF" works if the pileup is thin. Since hunters from the two communities follow different spotting channels, make sure you are spotted in both places: POTA spots go through the POTA site, and WWFF spots use WWFF's own spotting tools and the usual cluster networks. A spot in one place will not necessarily show up in the other. Because of the higher target, plan for band and mode variety. Working the same station on a different band is generally fine for the count, but check the current rules rather than counting on it. Running some CW or digital alongside SSB can help fill the numbers when one band goes quiet. Keep a paper tally as a backup, and note your UTC start time. For hunters, KFF references are worth watching for if you collect WWFF awards or diplomas. Award levels and endorsements are defined by WWFF, so read the current award rules and look up your national program's pages before you decide what to chase. Hunters need only a clean contact and the right reference in the activator's log, so it helps to confirm the reference back with the activator when you are unsure. One more tip: check the boundaries. A park or reserve might be listed under one reference while the area you are standing in belongs to another designation, or sits outside the boundary altogether. Look at the official boundary map and any posted rules on antennas and operating before setting up.
-
SSB audio chain: mic gain, ALC, compression, EQ and bandwidth for clean, readable signals
One addition on the ALC point: because meter scales differ between radios, use the manual as a starting point rather than trusting a universal 'no ALC' rule. Some rigs show ALC movement on every peak even when the output is clean, and others begin to distort before the meter looks alarming. The reliable test is to feed a dummy load, watch the output on a wattmeter, and check the transmitted signal with a second receiver or SDR. If you don't see output climbing in step with mic gain at the top end, you are compressing or limiting in the wrong place. I would also keep separate memory profiles if the radio allows it. A DX profile with a narrower TX passband and moderate processing, and a ragchew profile with a wider passband and the processor off, are easier to manage than changing five menu items every time the band changes.
-
Building a Wire Antenna from Scratch: Wire, Insulators, Chokes, Feedline and Modeling Before You Cut
On the modeling side, the part that trips people up is believing the numbers to more precision than the model deserves. The main check I'd suggest is a convergence test. Double the segments per wire and see if the feedpoint impedance changes significantly. If it does, the model isn't settled. In EZNEC, also try the same antenna over a couple of different ground types, because feedpoint resistance and take-off angle for low horizontal wires change noticeably with soil conductivity and height. For a dipole at, say, a quarter wave or lower, the pattern is heavily dominated by height, which is why NVIS-style high-angle radiation is common on low 80 m and 40 m dipoles. For verticals, model the radials explicitly. A perfect-ground vertical model will show gain figures that real installations seldom match. Compare ground-mounted radials against elevated radials, and see how the efficiency estimate and feedpoint resistance change. In MMANA-GAL, remember that its wire loss and ground settings are separate from your insulation or velocity-factor effects, so you will usually still end up trimming the real antenna. Use the model for choosing the structure, spacing and approximate dimensions, then use the analyzer to find the final length. If the real antenna resonates far from the model, check for nearby metal, coax routing, an uncorrected end effect from insulators, and whether the feedline choke is actually working.
-
Run vs. search-and-pounce: how do you decide when a multiplier is worth leaving a good run frequency?
On SO2R, I think the most useful way to see it is as two jobs rather than two radios. Radio 1 is the run radio: CQ, log, repeat. Radio 2 is the search radio: it listens, checks the bandmap, and calls only when it finds a mult worth calling. The aim isn't to make every QSO faster. It's to use the dead time between CQs to do the S&P work for free. That only pays if the run radio's CQ cycle gives you a listening gap, so message timing matters. A CQ that's too long wastes the gap, and one that's too short makes you impatient. Hardware tends to limit the benefit more than skill does. If both radios are on the same band, or on bands where harmonics land in each other's passband, receiver overload and key clicks make the second radio useless. Band-pass filters, stub filters, separate antennas, and physical spacing between antennas all matter. If you aren't sure whether you'll tolerate the setup, test it by transmitting on one radio and listening on the other across your usual band pairs before the contest. The worst time to find out is Saturday evening. On antennas: a single good antenna per band that you can point or switch quickly usually beats a larger, harder-to-manage system. For the run radio, a strong signal in your main target direction matters most. For the search radio, receive performance is often more important than transmit gain, so a decent receive antenna or a simple second antenna can help a lot. If you stack or use multiple yagis, be sure you can switch between them without delay, because every extra second spent switching comes out of your hunting time. Last, fatigue. Many people underestimate how much rate falls in the last third of a long contest, mostly through missed calls, wrong exchanges, and slow decisions. Plan rest periods before the contest and treat them as part of the strategy. Some rules also cap operating time or require minimum off periods for certain categories, so check the current rules for your contest. Meals, water, and a few planned breaks usually do more for your final score than an extra hour of tired operating. How do you handle the transition to SO2R? Do you start with the second radio only for finding mults, or do you try for simultaneous run-and-call from the beginning?
-
Prepping for the Technician (Element 2) exam: how to use the question pool without just memorizing letters
On question 1: the exam pulls one question from each question group, and the groups are not spread evenly across subelements. The FCC rules subelement (T1) contributes the most questions, and a few others contribute only two or three. So it makes sense to put extra time into the rules, operating procedures, and safety material, because that material is mostly plain reading and not calculation. Still, don't skip any group. A skipped group is one guaranteed miss, and you can only afford nine misses. For practice tests, a workable pattern is to read a chapter or section of a study guide, then drill only that subelement until you can explain why the right answer is right. Save full 35-question mock exams for the last stretch, when you want to check timing and see which groups still trip you up. If a practice tool shows explanations, read them even when you got the answer right. Question wording within a group varies, and understanding the concept protects you if the exam shows a different question from the same group than the one you drilled. One caution about memorizing letter positions: most exam sessions and software shuffle the answer order, so "it's always C" doesn't hold up. Memorize the content instead.
-
Building a ham go-kit in layers: what goes in the grab-and-go, what stays in the vehicle, and what stays home
For the question about when the repeater is down: I'd treat simplex as the default and repeaters as a bonus. Pick a primary and backup simplex frequency in 2 m and 70 cm for your group and agree on them ahead of time, with a time to listen. National calling frequencies like 146.520 MHz are fine for initial contact, but they may get busy, so a plan should say where to move after you connect. Remember that range on simplex depends heavily on terrain and antenna height, so a few feet of elevation or a better antenna can matter more than extra watts. It is also worth separating what you do as a ham from what you ask family to do. Family members without licenses can use FRS or GMRS (with the appropriate license for GMRS) for short-range contact around the neighborhood, while you use ham frequencies for wider coordination or for relaying information to a net. Keep traffic simple and plain language, and if you volunteer with a local emergency communications group, check their expectations for training and check-in procedures, because they differ from place to place.