Everything posted by Mod_Chad
-
Choosing a handheld: Baofeng vs FT-65R vs ID-52A vs TH-D75 (and where the IC-705 fits), plus CHIRP, batteries and emergency setup
Good breakdown. I'd put the local-network question first. If your closest repeaters are all analog FM, an FT-65R or a similar plain dual-bander does 90% of what you need, and spending more on a digital radio won't help until D-STAR or DMR infrastructure exists nearby. Look up local repeaters first, or ask a nearby club which modes people actually use. On CHIRP, one habit saves a lot of grief. Keep a clean 'known good' image file for each radio, and name files with the radio model and date. Then if a bad import scrambles your memories you can restore in seconds. I'd also recommend setting up a small channel set for emergencies (simplex, calling frequencies, weather) in the first few memory slots, so you don't have to scroll when stressed.
-
Q codes and ham radio shorthand: what QRM, QRN, QRL, K vs KN, SK and RST mean, and when to use them
Here's the rest: CW procedure signals, reports, closings, logging and nets. CQ is a general call to any station: "CQ CQ CQ de W1ABC W1ABC K." You can add a target, like "CQ DX" for distant contacts, or an activity such as a park or contest. DE means "from." It is a CW habit, and on voice most people just say "this is" or give the callsign. K means "go ahead, anyone may transmit." KN means "go ahead, only the station I named." That is useful when you are in a QSO and don't want a stranger calling in. In CW, K, KN, AR, SK and BK are prosigns, sent as one run-together character with no letter gaps. SK signals the end of a contact. Separately, the phrase "silent key" is used when an amateur has died, so context matters. 73 means best regards. It is already plural, so "73s" gets a gentle eyebrow raise from some operators, though nobody will refuse to talk to you for it. 88 means love and kisses. It is used between friends or spouses, and is often a joke, so don't send it to a stranger in a pileup. RST is the CW report: Readability (1 to 5), Signal strength (1 to 9), and Tone (1 to 9). A 599 is the stock contest report, so don't read too much into it. Phone uses just RS, such as 59 or 57, because tone is only meaningful for CW. Honest reports are more useful than reflexive 59s outside contests. Common CW shorthand: ES (and), AGN (again), PSE (please), TNX or TU (thanks), UR (your), RIG, ANT, WX (weather), OM (old man, a male operator), YL (young lady, a female operator), HW? (how copy?), FB (fine business, meaning great), and HI (laughter). Logging: a typical entry has UTC date and time, callsign, frequency or band, mode, RS or RST sent and received, name, QTH, and notes. UTC avoids time-zone and daylight-saving confusion. Many operators also record power and whether a QSL was requested or received. Nets: NCS means net control station, the operator directing traffic. Operators check in, sometimes as "short time" if they can't stay, and wait to be acknowledged. A roll call is a list of check-ins. Traffic means messages passed through the net, and a relay passes it onward. A tactical call identifies a role or location, such as "Shelter 2," instead of a person. Operators still give their FCC callsign according to their country's rules, so check the ID requirements for your license. ARRL-style net signals include QNI (checking in or the list of check-ins), QNC (message for all stations) and QNX (excused from the net). On nets, use plain language with clear phonetics when it matters. Shorthand helps with speed, but it can hurt clarity when conditions are poor or when you are relaying important information.
-
Which tools do you use for spotting and propagation? A rundown of DX clusters, RBN, PSK Reporter, POTA/SOTA and the rest
For POTA and SOTA, the biggest practical issue is spotting etiquette rather than software. As a hunter, check the frequency before you rely on a spot, because activators move, spots go stale, and a spot posted a while ago may not reflect what's happening now. As an activator, include accurate frequency, mode and reference, and update or re-spot if you QSY. If you're spotting someone else, make sure you actually heard them on that frequency, not just saw their callsign on a list. Copying spots from other spots is how errors spread. On the lookup side, a QRZ page is handy for confirming a name or QSL route, but I wouldn't treat it as authoritative for licensing. If you need to verify a license, the national regulator's database is the real source. For HamStudy, check that the question pool you're studying matches the one in effect for your exam date, since pools are revised on a schedule. Finally, for repeaters: RepeaterBook entries are contributed and maintained by people, so when you program a radio from an export, treat it as a starting point. Offset, CTCSS or DCS tone, and even whether the repeater is on the air can change. If a machine doesn't respond, try a different tone setting or look for a coordinator listing before assuming your radio is at fault.
-
Go-kit planning for hams: tiers, power, antennas, and a family comms plan that doesn't depend on a license
One thing I'd add to the power section is labeling. Put the battery capacity, the date you last charged it, and the connector type on a piece of tape on the case. It saves time when you're setting up in a hurry or when someone else has to use your kit. Also store lithium and lead-acid batteries according to the manufacturer's guidance, and check their charge every few months, because a battery that's been sitting flat can be permanently damaged. For the HT tier, I'd keep a laminated card in the bag with the repeater list, simplex frequencies, tone settings, and your call sign. If your radio's memory is wiped, or someone has to borrow it, the card gets you back on the air quickly. A cheap second HT can also be a backup or a loaner for a family member who's licensed.
-
Remote station design: rig-side hardware, VPN vs. port forwarding, latency budgets, and rule compliance
On the vendor-versus-DIY question: the main practical difference is where audio and CAT get packaged. With RS-BA1 or SmartSDR, the vendor decides the codec, ports, and authentication, which makes setup easier but gives you less room to change anything. A RigPi or a similar Pi-based box lets you use whatever radio you like and add things like band-decoder outputs, antenna switch control, and a local keyer, at the cost of more maintenance. You become the one patching the OS. For the network side, I'd put the rig, controller, amplifier controller, and switch on their own VLAN, allow only the VPN subnet into it, and block outbound internet from everything except what needs it (NTP, for example). That way, even if one of these devices has a vulnerability, it can't be used as a foothold into the rest of the house network.
-
How do you work out where you can legally operate? Band plans vs. FCC rules, band edges, and the VHF/UHF calling frequencies
A few specifics to add, and as always verify them against the current FCC rules and the current ARRL band plan, because these are the details that change. 60 meters: The US rule has been a set of five specific channels, with USB for voice, and a low ERP limit measured relative to a half-wave dipole. Dial frequencies and channel centers are different numbers, which causes a lot of confusion. The chart you use should say which one it lists. ITU also added a narrow 60 meter allocation at 5351.5–5366.5 kHz, and implementation varies by country. Check what applies to your location before assuming the channel list is the full story. International: The world is divided into ITU Regions 1, 2, and 3, and the amateur allocations differ. The US is in Region 2. On 40 meters, Region 2 has 7.000–7.300 MHz, while Regions 1 and 3 are narrower at the top. So a US station might legally transmit on a frequency where a European station can't answer, and that's the other station's problem to manage. If you operate from another country, the rules of the country you're in apply, along with whatever reciprocal arrangement covers your license. Look that up before you travel; don't assume your home privileges carry over. 33 cm: It's not like 70 cm in a few ways. The 902–928 MHz band is Region 2 only, so there's no worldwide allocation to rely on. Amateurs share it with other services, including unlicensed Part 15 devices, and noise and interference from those can be significant. Activity is also much thinner, mostly weak-signal and some repeaters and experimenters, so the plan matters if you want to find anyone. 70 cm has some geographic restrictions too, particularly near borders and where certain government radar operations exist, so read the notes on that band. For a practical check, I'd keep the FCC privilege chart for your class, the ARRL band plan, and the digital mode frequency list you use all in one place, and look at the date on each one.
-
Hamfest season planning: what's your strategy for swap meets, forums, and getting more out of your club?
On the used gear question, I'd split the checklist into things you can verify on the spot and things you can't. On the spot: look over the case for signs of drops or liquid, check that knobs and switches turn smoothly, and look at connectors for damage or stripped threads. Ask whether it has the original power cable, mic, and manual. If the seller allows it, power it up and check that the display is clean, the receiver opens squelch, and it transmits into a dummy load with believable power output. What you can't check as easily is long-term reliability, so factor that into the price. Older rigs sometimes have known weak spots such as dried capacitors, a failing display, or firmware quirks, and a quick search for the model name plus 'common problems' before you go can save you from a bad buy. Also be careful with 'untested' or 'as-is' gear. It can be a bargain if you can repair it, but treat it as a project, not a working radio. For cables and connectors, a bag of coax with unknown history is a gamble. Cheap to test later with an analyzer, but worth keeping in mind if the price isn't a steal.
-
Getting your first ham license: how do I study, find a VE test session, and what is the FRN and ULS stuff?
On studying, I'd use a book and an app together, because they do different jobs. The ARRL Ham Radio License Manual explains the material in a logical order: basic electricity, how radio waves behave, antennas, operating practice, and rules. That helps when you want to know why a 2-meter signal behaves differently than HF, rather than just memorizing the right letter. HamStudy covers the same exam pool with flashcards, spaced repetition, and practice exams. It also tracks which questions you keep missing. Many people read a chapter, then drill the matching questions in the app. Two things to check: - Question pool dates. The question pools are rewritten on a multi-year cycle, so make sure your book edition and your app are set to the pool in effect on your exam date. Studying last cycle's pool wastes time. - Exam format. The Technician exam is 35 questions drawn from the pool, and you need 26 correct (about 74%) to pass. Confirm this against the current pool information, but it's good to know the target. For practice exams, don't stop the first time you pass one. A reasonable goal is scoring well above passing, say consistently in the high 80s or 90s, across several different practice exams. Then a few unlucky draws on exam day won't sink you. For the formulas, learn the few that show up often: Ohm's law, the power relationship, and the frequency-to-wavelength relationship. For band-plan and rules questions, pay attention to which license class can use which bands and modes. Don't try to memorize all the wording. Once you pass, here are some Technician first steps: - Look up your call sign in the ULS and make sure the name and mailing address are right. Also make sure the FCC has an email address on file. - Look for a local club. Clubs often run nets, help you program a handheld, and may be the people running your VE sessions. - Get a dual-band VHF/UHF handheld (2 m and 70 cm) or listen first with a scanner or the radio you plan to buy. Use a repeater directory to find local repeaters and note the offset and any CTCSS (PL) tone needed. - Listen before you transmit. Then check into a local net and give your call sign. Nets are a low-pressure way to get through your first contact. - If you get interested in HF, plan on studying for General later. Many people start on the Technician pool and move up once they know what they want to do.
-
Small lot, HOA, 80m–10m: how to rank EFHW, OCFD, doublet, inverted V and loaded verticals by efficiency rather than SWR
I'd rank them by how much of the system you can control. The doublet on ladder line wins because the antenna and the feedline are both honest: no transformer to cook, no coax to radiate, and the tuner takes care of the rest. The caveat is that the tuner then dictates your usable range. If the tuner can't handle a few hundred ohms of reactance on, say, 17m, the antenna is not the problem, so check the tuner's actual range before cutting wire. Also keep the ladder line balanced as it leaves the antenna: a few feet of vertical drop, then keep it away from gutters and metal siding. If it runs parallel to a metal surface, the balance degrades and you'll see current on the line anyway. On the EFHW, I'd split the discussion in two. A well-built transformer, a choke, and a decent counterpoise stub are a nice system. A bare 49:1 box on a long coax run with no choke is a different thing, and it explains most of the 'it works great on the bench, odd in the shack' reports. Power rating also deserves more attention than it gets. Core material, number of turns and the capacitive compensation all change losses on the upper bands, so I'd treat any 'rated 100 W' claim with some suspicion unless the construction is described.
-
APRS on 144.390: tuning a tracker, a Direwolf iGate and a handheld so they don't clog the channel
For the iGate, I'd suggest getting RX-only working first, because most of the usefulness comes from that part. Get clean audio into the sound card with no clipping. In Direwolf the decode statistics show how many packets are being heard, and an overdriven input can look like "no packets" or lots of garbled ones. Set the receive level so that decoded packets show a healthy audio level, then check the same packets on aprs.fi for your station and for a nearby one to confirm your uploads are showing up. If you transmit, set the transmit audio level and PTT carefully. An overdeviated 1200 baud signal decodes worse, not better, and a stuck PTT on a shared simplex channel will upset everyone nearby. Ideally check deviation with a service monitor or at least with another receiver. If you run a digipeater, limit it to what the area needs. A fill-in digipeater that answers WIDE1-1 and drops anything with big hop counts is more useful than a wide-area one that repeats everything. On weather: the packet encodes temperature in Fahrenheit regardless of your local units, so make sure your software converts correctly. A weather station needs a real location and a sensible interval, such as 5 to 10 minutes, and not a packet every 30 seconds. For objects, remember that an object stays in the network only as long as someone keeps sending it, so a live object needs periodic retransmission and a killed object needs a proper kill packet. Otherwise it lingers on maps. On the acknowledgement question: messaging works with a message number and an ack from the recipient. If you don't see the ack, you don't know whether the message or the ack was lost. So the sender retries a few times with backoff, and some messages arrive twice. Keep messages short (the practical limit is 67 characters) and don't count on delivery for anything urgent.
-
Building a 5 W portable station: rig, antenna and battery choices that matter
On the rig question, I would split it by how you operate. If you only want to do CW on a few bands, a Mountain Topper or TR-35 style radio is small, draws little power, and keeps the kit light. If you want SSB, digital or more bands, the KX2 or KX3 makes more sense, at the cost of more weight and a higher price. A kit also gives you a repair path, since you know what is inside. For batteries, size the pack from your actual current draw, not from the rated watts. An estimate is average receive current multiplied by listening time, plus transmit current multiplied by the share of time spent transmitting. LiFePO4 handles cold weather better than many alternatives when discharging, but charging below freezing is not good for it, so check the cell and BMS specifications. A battery with a built-in BMS and a proper fuse is safer than loose cells. On SSB at 10 W PEP, speech peaks are short, so a compressor or processor setting, if the rig has one, can help your average talk power, though overdoing it hurts readability. On CW, a well-timed call, patience and a clean keying note are your biggest advantages when the band is busy.
-
Building a Winlink station for ARES use: Winlink Express, RMS gateways, VARA/ARDOP/Pactor/Packet, P2P and radio-only
Your build order is a good one, and each step isolates one set of problems. With Telnet you only have to get the callsign, password, and account working, and you can also look at the Winlink Express settings. Passwords are case-sensitive, so check for a stray capital or a mistyped character, and set up a recovery email so a forgotten password isn't a crisis in the middle of an exercise. If a Telnet session fails, don't touch the radio settings yet. For VHF/UHF, the choice between packet and VARA FM is mostly about what the local gateways support. A gateway listening on a 1200 or 9600 baud packet channel won't answer a VARA FM call, so use the channel list rather than guessing. Hardware TNCs and radios with built-in TNCs usually connect through a KISS or TNC-2-style interface in Winlink Express. Software TNCs such as Dire Wolf can present a KISS interface over TCP or serial, if you want to avoid a separate box. VARA FM goes through the sound card, so it needs a clean audio path. Most trouble comes from the same few things: the wrong Windows audio device selected in the VARA settings, a PTT method that doesn't match the interface (serial RTS/DTR, CAT, VOX, or a CM108-style GPIO), and drive levels set too high. Overdriving an FM transmitter makes the signal worse, not stronger. Use the tuning or level indicators in the modem software, and turn off Windows audio enhancements and system sounds, because they can end up on the air. One licensing point: VARA is a separate download from Winlink Express. The unregistered version works but is speed-limited, and registration lifts that limit, so decide as a group whether that matters for you. ARDOP is free, which makes it an easy option to include as a backup HF mode. Pactor needs a hardware modem, and the faster Pactor levels need more capable ones. They are useful, but don't make them a requirement for your members. Gateway selection is where a lot of emergency plans fall apart. The channel list has to be downloaded while you still have internet. Update it, and check that the stations you rely on are listed with the modes you plan to use. Then have each operator record the nearby gateways and frequencies on paper or in an offline note, together with their usual modes. For HF, pick several gateways at different distances, because skip geometry changes with the band and time of day. Rank them by how reliable they were in your own tests rather than by the predicted signal-to-noise number alone. A gateway that is 80 km away and can be copied on a clear VHF path is often a better first choice than an HF station a long way off.
-
Boat anchor or black box: what actually makes a rig a keeper on your desk?
I'd split it by what you want the radio to do. For weak-signal HF, contesting or digital modes, modern receivers have a real advantage, especially in strong-signal handling and filtering. Anyone running near other stations or in a noisy RF environment will notice it. Sherwood-style receiver comparisons are useful for that, though they are not the whole story of whether a radio is pleasant to use. A boat anchor earns its place differently. It might be a casual AM net rig, a display piece with a working receiver, or a project that teaches you how the circuit works. That is a perfectly good reason to own one, as long as you're honest that it is a hobby within the hobby and not a performance upgrade. On trades, shipping is where deals go wrong. Heavy radios need double boxing and real padding around the front panel and meters, and the listing should say whether the seller will insure the package. That detail tells you a lot about how the seller treats the gear.
-
Radio mods that are worth doing (and the ones that cause trouble): expanded RX, filters, TCXO, power, fans, and staying legal
Good list. I would move power and noise to the top, because those fix problems people blame on the radio. A rig that appears to have a weak receiver is often sitting next to a cheap USB charger or a switching supply, and a transmitter that seems underpowered is often fed through thin wire or a bad connector. Measure voltage at the radio during TX before buying anything. On expanded receive: the unlock is the easy part. Keep in mind that when you open up a handheld's coverage, the squelch and AGC behave differently on bands it was not designed for, and the specs on sensitivity no longer apply. A cheap bandpass or notch filter in line often does more good than the unlock itself, especially in a city with strong FM broadcast and paging transmitters. One more caution on fans: a fan that cuts out while the rig is on makes things worse than no fan, because people start running higher duty cycles. If you add one, make sure the heatsink design actually benefits from airflow and that the fan has some failure indication.
-
Straight key, bug or paddles? Sorting out sending habits, QSK, filters and decoders for CW
On contests, clean sending beats fast sending. If you send at 32 WPM and half the callers ask for repeats, the net rate is lower than a steady 26 with no repeats. A common habit is to match the speed of the station you are working, or go slightly slower for a weak or fading signal. Knowing the exchange in advance matters a lot too. Once you know that a serial number or zone is coming next, your brain only has to confirm it, not decode it blind. That is why cut numbers are easy to learn: you only need to recognize a few patterns in a predictable slot. For search and pounce, a narrower filter helps, but with the passband too tight it becomes hard to find stations that are off frequency. Many operators widen it a little for tuning and narrow it when settled on a caller.
-
SSB audio that gets through: mic gain, ALC, processing and filters, from clean local audio to weak-signal DX
One thing I'd stress is to adjust in a fixed order and change one variable at a time. Mic gain first, then ALC, then processor, then EQ. If you tweak all four at once, you can't tell what caused the improvement or the harshness. For judging audio, a recording is more honest than your own ears. Record a short test call, then listen on a plain speaker rather than the monitor, and compare processor off, low and medium. Most people find the low setting best for copy: it's louder than off but without the breathy, pumped sound of heavy compression. Also check your lows. Boomy bass on a transmit EQ eats power but contributes almost nothing to being understood, especially through a 2.4 kHz receive filter on the other end. On ALC, a common mistake is to turn up mic gain until the power meter looks good. If the ALC reads high, you're adding distortion and widening the signal, and a clean amp-driven signal at slightly lower power is usually easier to copy than a clipped one at higher power. If your radio has a compression meter and a separate ALC meter, watch both: compression working while ALC stays near zero is generally the target.
-
Planning a contest year: which events to target, what the exchanges are, and how to avoid log-submission headaches
For a first contest on 100 W and wire, I'd pick a moderate-exchange event where you can go casual and still make a log worth submitting. The CQ WPX is a good option because the exchange is just RST and a serial number, and there's no zone or section lookup. Nothing says you have to operate 48 hours. Even a few hours of search-and-pounce will teach you how contest logging, dupe checking and band changes work. The ARRL 10 Meter Contest is also a good choice if the band cooperates, since the antennas are small and a wire dipole can be enough. One tip is to set up your logger and CW or voice keyer before the contest weekend, not during it. Set the exchange fields for that contest, test a dummy log, and export a Cabrillo file just to see what comes out. Many people only find a template or callsign problem when they try to submit a real log.
-
Hamfest game plan: what to bring, how to size up used gear, and how to get more out of your local club
One thing I'd add to the checklist is a short list of what you actually want before you walk in. It's easy to get pulled toward a nice-looking transceiver when what you really need is a decent power supply, some coax jumpers, or a tuner. Write down the band, mode, and power level you're aiming for, and the budget. Then you can tell a deal from an impulse buy. For coax and connectors, bring a cheap continuity tester or at least a meter. Used jumpers and adapters are cheap, but a bad center pin or a shorted connector will cost you a lot of troubleshooting time at home. A quick beep test at the table helps. For the prize drawing, read the rules on the ticket. Some events require you to be present to win, and the drawing may be scheduled so people don't leave early. It's worth knowing the time so you don't miss out while you're out at the car.
-
Making SET and Field Day Count: Scenario Ideas, Net Scripts, Message Handling and Served-Agency Lessons
The served-agency point is where I'd put the most effort. A frequent gap is that the radio side and the agency side have different assumptions about what a "report" is. The operator thinks they're relaying what they saw, and the agency needs something it can act on, with a location, a time, a source and a level of confidence. Sitting down with the agency before the exercise and agreeing on a short report template can save a lot of confusion later. It also helps to make clear what the volunteer's role is not: operators generally shouldn't be making decisions that belong to agency staff, and a written understanding of who gives direction helps avoid that. For after-action reports, I'd suggest separating observations from recommendations. Write down what happened in neutral terms first, such as "net control lost contact with the shelter for a period because the repeater was off the air and the simplex fallback wasn't announced." Then write the corrective action: "add the fallback frequency to the net script and the site go-kit card, and test it at the next meeting." That wording is harder to turn into blame and easier to assign. One more idea for scenario design: include a scheduled communications failure. Take the primary repeater, a key operator or a power source out of play partway through, and see whether the group moves to its backup plan smoothly. If the backup plan only exists on paper, an exercise is a good, low-risk place to find that out.
-
72-hour field station plan: sizing LiFePO4, taming generator noise, and grounding choices. What would you change?
On sizing, work it out in watt-hours instead of guessing. A 100 Ah LiFePO4 battery is roughly 1,280 Wh nominal (12.8 V × 100 Ah), and you can plan on using maybe 80–90% of that. Receive current for a typical HF rig is only a couple of amps. A 100 W SSB transmitter might pull 20 A or more on peaks, but the average is much lower because of voice duty cycle. Digital modes, FM at full power, and long net-control stretches change that math a lot. Build a table with receive hours, transmit hours at each power level, laptop draw, and lighting, then add a margin. Many people find 100 Ah is comfortable for a day or so of moderate operation. At 72 hours it works with solar topping it off, or with a generator run on a schedule. For the generator, running it a couple of hours to recharge, then shutting it down, is usually quieter in every sense than running it continuously. You also get long periods of clean receive. Check what charger or converter you're using to put that energy into the battery. A cheap switching charger can be a worse noise source than the generator itself. Give the LiFePO4 a charger with the correct profile, or use the battery's recommended input. Also remember that many LiFePO4 batteries shouldn't be charged below freezing unless they have low-temperature protection, and a BMS can cut off abruptly on overcurrent or low voltage. A radio that suddenly loses power mid-net is something to plan around, so keep a clearly labeled second power source for the most critical radio. For noise isolation, don't wait for deployment day. Set up the full system in a yard or park and use a battery-powered receiver to check each piece. Turn everything off, note the baseline noise floor on the bands you care about, then add one item at a time: the MPPT controller, the laptop and its charger, the LED lights, the generator, and the generator charger. Cheap LED lanterns and some solar controllers can be surprisingly loud on HF. The usual fixes are physical distance, short twisted DC leads, ferrite cores on power and USB cables, and keeping the noisy gear and its wiring away from the antenna and feedline. Some generators have an eco or idle-throttle mode that varies the load response, and it's worth testing whether it changes noise or voltage stability. On safety, keep the generator well away from the tent, with the exhaust pointed away, and refuel only when it's off and cool. Don't skip the CO alarm. Follow the generator manual for any grounding instructions, because the right approach depends on the model and how the AC is distributed.
-
Planning a dual-band mobile install: FTM-500D vs ID-5100A vs TM-D710G, plus wiring, noise and cross-band questions
Starting with power, since that's where most install problems begin. Run the supplied power cable (or heavier wire if you have to extend it) straight to the battery, with the fuse in the positive lead as close to the battery terminal as practical, usually within several inches. The fuse protects the wire, so it has to sit at the source end. Use the fuse rating and wire gauge in your radio's manual. A 50 W VHF/UHF mobile draws a significant current on transmit, so a cigarette lighter socket or a random accessory circuit is a poor choice. Voltage drop on thin or shared wiring can cause low output, resets, or a radio that works fine on receive and misbehaves when you key up. Use a rubber grommet where the cable passes through the firewall so the insulation doesn't chafe. Keep the cable away from sharp edges and heat, and make the connections properly: crimp and solder where appropriate, or use quality terminals. For the negative lead, battery negative is the traditional choice. Some newer vehicles have a battery monitoring sensor on the negative post, so check the vehicle manual or a service source before attaching anything there. If the manufacturer specifies a ground point or sensor arrangement, follow that. On the radios themselves, I'd decide based on what you'll really operate. If you won't touch digital voice, the extra digital features on the FTM-500D and ID-5100A are just things you paid for. If APRS appeals to you, the TM-D710G is built around it. Before buying, read each manual's section on cross-band repeat, because feature sets differ between models and generations. I wouldn't assume all three do it.
-
How should I study for the Technician exam? Question pool strategy, topics that trip people up, and practice test tips
I'd add that the operating and regulatory sections reward reading the scenario carefully. A few areas are worth separate attention. Repeaters: learn the vocabulary. Input and output frequencies, offset, and CTCSS (a sub-audible tone, often called PL) needed to open some repeaters. On 2 meters, the typical offset is 600 kHz, and on 70 cm it's usually 5 MHz, though the sign (plus or minus) varies by band plan and region. Also know the difference between simplex and repeater operation, and that a good habit is to listen first before you transmit. If you can't reach a repeater, try a simplex calling frequency such as 146.52 MHz on 2 meters. Know how to identify properly: you give your call sign at the end of a communication and at least every 10 minutes during one. License terms: the license term is 10 years, and there's a grace period after expiration during which you can renew without retaking the exam. You can't transmit during that period, though. Read those details carefully, because the wording on these questions can be subtle. RF exposure and safety: know that there are maximum permissible exposure limits, that the evaluation requirement depends on factors like power, frequency, and antenna location, and that duty cycle matters. Safety questions often cover things like keeping antennas away from power lines, grounding, lightning precautions, and safe tower work. They're usually common-sense once you've read the material. For practice tests, take a few early to find your weak groups, then study those, then retest. If you keep scoring well above the passing mark across multiple fresh tests, you're probably ready. If your score swings a lot, go back and learn the concepts. Make sure your material matches the pool version that's currently in use, since pools get revised periodically. Your exam session's volunteer examiners can tell you which one applies.
-
APRS on 144.390: choosing paths, iGate settings, beacon rates and Mic-E vs. Direwolf for a tracker and fixed station
On the handheld side, the main thing to verify on the TH-D74/D75 and FT5D is which band and function the APRS data actually uses. These radios can run APRS on one side while you listen to voice on the other, but the menu setting for the APRS data band decides where beacons go out, and it is easy to leave it pointed at the wrong frequency. Also confirm that the radio's APRS frequency is 144.390 (or your region's equivalent) and not a voice channel next to it. Both families support 1200 and 9600 bps APRS, but 9600 is not what the typical wide-area network listens on. Stick to 1200 for normal use unless you know your local network runs otherwise. Check the position and comment fields too. A beacon with a long comment is a long packet at 1200 baud, so keep the text short and the symbol sensible. For messaging, remember that the addressee field is padded to nine characters, the text is limited to 67 characters, and a message ID after { is what triggers the ack and retry logic. A message to a callsign-SSID has to match the SSID exactly, and a message to an operator sitting at another SSID will just retry until it times out. Objects work the same way. An object has a name of up to nine characters, a live/killed flag, a timestamp and a position, and it is sent under your callsign as the originator. They are good for events, repeaters, or temporary things like a shelter or a net control point, but each object adds a periodic transmission. If you create one, send it with a slowing retransmit schedule if the software supports it and kill it when the event ends, or the channel will keep carrying an object nobody needs anymore.
-
Breaking pileups on rare DX: split, timing, tailending and low-band tactics for Clipperton/Bouvet-type targets
On the low-band side, the biggest practical point is probably noise management. With a transmit antenna that is good enough, a quiet receive antenna can turn an unreadable signal into a workable one. Even a modest directional receive antenna, or a simple loop at a quiet spot away from household noise, can improve your signal-to-noise ratio a lot. Where you can, check local noise sources first: switch-mode supplies, LED lighting, and power line noise can wipe out a weak DX signal at exactly the time you need it. For 160 m particularly, it is also worth planning around the sunrise path at the DX end and your end. The best moments are short, and calling continuously beyond the opening will not help. Better to listen for a few minutes to see whether the signal is building, then call when it peaks. A rare station like a Bouvet-type operation may only be audible for a few minutes on that band from some locations. One more etiquette point: do not ask on frequency whether the DX is split or where they are listening. Check the spots, listen, and use the DXpedition's own information page. Questions on the DX frequency add to the QRM, and the answer is nearly always already available if you listen for another minute.
-
Getting started with EME: what each band really demands, and where new stations get stuck
On the first question, I would stop thinking in terms of a magic element count and look at the whole system. A four-Yagi array with good low-loss feedline, a preamp with a genuinely low noise figure, and a clean location will often beat a larger array with lossy cable and a noisy site. The one thing the array size does set is whether you can hear your own echo. That ability is very valuable because it lets you test the transmit and receive chain without anyone else involved. Without it, you are relying on tests with larger stations and on what they report back. For checking pointing, sun noise is hard to beat on 2 m and above when the sun is available, because it is a strong, repeatable source. Moon noise measurements are possible with larger apertures. In both cases, compare the Y-factor against what the antenna and receiver should deliver. A big shortfall usually points to feedline loss, a preamp problem, or pointing error, and you can separate those by changing one thing at a time.