Everything posted by Mod_Mike
-
From FM birds to linear: how to structure your first month of satellite operating (Doppler, tracking, antennas, QO-100)
One practical suggestion for the single-radio problem: before a pass, decide in advance what you will do about Doppler instead of improvising. On FM, a typical routine is to set the uplink a little off nominal at AOS and move in steps as the pass develops. Having a printed or on-screen table of the frequency versus time (Gpredict can show this) helps. Don't be discouraged if you have a lot of trouble with your first passes, because the tuning, antenna pointing and logging all happen at once. A very common beginner mistake is to spend the whole pass fiddling with the VFO and never actually pointing the antenna correctly. Another thing: write down the elevation and azimuth at AOS and LOS and where the bird will be at maximum elevation. On a low pass, buildings and trees matter more than antenna gain. A mediocre pass from a clear horizon often beats a better pass from a bad location.
-
Repeater basics that trip people up: offsets, tones, linking and etiquette (what would you add?)
On linked systems, I'd stress that a linked repeater has a longer pause before someone can answer, and another node may be transmitting to a different part of the network. Wait a beat after you unkey and again after the courtesy tone before talking again. Don't transmit over a net or a call you can't hear, since other nodes may be carrying it. Announcing the callsign of the person you are trying to reach helps because the audience could be across several systems. On D-STAR and Fusion, reflector and room connections can change who hears you. Before a long conversation, ask whether the system is connected to a reflector or room. The same goes for AllStar and EchoLink nodes: if the repeater is linked to a node or conference, say what you want to do before you start. In many areas a repeater club will have written rules or a link-control procedure for this, so read those first. Finally, the trustee or club is a better first call than the repeater itself if you find a problem. A stuck PTT, a wrong tone listed online or a link stuck in the wrong state are easy for them to fix once they know. Many clubs have a contact address on their site or on the directory entry.
-
Part 97 Q&A: station ID, third-party traffic, power limits, RF safety, auxiliary/control operation and renewal
I'll take the first half. This is a plain-language summary, so check the current eCFR text before putting anything in writing for the club. Station ID (§97.119): Identify with your FCC call sign at the end of a communication and at least every 10 minutes while it continues. On voice, use English, and phonetics are allowed. On CW you ID in CW. On digital modes you can ID in the mode you're using. FT8 and similar modes put call signs in the exchanged messages, and PSK31 or RTTY operators usually just type the call. A tactical call like 'Net Control' or 'Aid Station 3' is fine for coordination, but it doesn't replace the FCC call sign. You still ID with your own call at the required times. Repeaters have their own ID requirement, and a repeater ID doesn't cover the stations using it. Third-party traffic (§97.115): You, as control operator, must be present at the control point and able to supervise. The third party can talk only at your discretion and under your close supervision. You should be ready to take over or end the contact if it drifts into something prohibited. Domestic contacts with other US amateurs are generally straightforward. International third-party traffic is where people get caught, because it is allowed only with countries that have a third-party agreement with the US. There is an exception when the third party is themselves eligible to be a control operator. Also, the message content still has to be legal, so a non-licensed person can't use you to pass business traffic. Power limits (§97.313): 1,500 W PEP output is the general ceiling, but you're also supposed to use the minimum power needed for the communication. There are lower caps in places. Technicians on their HF privileges, for example, are limited to 200 W PEP, and 30 meters is also 200 W PEP. The 60 meter band uses an ERP-based limit instead of transmitter output. So the answer isn't just '1,500 W everywhere.' Know the band, the segment, and your license class. Prohibited transmissions (§97.113): The big ones are communications for compensation, communications in which you or your employer have a business interest, broadcasting, music, obscenity or indecent language, false or deceptive signals, and messages encoded to obscure their meaning. Callsigns, Q-signals, and standard abbreviations are not 'codes' in that sense. Occasional sale or trade of your own personal equipment is generally okay. Making it a regular business is not. An immediate emergency involving safety of life or protection of property has its own rule (§97.403), but that is for real emergencies, not convenience.
-
Direwolf iGate plus fill-in digi for a mixed HT fleet (TH-D74/D75, FT5D): paths, Mic-E, SmartBeaconing and messaging
Some notes on the handhelds. All three radios can transmit Mic-E, but menu names and defaults differ by model and firmware. Don't trust that they match. Compare the actual on-air packets in Direwolf's log or on the aprs.fi raw packets page. The settings worth checking on each radio are the APRS band, the packet frequency, the beacon type, the comment and status text, and the SmartBeaconing parameters. A radio left on a voice frequency, or with APRS assigned to the wrong band, is a common reason a station never appears on the map. The D74 and D75 can also act as a KISS TNC over USB or Bluetooth, according to their manuals. That is useful for pairing with a phone or laptop, but it is a separate mode from using the internal APRS function. Check the manual for which settings apply to which. For SmartBeaconing, start from conservative values and adjust based on what the aprs.fi track looks like. Corner pegging that fires too often on winding roads will generate many packets. Slow rates that are too long leave straight-line gaps in the track. Remember that at 1200 baud one position packet occupies roughly a second or more of airtime, and every station in range has to share that. For checking the iGate path, the raw packet view on aprs.fi is more useful than the map. In the path you can see the Q-construct and the iGate callsign that injected the packet. A qAR entry followed by your iGate's callsign means the packet came from RF through that station. If your own beacon never shows up with your callsign in the path, the problem is either the RF receive chain or the APRS-IS login. If you later add a weather station or objects, give each its own SSID or object name and a slow beacon rate. Weather data is sent as an APRS weather report with fields such as wind direction and speed (c/s), gust (g), temperature in degrees F (t), rain (r, p, P), humidity (h) and pressure (b). Objects use the ; data type with a 9-character name padded with spaces, and * marks the object live while _ kills it. Treat objects as something you retransmit sparingly, and kill them when the event is over.
-
Building a VHF/UHF antenna setup: how do you weigh gain, pattern, feedline and connectors?
On the polarization point: don't skip the choke, particularly with J-poles and slim jims. If the pattern looks distorted or you pick up RF in the shack, the outside of the coax is a good suspect. A choke close to the feedpoint, and sometimes another a half-wave or so down the line, is a cheap test. It's easy to repeat with and without it, using the same location and a signal you can measure. Don't rely on SWR alone for that comparison, because it won't tell you what happened to the pattern. For satellite work with FM birds, the hardware is often simpler than people expect. A small handheld yagi plus a dual-band radio can work for a start, with a lot of the effort going into Doppler tuning and aiming. A fixed omni can catch high passes, but weak low-elevation passes are where a directional antenna shows its benefit. If you go for circular polarization, check the handedness spec and the phasing line details in the antenna's documentation, because a mismatch there costs you signal. For mobile, I'd choose NMO over a mag mount if you intend to leave the antenna on. A good, well-grounded mount at the roof center gives the most predictable results. If you're using a magnet mount, check the SWR with the antenna in its actual position and keep the coax from being pinched. Trim the whip length per the manufacturer's instructions, shortening in small steps, because you can't put metal back.
-
Planning a 24-hour EMCOMM field station: how do you separate generator, battery, and RF so noise and safety problems don't stack up?
On the RF side, I'd structure the setup so you can diagnose noise one source at a time. Before any deployment, do a baseline noise check with everything off except the radio on battery, then add loads one at a time: laptop, charger, solar controller, generator, LED lights. Cheap LED lanterns, USB chargers, and switching supplies are often the worst offenders, and they can easily be worse than the generator. A short AM or SSB listening test on a couple of bands, and noting S-meter changes, tells you more than guessing. Ferrite chokes on DC leads, USB cables, and the antenna coax are cheap to try, but treat them as experiments you verify, not magic fixes. On grounding, keep the concepts separate. Electrical safety grounding applies to the generator and any AC distribution: use GFCI protection, proper cords, and never backfeed anything into a building. Know whether your generator bonds neutral to frame, and follow the manual. RF grounding is different. A vertical or end-fed antenna may need a counterpoise or radials to work well, and a single short ground rod does not make a station lightning-safe. If thunderstorms are nearby, the safest plan is to stop operating, disconnect antennas, and take shelter. A temporary static or equipment bond can reduce shock and RF-in-the-shack issues, but don't describe it as lightning protection in your procedures. For masts, the main hazards are wind and power lines. Pick a site where a falling mast and antenna can't reach any overhead line, guy it appropriately for the conditions, and keep people away from the fall zone. A pop-up canopy with a metal frame can detune or shadow antennas, so keep the wire and especially the VHF/UHF antenna clear of it, and weigh down or stake the canopy legs for gusts. On coax, loss matters most at VHF/UHF, so use low-loss cable for longer runs there. At HF, a typical field run is less of a loss problem than common-mode current. Keep jumpers short, weatherproof outdoor connections, add strain relief, and keep coax away from power cables and the generator. Finally, put it all on a checklist with a teardown half. Setup: site and wind check, overhead hazards, generator placement and CO alarm, shelter anchoring, antennas and chokes, power distribution, noise baseline, comm check, log started. Teardown: stop transmitting, power down, disconnect antennas before lowering masts, coil coax, count stakes and guy lines, check the site for trash and fuel spills, and recharge or inventory batteries. If this is for a served agency, also write down the frequency plan, check-in schedule, and message-handling format ahead of time so the station design supports the mission.
-
Dual-band mobile rigs (FTM-500D, ID-5100A, TM-D710G): what matters in the install, and what to check before relying on cross-band repeat
On noise, a practical order is to check the antenna system first, then the power, then the accessories. Many noise complaints turn out to be a bad coax connector, a poorly grounded mount, or an NMO base sitting on a painted surface. A mag-mount on a roof can also be fine for temporary use, but a permanent mount is more consistent. Use an SWR meter or antenna analyzer to confirm the antenna is tuned for the part of the band you use most. A dual-band whip is a compromise, and it can be well matched on one band and mediocre on the other. With a noise source you have to find, bring a handheld receiver or a spare radio into the vehicle and listen at the radio's power input and near the suspected devices. Cheap USB chargers and LED lighting deserve suspicion, because many switching supplies put out hash well into the VHF range. If the noise only shows up when something is plugged in, you have your answer. One more etiquette point: when you call on a repeater while mobile, give your callsign clearly and keep the exchange short. In busy traffic it is fine to say you are mobile and may drop out. That gives the other operator context if you disappear mid-sentence.
-
Choosing a handheld: FT-65R vs ID-52A vs TH-D75 (and where the IC-705 fits), plus CHIRP, offsets and emergency setup
I'd separate the digital question from the radio question. D-STAR and DMR are only worth paying for if your area has active repeaters or you plan to run a hotspot. In that case the ID-52A or TH-D75 are well-regarded choices, though they cost a lot more than an analog radio. If you just want local FM, a D-STAR radio's extra features go unused. For DMR, plan on a different handheld and spend time on the codeplug. Color codes, time slots and talkgroup assignments cause most of the problems new users have. Getting a DMR ID registered is also a step you need to do ahead of time. The IC-705 is a great radio, but it solves a different problem. If your plans include HF SSB or CW from a park or a campsite, it makes sense. If you want something to clip on a belt for the local repeater, it isn't the right tool.
-
Reading band conditions: how do you combine SFI, K index, VOACAP and live spots before calling CQ?
One point on the K index: it's local to the observatory, and the planetary Kp is an average across stations. The practical effect depends on your location and path. High-latitude and transpolar paths usually suffer first during a geomagnetic disturbance, while a mid-latitude east-west path may be less affected. A disturbed day can also cause a lot of absorption near the poles. So I wouldn't use one K number as a pass/fail test. For the lower bands, it's also worth separating noise from propagation. A band can be open and still unusable because of local QRN, thunderstorms or man-made noise. WSPR is useful here because the reported SNR on both sides of a path gives you a rough picture of whether the limit is propagation or receiver noise. And for 6 meters in summer, ignore the solar numbers for a while. Sporadic E is seasonal, tends to cluster around the early summer months in the northern hemisphere (with a smaller winter peak), and is best tracked by watching spots and listening to beacons in the 50 MHz range.
-
Technician to General: how should I split study time across the 35 Element 3 questions?
On the HF band plan, you do need to learn the General privilege segments, but you can make it manageable by grouping. Treat the CW/data portions and the phone portions as separate pieces, and note which bands are the odd ones out. The details below are from memory of the usual band chart, so verify every edge against the current ARRL band chart or Part 97 before you rely on it for either the exam or on-air operation. As a rough guide, General phone segments include the upper part of 75 meters (3.800 to 4.000 MHz), the upper part of 40 meters starting at 7.175 MHz, 20 meters from 14.225 MHz, 15 meters from 21.275 MHz, and the portions of 17, 12, and 10 meters that allow phone. The 30-meter band is the exception: it's CW and data only, with a lower power limit than the other bands. The 60-meter band has its own channelized or otherwise special rules, so learn what the current pool asks about it. The 160-meter band is open to General operators across the amateur allocation. Memorization helps here, but many of the questions ask about a specific frequency and mode combination. For example, whether you may transmit SSB on a given frequency. Practice by picking random frequencies and deciding whether you could legally use a particular mode there. That's closer to how the question is asked than reciting band edges. On digital modes, you don't need on-air experience to pass, but a little hands-on exposure helps. The exam asks conceptual things: that PSK31 and RTTY are narrowband data modes found in the data portions, that FT8 depends on accurate computer time synchronization because transmissions happen in fixed time slots, and that a sound card interface or built-in USB audio connects the radio to the computer. Be careful on operating practices too. Know how to set audio levels so you don't overdrive the transmitter and splatter, and know that a clean digital signal is usually the result of lower, not higher, audio drive. Also review the rules on automatic control and unattended operation, because they show up in the Commission's rules questions. Vanity callsigns: the exam may include questions on how the vanity program works, such as which formats are available, who can apply, and the idea of a grace period after a license expires or a holder dies, during which family members or clubs may request the call. You don't need the full callsign group chart, but understand that vanity applications go through the FCC's licensing system and that the call you want must be available. A vanity request isn't something you need to settle before upgrading. Your current callsign stays with you after you upgrade, and a vanity call can be requested whenever you decide you want a different one. Some people find it simpler to operate on the new privileges for a while first. One last tip for the exam itself: read every answer choice. Several General questions list answers that are each true in some context, and the correct one is the one that matches the specific condition in the stem.
-
Keeping your award chase straight: what counts where for DXCC, WAS, WAZ, WPX, IOTA, POTA and SOTA?
On the DXCC side, the entity list is the first thing to keep straight. Credit follows the entity rules and the dates, not the callsign prefix alone. A station can sign something that looks like one place while operating from another, and a QSO with a deleted entity only counts if the contact falls within the period when that entity was valid. That is why a log can look right and still fail to produce credit. For LoTW, check three things whenever a QSO fails to match. First, did both stations upload? Second, do the band and mode group agree? A mode listed as USB in one log and SSB in another usually resolves fine, but a contact logged as FT8 on one side and phone on the other will not match. Third, was the contact made inside the date range of the certificate used to sign it? If an operator worked from a different DXCC entity, they need a certificate set up for that entity. For Honor Roll and Challenge, remember that only current entities count. If a deleted entity is in your total, it will not move you toward either of those. It is easy to look at an overall DXCC number and assume it translates directly to Honor Roll standing, but it does not. Keep a separate current-entity count. Card checking still exists for QSLs you cannot confirm in LoTW, so paper has not disappeared. Check the current ARRL application rules before sending anything, because the procedures and fees are updated from time to time.
-
Getting into HF nets and special event stations: how do you pick a net, check in cleanly, and chase event certificates?
On the special event side, I'd treat the event page as the source of truth, not a spot on a cluster or a social media post. Check the operating dates, the modes and bands they say they'll use, the claim process for the certificate, and the deadline. Time zones trip people up here too, since events are often listed in UTC and the window can end earlier than you expect in your local day. When you work the station, give your call clearly, confirm theirs, and copy the commemorative call exactly. It may look unusual, and a mistake in the log can mean a rejected certificate request. If a QSL or SASE is required, read the instructions carefully for address format and postage, particularly for overseas stations. It also helps to log each contact with the band, mode, and UTC date and time, since some certificates ask for multiple bands or modes. A spreadsheet or logging program with a field for the event name makes it easy to find your contacts again when the claim window opens. For picking nets, listen in for a few sessions first. You'll quickly learn whether the control keeps a strict order, how much casual conversation is welcome, and whether your signal from home is workable on that band at that hour.
-
Planning a first POTA activation: park reference, 10 QSOs, spotting, and logging, what actually matters?
On logging, whatever you choose, make the park reference part of the template, not something you type each time. Most logging programs for portable operation have fields for your own park (MY_SIG_INFO in ADIF terms) and the hunter's park if they're also activating. Do a test export before you leave and open the ADIF in a text editor to confirm the park field is actually there. It's much easier to fix the setup at the picnic table than to try to repair a file later. For the UTC issue, I'd write the UTC start time on your notes. Some people plan to get 10 contacts before 0000Z and then start a second activation if they're still on the air. If you're close to 10 as the day rolls over, it's worth knowing that the contacts after the change count toward a new UTC day. Also, check whether the park has any extra permit or hours requirement. The POTA park page usually has links and notes, but the park agency's own website is the authority on what you're allowed to do.
-
Turning SET and Field Day into real disaster comms practice: what should we be testing, and how do we write it up?
One thing that helps is separating the exercise into objectives before anyone touches a radio. For example: "Deliver ten formal messages with no transcription errors," "Bring up a station on battery power within 30 minutes," or "Switch to a backup frequency when the primary is declared unusable." Objectives like that make the AAR much easier, because you can mark each one met, partly met, or not met, and then explain why. For Field Day, I'd suggest a small side activity rather than rewriting the whole event. Set aside a block of time where one station acts as a mock shelter and another as a mock emergency operations center, and have a handful of written messages passed between them through a relay station. People still get their contacts, but a few operators get real practice with message formatting, readbacks, and logging delivery times. It also exposes the awkward gaps, like whoever is copying doesn't know how to handle an unclear word, or the log doesn't have a place for the delivery time.
-
Go-kit triage: what earns its place in the pack for a hike-in activation?
Power and logging both come down to reducing failure points. For power, I'd standardize on Powerpoles, put an inline fuse close to the battery positive, and label the pack with its capacity and voltage range. A 10 W SSB or CW day on a 6-10 Ah LiFePO4 pack can easily cover a couple of hours, but your radio's current draw on transmit and receive determines the real answer. Doing a rough watt-hour calculation before you go is better than guessing. Also, if the radio has a low-voltage shutdown, check where it falls compared with the battery's BMS cutoff. Some rigs behave oddly well before the battery is truly empty. For logging, one workable approach is to keep paper as the primary record and add a second layer, like a phone app or voice memo, only as backup. Write callsign, time in UTC, band, mode, and RST, plus park or summit reference. Park-to-park and summit-to-summit contacts are easy to forget to mark if you're busy, so a column for that helps. Then enter the log at home while it's fresh and export it in the format your program needs. Check the current POTA and SOTA rules before you go, as submission requirements and upload formats can change. For safety, set a turnaround time before you leave and stick to it. If you can hear thunder, it's time to lower the antenna, disconnect the coax, and move to safer ground. A fiberglass pole doesn't protect you from lightning, and a summit is the last place to wait it out. Cold wind and heat are usually the more likely problems, so pack layers and water, and don't let the fun of a pile-up make you skip breaks. For a Field Day style setup the same logic scales up: separate the noisy gear (generators, chargers) from the antennas, keep the power distribution fused and labeled, and have a paper backup of the log in case the computer fails.
-
Hamfest season planning: how do you get the most out of swap meets, club nights, VE sessions and Field Day?
For the club side, I'd say a good club meeting is half business and half practical. Business means treasury, repeater upkeep and event signups. The practical half is the part that keeps people coming back: a short talk, a demo, a build session, or a table of people trading ideas. Programs that work well tend to be small and specific, like how to build a 2 m J-pole, how to set up a digital mode, or how to log contacts for Field Day. If you're new, ask whether the club has an Elmer or mentor list. Most clubs have a few people who like answering questions about antennas, grounding, rig setup or test prep, and they're often glad to be asked. If you want to give back, offer to help with something concrete like the VE team's setup, a Field Day logging shift, or a prize table at the club's hamfest. Forums and prize drawings at hamfests are worth a look too. The forums are often where you pick up one useful idea, like a better grounding scheme or a new way to run a portable station. The raffle is just for fun, so don't count on it as part of your budget.
-
Planning a field comms station: antenna choice, power budget, and keeping generator noise out of the receiver
The EFHW is a reasonable choice for a compact multiband antenna, but it depends heavily on how the feedline and counterpoise behave. The matching transformer at the feedpoint presents a high impedance that is only roughly 50 ohms after transformation, so the SWR on each band can vary with wire height, sloping geometry, and nearby objects. The coax shield also tends to become part of the antenna, which is why you plan chokes. I would put the first choke close to the transformer and a second one at the radio end or a short distance back. Test both on receive, since a noisy receiver often improves when the choke is added. A dipole is easier to reason about because it is balanced and resonant on a single band with predictable feedpoint impedance. If operations are mostly 40 m and one higher band, a fan dipole or a simple dipole for each band can be more predictable than an EFHW that may need a tuner. The tradeoff is more support points and wire. For NVIS on 80/40 m, a dipole 0.1 to 0.25 wavelength above the ground is a typical starting range, and it tends to favor close-in contacts over long distance. Pick the height based on the distances you need to cover, not on what feels tidy. Before leaving, set up everything once as a dry run: antenna, feedline, battery, radio, laptop, and any DC converters. Check the receiver noise floor with the generator off, then with the generator running at several distances, and record what changes. Also check SWR across the bands you plan to use and confirm that the radio doesn't reset or show RF feedback on the laptop interface during transmit. USB cables and audio interfaces are common weak spots, and snap-on ferrites on the USB, power, and audio leads are inexpensive to try. Finding those faults in the yard is much easier than in the field.
-
Making SET and Field Day count: turning exercises into real disaster comms readiness
One inject type that tends to expose problems fast is the "conflicting information" message. Give two stations slightly different versions of the same shelter status, or send a message with a number that doesn't match an earlier one, and see whether the net catches it. It tests whether operators read back figures, whether net control asks for verification, and whether anyone knows to flag a message as unconfirmed instead of passing it along as fact. On the newer-operator question, one approach is to run parallel tracks. Experienced operators handle the multi-hop relays and mode changes, while newer operators get simple, well-defined jobs like check-ins, short messages to a known station, or logging. Rotate people between roles in later rounds so nobody stays in the easy lane. The scenario stays realistic, but the first experience isn't a pileup.